Voting - plugins not included in the installation file

[jitterjames]

but how will that affect people that already have it installed in the xbmcrepeat folder?

[jonib]

but how will that affect people that already have it installed in the xbmcrepeat folder?

If they don't remove the one in the XBMCRepeat dir, they would get two XBMC plugins in the add plugins list.
But it would work fine(I think).

jonib

[jonib]

I would just like to say Pako: I know that you are working hard on this without much help from anyone and I hope I speak for everyone when I say that your effort is greatly appreciated.

Damn I forgot, I wanted to thank everybody involved in transferring the forum, svn and site, nice work.

jonib

[abraxxa]

Shouldn't every plugin author decide how his plugin is named?

[jitterjames]

No. Your question implies that the issue we are discussing is much simpler than it actually is. We are not talking about what plugins should be called. We are talking about possibly renmaing plugins, and possibly replacing older plugins with newer versions, or possibly keeping old and new versions side by side. Furthermore we are talking about plugins that will be included in the standard install. We are trying to decide as a group what the best course of action is that will create the least amount of long term confusion for users, both old and new.

If someone comes along and creates a new plugin they can call it whatever they want, as long as it is not obviously offensive. But if you read the actual discussion taking place in this thread it is obvious that we are not talking about that.

I would say that the opinion of the plugin developer is important though, assuming that they actually voice it.

[jonib]

but how will that affect people that already have it installed in the xbmcrepeat folder?

Oops, looks like I was wrong when I copied my plugin to XBMC2 dir and removed the XBMCRepeat dir, EventGhost complained about missing plugin.

So looks like it's best to use the XBMCRepeat dir for my plugin. But I'm going to change the visual name to XBMC2.

jonib

[jitterjames]

If you can keep the folder name, but change the display name without causing problems that is great. Though you may want to add something in the description about it being formerly known as xbmcrepeat, in case people are looking for it by that name. You may also want to add something to your forum thread to alert people of the new name.

[jonib]

If you can keep the folder name, but change the display name without causing problems that is great. Though you may want to add something in the description about it being formerly known as xbmcrepeat, in case people are looking for it by that name. You may also want to add something to your forum thread to alert people of the new name.

That was the plan.

jonib

[abraxxa]

No. Your question implies that the issue we are discussing is much simpler than it actually is. We are not talking about what plugins should be called. We are talking about possibly renmaing plugins, and possibly replacing older plugins with newer versions, or possibly keeping old and new versions side by side. Furthermore we are talking about plugins that will be included in the standard install. We are trying to decide as a group what the best course of action is that will create the least amount of long term confusion for users, both old and new.

If someone comes along and creates a new plugin they can call it whatever they want, as long as it is not obviously offensive. But if you read the actual discussion taking place in this thread it is obvious that we are not talking about that.

I would say that the opinion of the plugin developer is important though, assuming that they actually voice it.

When you, as the bundle packager, aren't allowed to rename a plugin, the discussion whether it should be done becomes superfluous.

[Pako]

1. I'm not sure what the result.
You can clearly tell me how I should proceed with plugins Dynamic Webserver and XBMCrepeat?

2. I'm almost ready to do a commit command.
But there is another problem. I still can not classify these four plugins:
LG_Plasma
RFXcom_xPL
SunTracker
TCPEvents
These plugins cause, that you can not run EventGhost with the argument -translate.
I have to wait for a fix or this time we do a new build without these plugins?

Pako

[jitterjames]

I think for both the webserver and xbmc repeat, that the old versions should be removed.

In the case of xbmcrepeat, the plugin name should remain the same but the folder should be named xbmc2

In the case of Dynamic Webserver, the plugin and folder name should remain the same.

[krambriw]

EventGhost with the argument -translate

What is the purpose to do this? And what can cause problems?

Best regards, Walter

[jonib]

In the case of xbmcrepeat, the plugin name should remain the same but the folder should be named xbmc2

The other way around. the directory name needs to be XBMCRepeat or everyone using it will need to reassign all XBMC actions.

jonib

[jonib]

1. I'm not sure what the result.
You can clearly tell me how I should proceed with plugins Dynamic Webserver and XBMCrepeat?

Remove the old XBMC plugin, add my XBMCRepeat plugin (I have attached latest of the two files needed). Keep it in the XBMCRepeat directory.

jonib

[jitterjames]

In the case of xbmcrepeat, the plugin name should remain the same but the folder should be named xbmc2

The other way around. the directory name needs to be XBMCRepeat or everyone using it will need to reassign all XBMC actions.

jonib

ooops. sorry.

Please also keep the plugin name and directory the same for dynamic webserver. Get rid of the old webserver.