* Thomas Wittek <[EMAIL PROTECTED]> [2006-06-07 15:05]:
> I guess that the architecture/design for such a flexible piece
> of software will be relatively complex.
All I can think of is “YAGNI”.
Defining a syntax in a configuration file doesn’t strike me as a
particularly smart move. You will eith
Damn, forgot the link.
Thomas Wittek schrieb:
> That's mainly what I did as stated in my first post[1]. [...]
[1]:
news://nntp.perl.org:119/[EMAIL PROTECTED]
Juerd schrieb:
> * Markdown does not have tables.
> * Textile does not have paragraphs in table cells.
> * Kwiki does not have paragraphs in table cells.
>
> Unless someone comes up with another way to do side-by-side layouts
> (extremely useful for showcasing differences between Perl 5 and Perl 6
Udo Güngerich schrieb:
> Thomas Wittek wrote:
>> Unfortunately you probably have to throw away/heavily modify earlier
>> increments, if you add features like a flexible syntax, which will need
>> a different internal infrastructure.
>
> Well, if object-oriented design has any advantage at all, her
Hi,
I have never understand this "my wiki syntax is better than yours"
thing. It's like "my templateing engine is better than yours".
I feel like which should have "wiki.conf" with :
...
syntaxhandler = SuperbPerl6Wiki::Syntax::MediaKwikiMikiBiky
...
That shall please everyone. :)
- Fagzal
