Java Interface Library v2/en - Versionsgeschichte

Cg am 18. März 2021 um 08:17 Uhr

2021-03-18T08:17:45Z

← Nächstältere Version		Version vom 18. März 2021, 08:17 Uhr
Zeile 820:		Zeile 820:
	----		----
	Back to [[Plugins]]		Back to [[Plugins]]

			[[Category: Plugins/en]]
			[[Category: Advanced/en]]

Cg: /* Activating the new Java Bridge */

2019-08-26T14:35:55Z

Activating the new Java Bridge

← Nächstältere Version		Version vom 26. August 2019, 14:35 Uhr
Zeile 38:		Zeile 38:
	If, for whichever reason you need to use the old bridge, you can switch back via the settings dialog (e.g. if you have an old JavaBridge installed on a target).		If, for whichever reason you need to use the old bridge, you can switch back via the settings dialog (e.g. if you have an old JavaBridge installed on a target).

	To deactivate the new bridge in expecco, navigate to ''Extras'' ► ''Settings'' ► ''Plugins'' ► ''Java Bridge'' and uncheck the ''Use new Bridge (experimental)'' checkbox:		To deactivate the new bridge in expecco, navigate to ''Extras'' → ''Settings'' → ''Plugins'' → ''Java Bridge'' and uncheck the ''Use new Bridge (experimental)'' checkbox:

	[[Datei:ActivateNewJavaBridge.png]]		[[Datei:ActivateNewJavaBridge.png]]

Cg: /* Calling Static Methods */

2019-05-18T11:47:00Z

Calling Static Methods

← Nächstältere Version		Version vom 18. Mai 2019, 11:47 Uhr
Zeile 219:		Zeile 219:
	Calling a static method on an object is not different from calling non static methods. In most cases you will call a static method not on an object but directly on the class. This is done by using the class object as "''receiver''" of the message. For example, if we want to call the static method "<CODE>isDefaultLookAndFeelDecorated()</CODE>" of the <code>JFrame</code> class, write:		Calling a static method on an object is not different from calling non static methods. In most cases you will call a static method not on an object but directly on the class. This is done by using the class object as "''receiver''" of the message. For example, if we want to call the static method "<CODE>isDefaultLookAndFeelDecorated()</CODE>" of the <code>JFrame</code> class, write:
	<CODE><PRE>		<CODE><PRE>
	(java ~~getJavaClass:~~'javax.swing.JFrame') isDefaultLookAndFeelDecorated.		(java @ 'javax.swing.JFrame') isDefaultLookAndFeelDecorated.
	</PRE></CODE>		</PRE></CODE>

Cg: /* Calling Static Methods */

2019-05-18T11:46:50Z

Calling Static Methods

← Nächstältere Version		Version vom 18. Mai 2019, 11:46 Uhr
Zeile 217:		Zeile 217:

	=== Calling Static Methods ===		=== Calling Static Methods ===
	Calling a static method on an object is not different from calling non static methods. In most cases you will call a static method not on an object but directly on the class. This is done by using the class object as "receiver" of the message. For example, if we want to call the static method <CODE>"isDefaultLookAndFeelDecorated()"</CODE> of the JFrame class, write:		Calling a static method on an object is not different from calling non static methods. In most cases you will call a static method not on an object but directly on the class. This is done by using the class object as "''receiver''" of the message. For example, if we want to call the static method "<CODE>isDefaultLookAndFeelDecorated()</CODE>" of the <code>JFrame</code> class, write:
	<CODE><PRE>		<CODE><PRE>
	(java getJavaClass:'javax.swing.JFrame') isDefaultLookAndFeelDecorated.		(java getJavaClass:'javax.swing.JFrame') isDefaultLookAndFeelDecorated.

Cg: /* Calling Instance Methods */

2019-05-18T11:46:11Z

Calling Instance Methods

← Nächstältere Version		Version vom 18. Mai 2019, 11:46 Uhr
Zeile 200:		Zeile 200:
	frame setSize:300 anyWord:200.		frame setSize:300 anyWord:200.
	</PRE></CODE>		</PRE></CODE>
	or any other selector with "setSize:" as its first component.		or any other selector with "<code>setSize:</code>" as its first component.
	The selector translation mechanism simply takes the first part as the Java selector.		The selector translation mechanism simply takes the first part as the Java selector.

	In practice, you should take a reasonably descriptive name, such as: "frame setSize:300 height:200" or only the Java name as first part, such as "frame setSize:300 _:200".		In practice, you should take a reasonably descriptive name, such as: "<code>frame setSize:300 height:200</code>" or only the Java name as first part, such as "<code>frame setSize:300 _:200</code>".

	For a call of a method with 4 arguments, we could write:		For a call of a method with 4 arguments, we could write:
Zeile 214:		Zeile 214:
	</PRE></CODE>		</PRE></CODE>

	Also here the <CODE>"y: width: height:"</CODE> can be named as you want, but the first part must be "setBounds:".		Also here the "<CODE>y: width: height:</CODE>" can be named as you want, but the first part must be "<code>setBounds:</code>".

	=== Calling Static Methods ===		=== Calling Static Methods ===

Cg: /* Calling Instance Methods */

2019-05-18T11:44:52Z

Calling Instance Methods

← Nächstältere Version		Version vom 18. Mai 2019, 11:44 Uhr
Zeile 189:		Zeile 189:
	In Java, the message name is a single identifier, and arguments are written in an argument list after the message name; eg: "<code>receiver.fooBar(arg1, arg2)</code>".		In Java, the message name is a single identifier, and arguments are written in an argument list after the message name; eg: "<code>receiver.fooBar(arg1, arg2)</code>".

	When message names are translated, only the very first part of the Smalltalk keyword message is taken ("foo" in the above example), and the remaining parts are simply ignored. ~~Thus, any of the Smalltalk messages "foo:bar:", "foo:xxxx:" and "foo:_:" (a single underscore as second part) all translate to the same Java message name "foo()".~~		When message names are translated, only the very first part of the Smalltalk keyword message is taken ("<code>foo</code>" in the above example), and the remaining parts are simply ignored.
			Thus, any of the Smalltalk messages "<code>foo:bar:</code>", "<code>foo:xxxx:</code>" and "<code>foo:_:</code>" (a single underscore as second part) all translate to the same Java message name "<code>foo()</code>".

	Therefore, to call a method with more than one argument, like <CODE>"setSize(int width,int height)"</CODE> on a JFrame instance we can write:		Therefore, to call a method with more than one argument, like <CODE>"setSize(int width,int height)"</CODE> on a JFrame instance we can write:

Cg: /* Calling Instance Methods */

2019-05-18T11:43:57Z

Calling Instance Methods

← Nächstältere Version		Version vom 18. Mai 2019, 11:43 Uhr
Zeile 185:		Zeile 185:
	</PRE></CODE>		</PRE></CODE>

	As method naming is different in Smalltalk and Java, a dynamic translation is applied when sending messages from Smalltalk code to a remote Java object. Smalltalk has arguments embedded inside parts of a so called "keyword" message, such as in "receiver foo:arg1 bar:arg2", where "foo:bar:" would be the message name, and "arg1", "arg2" be the arguments.		As method naming is different in Smalltalk and Java, a dynamic translation is applied when sending messages from Smalltalk code to a remote Java object. Smalltalk has arguments embedded inside parts of a so called "''keyword''" message, such as in "<code>receiver foo:arg1 bar:arg2</code>", where "<code>foo:bar:</code>" would be the message name, and "<code>arg1</code>", "<code>arg2</code>" be the arguments.

	In Java, the message name is a single identifier, and arguments are written in an argument list after the message name: "receiver.fooBar(arg1, arg2)".		In Java, the message name is a single identifier, and arguments are written in an argument list after the message name; eg: "<code>receiver.fooBar(arg1, arg2)</code>".

	When message names are translated, only the very first part of the Smalltalk keyword message is taken ("foo" in the above example), and the remaining parts are simply ignored. Thus, any of the Smalltalk messages "foo:bar:", "foo:xxxx:" and "foo:_:" (a single underscore as second part) all translate to the same Java message name "foo()".		When message names are translated, only the very first part of the Smalltalk keyword message is taken ("foo" in the above example), and the remaining parts are simply ignored. Thus, any of the Smalltalk messages "foo:bar:", "foo:xxxx:" and "foo:_:" (a single underscore as second part) all translate to the same Java message name "foo()".

Cg: /* Instantiating a Class */

2019-05-18T11:42:31Z

Instantiating a Class

← Nächstältere Version		Version vom 18. Mai 2019, 11:42 Uhr
Zeile 171:		Zeile 171:
	button := (java getJavaClass:'javax.swing.JButton') new.		button := (java getJavaClass:'javax.swing.JButton') new.
	</PRE></CODE>		</PRE></CODE>
			or
⚫	The first statement results in a proxy object for ~~the~~ "JFrame" instance. ~~The second line results in a proxy for a new "JButton" object.~~
			<CODE><PRE>
			frame := (java @ 'javax.swing.JFrame') new.
			button := (java @ 'javax.swing.JButton') new.
			</PRE></CODE>
		⚫	The first statement results in a proxy object for a new "JFrame" instance.
			The second line results in a proxy for a new "JButton" object.

	== Calling Instance Methods ==		== Calling Instance Methods ==

Cg: /* Java Class Access */

2019-05-18T11:41:47Z

Java Class Access

← Nächstältere Version		Version vom 18. Mai 2019, 11:41 Uhr
Zeile 136:		Zeile 136:
	jFrameClass := java getJavaClass:'javax.swing.JFrame'		jFrameClass := java getJavaClass:'javax.swing.JFrame'
	</PRE></CODE>		</PRE></CODE>
	there is also a shortcut:		there is also a shortcut message "@", which performs the same operation:
	<CODE><PRE>		<CODE><PRE>
	jFrameClass := java @ 'javax.swing.JFrame'		jFrameClass := java @ 'javax.swing.JFrame'

Cg: /* Java Class Access */

2019-05-18T11:41:18Z

Java Class Access

← Nächstältere Version		Version vom 18. Mai 2019, 11:41 Uhr
Zeile 134:		Zeile 134:
	This following code sample simply references (i.e. accesses) the class "<code>JFrame</code>" from the <CODE>"javax.swing"</CODE> package. The fully specified class name in Java would be <CODE>"javax.swing.JFrame"</CODE>:		This following code sample simply references (i.e. accesses) the class "<code>JFrame</code>" from the <CODE>"javax.swing"</CODE> package. The fully specified class name in Java would be <CODE>"javax.swing.JFrame"</CODE>:
	<CODE><PRE>		<CODE><PRE>
	java getJavaClass:'javax.swing.JFrame'		jFrameClass := java getJavaClass:'javax.swing.JFrame'
			</PRE></CODE>
			there is also a shortcut:
			<CODE><PRE>
			jFrameClass := java @ 'javax.swing.JFrame'
	</PRE></CODE>		</PRE></CODE>