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

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 the

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

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

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

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

Re: $1,000 prize for Perl 6 Wiki written in Perl 6

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),

Re: $1,000 prize for Perl 6 Wiki written in Perl 6

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]

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

* 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 either

OT: my wiki syntax is better than yours (was: $1,000 prize for Perl 6 Wiki written in Perl 6)

* Juerd [EMAIL PROTECTED] [2006-06-06 17:50]: side-by-side layouts (extremely useful for showcasing differences between Perl 5 and Perl 6) Good point. * Markdown does not have tables. But it lets you embed verbatim HTML as an escape hatch for constructs that it does not model, and although

Re: OT: my wiki syntax is better than yours (was: $1,000 prize for Perl 6 Wiki written in Perl 6)

Also realize that it is not necessarily the duty of Textile (et al) to handle that aspect beyond text formatting. A diff or history-revision view goes beyond the context of the tool. I don't think Juerd was talking about tables for the purposes of showing version diffs, but so you can give

Re: $1,000 prize for Perl 6 Wiki written in Perl 6

Thomas Wittek wrote: Good ideas. But maybe we should start a bit smaller ;) It might be a good idea to create a list of features separated in several increments (releases) to get a running system early. Absolutely. I could imagine increments like Parsing/Converting, Storage

Re: $1,000 prize for Perl 6 Wiki written in Perl 6

* Thomas Wittek [EMAIL PROTECTED] [2006-06-03 22:30]: Interestingly it is very similar to Markdown although I never heard about it before :) Hmm, it doesn’t look similar at all to me? Not even superficially similar, but most importantly, it looks line-based. Markdown is block-based. If you want

Re: $1,000 prize for Perl 6 Wiki written in Perl 6

On Jun 1, 2006, at 6:45, Ovid wrote: In any event, if you can come up with a solid set of contest rules, TPF can consider whether or not we can officially run the contest. It sounds like a nice idea, I just don't know what's involved. I wouldn't claim to entirely comprehend the rules,

Re: $1,000 prize for Perl 6 Wiki written in Perl 6

Hi, Hi Conrad, I run the grant committee for the Perl Foundation and I sit on the steering committee, so I suppose I can discuss your proposal (there are some other TPF folk here, too, so that's why this is a public email). Also, the following stuff is just off the top of my head and is in

Re: $1,000 prize for Perl 6 Wiki written in Perl 6

Darren Duncan skribis 2006-05-28 14:37 (-0700): For one thing, I'm assuming that a prize-qualifying solution won't be able to link-in legacy Perl 5 modules using Pugs' use perl5:Foo syntax; to do so would look bad if we are wanting to show off a Wiki solution using the NEW technology. I'm

Re: $1,000 prize for Perl 6 Wiki written in Perl 6

I'm wondering about some implementation logistics. For one thing, I'm assuming that a prize-qualifying solution won't be able to link-in legacy Perl 5 modules using Pugs' use perl5:Foo syntax; to do so would look bad if we are wanting to show off a Wiki solution using the NEW technology.

RE: $1,000 prize for Perl 6 Wiki written in Perl 6

-Original Message- From: Amir E. Aharoni [mailto:[EMAIL PROTECTED] Sent: Sunday, May 28, 2006 1:54 PM [...] It's funny - i was the first one who proposed the wiki idea and i didn't think that it will go so far (1000$$$). If you ask me, this wiki should be done ASAP in Media-Wiki.