> From: Alexey Starikovskiy <[email protected]>
> On 09/17/2010 12:09 AM, Colin Kingsbury wrote:
> > I have some very specific ideas about what I would like in my GUI, and
> > rather than starting yet another GUI from scratch, I thought I'd try
> <SNIP>
> AXIS is a mix of C++, python and Tcl/Tk. Here are 3 main files to start
> from:
> ./share/axis/tcl/axis.tcl
> ./src/emc/usr_intf/axis/scripts/axis.py
> ./lib/python/rs274/glcanon.py
>
>
OK. I spent some time reading the source and also took a tour through the
Touchy source and have a handful of questions as a result:
1. What is the purpose of the axis.tcl script in the whole stack? The
Axis.py is pretty minimally-documented/commented, so I don't think I've
really got a good sense of exactly how the pieces fit together and which is
responsible for what. I should confess that I've never used Tcl before, so
if this is following a pretty classic design pattern and I just need to read
a Tcl/Tk book, then say so :)
2. Has anyone run Axis in a debugger/IDE? I'm thinking that if I could set a
few breakpoints and step through it, I'll have a lot easier time making
sense of it. I'm agnostic on IDEs so if anyone has a known-good
configuration, I'd start there.
3. Switching over to Touchy, I noticed that there seems to be both an EMC
interface library and a HAL interface as well. While I (think) I understand
the role HAL plays in an architectural sense, it's not immediately clear to
me why a GUI would do some things by talking to EMC directly and other
things by talking to HAL directly.
Thanks in advance!
-cwk.
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
Emc-developers mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/emc-developers
