Futurescale, Inc. PureMVC Home

The PureMVC Framework Code at the Speed of Thought

Over 10 years of community discussion and knowledge are maintained here as a read-only archive.

New discussions should be taken up in issues on the appropriate projects at https://github.com/PureMVC

Pages: [1]
Author Topic: Multiton Module Demos and Interfaces, why does the view implement?  (Read 5070 times)
Posts: 8

View Profile Email
« on: June 20, 2008, 01:16:31 »


I am using the Module Pipeworks and Modularity Demos as a reference guide, and I saw in the Shell Views that they implement the interfaces that communicate to the Modules.

Is there any reason why its the View and not the Mediator for the Shell View?

The reason I ask is that I am making a module based project, which has a login in the shell, and basically after login, the shell will get the user roles, and load up modules... each module will need to know the user roles, so I have a getUserRoles() to be able to retrieve the user roles.. However I had not planned on storing the roles in the View Component, as its already in the Model Proxy.

Is there another approach to implementing the ModuleShell Interface that has the ability to retrieve data from the Proxies?


« Last Edit: June 20, 2008, 01:36:30 by mark_ellul » Logged
Global Moderator
Hero Member
Posts: 2871

View Profile WWW Email
« Reply #1 on: June 20, 2008, 06:26:35 »

Sure, you can do whatever you want in reponse to a method call from the module.

Pages: [1]