Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scaffold Generation Unneccessary? #2

Open
jrwest opened this issue Feb 21, 2010 · 4 comments
Open

Scaffold Generation Unneccessary? #2

jrwest opened this issue Feb 21, 2010 · 4 comments

Comments

@jrwest
Copy link
Collaborator

jrwest commented Feb 21, 2010

Do the Jobs views & controllers, other scaffolding provided with b-fu really need to be generated? I don't see anything in them where templates are needed. We could just add a UI path and add it to the necessary load paths. Developers have to add to their routes.rb anyway. See http://github.com/jrwest/rcumber for an example.

@ncr
Copy link
Owner

ncr commented Feb 22, 2010

I completely agree. Maybe we could use Rails 3 way of doing this - a subapp?

@jrwest
Copy link
Collaborator Author

jrwest commented Feb 22, 2010

subapp seems like good idea, especially if that was how Rails3 intends for it to be used but then do we risk losing <= 2.3.5 support? seems like many repos (rspec and some other big ones included) are coming to same fork in road, whether to maintain 2 repos one that supports rails 2 the other rails 3. or one that supports both. Maybe this needs to be a separate discussion point tho.

@ncr
Copy link
Owner

ncr commented Feb 22, 2010

Differences between Rails 2 and 3 are too big to keep compatibility without having ugly code. I prefer moving forward, what you say? :)

@jrwest
Copy link
Collaborator Author

jrwest commented Feb 22, 2010

Yea I agree. We can keep the old stable branch up for people who want to use it. Call the new release B-Fu 2 and only support rails 3. People can grab the old stable branch from <= 2.3.5. If there is real request for it we can always merge things we know are supported into the old branch.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants