Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Support a Canvas Finger Overlay Directive #4

Open
robinboehm opened this issue Oct 29, 2013 · 10 comments
Open

Support a Canvas Finger Overlay Directive #4

robinboehm opened this issue Oct 29, 2013 · 10 comments
Assignees
Milestone

Comments

@robinboehm
Copy link
Contributor

Support a directive like:

http://js.leapmotion.com/examples/canvas-fingers.html

@ghost ghost assigned robinboehm Oct 29, 2013
@0x-r4bbit
Copy link
Contributor

@robinboehm I don't think that this is something which should land in angular-leap itself. Since its an example. Its just something you could possibly do with angular-leap. So, it wouldn't make really sense to implement canvas-fingers as reusable component in form of a directive, since its not reusable enough. Its an example. Thats it.

@robinboehm
Copy link
Contributor Author

I would like to create a possibility to interact with applications like Bretto did in his example but in a more generic way. So I would need this kind of directive for this...
So for me, the aim of this project should be really easy usage of leapmotion inside of an angular project.
Not a basic framework to creating such things...that is done by the native leapjs people.

Or what do you think?

http://dewmap.com/experiment/leap-angular-01/index.html

@0x-r4bbit
Copy link
Contributor

@robinboehm okay, turned out that I misunderstood this issue. If you're talking about a layer which is actually invisible and should act as a generic leap motion interface for websites, then this is totally the way to go! However, before we able to implement this, we should start wrapping the native API correctly and abstract it away. I'm pretty sure, a proper $leap or $gesture service could be really helpful in this kinda directive.

Of course, you could also just start and hack it down, but I thought it'd be better to use proper components then, which we have to build anyway.

@robinboehm
Copy link
Contributor Author

Feel free to improve the services :)
I don't want to hang up in premature optimization,
so I just created a minimalistic service that only offers what I really needed.

I'm on the train for some hours now, try to hack a first draft! :)

@0x-r4bbit
Copy link
Contributor

@robinboehm Yea sure! It's just that the native API has much more to provide we should put correctly into reusable components, so we can build on top of them. Looking forward to your bits!

@0x-r4bbit
Copy link
Contributor

@robinboehm wow this looks SO NEAT! But I think we should introduce an angular-leap-ui module for such things. WDYT?

@robinboehm
Copy link
Contributor Author

@PascalPrecht Good Idea.
We could provide basic/core/generic functionality in a core and offer UI-Components in another module.

+1

@0x-r4bbit
Copy link
Contributor

@robinboehm glad you're agreeing! I think the finger overlay directive would also be part of that ui module.

@robinboehm
Copy link
Contributor Author

Example for Interaction with overlay cursor: https://github.com/aphex/leap-cursor-library.js/blob/master/src/js/leap-manager.js#L375

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants