<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=Content-Type content="text/html; charset=us-ascii">
<META content="MSHTML 6.00.2900.2873" name=GENERATOR></HEAD>
<BODY>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=888455000-14062006>suggest we chase both of those problems (<title>
parsing in analyzer, admin controller stylesheets) after getting current
round of code stuff settled and integrated (your file i/o, my initializer
stuff), then catch up on loose ends and polish work items. I'm starting to
have trouble juggling changes between various dev and test copies, would like to
get things integrated onto trunk before I accidently wipe out something
useful.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=888455000-14062006></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=888455000-14062006>[not trying to push you, just
observing]</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=888455000-14062006></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=888455000-14062006>I starting running build tasks last night to test the
various install flavors, but got bogged down poking around the rake file
exploring and then hitting problem with building zip's for some of the packages
(probably easy to fix, likely just something diff about your system or *nix that
I need to update on my system). Will try to get back into that
tonight.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=888455000-14062006></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=888455000-14062006>Rakefile change notes: there's a couple build tasks
that need doc/stylesheets/*.* added to their flie specs; some other tweaking on
the syntax check/LOC/mvparse of examples guys. Nothing
earthshaking.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=888455000-14062006></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=888455000-14062006>If it's ok with you, I'd like to factor out the prereqs
and installation instructions section of the current docs into a separate
doc/installation.html and then beef up the instructions to better explain the
flavors of packages available and when to pick which. I know on my
first install experience I gave up trying to figure out which of the downloads
to use and just grabbed the include-everything bundle. Not a problem for
experience rail-ers, I think, but sort of befuddling to
newbies.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=888455000-14062006></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=888455000-14062006>My goal is for this stuff to *look* polished when a
potential user arrives to browse the docs, easy to figure out whether it runs on
their system (platform version, prereqs, etc), and really easy for someone new
to rails or mv to get going. Doesn't matter how glorious the package is if
people thnk it looks half-baked or they can't get off the ground
easily.</SPAN></FONT></DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=888455000-14062006></SPAN></FONT> </DIV>
<DIV dir=ltr align=left><FONT face=Arial color=#0000ff size=2><SPAN
class=888455000-14062006>~ Deb</SPAN></FONT></DIV><BR>
<DIV class=OutlookMessageHeader lang=en-us dir=ltr align=left>
<HR tabIndex=-1>
<FONT face=Tahoma size=2><B>From:</B> Jeff Barczewski
[mailto:jeff.barczewski@gmail.com] <BR><B>Sent:</B> Tuesday, June 13, 2006 5:22
PM<BR><B>To:</B> djlewis@acm.org;
masterview-devel@rubyforge.org<BR><B>Subject:</B> Re: [Masterview-devel] Test
case: analyzer breaks on template that parser handles<BR></FONT><BR></DIV>
<DIV></DIV>That's a good point about the admin page not looking good without the
stylesheets, we should account for the fact that not everyone is going to run
the generator. Probably include a different stylesheet or embed some minor
style. <BR><BR>I can take a look at the template scan, I have mainly tested on
files that came out of the generator so maybe on something simpler that doesn't
have as many mv:generates, maybe we are getting into an empty list situation
that we weren't with the generator created files. <BR></BODY></HTML>