can you write a skin loader instead? And use the fact that css was created to solve this problem?
A few tweaks can become a nightmare to manage if your not familar with designing product lines. On Aug 30, 2011 4:41 PM, "Fearless Fool" <[email protected]> wrote: > Good news everyone: a customer wants to license our Rails-based app! > (Maybe we'll be able to afford something fancier than ramen noodle for > dinner!!!) The bad news is that they want a custom logo, custom color > scheme and "a few tweaks here and there". > > What are the established techniques for managing "a few tweaks here and > there"? > > Creating branch in git seems like it will do almost everything > necessary. The only complication I see is that we'll have to > back-merge enhancements and bug fixes in the main branch, but that would > be true for any approach. > > Simply stated: is there a compelling reason NOT to use git for creating > multiple 'skins'? > > - ff > > -- > Posted via http://www.ruby-forum.com/. > > -- > You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to [email protected]. > For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en. > -- You received this message because you are subscribed to the Google Groups "Ruby on Rails: Talk" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/rubyonrails-talk?hl=en.
