Here it is. Check it out.
http://code.google.com/p/herspos :) On 10/20/11, Phyo Arkar <phyo.arkarl...@gmail.com> wrote: > Yes, > > I was writing a POS application for my wife's sushi shop as a practice > . I am enjoying QooXDoo A Lot now. > > Its unfinished but already usable for adding Items and record. You > will get whole idea. > > Now i am going to Release it as Opensource, so Everyone can use and > contribute too. > > I am uploading to googlecode now. > > Thanks > > Phyo. > > On 10/18/11, wwwgong <wen.g.g...@gmail.com> wrote: >> Hi Phyo, >> I have exactly the same question as yours when you first started this >> thread 1 month ago. >> can you share your working sample with qooxdoo and web2py integration? >> I am interested in using Qooxdoo for custom UI in front of web2py. >> Thanks, >> Wen >> >> my email=wen.g.g...@gmail.com >> >> On Sep 19, 3:31 pm, Phyo Arkar <phyo.arkarl...@gmail.com> wrote: >>> yeah , how abt retrofittingQooxdoointo pyjamas? it should work. It >>> will be easier. Then introduce it into web2py how thats soudns? I only >>> tested pyjamas a bit. >>> >>> after coding mnore and more inQooxdoo,I realize jquery-UI main >>> weakness is making user depending on html and css , and selectors. >>> Actually that wont work for application style UIs. >>> >>> why i like about qooxdoois i never (really never) have to look back >>> at html and CSS at all. another main point is as i am a java hater , >>> even thoqooxdoocode is much like java its still in javascript so its >>> a lot easier.And not like GWT it dont need java to do anything at all >>> just python to generate and compile code :) . >>> >>> On 9/20/11, Ross Peoples <ross.peop...@gmail.com> wrote: >>> >>> >>> >>> >>> >>> >>> >>> > I have been looking atqooxdooas a replacement for jQuery UI for quite >>> > a >>> > while, since they seem to have a nice set of widgets. I don't know why >>> > it >>> > takes the jQuery UI team over a year to make a menubar widget (that's >>> > still >>> > not finished), when you could probably write your own high-quality >>> > version >>> > in a couple of days. That is the one thing that really bugs me about >>> > jQuery >>> > UI: the seemingly stagnent development pace. I understand that things >>> > like >>> > accessibility take a little more time, but other frameworks (and even >>> > individuals) can crank out new widgets in no time that are sometimes >>> > higher >>> > quality than the jQuery UI ones. (end rant) >>> >>> > Anyways, as you mentioned, web2py is focused more on traditional HTML. >>> >Qooxdooseems to generate its own HTML based on the JavaScript code you >>> > enter (like with desktop programming). It seems more like an AJAX >>> > application builder rather than an HTML additive, like jQuery. Before >>> > coming >>> > to web2py, I evaluated Vaadin, which is a Java server/client >>> > integrated >>> > framework that is built on Google Web Toolkit (like pyjamas is). Only >>> > you >>> > program everything in Java. It's pretty powerful and the widgets were >>> > the >>> > best I've ever seen (quite a lot of them too). The only problem with >>> > it >>> > though is that trying to do something that would be simple with HTML >>> > and >>> > JavaScript would require you to make your own widget and recompile the >>> > entire widget set. It was great for working inside the box, but way >>> > too >>> > difficult if you wanted to step outside the box. >>> >>> > Enough with the babbling: what we would need to do is make >>> > aqooxdoohelper >>> > that can generate JS code for the widgets. However, it might just be >>> > easier >>> > for everyone to write their own JavaScript, since it's well documented >>> > on >>> > theqooxdoosite. As for the AJAX communications, according to >>> > theqooxdoo >>> > site:http://manual.qooxdoo.org/1.4.x/pages/communication/rpc.htmlthey >>> > use >>> > JSON-RPC, which web2py already supports. They also have a Python RPC >>> > server >>> > (for an older version of >>> >qooxdoo):http://qooxdoo.org/contrib/project/rpcpythonso that could >>> > probably integrated into a web2py plugin or contrib module. Source >>> > link: >>> >https://qooxdoo-contrib.svn.sourceforge.net/svnroot/qooxdoo-contrib/t... >>> >>> > So to have web2py supportqooxdooapps, it would take a little bit of >>> > work, >>> > but it's totally do-able, and some of the pieces are already there. >
