Hi all,
the *#asset* compiler hint solved my problem.
Thank you.
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/qooxdoo-build-does-not-include-folder-with-images-tp7583593p7583625.html
Sent from the qooxdoo mailing list archive at Nabble.com.
--
On 17.05.2013 08:25, Markus Schneiders wrote:
> Hi Daniel,
>
> thanks for your answer. I will take a look into your Implementation. Perhaps
> I port this into C# and make my own implementation. Is this OK for you?
Sure, let me know if you have any questions about the implementation. If
you deci
> Hi all,
>
> the *#asset* compiler hint solved my problem.
>
> Thank you.
No, no, I won't let you get away so soon. If your code was missing #asset
hints then your source version should have *at least* warned you in the
browser that you are using "unmanaged" images. But you said you had no
warnin
Any other suggestions? I'm still looking for solution and would appreciate
any help.
Thanks.
2013/5/16 Alexander Voronin
> Well, after code been implemented everything gone wrong. Perhaps
> screenshot will clarify situation.
> Here is again qx.ui.mobile.page.NavigationPage based page
> with qx.
Hi Andreas,
yes, you brought up some interesting and valid points regarding the blog post
in [3].
It would be great if you could report the enhancement-bug at
http://bugzilla.qooxdoo.org and also point to the blog post there. Our
framework team will then investigate the issue and you as the bu
Only if you insist!
The only warnings I was getting are of the following type:
Warning: Unknown property '-moz-border-radius-bottomleft'. Declaration
dropped.
Source File:
file:///home/user/prb/qooxdoo-2.0.1-sdk/tool/bin/app/build/index.html
Warning: Unknown property 'auto-complete'. Declarati
Hi T,
the last time you helped me with a problem where I just couldn't find any
warnings in source-version (firebug)
I had to put this in my config.json
"source-disposerDebug" :
{
"desc" : "source version with 'qx.debug.dispose.level' for destruct
support",
"extend" : [ "source
This looks very much like only CSS warnings. Is this from the browser
built-in console? You should either use the console of Firebug in Firefox,
or the lightweight console that comes with qooxdoo (hitting F7 in your
app, in the source version). What do you get?
> Only if you insist!
>
> The only w
Modal busy indicator and other popups is looks different in IE10 and other
browsers.
Since playground for some reason do not allow to create popups here is code
fragment I'm using to create those one onattached image.
__createWaitPopup: function(text) {
if (MobilePortal.UI.ToolBarPage._waitPopup)
My client get "strange feeling" about the form.List and list.List behaviour
regarding the Drag & Drop (only on mobile device, from Qooxdoo Desktop not
mobile one) :
Currently when you perform a drag & drop on mobile device threw Qooxdoo
Desktop, you have to first select the item by doing a full ta
Yes, thanks, that might be one of the next steps. I just want to make sure
first that we are looking at the same console :-).
> Hi T,
>
> the last time you helped me with a problem where I just couldn't find any
> warnings in source-version (firebug)
> I had to put this in my config.json
>
> "sour
Is there a way to detect onorientationchange event for page in mobile part
of qooxdoo sdk?
--
когда я опустился на самое дно, снизу мне постучали..
--
AlienVault Unified Security Management (USM) platform delivers complet
Yes, this is possible:
qx.event.Registration.addListener(window, "orientationchange", function(e) {
console.log(e);
}, this);
Am 17.05.2013 um 13:27 schrieb Alexander Voronin:
> Is there a way to detect onorientationchange event for page in mobile part of
> qooxdoo sdk?
>
> --
> ко
ok, this works pretty nice except one thing :)
Intercepting this event like described above causes UI to act like hell -
master page disappears, details page do not resizes, etc.
What should I do to keep everything like it was but noticed somehow know
about this event? I'd propose to add it to page
I can't tell what the problem is from the snippet you posted, sorry.
Here's the code I used to test my solution:
var page = new qx.ui.mobile.page.NavigationPage();
page.addListener("initialize", function() {
var addButton = new qx.ui.mobile.form.Button("Add widget to
embed"
Hi,
the follow is my snipplet code:
//
__arr : ['A', 'B', 'C', 'D', 'E', 'F'],
fillData : function() {
for(var k=0; khttp://p.sf.net/sfu/alienvault_d2d___
qooxdoo-devel mailing list
qo
On Fri, May 17, 2013 at 11:04 AM, fei wang wrote:
> Hi,
>
> the follow is my snipplet code:
>
> //
> __arr : ['A', 'B', 'C', 'D', 'E', 'F'],
>
> fillData : function() {
> for(var k=0; k var args = ...
> var req = new qx.
Another way to do it could be to store the value of k on the request
object (also untested):
var req = new qx.io.request.Xhr("/hrm/services/ActionServlet2", "POST");
req.setUserData("reqid", k);
req.addListener("success", function(e) {
var req = e.getTarget();
console.log(req.getUserData("
As i say, i don't blame anyone.
I thought that was some ninja special effective.
Thanks for you explanations.
Regards
2013/5/16 Derrell Lipman
> On Thu, May 16, 2013 at 10:17 AM, Benjamin Dreux
> wrote:
>
>> Hi
>>
>> I'm looking at qx.ui.table.Table source code.
>> And i've noticed this
>> t
Hi,
I've been digging on something which looks like a simple issue at first
sight : defining the constructor of a custom (subclassed) widget.
Basically, with qooxdoo 2.1.1 uncommenting the portion below regarding the
constructor seems to cause the subclassed widget not to appear. I have seen
such
Nevermind, problem solved by looking through the demobrowser code, the
constructor body has to be :
construct : function(label, icon)
{
this.base(arguments, label, icon);
}
Fred
On Fri, May 17, 2013 at 5:38 PM, Frédéric Ménez wrote:
> Hi,
>
> I've been digging on something which looks like a
My vote is tap => touchstart => drag
Cheers
--
Geovanny Junio
Consultor de Tecnologia
geovanny (at) eutsiv.com
+55 31 9422-8885
+55 31 2519-8603
www.eutsiv.com
Este e-mail pode conter informação privilegiada e confidencial. Se você não
é destinatário da
mensagem, por favor apague a mensagem e com
The answer is very useful for me.
Thanks a lot
On Fri, May 17, 2013 at 11:28 PM, Daniel Wagner wrote:
> Another way to do it could be to store the value of k on the request
> object (also untested):
>
> var req = new qx.io.request.Xhr("/hrm/services/ActionServlet2", "POST");
> req.setUserData("r
Hi
For information, i've got this when i'm using a json store
(debug.dispose.level = 2)
002110 Missing destruct definition for '_transport' in
qx.io.request.Xhr[undefined]: [object Object] Native.js:59
002111 Missing destruct definition for '__response' in
qx.io.request.Xhr[undefined]: [object Ob
Done:
http://bugzilla.qooxdoo.org/show_bug.cgi?id=7411
Thank you for further investigation.
As promised I've done some tests on my own with interesting and promising
results (have a look at the bug report).
Maybe off topic: While digging thru the framework code I found this snipped
inside Widge
thron7 and Marc, thank you guys for your answers! Seems like I had a
delusion that "qooxdoo sources should not be served via http" :) I've
configured my webserver and made corresponding changes to config.json,
and everything is ok now.
Regards,
Ripston
On 13.05.2013 at 1:24 PM, "thron7" wrote:
26 matches
Mail list logo
