On Wed, Nov 3, 2010 at 3:17 PM, Lille <[email protected]> wrote:
> OK, a final question. If I go out into the freelance marketplace, how > do I protect my proprietary models? With a preloaded set of html > templates, I get around this problem, bc I don't need to provide > anything else, but if the designer needs to run Rails, then they get > everything. What are my options, mocking everything? > Thats an interesting question - I have not dealt with this but is a real problem. Maybe give ftp rights just to the views folder on your staging environment, let them upload changes and then they can see them in contxt of the app. Of course that kind of bypasses source control which you would have to work out. Curious what others would suggest. > > Lille > > On Nov 3, 12:09 pm, David Kahn <[email protected]> wrote: > > On Wed, Nov 3, 2010 at 9:55 AM, Lille <[email protected]> wrote: > > > Thanks for the clarification of the erb matter. (I guess the basic > > > requirement of these scripts is the employment of a vernacular that > > > any designer can work with.) > > > > > OK, so get a GitHub account and RSpec the views, e.g., to ensure that > > > any html elements involved in client-side functionality remain intact. > > > > For views, even better try cucumber. I adopted it a couple months ago and > > find that it makes writing tests simpler (using Engligh rather than so > much > > code), helps focus the tests through the user experience, and has > faculties > > to use selenium or similar to test javascript/ajax, which is something > that > > you might want to make sure has not broken with collaborating. > > > > > > > > > Comments on good 'marketplaces' for RoR-savvy designers invited... > > > > Cant help much here but I would think if you find someone who has worked > > with php, working with Rails Erb should be an easy switch. But also > depends > > on the complexity of your designs and how much interaction there is > between > > design and code. > > > > > > > > > Lille > > > > > On Nov 3, 11:49 am, David Kahn <[email protected]> wrote: > > > > On Wed, Nov 3, 2010 at 9:37 AM, Lille <[email protected]> > wrote: > > > > > Hi, > > > > > > > I've written all my view templates in erb, but now I need to > convert > > > > > them to straight html so that designers can work with them. How do > I > > > > > do this? > > > > > > Not possible - your designers have to know to work around the erb > > > portions, > > > > however all the erb should be framed within html so they should be > able > > > to > > > > work with the views as is. This is the case with every framework I > know - > > > > php, .net, rails, etc, that there will always be to a degree some > > > artifacts > > > > in the html/view file. > > > > > > > In this connection, any comments on best practices for working on > RoR > > > > > apps with designers would be appreciated. > > > > > > As far as work flow, depends on what you use for source control and > > > whether > > > > they have a source control account or whether you will just manually > > > manage > > > > the commits. Bottom line is that you should have tests for your app, > and > > > > commit regularly, including changes from designers to assure that > nothing > > > > has broken. Some others may have more extensive experience and advice > on > > > > this. > > > > > > > thanks, > > > > > > > Lille > > > > > > > -- > > > > > 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]<rubyonrails-talk%[email protected]> > <rubyonrails-talk%[email protected]<rubyonrails-talk%[email protected]> > > > > > <rubyonrails-talk%[email protected]<rubyonrails-talk%[email protected]> > <rubyonrails-talk%[email protected]<rubyonrails-talk%[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]<rubyonrails-talk%[email protected]> > <rubyonrails-talk%[email protected]<rubyonrails-talk%[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]<rubyonrails-talk%[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.
