[Jspro-devel] RE: Aims for Release 3

[Randolph T. F. <gat...@ci...>]

Hey Stuart -

Here are my thoughts on what you mentioned below:

(1) The Debug window - I totally agree with you that the Debug window is =
a
great addition to the toolset and a nice way to watch for errors.  So, I
obviously think it should remain.  Having said that, I also know that it =
has
a few big design flaws that need to be rearchitected.  I say we just =
leave
it as is for now.  I know what needs to be fixed to make it much more
system-friendly from a design standpoint, but I would like to take a =
little
more time to make sure that we both agree on a design path for it and =
then
attack the task with that plan.  My suggestion is that we get back to =
this
topic when I get back from my honeymoon.  If I forget, don't forget to
remind me.

(2) API docs - I am glad you went and took a look at jsDoc.  It is much
better than us starting from scratch, and we should be able to modify it =
for
our specific purposes (certain tags we use, etc.) if they decide not to
incorporate everything we need.  Overall, it's nice to know that we =
should
be able to generate some very good documentation soon.

(3) New methods - The only methods that I particularly had planned were =
some
browser-sniffing routines for the Browser class that I began work on.
Anything else besides that is fair game, so get to it! ;-)

(4) Breaking up Math and Array - Although I completely agree that Array =
and
Math should be broken up, I think it would be good to keep the classes
"whole" for at least one or two more releases due to the rapid =
development
schedule and upgrade cycle we have put in place.  This would give us =
time to
better plan out what we want to do to accomplish this, since we could
account for methods that we plan to build in as well as the ones we =
have.

(5) Website - I have finally begun work on our website.  This is where I
will be spending the majority of my time on jsPro for the near future, =
along
with my other task...(see below).  However, I will be leaving for my
honeymoon soon, so I won't be around for 2+ weeks starting a week from =
this
Sunday.  So, you could take over while I am gone or just wait until I =
get
back to finish it up.  All in all, I hope to have something simple
completed.

(6) QA - Honestly, Stuart, I really enjoy doing the QA stuff.  I think I =
am
good at it, and it makes me feel like I am making a good contribution to =
our
code base given that most of the ideas are coming from you.  Once I have =
the
time (post-wedding) to be able to commit more time to jsPro, I plan to =
do
some new development for jsPro myself, but up until now, I felt that =
this
was the best way for me to add value to the project.  So, don't really =
worry
if your code is not perfect or close to it (no offense! :-) the first =
time
out of the gate, since your initial development tasks are what is making
jsPro more awesome of a library of tools all the time.  If you keep
developing the new things to push the toolset forward, I am more than =
happy
to come behind to ensure consistency, clarity, etc.  All in all, I think
this separation of tasks is what is really making us quite a powerful
development team for two people (almost like extreme programming, except =
we
aren't sitting at the same computer! :-)

Cheers,
Randy

-----Original Message-----
From: jsp...@li...
[mailto:jsp...@li...] On Behalf Of Stuart =
Wigley
Sent: Monday, September 22, 2003 7:50 AM
To: jsp...@li...
Subject: [Jspro-devel] Aims for Release 3


Hi Randy,

There are a few things i'd like to clear up for
release 3, and I'd like to know thoughts on how
achievable they are:

1. The Debug window: how can we improve it? should we
just dump it? Do its benefits exceed the flaws that it
has? I do find it quite useful during debugging but it
could be something that we keep in cvs but don't
package into releases? Alternatively we could just
leave it for now and plan a longer term development of
it so that it becomes a more useful development
utility.

2. API docs: i've raised a support request with the
jsDoc guys because you can't currently generate docs
against our String, Array etc libraries (as they don't
have a Class definition). I think we should hold off
on generating API docs until we can create a full set.

3. New methods: I've got about a thousand new methods
I want to add in (:-) and as you've probably noticed
my approach is haphazard - is there in particular you
have planned?

4. Breaking up Math and Array: I want to split a lot
of the methods here out into new classes but I'm not
sure this is a job for R3. Maybe we should wait until
we have a few more methods available.

5. Website: if you are struggling with time
commitments i might just put something simple up to
prove that we exist...ok with you?

6. QA: thanks for what you've been doing. I really
need to spend more time checking my code. Maybe we
should write a developers guide and QA checklist?

Anything else?

I hope all is well at your end

Cheers
Stuart



________________________________________________________________________
Want to chat instantly with your online friends?  Get the FREE Yahoo!
Messenger http://mail.messenger.yahoo.co.uk


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Jspro-devel mailing list
Jsp...@li...
https://lists.sourceforge.net/lists/listinfo/jspro-devel