Masterview devel - Jun 2006 - Integrate new initializer mechanism into MIO rework.

ok, I think it all got out there and reorganized (sorry about the email
blizzard, the reorg from my working copy didn''t "take" so I
just brute-force
moved everything).  As far as I know all your recent changes have been
picked up and brought forward.
 
UPGRADE: You''ll need to recreate any MV settings customizations that
you
have into the new config/masterview settings.rb and env config files. Should
be pretty straightforward, doc/configuration.html describes settings.
 
init.rb and task/masterview.rake replicated manually into the plugin
generator templates.
 
Testing of the build products and installation variations incomplete -
can''t
easily do all that on my win32 box.  And I haven''t tested running the
masterview.rake tests on a rails app yet.
 
Rakefile changes:
 
o i was messing around with wrapping a ''dev'' namespace on
developer
utilities (parsing examples templates, syntax checking), change it back if
you don''t like
 
**the dev:mvparse_examples rake task is broken, needs to be fixed up for the
new mio but i punted for now
 
o was trying to unravel what chunks go into which build packages, so
you''ll
see a bunch of factoring in file subset specs - tested that as much as I
can, but we''ll have to doublecheck when doing a full build to make sure
all
the files we want in various build pkg''s are done properly
 
~ Deb
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/masterview-devel/attachments/20060615/721de1c8/attachment-0001.htm

I fixed the dev:mv_parse_examples task

Good job on the reorg and config work, it is pretty nice!!

I had a problem trying to use

config.after_initialize { MasterView::Log.level = DEBUG }

in my config/masterview/settings.rb

It throws me into some sort of rdb debug mode?? I thought I would ask you if
this works for you and if you had any ideas. I''m guessing that some
sort of
exception is being raised (but not shown) and this is kicking me into a
debugger?? Not sure, but if it is all working for you then I will look into
it. Let me know if you have any ideas.

Thanks,

Jeff

On 6/15/06, Deb Lewis <djlewis at acm.org> wrote:
>
>  ok, I think it all got out there and reorganized (sorry about the email
> blizzard, the reorg from my working copy didn''t "take"
so I just brute-force
> moved everything).  As far as I know all your recent changes have been
> picked up and brought forward.
>
> UPGRADE: You''ll need to recreate any MV settings customizations
that you
> have into the new config/masterview settings.rb and env config files.
> Should be pretty straightforward, doc/configuration.html describes
settings.
>
> init.rb and task/masterview.rake replicated manually into the plugin
> generator templates.
>
> Testing of the build products and installation variations incomplete -
> can''t easily do all that on my win32 box.  And I haven''t
tested running the
> masterview.rake tests on a rails app yet.
>
> Rakefile changes:
>
> o i was messing around with wrapping a ''dev'' namespace on
developer
> utilities (parsing examples templates, syntax checking), change it back if
> you don''t like
>
> **the dev:mvparse_examples rake task is broken, needs to be fixed up for
> the new mio but i punted for now
>
> o was trying to unravel what chunks go into which build packages, so
> you''ll see a bunch of factoring in file subset specs - tested that
as much
> as I can, but we''ll have to doublecheck when doing a full build to
make sure
> all the files we want in various build pkg''s are done properly
>
> ~ Deb
>
> _______________________________________________
> Masterview-devel mailing list
> Masterview-devel at rubyforge.org
> http://rubyforge.org/mailman/listinfo/masterview-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/masterview-devel/attachments/20060616/0ddba7fa/attachment.htm

MasterView.set_log_level( ''DEBUG'' )
 
generator style changes are good, i like that naming scheme better, reduces
possibility of inadvertant collision with apps'' own stylesheets.  We
need to
document this at some point ("Using the mv admin controller will add some
stylesheets to your app''s public/stylesheets..."
 
thx for the other fixes in initializer, obviously I hadn''t tested a few
of
those scenarios well enough
 
My priorities for today:
- respond to mv:generate keyword subst. and file ext. handling semantics
    mv:generate="{template_path}" and ="{template_path}.css"
- think about issues you raised about what/how to do config w/ new mio
- testing and documentation (doc/installation.html)
 
~ Deb

 
  _____  

From: Jeff Barczewski [mailto:jeff.barczewski at gmail.com] 
Sent: Friday, June 16, 2006 4:40 AM
To: djlewis at acm.org; masterview-devel at rubyforge.org
Subject: Re: [Masterview-devel] Integrate new initializer mechanism into MIO
rework.


I fixed the dev:mv_parse_examples task

Good job on the reorg and config work, it is pretty nice!!

I had a problem trying to use 

config.after_initialize { MasterView::Log.level = DEBUG }

in my config/masterview/settings.rb 

It throws me into some sort of rdb debug mode?? I thought I would ask you if
this works for you and if you had any ideas. I''m guessing that some
sort of
exception is being raised (but not shown) and this is kicking me into a
debugger?? Not sure, but if it is all working for you then I will look into
it. Let me know if you have any ideas. 

Thanks,

Jeff
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/masterview-devel/attachments/20060616/1eb3ee25/attachment.htm

>>  MasterView.set_log_level( ''DEBUG'' )
 
hmm hmm... string or symbol or be generous and accept either flavor of the
name from client??
 
    MasterView.set_log_level( :DEBUG )
 
and I suppose assignment is probably more natural that setter function, I
think I just hadn''t decided at the time I did that whether I liked
assigment
semantics directly on the MV module, but it''s probably fine
 
    MasterView::log_level= ''DEBUG''  #? or :DEBUG ?
 
I''ll put that in this morning.
 
Contemplating also supporting Masterview.log service, rather than
MasterView::Log.  If clients outside the MV/directives impls have legit need
to get the log, prefer accessor rather than direct ref to module constant.
Maybe premature, won''t add this unless we decide it''s
appropriate to expose.
 
~ Deb
-------------- next part --------------
An HTML attachment was scrubbed...
URL:
http://rubyforge.org/pipermail/masterview-devel/attachments/20060616/44dbc39c/attachment.htm