I have a qooxdoo application with an embedded svg element. (managed
by D3.js) it seem that the poor thing does not get any events
mouse events. Or almost none ... mouse-scroll events get through.
Any hints ?
cheers
tobi
--
Tobi Oetiker, OETIKER+PARTNER AG, Aarweg 15 CH-4600 Olten, Switzerland
w
I don't really know what the "usual" order is, but key,value seems a lot more
natural to me than value,key. After all, key=>value is always well defined
while value doesn't necessarily map to a single key.
Cheers,
Fritz
Fritz Zaucker
Oetiker+Partner AG
Aarweg 15
CH-4600 Olten
+41 62 775 9903
While we are at this topic:
I've just stepped into another 'inconsistency':
The 'forEach' methods of the Storage Classes[1] all call the callback function
with a 'switched' parameter signature.
Normally forEach-method callbacks have a signature of:
function (value, key, context)
while the stor
index.html is copied from source to build every time you build, so any changes
you make to index.html under source are always reflected in build.
On October 17, 2014 6:16:04 AM PDT, Sanne Peters
wrote:
>Hi Varol,
>
>Because the included script is used in the theme and the theme is run
>befo
Hi Varol,
Because the included script is used in the theme and the theme is run
before the code in the Application class and all your examples can only
be run when the Application class is loaded.
Unless I am wrong. If I am please explain why, because that would solve
my problem.
Secondly a c
Hey,
1st question I'd have is why would a include through the script tag not
be maintainable ? Seems odd.
Second there are a multitude of ways to include a script Using QooxDoo
you could use qx.bom.request.Script( );
A very simple function would be:
function require ( files, clb, ctx, pre ) {
Hi Mustafa,
I'll be sure to try that out, thanks for al the help!
Sanne
On 17/10/2014 13:20, Mustafa Sak wrote:
> Hi,
>
> all classes will be put together in one file on build version, even the theme
> classes. The generator will resolve the dependencies to your libraries, too.
> If you don't
Hi,
all classes will be put together in one file on build version, even the theme
classes. The generator will resolve the dependencies to your libraries, too. If
you don't want to use the full namespace of the library class inside your
theme, just use the @require[1] generator directive on top
I will gladly do!
Stefan
> Hi Stefan,
>
> You're right. This framework is growing over the last years with help of many
> developers
> with different paradigms and "styles" of programming.
>
> But with your help and the help of the community we can reach the goal to
> improve these interfaces
Hi Mustafa,
Does that mean that a qooxdoo library (say for example a vanilla
javascript library),
will be loaded before my custom defined theme if it has no real
dependencies?
Also:
"The generator will concatenate all used classes of libraries into the
application JS-file ordered by the depe
Hi Stefan,
You're right. This framework is growing over the last years with help of many
developers
with different paradigms and "styles" of programming.
But with your help and the help of the community we can reach the goal to
improve these interfaces
to become more heterogeneous. To reach th
11 matches
Mail list logo
