There's a groupware project for OOo IIRC. Perhaps all of this could be a 'view' in that app (kind of like 'queries' is a view in Base). As it might be used for collaboration eventually, this might be good to have in that app. However that app shouldn't be limited to just the server/client collaboration model, but should be able to be used stand-alone. I think that this app could be based on Base, as I've mentioned before, only replacing all of the views and adding somemore for the functionality we need. I don't know what's being planned for the groupware project, but this might be a great path to follow.
Another idea: it'd be great to be able to attach 'sticky notes' to a document, and have that sticky note stored not only in the document (like say a Writer or a Calc file) but also in this groupware system, automatically categorized, with the option to change where it is. Then you could make 'sticky note' todos and go back later to see where you left todo notes in all your documents. Pretty cool huh? Another idea: It'd be awesome if that groupware project also integrated with Thunderbird/Sunbird (Lightning) so that you could view this todo/sticky notes document in Lightning, as well as viewing it in OOo. An extension in Lightning, and an UNO component in OOo to integrate the two. We should also create some kind of API so that other people can create components/extensions for their PIM apps to collaborate with OOo. This needs to be modular so that people can come up with the solution that works for them. My mind is spinning. Cool. I like this already. :D Thanks, Jacob On Wed, 16 Mar 2005 16:32:19 +1100, Simon Lilburn <[EMAIL PROTECTED]> wrote: > Simon Lilburn wrote: > > > - Internal linking would be fantastic (say, like a Wiki). > > - An idea for the distant future would be the ability to export this > > to a Wiki system or have it collaborate with a Wiki that is online > > (i.e, check it out). But that's just a pipe-dream and might be a > > distant objective. > > - I know a little about XML, and it seems quite suitable that a > > tree-based document could be saved in XML quite easily; so keeping > > that format as the native one for said note-taking application (like > > Writer/OOo already is). [Could this then also be a part of the OASIS > > specification?] > > Sorry, I was a little unclear (chalk it up to shocking grammar) on these > points. Firstly, allowing for hyperlinking between notes in other tree > nodes and other tabs (or even documents in other OOo applications) would > add another dimension of organization/cross-referencing to those notes > which already have a large amount of very structured information. > The second point there was another suggestion that could be considered > for the future would be to export the note documents (i.e., a file with > several tabs and in each tab a large tree full of nodes) to an online > Wiki system where all the notes could be viewed and edited whilst the > structure remains intact. If this was considered, it might also be worth > considering allowing the program to (at a later date) download the file > again to bring it back into the note-taking application on the desktop > (thereby having a "check-out" function). This could aid in collaboration > of notes between a large group of people, say developers working on a > large software project who need to have documentation on each section of > the program. > Thirdly, I was trying (by the looks of it, poorly) to say that these > large note filled documents could be saved as XML which would increase > portability and, if it was accepted, could then become a part of the > OASIS standards specification for XML documents. > > Note to self: read emails more carefully before sending in future. Hope > that clears some ideas up. > > - Simon. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
