From: Benny M. <ben...@gm...> - 2010-03-06 20:15:54
|
2010/3/6 Doug Blank <dou...@gm...>: > On Sat, Mar 6, 2010 at 9:45 AM, Benny Malengier > <ben...@gm...> wrote: >> 2010/3/6 Doug Blank <dou...@gm...>: >>> On Sat, Mar 6, 2010 at 5:08 AM, Benny Malengier >>> <ben...@gm...> wrote: >>>> 2010/3/6 jerome <rom...@ya...>: >>>>> yes a little bit annoying but just a visual issue, before a new beta, maybe to fix the load/diplay problem on 'Ancestry' category ! >>>>> >>>>> Gramps-3.2beta1 provides only one view on 'Ancestry' category (the PedigreeView). >>>>> >>>>> FanChartView is ignored and I cannot load any addons for this category :( >>>> >>>> If you look in the gpr.py file, you see that the status is UNSTABLE, >>>> so it will not load for users. >>>> I'll change it to STABLE. >>>> Some plugins on the addons may also be unstable. It is up to the >>>> plugin writer to decide if the plugin should be exposed to normal >>>> users. It would be best to update the wiki page on addons, so that >>>> unstable plugins are not in the main section, and it is made clear to >>>> users they must run the _development_ version to see the plugin and >>>> use it. >>> >>> Maybe STABLE/UNSTABLE doesn't make as much sense now that people can >>> HIDE/SHOW plugins? Perhaps those UNSTABLE that ship with Gramps should >>> just be initially hidden? >> >> If something is unstable, it means it is not ready for prime time. > > Except that is not what we are using it for: we use it to be only > visible if not -O for debug tools. I'm moving the UNSTABLE > CalcEstimatedDates and Django Import/Export to Addons, so the only > ones UNSTABLE items left are the debug tools. Feel free to create a status==DEBUG :-) If you move UNSTABLE plugins to addons, be carefull that users don't just download them with the wrong expectation, so leave them UNSTABLE if they are not yet meant for the normal user. As to UNSTABLE in Gramps, it is more convenient to put a plugin to status UNSTABLE and already add it to the Makefiles, then to do it otherwise. So it is from a developing point of view an intersting way to handle not yet finished plugins. It is normal however that in the end all plugins in gramps development branch become STABLE or are removed. It is in other words not a contradiction that there are at the moment no real UNSTABLE plugins in our code. I do think that for addons you need to give the users a way to make a distinction between plugins that are fully developed, and others that are in development. Eg, I used the timeline view, but I saw several bugs. It would be unfortunate if people don't trust gramps-addons because they download something that then they are not satisfied with. A way to give stars as in firefox, or to indicate clearly "work in progress" is important. Consider the first users that go to http://www.gramps-project.org/wiki/index.php?title=3.2_Third-party_Plugins from within Gramps. They look at the top of that file and see two experimental views that will not work for them or be confusing (missing dependencies, not integrated with the rest of Gramps), then two very advanced exporters they don't need, then a clock they don't need, ... >From a PR point of you, you should really organize that page from the most usefull, to the less usefull, to the experimental plugins. Benny > > -Doug > >> There is nothing wrong with that, and it is good to protect our users >> from unstable code. >> It is already possible to hide by default Stable code, see eg the html >> view, so I see no reason to change the policy. >> One of the failings of OSS is immature code being to quickly usable by >> users, which then decide they don't like it, not taking into account >> the code was not finished in the first place. >> >> Benny >> >>> -Doug >>> >>>> >>>> Benny >>>> >>>>> >>>>> --- En date de : Sam 6.3.10, Benny Malengier <ben...@gm...> a écrit : >>>>> >>>>>> De: Benny Malengier <ben...@gm...> >>>>>> Objet: Re: [Gramps-devel] Gramps 3.2.0-0beta1 >>>>>> À: "Stéphane Charette" <ste...@gm...> >>>>>> Cc: "gramps-devel" <gra...@li...> >>>>>> Date: Samedi 6 mars 2010, 0h21 >>>>>> 2010/3/6 Stéphane Charette <ste...@gm...>: >>>>>> >> It seems that it is a Makefile error, Jerome fixed >>>>>> it. You will want >>>>>> >> to patch the beta with it for distribution >>>>>> > >>>>>> > This warrants a beta2, no? I can make time this >>>>>> weekend to put it together >>>>>> > if we want it. >>>>>> >>>>>> It sure is annoying. If you have time, an updated beta for >>>>>> this would >>>>>> be nice. Gramps is working however, so people can still >>>>>> test with this >>>>>> beta. >>>>>> >>>>>> Benny >>>>>> >>>>>> > >>>>>> > Also: James, I *really* could use the debian files >>>>>> (control, rules, ...?) >>>>>> > you use to create the package. The ones I use in our >>>>>> svn repository are >>>>>> > quite out-of-date. I think a while back you talked >>>>>> about fixing up some of >>>>>> > the requirements, but I don't know if our repository >>>>>> was updated. >>>>>> > >>>>>> > Stéphane >>>>>> > >>>>>> >>>>>> ------------------------------------------------------------------------------ >>>>>> Download Intel® Parallel Studio Eval >>>>>> Try the new software tools for yourself. Speed compiling, >>>>>> find bugs >>>>>> proactively, and fine-tune applications for parallel >>>>>> performance. >>>>>> See why Intel Parallel Studio got high marks during beta. >>>>>> http://p.sf.net/sfu/intel-sw-dev >>>>>> _______________________________________________ >>>>>> Gramps-devel mailing list >>>>>> Gra...@li... >>>>>> https://lists.sourceforge.net/lists/listinfo/gramps-devel >>>>>> >>>>> >>>>> >>>>> >>>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Download Intel® Parallel Studio Eval >>>> Try the new software tools for yourself. Speed compiling, find bugs >>>> proactively, and fine-tune applications for parallel performance. >>>> See why Intel Parallel Studio got high marks during beta. >>>> http://p.sf.net/sfu/intel-sw-dev >>>> _______________________________________________ >>>> Gramps-devel mailing list >>>> Gra...@li... >>>> https://lists.sourceforge.net/lists/listinfo/gramps-devel >>>> >>> >> > |