[dokuwiki] Re: Help with DokuWiki as a school project
- From: Michael Hamann <michael@xxxxxxxxxxxxxxxx>
- To: dokuwiki <dokuwiki@xxxxxxxxxxxxx>
- Date: Tue, 01 Mar 2011 00:00:36 +0100
Hi,
first of all: please reply to the mail you refer to. At least my mail
client (and many more) match replies based on the In-reply-to - header
your mail client adds invisibly and not based upon the subject.
Excerpts from rezlemic's message of 2011-02-28 22:33:10 +0100:
> Excerpts from Michael's message of 2011-02-25 16:08:20 +0100:
> > [...] Nevertheless there is
> > one idea that is still in the list but imho too small for GSOC:
> > http://www.dokuwiki.org/devel:ideas:remote_api. I might be wrong, but I
> > think this would fit into 20-30 hours. Have a look at
> > lib/exe/xmlrpc.php: There is very little in that dokuwiki_xmlrpc_server
> > class that is specific to XML-RPC: it's basically just that one call to
> > serve() and the error class. [...]
>
> Did I get it right, that you need from me:
> - rewrite the dokuwiki_xmlrpc_server class to be more independent?
> Could you send me more instructions, please?
Yes, it should be usable for different APIs like XML-RPC and JSON-RPC.
The idea is that we implement the DokuWiki specific calls just once and
then there are different implementations that make these calls available
over different interfaces. These interface implementations should offer
an external interface, call these generic methods and then transform the
results (be it the intended result or an error message) into an
appropriate format for the client. Writing the interface (maybe even in
the PHP sense of interface) these interfaces can use/implement is what
you should do if you decide to implement this feature.
You could also pick one of the additional ideas I've added today to the
page linked above and e.g. implement support for changing ACLs over
XML-RPC (instead of the original idea if you like this more).
> > 2-
> > There is a jQuery rewrite in progress. However Pierre Spring who started
> > that rewrite currently hasn't the time for finishing it. You can find
> > his work at https://github.com/caillou/dokuwiki-jQuery (look at the
> > commits to get an impression what he has changed and what this rewrite
> > is about). There have been some changes to the JS code of DokuWiki
> > in the meantime that need to be merged with his work (there is one
> > file that is automatically merged that might need to be adapted and
> > there are conflicts in > lib/scripts/linkwiz.js and
> > lib/scripts/media.js, but I don't think it's that > problematic).
> > [...]
>
> Did I get it right, that you need:
> 1) merge the files lib/scripts/linkwiz.js and lib/scripts/media.js
> from Pierre Spring with these files in the files in the main
> repository https://github.com/splitbrain/dokuwiki ?
> 2) continue to Pierre's work ?
Yes, exactly. I'm not sure if that's clear, but you shouldn't pick just
these two files and merge them but merge the whole master branch from
https://github.com/splitbrain/dokuwiki into the version of Pierre Spring
using Git. These two files are just the files Git can't merge
automatically.
As I've written in the mail for Jan Zmátlík you two could also work
together on one project or if you want you could also pick some bugs or
ask me to propose some possible bugs you could fix.
> And at the conclusion one more question: If I choose a topic to solve,
> should I write you which one and should I continuously inform you
> about my worok? Or should I work on it in quiet and write you when I
> will have something for you?
Yes, you should write us which one you've choosen because if you pick
one of the ideas we're currently offering as GSOC ideas we need to
remove that idea from the GSOC list (at least if you implement a major
part of it). If possible it would be good to know that till March 11 (or
at least what you'll take most probably).
Furthermore you should continuously inform us about your work. You could
also simply work in your own fork on GitHub so we can follow your
changes and review your changes directly on GitHub. Then we can make
sure that your work goes into the right direction and we'll like your
code.
Michael
--
DokuWiki mailing list - more info at
http://www.dokuwiki.org/mailinglist
Other related posts:
