From dlewis at agilemind.com  Fri May 18 18:24:59 2007
From: dlewis at agilemind.com (Deb Lewis)
Date: Fri, 18 May 2007 15:24:59 -0700
Subject: [Masterview-devel] Masterview was in the DRY Views tutorial on
	Friday
Message-ID: <000301c7999b$628ee120$d60c0a0a@cx797990aDLI9>

http://codefluency.com/assets/2007/5/18/VisForVexing.pdf

Check it out, I didn't realize we were in this tutorial talk!

We need to contact these guys and correct the misconception that MasterView
requires a separate generation step.

~ Deb


From jeff.barczewski at gmail.com  Sat May 19 01:12:12 2007
From: jeff.barczewski at gmail.com (Jeff Barczewski)
Date: Sat, 19 May 2007 00:12:12 -0500
Subject: [Masterview-devel] Masterview was in the DRY Views tutorial on
	Friday
In-Reply-To: <000301c7999b$628ee120$d60c0a0a@cx797990aDLI9>
References: <000301c7999b$628ee120$d60c0a0a@cx797990aDLI9>
Message-ID: <19cda190705182212m534cf43btbddb3341c8ab7baa@mail.gmail.com>

I agree. I didn't know that either or I would have went to it.

They said in the slides that it requires a generation step (which is true)
except that this step is automatic when a change in a template is detected.

I will put together an email that clarifies this.

Thanks,

Jeff


On 5/18/07, Deb Lewis <dlewis at agilemind.com> wrote:
>
> http://codefluency.com/assets/2007/5/18/VisForVexing.pdf
>
> Check it out, I didn't realize we were in this tutorial talk!
>
> We need to contact these guys and correct the misconception that
> MasterView
> requires a separate generation step.
>
> ~ 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 on Rails Training and Consultancy
http://inspiredhorizons.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/masterview-devel/attachments/20070519/826dedca/attachment.html 

From djlewis at acm.org  Tue May 29 03:07:25 2007
From: djlewis at acm.org (Deb Lewis)
Date: Tue, 29 May 2007 00:07:25 -0700
Subject: [Masterview-devel] Explicit dependency on Rails Inflector module
Message-ID: <001101c7a1c0$02c1da40$6501a8c0@cx797990aDLI9>

Jeff - Ran into this while checking out my rails dev system on mac (yay!).
Was trying to run the unit tests w/out having Rails installed to see if
MasterView can be run completely independently, which might be a useful
scenario to consider.  Interesting exercise in any case to explore
unintended dependencies which often creep in.

But... TemplateSpec uses ActiveSupport's Inflector module for mapping
controller/action names onto snake-case names used in file system refs, with
explicit require in masterview.rb.

Take a look when you get a chance and give me opinion on this dependency -
if MasterView::TemplateSpec.create_empty_shell_for_action is only invoked in
ops which would only be performed w/in a rails context, we could redo the
require so it quietly nop's or in some other fashion ensure that the
dependency is only activate when suitable.  All the unit tests run except
three tests in template_test which are explicitly excercising this function.

~ Deb


From jeff.barczewski at gmail.com  Tue May 29 18:55:20 2007
From: jeff.barczewski at gmail.com (Jeff Barczewski)
Date: Tue, 29 May 2007 17:55:20 -0500
Subject: [Masterview-devel] Explicit dependency on Rails Inflector module
In-Reply-To: <001101c7a1c0$02c1da40$6501a8c0@cx797990aDLI9>
References: <001101c7a1c0$02c1da40$6501a8c0@cx797990aDLI9>
Message-ID: <19cda190705291555u9016586q2bf2a03955f0066f@mail.gmail.com>

Great! Yes, we can certainly do something to fix this.

And yes, create_empty_shell_for_action only currently makes sense in rails
where we are using layouts.


On 5/29/07, Deb Lewis <djlewis at acm.org> wrote:
>
> Jeff - Ran into this while checking out my rails dev system on mac (yay!).
> Was trying to run the unit tests w/out having Rails installed to see if
> MasterView can be run completely independently, which might be a useful
> scenario to consider.  Interesting exercise in any case to explore
> unintended dependencies which often creep in.
>
> But... TemplateSpec uses ActiveSupport's Inflector module for mapping
> controller/action names onto snake-case names used in file system refs,
> with
> explicit require in masterview.rb.
>
> Take a look when you get a chance and give me opinion on this dependency -
> if MasterView::TemplateSpec.create_empty_shell_for_action is only invoked
> in
> ops which would only be performed w/in a rails context, we could redo the
> require so it quietly nop's or in some other fashion ensure that the
> dependency is only activate when suitable.  All the unit tests run except
> three tests in template_test which are explicitly excercising this
> function.
>
> ~ 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 on Rails Training and Consultancy
http://inspiredhorizons.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/masterview-devel/attachments/20070529/40f81326/attachment-0001.html 

From jeff.barczewski at gmail.com  Wed May 30 17:56:20 2007
From: jeff.barczewski at gmail.com (Jeff Barczewski)
Date: Wed, 30 May 2007 16:56:20 -0500
Subject: [Masterview-devel] Preparing to do 0.3.3 release,
	anything else that needs to be in there?
Message-ID: <19cda190705301456k149b9153o1c1f56189cf54f4b@mail.gmail.com>

Deb,

I have went through an additional look at the 0.3.3 changes, and am closing
in on a release. Is there anything else that needs to be in there? I would
like to get this out soon if possible.

We can probably wait on the change for to eliminate need for rails class
(pure ruby) unless you think it is easy fix.

Thanks,

Jeff
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/masterview-devel/attachments/20070530/dafe4b24/attachment.html 

From djlewis at acm.org  Wed May 30 19:53:00 2007
From: djlewis at acm.org (Deb Lewis)
Date: Wed, 30 May 2007 16:53:00 -0700
Subject: [Masterview-devel] Preparing to do 0.3.3 release,
	anything else that needs to be in there?
In-Reply-To: <19cda190705301456k149b9153o1c1f56189cf54f4b@mail.gmail.com>
References: <19cda190705301456k149b9153o1c1f56189cf54f4b@mail.gmail.com>
Message-ID: <000c01c7a315$a8074d40$6601a8c0@cx797990aDLI9>

?store your RailsConf lightning talk?  [and any other preso's you might have
from SL ruby that you'd like to post]
 
but nothing that needs to hold us up, I think.  I have a hack patch for the
Rails Inflector dependency that allows our unit tests running on both Mac
and Windows - it's superficially easy to fix but I don't like what I did and
would prefer to hold off and think it through before submitting.
 
My "burning issues" right now are all doc improvements and nothing's ready
yet - better user docs; have some pieces of code to pull together so we can
extract directive documentation from rdoc content.
 
~ Deb

  _____  

From: masterview-devel-bounces at rubyforge.org
[mailto:masterview-devel-bounces at rubyforge.org] On Behalf Of Jeff Barczewski
Sent: Wednesday, May 30, 2007 2:56 PM
To: masterview-devel at rubyforge.org
Subject: [Masterview-devel] Preparing to do 0.3.3 release,anything else that
needs to be in there?


Deb,

I have went through an additional look at the 0.3.3 changes, and am closing
in on a release. Is there anything else that needs to be in there? I would
like to get this out soon if possible.

We can probably wait on the change for to eliminate need for rails class
(pure ruby) unless you think it is easy fix. 

Thanks,

Jeff

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/masterview-devel/attachments/20070530/097a7b94/attachment.html