There's a new build up on the web site this morning, and it contains the
following:

- The TGrid component now includes functionality for automatic sorting of
datasets by clicking on the column headers.  This works with bound grids
only.  There is also now a public Cells property that allows you to easily
get/set any cell using column/row coordinates.

- The TDataSet component editing is almost done, but not quite.  For
example, inserts work, but not updates/deletes or transactions/JSON.
There's also a new Find and Sort methods, and you can now use the RowID
property as an order-independent bookmark position.  In general, the dataset
should be wrapped up very soon.

- There are some fixes to some of the data-aware functionality of several of
the controls.

- There's a half-implemented THTMLObject component, don't use it yet.

- The IE issue with clicking on the label of check boxes and radio buttons
is fixed (again ).

- The OnChange event is working like Delphi now for input controls, but
still needs some work to handle cut/paste operations.

- The transparency of TLabel and TImage components now works properly at
design-time in the form designer, making layered interfaces with graphics a
lot easier to deal.

- There is now a tab ordering button/dialog available in the form designer
for easily modifying the tabbing order for container forms/controls.

- There's now a MaxLength property for all TEdit/TComboBox controls.

- There's now a new property called AllowEdit for TComboBox controls that
works like the csDropDownList option in Delphi's TComboBox.  Turning it
on/off will control whether you can type directly in the edit portion of the
combo box.

- The selected control anchors in the form designer were changed to squares.
I got tired of trying to deal with transparency issues with them when they
were rounded. I won't go into detail, but Windows wasn't designed for
dealing with transparent, handled child controls.

- The issue with compiling linked units is now fixed.  Paul Coshott reported
this one, and it had to do with a compilation error when you did this
(pretty common):

unit MyUnit1;

interface

uses MyUnit2;

implementation

end.

unit MyUnit2;

interface

implementation

uses MyUnit1;

end.

I had to rework the way that the compiler stages the compilation of the
interfaces and implementations.

- There's bunch of minor fixes in the compiler, including a pretty big
performance improvement in the emitting stage.

- The EException classes (and descendants) are now gone from the framework.
Most JS engines in the popular browsers have an issue with how they report
error messages from any Error core exception object descendants, basically
making such functionality worthless (even though it worked fine as far as
EWB is concerned).  The framework now simply uses:

raise EError.Create(<ErrorMessage>)

everywhere.  You should do the same in your applications when you want to
raise an exception with a custom message.

- The issue with nested external JS namespaces is fixed (reported by Bob
Devine).  To use nested namespaces, you have to use the following
constructs:

Bob's JS code:

var EWBT = {
    TestObject : function TestObject()
    {
        this.Sum = function(A, B)
        {
            return A + B;
        };
        this.Title = 'TestObject_Title';
    },
    Title : 'EWBT_TestTitle'
};

EWB declarations:

external TTestObject = class
  public
    function Sum(A, B: integer): integer;
    property Title: string read;
  end;

external TEWBT = class
  public
    class property TestObject: TTestObject;  // "class property" is the key
here
    property Title: string read;
  end;

It's a little goofy, especially because the syntax is confusing class/object
instances with class types, but it's the only way to workaround this problem
for now and have the proper JS code emitted.  I'll be revisiting this later
to try and fix it for good, and this will probably involve allowing external
constructors to be named anything that you want.

That's it for now.  I should have another build up later this week with the
editing capabilities done, and I'm going to try and also fit in a data
source editor in the IDE.  That will allow for dealing with datasets in the
IDE with the built-in web server instead of having to run the external test
web server.

--
Tim Young
Elevate Software
www.elevatesoft.com

Hi Tim

Since I upgraded my EWB, when I run a app it comes up with a blank screen(apart from the EWB menu and icons at the top).  The first time I ran it is said "Navigation Cancelled" and it says "http://localhost/project3.html".  

I created a new very simple project but it does the same.

Is there some new setting I am missing?

Thks
Godfrey

"Tim Young [Elevate Software]" wrote:

There's a new build up on the web site this morning, and it contains the
following:

Thanks Tim - the nested namespaces are working fine and I can now
reference the RemObjects SDK objects directly.

Cheers, Bob

I'm getting an error with the latest build whenever I try to add a non-visual component to a form, ie. TTimer, TDataSet or TServerRequest:

"Control '' has no parent window"

Is anyone else getting this?

Yes I also get that.

Cheers, Bob


On 20/02/2012 21:01, Steve Gill wrote:
> I'm getting an error with the latest build whenever I try to add a non-visual component to a form, ie. TTimer, TDataSet or TServerRequest:
>
> "Control '' has no parent window"
>
> Is anyone else getting this?
>

Godfrey,

<< Since I upgraded my EWB, when I run a app it comes up with a blank
screen(apart from the EWB menu and icons at the top).  The first time I ran
it is said "Navigation Cancelled" and it says
"http://localhost/project3.html".

I created a new very simple project but it does the same. >>

Is this with IE ?  If so, please be sure to always include the version ?
Does it run with FireFox ?  If you could send me the project, I would
appreciate it.

There was one issue that I came across today, but it had to do with IE and
the Delete method of the TDataSet component.  The problem is that IE has
some issues with certain reserved JS keywords that FireFox and others don't.
At any rate, there's a new build up this evening (~9:00pm timestamp) that
corrects this issue with IE and reserved JS keywords.

--
Tim Young
Elevate Software
www.elevatesoft.com

Bob,

<< Thanks Tim - the nested namespaces are working fine and I can now
reference the RemObjects SDK objects directly. >>

Fantastic, thanks.

--
Tim Young
Elevate Software
www.elevatesoft.com

Steve,

<< I'm getting an error with the latest build whenever I try to add a
non-visual component to a form, ie. TTimer, TDataSet or TServerRequest:

"Control '' has no parent window" >>

Sorry for this - there's a new build up this evening that fixes this
(~9:00pm timestamp).

--
Tim Young
Elevate Software
www.elevatesoft.com

Downloaded new build and installed.  Running fine now.

"Tim Young [Elevate Software]" wrote:

Is this with IE ?  If so, please be sure to always include the version ?
Does it run with FireFox ?  If you could send me the project, I would
appreciate it.

There was one issue that I came across today, but it had to do with IE and
the Delete method of the TDataSet component.  The problem is that IE has
some issues with certain reserved JS keywords that FireFox and others don't.
At any rate, there's a new build up this evening (~9:00pm timestamp) that
corrects this issue with IE and reserved JS keywords.

--
Tim Young
Elevate Software
www.elevatesoft.com

Godfrey,

<< Downloaded new build and installed.  Running fine now. >>

Great, thanks for the update.

--
Tim Young
Elevate Software
www.elevatesoft.com