On Jun 25, 2:05 pm, FND <[email protected]> wrote: > However, the problem I see here is being tied to the TiddlyWiki > universe. Your approach - leveraging sections and slices - requires > parsing of the tiddler body, and thus a certain awareness of its > structure. This is problematic for a generic system like TiddlyWeb, > which is designed to be content-agnostic.
This isn't necessarily that much of a problem. If the content needs to appear in a particular form in the TiddlyWiki, then the server-side just needs to make sure that it properly processes to that form when generating the TiddlyWiki. The storage system can continue to do whatever it likes. Serializing to a particular form on the server is not too terribly complicated. What becomes complicated is making sure that the TiddlyWiki does the right form of PUT to save stuff back to the server. That complexity can be held in the client (where it ought to be for sake of scalability and tweakability). So really, it is a matter, as we've been saying, of agreement on some format, any format really, that is satisfactory for the various client side use cases and then documenting it so server-sides can serialize to it. -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
