Who's working on what?

[EMBTonkin]

Just post what you are working on to avoid too much overlap. Currently working on: • Fixing problems I left behind in rush to get ready for presentation

• Stop using 'setPreferedDimention' and find a decent layout manager.
• Cancel button for dialog boxes, input validation
• Better AddDragon function for DragonTree
• Support parent changing? Or remove altogether
• revisit test functions to ensure they still work (such as getGen, which does not)

To Do: • Highlight ancestors of selected dragon as well?

[StrykeSlammerII]

default constructors and DragonTree.addDragon( new Dragon ) is done. we may need to discuss additional parameters for that method, but that can be done elsewhere ;)

Currently working on: Committing stuff back onto the master branch -_-

[StrykeSlammerII]

• fixed an issue in my previous addDragon() caused by using new Dragon(node) rather than keeping the same Dragon objects. I'm still not sure we should be tracking allDragonList; see my comments on DragonTree.java
• added getDragonByID(String ID) though we'll need to verify when adding dragons that the ID is unique.

TODO: DragonTree.getGeneration(int) and DragonTree.getActiveDragons(); possibly change the second to getExaltedDragons(boolean) in case we want dragons that ARE exalted? (or getDragonsByExalted(boolean) ? we should probably settle on a naming system for these get methods)

[StrykeSlammerII]

Next TODO:

• Analysis.canBreed(Dragon, Dragon) should be the only method left there, for now; working on howto parse Ancestries for that.
• There's still some discussion on whether Dragon needs a pointer to DragonTree's Document.
• Parents, Children, and possibly color & gene get/setters may need to be adjusted to the recent updates to DRG format. (whoops, thanks EMBTonkin!) \ Dragon default constructor certainly needs updated!

[EMBTonkin]

I fixed the getters and setters right away, so they should all be good.

I don't think it need a pointer to the Document because we can get the Document via it's node, so we just need to pass the Document into the constructor for completely new Dragon for it to make it's first Node.

[StrykeSlammerII]

( haha oops you did fic those--thanks! )

Oh, ok.... the adopt-a-node method should work when adding the new Dragon to DragonTree's Document, but passing the Document down does still make sense and would be a smidge more efficient.

[StrykeSlammerII]

• Updated the default Dragon constructor and it DOES require a Document to be passed in, now. (It doesn't save that though, so we're still using something like us.getDocument if we need the Document after construction.)
• Also updated it to the most recent changes to DRG format, so it should have the full XML tree again.

Other than Analysis.CanBreed( Dragon, Dragon ), what else would you like me to work on the next week or so?

[EMBTonkin]

After Analysis.CanBreed( Dragon, Dragon ), I think we will have finished most of the basic underlying stuff.
You could see if there's any more analysis functions you think would be useful, or you could join me on the UI side.
There's also the 'Not Quite Auto Add' feature, but I have to make sure it's within the Terms of Use before we go ahead with that. I'll let you know how that ends up.

[EMBTonkin]

I had a thought.
Here is my though: Instead of returning a Boolean (a data type, not the familiar). Analysis.CanBreed( Dragon, Dragon ) should return a list of common ancestors. That way, we can treat an empty list as true and a non empty list as false, and we can then use the non empty list to tell the user which dragon(s) are causing the common ancestor problem!

[StrykeSlammerII]

Oo, I think I like that. Though... would it be worth making that list it's own public method "CommonAncestors", and keep CanBreed as a boolean wrapper for it? ( returning a List to the question 'can these two breed?' seems kinda weird, to me )

Sorry about being MIA recently; I couldn't get a VM to work right somewhy, so I ended up swapping a fresh hard drive in and installing on that. Aside from there being no Win10 drivers for my soundcard, everything seems to be running correctly..... but it restricts my ability to taskswap if there's a background task I need a specific OS for, which is why I didn't want to do things this way :/ Ah well.

Also, my workshift is changing from evening to morning on Monday, so I have no idea how awake I'll be next week XD I'm expecting to get some work done on Sunday though!

[EMBTonkin]

Oo, I like your idea a lot too! So first we could get a boolean, and then if it's false we could get the list of common ancestors. Don't worry about being absent, I'm sure you've been doing important real life things when not struggling with your computer. I've only been able to do as much as I can because I have a really easy class scheduled this semester. I don't know if your change in work-shift is a good thing or a bad thing, but good luck with it!

[StrykeSlammerII]

finally got my text editor working again >_> and have a rough draft of CommonAncestors that still doesn't work right. I may get some more done Monday, or maybe not. weekend plans still in flux.

[EMBTonkin]

Don't sweat it. I've done nothing for the past two weeks. :/