Hello All,

I work on real-time financial trading systems written in Java/Swing/Sybase
(and some other technologies). However, I am quite inexperienced with web
technologies such as JavaScript, Ajax, json, servlets etc. Please go easy on
me ;-) 

I'd like to create a web front-end on one of these systems. After a bit of
research on stuff like ExtJS/Sencha (not sure of the licensing), jQuery
seems to be to "low-level" for me right now and a few others - I've decided
to invest time in learning qooxdoo.

Over the last 2 days, in between watching the footie (c'mon, England!), I've
managed to:
- go through all the qooxdoo demos - v. nice and fully-featured. (Well done,
guys!).
- downloaded and ran the HelloWorld custom app - my first ever foray into
javascripting.
- modified the HelloWorld app to use RPC to talk to the RpcServlet running
on Tomcat.  Not sure how current RpcJava qooxdoo-contrib is as I initially
couldn't get this work at all. But after putting in loads of debug stmts I
found that RpcServlet.getServiceInstance() method uses the
MethodUtils.getMatchingAccessibleMethod() which for some reason never
returns. I fixed it locally by using the MethodUtils.getAccessibleMethod()
instead - my first ever bit of rpc-json'ing :-)

So the end architecture I hope to have is:-
- qooxdoo web frontend GUI calling the....
- RpcServlet or my own variant running in Tomcat (via Apache web server)
using an...
- in-house application server providing accessing to services etc etc. It
also supports a simple login() and permissions() services for authentication
and authorisation.

Next on my list to find out about is:-
1. How do I do async updates back to the qx client? Or do I have to
implement up a client driven polling mechanism?
2. The trading system is quite complex (ie 30+ screens). I guess this could
mean a huge production javascript file. What are the options/tradeoffs in
partitioning a GUI into bitesized bits? 
3. Client Login/Authorisation : Will just use the servlet session. 

I feel confident about 3. but if anyone has any views on 1 and 2, then I'd
be most grateful.

In the meantime, I'll try all the other tutorials.

Cheers,

nrg-b

PS: C'mon, Engerland!

-- 
View this message in context: 
http://qooxdoo.678.n2.nabble.com/Hello-from-a-newbie-tp5227706p5227706.html
Sent from the qooxdoo mailing list archive at Nabble.com.

------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel

Reply via email to