a possible way forward ? - after Cologne 2017 !
Posted: Tue Apr 11, 2017 10:22 am
Hi Robert, Team, and all X# community and colleagues,
Now that the German xBase.Future conference is so close, and my preparation is all but done, I have started looking ahead to after the conference.
I wish to share with you some thoughts which I had very recently. These are to do with possible contributions I can make to helping promote X# / xBase and helping my friends and colleagues in that same community. Now that I am retired from paid work, I can contribute to making things easier for guys to get to grips with certain areas of X# and .NET - there are some areas where I have little to no knowledge however ;-0) someone else can cover those!
So far, since October last year (2016) I have explored X# and experimented with some new and exciting parts of the Roslyn based compiler, and placed working tests and snippets into a special appendix - named 'Appendix X' in my eVolume of eNotes called "ClickStartLINQ" - see a couple of images below (captured with SnagIt version 13) :-
I started to put my new X# 'stuff' into this appendix simply because I was focused on doing a lot of good material on LINQ within the X# syntax - remember it was all new to me as previously I had to do my LINQ work in a C# class library. the rest of the 'ClickStartLINQ' eNotes had been done years before that and had therefore to be based on C# - this work has been left in the eNotes, as it was previously.
However, as time progressed from last October, I started doing many more areas of interest in X#, and these got added into the 'X' appendix. So at the moment, the existing sections and subsections are a bit mixed together - check below :-
Okay then, the Conference guys will get all the X# working code I have generated - BUT - there seems to me to be a need for a new and better structured set of eNotes - possibly called "ClickSatrtXSharp", in which I try to add sub-sections on all of the topics I regularly use in my applications.
It would seem sensible to me if I made such a set of notes initially based on Desktop app technology (the stuff I have been doing for a while), but then moved to Windows Universal apps and .NET CORE apps, as well as Android and Cross-Platform types of stuff.
Another aspect of the eNotes could be that I show clearly how Visual Studio is used to create the X# apps, as it would seem that many guys need some support with VS work - there is plenty of support out there for Chris's XIDE, from both Chris and guys like Frank, Wolfgang and others. But we do need some support for X# with VS I feel.
I am afraid that it is so long since I did 'WinForms' that I would have to give that topic area a miss. Anyway, WPF and XAML seems to have plenty of life left in them for the Universal and Cross-Platform work, so VS will be needed for new technologies I feel.
Finally, I did also think of moving over my Printing class library to X# from Vulcan, as it still has a big job to play I feel. It was the first thing I did when experimenting with a move from VO to .NET and VN. Printing and printers still has a role to play in our coding I feel, and it was one of the larger sections under-pinning my 'Invoices' application from many 'DevShare's ago.
Are there any topic areas which you particularly think should be included in such a brave venture?
First of all, do you think it is worth me making the effort ? I may also acquire a new web site with a suitable new name.
Such a venture would be done on a basis of continual website updating, as fresh topics and sub-sections were added. So there would be no waiting around, or holding back of material until the whole thing was completed. We could even start with the whole Appendix 'X' being available in the new eVolume - I would leave it in place until all new folder structures came on stream.
Any thoughts ?
Phil.
Wales, UK.
Now that the German xBase.Future conference is so close, and my preparation is all but done, I have started looking ahead to after the conference.
I wish to share with you some thoughts which I had very recently. These are to do with possible contributions I can make to helping promote X# / xBase and helping my friends and colleagues in that same community. Now that I am retired from paid work, I can contribute to making things easier for guys to get to grips with certain areas of X# and .NET - there are some areas where I have little to no knowledge however ;-0) someone else can cover those!
So far, since October last year (2016) I have explored X# and experimented with some new and exciting parts of the Roslyn based compiler, and placed working tests and snippets into a special appendix - named 'Appendix X' in my eVolume of eNotes called "ClickStartLINQ" - see a couple of images below (captured with SnagIt version 13) :-
I started to put my new X# 'stuff' into this appendix simply because I was focused on doing a lot of good material on LINQ within the X# syntax - remember it was all new to me as previously I had to do my LINQ work in a C# class library. the rest of the 'ClickStartLINQ' eNotes had been done years before that and had therefore to be based on C# - this work has been left in the eNotes, as it was previously.
However, as time progressed from last October, I started doing many more areas of interest in X#, and these got added into the 'X' appendix. So at the moment, the existing sections and subsections are a bit mixed together - check below :-
Okay then, the Conference guys will get all the X# working code I have generated - BUT - there seems to me to be a need for a new and better structured set of eNotes - possibly called "ClickSatrtXSharp", in which I try to add sub-sections on all of the topics I regularly use in my applications.
It would seem sensible to me if I made such a set of notes initially based on Desktop app technology (the stuff I have been doing for a while), but then moved to Windows Universal apps and .NET CORE apps, as well as Android and Cross-Platform types of stuff.
Another aspect of the eNotes could be that I show clearly how Visual Studio is used to create the X# apps, as it would seem that many guys need some support with VS work - there is plenty of support out there for Chris's XIDE, from both Chris and guys like Frank, Wolfgang and others. But we do need some support for X# with VS I feel.
I am afraid that it is so long since I did 'WinForms' that I would have to give that topic area a miss. Anyway, WPF and XAML seems to have plenty of life left in them for the Universal and Cross-Platform work, so VS will be needed for new technologies I feel.
Finally, I did also think of moving over my Printing class library to X# from Vulcan, as it still has a big job to play I feel. It was the first thing I did when experimenting with a move from VO to .NET and VN. Printing and printers still has a role to play in our coding I feel, and it was one of the larger sections under-pinning my 'Invoices' application from many 'DevShare's ago.
Are there any topic areas which you particularly think should be included in such a brave venture?
First of all, do you think it is worth me making the effort ? I may also acquire a new web site with a suitable new name.
Such a venture would be done on a basis of continual website updating, as fresh topics and sub-sections were added. So there would be no waiting around, or holding back of material until the whole thing was completed. We could even start with the whole Appendix 'X' being available in the new eVolume - I would leave it in place until all new folder structures came on stream.
Any thoughts ?
Phil.
Wales, UK.