Mario > > I'm thinking about it, but at the moment I didn't have a good idea. The > main concern is content "exchangeability" ... A well defined wikitext > syntax guaranties readability with federated wikis. .. There is still some > hope :) > > ยป : <classnames> >> i : <classnames> >> ii : <classnames> >> asdf : <classnames> >> > > This would mean I need to create a completely new parser. ... ATM I'm > using the default functions, that are already part of the core and battle > tested. > > >> (or even style definitinos directly instead of the classnames) >> > > ONOooooo... style is hardcoded and will always win. So document > consistency will be broken completely. >
I believe all we are talking about here is a dictionary of custom or standard classes one may use in the wiki. they are .classnames the user build or takes from a small list, Either to lookup and type or apply with an Editor toolbar button. No parsing required in the greater tiddlywiki, it will just work out of the box. I will have a look at building it to demo. Regards Tony -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/2c97e13b-3f1c-4a19-84a2-b95b7acf1327n%40googlegroups.com.
