TOPIC:

Hello,

should the XSharp.Tools.WPF library depend on the XSharp.VO library or only on on the XSharp.Core library?

Cons:

• for a new application, VO datatypes could be left behind
• a WPF application could also be written in other languages, using the XSharp.Tools.WPF library

Pros:

• even in a WPF application I would see the Transform() function as needed - and this function is in the XSharp.VO library
• a WPF application should also be able to use our older business logic that may make use of the Date datatype, codeblocks, arrays or the AScan()/ASort() functions
• the internal code of the library will be smaller and faster if functions from both libraries can be used

Personally, I would go for a dependeny on both XSharp.Core and XSharp.VO libraries - I have to admit that it boosted my productivity when I started to use the X# runtime in my pure X# applications.

Wolfgang

Hi Wolfgang

In my opinion, it would be best to have a XSharp.Tools.WPF library in Core dialect, and this would contain the maximum amount of the VO function transcribed in Core dialect. It was one of the first libraries I wrote in XS that emulated the most used functions from VO (like Str (), WorkDir (), Left (), Right (), Val (), Len () .... ).

Juraj

Hi Juraj,

that is what I tought first, but when I discovered that the Transform() method is in the XSharp.VO library (because of the support for Date and Usual).
And IMHO a Picture property is absolutely essential to every business application - and that needs the Transform() function.
In my first X# applications, I had rewritten also all these functions, but now I'm returning to the versions of the runtime - it makes much more sense to me.

Wolfgang

Hi Wolfgang,

I tried to convert one small WPF app from core dialect to VO dialect. I just had to fix more "." to ":" otherwise everything worked OK. Is there anything in Core dialect that will not work in VO dialect?

Juraj

Hi Juraj,

Is there anything in Core dialect that will not work in VO dialect?

The VO dialect is more permissive... AFAIK there is nothing, and I have not found anything in the comparison table: www.xsharp.eu/help/dialects.html

The inverse is not true, there are many things that work in VO dialect, but not in Core dialect.

Wolfgang

Wolfgang,

We will try to move (parts of ) the Transform support to XSharp.Core in one of the next builds.

Robert

Hi Robert,
Thank you very much!
Then I will keep only the dependency to Core in the WPF library
Wolfgang