Closed jess closed 12 years ago
Seems like an OK idea in general, but I'm not real keen on automatic conversion from erb->haml; I think I'd prefer to just see seperate starter templates for haml. Think you can try taking that path?
Hey @ntalbott this was the path @jess and I had discussed offline. Why aren't you keen on automatic conversion?
In general I just don't trust auto-converters; hand-crafted almost always comes out better IMO. Plus, it's not an approach that (as far as I know) would work for other template types, so haml would end up being a one-off instead of setting the stage for a bunch of different possible defaults.
HI Guys,
This was the issue I had. (This was back in November, so it may have changed??)
Check out this video first: http://screencast.com/t/u4pTs7oL
Then see this issues with converting html5 to haml...looks like there's an open issue. Link 1
Yah, that issue :smile:
So I'd recommend that each skeleton type have its own set of templates if we're going to do custom skeleton types.
Would be nice if templates could declare dependancies on other templates. So we could have one template declare the skeletal CSS and another inset the view templates.
I'm fine with whatever solution you guys want to pull together here.
I personally don't care enough about this to implement it, but will gladly review patches that make it happen. Going to close this PR out, though, since I think we agree it isn't the right approach.
Here's a good start...we just need to work in the error notifications if they don't have proper gems installed.