Although it would be great for the interface to be independent of XML/XSLT libraries, at present we're dependent on the (excellent) gnome project libxml parser and libxslt transformation engine.
Someone will need to download libxml2 from the project website and compile/install it on your host web server. If you're on a Win32 machine there is a precompiled binary available, see the Win32 Install page for details.
The XApperator controller and modules are written in Perl so yep its no suprise that you'll need Perl5. XApp only makes use of a small number of external perl modules so dependencies are very lite. If you're on a *nix machine Perl will probably already be installed. If you're on a Win32 machine see the Win32 install notes to get Perl installed.
Perl interfaces to the gnome libxml library are available from CPAN. XApp should only be using vanilla DOM calls and XPath queries so it should be possible to switch to another XML i/f later
If you're on a *nix machine you should be able to install these modules using the usual
perl Makefile.PL, make, make test, make install procedure. If you're on a Win32 machine you should check out the Win32 Install page.
This seems pretty obvious, but you will need a web server capable of running CGI scripts and on a plaform for which you can source or build the libxml libraries. You'll need to create some folders, set some permissions, and maybe setup authentication and ReWrite rules etc. The person who does this may not be you, but someone will need the admin skills to do it.
To deploy XApp you don't really need extensive Perl expertise unless you want to pretty up the chrome around the edit interface, or modify the behaviour of the XApp engine itself. If all you want to do is edit data and you're not concerned about looks then XApp will do what you want out of the box without any Perl hacking
If you only want to manage data in XML files using XApperator and dont need to publish the XML in some other format then you dont need any XSLT skill
If you want to be able to publish the edited XML though (e.g. to HTML) you'll need enough XSLT knowledge to create your own publish.xslt file. Often this publishing stage is pretty straight forward and the sample apps that ship with XApp should be useful examples.
The editing UI of XApp is generated through a supplied XSLT file that you typically wont need to maintain unless you want to modify the behaviour of XApp itself. In that case you'll need a pretty good understanding of XSLT
Authored using: XApperator