Ye. Got an idea already for how to save/load configuration data in some generic way. For this view, the config syntax will be:
- Code: Select all
Default sets the default width of a block, use spell id : width to customize. The hard work is to add a generic config loader, but a table like
id, type, key1, key2, key3, key4, title, description, data, owner, permissions (755?), flags
can be used to save this, and things like saved expressions (with key1=boss, key2=mode bits, key3=tag, key4=group for db-based filtering).
Description will probably be formatted with a variant on Textile (same for comments on stories @ homepage etc), still working on the lexer / parser for that. The default Textile ones generate tagsoup like <em><strong>invalid!</em></strong> and are a bit uh, regex-y.
Okay, an "everything is allowed, if not valid, display as text" language is not strict LL(1) and ANTLR really chokes on it, but a handcrafted LL(2) parser handles most things with only a few explicit greedy rules. Even llnextgen
could probably handle it...
Oh well, there's a reason why no-one produced a proper parser for wikis yet.
<3 hunting down the annoying export bug, so much more time left for new stuff now.