![]() ![]() Added new 'dragHandle' and 'style' attributes.Added support for adding input elements to the row facet.Now supports any values of any type (not just Strings).Added new "varyBarColor" attribute to allow bars of different colors within the same series.Now supports exporting the chart image to the server.Added HTML5 'placeholder' attribute support.Removed the previously deprecated attribute "run".The ACE Component TLD documentation now includes the default execution and rendering scope for each client event, as well as the default client event for each component.Changed the default execute scope to instead of for the following components/events: ace:linkButton/action, ace:maskedEntry/valueChange, ace:menuItem/action, ace:printer/action, ace:pushButton/action, ace:radioButton/action, ace:autoCompleteEntry, ace:richTextEntry, ace:menuItem.The "activate" event will continue to function as an alias to the new "action" event for backwards compatibility: ace:checkboxButton, ace:dataExporter, ace:linkButton, ace:menuItem, ace:printer, ace:pushButton, ace:radioButton. The default ajax event for the following Action components has been changed to 'action' (instead of 'activate').The default "execute" value has been changed to instead of Changed the default client event to "valueChange" for the following Input components: ace:autoCompleteEntry, ace:richTextEntry, ace:textAreaEntry, ace:textEntry.To better align with standard JSF 2.2 f:ajax and client event behaviors, the following changes have been made:.Removed previously deprecated attributes "cache", and "dynamic".Reduced JavaScript resource footprint and optimization, only loads the resources you need for the components you are using.See the ACE Components Wiki for reference documentation on these components. Existing applications that use those components will need to be migrated to use the ACE and/or MOBI components.Įxisting ICEfaces applications will need some degree of adaptation to work correctly with this release, the scope of which will depend on the specific features and components that they leverage from prior ICEfaces releases. Rather than invest the engineering resources to bring these up to spec for JSF 2.2, we decided to focus our energies on further evolving the newer ACE and MOBI components. Most of these components rely on an earlier ICEfaces Direct-to-DOM rendering technique that isn't compatible with many newer JSF features, such as partial-page rendering (f:ajax). ![]() ![]() The most significant change is that the legacy ICE (Compat) components have not been brought forward into the 4.0 release. ICEfaces 4.0 is a major version release and as such adds, removes, and changes a significant number of features and APIs. ICEsoft Maven Repository and Maven Central Repository.ICEfaces is available for download in the following formats: Extensive updates to the ICEfaces Showcase sample application, including new ICECORE and Mobile Components demos.Use of the Mandatory Resource Configuration scheme for dynamically loaded components no longer required.Enhanced ICEpush library, now supports Cloud-Push capabilities.Targets (and requires) JSF 2.2 and supports features such as HTML5 pass-through attributes, f:ajax reset, etc.4 new ICECORE components, with additional JavaScript APIs for ICEfaces bridge features.25 new integrated ICEfaces Mobile Components (MOBI), including Native device support via BridgeIt.Can you please provide the alternative code for the below.ICEfaces 4.0 is an official ICEfaces major release. I can able to run the project in Icefaces 3.3 But some of the functionality was not working properly. I am very new to Icefaces, so pardon me if I ask any silly questions. This is the first time I am doing this conversion process and facing lots of difficulties. I have a project to Migrate icefaces 1.8 to 3.3. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |