Many noticed my personal project pnWikka.
To answer most of the question you may have, I'm inviting you to take a look at it, as it says on the front page, I sniffed (with the authors permission of course) many pages from the original site about the module itself.
But to answer some people asking me some question that they may not have found in the documentation, here it goes.
Does pnWikka saves the revisions in the DB ? Yes it does save the pages and revisions in the DB, not in files. It is apparently a point that many finds important so now you know.
Is it templated ? Yes, for the most part. While working on pnWikka, it went fast on the fork road instead of a wrap up (like the pn-cms Doku module for example) because of the nature of the Wikkawiki. (Hardcoded).
It is not 100% templated yet but I would say it is 90% templated.
Is it Multilingual ? Yes but again, there are issues. For example, the word "Category" is a keyword telling to the Wikka script (and pnWikka) that it's a category or that the page is part of a category. You can see the documentation about that [ HERE ].
I will later on work on the module so that the category keyword can be set for a definite language. I'm not into it yet and I'm still not sure how I will pull that up. But for the most part of the module, most if not all language related text has been pull out of the code (Wikkawiki is hardcoded) and language files were created.
Will you be able to import data from another wiki ? I hope. When initialising the module, pnWikka will check if you have a stand alone Wikka wiki (wikka prefix for the tables). If so, it will ask you if you want to import the pages and revisions from you Wikka. If your Wikka is not detected (different table prefix), you'll be able to give the prefix so that pnWikka can try to import your data.
I am also working on a script to import pages from a Doku wiki. I don't know if I'll finish it before opening testing of the pnWikka but rest assure that it's in the plans.
As for other wikis, for the moment, there is no plan yet. Maybe it won't come from me... it all depends of the difficulty and the time I have. For the moment, I'm putting my efforts on the stand alone Wikka and Doku.
As for the rest... feel free to ask or... Wait and see ! ;)
Why Wikka ? Why not ? The Wikka wiki had all I need for a simple wiki and it did not had all the annoying flaws of the pnWiki (written in pnHTML and looked like it was never finished) and I'm a sober guy... So I'm not really interested in most wikis having all sort of gadgets and colorful stuff. I only wanted a wiki. Wikka was simple enough to work with from the code perspective and it was easier to see it become a module for PostNuke than many others out there.
As there are a zillion wikis, some better, some not, one must stop and choose something. I was tired of testing and I liked Wikka. So Wikka I chose. I am totally aware that some other wikis can be better than Wikka... but when I started on pnWikka... I felt no regret. ;)
ETA ? Nope... ;)
C !
To answer most of the question you may have, I'm inviting you to take a look at it, as it says on the front page, I sniffed (with the authors permission of course) many pages from the original site about the module itself.
But to answer some people asking me some question that they may not have found in the documentation, here it goes.
Does pnWikka saves the revisions in the DB ? Yes it does save the pages and revisions in the DB, not in files. It is apparently a point that many finds important so now you know.
Is it templated ? Yes, for the most part. While working on pnWikka, it went fast on the fork road instead of a wrap up (like the pn-cms Doku module for example) because of the nature of the Wikkawiki. (Hardcoded).
It is not 100% templated yet but I would say it is 90% templated.
Is it Multilingual ? Yes but again, there are issues. For example, the word "Category" is a keyword telling to the Wikka script (and pnWikka) that it's a category or that the page is part of a category. You can see the documentation about that [ HERE ].
I will later on work on the module so that the category keyword can be set for a definite language. I'm not into it yet and I'm still not sure how I will pull that up. But for the most part of the module, most if not all language related text has been pull out of the code (Wikkawiki is hardcoded) and language files were created.
Will you be able to import data from another wiki ? I hope. When initialising the module, pnWikka will check if you have a stand alone Wikka wiki (wikka prefix for the tables). If so, it will ask you if you want to import the pages and revisions from you Wikka. If your Wikka is not detected (different table prefix), you'll be able to give the prefix so that pnWikka can try to import your data.
I am also working on a script to import pages from a Doku wiki. I don't know if I'll finish it before opening testing of the pnWikka but rest assure that it's in the plans.
As for other wikis, for the moment, there is no plan yet. Maybe it won't come from me... it all depends of the difficulty and the time I have. For the moment, I'm putting my efforts on the stand alone Wikka and Doku.
As for the rest... feel free to ask or... Wait and see ! ;)
Why Wikka ? Why not ? The Wikka wiki had all I need for a simple wiki and it did not had all the annoying flaws of the pnWiki (written in pnHTML and looked like it was never finished) and I'm a sober guy... So I'm not really interested in most wikis having all sort of gadgets and colorful stuff. I only wanted a wiki. Wikka was simple enough to work with from the code perspective and it was easier to see it become a module for PostNuke than many others out there.
As there are a zillion wikis, some better, some not, one must stop and choose something. I was tired of testing and I liked Wikka. So Wikka I chose. I am totally aware that some other wikis can be better than Wikka... but when I started on pnWikka... I felt no regret. ;)
ETA ? Nope... ;)
C !
| About pnWikka | Log-in or register a new user account | 0 Comments | |
|
| |
| Comments are statements made by the person that posted them. They do not necessarily represent the opinions of the site editor. |