Block categorization
Closed this issue · 8 comments
List the blocks in the GUI as described below.
Network I/O:
- fromEmail
- fromFile
- fromHTTPGetRequest
- fromHTTPStream
- toEmail
- toFile
- toHTTPGetRequest
- webrequest
Data Stores:
- redis
- mongo
- elasticsearch
Queues:
- nsq
- amqp
- sqs
- beanstalk
Parsers:
- xml
- csv
Stats:
- count
- histogram
- timeseries
- zipf
- poisson
- fft
- gaussian
- kullbackLeibler
- learn
- linearModel
- logisticModel
- movingAverage
- categorical
Core:
- map
- mask
- javascript
- filter
- cache
- set
- join
- bang
- ticker
- queue
- priority queue
- toggle
- tolog
- unpack
- pack*
Embedded Systems:
- analogpin
- digitalpin
maybe Hardware I/O instead of embedded systems? I worry that embedded systems means a lot more than just reading and writing to pins.
sure. Hardware I/O then.
should toFile/fromFile go to stores?
good idea, moved them to data stores. will push changes in a moment.
Uninformed opinion to follow:
As a user wouldn't I expect queue and priority queue under Queues?
On Jun 3, 2014, at 11:49, Jacqui Maher notifications@github.com wrote:
List the blocks in the GUI as described below.
Network I/O:
fromEmail
fromFile
fromHTTPGetRequest
fromHTTPStream
toEmail
toFile
toHTTPGetRequest
webrequest
Data Stores:redis
mongo
elasticsearch
Queues:nsq
amqp
sqs
beanstalk
Parsers:xml
csv
Stats:count
histogram
timeseries
zipf
poisson
fft
gaussian
kullbackLeibler
learn
linearModel
logisticModel
movingAverage
categorical
Core:map
mask
javascript
filter
cache
set
join
bang
ticker
queue
priority queue
toggle
tolog
unpack
pack*
Embedded Systems:analogpin
digitalpin
—
Reply to this email directly or view it on GitHub.
Yeah, I thought the same thing. Mike, can you address this, since it was
your argument/discussion that led to these 2 being listed under "Core" -
thanks.
On Thu, Jun 5, 2014 at 10:19 AM, mboggie notifications@github.com wrote:
Uninformed opinion to follow:
As a user wouldn't I expect queue and priority queue under Queues?
On Jun 3, 2014, at 11:49, Jacqui Maher notifications@github.com
wrote:List the blocks in the GUI as described below.
Network I/O:
fromEmail
fromFile
fromHTTPGetRequest
fromHTTPStream
toEmail
toFile
toHTTPGetRequest
webrequest
Data Stores:redis
mongo
elasticsearch
Queues:nsq
amqp
sqs
beanstalk
Parsers:xml
csv
Stats:count
histogram
timeseries
zipf
poisson
fft
gaussian
kullbackLeibler
learn
linearModel
logisticModel
movingAverage
categorical
Core:map
mask
javascript
filter
cache
set
join
bang
ticker
queue
priority queue
toggle
tolog
unpack
pack*
Embedded Systems:analogpin
digitalpin
—
Reply to this email directly or view it on GitHub.—
Reply to this email directly or view it on GitHub
#502 (comment).
Jacqui Maher
Research Engineer
The New York Times R&D Labs
@jacqui / jacqui.maher@nytimes.com
+17182905392 cell, +12125561471 desk
Just saw this discussion when the closing popped up in my email. 1) there is no priority queue block. 2) queue belongs in core because it's a basic mechanism that actually implements a queue, rather than interacting with an external queueing service like rabbit / nsq. I'll make a pull request with a proposed change and link through to it from here.