On Wed, 2010-09-15 at 16:25 +0300, Vlad Dragu wrote: > [Vlad] this is my feeling also. As we add additional features to the > code, it becomes harder and more time consuming to change the > structure to OO and data objects. > As far as estimating how much time it will take, I think in 2 days I > can implement the OO code for the user / session. For data objects I'm > not so sure, but my guess is that once I implement it for a particular > case, it will be easy to replicate throughout the code. So, maybe a > day for the first one and another day or two for the rest of them.
Sounds like the right way to go - maybe we could make this the focus of alpha2.2. This would ensure you would have a good basis for developing future releases. Did you count converting all the code in objects, or just the user/session? What would remain to implement in objects afterwards? To avoid facing the same issue in the future, you'll want to have a solid base OO structure at the end. Maybe it would be worth trying to quickly model the general structure with a simple UML schema, to tackle potential issues with the structure before starting to alter the code (not the full-fledged UML btw, just the elements on this page would do it: http://atlas.kennesaw.edu/~dbraun/csis4650/A&D/UML_tutorial/class.htm ). If we make this alpha2.2, you could work on the modeling this Friday, then I would review and modify it if necessary over the week-end, and then you would have from Monday to Thursday to implement the structure. What do you think? David, what do you think too? Making this the alpha2.2 would be useful from a technical standpoint, and it would also give us a few more days to polish the Sims-like leveling. But I don't know what you have in mind to finish alpha2.1 and for alpha2.2. Especially because the completion of alpha2.0 and 2.1 depend on Ajaxim, and it doesn't look like it's going to get completed quickly. > > 1. Remove the action from the queue (to prevent the user to > > trigger > > the same action twice if the method takes some time to be > > executed) > > 2. Call the method > > 3. Look at the method return value - by default do nothing, if > > false re-add the action to the queue (with the same flags and > > everything - so you probably want to store the action details > > before removing it from the queue in 1.) > > > > Or am I missing something? > [Vlad] I will give it a try. I think it will work Perfect! Thanks for everything, Xavier. _______________________________________________ Hackit Bar mailing list - [email protected] Wiki: http://community.hackit.cx/ List: http://community.hackit.cx/ml/ Forum: http://community.hackit.cx/forum/ Ideas: http://community.hackit.cx/ideas/ IRC: irc://irc.freenode.net/#politis
