Bugs item #2795993, was opened at 2009-05-23 23:18
Message generated for change (Tracker Item Submitted) made by jepler
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=106744&aid=2795993&group_id=6744
Please note that this message will contain a full copy of the com
My 2 cents...
I'm new to emc. I chose emc for my lathe after using mach for my mill,
mainly for the threading support, but also because it was open source.
I was very impressed with the internal architecture of emc, and how easy it
was to build and a configure a system with components, pins an
Axis could be MUCH more than what it is, and maybe it would if the code base
was more attractive. tk, the gui toolkit used is the single worst choice that
you can make, and it's the main driver of the code's disorganization.
Refactoring axis to a better structured project that use the very bes
Maxime,
Your willingness to contribute is certainly appreciated. My view is that a
new user interface needs a raison d'etre, where such things as simply
reorganizing the code or rewriting it in a modern gui environment would not
seem to meet that test. I can't speak for Axis on a coding level beca
Bugs item #2795877, was opened at 2009-05-23 17:31
Message generated for change (Tracker Item Submitted) made by nobody
You can respond by visiting:
https://sourceforge.net/tracker/?func=detail&atid=106744&aid=2795877&group_id=6744
Please note that this message will contain a full copy of the com
I could argue that such a "casual user" could hurt himself in many ways, and
shouldn't be given access to the machine.
I'd rather postpone the stepconf discussion to later, it is not high priority
to me. Which brings us back to :
- AXIS code organization/refactoring
- opinion on the migra
