Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

JSON metadata #144

Closed
plfiorini opened this issue Feb 16, 2014 · 0 comments
Closed

JSON metadata #144

plfiorini opened this issue Feb 16, 2014 · 0 comments

Comments

@plfiorini
Copy link
Member

Use JSON for metadata instead of desktop entries.

@plfiorini plfiorini added this to the Version 0.2.1 milestone Feb 16, 2014
@plfiorini plfiorini self-assigned this Feb 16, 2014
plfiorini added a commit that referenced this issue Feb 16, 2014
JSON files are easier to handle because we don't need extra code from
libqtxdg to handle them (Qt 5 already provides an API).

The only reason I was reluctant and started with desktop entries was that
Transifex supports them, but we can synthesize a desktop file from
the JSON metadata with only Name and Comment key and give it to
the translation system. Such a script would also add the translations
to the JSON files as well.

Issue: #144
plfiorini added a commit that referenced this issue Feb 16, 2014
Follow latest changes and load JSON files instead of desktop entries.
Since the "mainscript" key is available to all plugin types we
also add a PluginMetadata::mainScript() method.

Issue: #144
plfiorini added a commit that referenced this issue Feb 16, 2014
PluginMetadata now has a method that returns the main script relative
path, so use that.

Issue: #144
plfiorini added a commit that referenced this issue Feb 16, 2014
There are a few places where we don't use packages yet so we have to
manually load the metadata.

Issue: #144
@plfiorini plfiorini modified the milestones: Version 0.3.0, Version 0.2.1 Feb 23, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant