These are chat archives for machinekit/machinekit

30th
Nov 2015
Bas de Bruijn
@luminize
Nov 30 2015 06:10
I think both are valuable, (but both certainly not prio1). Can i ask you to try out http://thebrain.com make a small mindmap and navigate thru that map? Use the keyboard. Now if we can have that behaviour, with or without GUI imo that would bring focus to the component when making a configuration.
Michael Haberler
@mhaberler
Nov 30 2015 06:15
I am lost, are you suggesting a mindmap to explain something, or to devise a GUI like that program?
Bas de Bruijn
@luminize
Nov 30 2015 06:18
Just install it and try it out ;) takes 5 minutes
Michael Haberler
@mhaberler
Nov 30 2015 06:19
well I know what a mind map is and have used it in the past - fine, but then what is the plan
Bas de Bruijn
@luminize
Nov 30 2015 06:23
It's about navigating that mind map, and keeping focus on the thing you're doing. Install the trial, play around and visualize a component instead of a node when you navigate that map. Go on, that's an order. Report back when you have given it thought. :) can't explain more if you haven't tried it
Michael Haberler
@mhaberler
Nov 30 2015 10:04
Sorry - I do not share the enthusiasm expressed here, so I will not engage. On the order of import/urgent/wise use of scarce developer time I doubt it is either, besides being an evidently ill-defined problem (maintenance? design? inspection?).
Bas de Bruijn
@luminize
Nov 30 2015 10:08
That's what I originally said: no prio uno. Just an idea. But if the goal is re-usability also in other projects than making/changing Hal configurations is IMO important. And the current HAL file is bad in usability and readability.
Bas de Bruijn
@luminize
Nov 30 2015 10:52
:point_up: November 30, 2015 12:08 AM
what would you like yourself when you're making HAL files? like the inspector idea ? would you want big overview of everything? or maybe show component xxx where you can easily fly to the component that is attached via a signal? maybe some shortcuts?
Michael Haberler
@mhaberler
Nov 30 2015 11:07
I am oldfashioned, so none of it
halshow eventually needs replacement as all the tcl/tk stuff should go, and that is an inspector/modifier
if anything, the driving datastructure should be the protobuf representation of HAL, not yet another layer of XML or whatnot ontop
Bas de Bruijn
@luminize
Nov 30 2015 11:25
I was thinking about revamping halrun/halcmd? Would that be something for ye olde fashioners ;) personally I like the simplicity/keyboard of halrun, but when configs get bigger I lose the overview
GP Orcullo
@kinsamanka
Nov 30 2015 13:47
Hey guys, how do we deal with the version numbers for the packaging?
Michael Haberler
@mhaberler
Nov 30 2015 15:19
Until @zultron returns, maybe just use Unix timestamp (and make it a bash function so it's easily replaced)
it needs to be fixed just before feeding @zultron ' apt repo again