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


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

Facelift Pro 2 for VO released

Started by"Paul Piko" <paul_remove@piko.com.au>
First post2016-03-04 14:27 +1100
Last post2016-03-16 11:55 +0100
Articles 10 — 4 participants

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


Contents

  Facelift Pro 2 for VO released "Paul Piko" <paul_remove@piko.com.au> - 2016-03-04 14:27 +1100
    Re: Facelift Pro 2 for VO released "Rene J. Pajaron" <rjpajaron@gmail.com> - 2016-03-13 19:13 -0700
      Re: Facelift Pro 2 for VO released "Paul Piko" <paul_remove@piko.com.au> - 2016-03-14 17:54 +1100
        Re: Facelift Pro 2 for VO released "Rene J. Pajaron" <rjpajaron@gmail.com> - 2016-03-14 05:04 -0700
    Re: Facelift Pro 2 for VO released D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2016-03-14 14:11 +0100
      Re: Facelift Pro 2 for VO released "Rene J. Pajaron" <rjpajaron@gmail.com> - 2016-03-14 21:34 -0700
        Re: Facelift Pro 2 for VO released D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2016-03-15 11:55 +0100
          Re: Facelift Pro 2 for VO released Karl Faller <mail_withoutthat_@_drei-f_andthat_.de> - 2016-03-15 14:00 +0100
          Re: Facelift Pro 2 for VO released "Rene J. Pajaron" <rjpajaron@gmail.com> - 2016-03-15 16:24 -0700
            Re: Facelift Pro 2 for VO released D.J.W. van Kooten <vankooten@removethis.ic2.com> - 2016-03-16 11:55 +0100

#9098 — Facelift Pro 2 for VO released

From"Paul Piko" <paul_remove@piko.com.au>
Date2016-03-04 14:27 +1100
SubjectFacelift Pro 2 for VO released
Message-ID<nbb007$19vi$1@gioia.aioe.org>
I am happy to release the second version of Facelift Professional for Visual
Objects.

Facelift Pro takes VO window entities and turns them into Windows Forms/WPF
source code that can be used in Visual Studio's visual form designers. This
means you don't have to spend your time re-drawing windows when you want to
move to a new .NET GUI; you can avoid that error-prone, tedious, manual
labour and have Facelift prepare your new windows. This lets you concentrate
on the other tasks needed to move to the new GUI.

This release brings Visual Studio 2015 support, updates for the current
framework, and new language templates.

Facelift outputs code in your choice of 4 .NET languages - C#, VB.NET,
Vulcan.NET and X#.

People with a current Facelift Pro licence can move to version 2
immediately; the version 1 licence file is valid for use with version 2!

More details are available here: http://www.piko.com.au/facelift

Regards,
Paul Piko 

[toc] | [next] | [standalone]


#9144

From"Rene J. Pajaron" <rjpajaron@gmail.com>
Date2016-03-13 19:13 -0700
Message-ID<ae08acf5-2b60-4cbb-b524-cf49dcc82f4e@googlegroups.com>
In reply to#9098
Hi Paul,

this is great.

This will make me take another hard look in converting our huge VO apps to .NET again.  Just upgraded to latest VO service packs last December.

If I can smoothly convert each forms to WinForms/WPF, and port it slowly it for Telerik WinForms/WPF that would be great.  I once contacted you if I can do this automatically.  I have Telerik DevCraft Complete.

Let me know if I can download a demo version of this and do some sampling conversion.

--

Rene



On Friday, March 4, 2016 at 11:38:54 AM UTC+8, Paul Piko wrote:
> I am happy to release the second version of Facelift Professional for Visual
> Objects.
> 
> Facelift Pro takes VO window entities and turns them into Windows Forms/WPF
> source code that can be used in Visual Studio's visual form designers. This
> means you don't have to spend your time re-drawing windows when you want to
> move to a new .NET GUI; you can avoid that error-prone, tedious, manual
> labour and have Facelift prepare your new windows. This lets you concentrate
> on the other tasks needed to move to the new GUI.
> 
> This release brings Visual Studio 2015 support, updates for the current
> framework, and new language templates.
> 
> Facelift outputs code in your choice of 4 .NET languages - C#, VB.NET,
> Vulcan.NET and X#.
> 
> People with a current Facelift Pro licence can move to version 2
> immediately; the version 1 licence file is valid for use with version 2!
> 
> More details are available here: http://www.piko.com.au/facelift
> 
> Regards,
> Paul Piko

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


#9145

From"Paul Piko" <paul_remove@piko.com.au>
Date2016-03-14 17:54 +1100
Message-ID<nc5n89$1p5m$1@gioia.aioe.org>
In reply to#9144
Hi Rene,

Yes, I did start on Telerik versions of the templates.

E.g. I took the existing Facelift Win Forms templates and replaced:

System.Windows.Forms.Form with Telerik.WinControls.UI.RadForm

System.Windows.Forms.TextBox with Telerik.WinControls.UI.RadMaskedEditBox

etc

Unfortunately I didn't finish it off before the Telerik evaluation period 
was over. I need a list of the Telerik controls that correspond to the 
standard Windows Forms/WPF ones, and any creation code differences. Then it 
is just a matter of updating the templates.

Regards,
Paul


"Rene J. Pajaron"  wrote in message 
news:ae08acf5-2b60-4cbb-b524-cf49dcc82f4e@googlegroups.com...

Hi Paul,

this is great.

This will make me take another hard look in converting our huge VO apps to 
.NET again.  Just upgraded to latest VO service packs last December.

If I can smoothly convert each forms to WinForms/WPF, and port it slowly it 
for Telerik WinForms/WPF that would be great.  I once contacted you if I can 
do this automatically.  I have Telerik DevCraft Complete.

Let me know if I can download a demo version of this and do some sampling 
conversion.

--

Rene



On Friday, March 4, 2016 at 11:38:54 AM UTC+8, Paul Piko wrote:
> I am happy to release the second version of Facelift Professional for 
> Visual
> Objects.
>
> Facelift Pro takes VO window entities and turns them into Windows 
> Forms/WPF
> source code that can be used in Visual Studio's visual form designers. 
> This
> means you don't have to spend your time re-drawing windows when you want 
> to
> move to a new .NET GUI; you can avoid that error-prone, tedious, manual
> labour and have Facelift prepare your new windows. This lets you 
> concentrate
> on the other tasks needed to move to the new GUI.
>
> This release brings Visual Studio 2015 support, updates for the current
> framework, and new language templates.
>
> Facelift outputs code in your choice of 4 .NET languages - C#, VB.NET,
> Vulcan.NET and X#.
>
> People with a current Facelift Pro licence can move to version 2
> immediately; the version 1 licence file is valid for use with version 2!
>
> More details are available here: http://www.piko.com.au/facelift
>
> Regards,
> Paul Piko 

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


#9147

From"Rene J. Pajaron" <rjpajaron@gmail.com>
Date2016-03-14 05:04 -0700
Message-ID<2246a856-4eea-4c71-9f51-6a546cf7727c@googlegroups.com>
In reply to#9145
Hello Paul,

I will send you private message.

Thanks,

Rene

On Monday, March 14, 2016 at 2:55:11 PM UTC+8, Paul Piko wrote:
> Hi Rene,
> 
> Yes, I did start on Telerik versions of the templates.
> 
> E.g. I took the existing Facelift Win Forms templates and replaced:
> 
> System.Windows.Forms.Form with Telerik.WinControls.UI.RadForm
> 
> System.Windows.Forms.TextBox with Telerik.WinControls.UI.RadMaskedEditBox
> 
> etc
> 
> Unfortunately I didn't finish it off before the Telerik evaluation period 
> was over. I need a list of the Telerik controls that correspond to the 
> standard Windows Forms/WPF ones, and any creation code differences. Then it 
> is just a matter of updating the templates.
> 
> Regards,
> Paul
> 
> 
> "Rene J. Pajaron"  wrote in message 
> news:ae08acf5-2b60-4cbb-b524-cf49dcc82f4e@googlegroups.com...
> 
> Hi Paul,
> 
> this is great.
> 
> This will make me take another hard look in converting our huge VO apps to 
> .NET again.  Just upgraded to latest VO service packs last December.
> 
> If I can smoothly convert each forms to WinForms/WPF, and port it slowly it 
> for Telerik WinForms/WPF that would be great.  I once contacted you if I can 
> do this automatically.  I have Telerik DevCraft Complete.
> 
> Let me know if I can download a demo version of this and do some sampling 
> conversion.
> 
> --
> 
> Rene
> 
> 
> 
> On Friday, March 4, 2016 at 11:38:54 AM UTC+8, Paul Piko wrote:
> > I am happy to release the second version of Facelift Professional for 
> > Visual
> > Objects.
> >
> > Facelift Pro takes VO window entities and turns them into Windows 
> > Forms/WPF
> > source code that can be used in Visual Studio's visual form designers. 
> > This
> > means you don't have to spend your time re-drawing windows when you want 
> > to
> > move to a new .NET GUI; you can avoid that error-prone, tedious, manual
> > labour and have Facelift prepare your new windows. This lets you 
> > concentrate
> > on the other tasks needed to move to the new GUI.
> >
> > This release brings Visual Studio 2015 support, updates for the current
> > framework, and new language templates.
> >
> > Facelift outputs code in your choice of 4 .NET languages - C#, VB.NET,
> > Vulcan.NET and X#.
> >
> > People with a current Facelift Pro licence can move to version 2
> > immediately; the version 1 licence file is valid for use with version 2!
> >
> > More details are available here: http://www.piko.com.au/facelift
> >
> > Regards,
> > Paul Piko

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


#9148

FromD.J.W. van Kooten <vankooten@removethis.ic2.com>
Date2016-03-14 14:11 +0100
Message-ID<asddebpp9stdf52ot3aruson27274u3tg7@4ax.com>
In reply to#9098
On Fri, 4 Mar 2016 14:27:20 +1100, "Paul Piko"
<paul_remove@piko.com.au> wrote:

Hello Paul,

>I am happy to release the second version of Facelift Professional for Visual
>Objects.

Congratulations!

We have not -yet- decided to move our VO programs to .Net. I think the
next thing to try out is if I can use Vide/Xide to do more of my daily
work. Especially working with VS whole day is a major reason why I'd
prefer to keep working with VO, Vide/Xide solving part of the
unpleasant experience.

However, if & when I move, I think Facelift  is a necessity to
convert. Staying with the VO type windows while working in .Net feels
a bit like keeping the command prompt based Clipper programs in VO in
the '90s.

Dick

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


#9150

From"Rene J. Pajaron" <rjpajaron@gmail.com>
Date2016-03-14 21:34 -0700
Message-ID<54cfe93f-00b4-44e5-8d4e-5d9c3384230f@googlegroups.com>
In reply to#9148
On Monday, March 14, 2016 at 9:12:06 PM UTC+8, D.J.W. van Kooten wrote:
> On Fri, 4 Mar 2016 14:27:20 +1100, "Paul Piko"
> <paul_remove@piko.com.au> wrote:
> 
> Hello Paul,
> 
> >I am happy to release the second version of Facelift Professional for Visual
> >Objects.
> 
> Congratulations!
> 
> We have not -yet- decided to move our VO programs to .Net. I think the
> next thing to try out is if I can use Vide/Xide to do more of my daily
> work. Especially working with VS whole day is a major reason why I'd
> prefer to keep working with VO, Vide/Xide solving part of the
> unpleasant experience.
> 
> However, if & when I move, I think Facelift  is a necessity to
> convert. Staying with the VO type windows while working in .Net feels
> a bit like keeping the command prompt based Clipper programs in VO in
> the '90s.
> 
> Dick

Dick,

F4 is the hotkey I hated most in VO.  It is tiring reading your constant bashing of VS or anything Microsoft.  You remind me of my father in law.

--

Rene

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


#9151

FromD.J.W. van Kooten <vankooten@removethis.ic2.com>
Date2016-03-15 11:55 +0100
Message-ID<3bqfeb1joo4jshceietrhh7h9t29aos36e@4ax.com>
In reply to#9150
On Mon, 14 Mar 2016 21:34:41 -0700 (PDT), "Rene J. Pajaron"
<rjpajaron@gmail.com> wrote:

Hello Rene,

>F4 is the hotkey I hated most in VO.  

? 

Then don't press it. I'd say. It cascades windows....


>It is tiring reading your constant bashing of VS or anything Microsoft.  You remind me of my father in law.

Then don't read it. But it's good someone defends poor old Microsoft
of course.

I don't know your father in law. He dislikes VS as well I understand.
I can imagine that.

Dick

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


#9159

FromKarl Faller <mail_withoutthat_@_drei-f_andthat_.de>
Date2016-03-15 14:00 +0100
Message-ID<ar1geb993vik34lgt1ararltgodubcrqh3@4ax.com>
In reply to#9151
Dick,
>I don't know your father in law. He dislikes VS as well I understand.
>I can imagine that.
<rofl>

Karl

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


#9163

From"Rene J. Pajaron" <rjpajaron@gmail.com>
Date2016-03-15 16:24 -0700
Message-ID<3ebec4f6-e32d-45fa-a018-6bbd320e8e82@googlegroups.com>
In reply to#9151
Hi Dick,

My father in law is a great man.  It is a compliment actually, if you know him. 

F3 seat beside F4. When search something, with lots of SCE windows open, split screen all the place, and I have press F3 to search within the context of focus SCE window, 5 in 100 press of F3, landed on F4. I have to ask, is there a chance to disable this hotkey.

--

Rene
On Tuesday, March 15, 2016 at 6:55:42 PM UTC+8, D.J.W. van Kooten wrote:
> On Mon, 14 Mar 2016 21:34:41 -0700 (PDT), "Rene J. Pajaron"
> <rjpajaron@gmail.com> wrote:
> 
> Hello Rene,
> 
> >F4 is the hotkey I hated most in VO.  
> 
> ? 
> 
> Then don't press it. I'd say. It cascades windows....
> 
> 
> >It is tiring reading your constant bashing of VS or anything Microsoft.  You remind me of my father in law.
> 
> Then don't read it. But it's good someone defends poor old Microsoft
> of course.
> 
> I don't know your father in law. He dislikes VS as well I understand.
> I can imagine that.
> 
> Dick

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


#9170

FromD.J.W. van Kooten <vankooten@removethis.ic2.com>
Date2016-03-16 11:55 +0100
Message-ID<sreiebpos05javuqftfhjk7if80aso552r@4ax.com>
In reply to#9163
On Tue, 15 Mar 2016 16:24:54 -0700 (PDT), "Rene J. Pajaron"
<rjpajaron@gmail.com> wrote:

Hello Rene,
>
>My father in law is a great man.  It is a compliment actually, if you know him. 

I don't know but I thank you for the compliment then. I hope you don't
find him tiring however <g>.

>
>F3 seat beside F4. When search something, with lots of SCE windows open, split screen all the place, 
>and I have press F3 to search within the context of focus SCE window, 5 in 100 press of F3, 
> landed on F4. I have to ask, is there a chance to disable this hotkey.

Ok, I understand. I don't think you can easily disable it. There are
so called keyboard hook programs. Not sure if they can override
shortcut keys in an active Windows program as VO but it's maybe worth
a try. Ideally there should have been a counter shortcut to restore
windows to maximized in VO.

Dick

[toc] | [prev] | [standalone]


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


csiph-web