RE: [Asunit-users] Great tool, but where's the documentation?

[Kristopher S. <ksc...@re...>]

Thanks, Luke.

>What platform are you running?

At home I tend to use the Mac and at work I tend to use Windows. I'm =
using Eclipse on both platforms, so I'll go ahead an use its built-in =
CVS support which seems to allow me to create patch files easily, so I =
think I'm all set there.

How frequently would you prefer that I send you patch files? I've =
finished documenting the Assert class. Should I send a patch file =
containing those changes to you now, or should I wait until I have more =
classes finished?

Also, I've decided to use Dave's as2api utility as my reference doc =
generator when proofing my doc comments. I've chosen as2api because a) =
I'd like to support Dave's efforts (thanks, Dave!), b) using as2api =
should help ensure that the doc comment formatting will parse properly =
in any doc gen tool that supports javadoc style tags, and c) it's free. =
There are some downsides, however. From what I can tell, as2api can not =
currently generate XHTML-compliant markup (and in fact, the markup =
required to get the doc comments to display properly will likely have to =
change if as2api ever does become XHTML-compliant), and it doesn't =
support alternate output formats - especially Flash Help and XML.

Kris




-----Original Message-----
From: Luke Bayes [mailto:lb...@gm...]
Sent: Mon 7/4/2005 7:24 PM
To: Kristopher Schultz
Cc: asu...@li...
Subject: Re: [Asunit-users] Great tool, but where's the documentation?
=20
Hey Kris,

I've been using CVS for a long time now too - but I'm also very
inexperienced when it comes to dealing with patches! Maybe we can
learn this thing together. ;-)

I've checked in my branch - the head revision should be all set for
you to do an update.

What platform are you running?=20

I use Windows which means that I get to use Tortoise SVN. In this
case, you can just right click on a CVS repository and choose "Create
Patch". This will generate a .patch text file that contains all of
your changes. You can simply email me that patch file, I can easily
integrate on my end and then you'll need to do another update.

One thing that has worked pretty well for me in the past, was to
actually copy the cvs directories into my Macromedia Configuration
directory. Then I can edit the actual files as they're being used,
test them, and update them periodically to get the latest. I wouldn't
recommend "leaving" your config in this state, but for periods of
heavy development, it helps find the simple errors sooner.

I just did a quick google search on "create cvs patch file" and there
seem to be a lot of resources out there.

Here's the first one that came up for me:
http://owen.sj.ca.us/rkowen/howto/cvs.html#patch

Basically, what I'll be looking for is a single .patch file that
includes all changes that you've made since the repository was last
updated.

Thanks,


Luke Bayes
www.asunit.com