The Altair Community is migrating to a new platform to provide a better experience for you. In preparation for the migration, the Altair Community is on read-only mode from October 28 - November 6, 2024. Technical support via cases will continue to work as is. For any urgent requests from Students/Faculty members, please submit the form linked here

What is the correct syntax to name a group?

kaymankayman Member Posts: 662 Unicorn
edited November 2018 in Help

Hi there,

 

having some fun creating my own extensions, works out fine but I can't get my folder (group) names shown correctly when following the examples in the documentation. The operator is showing up nicely, correct name and icon etc, but the folders / groups keep having the key value instead of the wanted name.

 

These are my 2 files :

 

<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<operators name="myOperators" version="6.0" docbundle="com/rapidminer/extension/resources/i18n/OperatorsDocmyTest">
<group key="myGroupKey">
<operator>
<key>myOperatorKey</key>
<class>com.rapidminer.extension.operator.myOperatorClass</class>
<icon>main.png</icon>
</operator>
</group>
</operators>

and this is the Doc XML

 

<?xml version="1.0" encoding="windows-1252" standalone="no"?>
<operatorHelp lang="en_EN">
<!-- This one works, my operator shows the name. -->
<operator>
<key>myOperatorKey</key>
<synopsis>short synopsis</synopsis>
<help>Some more help</help>
<name>Operator name for testing purposes</name>
</operator>
<!-- But this one only shows the key -->
<group>
<key>myGroupKey</key>
<name>Group name for testing purposes</name>
</group>
</operatorHelp>

So, am I overlooking something syntax wise? Do I need to use attributes instead of elements (or vica versa) when looking at groups, or are there other restrictions related to naming a key?

 

Apart from the folder name (I simplified the whole flow a bit in the provided examples) all works fine so i a bit puzzled on where thigns go wrong.

 

thanks!

Tagged:

Answers

  • mmichelmmichel Employee-RapidMiner, Member Posts: 129 RM Engineering

    Hi kayman,

     

    this seems to be a bug. As workaround you could use the fully qualified group key:

    	<group>
    <key>extensions.myTest.myGroupKey</key>
    <name>Group name for testing purposes</name>
    </group>  

     

    Cheers,

    Marcel 

Sign In or Register to comment.