Memory topic map - Revision history

Akivela: /* Creating Memory Layer */

2010-08-03T16:58:29Z

‎Creating Memory Layer

Akivela: /* See also */

2009-10-30T10:25:30Z

‎See also

Olli: /* Creating Memory Layer */

2008-09-11T08:04:50Z

‎Creating Memory Layer

Akivela at 16:54, 28 August 2008

2008-08-28T16:54:07Z

Akivela: /* Creating Memory Layer */

2008-07-26T12:10:26Z

‎Creating Memory Layer

Akivela at 09:21, 30 June 2008

2008-06-30T09:21:37Z

Akivela: /* Creating Memory Layer */

2008-06-30T09:20:32Z

‎Creating Memory Layer

Akivela at 09:17, 30 June 2008

2008-06-30T09:17:17Z

Akivela: /* Creating Memory Layer */

2008-06-30T09:02:19Z

‎Creating Memory Layer

Akivela: /* Creating Memory Layer */

2008-06-30T09:01:48Z

‎Creating Memory Layer

← Older revision		Revision as of 16:58, 3 August 2010
Line 11:		Line 11:


−	You can also select to import Wandora's mini ontology '''resources/conf/wandora_mini.xtm''' to the created layer. This mini map contains a set of Wandora's fundamental topics and associations. Mini ontology is handy if you decide to delete Wandora's default '''Base''' layer later on. In order to work properly Wandora requires at least minimal ontology with language and Wandora class topics. After layer creation you should see new layer at the left bottom of application window (see image below). After layer creation you can select the layer and modify the topic map within. You could import ~~exsisting~~ XTM file into the layer for example.	+	You can also select to import Wandora's mini ontology '''resources/conf/wandora_mini.xtm''' to the created layer. This mini map contains a set of Wandora's fundamental topics and associations. Mini ontology is handy if you decide to delete Wandora's default '''Base''' layer later on. In order to work properly Wandora requires at least minimal ontology with language and Wandora class topics. After layer creation you should see new layer at the left bottom of application window (see image below). After layer creation you can select the layer and modify the topic map within. You could import existing XTM file into the layer for example.

@@ Line 22: / Line 22: @@
 * [[Linked topic map]]
 * [[Query topic map]]
-* [[Remote topic map]]
+<!-- * [[Remote topic map]] -->

← Older revision		Revision as of 08:04, 11 September 2008
Line 11:		Line 11:


−	You can also select to import Wandora's mini ontology '''conf/wandora_mini.xtm''' to the created layer. This mini map contains a set of Wandora's fundamental topics and associations. Mini ontology is handy if you decide to delete Wandora's default '''Base''' layer later on. In order to work properly Wandora requires at least minimal ontology with language and Wandora class topics. After layer creation you should see new layer at the left bottom of application window (see image below). After layer creation you can select the layer and modify the topic map within. You could import exsisting XTM file into the layer for example.	+	You can also select to import Wandora's mini ontology '''resources/conf/wandora_mini.xtm''' to the created layer. This mini map contains a set of Wandora's fundamental topics and associations. Mini ontology is handy if you decide to delete Wandora's default '''Base''' layer later on. In order to work properly Wandora requires at least minimal ontology with language and Wandora class topics. After layer creation you should see new layer at the left bottom of application window (see image below). After layer creation you can select the layer and modify the topic map within. You could import exsisting XTM file into the layer for example.

← Older revision		Revision as of 16:54, 28 August 2008
Line 1:		Line 1:
−	Memory topic map is a topic map construct kept in computer's memory during edit time. Memory topic map is probably the most common topic map construct Wandora user requires. Memory topic map requires no external initialization and is ready after creation.	+	Memory topic map is a topic map construct kept in computer's memory during edit time. Memory topic map is probably the most common topic map construct Wandora user requires. Memory topic map requires no external initialization and is ready for usage after creation.

	Memory topic map can hold thousands of topics and associations. Actual limitations depend on the amount of memory you give to the Java Runtime Environment. Wandora includes four different startup scripts with different memory footprint (discussed in [[Running Wandora]]). Default script gives JRE 750M enough to hold topic maps with ~50 000 topics and ~100 000 associations.		Memory topic map can hold thousands of topics and associations. Actual limitations depend on the amount of memory you give to the Java Runtime Environment. Wandora includes four different startup scripts with different memory footprint (discussed in [[Running Wandora]]). Default script gives JRE 750M enough to hold topic maps with ~50 000 topics and ~100 000 associations.

← Older revision		Revision as of 12:10, 26 July 2008
Line 15:		Line 15:

	[[Image:newLayerExample.gif\|center]]		[[Image:newLayerExample.gif\|center]]
		+
		+	== See also ==
		+
		+	* [[Layered topic map]]
		+	* [[Database topic map]]
		+	* [[Linked topic map]]
		+	* [[Query topic map]]
		+	* [[Remote topic map]]

← Older revision		Revision as of 09:21, 30 June 2008
Line 1:		Line 1:
−	Memory topic map is a topic map construct kept in computer's memory during edit time. Memory topic map is probably the most common topic map construct Wandora user requires. Memory topic map requires no external initialization ~~but~~ is ready after creation.	+	Memory topic map is a topic map construct kept in computer's memory during edit time. Memory topic map is probably the most common topic map construct Wandora user requires. Memory topic map requires no external initialization and is ready after creation.

	Memory topic map can hold thousands of topics and associations. Actual limitations depend on the amount of memory you give to the Java Runtime Environment. Wandora includes four different startup scripts with different memory footprint (discussed in [[Running Wandora]]). Default script gives JRE 750M enough to hold topic maps with ~50 000 topics and ~100 000 associations.		Memory topic map can hold thousands of topics and associations. Actual limitations depend on the amount of memory you give to the Java Runtime Environment. Wandora includes four different startup scripts with different memory footprint (discussed in [[Running Wandora]]). Default script gives JRE 750M enough to hold topic maps with ~50 000 topics and ~100 000 associations.

← Older revision		Revision as of 09:20, 30 June 2008
Line 11:		Line 11:


−	You can also select to import Wandora's mini ontology '''conf/wandora_mini.xtm''' to the created layer. This mini map contains a set of Wandora's fundamental topics and associations. Mini ontology is handy if you ~~have decided~~ to delete Wandora's default Base layer later on. In order to work properly Wandora requires minimal ontology. After layer creation you should see new layer at the left bottom of application window (see image below). After layer creation you can select the layer and modify the topic map within. You could import exsisting XTM file into the layer for example.	+	You can also select to import Wandora's mini ontology '''conf/wandora_mini.xtm''' to the created layer. This mini map contains a set of Wandora's fundamental topics and associations. Mini ontology is handy if you decide to delete Wandora's default '''Base''' layer later on. In order to work properly Wandora requires at least minimal ontology with language and Wandora class topics. After layer creation you should see new layer at the left bottom of application window (see image below). After layer creation you can select the layer and modify the topic map within. You could import exsisting XTM file into the layer for example.
		+

	[[Image:newLayerExample.gif\|center]]		[[Image:newLayerExample.gif\|center]]

@@ Line 1: / Line 1: @@
 Memory topic map is a topic map construct kept in computer's memory during edit time. Memory topic map is probably the most common topic map construct Wandora user requires. Memory topic map requires no external initialization but is ready after creation.
-Memory topic map can hold thousands of topics and associations. Actual limitations depend on the amount of memory you give to the Java Runtime Environment. Wandora includes four different startup scripts with different memory footprint. Default script gives JRE 750M enought to hold topic maps with ~50 000 topics and ~100 000 associations.
+Memory topic map can hold thousands of topics and associations. Actual limitations depend on the amount of memory you give to the Java Runtime Environment. Wandora includes four different startup scripts with different memory footprint (discussed in [[Running Wandora]]). Default script gives JRE 750M enough to hold topic maps with ~50 000 topics and ~100 000 associations.
 == Creating Memory Layer ==

← Older revision		Revision as of 09:02, 30 June 2008
Line 11:		Line 11:


−	You can also select to import Wandora's mini ontology '''conf/wandora_mini.xtm''' to the created layer. This mini map contains a set of Wandora's fundamental topics and associations. Mini ontology is handy if you have decided to delete Wandora's default Base layer later on. In order to work properly Wandora requires minimal ontology. After layer creation you should see new layer at the left bottom of application window. After layer creation you can select the layer and modify the topic map within. You could import exsisting XTM file into the layer for example.	+	You can also select to import Wandora's mini ontology '''conf/wandora_mini.xtm''' to the created layer. This mini map contains a set of Wandora's fundamental topics and associations. Mini ontology is handy if you have decided to delete Wandora's default Base layer later on. In order to work properly Wandora requires minimal ontology. After layer creation you should see new layer at the left bottom of application window (see image below). After layer creation you can select the layer and modify the topic map within. You could import exsisting XTM file into the layer for example.

	[[Image:newLayerExample.gif\|center]]		[[Image:newLayerExample.gif\|center]]

← Older revision		Revision as of 09:01, 30 June 2008
Line 11:		Line 11:


−	You can also select to import Wandora's mini ontology '''conf/wandora_mini.xtm''' to the created layer. This mini map contains a set of Wandora's fundamental topics and associations. Mini ontology is handy if you have decided to delete Wandora's default Base layer later on. In order to work properly Wandora requires minimal ontology. After layer creation you should see new layer at the left bottom of application window.	+	You can also select to import Wandora's mini ontology '''conf/wandora_mini.xtm''' to the created layer. This mini map contains a set of Wandora's fundamental topics and associations. Mini ontology is handy if you have decided to delete Wandora's default Base layer later on. In order to work properly Wandora requires minimal ontology. After layer creation you should see new layer at the left bottom of application window. After layer creation you can select the layer and modify the topic map within. You could import exsisting XTM file into the layer for example.

	[[Image:newLayerExample.gif\|center]]		[[Image:newLayerExample.gif\|center]]
−
−	~~Letter '''M''' marks for a memory topic map layer. Letter '''D''' marks for a database topic map layer.~~