[quote=“mcvflorin, post:20, topic:169767”]The plugin from apps.mios has only been updated to work with UI5.
[…]
The code.mios.com page was updated with the configuration instructions for UI5. This is the page that the Help button links to.[/quote]
So that talk on that page about “Panel connected to Vera via Ethernet or wireless” is discussing a version that doesn’t exist? Because I haven’t put any IP-address stuff into that plugin, and you say you haven’t either.
Some feedback on using apps.mios.com’s SVN interface.
There’s no way for me to see diffs between versions of a file. Since I am only dumping files here that’s not a huge loss for me.
It’s a pain to upload the ten files of the CurrentCost plugin, one by one. It takes a ton of mouse clicks. It’s also easy for me to lose track of which file I’m up to: the “Upload File” dialog doesn’t remind me which file I’m expected to be uploading, and the checkboxes in the left column don’t check themselves when I have uploaded a file. The warning that I have uncommitted files only appears after I’ve left the page and come back to it.
Scrollbars-within-scrollbars are awkward.
- I can mark a plugin as Vera3 only, but I can’t mark it as Vera2+Vera3 only. Oh, I get it. I can submit multiple releases, one for each platform.
- I don’t know how to format the string for Compatible Firmware in the Add Release section, or to give multiple ranges (“1.1.1225 to 1.1.1460, or 1.5.239-1.5.255”). Oh, I get it. I can submit multiple releases, one for each range.
I can’t set the plugin’s licence. It always shows empty on most pages and “GPL” on the Edit page.
On the “Installed plugins” page there is the ungrammatical “Please select an unit to be able to see plugins installed on it.” “A unit” is traditional.
The “compressed” checkboxes on the Versions page don’t remember their state, and seem to always remain on. There is no way for me to see in the UI whether a previously-submitted release is compressing a file or not, so I can’t be certain that I created the release with the right compression on each file. Edit: It’s worse than that, see Bug 2042.
Once a release is submitted for approval, I can’t unpublish it (say, when I discover a mistake.)
Come to think of it, why is Vera1 even in the platform list? It can’t run UI5 and so can’t access the marketplace.
These quibbles aside, I (think I) managed to update a couple of my plugins.
Thanks for the feedback. Most of the issue you reported already have an entry in Mantis. Currently the apps.mios issues have low priority compared to UI5 issues so it’s likely there won’t be a fix for them very soon.
I’ve set the above file in plugin 1128 to be uncompressed (because I am maintaining this plugin for UI4 too). However, it won’t load on users’ Veras, mine or others.
Clearly, FileUtils::ReadURL() isn’t expecting to see an uncompressed file and so continues to look for a .lua.lzo file.
This is a showstopper for almost all of my plugins. How can it be fixed? Reported as Bug 2042.
The option to have uncompressed files will be removed. In firmware version 1.5.161 the require() Lua function has been overloaded to handle compressed Lua files. Also, setting the package.path variable is no longer necessary for Lua files in /etc/cmh-lu and /etc/cmh-ludl.
Excellent. What about other auxiliary non-Lua files my plugin might have: config files, init scripts, images. Some of these are not going to want to be compressed. Is the ability to specify these kinds of files as uncompressed going away on apps.mios.com?
I need to know that too, Thanks for clearing that…
I tried using some png files as additional icons. When creating a version on apps.mios.com I gave them the path “/www/cmh/skins/default/icons” and I unchecked the “compress”. When I then try to install the plugin the vera doesn’t seem to be able to download the images:
I replied to your other post… 1.5.265 is released to the beta team first. Once the fixes are confirmed, it will be released to the public. Becoming a beta tester requires to be voted in by the beta team.
What about other auxiliary non-Lua files my plugin might have: config files, init scripts, images. Some of these are not going to want to be compressed. Is the ability to specify these kinds of files as uncompressed going away on apps.mios.com?
I will talk to Aaron about this when he returns from CES.[/quote]
I was wondering if this got resolved? It currently seems if you don’t tick the “Compress” tickbox, then the plugin install fails. Ticking it of course just makes the plugin itself fail as an uncompressed file is expected.
Also, when releasing a new version, the “Destination Path” is always cleared - when there are a number of files that don’t go into the default directory, it takes some time to type the path back in each time.