[Masterview-devel] Test case: analyzer breaks on template that parser handles

[Jeff Barczewski]

Yes, I agree. I am trying to get the code released asap.

I fully agree about it looking polished, that makes a huge difference in
whether people will actually look into something.

On 6/13/06, Deb Lewis <djlewis at acm.org> wrote:
>
>  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.
>
> [not trying to push you, just observing]
>
> 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.
>
> 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.
>
> 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.
>
> 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.
>
> ~ Deb
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://rubyforge.org/pipermail/masterview-devel/attachments/20060614/a3ece1de/attachment-0001.htm