Jeff - greetings! Hard to believe, but I''m gonna break loose some time for rails and masterview at last!! I''m making a pass at upgrading a site to rails 2.0 and shaking out whatever issues show up with hooking in masterview, so I forked off a branch to keep track of what I''m changing as I do that. I did some experiments a couple months ago with running masterview in standalone configurations and wasn''t very happy with any of my solutions, so never commmitted anything. Fundamementally our whole configuration and initialization turns out to be much too tightly coupled to rails assumptions. So I''m probably going to be fairly aggressive about rethinking this whole area as part of seeing what needs to change for Rails 2.0 so that we end up with a cleaner approach to using masterview in diff operating contexts (say.... merb!!) Would like to get this going over the next week or so - would like to have a good story for RailsConf that masterview is up-to-date and still alive. ~ Deb
On Sat, May 10, 2008 at 12:50 PM, Deb Lewis <djlewis at acm.org> wrote:> Jeff - greetings! Hard to believe, but I''m gonna break loose some time > for rails and masterview at last!!Wonderful!> > > I''m making a pass at upgrading a site to rails 2.0 and shaking out > whatever issues show up with hooking in masterview, so I forked off a > branch to keep track of what I''m changing as I do that.Great!> > > I did some experiments a couple months ago with running masterview in > standalone configurations and wasn''t very happy with any of my > solutions, so never commmitted anything. Fundamementally our whole > configuration and initialization turns out to be much too tightly > coupled to rails assumptions. So I''m probably going to be fairly > aggressive about rethinking this whole area as part of seeing what > needs to change for Rails 2.0 so that we end up with a cleaner approach > to using masterview in diff operating contexts (say.... merb!!)I agree, we need to make it easy to go between many of the Ruby web frameworks, especially merb. Some of the ruby frameworks are supporting the Rack api which is supposed to make it easy to plug and play web frameworks. I''m sure that only touches the surface though and we still need a good way to config and init. I would welcome whatever we can do to make this simpler and less dependent on Rails. This is definitely a direction I wanted to go for some time now. I would love for us to be able to move between these environments easily.> > > Would like to get this going over the next week or so - would like to > have a good story for RailsConf that masterview is up-to-date and still > alive.I agree. Has been on my plate for sometime too. I have lots of things to discuss with you about next major version of MasterView, we can discuss at conference, I plan to have some details written up to make it productive discussion. Can''t start on that until we have any Rails 2.0 and any portability issues worked out, so let me know if you get hung up on anything or want me to look at. I''m hoping to make some time dedicated to MV as well. I need to use it in the near future for another big project so we should get some good updates in these coming months. Have a blessed day! Thanks for all your help and inspiration! Jeff -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://rubyforge.org/pipermail/masterview-devel/attachments/20080512/62653036/attachment.html>
status update: spent the weekend poking around, as much about reviewing and tweaking my own rails app as focusing on the masterview side - there are some changes in how the config/init mechanisms work which are actually quite nice, seems to clean up the app and I think has some hooks to solve some problems I never quite saw how to cope with in older versions having to do with plugin loading order and possible interactions between mv directive impls and plugin code. So far just a few relatively minor tweaks in rendering methods to clean up some deprecated methods we used in places we''re hooking into the rails rendering framework. In the midst of sorting out a problem with template rendering and what we did to hook in our masterview admin controller - believe there''s now a clean way to add its layouts into the general rendering framework, there''s a new notion of view_paths in Rails 2.0 and I think we just want to tack our MV extras/app/views dir onto the end of the list of view_path''s that normally contains the main app/views, then our admin views and layouts will get picked up normally if not overridden by the app itself. Probably other wrinkles will show up when introducing the REST stuff, but for now I''m just working through the vanilla old-style rhtml views arrangement. What are your RailsConf travel plans? I''m flying up on Wednesday, so will be kicking around that afternoon/eve before things start on Thu. Spaced out on making hotel reservations, so had to scramble last week to find a room - staying at low-rent (in all senses) place right by OCC. ~ Deb