[wiki] Textbook redesign 2

zero · 2008-02-19 17:46:29

What are you referring to re scalability and support, marios? The number of editors? Are there limits on what txp can handle?

hakjoon · 2008-02-19 18:01:16

Oh and let me repeat this. “I HATE MEDIAWIKI”. We are not staying with MediaWiki unless someone else wants to manage it.

DokuWiki was seen as at least slightly less of a Pain and it can use textile which is a plus. I would prefer to pursue adding the needed functionality to TXP vs having to leanr the ins and outs of another package that I don’t use for anything else.

I see versioning and multi language support as the bigger gotchas but it could also be a workflow issue. The whole process of creating new pages and interliking them is much more cumbersome in TXP IMO.

I really feel that the main problem with Textbook is content so whatever gets more people writing the better.

marios · 2008-02-19 18:35:05

zero wrote:

What are you referring to re scalability and support, marios? The number of editors? Are there limits on what txp can handle?

I was thinking about what Patrick just mentioned. That it is hard, timeconsuming und cumbersome, to do it at this stage, to get the multilingual IA structure right at this point. ( There is currently only one Developer on MLP ) Anyway, just my opinion.

( what I’d wish for the future, would be I tight Integration between MLP and TXP, but that didn’t happen yet )

regards, marios

zero · 2008-02-19 18:49:42

MLP is beyond me, like most of the technical stuff is, but I will be happy to put a lot of work into Textbook in a month’s time when I finish the work I’ve been forced to do. Patrick hates Mediawiki, nobody seems to want to take it over, nobody seems so keen to use Docuwiki, so it seems to me that Textpattern is the way to go. If you techies can sort it out between you, I’ll do all the copying and pasting and take charge of the editing etc. I’m sure some of you will keep an eye on me and make sure I keep the standards high ;)

hakjoon · 2008-02-19 19:06:23

Here a few things that DokuWiki has going for itself.

it can use textile along with other syntax options (markdown)
organizatinal stuff seems better
versioning and diffing
It can convert the interface to the content language (this is something that people wanted at one point)
There is no database
Auto TOC
Content locking for no edit collisions (txp does not have this AFAIK)
Breadcrumbs
syntax is extensible
customizable Auth with experimental punBB one already (no more need for multiple accounts)

marios · 2008-02-19 21:22:25

So how this can be done then @zero? Patrick says, he has a brand new TXP install to hand over the keys.
As we know, 4.0.6 will NOT work with MLP, and I don’t think, that there is any other possible viable solution for the rest of the dozen of Languages.
And also it doesn’t make sense, to go backwards to 4.0.5.

Last edited by marios (2008-02-19 21:25:10)

els · 2008-02-19 22:09:18

I agree with marios. Even if MLP will be updated for 4.0.6, depending heavily on a plugin (that is even also a hack) for an essential TXP site is not a good idea in my opinion.
Also, I don’t know DokuWiki at all, but it’s advantages that hakjoon mentioned – and especially # 3, 4 7 and 10 – seem really useful (if not indispensable) features, and it will take a lot of hard work at the least to make TXP do the same.

zero · 2008-02-19 22:25:03

So how this can be done? Be patient? I’m sure Steve will make MLP work with 4.0.6 when he gets the time. Of course, future txp versions may give the same problem. Are we sure Dokuwiki is OK regarding language? I only speak English so don’t know what is involved. Here’s the dokuwiki language page

I’ve been looking at DokuWiki and the manual There’s a lot to learn. Transferring from Mediawiki is possible but only one page at a time

So there’s a real big learning curve and transfer won’t be much faster than transferring to txp. Is it practical to use txp? Or are we being too optimistic about it? Perhaps there are problems that will make it very difficult? I can’t answer these questions – it needs devs or plugin writers to advise. Mary has already said Dokuwiki, Patrick seems to be indicating Dokuwiki…

hakjoon · 2008-02-19 23:00:49

I think I can automate the page transfer. There is a perl module for reading MediaWiki dump files, I’m thinking is I combine that with the script to transfer the syntax we could make things quicker. I need to flex my Perl muscles a little (they haven’t gotten much use for a few years). I figure I might see if I can modify it to convert to Textile while I’m at it if I can.

There are some issues with translation. I think DokuWiki requires that all the pages have the same name, but the way it’s done is through namespaces which mimics how we do it now in MW.

At the very least this gives a tool that can use Textile which would also make a future move to TXP easier. I would love to do this in TXP as it’s a system I am already familiar with, but it seems pretty involved to make it work.

Oh and bert has started transfering some stuff over to dokuwiki so we can leverage that work.

Last edited by hakjoon (2008-02-19 23:02:19)

zero · 2008-02-19 23:05:10

I vote for dokuwiki then! (until I change my mind;)

marios · 2008-02-19 23:49:28

Just taking a short look, there’s two things that come in handy in Dokuwiki:

Saves stuff/data as plain text files ( That is good I think, as it makes it easier for other tools to use the data )
Syntax Hihglighting ( Here it uses the Geshi Syntax Hilighter, not ideal, but better then nothing )

I could probably write the necessary extension at some point, so as to have the proper syntax hilighting for txp tags ( Which would be nice to have )

regards, marios

Last edited by marios (2008-02-19 23:49:50)

thebombsite · 2008-02-20 08:54:00

Steve (iblastoff) did a txp syntax file for EditArea. Don’t know if that might be a useful start-point for Geshi.

marios · 2008-02-20 09:07:12

thebombsite wrote:

Steve (iblastoff) did a txp syntax file for EditArea. Don’t know if that might be a useful start-point for Geshi.

It’s a different approach. I’m trying to do the same now, extending a mootools class for a differnt purpose.
It could be usefull to go around Geshi, which is sort of heavy.

By the way, I m getting the Internal Server Error again on Textbook ( What I wanted to do, is to add the offset attribute to the linklist entry of the taglisting which became available on version 4.0.6, but no honey again there )

regards, marios

Last edited by marios (2008-02-20 09:09:39)

hakjoon · 2008-02-20 14:40:20

See this is why I want off MediaWiki. This has been happening since we got moved to a new box and no one can figure out why. It normally just fixes itself but I’m going to go do my dance of the million table repairs.

marios · 2008-02-22 01:29:54

Meet TeXari Light.

.

(mootools-based)

I’ve also emulated the line-numbers with Javascript and CSS.( TextMate Style)

( The colors need some more tweaking )

Textpattern CMS

Textpattern CMS support forum

#16 2008-02-19 17:46:29

Re: [wiki] Textbook redesign 2

#17 2008-02-19 18:01:16

Re: [wiki] Textbook redesign 2

#18 2008-02-19 18:35:05

Re: [wiki] Textbook redesign 2

#19 2008-02-19 18:49:42

Re: [wiki] Textbook redesign 2

#20 2008-02-19 19:06:23

Re: [wiki] Textbook redesign 2

#21 2008-02-19 21:22:25

Re: [wiki] Textbook redesign 2

#22 2008-02-19 22:09:18

Re: [wiki] Textbook redesign 2

#23 2008-02-19 22:25:03

Re: [wiki] Textbook redesign 2

#24 2008-02-19 23:00:49

Re: [wiki] Textbook redesign 2

#25 2008-02-19 23:05:10

Re: [wiki] Textbook redesign 2

#26 2008-02-19 23:49:28

Re: [wiki] Textbook redesign 2

#27 2008-02-20 08:54:00

Re: [wiki] Textbook redesign 2

#28 2008-02-20 09:07:12

Re: [wiki] Textbook redesign 2

#29 2008-02-20 14:40:20

Re: [wiki] Textbook redesign 2

#30 2008-02-22 01:29:54

Re: [wiki] Textbook redesign 2

Board footer