Re: [Jsdoc-user] [JSDoc 2 is now in the Initial Planning Phase -- Have at it!]

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

I believe I am 'pagameba' on sourceforge.  I have no experience with  
Google so I can't comment on that.

Cheers

Paul

On 18-Oct-06, at 12:24 PM, Michael Mathews wrote:

> Great, thanks for the commitment, Paul. We can use any help we can  
> get! What's your ID on SourceForge.net, I'll add you as a developer  
> on the project (even if you just do testing).
>
> I'm considering hosting the JSDoc 2 project on google actually. Any  
> one have a preference? One difference I've found is that google  
> uses svn and is somewhat faster, but sourceforge is more featureful.
>
> Vote now...
>
> On 18/10/06, Paul Spencer <psp...@dm...> wrote: I would  
> love to be part of your testing team.  I can provide some
> samples of Prototype code that should test the system, and can run
> tests against some fairly large projects - um, now I'll have to
> actually write the documentation!
>
> Cheers
>
> Paul
>
> On 18-Oct-06, at 9:06 AM, Michael Mathews wrote:
>
> > Hi Paul,
> >
> > I think it's pretty safe to say JSDoc 2 will support Prototype. The
> > only question is how to best implement that support. You can help:
> > send me a typical file of Prototype JS you've written and can't get
> > JSDoc 1 to work with. I'll make that part of a unit test and start
> > planning how to support that syntax. (I've never actually used
> > Prototype myself)
> >
> > It may be as simple as writing some detailed documentation on how
> > to get the current tool to work with Prototype's syntax, but if, as
> > I suspect, the JSDoc tool itself needs to be modified, we'll make
> > that a priority.
> >
> > Also would you volunteer to run tests on any new release candidates
> > to confirm that they work against your Prototype code?
> >
> > regards,
> > Michael < mi...@gm...>
> >
> > On 18/10/06, Paul Spencer <psp...@dm...> wrote: Gabriel,
> >
> > for me, the most pressing need is for something that can work with
> > Prototype.js (http://prototype.conio.net) style coding.  I think
> > jsdoc already has excellent features for its output, but it is
> > essentially unusable for me as I am using Prototype as my base
> > library.  It would also be awesome just for documenting Prototype :)
> >
> > Cheers
> >
> > Paul
> >
> > On 16-Oct-06, at 11:30 AM, Gabriel Reid wrote:
> >
> > > Hi Everyone,
> > >
> > > I'm just passing on this announcement from Michael Mathews about a
> > > second
> > > incarnation of JSDoc that is currently in the planning phase.  
> We're
> > > hoping
> > > to address the many shortcomings of the current version of JSDoc,
> > > but we
> > > first need to get feedback from everyone who is using the tool.
> > >
> > > If you have any JavaScript documenting wants or needs that JSDoc
> > isn't
> > > currently addressing, now is your chance to let yourself be heard!
> > >
> > > The discussion can be found at <http://groups.google.com/group/
> > > jsdoc-2>.
> > >
> > > Looking forward to hearing from you!
> > >
> > >
> > > Regards,
> > >
> > >     Gabriel Reid
> > >
> > >
> > > ----- Forwarded message  -----
> > >
> > > ANNOUNCEMENT: For quite a long time now Gabriel Reid has been
> > laboring
> > > valiently to keep up with the evolving needs and requests of the
> > JSDoc
> > > users, burdened by a general design which simply wasn't flexible
> > > enough
> > > to easily handle the new world of JavaScript we now find
> > ourselves in.
> > >
> > > I take full responsibility for getting Gabriel into this
> > situation and
> > > want to make what ammends I can by helping to design a new, more
> > > powerful, flexible and extensable version for the future. JSDoc  
> 2.0
> > > will be a ground-up rebuild with the paramount intention of  
> handling
> > > more variations in code and style than was possible in JSDoc 1.
> > >
> > > So, while the clay is still wet and gooey, you are highly
> > > encouraged to
> > > stick a finger into the shape of what JSDoc 2 will be. What  
> have you
> > > always wanted but couldn't have in your JS documentation? Any and
> > all
> > > suggestions will be considered and, if the case is good, will be
> > > implemented.
> > >
> > >
> > > ----- End forwarded message -----
> > >
> > >
> >  
> ----------------------------------------------------------------------
> > > ---
> > > Using Tomcat but need to do more? Need to support web services,
> > > security?
> > > Get stuff done quickly with pre-integrated technology to make your
> > > job easier
> > > Download IBM WebSphere Application Server v.1.0.1 based on Apache
> > > Geronimo
> > > http://sel.as-us.falkag.net/sel?
> > > cmd=lnk&kid=120709&bid=263057&dat=121642
> > > _______________________________________________
> > > Jsdoc-user mailing list
> > > Jsd...@li...
> > > https://lists.sourceforge.net/lists/listinfo/jsdoc-user
> >
> > +-----------------------------------------------------------------+
> > |Paul Spencer                          psp...@dm...     |
> > +-----------------------------------------------------------------+
> > |Chief Technology Officer                                         |
> > |DM Solutions Group Inc                 http://www.dmsolutions.ca/ |
> > +-----------------------------------------------------------------+
> >
> >
> >
> >
> >
> >  
> ----------------------------------------------------------------------
> > ---
> > Using Tomcat but need to do more? Need to support web services,
> > security?
> > Get stuff done quickly with pre-integrated technology to make your
> > job easier
> > Download IBM WebSphere Application Server v.1.0.1 based on Apache
> > Geronimo
> > http://sel.as-us.falkag.net/sel?
> > cmd=lnk&kid=120709&bid=263057&dat=121642
> > _______________________________________________
> > Jsdoc-user mailing list
> > Jsd...@li...
> > https://lists.sourceforge.net/lists/listinfo/jsdoc-user
> >
>
> +-----------------------------------------------------------------+
> |Paul Spencer                          psp...@dm...    |
> +-----------------------------------------------------------------+
> |Chief Technology Officer                                         |
> |DM Solutions Group Inc                http://www.dmsolutions.ca/ |
> +-----------------------------------------------------------------+
>
>
>
>
>

+-----------------------------------------------------------------+
|Paul Spencer                          psp...@dm...    |
+-----------------------------------------------------------------+
|Chief Technology Officer                                         |
|DM Solutions Group Inc                http://www.dmsolutions.ca/ |
+-----------------------------------------------------------------+