I downloaded NI session strings 2. It was not showing in Kontakt 5. I upgraded to Kontakt 6, still not showing. Instead, when I click on the library and try to add the software folder Session Strings 2 Library to Kontakt it tells me 'Session Strings 2' already exists within the Kontakt Libraries tab'. But it does not show.
In accordance with the way swingproposes to handle text, JTerm is implemented by defining asubclass Session of Document. A singleJTerm window could handle multiple sessions (just callsetDocument). The main application is interaction withJava interpreters: to provide a shell window where you can interactwith Java objects. The "interpreter" can however be anything thatimplements a very simple interface calledStringEvaluator. This contains only one methodevaluate that given a string returns a result stringtogether with a boolean telling whether the result string is a regularresult or in fact an error message (has influence on the color of theresult string).Getting startedTo see what JTerm does, try java de.jtem.jterm.Test
This is a terminal for a dummy interpreter that "evaluates" commandstrings by converting them to lower case. For a really useful exampleput bsh-*.jar from the lib directory ( or download from the BeanShell web page www.beanshell.org) into your class path. Then you can try java de.jtem.jterm.BshTerm
The edu-sharing activity module adds a new option to the activities/resource menu. Using the edu-sharing resource allows you to either pick content from the repository or upload it to a folder of the repository. You may pick which version of the content you would like to provide in the course (always the latest vs. the version you just picked).
Hi Steffen. Thanks for sharing the set of edusharing plugins with the community. Please note, all the "Recommended" warnings reported above should really be considered as required as we insist on them before approving the plugin (they will be marked as required in the next version of the plugins directory UI). Please pay attention to them and fill them. Thanks for understanding.
I know you have been waiting in the approval queue for a long time now. But I am sure it will help the integration if the implementation follows the Moodle coding style more. I am going to mark this as needing more work. Once there are new versions uploaded here, please schedule the plugins for re-approval again.
There are certain areas in the code which I think could be reconsidered from both Moodle and edu-sharing API perspective - such as sending the raw value of session_id() as a session ticket to the remote server. Also the way how your Moodle plugins deal with session storage (e.g. directly setting properties like $_SESSION["USER"]->ticket) are warmly discouraged in common Moodle plugins. I can understand it may not be always possible to follow these guidelines as the other side of the integration (edu-sharing server and its API) may be limiting factor as well.
Please note string definitions like $string['modulename'] = $string['pluginname'] = '...'; are not supported by the AMOS parser at lang.moodle.org (we do not eval() these files) so we could not register strings of your plugin there.
b37509886e