*.flo source code

64 views
Skip to first unread message

veselov.m...@yandex.ru

unread,
Aug 30, 2019, 12:06:46 PM8/30/19
to Automate
Can you describe how *.flo works? I thought flow files are like xml or json, but it is not. So i want to create flow editor for PC

bezar...@gmail.com

unread,
Aug 30, 2019, 12:13:36 PM8/30/19
to Automate
Maybe open the file as text

veselov.m...@yandex.ru

unread,
Aug 30, 2019, 1:05:29 PM8/30/19
to Automate
ehm...?

Frantisek Skuta

unread,
Aug 30, 2019, 1:09:20 PM8/30/19
to Automate
this was already requested, even the PC editor. However, author stated that .flo is not in any format like that. It's part of "executable". Not sure how he described it but it's not easy to make PC editor and you'd have to have a lengthy discussion with author to create such tool :-)

Dňa piatok, 30. augusta 2019 18:06:46 UTC+2 veselov.m...@yandex.ru napísal(-a):

veselov.m...@yandex.ru

unread,
Aug 30, 2019, 1:42:44 PM8/30/19
to Automate
please can non-developers stop answering me, you don't even know how flow format works. i don't need useless answers.

Henrik "The Developer" Lindqvist

unread,
Aug 30, 2019, 1:55:10 PM8/30/19
to Automate
It's the correct answer. There's is no "source code", the flows are store in a binary format of the AST.

veselov.m...@yandex.ru

unread,
Aug 30, 2019, 3:38:50 PM8/30/19
to Automate
thanks anyway, but do you know how can i get block IDs (or names in binary, idk what is it)? I know, that «C0 11» in HEX is toast show block, but i want to get other names without long searching

Henrik "The Developer" Lindqvist

unread,
Sep 1, 2019, 3:26:20 PM9/1/19
to Automate
It's the first 1-5 bytes, varint encoded, of every block, but would have to read the entire AST to access it for every block, and data of every block is layout out differently, depending on the fields is includes.
As said, it would be near impossible without me releasing the specification. Features to export and import "source code" is already on the to-do list.
Reply all
Reply to author
Forward
0 new messages