IntroductionTreeDroid can do more than it's currently designed to; since the base idea and even the schema are both fairly simple, there's lots of room to expand and improve the tool. Planned Upcoming FeaturesThese are features or ideas that are actually in the works. Undo FeatureIt thoroughly sucks to accidentally delete an entire branch and all its leaves, since that's a lot of data to re-enter. - Multi-level undo?
- The "lazy" way to do this is to just take snapshots of the whole database, though it's unclear at the moment whether SQLite (or Android) supports this in any reasonably easy fashion. This makes the app's data usage unnecessarily high, too -- make a copy of a 50k database for a 95-byte change?
- The non-lazy way to do this is to store the "undo" version of every query executed for later playback if desired, stored in a separate table, with an option to purge undo data if it gets too big/unwieldy. This could take awhile to build.
IdeasThese are (potentially) good ideas for TreeDroid that haven't been worked on yet. Cloud StorageThrough Google App Engine, there's a processing and storage cloud available, providing high availability and good performance, that could be used to store a user's trees. This could either function similarly to Android's built-in calendar and mail apps (where data is kept in sync in the background, with no user interaction) or it could be a simpler, manual update function (where the user must deliberately tell the app to save the current database to the cloud, or retrieve it from the cloud). This developer is more inclined to make the feature fully automated. - Should this include version control or undo history?
- Should the cloud feature just be a storage medium for TreeDroid on the Android phone, or should it also include an application to work with the data online from the browser (i.e. an online outliner)?
XML Import/ExportAbility to export the tree to the SD card as an XML file, and to import an XML file from the SD card into the tree (either replacing the data in the tree, or merging the imported tree with the current one, or adding the imported tree's nodes as a branch of the existing one). - Perhaps this is the storage method the Cloud Storage feature uses? Might make version control easier.
- Perhaps this might also be useful for implementing Undo?
|
Sign in to add a comment
You might look into working with the developer of Shadow Plan, which is a Palm app which does much the same thing. If you could put your heads together and make a G1 outliner which syncs to the desktop (possibly using Bonjour, as SplashID does), that would be fantastic. I would pay for that.
Hi. If this works, I'd pay for it. If you manage to add mind mapping to basic outlining, even better! - anything useful to be learned from Freemind? Good luck!
I would pay for this too!