-- Cristian Bichis <[email protected]> wrote
(on Friday, 15 April 2011, 05:34 PM +0300):
> I am having the same "issues" with the DocBlox and i have some suggestions:
> 1. Left frame is too small or maybe fonts are too large... Try to
> navigate to Zend\View\Helper and you going to see lot of wrapped
> class names, is hard to read...
> 
> Either making larger the left frame or reducing font sizes may help...
> 
> 2. The format from the right column was much more easily to
> "read"with the old phpDocumentor, i think especially due to using
> diff colors for some of the parts of the documentation (constants or
> member variables or so if i recall).

Mike van Riel (lead on the DocBlox project) has been working on both of
these, to my knowledge, and we may be rolling out a new version in the
next week or so.

> Cristian
> > -- ZED MASTER<[email protected]>  wrote
> > (on Friday, 15 April 2011, 09:58 AM -0300):
> > > Why have you changed the format from the API documentation?
> > For a variety of reasons:
> > 
> >   * Moved to an actively developed project (DocBlox) that not only works
> >     for PHP 5.2 and below but also for PHP 5.3 (important as we move
> >     towards ZF2).
> >   * Speed and resource usage. phpDocumentor took 80-100 minutes minimum
> >     -- when it didn't consume all available RAM. DocBlox renders in less
> >     than 10 minutes and is very resource-conscious.
> >   * Ability to modify templates. phpDocumentor's templating system was
> >     not well documented, and it was incredibly difficult to modify.
> >     DocBlox is more flexible -- as you'll see in the coming weeks.
> > 
> >  >It was confusing and hard to see.
> > Can you please be more specific so that we can address the concerns?
> > This is too vague to enable us to make any meaningful chanegs.

-- 
Matthew Weier O'Phinney
Project Lead            | [email protected]
Zend Framework          | http://framework.zend.com/
PGP key: http://framework.zend.com/zf-matthew-pgp-key.asc

-- 
List: [email protected]
Info: http://framework.zend.com/archives
Unsubscribe: [email protected]


Reply via email to