Native Resource compiler

[wriedmann]

Hi Robert,

I have no problems building my VO style applications because I stay away from VS whenever possible, and prefer to use XIDE instead.

Wolfgang

P.S. that has forced me to try to build WPF windows in code, and with a few new classes this code is much more readable than the relative XAML forms

[Phil Hepburn]

Hi Wolfgang, good morning to you, its a lovely sunny morning here in Newport, Wales

I am sure you are right in all that you say, ... for yourself at least.

However, I do have to say to other Forum readers that code and script clarity, and readability, generally comes from the guy who did the 'writing'.

I, like you, started off hating XAML, but that was mainly due to it being VERY badly written and presented. Now I use XAML a lot, and effectively, BUT, I do try and write it WELL.

Remember, it is also possible to make even lovely X# syntax code look dreadful, and hard to read.

Anyone who does not script in XAML at least now and again, will never 'break through' !

I manage quite well in VS with the XAML editor - but then I have invested a lot of time getting quite good at it - thank goodness :whistle: :cheer:

Regards to all,
Phil.
Wales, UK.

[wriedmann]

Hi Phil,

of course, this is my personal preference, and I know that I'm in an absolute minority <g>.

But: the most dialogs I'm writing in my VO applications are dynamic ones - not painted, only defined (this is VO code, I have to write similar code also X#):

Code: Select all

oDlg := DynDialog{ _oWindow }
oDlg:Caption		:= _cCaption
oDlg:AddDateField( "FromDate", "From date",, ConDate( Year( dBuchungsDatum ), 1, 1 ) )
oDlg:AddDateField( "ToDate", "To date",, EoM( dBuchungsDatum ) )
oDlg:AddLogicField( "Details", "with details,, _lMitDetails )
oDlg:AddLogicField( "Export", "with export to Excel",, false )
oDlg:Show( SHOWCENTERED )

Generation of windows in code has a lot of advantages for me....

But again: for me. Most other people will prefer the XAML editor.

Wolfgang

[Phil Hepburn]

Yes Wolfgang,

The 'ML' in XAML does stand for "mark up language" and you require runtime generated form stuff.

That's OK with me, as long as you don't give all the Forum new guys the wrong impression about script and the XAML editor in VS. It works, and works well.

Now then, time for some lunch ;-0)

Cheers,
Phil.

[wriedmann]

Hi Phil,

as always, in programming there is not only one correct way to do something - there are several ones, if you ask 3 programmers how to do something, you will receive at least 5 different answers.

You will never hear from me that my solution to a problem would be the absolute best - fortunately I know several programmers that are much better than I will ever be, and so I can expect that someone other can find a better solution.

I have only to find my own way (not every time the easiest thing), because I have very specific needs, and therefore you can see sometimes very uncommon solutions from me.


Wolfgang

[Phil Hepburn]

Yes,

But you do make life interesting B) :whistle:

Only 5 different answers ???

So have a nice weekend !

Weather still nice in Newport - quite a change, it usually rains 100% of the time.

Cheers,
Phil.
Wales, UK.

[robert]

Phil, Wolfgang,

This has nothing to do anymore with the Native Resource compiler.
Thread closed.

Robert