aktuelle Projekte

Mich fasziniert das Konzept der Wikis. Ich hoffe, dass aus dem LinuxWiki nicht nur noch eine "ganz nette" Linuxeinführungsseite wird, sondern das Konzept den Inhalt wirklich eine Evolutionsstufe weiter bringt.

/Wer soll das bezahlen?

Nachrichten

moin Florian. I got difficulties in using ImportHtml.py within a moinmoin wiki. It should work an a Windows standalone server with Python24 after putting the Scriptfile in directory wiki/data/plugin/action. I try to call it with [[Action(ImportHtml,myName)]].
But I recieve a TypeError'NoneType' object is not callable. I managed to call the routine HTML2MoinMoin via console. (I typed: "python HTML2MoinMoin "http://www.google.de" in the actions dir and thought: Well done young boy.) But I am not able to use it with wiki... in order to recieve the output e.g. So if You got advices I'd be thankfull. greets


Hello Florian, Nice to have you drop by SwitchWiki! I really liked your ideas about what we could do about inter wiki maps. The idea behind is not to merely create an alphabetical list. That was just the first step to try and get wikis to link to each other based on content and other ways. Currently LionKimbro is also working on how to unite wikis through his WikiNode project, which I think is awesome. I would like to see more linkage through content of wikis and frankly whatever other cool links happen (like language groupings, etc.) -- Best, MarkDilley - (your ideas seem similar to MusicBrainz implementation with their music data... hmm :-)


Dear Florian,

I'm writing to you here because I'm getting the dread Page could not get locked error on MoinMoin:FlorianFesti.

I've left our writeup on CommunityWiki:MachineCodeBlocks2.

I thought about it, and realized that semi-colons in HTML fragment entities would not be a problem, because they will be turned into whatever they actually are (ampersands, whatever,) as part of the HTML->text conversion. What would be a problem in HTML fragments, is bona-fida semi-colons. i.e.: The user wants to actually put in a semicolon. But I think this can be dismissed as a necessary cost. Conclusion: We do not need to change our line separators.

Further:

I don't think we can use JSON, because brackets are link designators in almost all wiki. JSON uses brackets for links. That said, we may want to use English to designate parts of the machine-code-blocks system. Ex: MCB-LIST foo; bar; baz; MCB-LIST-ENDS. Or MCB-DICT-BEGINS foo: 1, bar: 2, baz: 3; MCB-DICT-ENDS.

That said, it looks pretty nerdy.

One of our goals is to be something that people who use wiki will be comfortable with. Key redefinition to signify a list- that seems like something people will be comfortable with. Linking to other dictionaries specified on the same page- I think people will even be okay with that.

We could do this, for naming blocks:

Somewhere on wiki page FooBar...

BEGINBLOCK(foo)
|| whatever: || xyz; ||
|| other_side: || [wiki:Self/FooBar#bar FooBar#bar]; ||
ENDBLOCK

BEGINBLOCK(bar)
|| whatever: || abc; ||
|| other_side: || [wiki:Self/FooBar#foo FooBar#foo]; ||
ENDBLOCK

Which, here, would look like:

BEGINBLOCK(foo)

whatever:

xyz;

other_side:

FooBar#bar;

ENDBLOCK

BEGINBLOCK(bar)

whatever:

abc;

other_side:

FooBar#foo;

ENDBLOCK

One annoyance of using #blah that this exposes: most wiki don't have easy support for hash-links. Most wiki aren't really built for linking to parts of a page. That said, it's nice that people can do this. And at the very worst, you just spell out the full URL+hash.

-- 216.254.10.144 2005-06-05 03:00:45


KategorieHomepage KategorieRedHatBenutzer

FlorianFesti (zuletzt geändert am 2007-12-23 22:49:31 durch localhost)