From: Steve W. <sw...@pa...> - 2002-02-21 16:51:01
|
Finally, we should consider whether this is just programmer gold plating. I think we should have three good reasons to have comment blocks in Wiki markup. Oh, and to muddy the waters further (and continue to reinvent HTML), comments could optionally render as HTML comments on the other end. yuck ~swain Lawrence Akka wrote: > At 16:37 21/02/2002, you wrote: > >> Lawrence Akka said: >> > Anyway, people should not have to use <pre> for code >> > blocks if they don't want to (even if it *is* a good idea). >> >> If we adopt the new markup they will have to. Otherwise their >> code will get run together in one big paragraph. > > > Oh yes. I'd forgotten that. > > > > >> > Also, whilst I'm on this rant, why should comments not be multiline? >> > Would it be useful to be able to comment out large blocks of wikitext, >> > without actually deleting it? They could be picked up by the block >> > parser, and the inline parser, couldn't they? >> >> As long as we make them either block-level or inline-level the parsers >> will be able to deal with them fairly easily. (I.e. if we make them >> inline ((so that you can do this)), then they will not be allowed to >> span paragraphs.) > > > What I had in mind was the > {{ability to > do this }} > sort of {{thing}} > > > >> I'm not sure we want to make it too easy to comment large blocks of >> text anyway. Comments as instructions to the editor are good, I >> think. Comments as a place to store work in progress (or whatever) >> are a bad idea (on a wiki). Either just show the work in progress, >> or put it on it's own page.... > > > Actually, I think I agree with that (happens sometimes, you know) > > L > > > _______________________________________________ > Phpwiki-talk mailing list > Php...@li... > https://lists.sourceforge.net/lists/listinfo/phpwiki-talk > > > |