<div class="gmail_quote">2010/11/22 Martin Dobias <span dir="ltr"><<a href="http://wonder.sk">wonder.sk</a>@<a href="http://gmail.com">gmail.com</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi Alessandro<br>
<div class="im"><br>
On Sun, Nov 21, 2010 at 2:00 PM, Alessandro Pasotti <<a href="mailto:apasotti@gmail.com">apasotti@gmail.com</a>> wrote:<br>
> Hi,<br>
> I've just committed a first draft of the plugins app.<br>
> I've had not much time to test it, admin seems to be working, while public<br>
> views are still missing, I was thinking about using generic views as much as<br>
> possible.<br>
<br>
</div>Thanks a lot for starting with the draft, it looks good!<br>
<div class="im"><br></div></blockquote><div><br></div><div>Thank you for the comments!</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">
<br>
> I'm not sure about the "last" flag in versions, are not the version and<br>
> modified dates sufficient to determine the last version ?<br>
> I've also added some globs to .gitignore<br>
> Comments welcome!<br>
<br>
</div>My comments from a brief review:<br>
- download count should be rather related to plugin versions, not<br>
plugins - for more detailed stats<br></blockquote><div><br></div><div><br></div><div>Probably the best of both word would be a property (trigger) that sums the versions counters for a plugin. </div><div><br></div><div> </div>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
- in addition to user-readable name, there should be plugin's package<br>
(i.e. internal) name which is unique among plugins<br></blockquote><div><br></div><div>Yes I forgot that.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
- the plugin could have two more attributes: active "stable" version<br>
and active "development" (experimental) version. One of them can be<br>
empty, because not all plugins will produce separate<br>
stable/development versions. It should be then possible to change<br>
active version to any version that has been uploaded. I think this is<br>
better than having flags in plugin version model, because only one<br>
stable/development version can be active at one time.<br></blockquote><div><br></div><div>Yes, I thought about a trigger/check that makes the "active" version unique among a plugin branch (experimental and stable) but a version pointer from the parent would also work fine.</div>
<div><br></div><div>I will be working on these topics in the next days.</div><div><br></div><div><br></div></div>-- <br>Alessandro Pasotti<br>w3: <a href="http://www.itopen.it">www.itopen.it</a><br>