I know that downloading straight from the File Cabinet was the easiest way to get my app. However, I realized that I can't be tracking any kind of statistics on as to how many people download my app. I'll no longer be posting the latest build there. On the bright side, I've kind of gotten the hang of SourceForge's release system even though I don't like it. A new release will be posted on my project's home page almost every time I do a submission.
Oh, and my brain is probably very charred by now trying to think of an effective way to add skills to a skill plan.
Subscribe to:
Post Comments (Atom)
Posts
Just add a lil "+" sign to the left or right.
ReplyDeleteAdding a GUI element (a plus sign, for example) is the easy part. The tricky part is populating the table in a logical manner.
ReplyDeleteFor example, take a look at the massive "Large Artillery Specialization" graph. You'll see that "Gunnery" is a leaf in 9 different places. "Small Projectile Turret" is a node in 4 different places. "Sharpshooter" is in 3 different places. There are other repetitive nodes in this graph. If I don't have "Small Projectile Turret" trained at all, do I add it 11 different times (levels 1-5, 1-3 and 1-3) to my skill plan? Of course not. You only need it 5 times for levels 1-5.
Going further with this example, lets say you also want to add "Large Autocannon Specialization". Several of the skills are duplicates and thus don't need to be re-added. But then there's the question of where in the table can the new skills be placed. Should they placed at the end of the table? Sounds reasonable but then you're putting a huge limitation on the ability to add a new skill to the plan at whatever position you want. If you want that kind of freedom, a ton of validation code needs to be written to ensure the place you want to add your skills is valid.
All this stuff gets intensely complex which is why I'm having some difficulty keeping it straight in my head. I'm having some luck with it now by taking one step at a time such as creating a parser/validation object.
Well, coding never really been my strong side...
ReplyDeleteBut isnt it a way to prevent duplications?, Ohh and btw, you should make the updating timer clickable so i can update whenever i feel like it.
Another Idea is adding, in every skill category, a total SP of that category info, so for example:
Gunnery - 406576 SP of a total of XXXXXXX SP
or something simular.
Also, ingame name "Dansel" if you wanna talk, i'm willing to help wherever i can.
ReplyDeleteThere is a way to update whenever you want via the File menu. Clickable timer? Eh, maybe. I'd have to do some subclassing of NSProgressIndicator. It's not difficult but does take time. In the mean time, the requested functionality is there. If anything, unless I get a lot of demand, it's something I'm gonna keep on the back-burner for now.
ReplyDeleteI'm not sure if you understood my first reply. Of course there are ways to prevent duplication. Anything you want done is possible, you just have to program it right. But validation is a tedious process because you have to worry about accuracy and efficiency.
Well, when you're talking coding language too me, I wont understand alot. I have never been much into coding. I have been mapping and such for games, and also been designing stuff for like, lots of stuff, so i have a good feel for whats easy too use, but i just comeup with ideas and design, it's not my job too implement them though.
ReplyDelete