Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.clipper.visual-objects > #11409 > unrolled thread

Re X# and VULCAN and VO.. quick story of way forward

Started bySherlock <sherlock@sherlock.com.au>
First post2018-02-23 05:57 -0800
Last post2018-02-26 12:40 +0100
Articles 13 — 5 participants

Back to article view | Back to comp.lang.clipper.visual-objects


Contents

  Re X# and VULCAN and VO.. quick story of way forward Sherlock <sherlock@sherlock.com.au> - 2018-02-23 05:57 -0800
    Re: Re X# and VULCAN and VO.. quick story of way forward "Wolfgang Riedmann" <wriedmann@gmail.com> - 2018-02-23 16:17 +0100
    Re: Re X# and VULCAN and VO.. quick story of way forward D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2018-02-24 16:05 +0100
      Re: Re X# and VULCAN and VO.. quick story of way forward Karl Faller <mail_withoutthat_@_drei-f_andthat_.de> - 2018-02-24 22:33 +0100
        Re: Re X# and VULCAN and VO.. quick story of way forward "Wolfgang Riedmann" <wriedmann@gmail.com> - 2018-02-25 09:01 +0100
          Re: Re X# and VULCAN and VO.. quick story of way forward Karl Faller <mail_withoutthat_@_drei-f_andthat_.de> - 2018-02-26 13:25 +0100
            Re: Re X# and VULCAN and VO.. quick story of way forward "Wolfgang Riedmann" <wriedmann@gmail.com> - 2018-02-26 13:43 +0100
              Re: Re X# and VULCAN and VO.. quick story of way forward Chris Pyrgas <"chris (at)"@xsharp.eu> - 2018-02-26 15:05 +0200
                Re: Re X# and VULCAN and VO.. quick story of way forward "Wolfgang Riedmann" <wriedmann@gmail.com> - 2018-02-26 14:51 +0100
                Re: Re X# and VULCAN and VO.. quick story of way forward D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2018-02-26 23:14 +0100
                  Re: Re X# and VULCAN and VO.. quick story of way forward "Wolfgang Riedmann" <wriedmann@gmail.com> - 2018-02-27 07:12 +0100
                    Re: Re X# and VULCAN and VO.. quick story of way forward Karl Faller <mail_withoutthat_@_drei-f_andthat_.de> - 2018-02-27 09:23 +0100
        Re: Re X# and VULCAN and VO.. quick story of way forward D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2018-02-26 12:40 +0100

#11409 — Re X# and VULCAN and VO.. quick story of way forward

FromSherlock <sherlock@sherlock.com.au>
Date2018-02-23 05:57 -0800
SubjectRe X# and VULCAN and VO.. quick story of way forward
Message-ID<eba99b34-269b-4c6c-bbf3-ff1d8c1ba84e@googlegroups.com>
Forum

OK Clipper / VO / Vulcan and X#.  Used first two for long long time.

Vulcan I did not make the jump.  
X# would make the jump if I understand the following gray areas for me.

1/ Can I take VO say repo to X#.. how hard
2/ What do I lose.. what is missing?  Did I read you need parts of Vulcan to something ?

There my first questions.  

Happy to hear reason for and against.. the journey and what is planned.

Phil 

[toc] | [next] | [standalone]


#11411

From"Wolfgang Riedmann" <wriedmann@gmail.com>
Date2018-02-23 16:17 +0100
Message-ID<ffapjhFkgsrU1@mid.individual.net>
In reply to#11409
Hi Phil,

> Vulcan I did not make the jump.  
> X# would make the jump if I understand the following gray areas for
> me.
> 
> 1/ Can I take VO say repo to X#.. how hard

you can migrate your applications to X# using the XPorter tool, but
your applications need some work. Please read these documents for more
information:

https://www.riedmann.it/download/MigrationGuide_VO_to_XSharp.pdf

https://www.riedmann.it/download/wlib2_to_xs.pdf

https://www.xsharp.info/help/migratingappsfromvotox.html


> 2/ What do I lose.. what is missing?  Did I read you need parts of
> Vulcan to something ?

what you loose? IMHO nothing.... What you receive: a .NET application
that you can integrate with many .NET features.

But please read the first document - it will give you the informations
you need - therefore I wrote it.

Wolfgang

-- 

[toc] | [prev] | [next] | [standalone]


#11418

FromD.J.W. van Kooten <vankooten@removethis.ic2.com>
Date2018-02-24 16:05 +0100
Message-ID<epu29ddg530vkelk31n9oq2n9nql7f24gq@4ax.com>
In reply to#11409
Replying on message of Fri, 23 Feb 2018 05:57:35 -0800 (PST) from
Sherlock:


 Hello Phil,

>1/ Can I take VO say repo to X#.. how hard

We've done a conversion May last year of parts of one program for a
client. With the notes we made and the latest XPorter we'll repeat it
in the next few weeks on a larger scale. I'll create an entry in the
X# Documentation Project which should help others like you and let you
all know in this NG.

See this link for details:

https://www.xsharp.info/forum/public-chit-chat/542-the-x-documentation-project


>2/ What do I lose.. what is missing?  Did I read you need parts of Vulcan to something ?


You can keep VO forms and menu's and use bBrowser for Vulcan or use
Paul Piko's Facelift to convert windows to WPF or Winforms. We are
working out alternatives for bBrowser because that won't work with
native .Net windows.

I personally dislike Visual Studio in many respects; many improvements
above VO weigh far less for me than the loss of enitity based editing
and searching on last changed entities. Chris has written Xide, which
feels closer to VO but is still .prg (.cs) based editing (by nature;
only VO had this repo) and doesn't support WPF, but you may like that
better. Most other users don't seem to dislike Visual Studio as much
as I do. 

I had pretty extensive discussion following a problem I had with
debugging in VS (this problem was solved by Chris but the pro's and
contra's of entity based browsing are in the same thread):

https://www.xsharp.info/forum/public-chit-chat/557-debugging-in-visual-studio

Some other VS issues I dislike are in here:

https://www.xsharp.info/forum/public-chit-chat/573-some-other-visual-studio-things-i-consider-suboptimal

I haven't had reactions on that so I figure this indeed doesn't work
(well) in VS.

But VS is only part of it all I'd say, although this is what you maye
be using for hours a week.

Dick

[toc] | [prev] | [next] | [standalone]


#11424

FromKarl Faller <mail_withoutthat_@_drei-f_andthat_.de>
Date2018-02-24 22:33 +0100
Message-ID<iem39ddrrt23a10l53e6bqggih57sj5orr@4ax.com>
In reply to#11418
Dick,
>Chris has written Xide, ...and doesn't support WPF,
FTR, not quite true. There's no wpf forms designer there, but WPF
itself works, ask Wolfgang, who works with XIDE and WPF only in coded
form...

Karl
Regards

Karl

[toc] | [prev] | [next] | [standalone]


#11427

From"Wolfgang Riedmann" <wriedmann@gmail.com>
Date2018-02-25 09:01 +0100
Message-ID<fff8rnFk5jjU1@mid.individual.net>
In reply to#11424
Hi Dick, hi Karl,

> > Chris has written Xide, ...and doesn't support WPF,

> FTR, not quite true. There's no wpf forms designer there, but WPF
> itself works, ask Wolfgang, who works with XIDE and WPF only in coded
> form...


personally I like WPF very much, and creating WPF forms in code has
some advantages.

I have discussed with Chris many times about creating a designer for
WPF. Unfortunately it is not possible use XAML with a non-Microsoft
application, but it would be possible to change the WinForms editor
that it outputs WPF code instead of WinForms code. But this would
cripple the possibilities of WPF.

Wolfgang


-- 

[toc] | [prev] | [next] | [standalone]


#11434

FromKarl Faller <mail_withoutthat_@_drei-f_andthat_.de>
Date2018-02-26 13:25 +0100
Message-ID<83v79d93skc6cftc0ds7mrh1qcnt3o128f@4ax.com>
In reply to#11427
Wolfgang,
> Unfortunately it is not possible use XAML with a non-Microsoft
>application,
would you care to elaborate a bit? Steering clear from WPF up2now <g>,
i always thougth XAML as a standardized language to describe screens
and their behaviour, why shouldn't that work without VS/MS?

Just curious...
Karl
Regards

Karl

[toc] | [prev] | [next] | [standalone]


#11435

From"Wolfgang Riedmann" <wriedmann@gmail.com>
Date2018-02-26 13:43 +0100
Message-ID<ffidmtFbd58U1@mid.individual.net>
In reply to#11434
Hi Karl,

> > Unfortunately it is not possible use XAML with a non-Microsoft
> > application,
> would you care to elaborate a bit? Steering clear from WPF up2now <g>,
> i always thougth XAML as a standardized language to describe screens
> and their behaviour, why shouldn't that work without VS/MS?

Chris has invested some time, and tried several times to integrate XAML
compilation in XIDE, but failed.

Of course you can load XAML stylesheets at runtime (that is what I do),
but it is not possible to compile XAML to BAML. AFAIK it is Visual
Studio that does the XAML-to-BAML compilation, and only the BAML is
added as resource to the executable.
And for example it is not possible to inherit from a XAML based window
- the approach we have done for ages in VO (you can do it, but there is
some additional code needed).

I will show some code at the Koln conference that demonstrates the
power of WPF.

Wolfgang


-- 

[toc] | [prev] | [next] | [standalone]


#11436

FromChris Pyrgas <"chris (at)"@xsharp.eu>
Date2018-02-26 15:05 +0200
Message-ID<p710lp$19v3$1@gioia.aioe.org>
In reply to#11435
Guys,

 >>> Unfortunately it is not possible use XAML with a non-Microsoft
>>> application,
>> would you care to elaborate a bit? Steering clear from WPF up2now <g>,
>> i always thougth XAML as a standardized language to describe screens
>> and their behaviour, why shouldn't that work without VS/MS?
>
> Chris has invested some time, and tried several times to integrate XAML
> compilation in XIDE, but failed.


To be honest, I failed to do a WPF editor not because it is not possible 
to do it (the SharpDevelop guys have developed an in-house XAML/WPF 
editor), but because I am not really familiar with how WPF works. It was 
also very upsetting dealing with the complicated implementation 
details...WPF is extremely powerful, but the whole XAML/BAML scheme, the 
way code is generated from it and things like that were not good for my 
blood pressure, so I gave up :). Especially when comparing it with 
Windows Forms, which is designed in a straightforward enough way, which 
made it easy enough to create a completely custom form editor for 
it...(and not only it!)

Chris
(X# team)


>
> Of course you can load XAML stylesheets at runtime (that is what I do),
> but it is not possible to compile XAML to BAML. AFAIK it is Visual
> Studio that does the XAML-to-BAML compilation, and only the BAML is
> added as resource to the executable.
> And for example it is not possible to inherit from a XAML based window
> - the approach we have done for ages in VO (you can do it, but there is
> some additional code needed).
>
> I will show some code at the Koln conference that demonstrates the
> power of WPF.
>
> Wolfgang
>
>

[toc] | [prev] | [next] | [standalone]


#11437

From"Wolfgang Riedmann" <wriedmann@gmail.com>
Date2018-02-26 14:51 +0100
Message-ID<ffihmlFc9peU1@mid.individual.net>
In reply to#11436
Hi Chris,

> To be honest, I failed to do a WPF editor not because it is not
> possible to do it (the SharpDevelop guys have developed an in-house
> XAML/WPF editor), but because I am not really familiar with how WPF
> works. 

I already have an idea how a WPF window editor could be made without
XAML - like the XIDE WinForms editor it could create normal X# code.
Such an editor should use the Canvas content control, but it would
loose the biggest advantages of X#: the dynamic layout.

Wolfgang

-- 

[toc] | [prev] | [next] | [standalone]


#11438

FromD.J.W. van Kooten <vankooten@removethis.ic2.com>
Date2018-02-26 23:14 +0100
Message-ID<ah199dlo2b3tub6jir08aii6a70lags1d7@4ax.com>
In reply to#11436
Replying on message of Mon, 26 Feb 2018 15:05:43 +0200 from Chris
Pyrgas:


 Hello Chris,

>.WPF is extremely powerful, but the whole XAML/BAML scheme, the 
>way code is generated from it and things like that were not good for my 
>blood pressure, 


I think the WPF team first designed Visual Studio. It's the same mess,
extremly powerful no doubt and not good for my blood preasure either
;)

Dick

[toc] | [prev] | [next] | [standalone]


#11442

From"Wolfgang Riedmann" <wriedmann@gmail.com>
Date2018-02-27 07:12 +0100
Message-ID<ffkb6nFolviU1@mid.individual.net>
In reply to#11438
Hi Dick,

> > .WPF is extremely powerful, but the whole XAML/BAML scheme, the 
> > way code is generated from it and things like that were not good
> > for my blood pressure, 
> 
> 
> I think the WPF team first designed Visual Studio. It's the same mess,
> extremly powerful no doubt and not good for my blood preasure either
> ;)

no, I think it was the way around. They built WPF and saw that it was
very powerful, but without graphical editor nobody would use it.

It took several editions of Visual Studio until the WPF editor was
working how it works today. And I'm pretty sure the WPF people needed
to help the VS people very often.
If you see how complicated some expressions are in XAML and how simple
they are in code, you will understand.

To see the real power of WPF you need to think it in a completely
different manner - more like HTML then Windows GUI.

Wolfgang


-- 

[toc] | [prev] | [next] | [standalone]


#11444

FromKarl Faller <mail_withoutthat_@_drei-f_andthat_.de>
Date2018-02-27 09:23 +0100
Message-ID<qm3a9dp98b8airn59t4ha7mmnoh0i3he1e@4ax.com>
In reply to#11442
Wolfgang,
>To see the real power of WPF you need to think it in a completely
>different manner - more like HTML then Windows GUI.
You use both to interact with the user. Output to screen, input from
keyboard and/or a pointing device having properties like position and
actions like point & click,  maybe reacting to other running code.  
One wonders why it needs x-thousands of lines of code/files to make
this work ;-)

Karl
Regards

Karl

[toc] | [prev] | [next] | [standalone]


#11433

FromD.J.W. van Kooten <vankooten@removethis.ic2.com>
Date2018-02-26 12:40 +0100
Message-ID<h3s79ddus4b5jlbd9h6la669m57abukn37@4ax.com>
In reply to#11424
Replying on message of Sat, 24 Feb 2018 22:33:57 +0100 from Karl
Faller:


 Hello Karl,

>>Chris has written Xide, ...and doesn't support WPF,
>FTR, not quite true. There's no wpf forms designer there, but WPF
>itself works, ask Wolfgang, who works with XIDE and WPF only in coded
>form...
>
That's true of course, but although I do appreciate the idea of a
designed which basically generates code (like the 1:1 connection in
VS: change something in the designer and the XAML changes and v.v.) my
first choice is always to use a designer. Building screens from code
without seeing it in a designer doesn't look very appealing to me.

I admire Chris' work in every respect, but having chosen for WPF as
the forms I use, I -unfortunately- have to choose VS.

Dick

[toc] | [prev] | [standalone]


Back to top | Article view | comp.lang.clipper.visual-objects


csiph-web