From ed.howland at gmail.com  Thu Jun  8 12:41:41 2006
From: ed.howland at gmail.com (Ed Howland)
Date: Thu, 8 Jun 2006 11:41:41 -0500
Subject: [Masterview-users] Logging from within a directive
Message-ID: <3df642dd0606080941n316acca0l196c933e2aae725f@mail.gmail.com>

Hi,

I assume that the default logging level is Logger::DEBUG since by
setting that in init.rb, I get lots of log messages in the WEBrick
console window, like when the log level is not set. But if I put

Log.debug "content_str #{content_str}"

in my etag method of my directive, I don't see any output in that same
window (or in log/development.log)

Any ideas?

TIA,
Ed



-- 
Ed Howland
http://greenprogrammer.blogspot.com

From ed.howland at gmail.com  Thu Jun  8 12:48:22 2006
From: ed.howland at gmail.com (Ed Howland)
Date: Thu, 8 Jun 2006 11:48:22 -0500
Subject: [Masterview-users] Link_to_remote documentation
Message-ID: <3df642dd0606080948j113c442aq5e15a586d66173d1@mail.gmail.com>

Hi,

The documentation at masterview.org for the link_to_remote directive
may be a bit off. In order to make it work I needed the example to be:

<a mv:link_to_remote=":url => {:action => 'new'}">New product</a>

          becomes

%= link_to_remote 'New product',  :url => {:action => 'new'} %>

Note, that I am using RJS templates, which do not use the :update tag
in the link_to_remote. The proper Non-RJS example would probably look
like:

<a mv:link_to_remote=":update => 'mydiv', :url => {:action =>
'new'}">New product</a>


Ed
-- 
Ed Howland
http://greenprogrammer.blogspot.com

From jeff.barczewski at gmail.com  Thu Jun  8 16:28:30 2006
From: jeff.barczewski at gmail.com (Jeff Barczewski)
Date: Thu, 8 Jun 2006 15:28:30 -0500
Subject: [Masterview-users] Logging from within a directive
In-Reply-To: <3df642dd0606080941n316acca0l196c933e2aae725f@mail.gmail.com>
References: <3df642dd0606080941n316acca0l196c933e2aae725f@mail.gmail.com>
Message-ID: <19cda190606081328p223be4c7g3296a7fac959f112@mail.gmail.com>

The Logger is set on the MasterView module so you would probably need to
refer to it like

MasterView::Log.debug "foo"

or even better use

MasterView::Log.debug { "foo" }

The second form is better since it is a block and the block won't get
executed if the output level is above debug which saves cpu if you were
doing any string building concatenating, etc.

On 6/8/06, Ed Howland <ed.howland at gmail.com> wrote:
>
> Hi,
>
> I assume that the default logging level is Logger::DEBUG since by
> setting that in init.rb, I get lots of log messages in the WEBrick
> console window, like when the log level is not set. But if I put
>
> Log.debug "content_str #{content_str}"
>
> in my etag method of my directive, I don't see any output in that same
> window (or in log/development.log)
>
> Any ideas?
>
> TIA,
> Ed
>
>
>
> --
> Ed Howland
> http://greenprogrammer.blogspot.com
> _______________________________________________
> 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/20060608/0d34f5c0/attachment.htm 

From jeff.barczewski at gmail.com  Thu Jun  8 16:31:07 2006
From: jeff.barczewski at gmail.com (Jeff Barczewski)
Date: Thu, 8 Jun 2006 15:31:07 -0500
Subject: [Masterview-users] Link_to_remote documentation
In-Reply-To: <3df642dd0606080948j113c442aq5e15a586d66173d1@mail.gmail.com>
References: <3df642dd0606080948j113c442aq5e15a586d66173d1@mail.gmail.com>
Message-ID: <19cda190606081331k4b775a74vf8c5f2cb526c7384@mail.gmail.com>

Thanks. I will double check the code and update the code or docs
accordingly.

On 6/8/06, Ed Howland <ed.howland at gmail.com> wrote:
>
> Hi,
>
> The documentation at masterview.org for the link_to_remote directive
> may be a bit off. In order to make it work I needed the example to be:
>
> <a mv:link_to_remote=":url => {:action => 'new'}">New product</a>
>
>           becomes
>
> %= link_to_remote 'New product',  :url => {:action => 'new'} %>
>
> Note, that I am using RJS templates, which do not use the :update tag
> in the link_to_remote. The proper Non-RJS example would probably look
> like:
>
> <a mv:link_to_remote=":update => 'mydiv', :url => {:action =>
> 'new'}">New product</a>
>
>
> Ed
> --
> Ed Howland
> http://greenprogrammer.blogspot.com
> _______________________________________________
> 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/20060608/3c25e4c4/attachment.htm 

From ed.howland at gmail.com  Thu Jun  8 17:19:24 2006
From: ed.howland at gmail.com (Ed Howland)
Date: Thu, 8 Jun 2006 16:19:24 -0500
Subject: [Masterview-users] Link_to(_remote) + image_tag
Message-ID: <3df642dd0606081419m2f29da1ai14f00dcbd4536556@mail.gmail.com>

Hi.

The recommended way to create a link_to or link_to_remote with an
image_tag (where the a tag surrounds the image tag,) is to add
image_tag() as the first parameter to either helper. The docs on
mv:link_to and link_to_remote say they will use  the contents of the
<a ..> tag for the name of the link. If this is an image, it becomes
tricky. The child element img's src attribute is going to be something
like "../../../public/images/file.jpg". The link_to directive will
just quote this and  output :
<%= link_to '<img src="../../../public/images/file.jpg", :action => ...

So at runtime in Rails, the link will be relative to the public folder
and miss it entirely. If you use my new image_tag directive it gets
even messier because it tries to embed erb inside of a string of erb
with unclosed quotes etc.

To solve this I created a pair of reciprocal directives: link_to_image
and image_tag_link. The first doesn't quote its content so the
image_tag('mypic.gif') will appear naturally inside the erb tags as a
parameter to the link_to helper. The second directive, image_tag_link,
sets its content to '' and then just outputs a normal image_tag with
the attribute value.

The downside of this is the tags have to be used in a pair like thus:

<a href="#" mv:link_to_image=":action => show"><img
src="../../../public/images/mylink.gif" mv:image_tag_link="mylink.gif"
/></a>

and can't be used outside this scenario. But then the original
directives will do for all other cases.

Finally, the directive mv:link_to_remote_image is the same as
link_to_image, except it generates a link_to_remote helper call, with
the caveat from my earlier post about needing the :url=> parameter.

Ed

-- 
Ed Howland
http://greenprogrammer.blogspot.com

From jeff.barczewski at gmail.com  Thu Jun  8 17:28:38 2006
From: jeff.barczewski at gmail.com (Jeff Barczewski)
Date: Thu, 8 Jun 2006 16:28:38 -0500
Subject: [Masterview-users] Link_to(_remote) + image_tag
In-Reply-To: <3df642dd0606081419m2f29da1ai14f00dcbd4536556@mail.gmail.com>
References: <3df642dd0606081419m2f29da1ai14f00dcbd4536556@mail.gmail.com>
Message-ID: <19cda190606081428h5df0eea2q47cc229a3e10631a@mail.gmail.com>

A couple things we are doing in the future that will help. First we will be
moving the default directory for templates down to the same subdirectory
level so that ../.. won't be off (so it would default to being in
app/masterview instead of app/views/masterview.

We can probably improve the image_tag and stylesheet_tag to figure out the
proper parameter automatically from the other src. That would probably make
the most sense, so you  pick it from your editor and the proper tag will be
generated to use your assets from the default location.

And just to add on to the subdirectory and location of templates,
additionally we are planning to make masterview have the option of
generating its erb direct to the rails cache so it won't need to have
intermediate erb (.rhtml) files at all and thus we can just put the
templates into the view tree with all the other files. (We chose to not put
them there initially because it would be confusing with both .rhtml and
.html files there).

On 6/8/06, Ed Howland <ed.howland at gmail.com> wrote:
>
> Hi.
>
> The recommended way to create a link_to or link_to_remote with an
> image_tag (where the a tag surrounds the image tag,) is to add
> image_tag() as the first parameter to either helper. The docs on
> mv:link_to and link_to_remote say they will use  the contents of the
> <a ..> tag for the name of the link. If this is an image, it becomes
> tricky. The child element img's src attribute is going to be something
> like "../../../public/images/file.jpg". The link_to directive will
> just quote this and  output :
> <%= link_to '<img src="../../../public/images/file.jpg", :action => ...
>
> So at runtime in Rails, the link will be relative to the public folder
> and miss it entirely. If you use my new image_tag directive it gets
> even messier because it tries to embed erb inside of a string of erb
> with unclosed quotes etc.
>
> To solve this I created a pair of reciprocal directives: link_to_image
> and image_tag_link. The first doesn't quote its content so the
> image_tag('mypic.gif') will appear naturally inside the erb tags as a
> parameter to the link_to helper. The second directive, image_tag_link,
> sets its content to '' and then just outputs a normal image_tag with
> the attribute value.
>
> The downside of this is the tags have to be used in a pair like thus:
>
> <a href="#" mv:link_to_image=":action => show"><img
> src="../../../public/images/mylink.gif" mv:image_tag_link="mylink.gif"
> /></a>
>
> and can't be used outside this scenario. But then the original
> directives will do for all other cases.
>
> Finally, the directive mv:link_to_remote_image is the same as
> link_to_image, except it generates a link_to_remote helper call, with
> the caveat from my earlier post about needing the :url=> parameter.
>
> Ed
>
> --
> Ed Howland
> http://greenprogrammer.blogspot.com
> _______________________________________________
> 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/20060608/3d65d4ef/attachment.htm 

From djlewis at acm.org  Fri Jun  9 15:20:14 2006
From: djlewis at acm.org (Deb Lewis)
Date: Fri, 9 Jun 2006 12:20:14 -0700
Subject: [Masterview-users] Logging from within a directive
In-Reply-To: <19cda190606081328p223be4c7g3296a7fac959f112@mail.gmail.com>
Message-ID: <20060609192023.NNED5347.fed1rmmtao05.cox.net@DLI92cx797990>

Ed Howland wrote:
 
>> I assume that the default logging level is Logger::DEBUG ... [based on]
masterview plugin's init.rb
 
The next release of MasterView will include a rework of the mechanisms for
customizing the MasterView configuration.  The new approach will be similar
to the style used for rails app configuration, where you customize the
settings for your app by providing initialization specs in your config
directory, setting values in the configuration and allowing for
environment-dependent settings which override/augment the general config for
your app.
 
There'll be documentation on all the supported configuration options and
description of how to use them, along with some sort of example/prototype
config file so it's easy to drop in and get going if you want something
different than the standard defaults,.
 
I'll make sure there are options supported to allow configuring the logging
facilities.  (that area isn't quite sorted out, working on that right now)
 
[p.s. introducing myself: I'm currently working with Jeff on some
enhancements to MasterView, having recently picked it up to use in a rails
development project I'm doing and deciding there were some things I wanted
added or done differently.  kudos to Jeff, he's done a really nice job
creating MasterView]
 
~ Deb

  _____  

From: masterview-users-bounces at rubyforge.org
[mailto:masterview-users-bounces at rubyforge.org] On Behalf Of Jeff Barczewski
Sent: Thursday, June 08, 2006 1:29 PM
To: masterview-users at rubyforge.org
Subject: Re: [Masterview-users] Logging from within a directive


The Logger is set on the MasterView module so you would probably need to
refer to it like

MasterView::Log.debug "foo" 

or even better use

MasterView::Log.debug { "foo" }

The second form is better since it is a block and the block won't get
executed if the output level is above debug which saves cpu if you were
doing any string building concatenating, etc. 
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/masterview-users/attachments/20060609/4d51c6eb/attachment-0001.htm 

From ed.howland at gmail.com  Fri Jun  9 16:32:53 2006
From: ed.howland at gmail.com (Ed Howland)
Date: Fri, 9 Jun 2006 15:32:53 -0500
Subject: [Masterview-users] Logging from within a directive
In-Reply-To: <20060609192023.NNED5347.fed1rmmtao05.cox.net@DLI92cx797990>
References: <19cda190606081328p223be4c7g3296a7fac959f112@mail.gmail.com>
	<20060609192023.NNED5347.fed1rmmtao05.cox.net@DLI92cx797990>
Message-ID: <3df642dd0606091332n7a3a4428yeb70c490a58f2de2@mail.gmail.com>

On 6/9/06, Deb Lewis <djlewis at acm.org> wrote:
>
>
> The next release of MasterView will include a rework of the mechanisms for
> customizing the MasterView configuration.  The new approach will be similar
> to the style used for rails app configuration, where you customize the
> settings for your app by providing initialization specs in your config
> directory, setting values in the configuration and allowing for
> environment-dependent settings which override/augment the general config for
> your app.
>
> There'll be documentation on all the supported configuration options and
> description of how to use them, along with some sort of example/prototype
> config file so it's easy to drop in and get going if you want something
> different than the standard defaults,.
>
> I'll make sure there are options supported to allow configuring the logging
> facilities.  (that area isn't quite sorted out, working on that right now)

Great news. Looking forward to it. Do you have a timescale?

>
> [p.s. introducing myself: I'm currently working with Jeff on some
> enhancements to MasterView, having recently picked it up to use in a rails
> development project I'm doing and deciding there were some things I wanted
> added or done differently.  kudos to Jeff, he's done a really nice job
> creating MasterView]
>
> ~ Deb

Introducing myself as well. I've just started using MV in a recent
newly minted, but ongoing project. I've only completed the outer layer
of the first seach page so far, Today I hope to get the new entry
forms converted. (At the very least, I can through out a lot of my
other
small templates which had to be edited by hand each time I got them
back from the designer.

I've know Jeff for a few months through the StL.rb (St. Louis Ruby
brigrade.) He also gave a talk on it there and mentioned it during his
RoR talk at the StLLUG meeting where I've attended since naught-0.

So far it has been working out OK. I am getting our designer on
Subversion this afternoon, so we can share the files that way. As we
talked about in a recent post, the relative path was the only
confusing part to him. He lives in Dreamweaver-land and all paths are
below the project directory. Too bad there aren't things like symlinks
in Windows.

****
BTW, so I am not too far ahead of the projected directive syntax, will
one version of 'image_tag' look like this:

<img src="../../../public/images/my.gif" mv:image_tag="my.gif">

Currently, to support image sizes and other attributes, I am forced to
do this for all my image tags:

<img src="../../../public/images/my.gif" height="17" width="16
mv:image_tag="'my.gif', :size => '17x16'">

So even <img src="../../../public/images/my.gif"
needs:
 mv:image_tag="'my.gif'">

That is because I need to pass the complete argument as a string to
the image tag inside the erb. The quoting and unquoting of strings
inside attribute values of mv: is a real pain. Clearly, I need more
help on writing directives.

?

Thanks
Ed


>
>  ________________________________
>  From: masterview-users-bounces at rubyforge.org
> [mailto:masterview-users-bounces at rubyforge.org] On Behalf
> Of Jeff Barczewski
> Sent: Thursday, June 08, 2006 1:29 PM
> To: masterview-users at rubyforge.org
> Subject: Re: [Masterview-users] Logging from within a directive
>
>
> The Logger is set on the MasterView module so you would probably need to
> refer to it like
>
> MasterView::Log.debug "foo"
>
> or even better use
>
> MasterView::Log.debug { "foo" }
>
> The second form is better since it is a block and the block won't get
> executed if the output level is above debug which saves cpu if you were
> doing any string building concatenating, etc.
>
> _______________________________________________
> Masterview-users mailing list
> Masterview-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/masterview-users
>
>


-- 
Ed Howland
http://greenprogrammer.blogspot.com

From jeff.barczewski at gmail.com  Fri Jun  9 18:46:13 2006
From: jeff.barczewski at gmail.com (Jeff Barczewski)
Date: Fri, 9 Jun 2006 17:46:13 -0500
Subject: [Masterview-users] Logging from within a directive
In-Reply-To: <3df642dd0606091332n7a3a4428yeb70c490a58f2de2@mail.gmail.com>
References: <19cda190606081328p223be4c7g3296a7fac959f112@mail.gmail.com>
	<20060609192023.NNED5347.fed1rmmtao05.cox.net@DLI92cx797990>
	<3df642dd0606091332n7a3a4428yeb70c490a58f2de2@mail.gmail.com>
Message-ID: <19cda190606091546vb24e3e0t5f7285e72474005a@mail.gmail.com>

We are working diligently to get this out as soon as possible. I would like
to have something out before the Rails conference if possible. So we will
probably just release whatever is ready and then continue on.

Some of the high priority goals are to shore up the config mechanisms and
layout of the files, clean up the docs, create some how to videos and
examples.

Beyond that we want to build out the main missing directives, provide direct
to Erb cache (eliminating intermediate rhtml file), add more advanced
directives, cleanup api for building directives (so easier to use and
understand) and provide good examples for how to build your own.

Lots of killer possibilities for powerful directives including ajax'd grids,
calendars, custom rendering, ...

But we are just taking it one day at a time, trying to prioritize what needs
to be done first so that we won't break things as we build, so if we have a
good extendable foundation we can keep adding with minimal impact to users
(or that is the goal).

Of course Deb and I have our own personal things that we need in there for
various projects, but we will also be looking at how the users are wanting
to use the system as we go forward, so we can continue to reprioritize
feature additions.

On 6/9/06, Ed Howland <ed.howland at gmail.com> wrote:
>
>
> Great news. Looking forward to it. Do you have a timescale?
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/masterview-users/attachments/20060609/32e2dd6c/attachment.htm 

From djlewis at acm.org  Fri Jun  9 20:47:51 2006
From: djlewis at acm.org (Deb Lewis)
Date: Fri, 9 Jun 2006 17:47:51 -0700
Subject: [Masterview-users] Logging from within a directive [img element
	markup]
In-Reply-To: <3df642dd0606091332n7a3a4428yeb70c490a58f2de2@mail.gmail.com>
Message-ID: <20060610004753.XMVW24290.fed1rmmtao09.cox.net@DLI92cx797990>

RE: mv:image_tag attribute notation and Ed's remarks:

>> Currently, to support image sizes and other attributes, I am forced 
>> to do this for all my image tags:
>> <img src="../../../public/images/my.gif" height="17" width="16 
>>      mv:image_tag="'my.gif', :size => '17x16'">

Ed - we'll probably have to think about that a bit before responding
further.

In the meantime, you might consider some alternative techniques approaches
using css style rules with your <img> elements.

Option 1: if you have a small set of specific images that you use in a
number of places, consider defining a class in your css stylesheet for these
so you don't have to hard-code the size attributes in the <img> markup.

    <img src="../../../public/images/my.gif" height="17" width="16 
         mv:image_tag="'my.gif', :size => '17x16'" />

could be replaced with style rule and simplified markup:

    img.my-gif {  width: 16px;  height: 17px; }
    <img src="../../../public/images/my.gif" class="my-gif"
         mv:image_tag="'my.gif', :class => 'my-gif'" />

(don't like the need to duplicate the style rule class, but IMO that's still
a better than bolting down image file size attributes directly in content
pages)

Option 2: if you have a number of standard-sized images that you use
frequently, do a variation of the preceding with a style rule, say, some
name by 'visual-cue-img', whatever makes sense.

And a possible option 3: create a custom masterview directive to encapsulate
a standard pattern than you want to use across a number of pages in our
site.  

(I actually have a situation that #3 solves nicely in I'm doing right now,
so after working out details will probably contribute it to the next
MasterView release as an example of how to do a custom masterview directive)

>>> So even <img src="../../../public/images/my.gif" needs:
>>  mv:image_tag="'my.gif'"

Jeff - this might be interesting, let's take a look at this case when we
have a chance.  It's quite similar to the target substitution magic we're
working on right now for mv:generate.  The template being processed already
provides some info about what the directive should produce and it would be
nice if the author didn't have to repeat the image asset's name.  e.g. some
sort of mv:image="{this_src}" notation, if we can specify a sensible rule
about how to determine the relevant portion of the <img> tag's existing src
attribute to use in the generated output.

(?? mv:image_tag="{src_filename}" notation could work for images directly
contained in the std rails public/images dir; not sure how far to push on
trying to automagically determine a relative path name w/in the images dir,
there are issues of nesting in the template src dir that make ugly .. paths
like the above tricky)

~ Deb



From jeff.barczewski at gmail.com  Fri Jun  9 22:55:02 2006
From: jeff.barczewski at gmail.com (Jeff Barczewski)
Date: Fri, 9 Jun 2006 21:55:02 -0500
Subject: [Masterview-users] Logging from within a directive [img element
	markup]
In-Reply-To: <20060610004753.XMVW24290.fed1rmmtao09.cox.net@DLI92cx797990>
References: <3df642dd0606091332n7a3a4428yeb70c490a58f2de2@mail.gmail.com>
	<20060610004753.XMVW24290.fed1rmmtao09.cox.net@DLI92cx797990>
Message-ID: <19cda190606091955ge3055c0hd8c9a46b643b58a4@mail.gmail.com>

Yeah, I think we can easily make a tag that will intuit the path from the
src, and of course it can pick up the height and width from the settings.
Many times the wysiwyg editor will set those for you automatically, so if we
just pick those up then that would be a big help.

We could take it a step further and determine the image size ourself, cache
it, and if not specified auto use the image size.

Will start simple and then play around to see what we can do.

On 6/9/06, Deb Lewis <djlewis at acm.org> wrote:
>
> RE: mv:image_tag attribute notation and Ed's remarks:
>
> >> Currently, to support image sizes and other attributes, I am forced
> >> to do this for all my image tags:
> >> <img src="../../../public/images/my.gif" height="17" width="16
> >>      mv:image_tag="'my.gif', :size => '17x16'">
>
> Ed - we'll probably have to think about that a bit before responding
> further.
>
> In the meantime, you might consider some alternative techniques approaches
> using css style rules with your <img> elements.
>
> Option 1: if you have a small set of specific images that you use in a
> number of places, consider defining a class in your css stylesheet for
> these
> so you don't have to hard-code the size attributes in the <img> markup.
>
>     <img src="../../../public/images/my.gif" height="17" width="16
>          mv:image_tag="'my.gif', :size => '17x16'" />
>
> could be replaced with style rule and simplified markup:
>
>     img.my-gif {  width: 16px;  height: 17px; }
>     <img src="../../../public/images/my.gif" class="my-gif"
>          mv:image_tag="'my.gif', :class => 'my-gif'" />
>
> (don't like the need to duplicate the style rule class, but IMO that's
> still
> a better than bolting down image file size attributes directly in content
> pages)
>
> Option 2: if you have a number of standard-sized images that you use
> frequently, do a variation of the preceding with a style rule, say, some
> name by 'visual-cue-img', whatever makes sense.
>
> And a possible option 3: create a custom masterview directive to
> encapsulate
> a standard pattern than you want to use across a number of pages in our
> site.
>
> (I actually have a situation that #3 solves nicely in I'm doing right now,
> so after working out details will probably contribute it to the next
> MasterView release as an example of how to do a custom masterview
> directive)
>
> >>> So even <img src="../../../public/images/my.gif" needs:
> >>  mv:image_tag="'my.gif'"
>
> Jeff - this might be interesting, let's take a look at this case when we
> have a chance.  It's quite similar to the target substitution magic we're
> working on right now for mv:generate.  The template being processed
> already
> provides some info about what the directive should produce and it would be
> nice if the author didn't have to repeat the image asset's name.  e.g.
> some
> sort of mv:image="{this_src}" notation, if we can specify a sensible rule
> about how to determine the relevant portion of the <img> tag's existing
> src
> attribute to use in the generated output.
>
> (?? mv:image_tag="{src_filename}" notation could work for images directly
> contained in the std rails public/images dir; not sure how far to push on
> trying to automagically determine a relative path name w/in the images
> dir,
> there are issues of nesting in the template src dir that make ugly ..
> paths
> like the above tricky)
>
> ~ Deb
>
>
> _______________________________________________
> 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/20060609/c3c3d38e/attachment.htm 

From djlewis at acm.org  Mon Jun 12 17:05:40 2006
From: djlewis at acm.org (Deb Lewis)
Date: Mon, 12 Jun 2006 14:05:40 -0700
Subject: [Masterview-users] Logging from within a directive [img element
	markup]
Message-ID: <20060612210539.PJOC8684.fed1rmmtao12.cox.net@DLI92cx797990>

Ed - you've raised some good issues and ideas about where improvements in
this whole area of specifying images.  

Some of this is very similar to the work we're just now doing in the
mv:generate mechanism, so that when you write a masterview template you
don't have to needlessly repeat information to get the desired output file
name when there's a reasonable mapping from the source template's own name.
As soon as we get the template generation name handling stuff settled, we
can go back and look at providing equivalent simplification for asset
references like images.

One approach, per your description in your last message about what you've
prototyped, is to be more clever in the mv:image_tag to make it smart enough
to carry along attributes already specified in the template (class, style,
width/height...).  Seems like a good idea; we'd need to make sure we think
through whether there's any attributes that should *not* be picked up from
the template's <img> attributes or, say, if some exclude clause is needed.

There's also another approach I thought of over the weekend that might help
simplify working with images.  Recall your original case:

>     <img src="../../../public/images/my.gif" height="17" width="16"
>          mv:image_tag="'my.gif', :size => '17x16'" />

Instead of trying to use the full mv:image_tag, which was forcing you to
repeat both the image file ref and other attributes (in this case size info)
that are needed by the underlying rails image_tag helper, we might just want
a new directive mv:image_path (?mv:image_src?) which would operate like a
variation of the general mv:attr directive that allows you to replace
specified attribute values.  Would look something like:

     <img src="../../../public/images/my.gif" height="17" width="16"
          mv:image_path="my.gif" />

where the semantics are "replace the value of the src attribute with the
path to the image asset" and the directive implementation would run the
mv:image_path's attribute value through the standard rails image_path helper
function.

And then better yet would be a notation for the attribute value that in some
fashion says "use the image name from what I already said in the src
attribute", assuming we have some reliable way to infer subdir paths
properly:

     <img src="../../../public/images/my.gif" height="17" width="16'
          mv:image_path="{image_ref}" />

~ Deb

-----Original Message-----
From: Ed Howland [mailto:ed.howland at gmail.com]
Sent: Monday, June 12, 2006 10:22 AM
To: djlewis at acm.org
Subject: Re: [Masterview-users] Logging from within a directive [img element
markup]

On 6/12/06, Ed Howland <ed.howland at gmail.com> wrote:
> So, in the end I modified image_tag and image_tag_link to parse out 
> the values from attr_lckv hash and just reformat those into an 
> image_tag helper call. Now it works great with explicit sizes and/or 
> class.
>
> Not magic en
oops, hit the send button..

It is not magic enough to interpret the path relative to public/images. So
if you have a subfolder to that, I can't do it yet.
But the possibility is there, since I am using Pathname which allows for
some manipulation. Actually, I can just pass the subfolder as the argument
to mv:image_tag and prepend it to the image_tag if it exists and is non zero
length.

Ed

--
Ed Howland
http://greenprogrammer.blogspot.com



From djlewis at acm.org  Mon Jun 12 17:18:23 2006
From: djlewis at acm.org (Deb Lewis)
Date: Mon, 12 Jun 2006 14:18:23 -0700
Subject: [Masterview-users] Logging from within a directive
In-Reply-To: <3df642dd0606080941n316acca0l196c933e2aae725f@mail.gmail.com>
Message-ID: <20060612211822.LLEH6235.fed1rmmtao06.cox.net@DLI92cx797990>

Ed - the next release of MasterView will support configuration settings for
both the flavor of logger used (Log4r, the default if available, or Logger
from the standard Ruby library), along with a log_level setting.

The current default log level is DEBUG from Logger, ALL from Log4r.  (their
logging level naming conventions are somewhat different, but both support
DEBUG, INFO, WARN, ERROR as standard levels)  

We might want to modify the logger's built-in defaults that we currently
pick up so that the MasterView log is a bit smarter about choosing its
defaults, e.g., maybe DEBUG or ALL/ANY if development mode, WARN in
production.

~ Deb 

-----Original Message-----
From: masterview-users-bounces at rubyforge.org
[mailto:masterview-users-bounces at rubyforge.org] On Behalf Of Ed Howland
Sent: Thursday, June 08, 2006 9:42 AM
To: masterview-users at rubyforge.org
Subject: [Masterview-users] Logging from within a directive

Hi,

I assume that the default logging level is Logger::DEBUG since by setting
that in init.rb, I get lots of log messages in the WEBrick console window,
like when the log level is not set. But if I put

Log.debug "content_str #{content_str}"

in my etag method of my directive, I don't see any output in that same
window (or in log/development.log)

Any ideas?

TIA,
Ed



--
Ed Howland
http://greenprogrammer.blogspot.com
_______________________________________________
Masterview-users mailing list
Masterview-users at rubyforge.org
http://rubyforge.org/mailman/listinfo/masterview-users



From ed.howland at gmail.com  Mon Jun 12 18:01:55 2006
From: ed.howland at gmail.com (Ed Howland)
Date: Mon, 12 Jun 2006 17:01:55 -0500
Subject: [Masterview-users] Logging from within a directive [img element
	markup]
In-Reply-To: <20060612210539.PJOC8684.fed1rmmtao12.cox.net@DLI92cx797990>
References: <20060612210539.PJOC8684.fed1rmmtao12.cox.net@DLI92cx797990>
Message-ID: <3df642dd0606121501n1db68840q5c304a14c130f18a@mail.gmail.com>

On 6/12/06, Deb Lewis <djlewis at acm.org> wrote:
>
> Instead of trying to use the full mv:image_tag, which was forcing you to
> repeat both the image file ref and other attributes (in this case size info)
> that are needed by the underlying rails image_tag helper, we might just want
> a new directive mv:image_path (?mv:image_src?) which would operate like a
> variation of the general mv:attr directive that allows you to replace
> specified attribute values.  Would look something like:
>
>      <img src="../../../public/images/my.gif" height="17" width="16"
>           mv:image_path="my.gif" />
>
> where the semantics are "replace the value of the src attribute with the
> path to the image asset" and the directive implementation would run the
> mv:image_path's attribute value through the standard rails image_path helper
> function.
>
> And then better yet would be a notation for the attribute value that in some
> fashion says "use the image name from what I already said in the src
> attribute", assuming we have some reliable way to infer subdir paths
> properly:
>
>      <img src="../../../public/images/my.gif" height="17" width="16'
>           mv:image_path="{image_ref}" />
>
> ~ Deb

Well, ok. So in these cases, do you infer somehow that the resulting
tag is <%= image_tag("my.gif", :size => "17x16") just based on the
appearance of he mv:image_path attribute?

Ed

-- 
Ed Howland
http://greenprogrammer.blogspot.com

From ed.howland at gmail.com  Tue Jun 20 11:20:12 2006
From: ed.howland at gmail.com (Ed Howland)
Date: Tue, 20 Jun 2006 10:20:12 -0500
Subject: [Masterview-users] Gem mirror for Masterview
Message-ID: <3df642dd0606200820r28d3d2e9ue354d89ac0218dbe@mail.gmail.com>

Hi,

Is there a mirror for masterview_gem_pack? Rubyforge's gem server is
down for maint.

Is there a list of mirrors somewhere? Google was not much help.

How do gems get pushed out to mirrors? I tried for MV at
gems.rubyonrails.org, but nothing there.

Thanks

Ed

-- 
Ed Howland
http://greenprogrammer.blogspot.com

From jeff.barczewski at gmail.com  Tue Jun 20 23:03:45 2006
From: jeff.barczewski at gmail.com (Jeff Barczewski)
Date: Tue, 20 Jun 2006 22:03:45 -0500
Subject: [Masterview-users] Gem mirror for Masterview
In-Reply-To: <3df642dd0606200820r28d3d2e9ue354d89ac0218dbe@mail.gmail.com>
References: <3df642dd0606200820r28d3d2e9ue354d89ac0218dbe@mail.gmail.com>
Message-ID: <19cda190606202003p2c5bbe3hb2930ab1b38247b4@mail.gmail.com>

Yeah, unfortunately it was down. We'll keep a copy on masterview.org in the
future. Rubyforge has been pretty dependable until today, but it is up now.
Unfortunately we also didn't get this email delivered until now too since it
was down.

On 6/20/06, Ed Howland <ed.howland at gmail.com> wrote:
>
> Hi,
>
> Is there a mirror for masterview_gem_pack? Rubyforge's gem server is
> down for maint.
>
> Is there a list of mirrors somewhere? Google was not much help.
>
> How do gems get pushed out to mirrors? I tried for MV at
> gems.rubyonrails.org, but nothing there.
>
> Thanks
>
> Ed
>
> --
> Ed Howland
> http://greenprogrammer.blogspot.com
> _______________________________________________
> 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/20060620/66d4d737/attachment.html 

From djlewis at acm.org  Wed Jun 21 01:35:31 2006
From: djlewis at acm.org (Deb Lewis)
Date: Tue, 20 Jun 2006 22:35:31 -0700
Subject: [Masterview-users] Gem mirror for Masterview
In-Reply-To: <3df642dd0606200820r28d3d2e9ue354d89ac0218dbe@mail.gmail.com>
Message-ID: <20060621053535.JIZT19057.fed1rmmtao12.cox.net@DLI92cx797990>

try again now, rubyforge seems to (finally!) be back up tonight.  But good
observation about having some mirrors, we'll follow up and see about getting
alt. source available so we're not bottle-necked on rubyforge.

The new 0.2.0 release with a lot of improvements is coming out momentarily,
Jeff and I spent the day trying to pin down loose ends so we can post the
new build.  Along with some significant feature work, this release comes
with doc improvements and intro video by Jeff - we're trying to make it
easier for new users to check out MasterView and get started.

~ Deb 

-----Original Message-----
From: masterview-users-bounces at rubyforge.org
[mailto:masterview-users-bounces at rubyforge.org] On Behalf Of Ed Howland
Sent: Tuesday, June 20, 2006 8:20 AM
To: masterview-users at rubyforge.org
Subject: [Masterview-users] Gem mirror for Masterview

Hi,

Is there a mirror for masterview_gem_pack? Rubyforge's gem server is down
for maint.

Is there a list of mirrors somewhere? Google was not much help.

How do gems get pushed out to mirrors? I tried for MV at
gems.rubyonrails.org, but nothing there.

Thanks

Ed

--
Ed Howland
http://greenprogrammer.blogspot.com
_______________________________________________
Masterview-users mailing list
Masterview-users at rubyforge.org
http://rubyforge.org/mailman/listinfo/masterview-users



From ed.howland at gmail.com  Wed Jun 21 10:37:03 2006
From: ed.howland at gmail.com (Ed Howland)
Date: Wed, 21 Jun 2006 09:37:03 -0500
Subject: [Masterview-users] Gem mirror for Masterview
In-Reply-To: <20060621053535.JIZT19057.fed1rmmtao12.cox.net@DLI92cx797990>
References: <3df642dd0606200820r28d3d2e9ue354d89ac0218dbe@mail.gmail.com>
	<20060621053535.JIZT19057.fed1rmmtao12.cox.net@DLI92cx797990>
Message-ID: <3df642dd0606210737s70d07a74wa5b8b77118b4bbb8@mail.gmail.com>

On 6/21/06, Deb Lewis <djlewis at acm.org> wrote:
> try again now, rubyforge seems to (finally!) be back up tonight.  But good
> observation about having some mirrors, we'll follow up and see about getting
> alt. source available so we're not bottle-necked on rubyforge.
>
> The new 0.2.0 release with a lot of improvements is coming out momentarily,
> Jeff and I spent the day trying to pin down loose ends so we can post the
> new build.  Along with some significant feature work, this release comes
> with doc improvements and intro video by Jeff - we're trying to make it
> easier for new users to check out MasterView and get started.
>

That's great. The RubyForge server was announced to be upgraded on
ruby-talk, I just missed that. Tom Copland was nice enough to respond
in the middle of his upgrade to point me to a mirror. I couldn't get
the gem --source directive to work, but I could d/l manually.

If nothing else, I learned how to install gems different ways.

Still getting this message on 4 separate Win boxen:

gem install masterview-0.1.5.gem --local
....
lib/masterview/parser.rb:278:80: Skipping require of dynamic string:
"#{directive_path}#{fn}"

Ed

-- 
Ed Howland
http://greenprogrammer.blogspot.com

From jeff.barczewski at gmail.com  Wed Jun 21 11:43:57 2006
From: jeff.barczewski at gmail.com (Jeff Barczewski)
Date: Wed, 21 Jun 2006 10:43:57 -0500
Subject: [Masterview-users] Gem mirror for Masterview
In-Reply-To: <3df642dd0606210737s70d07a74wa5b8b77118b4bbb8@mail.gmail.com>
References: <3df642dd0606200820r28d3d2e9ue354d89ac0218dbe@mail.gmail.com>
	<20060621053535.JIZT19057.fed1rmmtao12.cox.net@DLI92cx797990>
	<3df642dd0606210737s70d07a74wa5b8b77118b4bbb8@mail.gmail.com>
Message-ID: <19cda190606210843j5d1551acvf0869fc623a9b2fd@mail.gmail.com>

Yes that happens in the rdoc creation. It is a warning that it isn't
following the dynamic requires, which is fine, but I don't know how to get
rid of the message yet.

If anyone knows how to do it then we can fix it so that it doesn't do that.

On 6/21/06, Ed Howland <ed.howland at gmail.com> wrote:
>
> On 6/21/06, Deb Lewis <djlewis at acm.org> wrote:
> > try again now, rubyforge seems to (finally!) be back up tonight.  But
> good
> > observation about having some mirrors, we'll follow up and see about
> getting
> > alt. source available so we're not bottle-necked on rubyforge.
> >
> > The new 0.2.0 release with a lot of improvements is coming out
> momentarily,
> > Jeff and I spent the day trying to pin down loose ends so we can post
> the
> > new build.  Along with some significant feature work, this release comes
> > with doc improvements and intro video by Jeff - we're trying to make it
> > easier for new users to check out MasterView and get started.
> >
>
> That's great. The RubyForge server was announced to be upgraded on
> ruby-talk, I just missed that. Tom Copland was nice enough to respond
> in the middle of his upgrade to point me to a mirror. I couldn't get
> the gem --source directive to work, but I could d/l manually.
>
> If nothing else, I learned how to install gems different ways.
>
> Still getting this message on 4 separate Win boxen:
>
> gem install masterview-0.1.5.gem --local
> ....
> lib/masterview/parser.rb:278:80: Skipping require of dynamic string:
> "#{directive_path}#{fn}"
>
> Ed
>
> --
> Ed Howland
> http://greenprogrammer.blogspot.com
> _______________________________________________
> 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/20060621/ee9cf1ea/attachment.html 

From jeff.barczewski at gmail.com  Wed Jun 21 16:38:34 2006
From: jeff.barczewski at gmail.com (Jeff Barczewski)
Date: Wed, 21 Jun 2006 15:38:34 -0500
Subject: [Masterview-users] [ANN] MasterView rails-optimized (x)html
	friendly template engine plugin - Release 0.2.0
In-Reply-To: <19cda190606211308k27ea6b6ah2d0f3a709261e242@mail.gmail.com>
References: <19cda190606211308k27ea6b6ah2d0f3a709261e242@mail.gmail.com>
Message-ID: <19cda190606211338l36599610q7ec3bce0c5af723d@mail.gmail.com>

MasterView rails-optimized (x)HTML friendly template engine plugin - Release
0.2.0

The MasterView development team is pleased to announce the general
availability of MasterView release 0.2.0. MasterView is a rails-optimized
(x)html friendly template engine plugin that provides another option to the
existing rails view templates (rhtml and rxml). The main idea is to provide
a template engine that would provide all the power of layouts, partials, and
rails helpers but still be editable/styleable in a WYSIWYG editor. It was
also a major goal that the syntax of these attribute directives be very
similar to rails helpers so that one could intuitively start using
MasterView with little learning curve other than knowing rails. MasterView
was inspired by Amrita, Kwartz, Tapestry, Zope/PHP TAL, Liquid, and Web
Objects but designed with a fresh approach and specifically targetted for
rails users.

Allow your web designers to work on the design while the developers focus on
coding. To get you up and running quickly the MasterView generator creates
usable styleable templates (along with controller and models) that can be
easily customized to your needs. Or start straight from your html prototype
and add MasterView attribute directives directly to those files. You can
re-edit those same template files at any time in your development life cycle
to update html layout and style.

This project was launched in January of 2006. Building on the suggestions of
early users, the MasterView project has been enhanced for better team usage
and for easier configuration/upgrading.  The original release generated a
single master file for all actions, but this has been changed to generate
separate files for each action and each template simply imports the other
supporting layouts and partials needed to provide full WYSIWYG design
capabilities in each file. A synchronizing (rebuilding) mechanism has been
created to automatically be able to sync up the imports so that designers
are always working with a consistent view. The single file generation
mechanism is still available as an option.

MasterView directives were designed to be user extended so that additional
directives could be loaded and shared amongst the community, providing
infinitely extendable options. Custom directives could be designed to wrap
complex layout and view code into a very simple declaration in your view.
For instance directives could be created that ajaxify tables so that they
support sorting, ajax updates, and gracefully degradation without
javascript. Directives might simply be used internally to simplify
repetitive view code.

Video
A quick start video which demos the basic operation is available at
http://masterview.org/videos/masterview_quick_start.html

MasterView is released under MIT open source licensing.

Main site: http://masterview.org/
Rubyforge Project site: http://rubyforge.org/projects/masterview


Goals

   - Create/extend a template engine for rails that would be XHTML
   friendly and thus could be edited/styled with a WYSIWYG HTML editor even
   late in development without breaking template.
   - Keep it simple. DRY. No extra config files, simple syntax with ruby
   flavor.
   - Design it specifically for ruby and rails. Use the full power and
   not be limited in its capabilities over what can be done with ERb (rhtml)
   - Work nicely with layouts, partials, and rails html helpers.
   - Reduce complexity, work with existing rails code, no extra view
   logic or hashes than what is used by ERb (rhtml). Scaffold generate initial
   templates or work from existing html prototype. Make scaffolds nicely styled
   and easily useable for production with minor changes.
   - Reduce the numbers of files, simplifying editing. Define partials
   and layouts naturallyl right in the template, no need to go to another file.

   - Preview in browser without running an app. Allow for dummy data in
   the template so that the page can be viewed and styled independently of the
   application.
   - Performance equal to ERb (rhtml)

Release Notes

   - Ability to easily utilize multiple template files for a controller
   making it easier to work together as a team on files and to keep file sizes
   manageable.
   - Added capability for eliminating rhthml generation, extends rails so
   that rhtml can be pulled directly from MasterView (rhtml file generation now
   optional)
   - Rails like configuration system which provides a clean way to
   configure options
   - MasterView admin pages for working with templates and viewing
   generated rhtml
   - Rake utilities to provide command line capabilities equal to those
   in MasterView admin pages.
   - Configuration and documentation cleanup.
   - Keyword expansions for generate and import directives.
   - Support for configuring MasterView logger and log_level

Installation - several options (gem install or plugin install)

   - As a gem - gem install masterview_gem_pack; cd railsapp;
   script/generate masterview_plugin
   - As a pure plugin using plugin install - script/plugin install
   svn://rubyforge.org/var/svn/masterview/tags/masterview
   - As a pure plugin download from rubyforge - download
   masterview-x.x.x.tgz or .zip and extract to
   railsapp/vendor/plugins/masterview

Visit the online documentation page at http://masterview.org/ for complete
installation and usage information.

We would love to hear your feedback and ideas around this project! Visit the
rubyforge project <http://rubyforge.org/projects/masterview> to join the
users mailing list or to add yourself to the announce list to receive future
announcements. Check out the
video<http://masterview.org/videos/masterview_quick_start.html>to see
MasterView in action!

Thanks for your time!!


MasterView Development Team
Jeff Barczewski and Deb Lewis
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/masterview-users/attachments/20060621/6f271f3c/attachment-0001.html 

From JBarczewski at rgatp.com  Mon Jun 26 12:34:35 2006
From: JBarczewski at rgatp.com (Barczewski, Jeff)
Date: Mon, 26 Jun 2006 11:34:35 -0500
Subject: [Masterview-users] Test to see if this is working since rubyforge
	move
Message-ID: <F523DFE088BE1D46AADC477449737F060108697B@stlpexc240.rgare.net>


From jeff.barczewski at gmail.com  Mon Jun 26 18:32:19 2006
From: jeff.barczewski at gmail.com (Jeff Barczewski)
Date: Mon, 26 Jun 2006 17:32:19 -0500
Subject: [Masterview-users] test to masterview-users
Message-ID: <19cda190606261532w7c4da0acs2898fe11317f2c51@mail.gmail.com>

test
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/masterview-users/attachments/20060626/dd6a02e9/attachment.html 

From ed.howland at gmail.com  Mon Jun 26 19:01:03 2006
From: ed.howland at gmail.com (Ed Howland)
Date: Mon, 26 Jun 2006 18:01:03 -0500
Subject: [Masterview-users] Test to see if this is working since
	rubyforge move
In-Reply-To: <F523DFE088BE1D46AADC477449737F060108697B@stlpexc240.rgare.net>
References: <F523DFE088BE1D46AADC477449737F060108697B@stlpexc240.rgare.net>
Message-ID: <3df642dd0606261601w3b0c4bdai304bad66eca74fa6@mail.gmail.com>

Apparently, yes.

On 6/26/06, Barczewski, Jeff <JBarczewski at rgatp.com> wrote:
>
> _______________________________________________
> Masterview-users mailing list
> Masterview-users at rubyforge.org
> http://rubyforge.org/mailman/listinfo/masterview-users
>


-- 
Ed Howland
http://greenprogrammer.blogspot.com

From jeff.barczewski at gmail.com  Wed Jun 28 10:49:30 2006
From: jeff.barczewski at gmail.com (Jeff Barczewski)
Date: Wed, 28 Jun 2006 09:49:30 -0500
Subject: [Masterview-users] Would like some feedback on new illustration and
	video for MasterView, look ok on macs, makes sense?
Message-ID: <19cda190606280749y4c80b2ccp383f1f9104ac5242@mail.gmail.com>

Hey fellow rubians,

I am just getting ready to do another mini release 0.2.1 which adds support
for Mongrel, adds image_tag and a few other things, but before I do I want
to get some feedback on a new illustration and shorter video.

Also we wanted to add in an illustration that helps explain how things work,
so I added that in as well. Would like to know if it makes sense to people
and also if it displays ok. I had a bit of a challenge with it looking good
on linux, windows firefox, windows IE. Also I don't have a mac so I would
like to know if this page and the others on the site are ok. Here is the
illustration link http://masterview.org/simple_diagram.html

We also had feedback that original flash video was way too long, so I
created a shorter one that runs in about 5 minutes. Let me know what you
think.
http://masterview.org/videos/demo_short.html

The main site link is
http://masterview.org/<http://masterview.org/videos/demo_short.html>

Thanks for any feedback. Just wanting to have some additional eyes before I
put it out to the world.

Blessings,

Jeff
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/masterview-users/attachments/20060628/25b5f929/attachment.html 

From jeff.barczewski at gmail.com  Wed Jun 28 14:28:17 2006
From: jeff.barczewski at gmail.com (Jeff Barczewski)
Date: Wed, 28 Jun 2006 13:28:17 -0500
Subject: [Masterview-users] [ANN] MasterView Release 0.2.1
Message-ID: <19cda190606281128k23e56b6yb45aa64662ae506b@mail.gmail.com>

Release 0.2.1 adds Mongrel support, a new image_tag directive and some
additional illustrations and links to videos. Also javascript_include
and stylesheet_link directives can infer the path from the src
attribute if the attr_value is empty. More information is available in
the directive documentation.

Also added additional logging around startup and the version of
MasterView that is running and a new admin page to visually see what
MasterView features are currently loaded (tidy,auto parsing on change,
parse on startup, reading rhtml direct from masterview (eliminating
rhtml file generation))

Release 0.2.1 is available via gem, rubyforge download, or svn
If using SVN then the recommended tag to pull is
svn://rubyforge.org/var/svn/masterview/tags/masterview which will
always point to the latest release.

Release 0.2.0 was a big release with much new functionality and
refactoring. As a result of the cleanup, configuration changed,
default template src path was changed from app/masterview to app/views
and one directive was renamed for clarity. Details below.

This release also received a major upgrade in the consolidation of IO
which allows for much flexibility in where and how templates and files
are read and written. Because of this upgrade it was easy for us to
extend Rails to load the rhtml (erb) directly from MasterView without
serializing to the file system (although can be configured optionally
to do so).


UPGRADE NOTES: If you have customized your MasterView configuration
in the init.rb file of your existing plugin installation, you *MUST*
migrate your configuration to the new settings file configuration mechanism
(config/masterview/settings.rb and environment settings files).

Also note that a directive was renamed from gen_render to gen_partial to
more clearly represent the functionality and eliminate future confusion.
Be sure to change any references to gen_render to gen_partial.

The default location for MasterView templates is now the standard Rails
app/views directory rather than app/masterview.  Either move your
existing templates into app/views or update the MasterView
config.template_src_dir_path setting in your
config/masterview/settings.rb to reference your existing templates
source directory.

If you have any questions or problems with the new release, let us know.

Thanks,

Jeff

From ed.howland at gmail.com  Fri Jun 30 11:51:17 2006
From: ed.howland at gmail.com (Ed Howland)
Date: Fri, 30 Jun 2006 10:51:17 -0500
Subject: [Masterview-users] [ANN] MasterView Release 0.2.1
In-Reply-To: <19cda190606281128k23e56b6yb45aa64662ae506b@mail.gmail.com>
References: <19cda190606281128k23e56b6yb45aa64662ae506b@mail.gmail.com>
Message-ID: <3df642dd0606300851t57359103rd4e352f7326cc7f0@mail.gmail.com>

On 6/28/06, Jeff Barczewski <jeff.barczewski at gmail.com> wrote:
> The default location for MasterView templates is now the standard Rails
> app/views directory rather than app/masterview.  Either move your
> existing templates into app/views or update the MasterView
> config.template_src_dir_path setting in your
> config/masterview/settings.rb to reference your existing templates
> source directory.
>
> If you have any questions or problems with the new release, let us know.
>
> Thanks,
>
> Jeff

Jeff, I don't think the web page reflects this:

http://www.masterview.org/guide.html

It still says app/views/masterview is the location for MV templates.

Ed

-- 
Ed Howland
http://greenprogrammer.blogspot.com

From jeff.barczewski at gmail.com  Fri Jun 30 12:37:19 2006
From: jeff.barczewski at gmail.com (Jeff Barczewski)
Date: Fri, 30 Jun 2006 11:37:19 -0500
Subject: [Masterview-users] MasterView release 0.2.2 - maintenance release,
	fixes rhtml error, documentation updated
Message-ID: <19cda190606300937y75b3d4dcqa7b0c85a38c73d43@mail.gmail.com>

MasterView 0.2.2 - maintenance release

Fixes problem when rails encounters exception in either compiling or
involving RuntimeError in the generated rhtml. The rails TemplateError
class looks at the file system for the template contents. So when
generate_rhtml is false (no file is generated) rails was not able to
find source and was not outputting an error page. Rails TemplateError
class was extended to look at MasterView store first and then fallback
to file system.

Documentation was updated with some more details around
generator and including screenshots and an illustration.

Jeff
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/masterview-users/attachments/20060630/7398d765/attachment.html 

From jeff.barczewski at gmail.com  Fri Jun 30 12:38:17 2006
From: jeff.barczewski at gmail.com (Jeff Barczewski)
Date: Fri, 30 Jun 2006 11:38:17 -0500
Subject: [Masterview-users] [ANN] MasterView Release 0.2.1
In-Reply-To: <3df642dd0606300851t57359103rd4e352f7326cc7f0@mail.gmail.com>
References: <19cda190606281128k23e56b6yb45aa64662ae506b@mail.gmail.com>
	<3df642dd0606300851t57359103rd4e352f7326cc7f0@mail.gmail.com>
Message-ID: <19cda190606300938m5c719557j20a4619da4b54cd9@mail.gmail.com>

Thanks. We will get it updated.

On 6/30/06, Ed Howland <ed.howland at gmail.com> wrote:
>
> On 6/28/06, Jeff Barczewski <jeff.barczewski at gmail.com> wrote:
> > The default location for MasterView templates is now the standard Rails
> > app/views directory rather than app/masterview.  Either move your
> > existing templates into app/views or update the MasterView
> > config.template_src_dir_path setting in your
> > config/masterview/settings.rb to reference your existing templates
> > source directory.
> >
> > If you have any questions or problems with the new release, let us know.
> >
> > Thanks,
> >
> > Jeff
>
> Jeff, I don't think the web page reflects this:
>
> http://www.masterview.org/guide.html
>
> It still says app/views/masterview is the location for MV templates.
>
> Ed
>
> --
> Ed Howland
> http://greenprogrammer.blogspot.com
> _______________________________________________
> 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/20060630/43eecddd/attachment.html 

From ed.howland at gmail.com  Fri Jun 30 15:33:46 2006
From: ed.howland at gmail.com (Ed Howland)
Date: Fri, 30 Jun 2006 14:33:46 -0500
Subject: [Masterview-users] MasterView release 0.2.2 - maintenance
	release, fixes rhtml error, documentation updated
In-Reply-To: <19cda190606300937y75b3d4dcqa7b0c85a38c73d43@mail.gmail.com>
References: <19cda190606300937y75b3d4dcqa7b0c85a38c73d43@mail.gmail.com>
Message-ID: <3df642dd0606301233l4c425fb0k7ed8145e7e4c34a0@mail.gmail.com>

On 6/30/06, Jeff Barczewski <jeff.barczewski at gmail.com> wrote:
>
> Documentation was updated with some more details around
> generator and including screenshots and an illustration.
>
> Jeff
>

One small almost insignificant note. The short video shows the admin
pages and the fact that you can click on a link to view the source of
the generated rhtml. But you have to enable both those options in
config/masterview/settings.rb. So people following along might not get
the same results.

Also, the way the scaffold is structured is a little confusing. Both
the new.rhtml and edit.rhtml use the partial _form.html. But if you
edit edit.html, it will not regenerated _form.html. You have to edit
new.html to regenerate it. This was confusing to me and Jeswin when we
tried it out. I thought the Windows version wasn't working but it was,
we just had the wrong file.

Otherwise, great work. I'm on to trying out the new tags.

-- 
Ed Howland
http://greenprogrammer.blogspot.com

From djlewis at acm.org  Fri Jun 30 16:07:29 2006
From: djlewis at acm.org (Deb Lewis)
Date: Fri, 30 Jun 2006 13:07:29 -0700
Subject: [Masterview-users] MasterView release 0.2.2 -
	maintenancerelease, fixes rhtml error, documentation updated
In-Reply-To: <3df642dd0606301233l4c425fb0k7ed8145e7e4c34a0@mail.gmail.com>
Message-ID: <20060630200734.PIBW11027.fed1rmmtao07.cox.net@DLI92cx797990>

Ed wrote:
>> One small almost insignificant note. The short video shows the 
>> admin pages and the fact that you can click on a link to view 
>> the source of the generated rhtml. But you have to enable both 
>> those options in config/masterview/settings.rb. So people 
>> following along might not get the same results.

Jeff - I think Ed's got a good point, this is the kind of thing that's
confusing/annoying to new users (exactly the folks that we want to ensure
get off the ground easily)

Suggest we change the defaults on config.enable_admin_pages and
config.enable_view_rhtml so they're on by default in development
environment, off otherwise.  Think we might have considered this briefly
already but it got lost in the shuffle getting 0.2.0 out the door in time
for RailsConf.

~ Deb



From jeff.barczewski at gmail.com  Fri Jun 30 16:12:30 2006
From: jeff.barczewski at gmail.com (Jeff Barczewski)
Date: Fri, 30 Jun 2006 15:12:30 -0500
Subject: [Masterview-users] MasterView release 0.2.2 - maintenance
	release, fixes rhtml error, documentation updated
In-Reply-To: <3df642dd0606301233l4c425fb0k7ed8145e7e4c34a0@mail.gmail.com>
References: <19cda190606300937y75b3d4dcqa7b0c85a38c73d43@mail.gmail.com>
	<3df642dd0606301233l4c425fb0k7ed8145e7e4c34a0@mail.gmail.com>
Message-ID: <19cda190606301312u5b5f17e8j3749eb73487a2fae@mail.gmail.com>

Thanks for the feedback. We will try to clarify those points.

It would be nice if I can figure out someway to indicate which files to edit
to get the proper partials since that will get many people at first.

On 6/30/06, Ed Howland <ed.howland at gmail.com> wrote:
>
> On 6/30/06, Jeff Barczewski <jeff.barczewski at gmail.com> wrote:
> >
> > Documentation was updated with some more details around
> > generator and including screenshots and an illustration.
> >
> > Jeff
> >
>
> One small almost insignificant note. The short video shows the admin
> pages and the fact that you can click on a link to view the source of
> the generated rhtml. But you have to enable both those options in
> config/masterview/settings.rb. So people following along might not get
> the same results.
>
> Also, the way the scaffold is structured is a little confusing. Both
> the new.rhtml and edit.rhtml use the partial _form.html. But if you
> edit edit.html, it will not regenerated _form.html. You have to edit
> new.html to regenerate it. This was confusing to me and Jeswin when we
> tried it out. I thought the Windows version wasn't working but it was,
> we just had the wrong file.
>
> Otherwise, great work. I'm on to trying out the new tags.
>
> --
> Ed Howland
> http://greenprogrammer.blogspot.com
> _______________________________________________
> 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/20060630/d276f635/attachment.html 

From jeff.barczewski at gmail.com  Fri Jun 30 17:20:04 2006
From: jeff.barczewski at gmail.com (Jeff Barczewski)
Date: Fri, 30 Jun 2006 16:20:04 -0500
Subject: [Masterview-users] MasterView release 0.2.2 -
	maintenancerelease, fixes rhtml error, documentation updated
In-Reply-To: <20060630200734.PIBW11027.fed1rmmtao07.cox.net@DLI92cx797990>
References: <3df642dd0606301233l4c425fb0k7ed8145e7e4c34a0@mail.gmail.com>
	<20060630200734.PIBW11027.fed1rmmtao07.cox.net@DLI92cx797990>
Message-ID: <19cda190606301420k15b82643o3cd0d475ac2c835@mail.gmail.com>

OK. I updated the defaults in the generated development.rb so that
enable_admin_pages and enable_view_rhtml are both true so that by default
people will be getting things turned on.

It will go out with the next release.

Jeff

On 6/30/06, Deb Lewis <djlewis at acm.org> wrote:
>
> Ed wrote:
> >> One small almost insignificant note. The short video shows the
> >> admin pages and the fact that you can click on a link to view
> >> the source of the generated rhtml. But you have to enable both
> >> those options in config/masterview/settings.rb. So people
> >> following along might not get the same results.
>
> Jeff - I think Ed's got a good point, this is the kind of thing that's
> confusing/annoying to new users (exactly the folks that we want to ensure
> get off the ground easily)
>
> Suggest we change the defaults on config.enable_admin_pages and
> config.enable_view_rhtml so they're on by default in development
> environment, off otherwise.  Think we might have considered this briefly
> already but it got lost in the shuffle getting 0.2.0 out the door in time
> for RailsConf.
>
> ~ Deb
>
>
> _______________________________________________
> 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/20060630/47f468af/attachment.html