On 7/5/13, Yuvi Panda <yuvipanda(a)gmail.com> wrote:
On Sat, Jul 6, 2013 at 6:36 AM, Matthew Walker
<mwalker(a)wikimedia.org>
wrote:
1. Not be
tortoise slow
Pretty sure this only matters because we do continuous integration --
we
probably don't need to do this for every commit...? Maybe once a day?
In any case -- who says PHPDoc is any faster.
Slow to use, not slow to generate. On my firefox it constantly gets
stopped with a 'script on this page is taking too long to run'
Interesting. For me its speedy (or at least acceptably fast) and I'm
on firefox 3.5
2. Have usable search
The demo at least
doesn't even offer search functionality...
But does this even matter? I would argue in favour of a independent search
solution along the lines of Ohloh [1] so that we can integrate our JSDuck
documentation.
Haven't checked out Ohloh's, but something as simple as 'I want to see
documentation for WikiPage::factory' should be achievable by typing
'WikiPage::factory' into the docs. I'm setting up a phpdoc instance on
my local system, to see how it goes.
I generally go directly to the class I want, so not really something
that would bother me (Actually I didn't even know we had a search
box).
I also primarily use grep locally to search for things... I guess
newbies which are the documentations primary use case, probably are
less likely to do that.
--bawolff