(anonymous guest) (logged out)

Copyright (C) by the contributors. Some rights reserved, license BY-SA.

Sponsored by the Wiki Symposium and the Nuveon GmbH.

 
View Attach Info

Add new attachment

Only authorized users are allowed to upload new attachments.

This page (revision-36) was last changed on 18-Sep-2008 16:30 by 86.121.181.221  

This page was created on 26-Feb-2007 20:41 by YvesPiguet

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Difference between version and

At line 37 added 19 lines
The canonical domain name for my university's faculty is {{{wmid.amu.edu.pl}}}. This is actually very short, as we use acronyms both for the unversity and the faculty name. Other universities/faculties domain names tend to be longer. A lot of development happens on universities: you'd then have {{{pl.edu.amu.wmid.macro.latex}}} (the "macro" keyword is needed to distinguish it from similar plugins, like {{{parser.latex}}}, {{{colorizer.latex}}} or {{{import.latex}}}).
I agree about the choice between possible clashes and nice and clean namespace, and also about the benefits that allow you to make central repositories, indexing, put important documentation online, etc. But I believe that the choice is not ours to make -- it's up to the developer.
If you want to start standarizing the extension names themselves, you open a Pandora box of internationalisation and localisation. On a Polish-only wiki, I will naturally want to use polish names for plugins. But domain names don't allow (by default) the use of characters like ą or ę. I believe that Chinese users would have even more trouble.
I like the idea of an "alt text", I think the same syntax that is used for images, {{{<<plugin paramaters|alt text>>}}} would be apropriate?
Of course, the alt text would be probably somehow distinguished from the normal text (tinted background? red text? frame around it?). I wonder what should be rendered when the plugin is missing and there is no alt text specified -- displaying the parameters might be too much (although they would usually give some hint on the intended contents), maybe just the name of the missing plugin?
Yves, I don't quite understand this sentence:
//If you accept name clashes, it isn't worth having it in the
standard, and it isn't worth having alternative contents because you can't be sure you won't map to your plugin
something else with the same name.//
Can you please elaborate?
-- RadomirDopieralski, 2007-02-27
Version Date Modified Size Author Changes ... Change note
36 18-Sep-2008 16:30 23.608 kB 86.121.181.221 to previous
35 07-Sep-2008 15:33 23.603 kB 86.121.181.74 to previous | to last
34 06-Sep-2008 00:50 21.895 kB RadomirDopieralski to previous | to last any example of plugin using >>?
33 31-Aug-2008 00:24 21.597 kB 86.121.181.74 to previous | to last
32 16-May-2008 17:31 20.927 kB Isonomia to previous | to last
31 28-Oct-2007 09:20 19.858 kB RadomirDopieralski to previous | to last restore
30 27-Oct-2007 21:46 19.87 kB 140.128.20.205 to previous | to last
29 26-Sep-2007 09:43 19.858 kB ChuckSmith to previous | to last restore
28 26-Sep-2007 01:25 19.902 kB 63.241.9.240 to previous | to last
27 26-Sep-2007 01:25 19.89 kB 195.246.155.219 to previous | to last
26 30-May-2007 17:04 19.858 kB RadomirDopieralski to previous | to last div & span
25 30-May-2007 16:05 19.637 kB YvesPiguet to previous | to last inline/block plugin
24 16-Apr-2007 01:10 19.204 kB 85.221.141.46 to previous | to last when to use text tags?
23 13-Apr-2007 22:53 18.408 kB 77.128.29.49 to previous | to last Balance design guidance
22 12-Apr-2007 01:53 18.033 kB 84.150.9.42 to previous | to last
21 11-Apr-2007 23:54 17.158 kB RadomirDopieralski to previous | to last reinvent the wheel
« This page (revision-36) was last changed on 18-Sep-2008 16:30 by 86.121.181.221