From ree at ree.hu Mon Oct 1 00:03:24 2007 From: ree at ree.hu (Balazs Ree) Date: Mon, 1 Oct 2007 00:03:24 +0200 Subject: [Kss-devel] ree-demoload branch merged to kss.demo/trunk Message-ID: I merged the ree-demoload branch to kss.demo trunk. kss.demo issues --------------- As a result all actual demos are moved to the "demo" subdirectory. This directory is now placeless, so after a little testing we can just move it over to the core plugin under kss.core/plugins/core . After that kss.demo does not need to be touched any more if we make a new plugin or change the demo of an existing one. The point is that all the plugins should have their demos as part of the plugin. The kss.template package provides a plugin skeleton that can be used with paster. You need to use the kss_zope_plugin template. The generated plugin comes with a simple but functional (!) demo page, and it immediately appears and becomes testable in the demo index page, if you include the zcml of the new plugin. So it'"s a great starting point if someone creates a new plugin. Selenium tests are also supported by the new mechanism. However the createpythontests.py script cannot be used as before, instead the @@kss_demo_registry_admin/createSeleniumTests view needs to be called, and it generates out the seltest_all.py file exactly as the script did it previously previously (the result is placed under the selenium_utils directory). A new test only needs to be dropped as .html into the plugin demo's selenium_tests directory, to be included in the tests. I mainly wrote the abowe paragraph because the kissbot will need to be changed to call the view on the zope instance instead of the script, and use the results from selenium_utils directory. (Godefroid will make this as we agreed.) Other then this it will not be important for developers, the kissbot will do everything. At a later point the original createpythontests.py will return to work again. This will happen when we switch to kss base and all the kss registry will move to plain pythonland. At this time, plugins will need to be touched a little (to move the kss registry to plain python) but the structure and logic will remain similar. Zope3 issues ------------- In addition to the above changes, I also made some fixes in kss.core and as a result now both kss.core and kss.demo trunk *works fully* on Zope3 as well. Only known issue is: zope unittests have never been made working on zope3. So part of the tests are failing with import errors. We still need to do this once. Further actions --------------- If everything is tested to work fine, I will: - also backport kss.demo changes to 1.2 branch. There is no big risk since kss.demo is not part of any running application, but it will allow the paster template to be used immediately under Plone 3.0. - move the actual demos and selenium tests to kss.core, under the core plugin where they really belong to. Further restructuring will be possible after that. (This will only happen on trunk, I won't touch kss.core 1.2 branch.) - the zope3 fixes should go to kss.core 1.2 branch as well. -- Balazs Ree From optilude at gmx.net Thu Oct 4 01:06:40 2007 From: optilude at gmx.net (Martin Aspeli) Date: Thu, 04 Oct 2007 00:06:40 +0100 Subject: [Kss-devel] Weird behaviour with kssSubmitForm and empty selects Message-ID: Hi, I have this TAL in oi.plum: That first