RE: [picocontainer-dev] Updated CSS for Pico Distribution

> > (It looks like its chopped off in mid-paragraph. Wait for the page to
> completely
> > load, and then scroll down towards the page bottom to see what I mean)
> >
> > I put the two stylesheets side by side for the moment and only flipped
> > PicoContainer's skin to reflect "pico2.css".  Since sometimes layout
> (once you
> > get to graphics folk) can start a holy war, I put the two side-by-side so
> people
> > can kick the tires on other parts of the pico docs by simply swapping the
> style
> > sheet reference and rebuilding the distribution.
> >
> > If everything is 'ok', then I'll remove pico.css, rename the new one from
> > pico2.css -> pico.css, and then we'll be able to flip the switch for all
> the
> > site docs.
> >
> > Let me know if you guys have any issues.
> >
> 
> Only issue I see is that one of the titles wraps around in the
> "Container Choices" menu - we could rename to CommandLinePicoContainer,
> the Arguments is kinda implicit in CommandLine ....

Ahhh, worked in my browser....  Safari does it again :)

> 
> BTW,  how do you feel about having an FX-Menu like
> http://waffle.codehaus.org/?  It's easy an unintrusive using
> http://mootools.net.   This is the js needed:

Honestly, I don't care for it that much when presented in that sense that waffle
uses it.  I think it hides too many options, so the user can't really see what
documentation is there with only a glance.  By having more of an old-fashioned
table of contents, I think we get our message across better.

Perhaps if we used it in the more of a super-high-level overview menu, ie 

PicoContainer (Has about, etc)
Documentation  
Download PicoContainer
Developer Information

That kind of thing... 

Otherwise, I find it a bit unfriendly the way the waffle site does it.

IMO, of course!



								-Mike



---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email