arsousa wrote:
>
> sandbox X -> sandbox Y (public)
>
And please note that by definition, Sandboxes cannot be public. They are
passed to the modules and are for the module's very private usage, in fact,
they are the only access to the rest of the application (that's why they're
called "Sandboxe
arsousa wrote:
>
> I just want to know the best way to do that. I know that no module is
> allowed access to other modules, so module have to publish "something"
> in sandbox, but then what should sandbox do?
>
> sandbox X -> Core -> Sandbox Y
> or
> sandbox X -> sandbox Y (public)
>
>
The S
arsousa wrote:
>
> I've already see the slides and in slide 53 says "The application core
> manage communication between modules".
> So I assumed the communication between modules should be something like
> this:
>
> Module X -> Sandbox X -> Core -> Sandbox Y -> Module Y
>
> But then I saw some
arsousa wrote:
>
> I've already see the slides and in slide 53 says "The application core
> manage communication between modules".
> So I assumed the communication between modules should be something like
> this:
>
> Module X -> Sandbox X -> Core -> Sandbox Y -> Module Y
>
> But then I saw some
Hi
Sorry for not responding to your question, yes i'm using qooxdoo 1.4
Thanks a lot, these advise will help me a LOT.
Regards
2011/5/10 thron7
> If you're on 1.4 (you didn't answer this question), you might use the
> "source-hybrid" job. It will create a version of your app into your
> source/
Tristan,
The caption bar doesn't resize for me when i use a different icon or when i
use the technique you mention. the icon does get bigger, but it does not
adjust the caption bar.
Victor
> Message: 6
> Date: Tue, 10 May 2011 08:26:02 +0200
> From: Tristan Koch
> Subject: Re: [qooxdoo-devel]
Hello Thomas,
Thank you for your reply.
I've already see the slides and in slide 53 says "The application core
manage communication between modules".
So I assumed the communication between modules should be something like
this:
Module X -> Sandbox X -> Core -> Sandbox Y -> Module Y
But then I sa
I haven't followed this whole thread, so maybe I missed it, but this
might be interesting: N.Zakas on scalable JS architecture:
http://developer.yahoo.com/yui/theater/video.php?v=zakas-architecture
(Slides are on slideshare).
T.
On 05/10/2011 06:02 PM, Ana Rita Sousa wrote:
> I've already under
I've already understand the logic which module only access to the sandbox
and the sandbox have access to the core.
But in major web applications modules needs information about each others.
For example an event is fired in module x that have to execute something in
module y.
In my project for insta
arsousa wrote:
>
> Each module should only to communicate with it sandbox, using methods like
> subscribe and publish. So if a module need communicate with the others,
> the
> sandbox will do that job.
> But my point was how should sandbox do it?
> As far as I could understand until now, one way
Each module should only to communicate with it sandbox, using methods like
subscribe and publish. So if a module need communicate with the others, the
sandbox will do that job.
But my point was how should sandbox do it?
As far as I could understand until now, one way to do that is to turn public
th
Hi,
could you please post the locator you're using to find the table?
Regards,
Daniel
On 05/10/2011 02:16 PM, ziepf wrote:
> Hi,
>
> the problem still exists also with the news user-extensions.js
> my python script displays an error:
>
> "Couldn't find table clipper widget: Error: Qxh Locator:
Sure. But that was just for demonstration.
I will try to explain more detailed.
Qx.io.remote.Rpc._callInternal()
Line 444: var argsArray = [];
In Build version argsArray has automatically .toJSON() function, in source
not
Qx.util.Json.__convertObject()
Line 420: if (qx.lang.Type.isFunction(inco
Hi,
the problem still exists also with the news user-extensions.js
my python script displays an error:
"Couldn't find table clipper widget: Error: Qxh Locator: Error resolving
path"
Hope that helps.
regards
ziepf
--
View this message in context:
http://qooxdoo.678.n2.nabble.com/Selenium-sea
You should never use for-in with arrays! See the archive/internet for
explanations.
T.
On 05/10/2011 12:41 PM, Mustafa Sak wrote:
> Hi List,
>
> I am confused! I am using rpc.callAsync functions, but my requests just
> get me errors at build version. After checking that issue with firebug I
> co
John,
great. Derrell has meanwhile been busy thinking about similar issues
(bug#5095). I'll see how these things converge, and will add comments to
the bug.
T.
On 05/10/2011 11:12 AM, John Spackman wrote:
> Hi Thomas,
>
> I've finally got round to doing this - the bug report is
> http://bugzil
Hi List,
I am confused! I am using rpc.callAsync functions, but my requests just get
me errors at build version. After checking that issue with firebug I could
see, that the params key has two dirrent values at build and source version
Source (the correct way)
params : ["test"]
Build
Hello Christian,
Thank you once again for this further help.
I'm studying your samples at the moment and trying to apply to my case.
I'm going to do some experiments with my code and after that give some
feedback.
Ana Rita
2011/5/9 panyasan
> see the methods:
>
>
> http://cboulanger.
Since we're at it, I really would like to hear from others (if there is any
interest at all, of course), how they would implement this architecture the
qooxdoo way.
How, for example, would one deal with building the UI parts of the modules?
If we're serious about not using the global namespace, a
Using a VirtualSelectBox or SelectBox the input data model must be like a
list. For your model json to be consider like list should be structure like
this:
http://demo.qooxdoo.org/current/demobrowser/#data~JsonToList.html
http://demo.qooxdoo.org/current/demobrowser/resource/demobrowser/demo/data/
Hi Thomas,
I've finally got round to doing this - the bug report is
http://bugzilla.qooxdoo.org/show_bug.cgi?id=5100 and includes a custom
loader and include file for config.json. There's no patches to the core
framework required but the bug report has a proposal for some potentially
useful chang
If you're on 1.4 (you didn't answer this question), you might use the
"source-hybrid" job. It will create a version of your app into your
source/ folder, wiht your app classes taken from the source/class path,
but all other classes (qooxdoo framework, other libraries/contribs you
are using, ...
Hi Tristan
Thanks for the help... I think it was too late yesterday to see this
easy problem with the return value *arg*.
About the link, I'll remember it for the next time!
Daniel
Am 10.05.2011 07:55, schrieb Tristan Koch:
> Hi Daniel,
>
> the data event you receive in your listener for the "c
23 matches
Mail list logo
