Can't understand where to know what physijs functions do. There are many functions like applyImpulse, applyForce etc. but there is no documentation for them.
Physi.js is a wrapper for ammo.js which is a port of bullet. I dont know of any good guides/tutorials for physi.js or ammo.js that covers more than a basic scene. However when you want to learn about what the functions are doing, you can look it up in the bullet physics docs.
What helped me understand were some bullet tutorials here: http://bulletphysics.org/mediawiki-1.5.8/index.php/Tutorial_Articles
and the Forum where you can find further information in some user posts: http://www.bulletphysics.org/Bullet/phpBB3/index.php?sid=0e8c6e5111583be0d17f1731e4c1dc19
Related
I had another question about processing and a project i'm making. I would like to play a movie in a loop on the background. I managed to do this by initializing a Movie and putting it in an image the size of my app. But now I would like to load in multiple movies and add a button to change the background when pressed with the leap motion. Is this possible ? Or should I use a different library for this ?
Thanks in advance!
Kind regards,
DarthSwedo
It's really hard to answer general "how do I do this" type questions. Stack Overflow is designed more for specific "I tried X, expected Y, but got Z instead" type questions. You'll have much better luck if you just try something and post an MCVE if you get stuck.
That being said, I'm going to try to clear up some of the general confusion you seem to have.
Step 1: You need to figure out what library or libraries you're using. In all of your questions, you seem to not be sure which library you're using. Which Leap Motion library are you using? How did you set it up? Where is its documentation? You say you're using a Movie class. Where is that coming from? Are you sure it's not from the Video library?
If you have more specific questions in the future, please provide this information. We can't really help you without it. But more importantly, you need to know the answers to these questions if any of this is ever going to make any sense.
Step 2: Read the documentation for those libraries. Processing comes with the reference. The Video library comes with its own documentation page. I'm sure whatever Leap Motion library you're using has something similar. You need to read about the functions available to you. That's a huge part of programming. Right now your question is just asking whether something possible, and the honest answer to that is, well, what happened when you googled it?
Step 3: Try something. After you read through the documentation, just try something. Write some code based on the examples in the documentation. Even if that code doesn't work, that's okay, because then you can use it as an MCVE and ask a more specific question.
Good luck.
I need help with a library system in prolog.
I tried to define all the books in my library this way:
book(['programming in logic'],
[nm(k, clark), nm(f, mcCabe)],
['programation'],
['editorial 123']).
And I tried to do a query for all programming books this way:
?- book(Title,Autgor,Genre,Editorial),
findall( Genre, (member('programation', Genre)), [G]).
but I need to suggest books by genre, author...
I also need to do statistics, most wanted book, genre most searched, author most wanted, things like that, but I'm not sure how to define the rules to do these queries. I have searched for examples, but only find things like family tree and I don't understand. If you could collaborate with examples for this exercise, I would appreciate too much.
For sure, modelling a library system could be a very complex topic.
I would suggest to start to learn RDF, for instance with SWI-Prolog, that has a very powerful library devoted to the task.
I just tried to use RDF to model objects simpler than biblio domain.
Anyway, I googled 'biblio ontology' and got some reasonable result, like bibo.
To start with, maybe you could consider some introductory material.
Besides Ruby-Doc, what sources are best to take some examples and tutorials from, especially about Tk/Tile in Ruby? I found myself more normal with
http://www.tutorialspoint.com/ruby/ruby_tk_guide.htm
http://www.perfectxml.com/syngress/ruby/Page1.asp
but the information is pretty vague, and there is not so much to learn from. I had to consult multiple sources. I found two books from O'Reilly Media:
http://shop.oreilly.com/product/9781565924987.do
http://shop.oreilly.com/product/9781565924338.do
but don't know if it's the right thing to start with. Even Lynda.com doesn't have anything interesting to look into.
The best site I know of for learning Tk is TkDocs, which has a tutorial that covers multiple languages including Ruby. (To just see the Ruby version, set the language in the side-bar. Alternatively, leave it at the default of “All Languages” to find out how other languages bind the same library; the differences can be illuminating…)
(Mathematica version: 8.0.4)
lst = Names["Internal`*"];
Length[lst]
Pick[lst, StringMatchQ[lst, "*Bag*"]]
gives
293
{"Internal`Bag", "Internal`BagLength", "Internal`BagPart", "Internal`StuffBag"}
The Mathematica guidebook for programming By Michael Trott, page 494 says on the Internal context
"But similar to Experimental` context, no guarantee exists that the behavior and syntax of the functions will still be available in later versions of Mathematica"
Also, here is a mention of Bag functions:
Implementing a Quadtree in Mathematica
But since I've seen number of Mathematica experts here suggest Internal`Bag functions and use them themselves, I am assuming it would be sort of safe to use them in actual code? and if so, I have the following question:
Where can I find a more official description of these functions (the API, etc..) like one finds in documenation center? There is nothing now about them now
??Internal`Bag
Internal`Bag
Attributes[Internal`Bag]={Protected}
If I am to start using them, I find it hard to learn about new functions by just looking at some examples and trial and error to see what they do. I wonder if someone here might have a more complete and self contained document on the use of these, describe the API and such more than what is out there already or a link to such place.
The Internal context is exactly what its name says: Meant for internal use by Wolfram developers.
This means, among other things, the following things hold about anything you might find in there:
You most likely won't be able to find any official documentation on it, as it's not meant to be used by the public.
It's not necessarily as robust about invalid arguments. (Crashing the kernel can easily happen on some of them.)
The API may change without notice.
The function may disappear completely without notice.
Now, in practice some of them may be reasonably stable, but I would strongly advise you to steer away from them. Using undocumented APIs can easily leave you in for a lot of pain and a nasty surprise in the future.
I have been thinking about making my own diagram to better put my head around how all the classes and modules in Ruby inherit from each other. How it all ties together visually. I am sure there is a good one out there. I Googled it but was not satisfied with the results. Any suggestions?
I am also a visual learner and ended up drawing my own "homemade" diagram:
Hope this helps.
One of the best explanations and diagrammatic explanation of the ruby object model can be found in this book: Metaprogramming Ruby I tried googling the relevant pages but came up empty
For a good understanding on how the Ruby Object Model and Metaprogramming work, I would highly recommend these ScreenCasts by Pragmatic Programmer's Dave Thomas:
http://pragprog.com/screencasts/v-dtrubyom/the-ruby-object-model-and-metaprogramming
Dave Thomas is awesome at explaining the concepts, and the screencasts have nice graphics in them visualizing how things relate to each other.. those ScreenCasts are straight to the point, without distractions - and are worth every penny, err cent!
There is also a book "Metaprogramming Ruby" http://pragprog.com/book/ppmetr/metaprogramming-ruby
but although it covers a lot of concepts, the book is badly written, and through it's writing style makes it really hard to memorize the concepts / or use the book as a reference to look up things later..
A diagram showing superclass and eigenclass links between Ruby objects (but not the module inclusion links) is available at www.atalon.cz.
Since 11 January 2012 there is a diagram containing module inclusion links.