From WoWWiki

CastParty » CVS Note that with CVS you get all the latest changes. The code here is often untested and may not always work.

Command line CVS checkout

• Make a temporary folder to checkout the code to, like CastParty_CVS
• Go to the newly created folder
• Type these magic lines:
  • cvs -z3 -d:pserver:anonymous@wowcastparty.cvs.sourceforge.net:/cvsroot/wowcastparty co CastPartyGUI
  • cvs -z3 -d:pserver:anonymous@wowcastparty.cvs.sourceforge.net:/cvsroot/wowcastparty co CastPartyOptions

This should give you three folders named as the modules you just checked out. Copy these folders to <YourWow>/Interface/Addons/ and that's it.

If you later on want to update from the CVS again, you can run this commando from the same folder you ran the above three:

• cvs -z3 -d:pserver:anonymous@wowcastparty.cvs.sourceforge.net:/cvsroot/wowcastparty up -dPR

Anonymous Access

• Install the latest of TortoiseCVS
• Setup TortoiseCVS as follows:
  • Click fetch list.
  • Download the modules

Developers Access

• install the latest of TortoiseCVS (but you can use others if you want)
• Setup an account on sourceforge.net. If you want to automate logging into CVS with tortoise, you must use pageant.
  • To use pageant, you have to setup your public/private key with sourceforge.
  • You have to use puttygen to do this.

• Save your private/public key to your hdd
• Upload your public key to sourceforge.
• Wait a day or two for sourceforge to update it (only if you want to automate the update/commit process)

• Create a shortcut for pageant. make the shortcut be: pageant.exe YOUR_PRIVATE_KEY.ppk

• Setup TortoiseCVS as follows:

• Click fetch list.
• Download the modules

Module list

Relevant to current work.

The nonGUI (original) module of CastParty is:

• wowcastparty

The current modules I am working on with and for CastParty (advanced and GUI options) are the following: Note: I include all of the option dependencies that I tinker with as modules as well.

• CastPartyGUI
• CastPartyOptions

The current modules for WoW development

• myDebug (allows for checking variables with a gui.)
• SciTE for WoW (tinkered with and modified)

Here is some information about what Scite for WoW is:

It's called SciTE and I've taken what was publicly available, and tricked it out for WoW mod development! There is also one available for XML development (don't remember the name of it ... i do it by hand...). Scite for WoW is the best thing i know about for WoW LUA development. It does code highlighting as well as API autocompletion and tooltips. I'm working on finishing the CastParty specific stuff, and need help filling out the details for the WoW (and CastParty tooltips as well) API details.

I did this because I was sick and tired of silly typos. This helps tremendously, as the code is colored, so if it's typed incorrectly, I'll know about it. There is also a utility I integrated called WoWBench. It allows you to test an addon OUTSIDE of wow by firing events and looking at results. It is completely contained within LUA, and is separate from wow. (Update: It's not easy to use....)

ALSO... You can now test your code to make sure it is LUA "correct" (just press F5) or compile it (F7 and ctrl+F7) so you don't have to wait for wow to load (or reload) just to figure out you typed "tjen" instead of "then". Just double+click on the error message, and it takes you to the code!!! it' so cool and open source! woot!

haleLUAjah!
-nathan

and... it's a big download. You MUST setup config.lua to your liking in the WoWBench dir. for that to work properly. You shouldn't have to recompile everything, but just in case, run the WoWBench Compile option from the TOOLS menu just in case.

PS: Concerning SciTE for WoW... I need lots of help filling in and checking the wow api tooltips. most of them are there, but there are duplicates and blank entries.. :( if you tinker with it, make sure to commit right away, and before you tinker, make sure you update, so you don't redo the same thing someone else might have done. (that is.. if you care to use it).