Beta Updates

Please add an answer to this issue whenever you release an update. Otherwise there is no way we notice there is an update available and must run the downloader every now and again.

The latest build includes the following fixes and additions:

We have just published a new build (1.1.90.0) including the following fixes and additions:

A new build (1.1.92.0) is available, including the following fixes/additions

Latest build (1.1.95.0) has just been uploaded. It includes the following fixes and enhancements:

A new build (1.1.98.0) has just been uploaded. Here´s the list of new fixes and additions:

Hi,

I just noted by chance that there is a new update (1.2.5) available. Could please keep us posted about the changes and additions?

Thanks!

Hi Markus,

I see your point. However during the beta phase we are updating the build several times, mainly to gather testers/bug reporters feedback
before we set open issues to “Complete”.

Then we post a list of issues together with an announcement of a new build.

Of course this will change once we are in “official release mode”. Then we´re going to separate into development/internal builds
and production builds.

Best regards
Frank

A new build with the following issues fixed has been uploaded.

A new build (1.2.8) is available and includes the following fixes and enhancements

A new Wisej build (1.2.9) has just been uploaded. It includes the following fixes and enhancements:

A new build is available (1.2.10). It includes the following fix and enhancement.
Please note the namespace change !

We have just uploaded a new build (1.2.11). It includes the following fixes and enhancements.
Please note additional information about that build.
Please also note that we are preparing a new automatic notification system for updates and release notes that will be available soon.And finally please be informed that all remaining open data grid view issues will be part of the new Wisej build.

A new build (1.2.14) with the following fixes/additions has been uploaded:

We´re happy to announce a new build (1.2.19). It includes the following fixes and additions:

A new build (1.2.22) is now available. It includes the following fixes:

We´re happy to announce a new beta build (1.2.25).

In addition to a rather large list of bug fixes (see below) you will find the following additions:

• Added Tools to TextBox (we will add it to the ComboBox as well, in our next update)
• The MonthCalendar control is now available, though not fully functional (selection and events don´t work yet)
• All themes have been updated to support the MonthCalendar plus some other fixes.
  –> Please redownload them as well !

A new build (1.2.31) of Wisej has just been uploaded with a lot of fixes and major improvements.

You will find the list of issues further below, please note the following additional information:

All themes have been updated.

General improvements in the Theme Builder. 

Massive UI speed improvement:

The core qooxdoo widget engine has been optimized significantly. Some tests showed an ever greater increase in time when creating many controls. The new optimized queues show a constant low time. When creating 500 controls we went from 3-5 seconds to about 250ms.

Wisej now only sends to the client the controls that have been made visible at least once. This optimization greatly increases the performance when creating complex forms with tabs or hidden panels. It makes no difference to the server side code. All extenders (tooltip, javascript, etc.) have been updated to wait for a control to be created to extend it.

The core UI flush – the javascript that renders the DOM – has also been improved. The standard flush uses a single animation frame. It is slightly faster to complete but causes long frames in the browser (small freeze). An alternative more “frame friendly” flush can be turned on by adding “options”: {“optimizeFrames”: true} in the application json file. This option should make the rendering a bit more fluid. This new flush method will be improved further.

Additional changes:

Changed RemoveAll() to Clear() in all property extenders.

Several bug fixes in all property extenders when disposing the component or detaching controls.

A new build is available.

Most of the fixes are around focus management, validation, cleaning up the code, and closing loose ends.

We are going to slow down for a couple of weeks due to vacations. However, urgent fixes and nightly builds will still be uploaded.

Most of the effort at the moment is going to completing the minimum control set and the last missing control is the ListView. It’s very close to being ready. It uses the qooxdoo virtual infrastracture (similar to the datagrid) and it’s able to render an unlimited number of items by creating only the visible dom elements. I have seen it scrolling 1M items without slowing down.

1.2.39.0 Update

Sorry, it’s not fully tested. Still short until Monday.

Breaking Changes

– The ToolClick event and OnToolClick method have been changed to be consistent with the .NET event system. Now the sender is the control that owns the tools, and the args is an instance of ToolClickEventArgs with a property named Tool that is a reference to the ComponentTool widget that was clicked. Known issue: The tool button must have a name or it’s not detected correctly by the event.

– The property Application.Context has been removed. There is no need to save and restore the context for out-of-bounds real time updates.