The final release candidate build is now up.  You can read more about it
here:

http://www.elevatesoft.com/blog?action=view&id=product_status_update

There are two new examples in the \examples subdirectory under the main
installation directory.  One is for form submittals and the other is a
complete master-detail database/transaction example.  In addition, the
installation will automatically configure the datasets necessary for running
the master-detail example in the IDE.

One thing that you have to drill into your head when looking at the
master-detail example is asynchronous, asynchronous, asynchronous.  Modal
forms/message dialogs, as well as the submittal of transactional data (JSON)
to the web server during a commit of the final transaction level (nested
transactions are supported now), are all asynchronous.  So, things like the
TForm's OnCloseQuery require some basic state management about where in the
"close process" the form is when using a modal dialog to prompt the user for
saving/cancelling changes.  Just always remind yourself that these type of
event handlers will "run through" to their conclusion, even with a message
dialog.  The good thing, though, is that you don't have to jump through
hoops to get modal progress forms to work.

One note on the DataSet Manager - it only currently supports using *Unicode*
ElevateDB databases, so if you try an ANSI database it won't work.  I'm
working on a possible improvement to EDB that will affect this, so I'm
leaving this alone until that materializes/turns out to be unworkable.

I'm still working on finishing up the docs, so I would appreciate it if
everyone could still abide by my previous post about support questions.  The
quiet time was very useful, and I was able to get quite a bit of new stuff
done with the product that I otherwise wouldn't have had time to do.  So,
the quiet is very much appreciated.

Hopefully this build will resolve any outstanding issues with
bugs/performance from the prior build.  I do have one more performance
improvement to do with the framework before the final release, but it isn't
a major one and shouldn't affect most projects.

Thanks,

Tim Young
Elevate Software
www.elevatesoft.com

> The final release candidate build is now up.

Sorry to be thick, but would it still say "7/3/2012 9:05:10 AM" as the date and
time on the web site? I don't want to go back in time with my install. Thanks!

/Matthew Jones/

Matthew


What's wrong with 9:05 am on the 3rd July 2012. You won't be going back that far

Roy Lambert [Team Elevate]

Sorry, I just fell over international date formatting. 8-)

FWIW, we always show dates at 3 Jul 2012 so that everyone can follow them safely.
Far too many americans fall over on the dd/mm/yy layout we use. Seems I fell over
the mm/dd/yy layout instead. Not helped by still being the same build as ever of
course.

/Matthew Jones/

Matthew


Bloody limey <vbg>

Roy Lambert

LOL! It is this sort of thing that you fall over in international trade, and can
cause confusion (witness: me). Given a computer is generating these dates, it is
worth considering if anything can be done when working on such things. I've just
had an email saying my maintenance plan "will be expiring on 8/2/2012" - you mean
it expired in February? My goodness. Only if one is made aware, and how easy it is
to fix (but sure, not worth doing when one is busy getting a product ready for
sale), can you improve the understanding for everyone.

Dates are an easy thing to internationalise. Text can be much harder - we once had
a customer tell us that we "swear him badly" (which we took to mean we had insulted
him). That hadn't been our intention of course. If only human language was easy.

/Matthew Jones/

Matthew

>If only human language was easy.

and if only human beings (especially customers) were easy!

Roy Lambert

Matthew,

<< LOL! It is this sort of thing that you fall over in international trade,
and can cause confusion (witness: me). Given a computer is generating these
dates, it is worth considering if anything can be done when working on such
things. I've just had an email saying my maintenance plan "will be expiring
on 8/2/2012" - you mean it expired in February? My goodness. Only if one is
made aware, and how easy it is to fix (but sure, not worth doing when one is
busy getting a product ready for sale), can you improve the understanding
for everyone. >>

I've, at the very least, changed the dates to use textual day of week/months
so they're a little easier to understand.  The web site is currently
JS-free, so it can't detect the date/time format settings yet.

Tim Young
Elevate Software
www.elevatesoft.com

I think going javascript for local formatting would be too far. And since so many
will have their locale incorrect, it might confuse more. But text months is a
perfect solution. Thanks for considering and implementing it.

/Matthew Jones/