I don't think the PB team is interested in this yet. However, time passing they will come to realize the necessity behind such a step. Because let's face it: it can't be that hard to publish an API that does
open, close, addNode(guid, type), findThoughtBy(name,guid,attachement,tag), addAttachmentTo(guid), getLinks(giud), addTag, addTagTo(), getNotes(guid), ... - the basics off the top of my head -
from any location on the planet that has internet access and that works on a running and a non-running instance of PB (esp. the latter case should be easy and is what i am looking into right now if at all possible).
I dislike software that can't attach to anything else. And that in the age of orchestrating one's information and application heaven (or hell). Import/ export stuff is so 90s to quote s.o. close to me.
Or at least: provide us with an xml-structure that is "live" and that i don't have to export every step of the way... An xml-export takes about 5min on one of my brains and don't ask about webbrain... (ok, slow netbook, but still).
The reason i was looking into H2-access (and i haven't stopped) is that i need to be able to take my data along wherever need be. I still am using PB as my main information-storage application and it runs whenever my computer is running. I've also started using it as a calendar reminder for the non-critical stuff and i use it extensively w/ regard to GTD: next action, now, waitingFor etc. Now, when i want the latest data available on the road, i have to export the xml to a server (or create a webbrain that takes forever) and query it through a web interface. How eh, degenerate is that? Instead, i could simply save a complex hsql query (for that PB is no good yet) and run it with a click on a link on an up2date version of the DB as it it on my harddrive/... and visualize that via wap/ html on my cell.
I also want to be able to input stuff into the brain w/o having it in front of me (eg from my cell). To do so, i had to go the great length of creating a mail2pbxml component so that when i come home at night i can import the xml from there into the brain (see one of my threads in this forum). If i forget to import or if stuff changed in the meantime, well, more sorting work and more inconsistencies. Instead i just push the info via hsql onto my "sleeping beauty of a brain.data.db"...
On uservoice i see all those requests and i am sure that most of them are smart ideas. Most of these come down to this: give potential developers the tools at hand to make the software better by e.g. writing plugins or through the use of an API manipulating thoughts. I am not saying to make it open source though that would be fantastic. What i'm asking is simply: give me my data back. I know it's in my PB and i can export it/ etc. BUT: When it takes too much effort to do so, that software has to go. And that would be a shame because PB fills precisely the void between good visual access to your data and sth. like personal datawarehousing. While i think there are better tools out there to focus on issues/ creating overviews on stuff, it is the best i know for accessing data quickly and linking stuff that belongs together easily.
Ask me what i would do with such access? Wait for PB6beta, check out the meta-data functionality if it's included (typed nodes etc) and tap into that potential to cross-link what i'm doing on my pc while PB is running (open apps, open files, ...) as well as what my cell data offers (gps, ...) with the data that's inside PB. I want to be able to add a thought in PB (let's say "milk" underneath "groceries") and my cell to go off reqall-style when I'm near a grocery store that is cross-ref'd in PB as carrying milk. Or i want a picture taken on my cell to appear in PB and that is automatically linked to the city/ person i'm at w/i PB. Or i want PB to automagically open the thought of a person i work with when the person calls me on my phone in realtime (or pinning it for a couple of seconds, or updating a "CONTEXT"-node, yay).
Ultimately, i want fragmentation to stop. Information should flow freely and not be staggering like a drunken man through too small a door...
Oh gosh, another one of those rants where i find no end. Well, i'm passionate about this software and have been from early natrificial days on. So i hope you'll excuse me (and not censure me as done in the past).
I guess it would have been more productive to list all api functions that we would like to see, hehe. Or coming back to H2: getting an answer as to whether pursuing access on the db would be considered illegal by PB. Anyone from PB on that matter?
Anyway, looking forward to you ideas. dinner awaits. Sorry for the long post.