yes this is true they would have to re edit their glade file.
> mostly cut and paste.
> I don't really see a large burden with that. We try not to do
> major changes between major releases.
> besides that would be a choice the user makes. Edit the glade
> file means you must maintain it after updates. Use Embedded
> tabs - don't worry about updates.
> As for devs supporting users - it is pretty simple.
> Erase the glade file. If touchy works then the glade file needs
> work.
>
My two cents also does not see a large burden especially when it is the
user's choice. To allow the best user's decision the update/upgrade
particulars should be clearly explained/revealed.
> > > I might add that your command:
> > > xterm -into {XID} -rv -fn
> > > ...
> > > Where loading a gladefile modifying it then saving it is more
> > > user friendly.
> >
> > It's a cute trick that shows how flexible the scheme is. In a more
> > typical case, the command line would be one that makes a vcp panel.
> > It is no more complicated than a loadusr line in a hal file is.
> >
> Actually loadusr is cryptic. You have no idea how many hours I spent
> with classicladder and pyvcp trying to get them to load/work properly when
> I started. It's easy for us devs to forget how much one must learn all at
> once to configure EMC.
>
I agree with the overwhelming appearance of a first look.
>
> > Glade files are fragile because of their interdependence with the rest
> > of the source code regarding things like widget names. I think you
> > greatly overestimate the extent to which modifying a screen (without
> > breaking it) in glade is easy and user-friendly. I know you're an
> > experienced user of glade.
>
> Well this may be true. By user friendly I meant point and click.
> It would not take long to write a page about how to stay out of major
> trouble when modifying Touchy.
>
Point and click, Plug and Play - sometimes not compatible with 'user
friendly'
> >
> > > Why not have both options? embedding and custom glade files?
>
Could not agree more!!!
> >
> > Because I think the problems the custom diverging glade file scheme
> > will cause are onerous and will be a pain in the neck for users and
> > those supporting them (especially me).
>
> Yes I guess we just disagree about that. There would be problems I just
> don't think end-of-the-world pain. :)
>
My only comment here is 'the current support from EMC2 is incredible'
> >
> > Pavel's changes cause EXACTLY NONE of these problems that worry me.
> > His changes give almost as much flexibility without causing the
> > fragility and merge problems.
> >
> > Chris
>
> His changes only allows multiple tabs on the main notebook I think.
> This is allows some pretty damn cool things ( that my patch can not )
> and is enough for most people but is no where near as flexible as
> directly editing the glade file.
>
> Anyways since there is no interest for my changes I will drop it.
>
I have been watching this and meaning to try it. This type of development
is part of the fundamental reason for open software - CHOICES
>
> BTW while testing all this I gotta say Touchy is nicely intuitive.
> Add a preview tab then its an alternative to AXIS even with out
> a touch screen.
>
I guess as an operator/programmer for production work I don't see much
need for a preview. For single parts/tooling the preview can be useful.
>
> Cheers Chris M
>
>
--
dos centavos
------------------------------------------------------------------------------
Beautiful is writing same markup. Internet Explorer 9 supports
standards for HTML5, CSS3, SVG 1.1, ECMAScript5, and DOM L2 & L3.
Spend less time writing and rewriting code and more time creating great
experiences on the web. Be a part of the beta today.
http://p.sf.net/sfu/beautyoftheweb
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers