Name of tool, name.xrnx for autoupdate?

Renoise Tool Development
1

I have a question about the name of the XRNX file to upload it in the tools section of www.renoise.com.

How do they detect the update tool that there is a new version of the tool that a user has uploaded to the server?

The name of the tool influences?For example, is it possible to put names like this?:

  1. First file: ulneiz.NameTool_v1.0.xrnx
  2. First update: ulneiz.NameTool_v1.1.xrnx
  3. Second update: ulneiz.NameTool_v1.2.xrnx
  4. etc…

In other words, using these names will Renoise detect that an update exists?

The file manifest.xml is this:

<?xml version="1.0" encoding="UTF-8"?>
<RenoiseScriptingTool doc_version="0">
  <ApiVersion>5</ApiVersion>
  <AutoUpgraded>true</AutoUpgraded>
  <Name>NameTool</Name>
  <Id>ulneiz.NameTool_v1.0</Id>
  <Version>1.00</Version>
  <Author>ulneiz</Author>
  <Category>Pattern Editor, Phrase Editor</Category>
  <Description>The Description...</Description>
</RenoiseScriptingTool>

Is this line in charge of detecting a new update?: 1.00

Or is it necessary that the “Id” is always the same in all updates? ulneiz.NameTool_v1.0

How should I proceed exactly?

It’s the first time I’m going to upload a tool to the www.renoise.com server, and I want future autoupdates to work properly …

Thanks!

2

The basic idea is that your manifest and the tool page need to match.
Then, it does not matter so much what the file is called - only the manifest version is of importance

This works, since the tools .zip is extracted when submitting (to scan for potentially malicious code)

You definitely DON’T want this value to be true, btw.

<AutoUpgraded>true</AutoUpgraded>seScriptingTool>

It will prevent auto-updating, as the server will regard auto-upgraded tools as not being a “real” update.

3

The basic idea is that your manifest and the tool page need to match.
Then, it does not matter so much what the file is called - only the manifest version is of importance

This works, since the tools .zip is extracted when submitting (to scan for potentially malicious code)

You definitely DON’T want this value to be true, btw.

<AutoUpgraded>true</AutoUpgraded>seScriptingTool>

It will prevent auto-updating, as the server will regard auto-upgraded tools as not being a “real” update.

:o Ok, thanks!

Then I must keep the “Id” of the manifest, and change the “Version” of the manifest in each update. But it is possible to change the name of the name.xrnx file.Finally, AutoUpgraded must be “false”.

One last question. I have seen in some manifestos that says “Icon” or “Ico” (folder_address???). What is it for? Does an icon appear somewhere?Should the icon be a .ico within the root folder of the tool?

4

Yep, you got everything right :slight_smile:

I have seen in some manifestos that says “Icon” or “Ico” (folder_address???). What is it for?

I don’t know - maybe some leftover implementation detail that never actually got used for anything… huh.png

5

Ok, then I forget about the “icon” theme.I think I have everything ready.

Maybe this weekend I’ll post something interesting …

Thanks for everything!

6

This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.