My List of things which could be improved in, or added at Wikka

(the items are listed in descending priority)

1. I18n, L10n=> WikkaInternationalization, HandlingUTF8

1. a better System for Categorys => CategorySystemOverhaul

1. A Calendar/organizer => GmBowenCalendar & see below

1. E-Mail and => WikkaAndEmail & see below for some thoughts

1. Toc (Table of Content) -> already implementet in WackoWiki

1. Usermanagement -> UserAdmin

1. User-to-User-Messages-System (working on this...see MailBox...the code (so far) is there....feel free to play with it - GmBowen)

1. Access to the Config.php through a wikka-interface

1. Footnotes (http://www.istitutocolli.org/uniwakka/FootNote)

1. LaTex support (http://www.istitutocolli.org/uniwakka/MathInsert)

1. OpenOffice import/export

1. Smilys (http://www.istitutocolli.org/uniwakka/TablesAndSmileys

And, naturely, everything which gives Wikka new features oder improves the usability/the code.

---

My thoughts about Wikka

Although WikkaWiki is now a very interesting pice of software, there are always things which could be done better. And because I do not want to talk only, I made some contributions to wikka in the three fields which seem the most important to me:

Documentation

There's no good representation without good documentation

The most important part for every project is a good documentation. This occurs to software, too. Not only for developers, but also for administrators and end-users. A documentation is only good if there are no questions remaining after reading it!

Configurability

Since people use wikka for many different purposes, wikka needs a maximum of configurability. My additions to that goal:

1. UserRegistration: An admin can choose if registration is disallowed, allowed only if you know a register-code, or allowed for everyone. This option (and the registration code) are stored in the config

1. StayLoggedIn: Let the user choose if he wants to have permanent cookies with his name and password or only a session-based cookie (to be logged out when all browser windows are closed)

Compatibility

to be added


to be continued...

Fisrt Draft for an actions-howto

WikkaDocumentation Wikka Documentation

---

How to write your own actions

You are missing functionality in wikka? Something which maybe important to you but not to all wikka users? Why don't write yor own action? This HowTo wants to give you some help and hints for this.

Planning

At first, you should think about what you want to do and if an action is the best choice for it.

Action vs. Handler

Mostly you will have to choose between action and handler. You can easily seperate them with the following question:
Do you add something to a page, or do you want to do something with the page?

1. for an addition to a page (the google-form, a weather-forecast, a table), an action should be your choise

1. for doing something to a page (like cloning, deleting, editing...), use a handler

Let others do your work... ;-)

Since there are many people connected to the internet, it is highly possible that someone needed the same functionality as you and has already written it. You surely have looked at the (offical) WikkaFeatures and the Development-Category, but have you also seen the (inoffical) CodeContributions and the UserContributions-category?

It may take you some time to search all this places, but it is better than doing the same work twice.

... or at least help you

When you have started working on your action, announce this at PluginsInDevelopment, perhaps someone else would like to work on that, too.


- searching the internet for code
- security (actions are open for everyone, solutions for [logged-in-user/Admin only])
- validity (xhtml, main sources for errors)
- parameters (how to get them, need of standard-values, proof of type...)
- errorhandling
- problems with teh writing
- generell part about html/php?
- box avout xhtml?
- test about libraries and using wikka-functions

---

CategoryUsers