Hey Guys
Chris thanks for responding about Touchy.
> Date: Thu, 12 Aug 2010 09:17:51 -0500
>
> Thanks for your work on this and I'm very open to having part of
> touchy be a customizable vcp. However I'm worried that letting the
> user modify whatever he wants in glade is going to cause trouble and
> break the existing functionality of touchy.
>
I never thought of this at the time good point.
> Now on to my counter-idea:
>
> With the way AXIS does vcp in mind (the user widgets adjacent to the
> fixed widgets), I wonder if touchy could have a "User" tab. If there
> was a touchy-vcp.glade file in the configuration, could touchy create
> a User tab and add those glade widgets to it? Or maybe do like in
> AXIS, where the user widgets are beside the fixed widgets?
>
> Having the user working with just his own widgets in glade seems
> really superior to having him working with all of the touchy layout,
> which is kind of intricate.
>
IMHO:
I would prefer not limit people on what they can do with touchy / VCP.
I figure if they can get EMC configured for a large machine they can
figure out how to modify touchy with out breaking it. (and it's easy to test)
I'll use HAL as a quick example: we don't really limit what people
can do with HAL components (It's pretty easy to break a HAl
config so it won't even run) Instead, we document and encourage
interactive experimenting. with out the limits we gain great
flexibility for a large variety of machines / taste.
Yes it means we have to field some questions about problems encountered.
While having a special spot for user VCP is a good idea, I don't think
we should force the user to abide. In AXIS I sometimes wish I could
put pyvcp panels somewhere else but cannot. Not because they can't go there
but because someone choose were I could put them. (though I must say it works
well and not many questions about AXIS not working with pyvcp panels)
So here is my counter-counter idea :)
- Allow editing of the full touchy glade file.
- Document the hazards of modifying the standard widget set in manual.
- encourage people to use a special panel for user widgets by:
telling people 'if you put widgets HERE you will not ever break touchy'
Making it obvious. for instance add the note book with a tab for userVCP
blank to standard touchy glade. (if the tab is empty it won't show up)
Telling them in manual "Use the userVCP tab and Touchy will always work"
- reminding people if you really screw up touchy so it doesn't work
delete the edited glade file and touchy will use the default screen again.
> I do not know if it's possible for a second glade file to be loaded
> after the initial one - do you know about this?
>
As Jeff pointed out yes we could .
Why not allow full editing in master for now and if it ends up being a real
problem
we could switch to a separate glade file before releasing it.
Chris M
------------------------------------------------------------------------------
This SF.net email is sponsored by
Make an app they can't live without
Enter the BlackBerry Developer Challenge
http://p.sf.net/sfu/RIM-dev2dev
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
