Fernando,

<< Now, what's in the server side? Where is the data coming from? >>

Duh, I forgot the most important part.  I've posted a web server that you
can use to serve up DBISAM tables.

--
Tim Young
Elevate Software
www.elevatesoft.com

Thanks Tim. The funny part was that I *could* run the project in the
IDE and it ran with data. It was when I put the project on my internet
server that no data came up. I do understand that it is due to
cross-domain restrictions.

I will look at the test web server as well.

--
Jan


Tim Young [Elevate Software] wrote:

> You may not be able to run the project in the IDE due to cross-domain
> restrictions.  You'll basically be trying to load data from
> www.elevatesoft.com while using localhost for the rest.

It would be nice to have this demo updated with the current status of EWB.

Leslie,

<< It would be nice to have this demo updated with the current status of
EWB. >>

What specifically are you looking to see ?  I'm not sure if I'm going to
enable editing on the common demo, mainly because of the problems with
people constantly changing the demo data.

--
Tim Young
Elevate Software
www.elevatesoft.com

My main interest is speed on moderate mobile phones and  tablets via 2g/3g connection. Especially the speed of lookup controls. Larger datasets cannot be stored on the client side so the speed of scrolling and the reaction time to speed search is the key factor in user experience.

Editing the the data would not be a problem if the server starts a transaction for every user  which is rolled back after a period of inactivity. The user can be notified before it happens and the roll back can be postponed.

If keeping transactions open prevents other users from updating  and the server is stateful then allowing editing for some small table which is stored in memory for every web session would allow to test how EWB handles both updates and large lookup datasets.

Leslie,

<< My main interest is speed on moderate mobile phones and  tablets via
2g/3g connection. Especially the speed of lookup controls. Larger datasets
cannot be stored on the client side so the speed of scrolling and the
reaction time to speed search is the key factor in user experience. >>

Two points:

1) There aren't any lookup controls in EWB.  You have to load the data into
the appropriate list or combo box control manually.

2) Datasets, in general, are not virtual in EWB.  They do not provide
automatic pagination and require you to load the "pages" as necessary, if
you want to provide pagination or virtual scrolling.

<< Editing the the data would not be a problem if the server starts a
transaction for every user  which is rolled back after a period of
inactivity. The user can be notified before it happens and the roll back can
be postponed. >>

Transaction activity is cached until the user/developer in the EWB
application decides to commit the updates to the back-end.  The back-end
update process goes like this:

1) EWB application calls StartCommit on every TDataSet that it wants to send
over transactions for.  This method returns a JSON string representing the
transaction data since the last commit point.  The EWB application then
sends over the JSON data to the back-end using a TServerRequest.

2) Once the EWB application receives a positive response from the back-end,
it then calls EndCommit for every applicable TDataSet, which then clears out
the transaction log for that dataset and ends the transaction.

<< If keeping transactions open prevents other users from updating and the
server is stateful then allowing editing for some small table which is
stored in memory for every web session would allow to test how EWB handles
both updates and large lookup datasets.  >>

Neither EWB nor any web server is stateful, at least not without a lot of
work.  When a transaction is "open" on the EWB side, the back-end has no
idea that such a "transaction" even exists.  Everything is cached in memory
in the browser with EWB, and no local storage space is assumed.

--
Tim Young
Elevate Software
www.elevatesoft.com

After looking at the IDE, this one demo was impressive enough to convince me to buy!

Great work...


That said, on Chrome it usually does not work for me, with js errors:

Uncaught TypeError: Cannot call method 'toLocaleUpperCase' of null cdcollector.js:1
f3 cdcollector.js:1
c_jF cdcollector.js:1
c_init cdcollector.js:1
cdcollector_load cdcollector.js:1
onload

On FF it works great and for some strange reason it worked once on Chrome..

Sure these are minor issues but worth passing on..

Richard,

<< After looking at the IDE, this one demo was impressive enough to convince
me to buy!
Great work... >>

Thanks for your order.

<< That said, on Chrome it usually does not work for me, with js errors:  >>

Which version of Chrome are you using ?  Also, are you running it using the
local web server in the IDE or via the file system ?

Thanks,

Tim Young
Elevate Software
www.elevatesoft.com