Masterview devel - Feb 2009 - Working on rails 2.1 masterview at last

Finally getting into this so we can get up on rails 2.1, but looks like 
it''s gonna be almost as painful as the rework for hooking into rails 
2.0 - the code we need to hook into has been refactored and it''s very 
slow going unravelling where assumptions and approach have been 
changed; I can at least debug in the framework when necessary, but it''s
extraordinarily slooooooooooow.

~ Deb

How about if we simply remove the configuration to allow in memory and just
make it go direct to file always. Then we don''t need to maintain any of
that
code. Writing to file allows all the normal stuff to work as it should in
any version of rails.

And we now have rake tasks to clean up things as well.

Jeff

On 2/15/09, Deb Lewis <djlewis at acm.org> wrote:
>
> Finally getting into this so we can get up on rails 2.1, but looks like
> it''s gonna be almost as painful as the rework for hooking into
rails
> 2.0 - the code we need to hook into has been refactored and it''s
very
> slow going unravelling where assumptions and approach have been
> changed; I can at least debug in the framework when necessary, but
it''s
> extraordinarily slooooooooooow.
>
> ~ Deb
> _______________________________________________
> Masterview-devel mailing list
> Masterview-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/masterview-devel
>


-- 
Jeff Barczewski, MasterView core team
Inspired Horizons Ruby Mentoring and Development
http://inspiredhorizons.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
<http://rubyforge.org/pipermail/masterview-devel/attachments/20090408/1b16adb1/attachment.html>

On Wed, 8 Apr 2009 17:02:53 -0500, Jeff Barczewski
wrote:
> How about if we simply remove the configuration to allow in memory and just
> make it go direct to file always. Then we don''t need to maintain
any of that
> code. Writing to file allows all the normal stuff to work as it should in
> any version of rails.
> 
> And we now have rake tasks to clean up things as well.
True.... but.  I know for my own development I really really do want 
rendering directly from my masterview view templates and auto-detect of 
changes, it''s a huge time-saver and kruft-reduction in my workflow.

I got the initial part of rails 2.1 integration working a month ago, 
s.t. rendering would pick up rhtml coming out of a masterview template, 
but then needed to decipher the hooks for change detection and had to 
leave things at that point.  I was on the road pretty much all of March 
and no time to continue; back now and have some time reserved this 
weekend to see if I can finish unravelling, because this is blocking 
some work I want to do.

You going to be at railsconf?

~ Deb

On Fri, 10 Apr 2009 13:37:29 -0700, Deb Lewis wrote:
> have some time reserved this 
> weekend to see if I can finish unravelling
ok, I think I got the Rails 2.1 ERB compilation unravelled, just needed 
some quiet time to get my brain wrapped around what''s going on.  The 
code''s ugly and I think we''ve got some real perf issues to
track down,
but things seem to basically work again.  Committed to trunk in our 
repos.

I''m going to look at Rails 2.2 and 2.3 tomorrow and see if I can get 
that going quickly so we''re caught up to the current version of the 
platform; hopefully less change in the rendering subsystem that we had 
in 2.0 and 2.1.

If I can get that stabilized, it''ll give us a window to get onto Rails 
3 before the release and consider whether there are framework changes 
we''d like to propose.

~ Deb

On Mon, 20 Apr 2009 10:21:10 -0500, Jeff Barczewski
wrote:
> You going to be at railsconf?
> 
> Doesn''t look like it is going to work this year :-(  but I am
going to try
> and follow all the blog coverage of it.
> 
> Hoping to maybe do Rubyconf this year.
Ah well.  I was on the fence about going, but Las Vegas isn''t a bad 
drive from socal so I''m gonna go.  (much as I dislike LV and the whole 
NV gambling scene)

I''d actually be (more?!) interested in RubyConf, any word on when and 
where that''ll be this year?

~ Deb