Hi Ivaylo,

as for your more general question, it's certainly a viable approach to 
use qooxdoo for an app's presentation layer only. That's how projects 
like Eclipse RAP do it. Then again, qooxdoo is very well suited for fat 
client applications and it might make your life a lot easier if you did 
some of the data processing in the client, only talking to the server if 
you need to access/store data. Of course, you might be reinventing the 
wheel here by reimplementing XRMS' functionality in qooxdoo.

Maybe some of the other devs on the list can weigh in with their 
experiences.

I'm afraid I can't really help you with the PHPRpc stuff other than 
point you towards the docs[1], which you're probably already familiar 
with. But there's quite a few people on the list who use RPC backends 
extensively so I'm sure someone more knowledgeable will come along 
shortly. ;-)


Regards,
Daniel

[1] http://qooxdoo.org/documentation/0.8/rpc_php

ITgopher schrieb:
> Hi, Everyone!
> 
> I wanted to get a bit of advice before I throw too much time and effort into
> this...
> 
> I am part of a large PHP project (XRMS CRM) and have been doing a bit of
> work on it, all of it in PHP so far.  I am presently developing a plugin for
> XRMS for which I wanted to leverage qooxdoo's interface magic and that way
> open the door for XRMS implementing an AJAX-ified UI over time.
> 
> The issue I personally have is that I do not know JavaScript and do not have
> the resources to hire a developer who would.  Of course, it is no black
> magic - one can learn anything and I have had no problems in understanding
> the code of the demos, tweaking them to get various results, etc.
> 
> The idea is to do all data access/processing within XRMS, exclusively in
> PHP, due to the extensive and solid  work that has gone into XRMS's API
> (ACL, sessions, etc.) and then pass the data to qooxdoo's interface to
> render it sweetly for the user.  My understanding was that I would simply be
> using the qooxdoo's widgets to do the rendering of data and collecting user
> input after which I could simply pass that back to PHP and use the XRMS API
> to store/process the newly supplied inputs.
> 
> Sounds wonderful in theory.  In practice, not so easy.
> 
> I got "Hello World" working, no problem.  I got the PhpRpc server setup and
> got RPCExample working and, at least the Echo Test works (I will look at the
> rest later today 'cause something seemed fishy).
> 
> Here is my question?  Considering that I am not JS expert by a long shot,
> just how complicated would it be to use qooxdoo to acomplish the task I have
> envisioned?  Configuring the UI widgets did not seem to be quite so
> complicated and I think I can manage that.  What stumps me is the PhpRpc.  I
> have had spotty success in gathering information about it - the wiki doc is
> most likely a bit outdated and I had to piece together what I needed to get
> RPC Example from some of the posts here (modifying config.json and using the
> core qooxdoo generator.py instead of the RPCExample generate.py)
> 
> I seemed to notice that the PhpRpc is a shiny new release and there is still
> work going into it but I was wondering if there is some more organised
> information on its use, how to pass data back and forth to the PHP script,
> etc.  I am just a bit lost at the moment and don't know where to start
> looking.  Any help would be appreciated.
> 
> Of course, if, after reading the above, you feel that I am trying to scoop
> water out of a quickly sinking boat with a spoon, please let me know before
> I join the fishes ;)
> 
> Have a great day, everyone!
> 
> Cheers,
> Ivaylo


------------------------------------------------------------------------------
The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
production scanning environment may not be a perfect world - but thanks to
Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
Series Scanner you'll get full speed at 300 dpi even with all image 
processing features enabled. http://p.sf.net/sfu/kodak-com
_______________________________________________
qooxdoo-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to