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 samples of this architecture in qcl context which > confusing a little bit > > this.__sandbox = sandbox; > var yyy = yyy.module.AccessControl.getInstance(); > if ( ! yyy.sandbox ) yyy.sandbox = this.__sandbox; >
Ok, now I understand, it is a piece from my code that I shared as example. That is an embarrassing dirty hack which should NOT be used as an example, it was simply done out of laziness in order not to have to create another module. Please disregard this, it has nothing to do with core-sandbox-module architecture. Hope that helps ;-) C. -- View this message in context: http://qooxdoo.678.n2.nabble.com/qcl-access-demo-application-tp6295025p6349051.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
