Hi Frank,
Conversion is going to be more interesting and enjoyable than just challenging.
I did just that when I converted from Clipper to xHarbour.
With Cule, I wrote a convertor for forms from resource to .net code which worked for me and need
to check my archives for the code now.
TBrowse....., guess there are other browse functionalities developed for VO and Vulcan that can do most of the work for us. I have moved to DataGridView since.
I would suggest that you redesign all your forms with the designer than just converting from row/col to pixel.
Other big option is WPF when it is ready.
Roslyn is the way forward and there are other possibilities that one would like to explore later and adopt.
Cheers!!!
C# and XSharp
-
Frank Maraite
- Posts: 176
- Joined: Sat Dec 05, 2015 10:44 am
- Location: Germany
C# and XSharp
Hi Kannan,
I do WPF by code too, in Vulcan and now in X#. There is nothing that prevents from using it. I want to show a library for that in Cologne.
The work I'm doing now is to eleminate usage of USUALS and ARRAYS. X# shows me now were I used them and does not compile. But this is necessary to use data binding. WPF does not now about ARRAYS for example, even when X# support this. Or better to say: I would expect that. Don't know what kinds of hacks Robert has in mind.
Frank
yes it is.Conversion is going to be more interesting and enjoyable than just challenging.
I did just that when I converted from Clipper to xHarbour.
With Cule, I wrote a convertor for forms from resource to .net code which worked for me and need
to check my archives for the code now.
I use WPF DataGrid of course directly on DBF. I added special behaviour to TBrowse. Until now I didn't managed to get the same behaviour to DataGrid. Havo to look into somethinge else like DevExpress after the Cologne conference.TBrowse....., guess there are other browse functionalities developed for VO and Vulcan that can do most of the work for us. I have moved to DataGridView since.
WPF is ready(see above)! There is no need to do that producing X# code. Use the build in designer of VS or Expression Blend like I tried. Doing it the right way with full data binding than you have no code behind. Just use the dlls. That's the big pro of .Net: We can freely mix languages and use the best for our needs.Other big option is WPF when it is ready.
I do WPF by code too, in Vulcan and now in X#. There is nothing that prevents from using it. I want to show a library for that in Cologne.
The work I'm doing now is to eleminate usage of USUALS and ARRAYS. X# shows me now were I used them and does not compile. But this is necessary to use data binding. WPF does not now about ARRAYS for example, even when X# support this. Or better to say: I would expect that. Don't know what kinds of hacks Robert has in mind.
Frank
C# and XSharp
Frank,
ROSYLN is a definite step forward...Want to congratulate the guys for the bold step forward..
Wish we could have a comparison for features with samples for most of the needs.
As most have gone for C# and the likes in these years, expect X# to make a big splash real soon, as the next big thing, in the xbase world.
Mixing C# and X# sounds real great. Would like to test this when things are ready for the big roll.
Greetings!!!
ROSYLN is a definite step forward...Want to congratulate the guys for the bold step forward..
Wish we could have a comparison for features with samples for most of the needs.
As most have gone for C# and the likes in these years, expect X# to make a big splash real soon, as the next big thing, in the xbase world.
Mixing C# and X# sounds real great. Would like to test this when things are ready for the big roll.
Greetings!!!