< Kexi | PluginsRevision as of 16:27, 22 September 2014 by Jstaniek (talk | contribs) (Jstaniek moved page Kexi/Web Forms to Kexi/Plugins/Web Forms: hierarchy)(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff) Contents 1 Web Forms 1.1 Synopsis 1.2 Use cases 1.3 Implementation details 1.3.1 HTTP Server component 1.3.2 Configuration files 1.3.3 Data access 1.3.4 Forms conversion 1.4 Why not use lighttpd instead? 2 Links 2.1 Network libraries 2.2 Useful/interesting stuff 2.3 AJAX Toolkits 2.4 Competitors 3 Notes Web Forms Synopsis Web Forms are a technology which can be found even in other leading applications (such as Microsoft Access) but it's encumbered by the use of proprietary or non-standard technologies thus avoiding any usage outside the original platform. Kexi Web Forms implementation will be kept as simple as possible and adhere to W3C standards in a way that any user with a WWW browser (even text-based ones such as link, lynx, w3m) will be able to manipulate records with ease, even if they don't have Kexi installed. Use cases Note Status: TODO Implementation details HTTP Server component The actual implementation uses pion-net-library, for older implementation see 'Notes' below, for more informations about pion-net see the 'Links' section below. Configuration files I'd like to avoid configuration files as much as possible. Kexi Web Forms Daemon should avoid any on-the-fly configuration file generation. Maybe some configuration data can just be integrated inside the .kexi file (need to discuss about this with Jaroslaw). Data access Data access is done through KexiDB2 library Forms conversion Doing a GUI -> Web form conversion can be quite difficult, that's why, at the very beginning development stages I'll focus on generating Web forms on the fly by querying the database through KexiDB2 library. Using configuration data (stored in configuration or .kexi file) the user will be able to choose which fields to hide. Why not use lighttpd instead? First of all, I wanted to use, for my first implementation, a web server designed to be embeddable inside an application, that's why I chose SHTTPD. SHTTPD has a clean, simple API and some interesting add-ons (like HTTPS, CGI, SSI support) while remaining, in fact, quite simple. Lighttpd, instead, is mainly designed to be a standalone web server. With this initial release I wanted to avoid code-generation and have a tight integration with web server' core. I didn't want to write a server module and instead provide a small executable with shttpd statically linked in it. Of course during next months some apache and lighttpd modules would certainly pop-out as soon as I stabilize the core of the web forms exporter. Links Comparison of web servers (Wikipedia) Network libraries Pion Network Library Useful/interesting stuff Forms builder Access-On-Web.de Webtoolkit AJAX Toolkits Echo Competitors Zoho creator Website Presentation Dabbledb Website Demo Notes See the old web page at http://kexi-project.org/wiki/wikiview/[email protected] Give a look at SimpleCommandLineApp as suggested by Jaroslaw Latest working revision with old http backend Path: webforms URL: svn://anonsvn.kde.org/home/kde/trunk/koffice/kexi/webforms Repository Root: svn://anonsvn.kde.org/home/kde Repository UUID: 283d02a7-25f6-0310-bc7c-ecb5cbfe19da Revision: 828892 Node Kind: directory Last Changed Author: villani Last Changed Rev: 827690 Last Changed Date: 2008-07-03 18:04:32 +0200 (Thu, 03 Jul 2008) Retrieved from "https://community.kde.org/index.php?title=Kexi/Plugins/Web_Forms&oldid=39631" Content is available under Creative Commons License SA 4.0 unless otherwise noted.