PDA

View Full Version : AJAX Library 1.1 for Visual DataFlex 12.1 Beta 1 is available for download/testing.



Eddy Kleinjan
24-Sep-2007, 08:35 AM
We proudly announce the availability of the

AJAX Library 1.1 for Visual DataFlex 12.1 Beta 1!



--------------------------------------------------------------------------------

To download the beta, see the details at the bottom of this message.

Some of the new features:

Auto suggest type boxes:



AJAX Library Setup Wizard:



AJAX Style HTML Page Wizard:



Other new features/enhancements include:

a.. An new attribute 'vdfDataBinding' has been introduced. The attribute vdfDataBinding can be used throughout the whole form to display data. It can be attached to any html element to display data read only data (althrough the element must be able to contain data like span, div, td and many others). On input elements the vdfDataBinding overrides the name.
b.. Support for new user defined dialogs
c.. New improved error system based on Try...Catch blocks
d.. Function keys are not user configurable at the <form> level
e.. A new attribute 'vdfUseDescriptionValue' can be used on displayonly style elements to display a fields' description instead of its stored value.
f.. The following attribute are now available on field level to override a form's value: vdfValidateClient, vdfValidateServer, vdfValidatePrevent, vdfValidateAdjust
g.. The field object now has a onValidate function which triggers before validating and can be used to cancel the validation.
h.. JModalDialog now has onBeforeClose & onClosed events.
i.. JModalDialog_DisplayDOM(sWidth, sHeight, sTitle, oContent, bClone, sContainer) can be used to display modal dialogs with content from anywhere in the page.
j.. JModalDialog_DisplayURL(sWidth, sHeight, sTitle, sURL, sContainer) can be used to display modal dialogs with content from the specified URL.
k.. User defined suggestion values can be added to the suggestion list using the vdfUserSuggestions attribute on a vdfField, adding properties also overwrite the vdfSuggestionType="none" setting.
l.. Adding the vdfSuggestionType property to a field now enabled a suggestion list which will popup suggestions based on the user's input, values are "none", this is the default and won't display any suggestions, "description", this will use the values from the field's description table as suggestions, and "value", which will use all existing values in the table to determine the suggestionlist.
m.. RMI calls now will show an alert message if an error occured, this alert can be suppressed in case of custom error handling.
n.. The use of grids related to other grids (nested grids) is now supported.
o.. A combo list no longer requires the use of the server side DDValue function to be generated, it is now possible to add a <select> element with the proper settings which will be automatically filled with the correct <option> elements.
p.. A new examle 'Wines' has been added.
Samples
There are three Visual DataFlex AJAX examples in the beta available. They are:

a.. Order Entry: The Order Entry example application build using the AJAX framework. New modern, attractive interface, many of the AJAX framework features implemented. For editing of records the user needs to login inside the application, else the user can only view records
b.. Contact Manager: The Contact Manager example application using the AJAX framwork. Users need to login to view or edit/delete records. The panel shows the usage of dblist for viewing records or dbgrid for editing records. A constraint-on-the-fly radiogroup to only view certain records is present.
c.. Wines: The Wines application using the AJAX framwork. The 'Maintenance' page shows how to maintain mutiple tables on a single pages using a separate form for each table. These tables are shown each in their own tab.
Support
If you have any questions or want to report bugs about this Alpha release, then please visit our newsgroups and go to the newsgroup called Libraries.AJAX.

Register and download:
You can register for this beta by following this link:
http://www.dataaccess.nl/IframeText.asp?pageid=1452

After you registered for this library you will get an e-mail with the download instructions for the library. The downloaded program is a setup program that guides you through the installation process.

Have fun!

The AJAX Library Development team at Data Access Europe.

Bob Worsley
24-Sep-2007, 07:19 PM
Hi Eddy... You've announced a Beta at the top, but at the bottom say "report bugs about this Alpha release". Sounds good though, gonna give it a test drive...
Bob
"Eddy Kleinjan" <eddy.kleinjan@dataaccess.nl> wrote in message news:tXZKS$q$HHA.4676@dacmail.dataaccess.com...
We proudly announce the availability of the

AJAX Library 1.1 for Visual DataFlex 12.1 Beta 1!



------------------------------------------------------------------------------

To download the beta, see the details at the bottom of this message.

Some of the new features:

Auto suggest type boxes:



AJAX Library Setup Wizard:



AJAX Style HTML Page Wizard:



Other new features/enhancements include:

a.. An new attribute 'vdfDataBinding' has been introduced. The attribute vdfDataBinding can be used throughout the whole form to display data. It can be attached to any html element to display data read only data (althrough the element must be able to contain data like span, div, td and many others). On input elements the vdfDataBinding overrides the name.
b.. Support for new user defined dialogs
c.. New improved error system based on Try...Catch blocks
d.. Function keys are not user configurable at the <form> level
e.. A new attribute 'vdfUseDescriptionValue' can be used on displayonly style elements to display a fields' description instead of its stored value.
f.. The following attribute are now available on field level to override a form's value: vdfValidateClient, vdfValidateServer, vdfValidatePrevent, vdfValidateAdjust
g.. The field object now has a onValidate function which triggers before validating and can be used to cancel the validation.
h.. JModalDialog now has onBeforeClose & onClosed events.
i.. JModalDialog_DisplayDOM(sWidth, sHeight, sTitle, oContent, bClone, sContainer) can be used to display modal dialogs with content from anywhere in the page.
j.. JModalDialog_DisplayURL(sWidth, sHeight, sTitle, sURL, sContainer) can be used to display modal dialogs with content from the specified URL.
k.. User defined suggestion values can be added to the suggestion list using the vdfUserSuggestions attribute on a vdfField, adding properties also overwrite the vdfSuggestionType="none" setting.
l.. Adding the vdfSuggestionType property to a field now enabled a suggestion list which will popup suggestions based on the user's input, values are "none", this is the default and won't display any suggestions, "description", this will use the values from the field's description table as suggestions, and "value", which will use all existing values in the table to determine the suggestionlist.
m.. RMI calls now will show an alert message if an error occured, this alert can be suppressed in case of custom error handling.
n.. The use of grids related to other grids (nested grids) is now supported.
o.. A combo list no longer requires the use of the server side DDValue function to be generated, it is now possible to add a <select> element with the proper settings which will be automatically filled with the correct <option> elements.
p.. A new examle 'Wines' has been added.
Samples
There are three Visual DataFlex AJAX examples in the beta available. They are:

a.. Order Entry: The Order Entry example application build using the AJAX framework. New modern, attractive interface, many of the AJAX framework features implemented. For editing of records the user needs to login inside the application, else the user can only view records
b.. Contact Manager: The Contact Manager example application using the AJAX framwork. Users need to login to view or edit/delete records. The panel shows the usage of dblist for viewing records or dbgrid for editing records. A constraint-on-the-fly radiogroup to only view certain records is present.
c.. Wines: The Wines application using the AJAX framwork. The 'Maintenance' page shows how to maintain mutiple tables on a single pages using a separate form for each table. These tables are shown each in their own tab.
Support
If you have any questions or want to report bugs about this Alpha release, then please visit our newsgroups and go to the newsgroup called Libraries.AJAX.

Register and download:
You can register for this beta by following this link:
http://www.dataaccess.nl/IframeText.asp?pageid=1452

After you registered for this library you will get an e-mail with the download instructions for the library. The downloaded program is a setup program that guides you through the installation process.

Have fun!

The AJAX Library Development team at Data Access Europe.

Bob Worsley
24-Sep-2007, 07:36 PM
Oops, spoke too soon. Got the link in the email, tried to download using my default FireFox browser, and all I could get was a file named "Visual". Renamed to Visual.exe and got the error "Could not initialize installation. File Size expected=3194530, size returned=3195014."

Tried the download 3 times, got the same result each time.
Bob

"Eddy Kleinjan" <eddy.kleinjan@dataaccess.nl> wrote in message news:tXZKS$q$HHA.4676@dacmail.dataaccess.com...
We proudly announce the availability of the

AJAX Library 1.1 for Visual DataFlex 12.1 Beta 1!



------------------------------------------------------------------------------

To download the beta, see the details at the bottom of this message.

Some of the new features:

Auto suggest type boxes:



AJAX Library Setup Wizard:



AJAX Style HTML Page Wizard:



Other new features/enhancements include:

a.. An new attribute 'vdfDataBinding' has been introduced. The attribute vdfDataBinding can be used throughout the whole form to display data. It can be attached to any html element to display data read only data (althrough the element must be able to contain data like span, div, td and many others). On input elements the vdfDataBinding overrides the name.
b.. Support for new user defined dialogs
c.. New improved error system based on Try...Catch blocks
d.. Function keys are not user configurable at the <form> level
e.. A new attribute 'vdfUseDescriptionValue' can be used on displayonly style elements to display a fields' description instead of its stored value.
f.. The following attribute are now available on field level to override a form's value: vdfValidateClient, vdfValidateServer, vdfValidatePrevent, vdfValidateAdjust
g.. The field object now has a onValidate function which triggers before validating and can be used to cancel the validation.
h.. JModalDialog now has onBeforeClose & onClosed events.
i.. JModalDialog_DisplayDOM(sWidth, sHeight, sTitle, oContent, bClone, sContainer) can be used to display modal dialogs with content from anywhere in the page.
j.. JModalDialog_DisplayURL(sWidth, sHeight, sTitle, sURL, sContainer) can be used to display modal dialogs with content from the specified URL.
k.. User defined suggestion values can be added to the suggestion list using the vdfUserSuggestions attribute on a vdfField, adding properties also overwrite the vdfSuggestionType="none" setting.
l.. Adding the vdfSuggestionType property to a field now enabled a suggestion list which will popup suggestions based on the user's input, values are "none", this is the default and won't display any suggestions, "description", this will use the values from the field's description table as suggestions, and "value", which will use all existing values in the table to determine the suggestionlist.
m.. RMI calls now will show an alert message if an error occured, this alert can be suppressed in case of custom error handling.
n.. The use of grids related to other grids (nested grids) is now supported.
o.. A combo list no longer requires the use of the server side DDValue function to be generated, it is now possible to add a <select> element with the proper settings which will be automatically filled with the correct <option> elements.
p.. A new examle 'Wines' has been added.
Samples
There are three Visual DataFlex AJAX examples in the beta available. They are:

a.. Order Entry: The Order Entry example application build using the AJAX framework. New modern, attractive interface, many of the AJAX framework features implemented. For editing of records the user needs to login inside the application, else the user can only view records
b.. Contact Manager: The Contact Manager example application using the AJAX framwork. Users need to login to view or edit/delete records. The panel shows the usage of dblist for viewing records or dbgrid for editing records. A constraint-on-the-fly radiogroup to only view certain records is present.
c.. Wines: The Wines application using the AJAX framwork. The 'Maintenance' page shows how to maintain mutiple tables on a single pages using a separate form for each table. These tables are shown each in their own tab.
Support
If you have any questions or want to report bugs about this Alpha release, then please visit our newsgroups and go to the newsgroup called Libraries.AJAX.

Register and download:
You can register for this beta by following this link:
http://www.dataaccess.nl/IframeText.asp?pageid=1452

After you registered for this library you will get an e-mail with the download instructions for the library. The downloaded program is a setup program that guides you through the installation process.

Have fun!

The AJAX Library Development team at Data Access Europe.

Bob Worsley
24-Sep-2007, 09:05 PM
Figuring the problem might be FireFox, I cut and pasted the link from the email, downloaded using IE, and got the same file size error. IE did name the file correctly though, I guess FireFox doesn't like the spaces in the setup name.
Bob

"Eddy Kleinjan" <eddy.kleinjan@dataaccess.nl> wrote in message news:tXZKS$q$HHA.4676@dacmail.dataaccess.com...
We proudly announce the availability of the

AJAX Library 1.1 for Visual DataFlex 12.1 Beta 1!



------------------------------------------------------------------------------

To download the beta, see the details at the bottom of this message.

Some of the new features:

Auto suggest type boxes:



AJAX Library Setup Wizard:



AJAX Style HTML Page Wizard:



Other new features/enhancements include:

a.. An new attribute 'vdfDataBinding' has been introduced. The attribute vdfDataBinding can be used throughout the whole form to display data. It can be attached to any html element to display data read only data (althrough the element must be able to contain data like span, div, td and many others). On input elements the vdfDataBinding overrides the name.
b.. Support for new user defined dialogs
c.. New improved error system based on Try...Catch blocks
d.. Function keys are not user configurable at the <form> level
e.. A new attribute 'vdfUseDescriptionValue' can be used on displayonly style elements to display a fields' description instead of its stored value.
f.. The following attribute are now available on field level to override a form's value: vdfValidateClient, vdfValidateServer, vdfValidatePrevent, vdfValidateAdjust
g.. The field object now has a onValidate function which triggers before validating and can be used to cancel the validation.
h.. JModalDialog now has onBeforeClose & onClosed events.
i.. JModalDialog_DisplayDOM(sWidth, sHeight, sTitle, oContent, bClone, sContainer) can be used to display modal dialogs with content from anywhere in the page.
j.. JModalDialog_DisplayURL(sWidth, sHeight, sTitle, sURL, sContainer) can be used to display modal dialogs with content from the specified URL.
k.. User defined suggestion values can be added to the suggestion list using the vdfUserSuggestions attribute on a vdfField, adding properties also overwrite the vdfSuggestionType="none" setting.
l.. Adding the vdfSuggestionType property to a field now enabled a suggestion list which will popup suggestions based on the user's input, values are "none", this is the default and won't display any suggestions, "description", this will use the values from the field's description table as suggestions, and "value", which will use all existing values in the table to determine the suggestionlist.
m.. RMI calls now will show an alert message if an error occured, this alert can be suppressed in case of custom error handling.
n.. The use of grids related to other grids (nested grids) is now supported.
o.. A combo list no longer requires the use of the server side DDValue function to be generated, it is now possible to add a <select> element with the proper settings which will be automatically filled with the correct <option> elements.
p.. A new examle 'Wines' has been added.
Samples
There are three Visual DataFlex AJAX examples in the beta available. They are:

a.. Order Entry: The Order Entry example application build using the AJAX framework. New modern, attractive interface, many of the AJAX framework features implemented. For editing of records the user needs to login inside the application, else the user can only view records
b.. Contact Manager: The Contact Manager example application using the AJAX framwork. Users need to login to view or edit/delete records. The panel shows the usage of dblist for viewing records or dbgrid for editing records. A constraint-on-the-fly radiogroup to only view certain records is present.
c.. Wines: The Wines application using the AJAX framwork. The 'Maintenance' page shows how to maintain mutiple tables on a single pages using a separate form for each table. These tables are shown each in their own tab.
Support
If you have any questions or want to report bugs about this Alpha release, then please visit our newsgroups and go to the newsgroup called Libraries.AJAX.

Register and download:
You can register for this beta by following this link:
http://www.dataaccess.nl/IframeText.asp?pageid=1452

After you registered for this library you will get an e-mail with the download instructions for the library. The downloaded program is a setup program that guides you through the installation process.

Have fun!

The AJAX Library Development team at Data Access Europe.

BO Lincoln
24-Sep-2007, 09:24 PM
I clicked the link in the email (Outlook Express) and got a prompt to "Do you want to run or save this file?"
I saved to disk without a problem.
I ran the AJAX install but cancelled because I don't have the latest 12.1 installed, yet...
I've got the cart a little before the horse, eh?
Anyway, the AJAX 1.1 install appears to have downloaded alright.

-BO

Jim Spence
25-Sep-2007, 11:19 AM
Had not trouble with download, but did have issue with version
mismatch.

I installed Studio version 12.1.65.0 and migrated my version 12.0
workspaces to it.

Installed Ajax library v1.1 Beta 1.

Recompiled.

Got runtime error during page load:
" Error 907 occured in.....Client & Server versions do not match
(client: 1.1, server: 1.1 Beta 1)"

I edit line 40 of cAxajSessionManager.pkg, giving it a property
psversion="1.1" instead of "1.1 Beta 1". No longer get error.

I hope this was the correct action to take.

Edwin van der Velden
25-Sep-2007, 11:43 AM
It sounds like you did not properly updated your client files or did not
changed the references to it.
Instead of changing the version at server level you should check your
AppHtml/VdfAjaxLib folder.

1. Did you overwrite the files in this folder with the 1.1 beta versions of
this.
2. Are references to these files pointing to the right folder (i.e.
AppHtml/VdfAjaxLib/1-1) and not some older version of the folder (like 1.0).

Regards,

Edwin


"Jim Spence" <Jim.Spence@hcss.com> wrote in message
news:qmcif310btcp4758telghds7mkc1hpqf11@4ax.com...
> Had not trouble with download, but did have issue with version
> mismatch.
>
> I installed Studio version 12.1.65.0 and migrated my version 12.0
> workspaces to it.
>
> Installed Ajax library v1.1 Beta 1.
>
> Recompiled.
>
> Got runtime error during page load:
> " Error 907 occured in.....Client & Server versions do not match
> (client: 1.1, server: 1.1 Beta 1)"
>
> I edit line 40 of cAxajSessionManager.pkg, giving it a property
> psversion="1.1" instead of "1.1 Beta 1". No longer get error.
>
> I hope this was the correct action to take.

Bob Worsley
25-Sep-2007, 12:25 PM
Apologies all, the problem turned out to be my router. I'd made a change a couple of weeks ago because of it's constant rebooting in some heavy usage circumstances, and that apparently upset file transfers. Just set it back and the transfer went fine.
Bob

Jim Spence
25-Sep-2007, 01:59 PM
Indeed stupid me failed to overwrite the files in my
AppHtml/VdfAjaxLib foelder with the new v1.1 Beta versions.

Nice job on the version mismatch check. Works as intended. (Except
for the part about me changing psVersion in cAjaxSessionManager)

All works fine now. Sorry for the alram, and thanks for helping me
complete the workspace migration.

Anders Ohrt
26-Sep-2007, 01:16 AM
> We proudly announce the availability of the AJAX Library 1.1 for Visual
> DataFlex 12.1 Beta 1!

Installed and runs fine. One observation though; the Ajax library isn't
really for VDF 12.1 as people that use 12.0 will want this upgrade (and
future ones) too since it contains bug fixes. I use VDF 11.1, so I needed to
install 12.1 just to get the library installed. This doesn't seem right. The
library should only require 12.0 since that was when the library system was
introduced, but then the library should live a completely separate life from
the rest of VDF.

// Anders

Eddy Kleinjan
2-Oct-2007, 06:51 AM
Hi Anders,

Please let me explain what our motivation is to make this a 12.1 requirement.

The AJAX Library is developed as a library. No surprise here. So it basically means that is could be attached to 'any' VDF version that supports libraries, and even to those that don't, like your 11.1 example. The reason why we 'require' VDF 12.1 is because the AJAX Library contains wizards that are compiled under 12.1. Those wizards will not run under any other version of VDF. We could of course include the same wizards compiled for other VDF versions, but that would create a version matrix for us that would pretty soon get out of control. Imagine the number of combinations that we have to test if we would include support for other versions.

We therefore decided to deliver the Library with the latest available version of VDF. In this case we choose that to be VDF 12.1 because that is the version that will be released soon, most probably before the 1.1 version of the AJAX Library.

This does not mean that the Library itself (which has VDF Classes, VDF Templates, JavaScript Client code, wizards and sample applications) does not run under older versions of Visual DataFlex. It probably does. But we do want to able to use any new techniques from VDF when they come along. For example, the structs and arrays that where introduced in VDF 11.1. And the WebServices.

So while the AJAX Library might be compatible with older versions than our target VDF version, we don't guarantee that. When new techniques come along, we want to have the freedom of using these techniques. Not to force to break backward compatibility, but because new technologies might be better to use.

Would you be helped if we would include a warning box that says something like:
"You don't have the required Visual DataFlex 12.1 version installed. When you continue this installation then the sample applications and the wizards will most probably not work. Would you like to install this version of the AJAX Library anyway?"

Best regards,
Data Access Europe

Eddy Kleinjan


"Anders Íhrt" <Anders.Ohrt@berendsen.se> wrote in message news:dMgtySAAIHA.4116@dacmail.dataaccess.com...

> We proudly announce the availability of the AJAX Library 1.1 for Visual
> DataFlex 12.1 Beta 1!

Installed and runs fine. One observation though; the Ajax library isn't
really for VDF 12.1 as people that use 12.0 will want this upgrade (and
future ones) too since it contains bug fixes. I use VDF 11.1, so I needed to
install 12.1 just to get the library installed. This doesn't seem right. The
library should only require 12.0 since that was when the library system was
introduced, but then the library should live a completely separate life from
the rest of VDF.

// Anders

Anders Ohrt
3-Oct-2007, 02:36 AM
> The AJAX Library is developed as a library. No surprise here. So it
> basically means that is could be attached to 'any' VDF version that
> supports libraries, and even to those that don't, like your 11.1 example.
> The reason why we 'require' VDF 12.1 is because the AJAX Library contains
> wizards that are compiled under 12.1. Those wizards will not run under
> any other version of VDF. We could of course include the same wizards
> compiled for other VDF versions, but that would create a version matrix
> for us that would pretty soon get out of control. Imagine the number of
> combinations that we have to test if we would include support for other
> versions.

> We therefore decided to deliver the Library with the latest available
> version of VDF. In this case we choose that to be VDF 12.1 because that
> is the version that will be released soon, most probably before the 1.1
> version of the AJAX Library.

> This does not mean that the Library itself (which has VDF Classes, VDF
> Templates, JavaScript Client code, wizards and sample applications) does
> not run under older versions of Visual DataFlex. It probably does. But we
> do want to able to use any new techniques from VDF when they come along.
> For example, the structs and arrays that where introduced in VDF 11.1.
> And the WebServices.

The problem was that I (and others I assume) was waiting for bugfixes in
this version. If we had moved up to 12.0 and deployed this, and you had made
changes (to not just the wizards) that made the library require 12.1, we
would have been forced to either upgrade to 12.1 (non-trivial) or to
continue using the 1.0 library and work around the bugs ourselves (possibly
non-trivial).

As always, it's a balance between the stability issue and adding with new
features. Adding features is fun, stability is boring. =)


> Would you be helped if we would include a warning box that says something
> like:
> "You don't have the required Visual DataFlex 12.1 version installed. When
> you continue this installation then the sample applications and the
> wizards will most probably not work. Would you like to install this
> version of the AJAX Library anyway?"

Definitely, that would be great.

// Anders

Eddy Kleinjan
3-Oct-2007, 03:02 AM
Thanks for you comments.

For about the bug fixes: Those are independent whether you are using 12.0 or 12.1. You can 'simply' add the AJAX Library 1.1 to a VDF 12.0 workspace (and remove the 1.0 version). Don't forget to copy over the new 1.1 JavaScript files into your workspace as well.

Setup:
When we implement the installation question that you don't have the right (recommended) VDF version installed, and choose to install it anyway, it will not do the following things:

- Register the AJAX Library Workspace Setup Wizard
- Compile the Sample Applications
- Register the Sample Applications for Web App Server
- Register the Sample Applications for Internet Information Server
- Create shortcuts to Internet Explorer to run the Sample Applications

The WBO Wizard will be installed, but will not run until you install VDF 12.1.

Whenever someone chooses to install VDF 12.1 afterwards, they can rerun the AJAX Library Setup.

Comments?


Eddy Kleinjan
Data Access Europe





"Anders Íhrt" <Anders.Ohrt@berendsen.se> wrote in message news:m89%23pAZBIHA.752@dacmail.dataaccess.com...

> The AJAX Library is developed as a library. No surprise here. So it
> basically means that is could be attached to 'any' VDF version that
> supports libraries, and even to those that don't, like your 11.1 example.
> The reason why we 'require' VDF 12.1 is because the AJAX Library contains
> wizards that are compiled under 12.1. Those wizards will not run under
> any other version of VDF. We could of course include the same wizards
> compiled for other VDF versions, but that would create a version matrix
> for us that would pretty soon get out of control. Imagine the number of
> combinations that we have to test if we would include support for other
> versions.

> We therefore decided to deliver the Library with the latest available
> version of VDF. In this case we choose that to be VDF 12.1 because that
> is the version that will be released soon, most probably before the 1.1
> version of the AJAX Library.

> This does not mean that the Library itself (which has VDF Classes, VDF
> Templates, JavaScript Client code, wizards and sample applications) does
> not run under older versions of Visual DataFlex. It probably does. But we
> do want to able to use any new techniques from VDF when they come along.
> For example, the structs and arrays that where introduced in VDF 11.1.
> And the WebServices.

The problem was that I (and others I assume) was waiting for bugfixes in
this version. If we had moved up to 12.0 and deployed this, and you had made
changes (to not just the wizards) that made the library require 12.1, we
would have been forced to either upgrade to 12.1 (non-trivial) or to
continue using the 1.0 library and work around the bugs ourselves (possibly
non-trivial).

As always, it's a balance between the stability issue and adding with new
features. Adding features is fun, stability is boring. =)


> Would you be helped if we would include a warning box that says something
> like:
> "You don't have the required Visual DataFlex 12.1 version installed. When
> you continue this installation then the sample applications and the
> wizards will most probably not work. Would you like to install this
> version of the AJAX Library anyway?"

Definitely, that would be great.

// Anders

Anders Ohrt
3-Oct-2007, 03:40 AM
> For about the bug fixes: Those are independent whether you are using 12.0
> or 12.1. You can 'simply' add the AJAX Library 1.1 to a VDF 12.0
> workspace (and remove the 1.0 version). Don't forget to copy over the
> new 1.1 JavaScript files into your workspace as well.

Yes, I did not mean to imply that the 1.1 library was not compatible with
12.0, it was just a "what-if" scenario.


> Setup:
> When we implement the installation question that you don't have the right
> (recommended) VDF version installed, and choose to install it anyway, it
> will not do the following things:
> [...]
> Comments?

Looks good to me.

// Anders