Wavemaker 6.1, el mejor entorno de desarrollo

Wavemaker es el mejor entorno de desarrollo web-java que he encontrado, y viene con todo, seguridad, CRUD en 5 minutos, bonito y editable CSS, drivers con Oracle, Mysql, postgresql, muchos widgets y mas, de veras lo recomiendo

WWW.WAVEMAKER.COM



WaveMaker 6.1 Release Notes

Studio Upgrade - Clear Browser Cache

When upgrading to a newer version of studio, clear your browser cache before using the new studio.
Clearing your browser cache avoids issues from cached libraries from previous studio versions. This is only need for studio users, not users of deployed applications.
Performance
Dynamic Widget Loading
New Editor Widgets
Gzipped JavaScript
Install and Enable Chrome Frame on IE Feature
Index.html Meta Tag to use GCF
Index.html code to install GCF
Config.js Install Prompt
Studio now uses GCF
GZipped resource folder
CSS Optimizations
Other Optimizations
Application Memory Usage
New Widgets
Dojo Widgets
Dojo Rich Text Editor
Dojo Fisheye
Dojo Lightbox
New Editors
Rounded Style Widgets
Rounded Tabs
Rounded Panel
Rounded Button
Busy Button
Twitter Feed
Templates
Centered Page Container Template
Fancy Centered Template
New Widget Properties
Autoscroll
AutoSize
MinHeight and MinWidth
Max Results for Service Variables
Select Editor ability to enter new value
Select Editor - has down arrow
PageContainer loadParentFirst
DataServices
Improved SVN integration
Updated Query Editor UI
Preserve Database Table order
Data Model Editor improvements
Related Editor Improvements
Default Form Field
Lookup Mode
Nested Related Editors
All Fields no longer auto added
Editable mode removed.
To Many Mode
Deployment
EAR file generation
Deploy to Amazon EC2 updated AMI
Runtime Version File
Fixed Bug Lists
Changes from previous release.
Compatibility
Automatic Upgrade
Style Changes
Page Names starting with lower case letters
Load Parent First Property for Page Containers
Deprecation of Service Variable onSuccess inData
Default Runtime Layer
Justified alignment of panels/containers is now deprecated
Known Issues
Performance

The primary objective for WaveMaker 6.1 is to improve performance. WaveMaker 6.1.0 should provide significant performance improvements for most applications. The following improvements have been implemented in the DevBuild.

Dynamic Widget Loading

In WaveMaker 6.1.0 the amount of JavaScript code uploaded to the browser has be significantly reduced. As a result the initial load of the application may be much faster. In early testing we are seeing between 50 to 500% increases in performance, depending on the application.

In earlier versions, all widgets were included in a single file that was upload to the browser when the application started, slowing initial load. Reload of the application was faster since the file was cached but the browser still had to parse a very large JavaScript file. In WaveMaker 6.1.0 widgets are packaged in a number of files. The files are only loaded in the browser if a widget in the file is used by the application. A base package is included in all applications which provides the logic to dynamically load the widget files as needed.

Debug will continue to load all widgets so it is important that testing is performed in non-debug mode. Specifically, WaveMaker recommends you use the Run button in addition to the Test Run button to ensure dynamic loading works properly in your application.

New Editor Widgets

WaveMaker 6.1 provides a new set of editor widgets, which are ~50% faster than previous editor widgets. The new widgets are available in the Beta section of the palette. For backward compatibility the original editors remain in WaveMaker 6.1. The original editors are available in the Editors section of the palette.
The new editors can be easily distinguished by the class name. The class names drop "Editor". Example:
wm.Text -- New Text Editor
wm.TextEditor -- Original Text Editor
Javascript access to the new editors no longer requires you to reference a .editor property, unless you are trying to access the underlying dojo dijit.
Gzipped JavaScript

The JavaScript files provided with WaveMaker have been gzipped to further reduce the size of files uploaded to the browser.

Install and Enable Chrome Frame on IE Feature

Google Chrome Frame (GFC) is an add on for Internet Explorer (IE) that provides the Chrome JavaScript Engine as a plugin to IE. WaveMaker applications use JavaScript extensively. Internet Explorer (IE6, IE7, and IE8) browsers include inefficient JavaScript Engines. Adrian Kingsley-Hughes of ZDNet reported that Google Chrome Frame boosts IE speed up to Chrome levels and summarized as follows:

IE7 using Chrome Frame is about 40 times faster at running through the SunSpider JavaScript benchmark test than IE7 alone.
IE8 using Chrome Frame is about 10 times faster at running through the SunSpider JavaScript benchmark test than IE8 alone.
Other publications have reported similar results. In addition, memory management is far more efficient when GCF is enabled. In our testing, browser memory remains constant through progressive executions of an application while growing significantly in IE. Our tests also showed that IE scales poorly. As a page becomes more complicated with more widgets and/or more data, IE slows. Each additional widget or data takes longer than the previous. GCF exhibits linear performance.
Based on these test results WaveMaker strongly recommends that IE users install GCF. Apps built with WaveMaker will perform and behave much better on IE if the Google Chrome Frame plugin is installed.

WaveMaker 6.1, beginning with 6.1.5 (DevBuild 6) now uses GCF if installed. WM 6.1 also includes an optional feature such that a WaveMaker app will detect IE and suggest the user install Google Chrome Frame, if it is not already installed.

Index.html Meta Tag to use GCF

Newly created projects in WM6.1 will generate an Index.html with the chrome frame tag,


This enables IE browsers to take advantage of chrome frame if already installed.
Existing projects will need to manually add this tag to use chrome frame if present. This tag can be used with any project and does not require WM 6.1

Index.html code to install GCF

The index.html file of new 6.1 projects also includes additional JavaScript code that enable the Chrome Frame installation prompt to the user. The prompt is not shown unless the flag in config.js is set to true.

Config.js Install Prompt

Newly created projects will generate a Config.js that includes a "wm.checkGoogleFrame" flag. The flag defaults to false.
If you set this flag to true, IE users will be prompted to install Chrome Frame. Users will need administrative rights on the browser computer to install Google Chrome Frame. The prompt looks like this when the user first visits the app. If the user declines, a cookie is set to avoid further prompts for 365 days.

Existing project config.js will not be changed. This feature depends on components that are new to WM6.1 and thus requires WM6.1. See retrofitting GCF install prompt for information about adding this feature to upgraded projects.

Studio now uses GCF

Studio now includes this meta tag. Studio will now load in Chrome Frame for users with GCF enabled.

GZipped resource folder


In a project's resources folder, there is now a "gzipped" folder. JS files in this folder will be served as compressed. Use compression to reduce the size of your js files transferred across the wire.
Example folder structure:

resources
gzipped
gzip1.js
gzip2.js
folderA
gzip3.js

To load gzip1.js and gzip3.js you will have to use the following command:
wm.gzScriptLoader('gzip1');
wm.gzScriptLoader('folderA.gzip3');

The gzipped folder is registered with the file controller. Users will have either just specify the fileName(if file is in /resources/gzipped folder) or specify path using dot (.) notation for further folder hierarchy (in case of gzip3, which is actually in resources/gzipped/folderA/gzip3 hence, "folderA.gzip3" ).
CSS Optimizations

The applying and rendering of CSS has been optimized. Improvement in performance varies by usage. While most improvement is expected to be modest, some reports have been dramatic.

Other Optimizations

In addition, WaveMaker 6.1.0 includes many small optimizations. These improvements have yielded performance benefits of 3-7%, depending on the application.

Application Memory Usage

WaveMaker 6.1's memory usage has been rigorously analyzed. Applications running inside efficient JS engines such as those in Chrome, Safari and FireFox show little to no memory growth in tests. Results are dependent upon both the specifics of the application and the browser used. Developers should continue to be careful about any allocations from their custom code.

New Widgets

Dojo Widgets

Dojo Rich Text Editor

The a dojo dijit based rich text editor joins the new editors palette section in 6.1.7. Class name is wm.RichText

Dojo Fisheye

A dojo fisheye widget, wm.DojoFisheye, has been added to the palette.
Dojo example (top of page)
Example WM Project

Dojo Lightbox

A dojo lightbox, wm.DojoLightBox, has been added to the palette.
Dojo example (select wide image, square or wide image]

New Editors

A new version of dojo dijit editors, Text, Date, Number, etc, appears on the palette under new editors. These editors have the same functionality, but have been reworked for improved performance. See new editor widgets

Rounded Style Widgets

Rounded Tabs

The Tabs Layer (wm.TabLayers) now defaults to rounded style tabs. The original tab styling is available by changing the 'layers type' to 'Tabs'

Rounded Panel

A panel with rounded corners and title bar

Rounded Button

A rounded style button (wm.RoundedButton) has been added to the palette.

Busy Button

Busy button invokes a service variable and indicates the busy status while the service variable is in flight.
Assign the clickVariable property to the service variable to be used. NOTE: This widget is not working properly in 6.1.6 Beta

Twitter Feed

A twitter feed widget, wm.TwitterFeed, has been added to Web Content

Templates

Centered Page Container Template

WaveMaker recommends use of pages and a page container for any application with more than small amounts of components. If an application has more than two layers, it should be using pages.
To help developers get started quickly with this layout, a Centered Page Container template complete with header and footer panels has been added to the palette templates.

Fancy Centered Template

A centered rounded content window with a grey surround, header and footer panels.

New Widget Properties

Autoscroll

Scrollbars will display only when the contents of the container is larger than the size of the container. WaveMaker recommends using either Autoscroll or ScrollX/ScrollY but not both. It is possible that ScrollX/ScrollY will be deprecated in a future version.

AutoSize

Containers will resize to fit their content and labels/wm.html will automatically size to their text.

MinHeight and MinWidth

Prevents % sized widgets from shrinking below the set minimum.

Max Results for Service Variables

Service variables now have the following properties for use with HQL queries or Java Service methods returning lists.
maxResults
designMaxResults
Select Editor ability to enter new value

Select editors now have a property named restrictValues. The property defaults to true, which means the only legitimate values are those in the pulldown menu. If the value is set to false, a user can type in any value and have it be accepted (displayValue == dataValue if an arbitrary value is entered). This property exists in new and old Select editor

Select Editor - has down arrow

When disabled, select editors do not display the down arrow to the right of the field.
This is often used with type ahead enabled select editors.

PageContainer loadParentFirst

Page containers now have a load parent first property. Default is enabled.
When enabled, the parent page will load and display before the page container page is loaded, providing a better application load experience for users.

Existing projects always load the page in the page container before the parent is completely loaded. When an existing project is upgraded to 6.1, this property is enabled which inverts this behavior causing the parent page to load before the page container's page is loaded and may cause problems if custom code was implemented in the parent page expecting the page container's page to be loaded. If the upgraded project experiences problems loading pages into page containers, disable this property and try it again.

DataServices

Improved SVN integration

WaveMaker no longer deletes the .svn directory when a data model re-import is performed, allowing SVN to manage and maintain the changes. Timestamp comment in dataservice java classes no longer updated by run or recompile.

Updated Query Editor UI

Query Editor now accepts test values for each input parameter. Improves support for list inputs. (HQL IN List)

Preserve Database Table order

Grids and LiveForms created on LiveData Services now preserve database table order providing a more logical default order. Previously alphabetical order was provided.

Data Model Editor improvements

We have added a schema evolution capability allowing you to modify a table definition without deleting existing tables and data. Bugs that limited the functionality of the Data Model editor have been fixed.

Related Editor Improvements

In addition to correcting many of the known issues with related editors, 6.1 improves the design time (studio) usage of related editor with smarter defaults and creation logic.

Default Form Field

The first relation is automatically set for the formField. Simply change the formField as desired.

Lookup Mode

Lookup is now the default for "to 1" relations. Only the lookup editor is added by default. Use 'addEditor' to add additional editors for additional field display. Change the form field property for the desired field. Add Editor will progress through the fields one by one.

Nested Related Editors

Related Editors can now be nested for related data to related data.
In a model where Address -> City -> Country
A related editor for Country can be added to the related editor for City.

All Fields no longer auto added

Related editors no longer auto add every related entity field to the related editor, lookup, editable or grid. Use the 'Add Editor' or 'add Column' (for grid) button to add any desired editors. Add editor adds one editor at at time. The form field defaults to the next field and can be changed using the formField property.

Editable mode removed.

Editable editing mode is for editing the related instance. This is generally only desired on 1:1 relations and often has constraint constraints. Users seeking to edit related data should use a live form on the related table directly.

To Many Mode

A read only grid with the first field is now the default for to many relations.

Deployment

EAR file generation

In addition to generating a WAR file, WaveMaker now also generates an EAR file. The EAR file is generated when you select the Generate WAR option from the deployment screen.

Deploy to Amazon EC2 updated AMI

The Deploy to EC2 option AMI has been updated. Details at: Deploying to Amazon EC2

Runtime Version File

The Runtime now includes a WMVersion file indicating the WM version the application is deployed upon.
The information is accessed via /lib/WMVersion. The file is copied in from the version of WM generating the application and indicates the runtime version the application is deployed with.
Example:
For an application running at http://demo.wavemaker.com/HQL_Guru
use:
http://demo.wavemaker.com/HQL_Guru/lib/WMVersion to see the version information.

Fixed Bug Lists

All 6.1.x Versions:
All Closed Issues

By pre-release version:
6.1.9 GA
6.1.8 Beta
6.1.7 Beta
6.1.6 Beta
6.1.5 DB6
6.1.4 DB5
6.1.3 DB4
6.1.2 DB3
6.1.1 DB2
6.1.0 DB1

Changes from previous release.

Compatibility

Automatic Upgrade

WaveMaker 6.1 increments the project version in .wmproject.properties file. An upgrade script to upgrade earlier projects is automatically run upon opening the project in the new version of studio. The upgrade process creates a copy of your original project before upgrading so you can revert back to your original project if needed.

The upgrade script from WM606 makes updates to project-springapp.xml and web.xml. Changes include enabling Dynamic Widget Loading and Gzipped JavaScript.
Chrome Frame changes to index.html and config.js are not part of the upgrade script and should be manually applied if desired. See retrofitting Chrome Frame for details.

Style Changes

Existing projects migrated to WM61 may wish to retain the pre-WM61 styling. Some components now default to the new style. Information on using preWM61 styles in WM61 is available in the pre-WM61 style page.

Page Names starting with lower case letters

Newly created pages will not be created starting with lower case characters.

Load Parent First Property for Page Containers

This is a new property for page containers and is enabled by default for new and upgraded projects. If code in the parent page expects a subpage to be loaded at start time, this property may need to be disabled.

Deprecation of Service Variable onSuccess inData


In JavaScript onSuccess functions for Service Variables, inData is deprecated.
JavaScript functions should begin using inSender.getData() instead.
Usage:
inSender.getItem(item) - returns a wm.Variable for that item
inSender.getData() - returns a structure of basic objects, same as inData (data only objects)

Default Runtime Layer

wm.Layers no longer creates a default layer at runtime if it has no layers. Design time in studio will continue to create a default layer. This change affects users creating and managing layers dynamically at runtime.

Justified alignment of panels/containers is now deprecated

This property was removed as an explicit option in WaveMaker 5.0, however it has still been supported in older projects. We now add deprecated warnings anytime a justified alignment is used when in design mode. It will continue to work at runtime, but will be removed in a future release.

Known Issues

Some of the known issues of particular interest are listed below. For all known issues in the release, see Jira

Query Editor cleared of queries in test/edit cycle
Inconsistent Date/Time handling across time zones
Related Editor data set cleared
Regeneration of Edit Panel upon changing button style