After two weeks of nice holidays, I’m back online.
My father became 70 and we spend one week together as family to celebrate this. The other week we visited friends and enjoyed our free time.
Now, back in Office, I noticed that my colleges turned Tine 2.0 an other time inside out. I had to dig through more than 300 commits. Many cool new internal features and again simplifications in the backend. So I’ll have to spend a day to adopt the tasks application to the new standards.
Really cool is the new schemaproc we have now. We can manage tables and relations in a really advanced way. We havn’t found this features, needed for a complex application design, in the existing PHP frameworks and so we are pretty exited about the results. Maybe we can bring this stuff into the Zend Framework.
Also noteworthy are the beginnings of setup and migration. In short it should be possible to install Tine 2.0 without an existing egroupware installation. Also the migration of existing data from egroupware is on the way. Maybe I can manage to finish the infolog->tasks import this week. Really exiting with this migration approach is, that we are able to migrate from different databases/versions easily. So let’s se what future brings 
Also during my holidays, the usability efforts became a lot more concrete. I even found the first interface prototype in my Inbox. Next week I’ll start to implement the first results from this in the addressbook.
As a conclusion of all this progress I take that I realy should take more holidays, as Tine develops great in those times
Here is my first package of the jsdoc-toolkit-ext. I had some homework to do, to avoid licensing issues and to have a cleanly serrated output package.
To use all you have to do, is to define a path to your ExtJS library in the app.main.js.
// path to ExtJS, relative to jsdoc-toolkit-ext
var pathToExtJS = '../ExtJS';
To run jsdoc, just go ahead as usual, e.g.:
java -jar jsrun.jar app/main.js -t=templates/ext -r ../tine20/Tinebase/js/ux/
If not specified differently, find the output package in
out/jsdox.
You can place this directory wherever you want, as it has no dependencies any more.
There is still some work to do, to make jsdoc-toolkit-ext compatible with the ExtJS doctag slang. If you like to help, please drop me a note.
As reported before, there is no tool out there to generate code documentation for ExtJS projects.
Thanks to Chris Scott there is a addition to the jsdoc-toolkit project for handling the specialized extjs methods and tags. He wrote a new plugin-manager which makes it easy to grep arbitrary tokens out of the token-stream.
Unfortunately, the jsdoc-toolkit project dosn’t like this additions, as they change the api of the core and bring dependencies to ExtJS libs which, by the way, have a totally different licence.
To have a quick solution I registered a sourceforge project to hold the extended code. I hope to get some more help form the ExtJS community, so that we have a working solutions shortly.
The current state of the generated output could be seen in the Tine 2.0 JS api docs.
As a long term goal, we should try to resolve the dependencies and bring the code as plugin into the original project.
