#hazzy | Logs for 2018-09-05
Back
[00:07:21] <Lcvette> Sweet turboss!!! That's awesomesauce!!!
[00:07:47] <Lcvette> I'm nurturing confused kitties
[01:10:08] -!- hazzy-lab has quit [Quit: Leaving.]
[01:34:30] -!- hazzy-lab has joined #hazzy
[01:34:30] -!- mode/#hazzy [+o hazzy-lab] by ChanServ
[01:42:47] -!- hazzy-lab has quit [Quit: Leaving.]
[02:54:58] -!- hazzy-dev has quit [Remote host closed the connection]
[02:55:16] -!- hazzy-dev has joined #hazzy
[09:31:14] -!- hazzy-lab has joined #hazzy
[09:31:14] -!- mode/#hazzy [+o hazzy-lab] by ChanServ
[09:45:53] <hazzy-m> morning
[09:46:54] <jthornton> morning
[09:49:36] * hazzy-m uploaded an image: jack-hijacks-cnc.jpg (320KB) < https://matrix.org >
[09:50:07] <hazzy-m> my nephew hijacked the cnc router, lol
[11:40:04] -!- Roguish has joined #hazzy
[12:56:22] <TurBoss> morning
[13:53:03] <Lcvette> morning
[13:55:34] <Lcvette> turboss is file system ready?
[14:26:28] -!- Roguish has quit [Remote host closed the connection]
[15:17:59] -!- Roguish has joined #hazzy
[15:49:27] -!- jthornton has quit [Read error: Connection reset by peer]
[15:49:27] -!- JT-Shop has quit [Read error: Connection reset by peer]
[15:53:54] -!- JT-Shop has joined #hazzy
[15:53:54] -!- jthornton has joined #hazzy
[17:21:33] -!- jthornton has quit [Read error: Connection reset by peer]
[17:23:41] -!- JT-Shop has quit [Read error: Connection reset by peer]
[17:24:10] -!- JT-Shop has joined #hazzy
[17:32:53] -!- robotustra has joined #hazzy
[17:35:00] <robotustra> what does [m] mean?
[17:35:30] <hazzy-m> the matrix :)
[17:35:52] <robotustra> matrix group?
[17:36:25] <hazzy-m> https://matrix.org
[17:36:49] <hazzy-m> Most of us on here are using matrix rather than IRC chat
[17:37:20] <robotustra> is it kind of telegram?
[17:37:29] <hazzy-m> it allows direct sharing of pictures and code with syntax highlighting etc.
[17:37:40] <robotustra> ok
[17:37:56] <robotustra> collaboration tool for developers?
[17:37:58] <hazzy-m> yes, it is like telegram
[17:38:54] <robotustra> I did some matrix today too.. https://imgur.com :)
[17:39:19] <robotustra> version 0.1 of my layout :)
[17:39:39] <hazzy-m> that looks awesome!!
[17:39:55] <robotustra> hope it will work awersome too
[17:39:59] <hazzy-m> did you figure out how to comunicate with LCNC?
[17:40:05] <robotustra> yes
[17:40:21] <robotustra> I will connect through linuxcncrsh
[17:40:34] <robotustra> I already tried yesterday
[17:40:36] <hazzy-m> Ok, that should work fine
[17:40:50] <hazzy-m> and then you can even have a remote interface :D
[17:41:20] <robotustra> except that if I'll work remotely I'll have to make an access to files on linuxcnc machine
[17:41:28] <hazzy-m> would be great for low power machines like an RPi
[17:41:32] <robotustra> but it's doable
[17:41:35] <hazzy-m> oh, that is ture ...
[17:41:59] <robotustra> but it could be done like throug rcp
[17:43:27] <hazzy-m> or maybe even a simple SAMBA share would work
[17:44:26] <robotustra> it's a task #999
[17:45:15] <hazzy-m> yes, lol
[17:45:28] <robotustra> for the beginning I have to make polling and parsing of data from linuxcncrsh
[17:46:09] <hazzy-m> Have you looked at using NML directly? It is not very hard ..
[17:46:44] <robotustra> but why?
[17:46:49] <hazzy-m> It might be easier than using linuxcncrsh
[17:46:53] <robotustra> no
[17:47:00] <robotustra> a lot of code
[17:47:19] <robotustra> I can add some stuff to linuxcncrsh after
[17:47:34] <robotustra> if I'll need it and even make a binary mode
[17:47:59] <hazzy-m> Ok, that makes sense
[17:48:43] <robotustra> because the author of lcncrsh was going to implemen it
[17:48:53] <hazzy-m> Qt has a good web-sockets library, I thought about using that to make a more modern version of linuxcncrsh
[17:49:20] <robotustra> I use qtsocket to connect to lcncrsh
[17:49:35] <hazzy-m> great!
[17:51:04] <hazzy-m> This is getting really exciting, so many promising GUIs in the works
[17:51:51] <robotustra> I was looking very simple control gui to work with touch screen
[17:52:38] <robotustra> without keyboard, or with a dedicated keyboard at the machine
[17:52:47] <robotustra> not standard one
[17:53:03] <hazzy-m> Are you using QtQuick or QWidgets?
[17:54:18] <robotustra> what is qtQuick?
[17:56:07] <robotustra> my app is a usual QApplication with QMainWindow
[17:56:08] <hazzy-m> It uses QML (which is kinda like java) to define the interface layout and function, and then c++ for the "backend"
[17:56:22] <hazzy-m> ok
[17:56:29] <robotustra> no, I did it low level
[17:56:36] <hazzy-m> and you are styling with QSS?
[17:56:40] <robotustra> no
[17:56:47] <hazzy-m> sorry for all the questions :)
[17:56:56] <robotustra> it's ok
[17:57:19] <robotustra> I did it (may be) very dumb way
[17:57:38] <robotustra> it's described in forth like language
[18:00:23] <hazzy-m> very interesting! I'll have to read your code and see what you are doing
[18:01:54] <Lcvette> hazzy, you getting close to some button making time?
[18:02:03] <Lcvette> or pushing again?
[18:02:13] <hazzy-m> Lcvette: Yes, very close!
[18:02:23] <Lcvette> timeframe?
[18:03:19] <hazzy-m> hopefully tomorrow evening if I get back early enough
[18:03:39] <Lcvette> if not, following day or?
[18:03:42] <Lcvette> just plannign ym schedule
[18:03:53] <Lcvette> planning my*
[18:03:59] <hazzy-m> If now I should have almost allday Friday to work on them
[18:04:06] <hazzy-m> if not*
[18:04:27] <Lcvette> ok, i will plan on friday for sure and check in tomorrow evening
[18:04:42] <hazzy-m> sounds good!
[18:04:53] <hazzy-m> making any progress in the shop?
[18:05:05] <hazzy-m> how is the lathe project?
[18:05:12] <Lcvette> catching up on neglected business
[18:05:28] <hazzy-m> excellent
[18:05:43] <Lcvette> inventory stock had gotten pretty low
[18:06:04] <Lcvette> hoping to have things caught back up by close of business tomorrow, just finished for the day today
[18:06:16] <Lcvette> called in by the dinner bell
[18:06:59] <hazzy-m> enjoy!
[18:07:12] <Lcvette> whats left on your vcp launcher
[18:07:22] <Lcvette> almost wrapped up with it?
[18:07:26] <robotustra> hazzy-m, my ini file looks like this https://pastebin.com
[18:07:37] <robotustra> and it's long
[18:07:51] <hazzy-m> Lcvette: very close to haveing it wrapped up!!!!
[18:11:13] <hazzy-m> robotustra: wow! So the icons are defined by the gcode looking commands?
[18:11:25] <robotustra> yes
[18:11:37] <robotustra> actually the syntax is very simple
[18:11:38] <hazzy-m> VERY NICE!
[18:11:45] <hazzy-m> I like it
[18:11:49] <robotustra> M<x>,<y>
[18:12:06] <robotustra> is translated to moveTo(x,y)
[18:12:11] <robotustra> ets
[18:13:06] <hazzy-m> Ok, so I see L (line) M (move) R (radius), is there a fill?
[18:13:19] <robotustra> yes
[18:13:35] <robotustra> button can have many states
[18:14:02] <hazzy-m> fantastic!
[18:14:05] <robotustra> state can have may pathes and each path is attached to pen color and bg color
[18:14:29] <robotustra> and state also have a command line
[18:14:33] <robotustra> and a status
[18:14:49] <hazzy-m> that sounds very flexible and powerful
[18:14:52] <robotustra> by pressing the button in some state this command is envoked
[18:15:00] <robotustra> yes
[18:15:30] <robotustra> format of command line is to define
[18:15:39] <robotustra> it's like mini program too
[18:18:18] <robotustra> R -rectangle, P - rounded rectangle, A - arc, circle
[18:18:32] <robotustra> but you'd got an idea
[18:19:15] <hazzy-m> yes, it seems very well thought out
[18:19:23] <hazzy-m> so I don't have to learn c++ after all, just therobotustraUI spec mini language 😃
[18:21:14] <robotustra> forth-like languages are simple
[18:22:27] <robotustra> and I'll put a lot of comments in this file to explain how to describe abd add new elements
[18:22:33] <robotustra> or customize it
[18:31:06] <robotustra> about "don't have to learn c++" is very deep observation
[18:32:53] <robotustra> imho the any configuration language for people far from programming should be evident and self descriptif ar clear from short comments
[18:36:50] <hazzy-m> I agree, and I think what you have there is elegant and reasonably approachable even for a novice
[18:38:18] <robotustra> imagine an expression of the face of a guy who need to customize gui in xml?
[18:40:03] <hazzy-m> yes, Lcvette knows all about trying to edit XML by hand :D
[18:41:29] <robotustra> I did my config not in simple english language just because I didn't write good parser for it yet :)
[18:42:00] <robotustra> and plain english is not so good for gui description
[18:50:13] <Lcvette> which one is xml?
[18:50:26] <Lcvette> im a master at it
[18:50:39] <Lcvette> providing you no longer need it to work afterwards
[18:50:54] <Lcvette> lol
[18:56:15] <robotustra> "who said XML?" (c)
[19:20:37] -!- jthornton has joined #hazzy
[19:45:07] <hazzy-m> LOL
[19:45:31] <hazzy-m> Lcvette: XML is what the .ui files are
[20:24:15] <Not-1af4> [02QtPyVCP] 07Kurt Jacobson pushed 031 commit to 03VCPLauncher [+2/-0/±2] 13https://gitlab.com/Hazzy/qtpyvcp/compare/69f024bb7b8a13d9fb543dafd1776968efb80366...6dc6895023c2742e879a43ee047787d9031c3ce2
[20:24:16] <Not-1af4> [02QtPyVCP] 07Kurt Jacobson 036dc6895 - use docopt for parsing command line options
[21:55:11] <robotustra> jthornton, hi, I saw you was doing mill g-code generator?