could you give an example?
----- Original Message -----
From: David Gerard <dgerard(a)gmail.com>
To: MediaWiki announcements and site admin list
<mediawiki-l(a)lists.wikimedia.org>
Date: Mon, 31 May 2010 23:41:59 +0100
Subject: Re: [Mediawiki-l] [Wikitech-l] a wysiwyg editor for wikipedia?
> On 31 May 2010 23:37, Steve VanSlyck <s.vanslyck(a)spamcop.net> wrote:
>
> >> (b) doesn't cope very well with the weirdest stuff done on English
> >> Wikipedia, where wikitext is tortured horribly to squeeze out every
> >> possible emergent side-effect for editor's use.
>
> > ?????
>
>
> en:wp not only uses ridiculous contortions of wikitext routinely, it
> seems to iteratively explore the furthest reaches of stuff that the
> parser just *happens* to do then turn them into normal parts of
> editing. That's why new editors hit "edit" on en:wp, are confronted
> with what may as well be an uneditable binary and run away never to
> hit "edit" again [*].
>
>
> - d.
>
> [*] possibly a slight exaggeration
>
> _______________________________________________
> MediaWiki-l mailing list
> MediaWiki-l(a)lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/mediawiki-l
>
On 31 May 2010 23:50, Angela <beesley(a)gmail.com> wrote:
>> The default editor on new wikia.com wikis is WYSIWYG-only. This works
>> tolerably well (a bit buggy, but actively worked on).
> It's not WYSIWYG only. You can switch between that and regular
> wikitext whilst you're on the edit page using the "source" button, or
> you can select which you want to use in your preferences. A new
> version was released a couple of weeks ago, so many of the older bugs
> are now resolved. There are some new ones of course, but it's
> improving all the time. :)
:-D
How installable and workable is this on, say, any random work intranet
with a fairly generic MW 1.16 installation? I may give it a go at work
...
[cc to mediawiki-l]
- d.
> (b) doesn't cope very well with the weirdest stuff done on English
> Wikipedia, where wikitext is tortured horribly to squeeze out every
> possible emergent side-effect for editor's use.
?????
On 31 May 2010 22:53, William Le Ferrand <william(a)corefarm.com> wrote:
> I've started to develop a simple wysiwyg editor that could be useful to
> wikipedia. Basically the editor gets the wiki code from wikipedai and builds
> the html on client side. Then you can edit the html code as you can imagine
> and when you are done another script converts the html back to wiki code.
>There is a simple demo here :
>http://www.corefarm.com:8080/wysiwyg?article=Open_innovation . You can try
>other pages from http://www.corefarm.com:8080/ (type the article name).
> You comments are welcomed!
What you're working on is a *hard* problem a lot of people have
attempted, with varying success. There's been some discussion of this
of late on mediawiki-l.
The default editor on new wikia.com wikis is WYSIWYG-only. This works
tolerably well (a bit buggy, but actively worked on).
The common WYSIWYG solution for MediaWiki is FCKeditor, which works
*almost* pretty well but:
(a) falls down badly when you try to mix WYSIWYG editing with wikitext
editing and chews up the wikitext
(b) doesn't cope very well with the weirdest stuff done on English
Wikipedia, where wikitext is tortured horribly to squeeze out every
possible emergent side-effect for editor's use
(c) is not actually being worked on at the moment. (Though one
mediawiki-l contributor says he's been using it to good effect on his
work intranet and is seeking permission to release back his changes
under GPL.)
http://mediawiki.fckeditor.net/http://www.mediawiki.org/wiki/Extension:FCKeditor_%28Official%29
FCK+MediaWiki discussion recently:
http://lists.wikimedia.org/pipermail/mediawiki-l/2010-May/thread.html#33896http://lists.wikimedia.org/pipermail/mediawiki-l/2010-May/thread.html#34061
You may care to have a look at FCKeditor+MediaWiki and see if you've
just reinvented the wheel and can help get that up to scratch. Or,
alternately, if your approach is different enough and better enough to
pursue nevertheless ;-)
- d.
Maps <http://mapping.referata.com/wiki/Maps> [0] and Semantic
Maps<http://mapping.referata.com/wiki/Semantic_Maps>[1] 0.6 are now
available for download [2].
This is a big update, including a lot of new features, bug fixes, security
patches, and most of all, internal improvements, making both extensions more
modular and extendible (these changes are not covered here, see the relevant
change logs for more info). It is also the first release of Semantic Maps
that requires you to run the SMW update script, as it requires a new table
layout to store coordinates (more info on
this<http://mapping.referata.com/wiki/Semantic_Maps#Upgrading_to_0.6>
).
The important new features are:
- Maps now supports real coordinate parsing and formatting, which allows
you to input coordinates in any of the supported notations at any point in
the extension, and can also request any output to be in the notation of your
choice. This means you can now choose what format Semantic
MediaWiki<http://mapping.referata.com/wiki/Semantic_MediaWiki>shows
coordinates in, such as in ask queries. The supported notations are
DMS, decimal degrees, decimal minutes and floats. All those can be either
directional or non directional. A new parser function has been added that
allows you to convert between any of these formats:
#coordinates<http://mapping.referata.com/wiki/Coordinates>
.
- New geographical functions:
#geodistance<http://mapping.referata.com/wiki/Geodistance>and #
finddestination <http://mapping.referata.com/wiki/Finddestination>. You
can use the #geodistance parser function to calculate the geographical
distance between two points, from and to any of the supported formats. The
#finddestination parser function can be used to find a destination given a
starting point, an initial bearing and a distance.
- Related to the new geographical functions is a rewritten distance query
in Semantic Maps. It now takes into account performance and is scalable,
which the old query was not, by using the new storage structure for
coordinates. The notation for distance queries has also changed. Instead of
using the like operator and a global distance parameter ( like
#ask:[[Property: :~coordinates]]|distance=42 ) you now only have to specify
your distance locally in the coordinate criteria itself like
#ask:[[Property: :coordinates (42 km)]]. Like you can see you can now also
specify a unit, which can be any of the supported
ones<http://mapping.referata.com/w/index.php?title=Help:Distance&action=edit&red…>
.
- Support for various width and height notations. Previously Maps only
accepted width and height values is px, forcing you to use maps of fixed
sizes. Since most people want to have their complete page width visible even
on small screens, this resulted in a lot of people using rather small maps,
and so wasting screen space. 0.6 allows you to specify the size in px, ex,
em, and most importantly, in %. The syntax is what you’d expect:
width=”420px”, width=”420em”, width=”42%”. width=”420″ will default to using
px, so is backward compatible. When using the % values, maps will even adapt
their size when the screen width or the height of the container they are in
is changed after the page has loaded.
- Not a new feature, but rather one that’s removed:
OSM<http://mapping.referata.com/wiki/OSM>support. The OSM service has
been completely removed from Maps and Semantic
Maps as it was rather broken and not easy to upgrade to the internal
structure of Maps 0.6. I’m planning to add it back later on, rewritten from
ground up, in 0.6.1 or 0.6.2 or so. Note that you can still view OSM maps on
your wiki using the
OpenLayers<http://mapping.referata.com/wiki/OpenLayers>service, which
has build in OSM layers, and also allows you to define your
own layers since 0.5.5.
The most notable bugfixes are:
- Fixed conflict with prototype library that caused compatibility
problems with the Halo extension.
- Added automatic icon image sizing for Google Maps and Yahoo! Maps
markers.
- Various security fixes, mostly preventing XSS attacks.
If no serious bugs are found in this release, a minor update can be expected
in a month or so.
[0] http://mapping.referata.com/wiki/Maps
[1] http://mapping.referata.com/wiki/Semantic_Maps
[2] http://mapping.referata.com/wiki/Help:Download
--
Jeroen De Dauw
* http://blog.bn2vs.com
* http://wiki.bn2vs.com
Don't panic. Don't be evil. 50 72 6F 67 72 61 6D 6D 69 6E 67 20 34 20 6C 69
66 65!
--
I have a simple tage extension that I wrote. It currently gets the name of the article through $_GET['article']
However this is an issue where pages that are not the main name space do not work because $_GET['article'] ends up equaling something like nameSpace:articleName
Is there a way to grab the article name and name space separately?
It would be even better if I could access the page id.
The php in the extension where I need to use this is
function efBildrTagsRender( $input, $args, $parser ) {
return '<img src="http://test.com/'.$_GET['title'].'.jpg" />';
}
Thanks,
-Adam
On 31 May 2010 13:11, Henny Savenije <webmaster(a)henny-savenije.pe.kr> wrote:
> Steve, are you the owner of this group?
No, he isn't. He is, however, a subscriber who doesn't like the group
being used for blatantly off-topic noise. And neither am I.
- d.
> There is your wish, and from others, to continue in an other newgroup.
It is not my personal wish to continue this elsewhere. It is my wish that
this topic GO elsewhere.
> Can you tell me which newsgroup I have to use about the morals standards
> of the community developing and installing MediaWiki?
No. That's the job of the people who want this discusion. GO AWAY.
> And will each member of this community incorporate the end results what
> is defined there as moral standards as their own moral standard without
> any further discussion?
We have no idea. We cannot tell the future. Again, GO AWAY.
It looks very nice - and your granddaughter is real gem! Keep on with the
software - there is so much to learn, and it's all fun!
----- Original Message -----
> http://abj.jidanni.org/ is a blog I made using MediaWiki.