You are not logged in.
As some of you know, I've been working on a "unified backend" branch to the Xinha codebase whose central goal is to route all client to server backend requests through a single entry point.
When I started this effort several weeks ago I was not very up to speed on the codebase or client side javascript/dhtml development. To make my life easier I started by reorganizing all the code, adding comment headers and extensive trace and error messages.
Turn off popup blockers and you can take a look at the current development snapshot of the unified backend branch at:
http://www.formvista.com/uploaded_html/ … index.html
If you want to look at the code itself you can point your subversion client to:
svn co http://svn.xinha.python-hosting.com/bra … ed_backend xinha_ub
PLEASE DO NOT SUBMIT CHANGES TO THIS BRANCH. SEND ME PATCHES INSTEAD VIA THE FORM AT:
http://www.formvista.com/contact.html
There is a simple client-side-only demo and a modified version of James's full example which lets you pick plugins. In order to use this version you must have a command line PHP interpreter. I've only tested it under Linux and with FireFox. (It's a development snapshot). To generate the documentation you need both command line PHP and Perl 5.8. Again, I've only run this under Linux.
Before running any of the backends you must first run the quick-and-dirty Configure.php script.
See the README_DEVELOPERS.txt file for more info.
Notable changes in this version:
. The Imagemanager and Linker backends now use xinha_ub/examples as their demo directory instead of DOCUMENT_ROOT. Should be less of a security issue.
. ImageManager and Linker now use the unified backend located in xinha_ub/backends/backend.php
. There is a central config file for the backend in xinha_ub/backends/backend_conf.php.in. The corresponding backend_conf.php file is generated by the Configure.php script.
. new config parameter HTMLArea.Config.linkReplacementMode which can be set to absolute or fullyqualfied. This is used by outwardHtml() to determine how links should be rewritten. The Xinha stock behavior was to change everything to http://yoursite/absolute/link making the resulting content unportable. By setting the option to "absolute" links back to the site will be rewritten as /absolute/link.
. Linker plugin now pops up an error message window is the feedback from scan.php doesn't parse. You can also turn on server debugging trace messages in scan.php to see the output.
. loading of plugins/linker callbacks no longer go into an endless loop if there is an error in the plugin javascript files.
. on editing a link Linker will not scroll to and highlight the item being edited (if it's in the tree).
. client side debugging trace messages have been added to Linker and ImageManager (which can be turned off by commenting out the _ddtOn() calls in imagemanager.js and linker.js. These trace messages are making it childs play to see what's going on and where the problems are.
Nothing in the client side design requires that the server backend be written in PHP. The design is such that other backends could be easily plugged in this architecture. For my work, I need a PHP backend so that's what I'm focusing on.
If you have any questions, comments or feedback please either post them here or you can contact me via the form at:
-----------------------------------------------------------------------------------------
Content Management with Business Intelligence [url]http://www.formvista.com[/url]
Offline