noflo / noflo-ccv Goto Github PK

6.0 6.0 5.0 594 KB

ccv face detection for noflo

License: MIT License

CoffeeScript 84.04% HTML 2.29% Python 6.23% Shell 0.55% C 6.90%

face-detection libccv noflo

noflo-ccv's Introduction

NoFlo: Flow-based programming for JavaScript

NoFlo is an implementation of flow-based programming for JavaScript running on both Node.js and the browser. From WikiPedia:

In computer science, flow-based programming (FBP) is a programming paradigm that defines applications as networks of "black box" processes, which exchange data across predefined connections by message passing, where the connections are specified externally to the processes. These black box processes can be reconnected endlessly to form different applications without having to be changed internally. FBP is thus naturally component-oriented.

Developers used to the Unix philosophy should be immediately familiar with FBP:

This is the Unix philosophy: Write programs that do one thing and do it well. Write programs to work together. Write programs to handle text streams, because that is a universal interface.

It also fits well in Alan Kay's original idea of object-oriented programming:

I thought of objects being like biological cells and/or individual computers on a network, only able to communicate with messages (so messaging came at the very beginning -- it took a while to see how to do messaging in a programming language efficiently enough to be useful).

NoFlo components can be written in any language that transpiles down to JavaScript, including ES6. The system is heavily inspired by J. Paul Morrison's book Flow-Based Programming.

Suitability

NoFlo is not a web framework or a UI toolkit. It is a way to coordinate and reorganize data flow in any JavaScript application. As such, it can be used for whatever purpose JavaScript can be used for. We know of NoFlo being used for anything from building web servers and build tools, to coordinating events inside GUI applications, driving robots, or building Internet-connected art installations.

Tools and ecosystem

NoFlo itself is just a library for implementing flow-based programs in JavaScript. There is an ecosystem of tools around NoFlo and the fbp protocol that make it more powerful. Here are some of them:

Flowhub -- browser-based visual programming IDE for NoFlo and other flow-based systems
noflo-nodejs -- command-line interface for running NoFlo programs on Node.js
noflo-browser-app -- template for building NoFlo programs for the web
noflo-assembly -- industrial approach for designing NoFlo programs
fbp-spec -- data-driven tests for NoFlo and other FBP environments
flowtrace -- tool for retroactive debugging of NoFlo programs. Supports visual replay with Flowhub

Requirements and installing

NoFlo is available for Node.js via NPM, so you can install it with:

$ npm install noflo --save

You can make a browser build of NoFlo using webpack. For webpack builds, you need configure the component loader statically with noflo-component-loader. For projects using Grunt, grunt-noflo-browser plugin makes this easy.

Installing from Git

NoFlo requires a reasonably recent version of Node.js, and some npm packages. Ensure that you have NoFlo checked out from Git, and all NPM dependencies installed. Build NoFlo with:

$ npm run build

Then you can install everything needed by a simple:

$ npm link

NoFlo is available from GitHub under the MIT license.

Changes

Please refer to the Release Notes and the CHANGES.md document.

Usage

Please refer to http://noflojs.org/documentation/. For visual programming with NoFlo, see https://docs.flowhub.io/.

Development

NoFlo development happens on GitHub. Just fork the main repository, make modifications and send a pull request.

We have an extensive suite of tests available for NoFlo. Run them with:

$ npm run build
$ npm test

Platform-specific tests

By default, the tests are run for both Node.js and the browser. You can also run only the tests for a particular target platform:

$ npm run test:node

or:

$ npm run test:browser

Discussion

There is a #noflo channel on the Flow-Based Programming Slack, and questions can be posted with the noflo tag on Stack Overflow. See http://noflojs.org/support/ for other ways to get in touch.

noflo-ccv's People

Contributors

Stargazers

Watchers

Forkers

sschepis asherbond mcanthony rmoorman cephdon

noflo-ccv's Issues

Bundle libccv instead of requiring it to be installed on system

libccv is not commonly present in distributions, and is designed to be embedded. It does not even have a make install target...

Right now everyone using noflo-ccv, directly or indirectly have to build it from scratch themselves. Would be better to just build it into the noflo-ccv code through node-gyp / static-linking.

An in-range update of grunt-noflo-browser is breaking the build 🚨

The devDependency grunt-noflo-browser was updated from `1.6.0` to `1.7.0`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

grunt-noflo-browser is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 21 commits.

764baf6 Release 1.7.0
58728df Merge pull request #41 from noflo/greenkeeper/babel-loader-8.0.0
faa7a70 Update appveyor Node version
ff1e2bc Update babel env
f59a123 Merge pull request #48 from noflo/greenkeeper/webpack-4.28.3
e493bb9 Merge pull request #45 from noflo/greenkeeper/grunt-contrib-jshint-2.0.0
119cc90 chore(package): update webpack to version 4.28.3
0b69cd2 chore(package): update grunt-contrib-jshint to version 2.0.0
51b73b2 Merge pull request #43 from noflo/greenkeeper/grunt-contrib-clean-2.0.0
99db276 Merge branch 'master' into greenkeeper/grunt-contrib-clean-2.0.0
13d5ad2 Merge pull request #42 from noflo/greenkeeper/grunt-contrib-connect-2.0.0
e2983f4 chore(package): update grunt-contrib-clean to version 2.0.0
10e1db6 chore(package): update grunt-contrib-connect to version 2.0.0
feaa2c5 fix(package): update babel-loader to version 8.0.0
fb7b9ab Merge pull request #38 from noflo/greenkeeper/update-to-node-10

There are 21 commits in total.

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of grunt-contrib-coffee is breaking the build 🚨

The devDependency grunt-contrib-coffee was updated from `2.0.0` to `2.1.0`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

grunt-contrib-coffee is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 8 commits.

14be62b Merge pull request #203 from gruntjs/v210
66dda8c v2.1.0
6879d8f Merge pull request #202 from gruntjs/upt-deps-a
93768c5 Fix tests for latest coffeescript
7d5b1c5 Update deps within delclared range
14315b4 Merge pull request #201 from gruntjs/upt-deps
d211122 Drop Node 6 in CI, add node 10
0681fc7 Update dependencies

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Version 10 of node.js has been released

Version 10 of Node.js (code name Dubnium) has been released! 🎊

To see what happens to your code in Node.js 10, Greenkeeper has created a branch with the following changes:

Added the new Node.js version to your .travis.yml
The new Node.js version is in-range for the engines in 1 of your package.json files, so that was left alone

If you’re interested in upgrading this repo to Node.js 10, you can open a PR with these changes. Please note that this issue is just intended as a friendly reminder and the PR as a possible starting point for getting your code running on Node.js 10.

More information on this issue

Greenkeeper has checked the engines key in any package.json file, the .nvmrc file, and the .travis.yml file, if present.

engines was only updated if it defined a single version, not a range.
.nvmrc was updated to Node.js 10
.travis.yml was only changed if there was a root-level node_js that didn’t already include Node.js 10, such as node or lts/*. In this case, the new version was appended to the list. We didn’t touch job or matrix configurations because these tend to be quite specific and complex, and it’s difficult to infer what the intentions were.

For many simpler .travis.yml configurations, this PR should suffice as-is, but depending on what you’re doing it may require additional work or may not be applicable at all. We’re also aware that you may have good reasons to not update to Node.js 10, which is why this was sent as an issue and not a pull request. Feel free to delete it without comment, I’m a humble robot and won’t feel rejected 🤖

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of grunt-contrib-uglify is breaking the build 🚨

Version 2.3.0 of grunt-contrib-uglify just got published.

Branch	Build failing 🚨
Dependency	grunt-contrib-uglify
Current Version	2.2.1
Type	devDependency

This version is covered by your current version range and after updating it in your project the build failed.

As grunt-contrib-uglify is “only” a devDependency of this project it might not break production or downstream projects, but “only” your build or test tools – preventing new deploys or publishes.

I recommend you give this issue a high priority. I’m sure you can resolve this 💪

Status Details

❌ continuous-integration/travis-ci/push The Travis CI build could not complete due to an error Details

Commits

The new version differs by 2 commits .

f3086c1 v2.3.0.
7dc5e1d Log fixes. (#454) r=vladikoff

See the full diff.

Not sure how things should work exactly?

There is a collection of frequently asked questions and of course you may always ask my humans.

Your Greenkeeper Bot 🌴

round values?

x y width and height could be rounded:

                {
                    "x": 367.5215516831421,
                    "y": 271.5025992013226,
                    "width": 54.27794792754907,
                    "height": 54.27794792754907,
                    "neighbors": 14,
                    "confidence": 8.305308969999993
                },

An in-range update of grunt-contrib-connect is breaking the build 🚨

The devDependency grunt-contrib-connect was updated from `2.0.0` to `2.1.0`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

grunt-contrib-connect is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ continuous-integration/travis-ci/push: The Travis CI build could not complete due to an error (Details).

Commits

The new version differs by 5 commits.

b6e703d v2.1.0
399dd5f Merge pull request #256 from TheGreatRefrigerator/master
f93c287 Fix the gitignore change
71fcea9 Upgrade morgan to v1.9.1
d5390ff Allow all configuration options of livereload to be passed through. (#246)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

An in-range update of grunt is breaking the build 🚨

The devDependency grunt was updated from `1.0.3` to `1.0.4`.

🚨 View failing branch.

This version is covered by your current version range and after updating it in your project the build failed.

grunt is a devDependency of this project. It might not break your production code or affect downstream projects, but probably breaks your build or test tools, which may prevent deploying or publishing.

Status Details

❌ continuous-integration/travis-ci/push: The Travis CI build failed (Details).

Commits

The new version differs by 5 commits.

8fcbed1 v1.0.4 (#1668)
0b13970 Update js-yaml to address https://npmjs.com/advisories/788 (#1667)
7db6cf7 Use SOURCE_DATE_EPOCH to render dates in template. (#1596)
a2d6d80 Revert "Indicate in package.json that Node.js 4 or newer is required (#1643)" (#1644)
773b7e7 Indicate in package.json that Node.js 4 or newer is required (#1643)

See the full diff

FAQ and help

There is a collection of frequently asked questions. If those don’t help, you can always ask the humans behind Greenkeeper.

Your Greenkeeper Bot 🌴

Use libccv

For nodejs target, we can use libccv (C library) instead of ccvjs (old implementation).

See use-libccv branch.

noflo / noflo-ccv Goto Github PK

noflo-ccv's Introduction

NoFlo: Flow-based programming for JavaScript

Suitability

Tools and ecosystem

Requirements and installing

Installing from Git

Changes

Usage

Development

Platform-specific tests

Discussion

noflo-ccv's People

Contributors

Stargazers

Watchers

Forkers

noflo-ccv's Issues

The devDependency grunt-noflo-browser was updated from 1.6.0 to 1.7.0.

The devDependency grunt-contrib-coffee was updated from 2.0.0 to 2.1.0.

Version 10 of Node.js (code name Dubnium) has been released! 🎊

Version 2.3.0 of grunt-contrib-uglify just got published.

The devDependency grunt-contrib-connect was updated from 2.0.0 to 2.1.0.

The devDependency grunt was updated from 1.0.3 to 1.0.4.

Recommend Projects

Recommend Topics

Recommend Org

The devDependency grunt-noflo-browser was updated from `1.6.0` to `1.7.0`.

The devDependency grunt-contrib-coffee was updated from `2.0.0` to `2.1.0`.

The devDependency grunt-contrib-connect was updated from `2.0.0` to `2.1.0`.

The devDependency grunt was updated from `1.0.3` to `1.0.4`.