search

revans / Ti

A Rapid Development framework for Titanium
http://www.codewranglers.org
MIT License
88 stars 21 forks source link

When generating a view, it always replace the stylesheet #1

Closed baldrailers closed 13 years ago

rupakg commented 13 years ago

Can you explain what you expect it should do and what is the behavior now?

baldrailers commented 13 years ago

the current behavior is that when you generate a view

ti s window Settings main

This will generate a template stylesheet located in app/<app_name/stylesheets/_settings.sass

When you have updates to that file, say you already have modifications and you generate another view under Settings

ti s window Settings details

This will replace the sass in the app/<app_name>/stylesheets/_settings.sass using the default template that ti provides.

We need to be able to detect if the file already exists and then ask the user if they want to replace it or not.

revans commented 13 years ago

I'd have to look, but I think Rails 3.1 is going to be creating an individual sass/coffee file for each view. If so, that is something that we might to do as well. e.g.

ti s window Settings main #=> app/::app_name::/stylesheets/settings/main.sass

ti s window Settings details #=> app/::app_name::/stylesheets/settings/details.sass

baldrailers commented 13 years ago

Actually if we adapt what Robert is saying, that will be faster to implement, the next question is that, do we really limit the folder creation into that part like:

app/::app_name::/stylesheets/settings/main.sass and app/::app_name::/stylesheets/settings/details.sass

what if a user wants to have another view under settings/details

revans commented 13 years ago

I'm trying to think through a reason why someone would choose to do:

app/::app_name::/stylesheets/settings/details.sass app/::app_name::/stylesheets/settings/details/main.sass

instead of something like:

app/::app_name::/stylesheets/settings/details/index.sass app/::app_name::/stylesheets/settings/details/main.sass

I think if we supported the former, we'd be encouraging bad design. Thoughts?

baldrailers commented 13 years ago

I think the idea is to have every views on their own sass file, but if it's already member of a domain, it should stick there?

The current implementation:

app/::app_name::/stylesheets/_settings.sass

baldrailers commented 13 years ago

I think we can close this 98c3906