Re: [qooxdoo-devel] How to get the displayed data from a filtered table?

Hi Jeff, Please can you re ask your question on gitter at https://gitter.im/qooxdoo/qooxdoo ?  We don't use this mailing list any more, and gitter allows much more responsive conversations. Regards John Sent from my phone On Thu, Oct 4, 2018 at 10:01 PM +0100, "Jeffrey

Re: [qooxdoo-devel] ES6 ES2015 ecmascript primitive usage in qooxdoo 6.0.0-alpha

Hi Marcel Did you see Derrell's reply at https://gitter.im/qooxdoo/qooxdoo?at=5bb3c6c2ae7be94016f00846 ? This mailing list is not used any more, Gitter is the place to ask questions Regards John On 02/10/2018, 20:17, "Marcel Ruff" wrote: Hi, when I use "let" or "const" from

Re: [qooxdoo-devel] How to use an external css url

Hi Please can you ask your question at StackOverflow and be sure to add “qooxdoo” as a tag? Asking on StackOverflow gets your question to as many people as possible and helps us build the public documentation. This mailing list isn’t used very much any more – but we are on Gitter at

Re: [qooxdoo-devel] Please some little help about url routing in mobile apps

by tweaking your code. Secondly, please would you consider asking this question via StackOverflow and tagging your question with “qooxdoo” - feel free to post back here with a link to the question, or chat on Gitter in the “qooxdoo” group there Regards John Spackman On 7 July 2016 at 02:23:20

Re: [qooxdoo-devel] question about mobile list and longtap

Hi guys Thanks for contributing and taking part on the list, but please can you communicate in English?  Qooxdoo is made up of users from across Europe as well as further afield, and the official policy is that all emails, discussions, comments, etc are in English. Thanks John On 7 July 2016

Re: [qooxdoo-devel] question about mobile list and longtap

Hi Please could you re-ask this question at StackOverflow and make sure you add the tag “qooxdoo”?  We’re trying to develop a more public set of Q and StackOverflow is a great way to do it Regards John On 28 June 2016 at 09:47:29, rsantiagopaz (rsantiago...@gmail.com) wrote: hi (sorry the

Re: [qooxdoo-devel] Qooxdoo generate doesn't support ... operator?

.n2.nabble.com/QxCompiler-add-ES6-faster-compilation-and-100-Javascript-API-to-building-applications-td7587992.html Regards John Spackman On 5 May 2016 at 15:32:16, Derrell Lipman (derrell.lip...@unwireduniverse.com) wrote: Ah, ok. So the problem here is that the qooxdoo generate.py utility does

Re: [qooxdoo-devel] Qooxdoo build-all deployment

Hi Andy Sorry for the delay in getting back to you, please could you re-ask your question via StackOverflow and I’ll answer it there?  We’re trying to build up a more public list of Q and it would be really helpful to have your question listed there. Please be sure to add the tag “qooxdoo” to

Re: [qooxdoo-devel] Organizing unit tests into a test suite

Hi Dimitri You can define setUp and tearDown on a unit test class to do exactly that, there are examples in the qx.test.* classes.  If you need to share setUp/tearDown between different unit test classes, you can use inheritance and/or static methods to do that because they are normal classes.

Re: [qooxdoo-devel] qooxdoo events best practices

Hi Dimitri Please can you ask this on StackOverflow?  We want to improve the Q and our SEO, and StackOverflow is a great way to do that. Make sure you use the “qooxdoo” tag on your question - I think I’ll get an email as soon as you’ve done it (I only signed up myself yesterday) but if you

Re: [qooxdoo-devel] Is it possible to add another object to the converter for a singlevalue-binding?

I think that would work (although it's hard to be sure without a working example) but you could solve the initial problem with a closure. John > On 15 Apr 2016, at 20:44, LoneSurvivor wrote: > > While writing the post, I got an idea: would it be a proper way, to create a

Re: [qooxdoo-devel] Scrollbars not showing in Chrome Version 49.0.2623.112 m

Hi Werner It looks like a bug to me - the issue is that the yellow bars on the side are where the native scroll bars go, but on Chrome & Safari they do not appear. This works as expected on Firefox and IE11. Please can you create an issue on github so that we can track it? Regards John

Re: [qooxdoo-devel] the bugzilla migration ...

+1 - the integration provided by github issues is so much better than bugzilla, having the archive on there too is great, IMHO it’s a no brainer to ditch BZ altogether now On 08/04/2016, 11:24, "qooxdoo Development on behalf of Dietrich Streifert"

Re: [qooxdoo-devel] New real time web application framework based on qooxdoo.

Hi Luca That looks really cool! I’m looking forward to my beta :) I have a few questions (well lots actually ;) but here’s a few for now...) Does the UI designer generate native Qooxdoo apps? And could this be used independently of a .net backend? How does the theme builder work? That

Re: [qooxdoo-devel] How do I access a list item?

Aha, yes me too – I assumed you were on desktop too. I’ve had a look at the code for mobile and AFAICT the item is not made available; the preferred method is to change the underlying model and ask the list to redraw itself. Here’s an example: http://tinyurl.com/hy2xzmh John From:

Re: [qooxdoo-devel] How do I access a list item?

Hi Tomas e.getData() will return an instance of qx.data.Array, which is the selection; what you want to do is access selection.getItem(0) to get an instance of qx.ui.form.ListItem. If you still have problems, please can you create an example in the playground? It’s much easier to help out if

Re: [qooxdoo-devel] Dropping qxcompiler qooxdoo fork?

Hi Stefan Yes, my branch can be ignored now Regards John On 26/03/2016, 12:50, "qooxdoo Development on behalf of d...@cost-savers.net" wrote: >Hi John, > >I have seen that you

Re: [qooxdoo-devel] qooxdoo issues moving to github

+1 Good idea :) John On 21/03/2016, 15:54, "qooxdoo Development on behalf of Tobias Oetiker" wrote: >Qooxdooers! > >We are in the process of migrating qooxdoo resources to public

Re: [qooxdoo-devel] GUI advises?

Hi You can get part way there using standard layout controls but some features such as darkening the rest of the page when the mouse is hovering the pop out card would require you to implement a custom layout. EG, a first pass could be to add the popout has a child inside your horizontal

Re: [qooxdoo-devel] Cursor-Events left/right in Textfield, added indirectly to a form.List

Hi Markus Do you mean that you’ve added things other than a ListItem to a list and they don’t work as expected, or that you have added ListItems which have child widgets that are TextField etc? I looked at this once and AFAICR there is very little that List requires from ListItem – the check

Re: [qooxdoo-devel] Component library

Hi Stefan I hadn't seen this when I replied earlier, but reading it now I think that this touches on the discussions ages ago about how to integrate contributions into builds. If bringing in outside contributions could be simplified, then the location and control of components, whether

Re: [qooxdoo-devel] Embed design elements rather than use images

Have you looked at combining multiple images into one? This would allow a similar drastic reduction in resource requests. There are features in qooxdoo to support this - although it's been a while since I've looked at it so while there may well be ways support for this can improve.

Re: [qooxdoo-devel] Component library

Hi Stefan Im not sure if I've misunderstood but while I think it would be quite straightforward to separate them off, Im not sure what the benefit would be? There's no runtime overhead because the compiler/generator would only bring in what's necessary, so it would be useful for admin

Re: [qooxdoo-devel] QxCompiler - add ES6, faster compilation, and 100% Javascript API to building applications

Hi Defero Sorry for the delay in getting back to you, it's been a very busy week I've not used parts in Qooxdoo, but AIUI you associate classes with a named part, and then use the API at runtime to force the loading of the part; how the compiler brings together for a part would be the

Re: [qooxdoo-devel] Evolving the qooxdoo Project

g-time qooxdoo fellows Fritz Zaucker and Tobi Oetiker joined to coordinate and drive the upcoming changes and improvements. Moreover, others we asked for their close collaboration are also on-board, e.g. Cajus Pollmeier, Derrell Lipman, Dietrich Streifert, John Spackman. Given the recent activi

Re: [qooxdoo-devel] cursor on images with scale true

Brill, thanks Bernardo On 24/02/2016, 12:53, "kreimer" wrote: >Added some check on getAllStyles() being not null. > > > >-- >View this message in context: >http://qooxdoo.678.n2.nabble.com/cursor-on-images-with-scale-true-tp7588002p7588105.html >Sent from the

Re: [qooxdoo-devel] cursor on images with scale true

Hi Bernardo That looks like a sensible fix - please can you submit it as a pull request? Cheers John On 23/02/2016, 13:49, "kreimer" wrote: >Hi! > >First, I want to apologise for having pasted all this code in this post, but >tinyurl said "414 Request-URI Too

Re: [qooxdoo-devel] QxCompiler - add ES6, faster compilation, and 100% Javascript API to building applications

On 23/02/2016, 11:33, "d...@cost-savers.net" wrote: >We can look at it and try to replace all python with grunt integration further >on the line the core team did before. >I can back on this asap. > >Stefan > Fantastic :) Cheers John

Re: [qooxdoo-devel] Supporting multiple plural forms in translations

Kind of - I think there’s a mistake in your JSON for ru.cows, or in ru.po, should it be: translations: { "es": { "cow": "vaca", "cows": "vacas" }, "ru": { "cow": "korova", "cows": [ "korovy", "korov" ] } } Or should the ru.po be: msgid "cow" msgid_plural "cows"

Re: [qooxdoo-devel] onUpdate binding callback not called if submodel has been updated

the model (line 34), onUpdate() has not be called. This is my problem, I would like to found a way to be "notified" when the model has changed. 2016-02-18 7:02 GMT+01:00 John Spackman <john.spack...@zenesis.com>: Hi William The onUpdate method is being called; is it possible that you w

Re: [qooxdoo-devel] Supporting multiple plural forms in translations

va", // msgstr[0] > >"cows":"korovy", // msgstr[1] > "cows@plural": [ "korova", "korovy", >"korov" ] // whole msgstr array > } >} > >Dimitri > >P.S. I've noticed that both QxCompiler and generate.py d

Re: [qooxdoo-devel] QxCompiler - add ES6, faster compilation, and 100% Javascript API to building applications

Hi Stefan Thanks for the support, Im glad you like it :) I agree that QxCompiler needs to stay focused on compiling, IMHO generate.py became the swiss army knife of the Qooxdoo toolchain and being written in Python and not as an API made made it opaque (for my purposes, at least) Generate.py

Re: [qooxdoo-devel] QxCompiler - add ES6, faster compilation, and 100% Javascript API to building applications

This should be straightforward once the continuous compiler process is done – I will implement that as an API too, so integrating with an HTTP server implementation would be trivial and could be done as a separate contrib or PR. I’ve been using https://www.npmjs.com/package/http-server and

Re: [qooxdoo-devel] QxCompiler - add ES6, faster compilation, and 100% Javascript API to building applications

Hi Adrian Then to install all dependencies and run, just do: npm install -g grunt-cli npm install //installs dependencies listed in package.json into node_modules folder grunt //runs default http-server:dev job Looking forward to ditch ./generate.py in favor of a simple and faster grunt

Re: [qooxdoo-devel] QxCompiler - add ES6, faster compilation, and 100% Javascript API to building applications

There’s a new release that went out just before the translation mod that does the shared cache - although the source-output directory is currently very similar to build-output, this is only temporary because build options can change the code which is output. This is primarily that calls to

Re: [qooxdoo-devel] Supporting multiple plural forms in translations

I think that the only thing missing from the toolchain to support this is being able to include the headers from the translation in the compiled application; I’ve just pushed a version of QxCompiler that now adds this. I have not done the corresponding changes to qx.locale.Manager because

Re: [qooxdoo-devel] QxCompiler - add ES6, faster compilation, and 100% Javascript API to building applications

r myself, just didn't get around to it yet. Cheers, Fritz On Fri, 19 Feb 2016, John Spackman wrote: > BTW I missed you comment on this earlier - by profiling, do you mean of > the compilation process or injecting profiling statements into the > generated code? > > On 18/02/20

Re: [qooxdoo-devel] momentum

That PR is withdrawn now in favour of this one, which has a much improved commit history: https://github.com/qooxdoo/qooxdoo/pull/173 John On 18/02/2016, 17:19, "John Spackman" <john.spack...@zenesis.com> wrote: >Just done it :) https://github.com/qooxdoo/qooxdoo/pull/17

Re: [qooxdoo-devel] QxCompiler - add ES6, faster compilation, and 100% Javascript API to building applications

> >Slightly offtopic: did you try Nashorn with your server-side? Should be >much faster and feature-rich. Besides, we are planning an opensource >project - JavaScript console for JavaEE with qooxdoo frontend a la >Playground. It would allow to author/run/manage server-side scripts, >with support

Re: [qooxdoo-devel] QxCompiler - add ES6, faster compilation, and 100% Javascript API to building applications

BTW I missed you comment on this earlier - by profiling, do you mean of the compilation process or injecting profiling statements into the generated code? On 18/02/2016, 17:51, "Dimitri" wrote: >I'm not a Node.js pro (I'm a JavaEE architect in fact :) so I'm not

Re: [qooxdoo-devel] momentum

Hi Stefan Great, I’m glad its working for you too :) Hopefully ES6 support something that we can use to help generate a bit of excitement back into Qooxdoo and make it more modern. It’s great to see it getting used in big projects so soon, IMHO the core is pretty stable but my main concern

Re: [qooxdoo-devel] QxCompiler - add ES6, faster compilation, and 100% Javascript API to building applications

bel- >> > > core/lib/transformation/file/options/option-manager.js:393 >> > > throw new Error("Couldn't find preset " + >> > > JSON.stringify(val) + " relative to directory " + >> > > JSON.stringify(dirname)); >>

Re: [qooxdoo-devel] QxCompiler - add ES6, faster compilation, and 100% Javascript API to building applications

Hi Dimitri You’ve done everything right but I’ve realised my mistake is that it’s not just the database any more, it’s the transpiled code is specific to each target and that it what’s taking the time. So the correct solution is that I must change QxCompiler to that several applications can

Re: [qooxdoo-devel] momentum

Just done it :) https://github.com/qooxdoo/qooxdoo/pull/170 It’s backwards compatible, the new dependency features are only enabled when QxCompiler runs and patches the loader on the fly. John On 18/02/2016, 16:51, "Tobias Oetiker" wrote: >Hi Dimitry, > >I have not seen

Re: [qooxdoo-devel] QxCompiler - add ES6, faster compilation, and 100% Javascript API to building applications

revious experiment, everything went smooth (except that it didn't in fact collect any qooxdoo deps, since I removed all plugins - but transpiling itself went fine). As for uglify - ah, that was stupid. I used original uglify, not uglify-js. Just tried the latter (2.6.1) - indeed, it takes

Re: [qooxdoo-devel] momentum

Hi Tobi This is really good news, well done and thank you for making this happen :) You’ve obviously had a busy morning because we’re already down to only 9 pull requests outstanding. I’ve responded to all of mine so a little more work but hopefully it’ll be quick. Regards John On

Re: [qooxdoo-devel] QxCompiler - add ES6, faster compilation, and 100% Javascript API to building applications

No problem; the next release will have a dbFilename property on qxcompiler.makers.Maker, so compile-app-demo.js now has this: // Makers use an Analyser to figure out what the Target should write var maker = new qxcompiler.makers.SimpleApp("qxt.Application", "qxt.theme.Theme").set({ // Targets

Re: [qooxdoo-devel] onUpdate binding callback not called if submodel has been updated

Hi William The onUpdate method is being called; is it possible that you were looking in the Playground log and not in the browser log? The Playground log only includes messages from this.warn() etc (or qx.log.Logger.warn() etc), but console.log() statements go direct to the browser console.

Re: [qooxdoo-devel] How to write to Test Runner log?

Hi Tina For instances of objects you can use this.debug(), this.warn(), etc or for static use you can use qx.log.Logger.debug() etc. Regards John On 17/02/2016, 21:00, "Tina" wrote: >How do I write to the Test Runner log seen in browser? I tried

Re: [qooxdoo-devel] QxCompiler - add ES6, faster compilation, and 100% Javascript API to building applications

. Just tried the latter (2.6.1) - indeed, it takes ~10 secs for qxt. Not bad. В Ср, 17/02/2016 в 20:56 +, John Spackman пишет: Got it – it was a bug in my plugin I introduced a while ago, but Chrome obviously supports arrow functions natively so I didn’t pick up that the translation was

Re: [qooxdoo-devel] QxCompiler - add ES6, faster compilation, and 100% Javascript API to building applications

1) - indeed, it takes ~10 secs for qxt. Not bad. В Ср, 17/02/2016 в 20:56 +, John Spackman пишет: Got it – it was a bug in my plugin I introduced a while ago, but Chrome obviously supports arrow functions natively so I didn’t pick up that the translation wasn’t happening any more. The .babel

Re: [qooxdoo-devel] QxCompiler - add ES6, faster compilation, and 100% Javascript API to building applications

the final code size as well as reduce dependencies, which will reduce the code size even more. My guess is that this will bring qxcompiler into the same ball park as generate.py in terms of the size of the final output John From: John Spackman <john.spack...@zenesis.com> Reply-To: q

Re: [qooxdoo-devel] QxCompiler - add ES6, faster compilation, and 100% Javascript API to building applications

Got it – it was a bug in my plugin I introduced a while ago, but Chrome obviously supports arrow functions natively so I didn’t pick up that the translation wasn’t happening any more. The .babelrc is not needed for this because we’re using it embedded, I think the .babelrc is only for the CLI

Re: [qooxdoo-devel] QxCompiler - add ES6, faster compilation, and 100% Javascript API to building applications

this modifies the original *.po files in your source directory, please take a backup of your files first. Build Target compression is next :) John From: John Spackman <john.spack...@zenesis.com> Reply-To: qooxdoo Development <qooxdoo-devel@lists.sourceforge.net> Date: Wednesday, 17 F

Re: [qooxdoo-devel] QxCompiler - add ES6, faster compilation, and 100% Javascript API to building applications

Hi Dimitri No worries, those are the kind of bug reports I like to hear, ones where it’s not my fault! :D Actually I’m a little surprised that the generator supports the # compiler hints still, I thought that had been dropped ages ago; I have yet to add warnings output for unresolved symbols

Re: [qooxdoo-devel] QxCompiler - add ES6, faster compilation, and 100% Javascript API to building applications

t; >> Subject: Re: [qooxdoo-devel] QxCompiler - add ES6, faster compilation, and >> 100% Javascript API to building applications >> >> John, >> >> this looks interesting! I like the API-based approach (Reminds me of the >> Clojure "boot" build sys

Re: [qooxdoo-devel] QxCompiler - add ES6, faster compilation, and 100% Javascript API to building applications

Hi Dimitri So further to this – I’ve made a lot of progress with translations today, but I’ve run out of time so rather than release anything half baked I’ll hold off until tomorrow John From: John Spackman <john.spack...@zenesis.com> Reply-To: qooxdoo Development <qoox

Re: [qooxdoo-devel] QxCompiler - add ES6, faster compilation, and 100% Javascript API to building applications

etrich.streif...@googlemail.com> wrote: >Hi John, > >we are using Centos 7.2 aka RHEL 7.2 which delivers nodejs 0.10.36 >through epel repository. > >Regards >Dietrich > > >Am 16.02.2016 um 08:26 schrieb John Spackman: >> Re Node 0.12: I think there was another proble

Re: [qooxdoo-devel] QxCompiler - add ES6, faster compilation, and 100% Javascript API to building applications

Hi Dimitri So it sounds like resources with paths have an issue, or maybe libraries with “.” in the namespace – I’ll have a look this morning but as it’s happening with UploadMgr then I have a reproducible case I can work on. I’ve had a look at the stack trace – but I can’t see any clues to

Re: [qooxdoo-devel] QxCompiler - add ES6, faster compilation, and 100% Javascript API to building applications

Hi Defero Thanks :) I found a bug in util.mkpath yesterday that might have been the problem you found - mkpath would start to create the folders and then stop, but that’s fixed now. Are you thinking of having a look at part loading? John On 15/02/2016, 17:15, "Defero"

Re: [qooxdoo-devel] QxCompiler - add ES6, faster compilation, and 100% Javascript API to building applications

API-based approach (Reminds me of the Clojure "boot" build system's tag line, "Builds are programs"[1]). It seems you have been working on that for a while. [1] http://boot-clj.com/ On Mon, Feb 15, 2016 at 9:28 AM, John Spackman <john-li...@zenesis.com> wrote: The

Re: [qooxdoo-devel] QxCompiler - add ES6, faster compilation, and 100% Javascript API to building applications

t the API, but also seen that the BuildTarget has a bug and doesn't work - it's only a minor issue but I probably wont have time to fix it until tonight John From: "John Spackman" <john.spack...@zenesis.com> Sent: Sunday, February 14, 2016 9:50 AM To: "qooxdoo Deve

Re: [qooxdoo-devel] QxCompiler - add ES6, faster compilation, and 100% Javascript API to building applications

Hi Dietrich Thanks :) There are two sets of changes – strict mode support (which is in the strict-mode-support branch), and mods needed for QxCompiler. I will put them up as pull requests once things settle down with QxCompiler, but in the mean time both branches are based on vanilla Qoxodoo

Re: [qooxdoo-devel] QxCompiler - add ES6, faster compilation, and 100% Javascript API to building applications

Hi Dimitri Thanks for checking out so quickly :) Re: npm and docs: done Re: qooxdoo submodule and https: fixed Re: QOOXDOO_PATH: no - that's a generator.py/config.json setting and config.json files are completely ignored; when using the QxCompiler API, once you have told it where the

Re: [qooxdoo-devel] QxCompiler - add ES6, faster compilation, and 100% Javascript API to building applications

Further to this - I've added some docs about the API, but also seen that the BuildTarget has a bug and doesn't work - it's only a minor issue but I probably wont have time to fix it until tonight John From: "John Spackman" &

[qooxdoo-devel] QxCompiler - add ES6, faster compilation, and 100% Javascript API to building applications

Hi all There is a first release of my QxCompiler that adds ES6 to Qooxdoo applications and replaces the generate.py toolchain with a faster, 100% Javascript tool that is easily extensible. You can find the first release at GitHub here: https://github.com/johnspackman/qxcompiler It’s an alpha

Re: [qooxdoo-devel] How to make parts independent

Hi Dimitri Thanks for the kind words :) The delay in releasing has been finding the time to do some proper testing before opening it up to scrutiny, but I've got it running the whole demo browser from Qooxdoo now and that's a pretty varied set of tests. The documentation isn't exactly

Re: [qooxdoo-devel] How to make parts independent

Hi Defero Sorry, I really haven’t forgotten - I’ve just been so flat out with work this year. I do think that I’ll be able to do the docs etc this week, but I’ll put what I have up regardless and then we’ll chat over the ML Regards John On 10/02/2016, 14:28, "Defero"

Re: [qooxdoo-devel] Scaling (but not skewing) Atom image

his over the years... Derrell On Tue, Jan 12, 2016 at 8:09 AM John Spackman <john-li...@zenesis.com> wrote: The only solution I have for this is to reimplement qx.core.basic.Image, but with added tweaks for scaling. I’ve created a playground demo but it is too large for a shortened URL bec

Re: [qooxdoo-devel] Drag & Drop changes

Ah, I see what you mean! I just tried it with a label instead of a button and it works fine, so I guess it’s a regression associated with widgets that have input. You could try filing a bug report, and it would be great if you could find the cause (if you can fix it, you could also file a

Re: [qooxdoo-devel] Attaching a custom event to an existing widget?

Ah yes, well spotted :) Regards John On 07/01/2016, 20:51, "LoneSurvivor" wrote: >Hi John, > >thank you for your answer, this was exactly what I was looking for. Also for >the example with the myData-object which would become my next hurdle. Thank >you very much! > >I

Re: [qooxdoo-devel] Attaching a custom event to an existing widget?

Hi This is easy so long as by “I have a number-property” you mean that you have an actual Qooxdoo property in your root widget, for example if you have something like this in your root widget class: qx.Class.define("my.RootWidget", { extend: qx.ui.core.Widget, properties: {

Re: [qooxdoo-devel] How to make parts independent

Hi Defero Yes, there is and I think it’s good news :) My original implementation was based on Esprima and I’ve had to rejig it to make it work with Babel for ES6 - I think it’s ready for alpha release baring one issue with environment settings and some documentation. Sorry it’s a bit later

Re: [qooxdoo-devel] Qooxdoo Automatic Memory Management - a proposal

Hi Petr, Varol Thanks for the feedback :) Petr, can we show that is definitive, that DOM->JS leaks have been fixed? Because if so then I agree that the registry can be eliminated completely. My concern is that I still see leaks in IE11 that survive page refreshes and wouldn’t want to make

Re: [qooxdoo-devel] Attaching a custom event to an existing widget?

You can’t directly bind to a number, but you can create a property in your own class and bind to that; this is a useful technique because if you want to do something when the value changes, your property can have its own “apply” method. John On 04/01/2016, 19:29, "LoneSurvivor"

Re: [qooxdoo-devel] MSingleSelectionHandling for non widgets

Hi Bernardo That sounds reasonable - can you do it as a pull request? I’d suggest not moving classes from their current location because of backward compatibility, and if you can implement it as a non-breaking change then there’s a good chance you can get it merged (plus off course you get to

[qooxdoo-devel] Qooxdoo Automatic Memory Management - a proposal

Hi all Apologies for a rather long post, please bear with me :) I’ve been thinking a lot lately about memory management in Qooxdoo apps, specifically how to reliably remove the need to call dispose() (without causing leaks) and reducing complexity to our applications — I have a proposal

Re: [qooxdoo-devel] Override issue

Hi Jonathan The problem is that _onFieldMouseDown does not exist – it looks like your example code is out of date, because since Qx 4.x there’s been a transition to “pointer” events over “mouse” events to better support mobile & tablets. In qx.ui.control.ColorPopup, _onFieldMouseXxxx has

Re: [qooxdoo-devel] How to make parts independent

l/pages/tool/grunt.html > > >Am 23.12.2015 um 10:40 schrieb John Spackman: >> Well I’ve talked about it now so I’d better put it up! :) >> >> My plan is to get it finished off and release on github as an alpha before >> getting-paid work start

Re: [qooxdoo-devel] How to make parts independent

: Wednesday, 23 December 2015 at 02:58 To: qooxdoo Development <qooxdoo-devel@lists.sourceforge.net> Subject: Re: [qooxdoo-devel] How to make parts independent John, that sounds incredibly cool! Derrell On Tue, Dec 22, 2015, 8:06 PM John Spackman <john-li...@zenesis.com> w

Re: [qooxdoo-devel] How to make parts independent

Hi Defero To make that work you’d need to be able to analyse the dependencies of each plugin on demand, and then load those classes to the client; I dont think you can do this with the current generator but as it happens I think I’ll have something that will do the job in the next week or so.

Re: [qooxdoo-devel] links to the qooxdoo application

If you do that then doesn’t that mean that you’ll have to serve the app up from several URLs (in which case the browser will see each URL as a separate app and cache the results independently), or redirect the user back to a common URL with a parameter? I think the differences with the API

Re: [qooxdoo-devel] links to the qooxdoo application

Hi Voger As the second tab will be opened by a link, you won’t have a window to postMessage to/from and AIUI there is no way to get one. This means that the only way to communicate with the main application in the first tab is via the server - and the only way to do that is to poll the server

Re: [qooxdoo-devel] Download PDF from inside qooxdoo desktop

Hi Marcel If you want to suppress the popup blocker warning then the trick is to make sure that the window.open() happens as a direct result of the users click event – I’ve got this in one of my apps and it works fine on Firefox for a PDF download (the PDF opens in another tab, without a popup

Re: [qooxdoo-devel] Browser windows in an application

Hi Markus That’s only possible if you open the window with the URL of the second application and have that application compiled with the theme you want to use – you can’t send the widgets to the other window because browser security only allows postMessage between windows, and that’s

Re: [qooxdoo-devel] preloading all png images on application init

Hi Dietrich If you’ve got a list of what those asset uris are, you can use qx.util.ResourceManager.toUri() to convert each one into a full url which you can then pass to qx.io.ImageLoader.load to do the preloading. If you don’t have a list of assets uris you can get them through

Re: [qooxdoo-devel] preloading all png images on application init

Hi Dietrich If you’ve got a list of what those asset uris are, you can use qx.util.ResourceManager.toUri() to convert each one into a full url which you can then pass to qx.io.ImageLoader.load to do the preloading. If you don’t have a list of assets uris you can get them through

Re: [qooxdoo-devel] Integrating Babel into the generator chain

I think at the moment this is a tricky thing to do in a fully integrated way but doing it manually should be fine - you need to precompile your code using babel, and then run the generator. You wouldn’t need to run the generator every time (unless you add dependencies to your code), but

Re: [qooxdoo-devel] Using external libraries via a Qooxdoo library in your app

Hi Sanne There is a generator config key “add-script” which can be used to inject dependencies into the build – I’ve not used it myself but you can find the docs here: http://manual.qooxdoo.org/current/pages/tool/generator/generator_config_ref.html Regards John From: Sanne Peters

Re: [qooxdoo-devel] Synchronising row heights of two grid layouts

That’s a tough one to do easily I think; all the key details are private fields in q.u.l.Grid. It should be easy to hack something together though if the grids are also going to have an identical number of rows and columns. I’d copy the entire class, make the private fields public, and

Re: [qooxdoo-devel] qx.io.remote.Request queued but not queued and qooxdoo hangs

Hi Kenneth Can you reproduce this if you stubbed out the remote call, simulating the callback with a setTimeout()? From your descriptions I’m not clear on whether there is a problem in the request handling or the UI code, and if you could show that it has nothing to do with the server request

Re: [qooxdoo-devel] Text selection and mouse events in Chrome

Hi Dimitri I’ve been able to find the two stack traces that call preventDefault during a mousemove event, they are: anonymous(), qx.event.type.Native.preventDefault, qx.event.type.Roll.stop, qx.ui.window.Window._onMoveRoll, qx.ui.core.EventHandler._dispatchEvent,

Re: [qooxdoo-devel] Text selection and mouse events in Chrome

, but hopefully straightforward to track down and prove or disprove. Hope it helps anyway :) John From: John Spackman Reply-To: qooxdoo Development Date: Thursday, 15 October 2015 at 09:55 To: qooxdoo Development Subject: Re: [qooxdoo-devel] Text selection and mouse events in Chrome Hi

Re: [qooxdoo-devel] Firefox 40.x+ / Qooxdoo problems

Hi Matt I’ve had a few odd issues when debugging with Firefox and the source/source-hybrid builds that sound similar, although only when under the debugger and not every time. I couldn’t track it down but it looked at the time as though the scripts were loading in the wrong order, and I

Re: [qooxdoo-devel] Firefox 40.x+ / Qooxdoo problems

in them in order – however, it says that for parts the generator wraps the content with a closure to allow controlling the evaluation order, but this cannot (and does not) happen when loading from source. John From: John Spackman Reply-To: qooxdoo Development Date: Friday, 9 October 2015

Re: [qooxdoo-devel] Table "column selector" problem ... is this a bug?

Try this version: http://tinyurl.com/oxmqcd8 On 09/10/2015, 06:49, "kirra5" wrote: >Thank you for the reply, but the example is not working and I don't know how >to make it work (there is no dom element). > >So, is the issue with the popup a bug? Should I make a

Re: [qooxdoo-devel] Table "column selector" problem ... is this a bug?

Ah - I think that’s going to be a problem unless you override some fairly fundamental handling code; it’s been a while since I looked at it but as I recall the issue will be that the framework does not distinguish between different types of popup, IE even though from your point of view the

Re: [qooxdoo-devel] Future of Qooxdoo?

Hi Phyo While there are lots of things that could be changed (and I agree with quite a few of the points you and Saaj have made), my guess is that it’s largely an issue of “need" and human resource to make the changes. I think it’s also important to note that Qooxdoo as a framework is very

Re: [qooxdoo-devel] MultiUploader for qooxdoo , Based upon Zenesis uploadmgr

Hi Phyo I’ve just moved UploadMgr contrib to github (https://github.com/johnspackman/UploadMgr) - if you redo your gist as a pull request I’ll include it in the repo John From: Phyo Arkar Reply-To: qooxdoo Development Date: Friday, 25 September 2015 at 11:57 To: qooxdoo-devel Subject:

Re: [qooxdoo-devel] List filter is very slow

1500 items in a list is quite a lot, I’ve tried playing with your example but can’t find a way to speed it up. I would guess that there is some optimisation that could be done in ListController but that’s something you’d have to look into if you wanted to solve it. Another solution might be

  1   2   3   4   5   6   >