xml3d / xml3d.tools.js Goto Github PK

View Code? Open in Web Editor NEW

2.0 3.0 1.0 18.5 MB

A Toolkit Library for XML3D

License: Other

JavaScript 99.75% CSS 0.25%

xml3d.tools.js's Introduction

xml3d.tools.js

A Toolkit Library for XML3D. For an overview take a look at the examples page

Build Instructions

Eclipse

Download the standard version of Eclipse.
In Eclipse go to File -> Import.
Select Existing Projects into Workspace and click Next.
Set the root directory to the xml3d.tools.js library
In the Projects field the library should appear.
Click on Finish.
In the file explorer on the left side expand the build directory.
Right-Click on build.xml and then Run as -> Ant Build.
Enjoy the newly built xml3d.tools.js in build/output.

By default Eclipse doesn't support Javascript in the editor. You can change that by:

Go to Help -> Install new Software
On the top in the field Work with: select the update site according to your release.
Wait for a long time until you see items listed in the big field (on the very bottom-right of Eclipse you see the status of retrieving all the available software).
In the field below the Work with type javascript.
Two options should be presented in the big field. They are the same, select one of the checkboxes to mark it for install.
Now search for web developer and mark the Eclipse Web Developer Tools for install.
Click Next and follow the install process.

Command Line

Make sure Ant is installed and accessible on the command-line
open a command-line and go to the build directory
type ant develop to concatenate all scripts or ant develop-min for a minified build

xml3d.tools.js's People

Contributors

Stargazers

Watchers

Forkers

ebersold

xml3d.tools.js's Issues

Class: better interface

XML3D.tools.Class needs two parameters, baseClass and body. But most of the time the base class is not used at all and only the body is passed into the function.

A better interface would be to create a class with:

myClass = XML3D.tools.Class({body});

and extend this class in this way:

myExtendedClass = myClass.extend({extendedBody});

This is similar to the class creation in http://backbonejs.org/.

Gizmo with multiple targets

Make it possible to have the gizmos modify a list of targets, and not just a single one.

Does not work with xml3d 4.8 release

The tools library heavily depends on DOMMutationEvents and will not work with the MutationObserver stuff 4.8 introduced. Especially the examine behaviour is pretty borked (even after trying to change listeners to use MutationObserver).

Camera controllers: turbo mode

Often one wants to travel to a certain location quite fast and then explore that location in detail. For that matter a camera controller should have something like a turbo button with which the user travels e.g. twice as fast.

RotateGizmo: axes sometimes inverted

Sometimes the axes of the gizmos are inverted in the sense that a mouse moving right causes the object to rotate to the left side. I could not yet reproduce this bug unfortunately.

Camera fly controllers: move along the up vector

It would be nice to have controls for moving along the up vectors, or say up and down.

Transformable for view elements

When using camera controllers we have to wrap view elements in group elements to be able to create a Transformable out of it. It would be nice to have Transformables for view elements so this does not have to be done.

ExamineBehavior: panning

Add the option to pan the camera along a plane. Means the camera is moved on a plane, but the point of examination stays fixed. That means the examination point might not be in the middle of the window anymore, but offset by an amount.

general: be able to receive jquery selectors as arguments

On many classes DOM elements are expected. It would be nice if jquery selectors could be passed in as well. This is a rather popular use case because many people use jQuery.

var xml3d = $("#myXml3dElement")[0];
var $defs = $(XML3D.tools.util.getOrCreateDefs(xml3d));

would become

var $xml3d = $("#myXml3dElement");
var $defs = XML3D.tools.util.getOrCreateDefs(xml3d);

RotateGizmo: adaptive sensivity

The rotation gizmo is way too sensitive at big scales (e.g. object with scale of 200). The gizmo should automatically adapt to the scale of the target node, to have the same sensitivity no matter the scale.