66 replies to this topic

[pieterg]

We had pipzap support years before there was even such a thing as a 'pipzap plugin'.
I do not feel the need to remove our pip zap implementation.

[Rob van der Does]

This so-called 'AMS'- plugin, isn't really a plugin: it's just a heap of existing plugins in one folder.

[littlesat]

it's just a heap of existing plugins in one folder.

And this heap has multiple licences... The main is on creative commons... while some parts are GPL and other parts again are closed source.... wierd....

[Rob van der Does]

Anyway: a 'plugin' like this one is not worth any investigation.

[rtzhjgg0]

My personal observation about thema: PLi - standard plugins.

PLi is a great image, compatible with all kind of boxes but with a long and growing list of incompatible plugins and skins

There is a pull of standard addons that runs pefectlly on all existent images except PLi. In cases when users ask about incompatibility of this standard addons to PLi, there is a typical way how admins answer:

- I never heard about the existence of such addon
- where is the code?
- why you need such an addon!?
- this addon is simply shit
- tell the autor to fix it himself

...strategy? or just sweep the problem under the carpet!?

Edited by rtzhjgg0, 18 June 2012 - 13:08.

[ims]

PLi is a great image, compatible with all kind of boxes but with a long and growing list of incompatible plugins and skins

for most plugins incompatibility you must thanks to dmm and it's "an.l climbers" from ...craft

[littlesat]

What are the growing numbers of plugins that are not compatible anymore...? Please call the long growing lost....

Edited by littlesat, 18 June 2012 - 13:46.

[WanWizard]

The question is how much longer this is true.

Fact is that more and more images are based on OpenPLi, and less and less on the (old GPL) DMM code. So perhaps plugin builders should start with using the OpenPLi image as their basis for development.

Also, if those plugin builders would make their source public, people could contribute and issues like this would be fixed a lot quicker.

And finally, if the plugin license forbids the plugin on certain platforms supported by OpenPLi, it is not a generally usable plugin, so why would we bother?

[rtzhjgg0]

...In cases when users ask about incompatibility of this standard addons to PLi, there is a typical way how admins answer:

- I never heard about the existence of such addon
- where is the code?
- why you need such an addon!?
- this addon is simply shit
- tell the autor to fix it himself
...

And when I ask the autors of that addons about compatibility problems of their addon with PLi, the answer is identical to what users receive here:

- I never heard about the existence of such image
- why you need such an image!?
- this image is simply shit
- tell the PLi people to fix it himself

[hemispherical1]

Luckily OpenPLi is open source software, you're more than welcome to remove it's pipzap implementation & use the plugin if you prefer...


--
hemi

[littlesat]

You even do not have to remove our PipZap.... you just install the PipZap plugin en then AMS if you want to use it... As far I understood there are no issues then.... everyone happy!!! Nobody/nowone has to fix anything....

When pipzap works in OpenPli I can even be added it as third party.. and AMS too... when someone make/add a dependance then in AMS tot PIPzap then there is no issue at all....

Unless the weird licenses....

Edited by littlesat, 18 June 2012 - 14:44.

[rtzhjgg0]

You even do not have to remove our PipZap.... you just install the PipZap plugin en then AMS if you want to use it... As far I understood there are no issues then.... everyone happy!!! Nobody/nowone has to fix anything...

After 2 days of intensive tests of my workaround (AMS + PiPzap-Plugin) I found no issues with AMS.
But having two PiPzap's in one image is really "dirty" and illogical. It causes things like double entries in extensions menu (see my shot).

Attached Files

•  double_entries.jpg   56.15KB   46 downloads

[littlesat]

Then someone should fix AMS for us.....

[Rob van der Does]

Then someone should fix AMS for us.....

Or first answer your previous question: what does AMS bring that isn't in PLi?

[littlesat]

I suggest IMDB integrated into the movieplayer with the sleeves....?

[rtzhjgg0]

@SatKiekerd
Remember, the "question" of this thread is: "I noticed a problem of X-plugin with Pli, how to solve it ?"

For that reason questions like:

"what kind of plugin is this ?"
or
"do you like this plugin ?"
or
"what is the difference between this plugin and Y ?"

...are simply OT. I'm not selling AMS

Edited by rtzhjgg0, 19 June 2012 - 14:37.

[Rob van der Does]

In the meantime we're 55 answers further. And we are now in the stadium of Littlesat's question: can somebody 'repair' (or adapt to PLi) this plugin.
So before spending any time on that, it would be good to know what AMS adds to PLi. Knowing that makes it a lot easier to adapt/leave out not needed items (because, as we stated before, this 'plugin'is in reality a heap of plugins).

Long story short: my question (in fact a repeat of Littlesat's question) is perfectly on-topic.

[rtzhjgg0]

This plugin don't need to be modified. I don't believe his autor will adapt his (overall running) plugin to the old pipzap patch.

[Rob van der Does]

Now you lost me completely.
You wanted a problem solved. After some discussion, the question arose if somebody would/could modify the plugin. And now you don't want it anymore?

[rtzhjgg0]

@SatKiekerd
The problem is not the plugin but the old pipzap patch. AMS runs on all E2 / OE2 images.


I wrote before:
---------
Just remove the old pipzap code and let users to install (if they wish) the PiPzap-Plugin. This old pipzap code, will only cause in future troubles/conflicts with other addons (like in the case of AMS).
---------