+1
Also, the code samples look a bit pre-1997... anything I can do to help out
with the CSS? Maybe something like this can help clean it up a bit:
div.example{
background: #f0f9fc;
border-left: 2px solid #c2c9d1;
padding: 1em;
margin: 1em 0 1em 1em;
}
div.programminglist{
background: #e2f1f8;
padding: 0.5em;
border-left: 1px solid #c2c9d1;
font-family: Consolas, Lucida Console, monospace;
}
--
Hector
On Fri, Jan 22, 2010 at 2:01 PM, Mark Wright <[email protected]>wrote:
> I really miss the navigation in the side bar that linked to every
> component rather than just the current components sub pages. Is there
> any way to get that back?
>
>
> Mark
>
> On Fri, Jan 22, 2010 at 2:11 PM, Nick Pack <[email protected]> wrote:
> > Its a shame that you guys couldnt replicate the original navigation flow
> > with the new version, IMO the previous version was a lot better!
> >
> > +2 cents
> >
> > ----
> > Nick
> >
> > Matthew Weier O'Phinney wrote:
> >>
> >> -- Mark Wright <[email protected]> wrote
> >> (on Friday, 22 January 2010, 12:41 PM -0700):
> >>>
> >>> What's up with the reference guide? Was there an update to the guide
> >>> that went horribly wrong?
> >>
> >> Likely you're not getting the new stylesheet; try refreshing. However,
> >> please also note that we've restructured the manual quite a bit,
> >> including using a new tool to render the manual (the PHP project's PhD
> >> docbook parser/renderer); this has led to changes in how navigation
> >> works.
> >>
> >
>
>
>
> --
> Have fun or die trying - but try not to actually die.
>
