RebelDawg wrote:I absolutely love SWGAide but due to it lacking some things, I have just recently started usuing JnF as well.
Is there anything that we the crafting community can do to help you get some of this coding done? Perhaps just some data entry type footwork for quick copy/paste into databases etc.
SWGAide is open source and found at http://sourceforge.net/projects/swgaide
so anybody that has programming skills are welcomed.
I tried making SWGAide as modular as possible so adding a new feature, such as profession wheel, expertize builder, etc., is just as simple as adding a new panel to the framework. Then some kind of easy to edit format for these features would be a help, we can always discuss how when somebody enters the small group of two developers
If anybody wants to help but lacks coding skills, the README file needs an update to include advices regarding Windows Vista. Perhaps also other documentation or the help files could be made better.
I lack the the time reading up on how to implement a trampoline
starter for SWGAide, one that starts SWGAide, if there is a current update available or already downloaded it replaces the old for the new; then it kicks off SWGAide as usual.
If anybody skilled in Java just wants to walk over the code and rinse
out leftovers or re-factor
parts of the code or modularize
other code, they are welcomed. I have a few ideas of what needs to be done with code that has kind of outgrown itself and should be made more modular to be easier to use by new features, so, there is always stuff that can be done, and be done better. I am certainly not a guru but learn from my mistakes and do my best to figure out the most user-friendly way to do things, if possible.
Currently I believe all of the schematics
here at SWGCraft could be verified and be completed if necessary. Next feature is indeed schematics and if SWGCraft is up-to-date it will be a breeze to use that information directly from this site. Do it systematically, profession by profession, level by level, detail by detail. Post in the schematics forum board. Add extra info to the comments field, for loot/quest/reward schematics add a comment on how achieved and details about it prior to learning it and similar data.
and what is given each level, XP necessary for each level, the in-game descriptions for the different abilities and skills. Open a new thread in a appropriate forum board where format can be discussed so it is easy to parse data for an application, XML is to prefer, but rather provide the data in a fixed text format and we can fix a script to make it machine friendlier later on.
data. Best format is XML here since this data really is a tree and having dependencies, some ugly as ... But again, it is better to have the all data and dependencies in text form and we can always fix it later on.
I am pretty sure there are many ideas out there, and if they are suitable in an application, shoot.
In fact, more than half of a developers work is to work out the stuff on paper first, to work out the description of what the application is supposed to do. Yes, exactly so, supposed
to do. So, if you have a bright idea but cannot program, try to write a text description of what you want it to look like and what it should do. Such as three buttons and a field where I see this. Clicking A does this, ... Any developer can pick up such a description and make wonders with it. The better and the more detailed the description the better, such as clicking B and if X is true then do this, otherwise that. Anybody is welcomed, you may imagine something that will never come to me nor Oarun