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
|
|
|
Show Posts
|
Pages: [1]
|
3
|
PureMVC Manifold / MultiCore Version / Re: testing the framework
|
on: February 17, 2010, 01:17:23
|
You do not change the structure of the framework (PureMVC Multicore) if you want to compile it. But you can change the structure of the client code (for exemple: EmployeeAdmin) of your project.
Anthony.
|
|
|
4
|
PureMVC Manifold / MultiCore Version / Re: testing the framework
|
on: February 16, 2010, 10:07:24
|
Hi, if you change the structure of the folders by org/puremvc/java by org/puremvc/java2
then you must change <entry-point class="org.puremvc.java2.multicore.demos.gwt.EmployeeAdmin" />
and in each java source code you must modify the package and the import package org.puremvc.java.multicore.demos.gwt; import org.puremvc.java.multicore.demos.gwt.employeeadmin.ApplicationFacade; by package org.puremvc.java2.multicore.demos.gwt; import org.puremvc.java2.multicore.demos.gwt.employeeadmin.ApplicationFacade;
Anthony.
|
|
|
5
|
PureMVC Manifold / MultiCore Version / Re: Why doesnt this port use concurrentHashMaps?
|
on: February 10, 2010, 03:34:05
|
This port doesnt use ConcurrentHashMaps instead of HashMap+synchronized because PureMVC Multicore is GWT compliant. GWT includes a library that emulates a subset of the Java runtime library and this library doesn't have java.util.concurrent.ConcurrentHashMap
Thanks Jason, effectively, methods such as Facade.removeCore are not threadsafe and i have to release a new version with correct code.
Anthony.
|
|
|
7
|
PureMVC Manifold / MultiCore Version / Re: Events on GWT
|
on: June 19, 2009, 03:17:24
|
I think you should use :
submitCommand.addClickHandler(new ClickHandler(){ @Override public void onClick(ClickEvent event) { // this tells the Mediator to handle the new activity. Activity act = new Activity(descriptionInput.getValue(), typeInput.getValue(), dateInput.getValue());
sendNotification(ApplicationFacade.NEW_ACTIVITY, act); } });
@Override public final String[] listNotificationInterests() { return new String[] { ApplicationFacade.NEW_ACTIVITY }; }
@Override public final void handleNotification(final INotification notification) { if (notification.getName().equals(ApplicationFacade.NEW_ACTIVITY)) { activity = (Activity) notification.getBody(); doAddActivity(activity); } Anthony.
|
|
|
8
|
PureMVC Manifold / MultiCore Version / Re: EmployeeAdm demo for GWT.
|
on: June 19, 2009, 03:06:04
|
From the PureMVC_Implementation_Idioms_and_Best_Practices.pdf
The responsibilities for the Mediator are primarily handling Events dispatched from the View Component and relevant Notifications sent from the rest of the system.
Since Mediators will also frequently interact with Proxies, it is common for a Mediator to retrieve and maintain a local reference to frequently accessed Proxies in its constructor. This reduces repetitive retrieveProxy calls to obtain the same reference.
Anthony.
|
|
|
|
|
|