Back to limesurvey.org

Welcome to the LimeSurvey Community Forum

Ask the community, share ideas, and connect with other LimeSurvey users!

Plugin shop

More
7 years 5 months ago #165521 by jelo
Plugin shop was created by jelo
This is a discussion thread (the wikipage feels not discussion-ready)
www.limesurvey.org/manual/Plugin_shop

The plugin shop is meant let users sell their own plugins, themes, question templates and demo surveys to other users on limesurvey.org.

The meaning of the word "stable" for users
www.limesurvey.org/forum/development/117...ord-stable-for-users
The topic has been locked.
More
7 years 5 months ago - 7 years 5 months ago #165523 by jelo
Replied by jelo on topic Plugin shop
For inspiration I suggest two stores of opensource tools:
apps.nextcloud.com/
wordpress.org/plugins/

For me the biggest issue is the compatibly info about plugins. The "and higher" info has to be put beside.
If the shop is open to plugins below LS 3.0 there has to be a easy way, to filter between the three branches.

Wordpress shows the important infos right away.


Nextcloud app store shows which plugins are official developed in the community and are constantly used and checked with all releases.
The meaning of the word "stable" for users
www.limesurvey.org/forum/development/117...ord-stable-for-users
Last edit: 7 years 5 months ago by jelo.
The topic has been locked.
More
7 years 5 months ago #165524 by jelo
Replied by jelo on topic Plugin shop
Always nice to see a link protection is place.

The metadata concept for Nextcloud apps might be another inspiration.
docs.nextcloud.com/server/12/developer_manual/app/info.html

Metadata Wordpress plugin:
developer.wordpress.org/plugins/the-basics/header-requirements/
The meaning of the word "stable" for users
www.limesurvey.org/forum/development/117...ord-stable-for-users
The topic has been locked.
More
7 years 5 months ago #165613 by ollehar
Replied by ollehar on topic Plugin shop
Hi jelo!

Great feedback! Also feel free to add it to the manual discussion page! (Each mediawiki page has a discussion page.)
The topic has been locked.
More
7 years 5 months ago #165614 by ollehar
Replied by ollehar on topic Plugin shop
www.limesurvey.org/manual/Talk:Plugin_shop
The topic has been locked.
More
7 years 5 months ago - 7 years 5 months ago #165706 by DenisChenu
Replied by DenisChenu on topic Plugin shop
I already put some information on wiki, but :

1. Allow to have different url for "plugin shop" , something like repository in fedora or debian

2. Allow to get any plugin (not in an official plugin shop) by url
or (see yunohost.org/#/apps )

After : plugin can be updatable like comfort update (with or without a key : plugin update url choice).


yunohost and spip have this system. The 2 are preconfigurated with "official and stable" plugin repo, but allow anything else.

[edit]
And 2 last current idea : information like 'copyright', 'update link', 'version compatible' come from a file in the plugin. Then even a plugin set up manually can be updatable.
Maybe we need different directory for "own plugin" and "url plugin" , didn't know.
Assistance on LimeSurvey forum and LimeSurvey core development are on my free time.
I'm not a LimeSurvey GmbH member. - Professional support - Plugins, theme and development .
I don't answer to private message.
Last edit: 7 years 5 months ago by DenisChenu. Reason: see edit
The topic has been locked.
More
7 years 5 months ago #165932 by DenisChenu
Replied by DenisChenu on topic Plugin shop
Another remark : need a Survey Theme + a Question Theme

If we can have same base code for each : it can be great. Then maybe use a config.xml for plugin too. Then have same basic part on all config.xml :)

This config.xml need something like : <type>(plugin|survey|question)</type>
Assistance on LimeSurvey forum and LimeSurvey core development are on my free time.
I'm not a LimeSurvey GmbH member. - Professional support - Plugins, theme and development .
I don't answer to private message.
The topic has been locked.
More
7 years 5 months ago #165938 by ollehar
Replied by ollehar on topic Plugin shop
Yes, we need same config.xml structure for all extensions, so the extension installer can be more simple.

You prefer XML over JSON, Denis?
The topic has been locked.
  • LouisGac
  • LouisGac's Avatar
  • New Member
  • New Member
More
7 years 5 months ago #165939 by LouisGac
Replied by LouisGac on topic Plugin shop
try to do that with json, you'll need external libs or a lot more code:
github.com/LimeSurvey/LimeSurvey/blob/ma...anifest.php#L83-L100

XML is a real query language, that open many possibilities.
B)
The topic has been locked.
More
7 years 5 months ago #165941 by DenisChenu
Replied by DenisChenu on topic Plugin shop

olle wrote: …

You prefer XML over JSON, Denis?

No, not exactlly (i don't care).

But : theme and question already use XML, then plugin can use XML.

I think all metada can follow the same rules :
github.com/LimeSurvey/LimeSurvey/blob/45...a/config.xml#L14-L27

for each "extensions"
Assistance on LimeSurvey forum and LimeSurvey core development are on my free time.
I'm not a LimeSurvey GmbH member. - Professional support - Plugins, theme and development .
I don't answer to private message.
The following user(s) said Thank You: LouisGac
The topic has been locked.
More
7 years 5 months ago - 7 years 5 months ago #165942 by ollehar
Replied by ollehar on topic Plugin shop
Yeah. What about the security problem with XML?

Edit: Details here: stackoverflow.com/questions/24117700/cla...oughout-php-versions
Last edit: 7 years 5 months ago by ollehar.
The topic has been locked.
  • LouisGac
  • LouisGac's Avatar
  • New Member
  • New Member
More
7 years 5 months ago #165943 by LouisGac
Replied by LouisGac on topic Plugin shop
we already deal with this problem since 2.50
The topic has been locked.
More
7 years 5 months ago #165944 by ollehar
Replied by ollehar on topic Plugin shop
Great. Then XML it is.
The topic has been locked.
More
7 years 5 months ago #165983 by jelo
Replied by jelo on topic Plugin shop

LouisGac wrote: we already deal with this problem since 2.50

What does deal with mean? Accept the security risk or mitigate it? Wonder what attack vector you all have in mind here.

The amount of metadata needed for the addons seems to be not that big as that JSON can muscle out XML (Remote control api was conquered by JSON ;-).
The meaning of the word "stable" for users
www.limesurvey.org/forum/development/117...ord-stable-for-users
The topic has been locked.
  • LouisGac
  • LouisGac's Avatar
  • New Member
  • New Member
More
7 years 5 months ago #165987 by LouisGac
Replied by LouisGac on topic Plugin shop
json is made for communication between programs. You query an api, you have the result as JSON. If you need a subset of the data of this JSON: you query again the API with better parameters, and you get a new JSON object.

XML is made for human, it's human readable (ex: easy to comment).
More important: it's a querying language in itself.
So you can easily "query" your document, to get the data that interest you inside that document. You have the document with all the data that interest you, and you "query the document" to have the subset of data you want. So, it's not at all the same logic than JSON. In a way, we could say: "XML is an API".
The topic has been locked.
Moderators: holch, tpartner

Lime-years ahead

Online-surveys for every purse and purpose

Pricing & Plans
Get started

Legal

About Us

Open Source