Elidune/XUL progress
Despite the lack of time some progress have been made :
- Made a method to convert any kind of SoapParameters to nested arrays structure
- Added some methods to the catalogView class to make it able to display more informations
- created a style based on Beagle UI
- login/logout implemented
Here comes a new screenshot:
Elidune/XUL progress (reloaded)
- Finished a nice soap connection wrapper: cool asynchronous callbacks support, sessions management, automatic autentication, errors reporting and easy construction of new soap commands
- Got all the datas structure of Elidune imported and converted as javascript objects
- Did a decent login box totally themable through css (as the whole application will be)
Elidune/XUL progress
A first screenshot to give a preview of what have been done :
Most of the components (soap support, datas bindings...) are done, the progress will be faster now.
Elidune, XUL, soap and gcc-4
Recently quiet a few problems have been resolved, I should progress much faster now.
On the server side :
- I've rewrote the management of the threads in Elidune server. It had some issues with deadlocks since the threads starting order was totally out of control.
- Fixed some bits to make the compilation under gcc 4 possible.
- Fixed some problems into the WSDL generation. Now it has proper datas structures definitions.
Xul client
- Created a connection class. It can already login, manage the session and do a research into the catalog.
- Started to build the UI. I'm thinking about a new orgranization of the UI, but since I had lot of issues for the soap connection I haven't progress much on this.
Almost working !
Finally I managed to send my first soap complex data structure in javascript ! (I got the authentication working). Ok, I still have an issue for having the soap listener callback working properly, but I'll figure out what the problem is.
Damn! I've spent so much time on this problem, trying to provide a XUL client interface to Elidune.
XUL is cool …
... but its documentation is totally lame !
The SOAP interface is really poorly documented, I've already spent so many hours trying to figure out how to send complex data types. All the example we can find are way to simple and no one on the forums/newsgroups seems to know about the problem.
I hope I can find a solution soon, I'd like so much to release Elidune server 1.0 with a XUL client to show for people to try the features online.
DB plugin
I've finished to implement the db plugin interface. Now it'll be very easy to use different databases schemas and make people adapt Elidune to their own architecture.
Lot of testing is needed now, but I am pretty happy with the new version of the Elidune server 
Soon I can start working more on the client side, stay tuned ....
Elidune website
This morning I've put the new Elidune website online.
Yes the content is not really finished yet and I'll try to motivate myself to sort things out soon, but as v1.0 is approaching I had to put some important informations. And, doesn't this site looks better that the previous one ?
By the way, I really need an english contributor (someone here ?), my english sucks too much (Fortunately I would have lessons soon).
Elidune progress
I've just merged the unstable branch into the trunk.
Elidune-server and Elidune-gtk are now both available through subversion at the url https://svn.elidune.org.
When I'll have time to finish the new version of elidune's web site (http://dev.elidune.org), I'll put more information on about how to get and build the sources.
Before v1.0, some work remains on the z39.50 client support and the db plugin...
gsoap migration is done !
A quick note to announce that the xml-rpc to soap migration in Elidune is done !
The server looks a lot nicer now, some major parts have been rewritten and it's now more clean, fast and scalable (wow, looks like an ad. for a car).
Another advantage is that the 'core' of the server allows you to launch multiple servers, then I'll be able to integrate a z39.50 server in the future that will directly share the soap server's code.
Now I've to finish the database plugin system, improve a lot the z39.50 client support and clean some bits here and there before releasing 1.0 version.
