Nick,


My bad, I should not use the 'status' word!
I only thought on something like:

DEVEL = False
  on gramps.gen.const or anywhere else

then, maybe:

from gramps.gen.const import DEVEL

if DEVEL:
    register(GRAMPLET, 
    id="Python Evaluation", 
    name="Python Evaluation",  # do not need translation marks
    description = "Gramplet allowing the evaluation of python code", # do not need translation marks
    version="1.0.0",
    gramps_target_version="4.1",
    status = STABLE,
    fname="eval.py",
    height=200,
    gramplet = 'PythonEvaluation',
    gramplet_title="Python Evaluation", # do not need translation marks
    )

We only register on a DEVEL stage.

See also GUI warning on 'gramps/gui/grampsgui.py'!
We need to remember to hide this welcome message before next major release... This was used to prevent and warn use of gramps as stable with trunk (was svn). Some translators also started to use git with master, sometimes with their main databases. 


def _display_welcome_message():
    """
    Display a welcome message to the user.
    """
    if not config.get('behavior.betawarn'):
        from .dialog import WarningDialog
        WarningDialog(
            _('Danger: This is unstable code!'),
            _("This Gramps 3.x-trunk is a development release. "
              "This version is not meant for normal usage. Use "
              "at your own risk.\n"
              "\n"
              "This version may:\n"
              "1) Work differently than you expect.\n"
              "2) Fail to run at all.\n"
              "3) Crash often.\n"
              "4) Corrupt your data.\n"
              "5) Save data in a format that is incompatible with the "
              "official release.\n"
              "\n"
              "<b>BACKUP</b> your existing databases before opening "
              "them with this version, and make sure to export your "
              "data to XML every now and then."))
        config.set('behavior.autoload', False)
       # config.set('behavior.betawarn', True)
        config.set('behavior.betawarn', config.get('behavior.betawarn'))


OK, the lazy patch might be to re-use 'behavior.betawarn' config key for registering these DEVEL gramplets too!!!

A properly way is maybe either a global single variable or a config key.


Jérôme.

Le jeu. 17 avril 2014 at 19:41, Nick Hall <nick__hall@hotmail.com> a écrit :
Jérôme,

Changing the status from STABLE to UNSTABLE will make them available for developers only.  Would a new status of DEBUG be better?

Creating a "grampletdebug.gpr.py" file is a good idea.

Nick.


On 17/04/14 14:56, Jerome wrote:
What should be the status of 'new' debug tools (migration from tool to gramplet)? 

register(GRAMPLET, 
         id="Python Evaluation", 
         name=_("Python Evaluation"), 
         description = _("Gramplet allowing the evaluation of python code"),
         version="1.0.0",
         gramps_target_version="4.1",
         status = STABLE,
         fname="eval.py",
         height=200,
         gramplet = 'PythonEvaluation',
         gramplet_title=_("Python Evaluation"),
         )

register(GRAMPLET, 
         id="Uncollected Objects", 
         name=_("Uncollected Objects"), 
         description = _("Gramplet showing uncollected objects"),
         version="1.0.0",
         gramps_target_version="4.1",
         status = STABLE,
         fname="leak.py",
         height=200,
         gramplet = 'Leak',
         gramplet_title=_("Uncollected Objects"),
         )

Like for Tools, we can have a "grampletdebug.gpr.py", which could be ignored for translation and ignored (or hidden) on releases?


regards,
Jerome

Le mer. 9 avril 2014 at 13:33, Nick Hall <nick__hall@hotmail.com> a écrit :
Devs, I suggest the following schedule for the release of v4.1: 9th April - Code freeze for new features. 7th May - String freeze and creation of maintenance branch. 21st May - Release date. This gives us four weeks of testing and bug fixing, followed by two weeks for the translators. This will keep us on track for previous releases: v4.0.0 - 21st May 2013 v3.4.0 - 22nd May 2012 v3.3.0 - 13th Jun 2011 Any help you can give with testing and bug fixing would be appreciated. Regards, Nick. ------------------------------------------------------------------------------ Put Bad Developers to Shame Dominate Development with Jenkins Continuous Integration Continuously Automate Build, Test & Deployment Start a new project now. Try Jenkins in the cloud. http://p.sf.net/sfu/13600_Cloudbees _______________________________________________ Gramps-devel mailing list Gramps-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/gramps-devel