> What were the reason for dropping the TiddlyWeb route for this > purpose?
The Django framework Saq uses here makes a lot of things very simple that we would otherwise need to write code for. However, Django also provides a RESTful API - which means that an intrepid developer could write a TiddlyWiki-based client providing an alternative front-end for the data provided by TiddlyHub. One could also write a TiddlyWeb store for this purpose. > if Fred with the support of BT wasn't able to - what could have > been then the reasons There were a number of factors to this. In hindsight, I have to admit I'd allowed myself to get pulled in different directions. The most important one was was getting more involved with TiddlyWeb development, which at the time was still in alpha stage - which also meant that, back then, it didn't yet do everything the Plugin Library needed it to. Either way, I think we're at a good point now, and this iteration of TiddlyHub certainly benefited a lot from the expertise (both conceptually and in terms of code) gained from the earlier efforts. -- F. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "TiddlyWiki" group. To post to this group, send email to TiddlyWiki@googlegroups.com To unsubscribe from this group, send email to tiddlywiki+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/TiddlyWiki?hl=en -~----------~----~----~----~------~----~------~--~---
