Hello Ana Rita, the idea is that the modules have only access to the sandbox for security reasons, so that no module can do bad things and wreck the application. Thus, the sandbox must necessarily provide everything the modules need to function. That is of course tricky - the sandbox API must be comprehensive, but also not bloated. I find that an interesting question - what does a typical widget need in order to function (build UI, handle events, communicate with backend).
Of course, modules need to be able to communicat. In my implementation, they communicate throught the sandbox using messages. They subscribe and listen to channels and perform actions dependent on the messages. They can even dispatch messages to the channels replicated on the server, thus reaching modules on other machines (think of a chat app). This way, behaviour is completely discoupled and apps break much less easily. Its a more complicated way of doings things, to be sure, but it has a lot of advantages... Cheers, C. -- View this message in context: http://qooxdoo.678.n2.nabble.com/qcl-access-demo-application-tp6295025p6345310.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ WhatsUp Gold - Download Free Network Management Software The most intuitive, comprehensive, and cost-effective network management toolset available today. Delivers lowest initial acquisition cost and overall TCO of any competing solution. http://p.sf.net/sfu/whatsupgold-sd _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
