Re: OT: wiki engine architecture (was: $1,000 prize for Perl 6 Wiki written in Perl 6)

2006-06-08 Thread Matt Todd
I would recommend using a templating system as opposed to having calls to include files in numerous pages. Even though it's minimal, it's still duplication, and it can get rather messy. I know that some people don't know about or don't like it, but I would recommend setting things up in a Model-V

Re: OT: wiki engine architecture (was: $1,000 prize for Perl 6 Wiki written in Perl 6)

2006-06-08 Thread Udo Güngerich
Michael Mathews wrote: > This is the smartest suggestion I've yet seen on the subject, but, not > being all *that* familiar with Perl6 Grammars (aren't they something > like contextually-smart regexes?), can anyone give an example of Perl > 6 code that uses grammars and can express some wiki-forma

Re: OT: wiki engine architecture (was: $1,000 prize for Perl 6 Wiki written in Perl 6)

2006-06-08 Thread Michael Mathews
On 07/06/06, A. Pagaltzis <[EMAIL PROTECTED]> wrote: Let's use Perl 6 Grammars to define syntaxes. We are just about to get this mindblowingly awesome tool for parsing; why insist on tieing our feet together and having to hop around like that? This is the smartest suggestion I've yet seen on th

OT: wiki engine architecture (was: $1,000 prize for Perl 6 Wiki written in Perl 6)

2006-06-07 Thread A. Pagaltzis
* 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