Bob, You might have considered this, but if you are dynamically computing the scoring, you could try a cached-value approach, where you cache the calculation of the score, and some operations (adjusting inputs, reparenting, modifying weighting of parent) would invalidate the calculation. If you are lazy about recalculating the score, then it would be no slower than now on display (with a speedup after being computed once), for some additional cost when you have to invalidate the tree (when the root is modified or reparented).
Of course, this is a space-for-time tradeoff, and the devices are memory-constrained. -Justin -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of scoobie Sent: Thursday, July 16, 2009 2:42 PM To: MyLifeOrganized Subject: [MLO] Re: Computed-Score Priority and Start Dates Bob, What's your take on being able to do all this in an iphone sized processor and screen? Do you think its possible? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MyLifeOrganized" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [email protected] For more options, visit this group at http://groups.google.com/group/myLifeOrganized?hl=en -~----------~----~----~----~------~----~------~--~---
