#7 Add Module::Starter to New Perl Project Wizard

Jim Graham

I've added the option to use Module::Starter to pre-populate the new Perl Project when created from the New Perl Project Wizard.

This addition involves adding elements to the new Project Page and adding a new Module Starter Preference page. I've also incremented the version numbers in the manifest.mf and in the feature.xml.

The one issue I've had is automatically mapping the Eclipse project name (Foo-Bar) to a Perl module name to pass to module-starter (Foo::Bar). I couldn't figure out how to add a listener to the Project Name text box since the projectNameField in WizardNewProjectCreationPage (which I've subclassed for the {erlNewProjectCreationPage) is private and I can't add a listener to it. I was hoping that listener could automatically update the module name. Instead I update the module name when "Use Module::Starter" is checked. Any thoughts on fixing this would be appreciated.

Thanks, Jim


  • Jim Graham

    Jim Graham - 2008-07-14

    Logged In: YES
    Originator: YES


    I see that you've committed some of this code. I had one fix in the preference page that I noticed after uploading this patch. I will pull down the latest CVS and see if it is still applicable.

    Thanks for committing this

    Regards, Jim Graham

  • Jan Ploski

    Jan Ploski - 2008-07-14

    Logged In: YES
    Originator: NO

    I applied your patch today (first commit) and also committed some required fixes (following commits, have a look; quite a few fixes were needed). The on-the-fly Perl module name update problem in the new project wizard could be worked around by overriding setPageComplete. Fortunately, this method is invoked from the private code in the superclass after each keystroke.

    I also changed the default enablement of module-starter to false, given that it requires additional software to be installed by the user. Furthermore, I changed the default for "override config" to true in order to make it work with default module-starter configuration (otherwise, the install gives a rather cryptic error message about missing author).

    Note for the future that you don't need to update the version number in MANIFEST.MF/feature.xml because they are automatically incremented by the release scripts in org.epic.website/admin. The current policy is to keep the version numbers in CVS unchanged until release time.

  • Jan Ploski

    Jan Ploski - 2009-02-07
    • status: open --> open-accepted
  • Jan Ploski

    Jan Ploski - 2010-12-08
    • status: open-accepted --> closed-accepted

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks