Hi Mustafa, Thanks for the swift reply... another reason to not use extjs where you have to solve it yourself and then they ask you for the solution!
From my previous list: 1. I actually want the entire qooxdoo library loaded at once. It is an "internal" tool or cached in the browser so I'm quite willing to take the hit the first time qooxdoo is loaded. I see now that I only referenced the website version. I will build the library myself... already have the sdk working. 2. Should I create a new application for the tool I'm building and should I reference the "build-all" output in that build or can I simply script-include "build-all"-script in the html-file? How do I start the qx.application.Standalone once all resources are loaded? 3. I think I got the hang of the build process but I'll get to that later :) 4. Basically the server-side can be deployed with no content other than the "base app" which is the online code app. I guees this is solved if I can get the tool up... Best regards, Kristian Mustafa Sak-5 wrote > Hi Kristian, > > first of all, welcome back. > > 1. Can I use http://cdnjs.cloudflare.com/ajax/libs/qooxdoo/4.1/q.js to do > the same as with extjs? >> If you just want to manipulate DOM elements, sure. But I guess this is >> not what you mend. To be able to concatenate all framework JS classes to >> a single file, you have to extend default build job. Your config.js >> should include a job like this: > > "jobs" : > { > > "build-all": > { > "extend" : ["build"], > "include" : ["qx.*"], > "let" : > { > "OPTIMIZE" : [] > } > } > } > > After running this job you will be able to deploy the file from > ./build/script folder anywhere you want to. > > 2. If yes, can I start a qooxdoo project for development with a simple > html-file and a "qx.application.Standalone"? >> Sure. It is all about JavaScript. > > 3. Will I still be able to build it? >> Not in a qooxdoo manner! One of the benefits of qooxdoo is the ability to >> organize your code in different class files and the dependency resolution >> by namespaces. So you will need tooling, which is provided by qooxdoo >> anyway. But to be able to deal with the generator, you "should" checkout >> the current SDK and create a regular standalone application. > > 4. The online tool has applications but can be built somewhere else and > imported, copied or deployed from somewhere else. Can I include those and > lazy load them using qooxdoo? >> I did not really get what you mend here. Sorry. > > Gruß > Mustafa Sak > > Applications & Integration > 1&1 Internet AG | Ernst-Frey-Straße 10 | 76135 Karlsruhe | Germany > > > -----Ursprüngliche Nachricht----- > Von: Asken [mailto: > kristian.ask@ > ] > Gesendet: Donnerstag, 8. Januar 2015 09:28 > An: > qooxdoo-devel@.sourceforge > Betreff: [qooxdoo-devel] Using the cdn and no build to start a qooxdoo > project > > Hi, > > Following the recent events at sencha I've decided to port my code to > something else. Since I've tried qooxdoo before, liking it, I'm going to > give it a go. There are however a few things I need to figure out before > committing. > > I currently have an online tool where I can edit and run code online. > Using ext I can include ext-all.js and get the full framework. I also > write and manage the tool within the tool it self. The plan is to be able > to move to a much slimmer device with no real processing power. > > 1. Can I use http://cdnjs.cloudflare.com/ajax/libs/qooxdoo/4.1/q.js to do > the same as with extjs? > > 2. If yes, can I start a qooxdoo project for development with a simple > html-file and a "qx.application.Standalone"? > > 3. Will I still be able to build it? > > 4. The online tool has applications but can be built somewhere else and > imported, copied or deployed from somewhere else. Can I include those and > lazy load them using qooxdoo? > > Best regards, > Kristian > > > > -- > View this message in context: > http://qooxdoo.678.n2.nabble.com/Using-the-cdn-and-no-build-to-start-a-qooxdoo-project-tp7586604.html > Sent from the qooxdoo mailing list archive at Nabble.com. > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming! The Go Parallel Website, > sponsored by Intel and developed in partnership with Slashdot Media, is > your hub for all things parallel software development, from weekly thought > leadership blogs to news, videos, case studies, tutorials and more. Take a > look and join the conversation now. http://goparallel.sourceforge.net > _______________________________________________ > qooxdoo-devel mailing list > qooxdoo-devel@.sourceforge > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel > > ------------------------------------------------------------------------------ > Dive into the World of Parallel Programming! The Go Parallel Website, > sponsored by Intel and developed in partnership with Slashdot Media, is > your > hub for all things parallel software development, from weekly thought > leadership blogs to news, videos, case studies, tutorials and more. Take a > look and join the conversation now. http://goparallel.sourceforge.net > _______________________________________________ > qooxdoo-devel mailing list > qooxdoo-devel@.sourceforge > https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel -- View this message in context: http://qooxdoo.678.n2.nabble.com/Using-the-cdn-and-no-build-to-start-a-qooxdoo-project-tp7586604p7586612.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Dive into the World of Parallel Programming! The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
