Re:Show HN: Riko – A Python stream processing engine modeled...
by tudorw on Thursday July 21, 2016 @09:38AM
(#12136734)
if someone can spin up a usable gui, charge enough to make a living without compromising on performance, promise some longevity and a way to export of my stuff I would probably pay for that, I loved pipes, the GUI was a big deal for me.
[ Parent
| on HN ]
Re:Show HN: Riko – A Python stream processing engine modeled...
by reubano on Thursday July 21, 2016 @10:27AM
(#12137052)
Have you investigated any of the existing GUIs? [1-3] I'd love to hear your thoughts on their pros/cons. I do plan to integrate a nice GUI framework if I can find one.
[1] https://azkaban.github.io/ [2] https://developers.google.com/blockly/ [3] http://nodered.org/
Re:Show HN: Riko – A Python stream processing engine modeled...
by beardicus on Thursday July 21, 2016 @10:43AM
(#12137172)
Node-RED is pretty great. I think a wiring interface is a better choice than a block-level thing like blockly.
Re:Show HN: Riko – A Python stream processing engine modeled...
by reubano on Thursday July 21, 2016 @10:49AM
(#12137209)
True, Node-RED is much more aligned to the original Yahoo! Pipes interface. I kinda like the scratch/blockly interface since you can make it clear which components can go where. Plus it's reminiscent of physical Lego blocks.
Which interface do you think is more newbie friendly? My gut says blocks (maybe something a bit more simple/refined than blocky) are easier to grok, while wires allow for designing more complex workflows.
Re:Show HN: Riko – A Python stream processing engine modeled...
by beardicus on Thursday July 21, 2016 @01:23PM
(#12138440)
I don't feel like blocks really maps well to the kinds of tasks i'd do in node-red and yahoo pipes, and presumably riko (I didn't dive too deep here yet though). a wiring interface better reflects the idea of inputs, filters, and outputs, and wiring them up in flexible ways. blocks seems a little rigid and more variable/iteration/function-based.
maybe figure out a few common workflows that people would make in riko or node-red, and mock up how they'd work/look in blocks vs. wiring/pipes.
Re:Show HN: Riko – A Python stream processing engine modeled...
by reubano on Sunday July 24, 2016 @01:34PM
(#12153975)
> maybe figure out a few common workflows that people would make in riko or node-red, and mock up how they'd work/look in blocks vs. wiring/pipes.
Good idea, what are your workflows?
Re:Show HN: Riko – A Python stream processing engine modeled...
by tudorw on Friday July 22, 2016 @03:20AM
(#12142207)
I think the wiring is a good way to show the connections, white space is needed to keep things readable so it allows for gaps and logical groupings, wires, strings, I think the analogy is fairly digestible to someone new to this. Thanks for everyone's input, I'll be taking a look.
Re:Show HN: Riko – A Python stream processing engine modeled...
by qw on Thursday July 21, 2016 @03:46PM
(#12139507)
Apache Nifi looks promising.
https://nifi.apache.org
Re:Show HN: Riko – A Python stream processing engine modeled...
by drdoom on Thursday July 21, 2016 @12:13PM
(#12137808)
Just curious:
What kind of a demand is there for a pipes-kind of product or even a customizable/searchable rss/feed integrator?
How much would a typical user be willing to pay for it?