I downloaded open exhibits thinking of downloading a file with a useful interface for users with little experience of programming language and easy application … I do not understand anything. Can anyone direct me as if I were a child? Because of the download can not find any kind of exe? but only docs, exemples, lib, templates, tutorials … what do I do with these if I do not know how that would work? please help me!
OpenExhibits is a framework, which means there is no single .exe file to run. Instead, it's like a shelf of parts available for you to build things with. Like, say you wanted to build a framed picture in real life, you would know you need the image, glass to protect it, a backing to mount it on, and the wood for the frame. You still have to cut all these items to the right size, but you don't have to forge the glass yourself, or mill the lumber for the wood of the frame from a tree. They're already made, you just have to put them together.
The best place to start with is our Tutorials: http://wiki.gestureworks.com/index.php/GestureWorksFlash:GestureWorks_Flash_Tutorials (To remove any confusion: Gestureworks is OpenExhibits, OpenExhibits is just the non-profit, educational version of the Gestureworks software. When Gestureworks is discussed, we also mean OpenExhibits.)
What you specifically want to start out with is our "Setting up Your Development Environment" tutorials. It goes through three different options: Flash Pro, Flash Builder, or FlashDevelop. These tutorials show you how to set up a basic project to build off of. Think of your "project" file (.FLA for Flash Pro, .project for Flash Builder, .as3proj for FlashDevelop) as your garage that you'll be building everything in. You see just a big, empty workspace, it looks rather plain and uninteresting, but it's where you start with everything.
Each of those tutorials goes over how to set up your project, and then link it to the OpenExhibits framework on your computer. The linkage is the most important part. This is like taking your garage (the base project), and setting up your shelves of parts (the framework) inside your garage so you have access to all those parts right away. Keep in mind, the framework does not literally have to be inside the project, the linkage steps set it up so you have access to all parts of the framework.
What your project will come out with when you eventually compile it is a .swf file. Those are what you're looking for when working with Actionscript.
Once you get familiar with setting up your project in your development environment, you'll probably want to look at the "Examples" folder in your download. You'll have to move through the different folders to see what's going on. A common one that most people want to know is how to show an image. So you can go to Examples/cml/Components/ImageViewer. Inside that folder, there's already a .as3proj file since we primarily work in FlashDevelop when developing OpenExhibits. But if you compare this folder to the project folder you built with the tutorial, you'll notice a similar structure. We have a "src" folder, that holds your Main.as class (think of this as your main construction tool for your whole project.) There's the "bin" folder, which is where the final product is output. And inside the "bin" folder, there's smaller, base folders that we need, such as "cml", which holds the CML for the viewer. Think of the CML as the blueprint. Only instead of drawing a picture frame, you write down the various things you want in CML declarations, and the project compiles them.
You can also open the Main.as file in every example "src" folder to see how we set up all of our basic AS3 projects. You really don't need to change a thing in almost all of them, and there's nothing that happens other than the program is told to run. The few exceptions are things like the "button", which has some extra code inside the Main. Otherwise, you need no programming to run anything. The only thing the Main handles is being pointed towards your CML (blueprint), to see what to build.
What happens when you run (compile) the project is the Main.as file opens up the Gestureworks application you've created. It works like a machine to read your CML (your blueprints) to assemble the parts (elements, components, frames, kits, etc.), into your final piece (a complete, multitouch viewer, or other project.)
You were really very exhaustive ... incredible I finally understood how it all works ... unfortunately the site is not well explained! I suggest you propose an extract from the text of this communication as Home of the Open Exhibits and consequently also for Gestureworks, all for dummies. Thank you so much! Stefano
Unfortunately practicing Flash Pro through tutorials Gestureworks (the link you sent me) and "Setting Up my Adobe Flash Environment" was not able to get the fateful "Hello World" I tried several times and it was really demeaning ... why you are getting me a little desperate. We are opening soon a antiquarium / museum in a village of town and I'm trying to set up in addition to archaeological finds, including multimedia platforms useful for the use of information and avant computerization. It will be useful to contact you in case I find more smoothly ... in the meantime, I offer you my thanks for your clarification on the subject.
Thank you very much.
Stefano, I'm also new to their framework and am using it with Flash pro. It does take a bit of finagling to make sure the library is fully installed properly, but it does work nicely once configured.
We're always trying to make sure to update the tutorials if something isn't consistently working (we also need to take out the requirement for a "key", that property is no longer used. What errors are you getting, if you're getting any errors? What do you see on screen if you're not getting any errors?