After adding all meta ops and contextualizer with associated functions and adding the
escape sequences too, I'm done so far. Not with Perl 6 but I have achieved for now what I wanted and will turn to
Kephra for a while. The next release just needs a hour or two and i got some fresh ideas too. With 568 entries in the
Appendix A and knowing that A-C are in good shape and almost completely n'cync with german version I can leave with good feeling.
Yesterday I also updated
wikipedia article about Perl. A section about 5.12 was missing and the section about current versions needed to be rewritten. So this corner is also cleared.
I use for my dayly work almost only Kephra and I really need some features to ease my doings.
But that was not the odd thing I wanted announce.
attention please.
The thing I'm going to propose is odd because I want it but I'm not willing to do it myself.
My dream is that the TPF wiki is run by a wikisoftware that doesnt suck and is written in perl 6. There is an attempt called november but it stuck since masak does other exciting stuff. I think parsing and rehashing data is the strength of Perl 5 and more so Perl 6. The second reason for a wiki software written in Perl 6 would be. Perl 6 needs a killer app (odd and unnecessary brutal marketing term). I have a feature set in my mind no other wiki today provides. a desirable software could be for many people the reason to install parrot/Perl 6 in the first place.
Mediawiki is not bad but its wikisyntax has still some limitations which is compensated by a lot of extention. it gone a bit like C++ plus and has no tags and other modern achievements. Socialtext sucks completely. sorry but it has so many limitantions, its hardly usable as a wiki for coding documentation. also foswiki, thewikiformerlyknownasTwiki is often a pain in the ass. what I need is a wiki where
- tables and pre areas that aren't inherently ugly
- tables and pre areas should contain links and all sorts of text formating
- user can change font family and size of different elements, so that there are actually readable
- a wiki syntax allows easily to display any character, despite its normal meta meaning
- editable article sections
- easy spam redo / group redos
- readable coloured diffs / no 10 pages display when all was changes are 10 char
- searchable history
- links with implicit anchors, so i can set in the index a link to the alias term
- or at least link anchors that doesn't do a implicit "\n"
- source code highlighting
- ... many more
Yes the third benefit would be that just my life would be easier. But i realized many of these features doesn't require much coding. Its just my dream may it will come true in this world.
ikiwiki (Score:1)
Re: (Score:1)
Why not overhaul Socialtext? (Score:1)
Re: (Score:1)
Re: (Score:1)
The homepage of the open source version is http://www.socialtext.net/open/ [socialtext.net].
What do you need an admin for?
Re: (Score:1)
Socialtext 4.0 Hosted? (Score:1)
Hi! I agree Socialtext 2.0 really is subpar. :-)
However, I'm coincidentally working for Socialtext, and am one of the main hackers of its Wiki Syntax!
I wonder if we can set up a Free-50 hosted account for the @cpan.org domain, and import the existing Perl 6 Wiki content: See http://www.socialtext.com/products/free50.php [socialtext.com] for details.
The gist is that all writers (not readers) need to be a CPAN author, which may have the nice dual side-effect of encouraging CPAN authorship and reducing spam.
The Social