Rep Price - Historique des versions

Camille Binard le 19 juin 2014 à 08:31

2014-06-19T08:31:01Z

← Version précédente		Version du 19 juin 2014 à 10:31
Ligne 1 :		Ligne 1 :
	{{Projet		{{Projet
	~~<!--Header-->~~
	\|name = Rep_Price		\|name = Rep_Price
	\|status = experimental		\|status = experimental
	~~<!--Image-->~~
	\|image =		\|image =
	~~<!--General-->~~
	\|description = fabrication de disque pour platine jouet de type Fisher Price avec boîte à musique.		\|description = fabrication de disque pour platine jouet de type Fisher Price avec boîte à musique.
	\|license = GPL v3.0		\|license = GPL v3.0
	\|contributeurs = ~~[[contributeur::~~Thomas]]		\|contributeurs = Thomas
	\|~~matériaux~~ = ~~[[materiau::~~PLA]],~~[[materiau::~~code]],~~[[materiau::~~Processing]], ~~[[materiau::~~openSCAD]]		\|ingrédients = PLA, code, Processing, openSCAD
	~~\|cadModel =~~
	\|url =		\|url =
	}}		}}

ThomasB : /* Une version avec Processing ? */

2013-01-10T16:31:40Z

Une version avec Processing ?

← Version précédente		Version du 10 janvier 2013 à 18:31
Ligne 203 :		Ligne 203 :
	nav.trans.set(width/2, height/2, 0);		nav.trans.set(width/2, height/2, 0);

	model = Primitive.~~sphere~~(50,18);		model = Primitive.cylinder(121, 5, 100, true);
	}		}

ThomasB le 10 janvier 2013 à 15:57

2013-01-10T15:57:32Z

← Version précédente		Version du 10 janvier 2013 à 17:57
Ligne 187 :		Ligne 187 :

	Je repasse donc avec succès sur Processing 1.5.1		Je repasse donc avec succès sur Processing 1.5.1

			Premier essai d'un export d'une forme simple en .STL

			<code>
			import unlekker.util.*;
			import unlekker.modelbuilder.*;

			MouseNav3D nav;
			UGeometry model;

			void setup () {
			size(600, 600, P3D);

			nav = new MouseNav3D(this);
			nav.trans.set(width/2, height/2, 0);

			model = Primitive.sphere(50,18);
			}

			void draw() {
			background(100);

			lights();

			// call MouseNav3D transforms
			nav.doTransforms();
			fill(255);

			model.draw(this);
			}

			public void mouseDragged() {
			nav.mouseDragged();
			}


			public void keyPressed() {
			nav.keyPressed();

			if(key=='s') {
			model.writeSTL(this, "sphere.stl");
			}
			}
			</code>

ThomasB : /* Une version avec Processing ? */

2013-01-10T14:40:48Z

Une version avec Processing ?

← Version précédente		Version du 10 janvier 2013 à 16:40
Ligne 180 :		Ligne 180 :
	Le problème viendrait de la classe MouseNav3D.java qui utilise une classe Java plus usité dans la dernière version de Processing		Le problème viendrait de la classe MouseNav3D.java qui utilise une classe Java plus usité dans la dernière version de Processing

	<tt> Event Handling has changed significantly in 2.0b7. Due to necessary changes in the OpenGL renderer, and to provide better compatibility with Android and JavaScript modes, we've added actual MouseEvent and KeyEvent classes to Processing. In previous releases, the MouseEvent and KeyEvent classes referred to the automatically imported "java.awt.MouseEvent" and "java.awt.KeyEvent". This is no longer the case, so your code will behave a little differently. The OpenGL renderer no longer uses AWT (and therefore doesn't use java.awt events), so it's a necessary change there. On Android, there's no such thing as java.awt. More details on this as I have time to write them up. ~~</tt>~~		<tt> Event Handling has changed significantly in 2.0b7. Due to necessary changes in the OpenGL renderer, and to provide better compatibility with Android and JavaScript modes, we've added actual MouseEvent and KeyEvent classes to Processing. In previous releases, the MouseEvent and KeyEvent classes referred to the automatically imported "java.awt.MouseEvent" and "java.awt.KeyEvent". This is no longer the case, so your code will behave a little differently. The OpenGL renderer no longer uses AWT (and therefore doesn't use java.awt events), so it's a necessary change there. On Android, there's no such thing as java.awt. More details on this as I have time to write them up.

	This also has implications for libraries, and the library developer pages have more information.		This also has implications for libraries, and the library developer pages have more information.

			</tt>

			Je repasse donc avec succès sur Processing 1.5.1

ThomasB : /* Une version avec Processing ? */

2013-01-10T14:30:37Z

Une version avec Processing ?

← Version précédente		Version du 10 janvier 2013 à 16:30
Ligne 180 :		Ligne 180 :
	Le problème viendrait de la classe MouseNav3D.java qui utilise une classe Java plus usité dans la dernière version de Processing		Le problème viendrait de la classe MouseNav3D.java qui utilise une classe Java plus usité dans la dernière version de Processing

	<~~ins~~> Event Handling has changed significantly in 2.0b7. Due to necessary changes in the OpenGL renderer, and to provide better compatibility with Android and JavaScript modes, we've added actual MouseEvent and KeyEvent classes to Processing. In previous releases, the MouseEvent and KeyEvent classes referred to the automatically imported "java.awt.MouseEvent" and "java.awt.KeyEvent". This is no longer the case, so your code will behave a little differently. The OpenGL renderer no longer uses AWT (and therefore doesn't use java.awt events), so it's a necessary change there. On Android, there's no such thing as java.awt. More details on this as I have time to write them up. </~~ins~~>		<tt> Event Handling has changed significantly in 2.0b7. Due to necessary changes in the OpenGL renderer, and to provide better compatibility with Android and JavaScript modes, we've added actual MouseEvent and KeyEvent classes to Processing. In previous releases, the MouseEvent and KeyEvent classes referred to the automatically imported "java.awt.MouseEvent" and "java.awt.KeyEvent". This is no longer the case, so your code will behave a little differently. The OpenGL renderer no longer uses AWT (and therefore doesn't use java.awt events), so it's a necessary change there. On Android, there's no such thing as java.awt. More details on this as I have time to write them up. </tt>

	This also has implications for libraries, and the library developer pages have more information.		This also has implications for libraries, and the library developer pages have more information.

ThomasB : /* Une version avec Processing ? */

2013-01-10T14:29:57Z

Une version avec Processing ?

← Version précédente		Version du 10 janvier 2013 à 16:29
Ligne 180 :		Ligne 180 :
	Le problème viendrait de la classe MouseNav3D.java qui utilise une classe Java plus usité dans la dernière version de Processing		Le problème viendrait de la classe MouseNav3D.java qui utilise une classe Java plus usité dans la dernière version de Processing

	<s> Event Handling has changed significantly in 2.0b7. Due to necessary changes in the OpenGL renderer, and to provide better compatibility with Android and JavaScript modes, we've added actual MouseEvent and KeyEvent classes to Processing. In previous releases, the MouseEvent and KeyEvent classes referred to the automatically imported "java.awt.MouseEvent" and "java.awt.KeyEvent". This is no longer the case, so your code will behave a little differently. The OpenGL renderer no longer uses AWT (and therefore doesn't use java.awt events), so it's a necessary change there. On Android, there's no such thing as java.awt. More details on this as I have time to write them up. </s>		<ins> Event Handling has changed significantly in 2.0b7. Due to necessary changes in the OpenGL renderer, and to provide better compatibility with Android and JavaScript modes, we've added actual MouseEvent and KeyEvent classes to Processing. In previous releases, the MouseEvent and KeyEvent classes referred to the automatically imported "java.awt.MouseEvent" and "java.awt.KeyEvent". This is no longer the case, so your code will behave a little differently. The OpenGL renderer no longer uses AWT (and therefore doesn't use java.awt events), so it's a necessary change there. On Android, there's no such thing as java.awt. More details on this as I have time to write them up. </ins>

	This also has implications for libraries, and the library developer pages have more information.		This also has implications for libraries, and the library developer pages have more information.

ThomasB : /* Une version avec Processing ? */

2013-01-10T14:29:34Z

Une version avec Processing ?

← Version précédente		Version du 10 janvier 2013 à 16:29
Ligne 180 :		Ligne 180 :
	Le problème viendrait de la classe MouseNav3D.java qui utilise une classe Java plus usité dans la dernière version de Processing		Le problème viendrait de la classe MouseNav3D.java qui utilise une classe Java plus usité dans la dernière version de Processing

	Event Handling has changed significantly in 2.0b7. Due to necessary changes in the OpenGL renderer, and to provide better compatibility with Android and JavaScript modes, we've added actual MouseEvent and KeyEvent classes to Processing. In previous releases, the MouseEvent and KeyEvent classes referred to the automatically imported "java.awt.MouseEvent" and "java.awt.KeyEvent". This is no longer the case, so your code will behave a little differently. The OpenGL renderer no longer uses AWT (and therefore doesn't use java.awt events), so it's a necessary change there. On Android, there's no such thing as java.awt. More details on this as I have time to write them up.		<s> Event Handling has changed significantly in 2.0b7. Due to necessary changes in the OpenGL renderer, and to provide better compatibility with Android and JavaScript modes, we've added actual MouseEvent and KeyEvent classes to Processing. In previous releases, the MouseEvent and KeyEvent classes referred to the automatically imported "java.awt.MouseEvent" and "java.awt.KeyEvent". This is no longer the case, so your code will behave a little differently. The OpenGL renderer no longer uses AWT (and therefore doesn't use java.awt events), so it's a necessary change there. On Android, there's no such thing as java.awt. More details on this as I have time to write them up. </s>

	This also has implications for libraries, and the library developer pages have more information.		This also has implications for libraries, and the library developer pages have more information.

ThomasB : /* Expérimentations */

2013-01-10T14:13:13Z

Expérimentations

← Version précédente		Version du 10 janvier 2013 à 16:13
Ligne 46 :		Ligne 46 :
	J'ai tout d'abord tenté de réaliser un disque en utilisant la [[ReprapPrusa]] de PiNG ainsi qu'[[OpenScad]] pour créer la forme initiale.		J'ai tout d'abord tenté de réaliser un disque en utilisant la [[ReprapPrusa]] de PiNG ainsi qu'[[OpenScad]] pour créer la forme initiale.

	Voici ici le code utilisé pour ~~imprimé~~ mon premier modèle de disque:		Voici ici le code utilisé pour imprimer mon premier modèle de disque:

	<code>		<code>

ThomasB : /* Expérimentations */

2013-01-10T14:12:58Z

Expérimentations

← Version précédente		Version du 10 janvier 2013 à 16:12
Ligne 44 :		Ligne 44 :
	== Expérimentations ==		== Expérimentations ==

	J'ai tout d'abord tenté de ~~réalisé~~ un disque en utilisant la [[ReprapPrusa]] de PiNG ainsi qu'[[OpenScad]] pour créer la forme initiale.		J'ai tout d'abord tenté de réaliser un disque en utilisant la [[ReprapPrusa]] de PiNG ainsi qu'[[OpenScad]] pour créer la forme initiale.

	Voici ici le code utilisé pour imprimé mon premier modèle de disque:		Voici ici le code utilisé pour imprimé mon premier modèle de disque:

ThomasB : /* Une version avec Processing ? */

2013-01-10T14:11:34Z

Une version avec Processing ?

← Version précédente		Version du 10 janvier 2013 à 16:11
Ligne 178 :		Ligne 178 :
	<code>NoSuchMethodError: You may be using a library that's incompatible to this version of Processing</code>		<code>NoSuchMethodError: You may be using a library that's incompatible to this version of Processing</code>

	Le problème viendrait de la classe MouseNav3D.java qui utilise		Le problème viendrait de la classe MouseNav3D.java qui utilise une classe Java plus usité dans la dernière version de Processing

			Event Handling has changed significantly in 2.0b7. Due to necessary changes in the OpenGL renderer, and to provide better compatibility with Android and JavaScript modes, we've added actual MouseEvent and KeyEvent classes to Processing. In previous releases, the MouseEvent and KeyEvent classes referred to the automatically imported "java.awt.MouseEvent" and "java.awt.KeyEvent". This is no longer the case, so your code will behave a little differently. The OpenGL renderer no longer uses AWT (and therefore doesn't use java.awt events), so it's a necessary change there. On Android, there's no such thing as java.awt. More details on this as I have time to write them up.

			This also has implications for libraries, and the library developer pages have more information.

Rep Price - Historique des versions

Camille Binard le 19 juin 2014 à 08:31

ThomasB : /* Une version avec Processing ? */

ThomasB le 10 janvier 2013 à 15:57

ThomasB : /* Une version avec Processing ? */

ThomasB : /* Une version avec Processing ? */

ThomasB : /* Une version avec Processing ? */

ThomasB : /* Une version avec Processing ? */

ThomasB : /* Expérimentations */

ThomasB : /* Expérimentations */

ThomasB : /* Une version avec Processing ? */

ThomasB : /* Une version avec Processing ? */

ThomasB : /* Une version avec Processing ? */

ThomasB : /* Une version avec Processing ? */

ThomasB : /* Une version avec Processing ? */

ThomasB : /* Une version avec Processing ? */

ThomasB : /* Expérimentations */

ThomasB : /* Expérimentations */

ThomasB : /* Une version avec Processing ? */