On 11 January 2011 17:45, Stephan Beal <[email protected]> wrote:
> On Tue, Jan 11, 2011 at 1:44 PM, David Bovill <[email protected]> wrote: > >> In my case I'd like to be able to keep track of script elements, handlers, >> functions, methods, classes etc and not the files they happen to be in....in >> a db is much the same, but I am wandering how I can use the db to store >> metadata such as the files the function is found in, so that I can link the >> script elements to these files. >> > > IIRC, one user recently posted that he [ab]used the wiki in that manner. He > stored some metadata in wiki pages and fished it out from there. > Would it not be possible to use the tag system to add metadata? If your IDE interface to DVCSs is shell/command based, fossil shouldn't pose > any particular problems for you. However, fossil is a monolithic > application, as opposed to a library with a CLI front-end, which makes it > essentially impossible to write anything _except_ shell-based add-ons for > it. Two or three years ago (has it been that long already!?!?!?) i looked > very closely at how to refactor fossil as a library+app, but by that point > fossil was already so large that the effort involved would have been > tremendous (and fossil has always evolved quickly, so it would not only be a > big target, but a fast-moving one). Such a refactor/rewrite would, however, > make things like GUIs much easier to write. > Yes - it would be nice, but CLI access is just fine as long as it works the same on all platforms. There are two specific questions before I dive in: 1. Is there a db schema 2. How can I search the wiki 3. Where are the sqlite files stored 4. Is it OK to add fields to the db in a hybrid app - all is it likely something will get clobbered :)
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
