Re: [cowiki-dev] Extension to coWiki text formatting
Sy <[email protected]>
| Newsgroups | gmane.comp.php.cowiki.devel |
|---|---|
| Message-ID | <[email protected]> |
Ok.. it took me a while to get a response put together..
> Actually, I prefer [[]] style as that is consistent with other wikis. I have found that Rubyists use (()) in there documentation tool, and Kai and dtg seem to strongly prefer it. I'd like to choose one or the other. When there are too many ways of accomplishing the same thing, a user will start to ask "What is the difference? When should I use one over the other?"
I prever square brackets as well, however Daniel is correct in saying
that we are choosing to exclude users by not allowing rounded
brackets. I I would be willing to accept rounded brackets as input
just to have them converted to square brackets. i.e. put a little
"convert double-brackets to double square-brackets" checkbox in the
edit box.
> >* Tables: I really like the new style of table that was being coded.
> >I think I understand your proposal, but I need an example.
>
>
> I didn't understand it and I couldn't *read* it at all! :-)
>
> ^ Heading 1 ^ Heading 2 ^ <left>Heading 3</left> ^
> | cell A1 | cell A2 | cell A3 |
> | <left>cell B1</left> | <left>cell B2</left>| <left>cell B3</left>|
> | cell C1 | cell C2 | cell C3 |
That's nowhere near as easy as:
{|
|-
| The first row
| The first row, second column
|-
| rowspan="2" |
| The second row
|}
Notice how each element is put on its own line? It makes it vastly
easier to visualise and update when working with the source.
We either need to go with a standard or make something that is the
best of all worlds. What about something like:
| cell A1 | cell A2 | cell A3 |
|-
| <left>cell B1</left> | <left>cell B2</left>| <left>cell B3</left>|
|-
| cell C1 | cell C2 | cell C3 |
* I assume that the heading is optional.
Now I could take that and convert it like so:
| cell A1
| cell A2
| cell A3
|-
| <left>cell B1</left>
| <left>cell B2</left>
| <left>cell B3</left>
|-
| cell C1
| cell C2
| cell C3
* I removed trailing pipes.
Now looking at that, the only difference between this and the table
syntax being thrown around earlier would be the beginning and ending
{| and |}
This method allows users to put in longer strings and still maintain
readability.
>>* Language processing instructions: Shorten to <html>, <php>, etc? or
>>if not, also allow "lang-html" etc..
>
>
> NACK. In the internal XML it could be represented this way, but the <? ?> syntax is a community standard that will be recognized for what it is doing, and it draws a clear distinction between data and instruction. Novice users will not be exposed to it, so I don't think their reaction to it is significant.
I think you misunderstood. I mean could the <language-html> etc tags
be shortened to make them easier to type?
> The other hole is a time-bomb-- A privileged user creates a malicious page and they are then demoted to a lesser level. Their malicious page still exists and won't be caught on display.
This is why MediaWiki allows people to see all the changes done by a
particular IP or user.. so they can check other pages which may have
been altered by them. This is why I would argue a "mass rollback"
feature, to target one user and rollback any of their edits, such that
their edit was the most recent one.
> PS-- I've completely left out definition style lists, which we should probably do. Also some wikis have a way of doing footnotes (again involving (())) that is nice to have.
Footnotes, as done by MediaWiki, work very well. They are done via a
funky variable-enabled template.
To see them in use, visit:
http://sysy.homeip.net/mw/index.php/Sandbox
Or to see the templates, visit:
http://sysy.homeip.net/mw/index.php/Template:Fn
http://sysy.homeip.net/mw/index.php/Template:Fnb
I have no idea how it works technically.. bt it's remarkably simple to
use.. and appears to just leverage on their existing
variable/templating technology.
Regarding PHP as a markup language.
I can see this kind of functionality used for, say, making tutorials.
Of note, there is one wiki which allows inline Ruby code.. and the
ruby interpreter can be set to a super-safe mode (no disk access, and
such) which provides the security needed. So the user is provided
some on-the-fly calculated Ruby code, and they can freely write their
own code and see its output.