Hi,
Christian I've to thank you once again for your help. That it's exactly what
I want.
Now I think I understand how to do the communication between modules.
I'll try to implement it in my project.
Ana Rita
2011/5/10 panyasan <i...@bibliograph.org>
>
> 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 "Sandboxes": you can play there without doing damage to anything
> else), and must not be shared with anything.
>
> C.
>
> --
> View this message in context:
> http://qooxdoo.678.n2.nabble.com/qcl-access-demo-application-tp6295025p6349274.html
> Sent from the qooxdoo mailing list archive at Nabble.com.
>
>
> ------------------------------------------------------------------------------
> Achieve unprecedented app performance and reliability
> What every C/C++ and Fortran developer should know.
> Learn how Intel has extended the reach of its next-generation tools
> to help boost performance applications - inlcuding clusters.
> http://p.sf.net/sfu/intel-dev2devmay
> _______________________________________________
> qooxdoo-devel mailing list
> qooxdoo-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
>
------------------------------------------------------------------------------
Achieve unprecedented app performance and reliability
What every C/C++ and Fortran developer should know.
Learn how Intel has extended the reach of its next-generation tools
to help boost performance applications - inlcuding clusters.
http://p.sf.net/sfu/intel-dev2devmay
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
