On Nov 10, 2011, at 11:09 AM, Martin Dobias wrote:
> On Thu, Nov 10, 2011 at 4:32 PM, Gary Sherman wrote:
>>
>> [general]
>> name=Metadata Test
>> description=test of metadata generation
>> version=0.1
>> qgisMinimumVersion=1.0
>> class_name=MetadataTest
>> author=GeoApt LLC
>> email_address=gs
On Thu, Nov 10, 2011 at 4:32 PM, Gary Sherman wrote:
>
> [general]
> name=Metadata Test
> description=test of metadata generation
> version=0.1
> qgisMinimumVersion=1.0
> class_name=MetadataTest
> author=GeoApt LLC
> email_address=gsherman@geoapt dot com
> ---
>
> If you have t
On Wed, Nov 9, 2011 at 6:28 PM, Alessandro Pasotti wrote:
>
> I think that the metadata for the plugins will probably change (and
> grow) over time, it would be probably a good idea to change the web
> plugins app schema to handle metadata as denormalized
> key-values-pairs.
That's a possibilit
On Nov 9, 2011, at 10:05 AM, Martin Dobias wrote:
> Hi all
>
> just want to let you know about a recent addition in master branch: I
> have introduced the possibility to put plugin's metadata to a text
> file (metadata.txt).
I've updated the PluginBuilder plugin to generate a metadata file. At
Good addition.
2011/11/9 Martin Dobias :
> Metadata in metadata.txt is preferred to the methods in __init__.py -
> if the text file is present, it is used to fetch the values. Backward
> compatibility is preserved - all existing plugins will continue to
> work. From QGIS 2.0 the metadata from __in
On Thu, Nov 10, 2011 at 07:01:12PM +1000, Nathan Woodrow wrote:
> I don't mind if the change log isn't stored in the ini, no big deal really.
> Was just throwing it out there.
>
> In the end it wouldn't be that hard for the web app to look for a CHANGELOG
> file and read that in. In the end we ju
I don't mind if the change log isn't stored in the ini, no big deal really.
Was just throwing it out there.
In the end it wouldn't be that hard for the web app to look for a CHANGELOG
file and read that in. In the end we just have to set something up with
easy to use and follow conventions so tha
2011/11/10 Sandro Santilli :
> On Thu, Nov 10, 2011 at 05:55:06PM +1000, Nathan Woodrow wrote:
>> Yeah. It would be easier from a developer point of view. I can just stick
>> my change log in there and the web app just reads it in saving me the time
>> to have to fill it out plus then when you do
On Thu, Nov 10, 2011 at 05:55:06PM +1000, Nathan Woodrow wrote:
> Yeah. It would be easier from a developer point of view. I can just stick
> my change log in there and the web app just reads it in saving me the time
> to have to fill it out plus then when you download it you have a central
> pla
On Wed, Nov 09, 2011 at 06:10:13PM -0300, Martin Dobias wrote:
> On Wed, Nov 9, 2011 at 5:45 PM, Nathan Woodrow wrote:
> > Good idea Martin.
> > I had the a thought the other day that it would be good to be able to list
> > the dependencies of the plugin in there too.
>
> Yes. And there are more
Yeah. It would be easier from a developer point of view. I can just stick
my change log in there and the web app just reads it in saving me the time
to have to fill it out plus then when you download it you have a central
place to look for the change log.
- Nathan
On Thu, Nov 10, 2011 at 5:49 P
2011/11/9 Nathan Woodrow :
>>>dependencies may be external python modules, other qgis python
>>>plugins, maybe something more...
> It would be good to also put a change set list some where, sometimes it's
> nice to see what has changed between a version of a plugin. The plugin
> website could read
>>dependencies may be external python modules, other qgis python
>>plugins, maybe something more...
It would be good to also put a change set list some where, sometimes it's
nice to see what has changed between a version of a plugin. The plugin
website could read this and then that would flow dow
2011/11/9 Martin Dobias :
> On Wed, Nov 9, 2011 at 5:45 PM, Nathan Woodrow wrote:
>> Good idea Martin.
>> I had the a thought the other day that it would be good to be able to list
>> the dependencies of the plugin in there too.
>
> Yes. And there are more things that should be added: plugin home
On Wed, Nov 9, 2011 at 5:45 PM, Nathan Woodrow wrote:
> Good idea Martin.
> I had the a thought the other day that it would be good to be able to list
> the dependencies of the plugin in there too.
Yes. And there are more things that should be added: plugin home page,
author name, author mail, ..
Good idea Martin.
I had the a thought the other day that it would be good to be able to list
the dependencies of the plugin in there too.
This list would have to be hand maintained but the author . The plugin
installer would then be able to see before trying to install what the
package needs to r
Hi all
just want to let you know about a recent addition in master branch: I
have introduced the possibility to put plugin's metadata to a text
file (metadata.txt).
Until now plugins' metadata were always retrieved from __init__.py by
calling python methods. Reading metadata from a text file has
17 matches
Mail list logo
