This page (revision-24) was last changed on 17-Dec-2012 21:25 by CarstenWasner

This page was created on 17-Dec-2012 09:52 by Daniel Zügner

Only authorized users are allowed to rename pages.

Only authorized users are allowed to delete pages.

Page revision history

Version Date Modified Size Author Changes ... Change note
24 17-Dec-2012 21:25 3 KB CarstenWasner to previous
23 17-Dec-2012 21:24 3 KB CarstenWasner to previous | to last
22 17-Dec-2012 21:22 3 KB CarstenWasner to previous | to last
21 17-Dec-2012 11:33 3 KB Daniel Zügner to previous | to last

Page References

Incoming links Outgoing links
FAQ Daniel Zügner ...nobody
FAQ Daniel Zügner

Version management

Difference between version and

At line 16 changed one line
Unfortunately, there is no Hot Code Replacement for Non-Java files. However, there is a [How-To for developing Javascript at runtime|http://denkbares.dyndns.org/d3web/Wiki.jsp?page=How-To%20Develop%20JavaScript%20in%20KnowWE], which may be useful for you.
Unfortunately, there is no Hot Code Replacement for Non-Java files. However, there is a [How-To for developing Javascript at runtime|How-To Develop JavaScript in KnowWE], which may be useful for you.
At line 25 changed 2 lines
*Right click on KnowWE-App in Eclipse
*Select {{{Tomcat > Update Tomcat Context}}}
*Right click on KnowWE-App in Eclipse and select
{{{Tomcat > Update Tomcat Context}}}
At line 29 added 2 lines
!!!What is a Plugin?
A Plugin is a module extending KnowWE's functionality. A plugin needs a plugin.xml file defining the Extensions for this plugin.
At line 32 added 2 lines
!!!What is an Extension?
An Extension implements the plugin's functionality using an Extension Point. For further definition and usage instructions see [this page|How-To Extension Points]..
At line 35 added 3 lines
!!!What is an Extension Point?
An Extension Point has a specific type, for example ''Action, TagHandler, TypeHandler'' or ''EventListener''. The defined extension point specifies that each extension has to give values for class, name, description, version, and priority. This has to be defined by each extension point; an extension point further can require additional value, for example the specification of a file name.
For further definition and usage instructions see [this page|How-To Extension Points].
At line 39 added 2 lines
!!!What is the Scope of an extension?
A scope is an selector of a specific subset of KDOM nodes. Its selection is based on the type of the KDOM nodes itself as well as on the type of the KDOM node's anchestors. It can be compared a little bit to the css selectors.
At line 42 added one line
The scope is a path of those KDOM node types that should be matched/selected. The path can be relative (anywhere in the KDOM tree) or root based. Specific path wildcards as "*" and "**" are allowed. The different kinds of Scopes and their usage are explained [here|How-To Extension Points].
At line 44 added one line
At line 35 changed one line
* What is an plugin, what is an extension, what is an extension point (http://d3webwiki.informatik.uni-wuerzburg.de/Wiki.jsp?page=Plugins%20and%20Extensions)
* What is an plugin, what is an extension, what is an extension point ([check here|http://d3webwiki.informatik.uni-wuerzburg.de/Wiki.jsp?page=Plugins%20and%20Extensions])
This page (revision-24) was last changed on 17-Dec-2012 21:25 by CarstenWasner Top