Details
-
Type:
Improvement
-
Status: Closed
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: EE-3.3.0.GA_P02, 4.0
-
Fix Version/s: EE-4.0.0.GA, EE-3.3.0.GA_P03, 4.1
-
Component/s: ACE-Components
-
Labels:None
-
Environment:All
-
Assignee Priority:P2
-
Support Case References:Support Case #13250 - https://icesoft.my.salesforce.com/5007000000zO4AD
Description
Feature Request: Add a way to notify the server when a gMapEvent is triggered.
Note on this behavior from Art:
Implement an actionListener on the ace:gMap component that would fire whenever a Google Maps event, registered via ace:gMapEvent, is triggered. The listener method would receive a special event object that would contain a reference to the gmap component object and a reference to the subcomponent that triggered the event, in this case a marker.
In rough terms, it would work like this:
<ace:gMap eventListener="#{bean.gMapEventListener}" .... >
<ace:gMapMarker latitude="0" longitude="0">
<ace:gMapEvent eventType="click" scriptToUse="/* client-side code */"/>
</ace:gMapMarker>
</ace:gMap>
public void gMapEventListener(GMapEvent event) {
event.getGMap();
event.getComponent();
event.getType();
}
This way, it would be necessary to only write one listener method and it wouldn't be necessary to write additional javascript code to send the request to the server.
Note on this behavior from Art:
Implement an actionListener on the ace:gMap component that would fire whenever a Google Maps event, registered via ace:gMapEvent, is triggered. The listener method would receive a special event object that would contain a reference to the gmap component object and a reference to the subcomponent that triggered the event, in this case a marker.
In rough terms, it would work like this:
<ace:gMap eventListener="#{bean.gMapEventListener}" .... >
<ace:gMapMarker latitude="0" longitude="0">
<ace:gMapEvent eventType="click" scriptToUse="/* client-side code */"/>
</ace:gMapMarker>
</ace:gMap>
public void gMapEventListener(GMapEvent event) {
event.getGMap();
event.getComponent();
event.getType();
}
This way, it would be necessary to only write one listener method and it wouldn't be necessary to write additional javascript code to send the request to the server.
Activity
Field | Original Value | New Value |
---|---|---|
Fix Version/s | 4.1 [ 11375 ] | |
Fix Version/s | EE-3.3.0.GA_P03 [ 11572 ] |
Assignee | Arturo Zambrano [ artzambrano ] |
Assignee Priority | P2 [ 10011 ] |
Fix Version/s | EE-4.0.0.GA [ 11171 ] | |
Fix Version/s | 4.1 [ 11375 ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #44006 | Tue Feb 03 17:48:07 MST 2015 | art.zambrano | |
Files Changed | ||||
![]() ![]() ![]() ![]() ![]() |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #44009 | Tue Feb 03 17:52:15 MST 2015 | art.zambrano | |
Files Changed | ||||
![]() |
Status | Open [ 1 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Resolution | Fixed [ 1 ] | |
Status | Resolved [ 5 ] | Reopened [ 4 ] |
Repository | Revision | Date | User | Message |
ICEsoft Public SVN Repository | #44017 | Thu Feb 05 15:53:17 MST 2015 | art.zambrano | |
Files Changed | ||||
![]() |
Status | Reopened [ 4 ] | Resolved [ 5 ] |
Resolution | Fixed [ 1 ] |
Fix Version/s | 4.1 [ 11375 ] |
Status | Resolved [ 5 ] | Closed [ 6 ] |
r43999: added server-side listener to ace:gMapEvent in the 3.3 EE maintenance branch.
The final approach changed from the original idea, to make it more convenient and usable. Instead or registering a single listener in the root ace:gMap component, the listener is registered in each individual ace:gMapEvent component. This way, it's not necessary to write code to identify which event component triggered the event.
Things work this way now:
The code above can be integrated into the /gMap/gMapEvent.jsf test page.