Hmm when I first tried adding pyvcp panels (a few years ago), I
Remember spending more then a few frustrating hours on it.
Then again I didn't have the excellent documentation that's
available now...
I took me quite a while playing with the GLADE editor too though.
That's not a fair comparison anyways as I developed the beginning
of gladeVCP so knew how it worked...
The real reason to drop pyvcp is to drop tkinter.
And in that case AXIS would need to be rewritten/replaced with
a no tcl/tkinter screen.
As I understand it, one of linuxcnc3's mandates is to shorten the list
of used languages.
But of course this is just me talking - time will tell what happens :)
Chris M
>
> I don't think you can beat how simple it is to add a simple PyVCP panel
> to Axis.
>
> On 10/20/2012 2:29 PM, Chris Morley wrote:
> >
> >> The diversification just keeps on growing!
> >>
> >> I have no experience writing for any of these. Is it going to be
> >> possible to factor applications like GladeVCP so that the choice of
> >> system technology can be made (relatively) trivially at build time?
> >>
> > We will need to write a glade3vcp module but after that its easy to
> > pick at build time, AFAIK there is no conversion program but I have not
> > looked very hard.
> > GTK2 and pygtk packages are sure to be around awhile but for instance
> > the current GLADE editor doesn't edit GTK2 glade files AFAIK.
> > I would foresee gtk3VCP and qtVCP be in a linuxcnc3 and dropping pyVCP.
------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_sfd2d_oct
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
