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

Juerd, My mistake: I misunderstood what you were saying (probably due to haste). But really, then, there are alternatives to using tables, such as DIVs, as well as simply modifying the parsing step to also parse for this special case in addition to Textile or what-have-you. I guess if I said an

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

I also agree that Object Oriented Design would work wonderfully well here. The key here is prototyping its shape and then filling in the details once it has taken this shape. I like the term 'messages' for methods because it reminds me that the objects must send requests, forms of communication,

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

* Ben Morrow <[EMAIL PROTECTED]> [2006-06-07 01:25]: > Preferably something rst-like? I was wondering why noone had proposed Kwid yet. Doesn’t anyone like it? Regards, -- Aristotle Pagaltzis //

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 > backe

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

Quoth [EMAIL PROTECTED] (Juerd): > > * 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 bet

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

Matt Todd skribis 2006-06-06 16:46 (-0400): > There are alternatives to using tables for side-by-side using > paragraphs. Simply having one cell for each line, for instance, allows > for highlighting green the added lines and red the removed ones, etc. Visually pleasing, but technically incorrect,

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 p

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

There are alternatives to using tables for side-by-side using paragraphs. Simply having one cell for each line, for instance, allows for highlighting green the added lines and red the removed ones, etc. Also realize that it is not necessarily the duty of Textile (et al) to handle that aspect beyo

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 althou

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

* 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), all of these formats ar

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

On Tue, 2006-06-06 at 10:59 -0400, Matt Todd wrote: > I particularly like the syntax of Textile or even Markdown (preferring > the former). In Ruby-land, these exist as RedCloth and BlueCloth. I > understand porting isn't fun, but I think that this is a viable > option, if not a great choice. Fo

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

Iraq invasion indeed wait, shouldn't go there. I particularly like the syntax of Textile or even Markdown (preferring the former). In Ruby-land, these exist as RedCloth and BlueCloth. I understand porting isn't fun, but I think that this is a viable option, if not a great choice. Not that th

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

> Ask Bj�rn Hansen <[EMAIL PROTECTED]> writes: > > Woah, we are getting really far away from talking about perl6 > > here... > > Kind of a usenet law or corollary? "Every discussion about wikis ends You're being a bit optimistic there, aren't you? The only way you'd end a my-wiki-is-better-than-y

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

Udo Güngerich schrieb: > Why not doing a wiki system that does NOT have a fix syntax but rather > allows defining its syntax rules in e.g. YAML and thus being entirely > flexible? > [..] > It should have a proper user/groups system as well... > [..] > Why not give the wiki a web service API [..] G

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

Ask Bjørn Hansen <[EMAIL PROTECTED]> writes: > Woah, we are getting really far away from talking about perl6 > here... Kind of a usenet law or corollary? "Every discussion about wikis ends in a discussion about the best wiki syntax." Steffen -- Steffen Schwigon <[EMAIL PROTECTED]> Dresden Perl M

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

Thomas Wittek wrote: >> Noone other than Mediawiki uses the Mediawiki syntax. I posit >> that the reason is that that syntax blows chunks. > > I have to agree. 'bold and italic' is definitely not what I > understand as an intuitive syntax. Hi everyone, I'd like to mention that the med