> Hi everyone, > > trying to realize a heavily OOP-based project, I decided that the OOP > layer > qx provides is just the best for my needs there is. However, I really > *only* > need the OOP layer, none of the other stuff,
Are you talking about the qx.Server component? Or is even that "too much" for you? > but information is rare and > the > little there is confuses me. I'm sorry to hear that. I would be happy if you could elaborate on that if you find the time. > The core manual says to use the 'qxoo-build' target Oups, that's really a relict from pre-qx.Server times. If possible please open a bug report for this. > â but what toolchain > do > I use (mobile, server, â¦)? The server manual says that I can use > qx-oo-3.0.min.js for this purpose, too. Yes, that's the current way to go. Stick to the qx.Server section of the manual [1]. [1] http://manual.qooxdoo.org/3.0.x/pages/server.html > > Currently I decided to go with the second approach as it doesn't require > me > to build the project all the time. But I experience a big inheritance > issue: > If C extends from B and B extends from A, I can't access A's methods on an > instance of C. Is there a way to get this to work? Or do I need to use a > toolchain with the build target? This should definitely be possible, provided you include classes A, B and C in your app. Please post a minimal example that can reproduce this behavior. > > Also, what is the best approach to deal with dependencies? If I have A.js > and B.js where B extends from A, I can't just include B.js in my project > before including A.js as it will throw an error. With more complicated > structures (inheritance, interfaces, ...) this becomes very complex very > quickly. Indeed. That brings us back to the tool chain topic. You have basically two options to use qx.Server (the qooxdoo component, or qx-oo.js, the JS file, respectively). I assume you are working in a Node environment. - Download it from our website or install it with NPM (package "qooxdoo"). Then you are basically on your own, writing Node code using the qx-oo API. You would probably use Node's require() to organize your own code and the interaction with qx-oo [2]. - You use the normal qooxdoo SDK ("qx.Desktop") to create an application of type 'server', e.g. with qooxdoo-3.0-sdk/create-application.py -n myapp -t server This application skeleton [3] uses the qooxdoo tool chain to manage dependencies. That means you need to organize your code in standard qooxdoo class files and structures ("source/class/myapp/Application.js"), but are then free to use the Generator, which creates a loader script which you run with Node, supports development and deployment versions, allows you to create Api docs, a test application, etc. etc. [2] http://manual.qooxdoo.org/3.0.x/pages/server/overview.html [3] http://manual.qooxdoo.org/3.0.x/pages/development/skeletons.html#server So, you either follow the Node programming model and use qx-oo.js as a module, or you follow the qooxdoo programming model and can leverage the qooxdoo tool chain. Hope this makes things clearer. Get back with any more questions you have. T. ------------------------------------------------------------------------------ Get 100% visibility into Java/.NET code with AppDynamics Lite! It's a free troubleshooting tool designed for production. Get down to code-level detail for bottlenecks, with <2% overhead. Download for free and get started troubleshooting in minutes. http://pubads.g.doubleclick.net/gampad/clk?id=48897031&iu=/4140/ostg.clktrk _______________________________________________ qooxdoo-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
