Loading...
 
Skip to main content

Development


You are viewing a reply to Development model for wiki syntax parser?

Re: Re: Development model for wiki syntax parser?

Thanks for the info, Damian! 😊

> You can already do 1, 2 and 3
>
> There is a recent forum topic for table formatting and alignment is dont with the div syntax.

I think I might have expressed myself less than sufficiently clearly. My point was development of basic wiki syntax, the 1--3 character codes, not the lengthy brace-name-parenthesis-brace-brace-name-brace plugin syntax.

So doing it with div syntax is in this perspective not a solution. The solution is to devise a minimal set of codes for wiki text that a large part of the users can agree is in sufficiently frequent use to be called basic. In this quest, it would seem to me to be sensible to consider consistency (cf. alignment: including all values of some dimension from which you include a value), frequently used web features (cf. linking to anchors within pages), and avoiding source text blowup for simple, often repeated constructs (cf. cell text formatting within tables).

> In 1.10 which is the latest development tiki there is a pluginable syntax parser. Its the same one thats used currently in TikiPro/BitWeaver, so if you want this function now, give BitWeaver a try: http://www.bitweaver.orgQuestion

Unfortunately, I did not succeed within 15 minutes of surfing that site (even after registering and doing a test page edit) to find any description of this wonderful parser.😑

Finally, I notice that my main question has not been commented or answered by anyone yet: What is the development decision process like for the wiki syntax?
Put slightly differently, is the basic wiki syntax freezed forever, relegating all and any useful and sensible future enhancements to a non-default-enabled plugin or modification?

Respectfully,

— Arne