"Alexander Trauzzi" <[EMAIL PROTECTED]> writes: > After the cross-post of my initial inquiry, I figured it would be a good > idea to come on and just say "Hi" to everyone reading. > > What - in terms of documentation - is qooxdoo needing? I want to start > learning how to work with qooxdoo, but I'm uncertain as to where the lion's > share of documentation work is focused.
Hi Alexander, The lion's share of existing documentation is per-class, per-function. If you know what you want to do and what class implements it, you can find the documentation for what parameters to pass to the appropriate methods. The problem, currently, is that if you _don't_ know that a widget exists, or what widget solves a particular problem, or what layouts are available, or ... (I could go on and on), there's no place to look. There a bit of (outdated) information on the web site, but it's quite sparse for teaching a newcomer how to use qooxdoo. > First thing I would like to get into is using the JSON RPC object in > qooxdoo. I can whip together some plain jane PHP scripts to interact with, > the concept is pretty basic. What, I'd really like however are some > examples of code or some pointers on how to get the program structured. The > source to the test suite maybe? The source to the test suite is part of the check-out from svn. It's in source/demo/example and source/demo/test. > #1 for me would be to create a dumb little program that fetches information > from the server - perhaps with a little logic on the far-side to pretty it > up. As I may have already stated in my initial emails, if I get the help > needed, I'll try to put together a little piece on how it was done. I have a new RPC test program that does exactly what you're looking for, in addition to the additional server file to implement the required calls on the backend. As soon as the dust settles with all of the reorganization being done on the source at the moment, I'll check this stuff in. I'll attach these two files to this message. If you've checked out the 'namespaces' branch already and have it working, then do the following: - Copy the backend/php/services directory into your web server root, e.g. /var/www/services - Place the attached fs.php file into services/qooxdoo/fs.php - Put the attached TreeFullControl_4.js and TreeFullControl.html files into source/demo/example - Place a bunch of useless files, some test hierarchy, into some directory that the web server has access to, and point path_sandbox in fs.php to that location. I copied a part of the qooxdoo source into my sandbox. The sandbox is the area of your live file system that will be accessed by the test. - Run the TreeFullControl_4.html test just as you'd run any other test. This test will show you how the RPC calls are used. It populates a tree based on live filesystem data in your specified sandbox, and lets you descend through the tree hierarchy of the sandbox. I have plans to extend this to do additional manipulation of the files in the sandbox, e.g. changing permissions, deleting files, etc. Cheers, Derrell
fs.php
Description: application/httpd-php
Shows a tree, with user-defined icons for some nodes. This tests listening for tree events. A separate alert is generated upon opening a folder that has contents; when opening a folder that has no contents; and closing a folder.
We also demonstrate changing the default value of 'allowShowPlusMinusSymbol' so that all folders initially have a plus/minus symbol. Then, upon opening an empty folder, we remove that icon.
Lastly, we demonstrate in the alert presented by tree events, use of the getHierarchy() method to obtain a full "path" for a tree node.
TreeFullControl_4.js
Description: JavaScript source
------------------------------------------------------------------------- Take Surveys. Earn Cash. Influence the Future of IT Join SourceForge.net's Techsay panel and you'll get the chance to share your opinions on IT & business topics through brief surveys -- and earn cash http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
