On Wed, Apr 29, 2009 at 8:52 AM, Stephan Beal <sgb...@googlemail.com> wrote: > On 4/29/09, Robert Ledger <rob...@pytrash.co.uk> wrote: >> I was thinking that it might be a good idea to provide a parser >> interface so that custom wiki implementations could easily >> be integrated with core fossil. > ... >> The <wiki ..> tag could also be used to enable/disable wiki features >> such as my proposed <!-- --> pass through or "kkinnell"s <annotation> >> markup. > > i think that's a great idea. The ability to create a custom wiki > parser in JS might also be really interesting. The wiki interface > approach might also allow us to layer wiki parsers :).
Scary idea I'm currently considering: implementing fossil-scm sync [1] in javascript. The idea would be that you could then write arbitrarily complex code (held within fossil-scm) to do whatever, and use fossil-scm as back-end persistent storage, sort of along the lines of [2] - to quote (BTW is the author of this on this list? Can't find a name or contact info on the blog): "My current long-term goal (i.e. “fantasy”) is to, bit by bit, reimplement or refactor the Fossil source base into a generic application platform. That would allow really rich applications can be written in C/C++ for use as CGIs, standalone web servers, or console applications. Fossil’s engine is based largely on sqlite3, which means that such apps would have a significant amount of built-in serialization support." I may also be damaged by having worked for the group that develops IBM Lotus Notes for many years - Note's killer feature is IMHO replication and offline support for arbitrary applications written within its framework, and its architecture is very close to fossil-scm's (applications and their data are in database files called .nsf files; the client and server runtimes that use these .nsf files use almost exactly the same code; there are similar artifact ID / UUID concepts). There are several implementations of SHA1 in Javascript, so it looks doable. I am hampered by the fact that, so far, I've managed to avoid learning JavaScript. I have the book "Object Oriented Javascript" [3] on order, which looked like the best option for people interested in using JavaScript as a language (rather than only as a way to write client-side code to interface with a back-end server running something else). Something else I ran across lately that might be useful is PubTools [4]; it looks like it might be possible to use it to add full-text search to fossil-scm without having to change any fossil-scm code (not that I'd be against doing that; I just have very weak C skills, and not sure if this kind of functionality is within the scope of what TH1 is intended to do or not). [1] The Fossil Sync Protocol http://www.fossil-scm.org/index.html/doc/tip/www/sync.wiki [2] Back to C… (last paragraph) http://blog.s11n.net/?p=46 [3] Book Review: Object Oriented Javascript by Stoyan Stefanov http://aboutjustin.com/blog/?p=172 [4] PubTools: Easy JavaScript for Working With Gears http://code.google.com/p/gears-pubtools/ Cheers, -- Daniel JB Clark | Sys Admin, Free Software Foundation pobox.com/~dclark | http://www.fsf.org/about/staff#danny _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
