From info at gauda.de  Tue Jul  8 06:45:09 2008
From: info at gauda.de (gauda)
Date: Tue, 8 Jul 2008 12:45:09 +0200
Subject: [Masterview-users] Problem with Rails 2.1
In-Reply-To: <20080604101526288498.b4410a1f@acm.org>
References: <4f081d850806040705l11dd2a4byf5ecb99b6a50b5d4@mail.gmail.com>
	<20080604101526288498.b4410a1f@acm.org>
Message-ID: <5973e83c0807080345p3b885134oa918bdef79382180@mail.gmail.com>

hello jeff,
is there a time planning when you'll release this good stuff for rails 2.1?
i hope you will do this. as i see the website is down :(

On Wed, Jun 4, 2008 at 19:15, Deb Lewis <djlewis at acm.org> wrote:
> Our MasterView hooks to compiling directly into the erb view cache in
> Rails doesn't work in Rails 2.0 either.  There were some changes in the
> ActiveView framework in 2.0 that affect how we need to hook in the
> template system, and further changes in this area in the just-released
> 2.1.
>
> I'm working on the rails 2.0 changes for MasterView right now - the
> basic changes we need to make for hooking into the view framework are
> understood, but I need to do more testing and tighten up the code
> before we release this.  I'll do the Rails 2.1 integration as soon as
> the 2.0 integration fixees are stabilized.
>
> Hopefully soon... got "de-railed" from updating MasterView while at
> RailsConf, so will get back to finishing this over the coming week.
>
> ~ Deb
> _______________________________________________
> Masterview-users mailing list
> Masterview-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/masterview-users
>



-- 
so long,
HANS

From jeff.barczewski at gmail.com  Tue Jul  8 12:29:47 2008
From: jeff.barczewski at gmail.com (Jeff Barczewski)
Date: Tue, 8 Jul 2008 11:29:47 -0500
Subject: [Masterview-users] Problem with Rails 2.1
In-Reply-To: <5973e83c0807080345p3b885134oa918bdef79382180@mail.gmail.com>
References: <4f081d850806040705l11dd2a4byf5ecb99b6a50b5d4@mail.gmail.com>
	<20080604101526288498.b4410a1f@acm.org>
	<5973e83c0807080345p3b885134oa918bdef79382180@mail.gmail.com>
Message-ID: <19cda190807080929p26304cf3hfaa56a3606d1741d@mail.gmail.com>

On Tue, Jul 8, 2008 at 5:45 AM, gauda <info at gauda.de> wrote:

> hello jeff,
> is there a time planning when you'll release this good stuff for rails 2.1?
> i hope you will do this. as i see the website is down :(



Thanks for letting me know about the website, provider must have changed
something. I am looking into it now.

I'll let Deb comment on when she thinks the changes might be ready for
release.

Jeff



>
>
> On Wed, Jun 4, 2008 at 19:15, Deb Lewis <djlewis at acm.org> wrote:
> > Our MasterView hooks to compiling directly into the erb view cache in
> > Rails doesn't work in Rails 2.0 either.  There were some changes in the
> > ActiveView framework in 2.0 that affect how we need to hook in the
> > template system, and further changes in this area in the just-released
> > 2.1.
> >
> > I'm working on the rails 2.0 changes for MasterView right now - the
> > basic changes we need to make for hooking into the view framework are
> > understood, but I need to do more testing and tighten up the code
> > before we release this.  I'll do the Rails 2.1 integration as soon as
> > the 2.0 integration fixees are stabilized.
> >
> > Hopefully soon... got "de-railed" from updating MasterView while at
> > RailsConf, so will get back to finishing this over the coming week.
> >
> > ~ Deb
> > _______________________________________________
> > Masterview-users mailing list
> > Masterview-users at rubyforge.org
> > http://rubyforge.org/mailman/listinfo/masterview-users
> >
>
>
>
> --
> so long,
> HANS
> _______________________________________________
> Masterview-users mailing list
> Masterview-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/masterview-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://rubyforge.org/pipermail/masterview-users/attachments/20080708/913f17c3/attachment.html>

From djlewis at acm.org  Thu Jul 10 00:44:33 2008
From: djlewis at acm.org (Deb Lewis)
Date: Wed, 9 Jul 2008 21:44:33 -0700
Subject: [Masterview-users] Problem with Rails 2.1
In-Reply-To: <19cda190807080929p26304cf3hfaa56a3606d1741d@mail.gmail.com>
References: <4f081d850806040705l11dd2a4byf5ecb99b6a50b5d4@mail.gmail.com>
	<20080604101526288498.b4410a1f@acm.org>
	<5973e83c0807080345p3b885134oa918bdef79382180@mail.gmail.com>
	<19cda190807080929p26304cf3hfaa56a3606d1741d@mail.gmail.com>
Message-ID: <20080709214433182265.4be77c87@acm.org>

(masterview.org is back up, thx jeff!)

apologies that the 2.x updates of Masterview are slow getting out...  
I've gotten stalled on the 2.0 updates out - the bulk of the rework 
needed was done weeks ago, but I have to finish testing some of the 
exception cases before these changes are safe to release.  I expect the 
2.1 updates to be easier, but we know that there are framework changes 
in the areas where we have do some rather ugly hooks to get into the 
rails page rendering cycle, so it probably won't be just a trivial 
tweak.

For the record, the main masterview template rendering engine itself 
isn't affected at all - the tricky area is integrating into the rails 
rendering framework so MV templates work properly in a rails app.  So I 
haven't tried it yet, but you could probably get running on 2.1 if 
you're willing to use the MV generate_rhtml_files option to pre-compile 
all your masterview view templates into .rhtml.  You lose auto-reload 
of changes during development, which is sad, but if your views are 
fairly stable that might be acceptable as a short-term workaround.

I'm still hoping to get the 2.0 changes wrapped up this weekend, but 
I'm under serious deadline pressure through the end of the month with 
work commitments.  So realistically I probably won't have any time to 
do the 2.1 update until beginning of August.

~ Deb

On Tue, 8 Jul 2008 11:29:47 -0500, Jeff Barczewski wrote:
> On Tue, Jul 8, 2008 at 5:45 AM, gauda <info at gauda.de> wrote:
> 
>> hello jeff,
>> is there a time planning when you'll release this good stuff for rails 2.1?
>> i hope you will do this. as i see the website is down :(
> 
> Thanks for letting me know about the website, provider must have changed
> something. I am looking into it now.
> 
> I'll let Deb comment on when she thinks the changes might be ready for
> release.
> 
> Jeff
>