Getting Started With the NetBeans IDE BlueJ Plugin

4 More Discussions You Might Find Interesting

1. Fedora

Installing netbeans

How can I install netbeans on Solaris. Is there a package manager like yum for Fedora. I have tried pkg install netbeans, doesnt find it. Already preformed pkg install slim_install and it installed the jre. However if I run the sh file downloaded for netbeans it says no compatible JDK found. Now...

2. Programming

Netbeans ide can't display chinese character in linux

When i write the source code in netbeans environment,if the source code,there are chinese characters,chinese characters will be displayed as box,how to solve this problem?please

3. Filesystems, Disks and Memory

shift hard disk from primary IDE channel to secondary IDE channal

Wellcomes All, some times ago I 've installed a Debian ditribution on an Hard Disk who was set as Primary Master. Few days ago, I 've decided to install another Hard Disk with a different Operating System. When I did that, I turned off the old hard disk, and I mouted the new one on the Primary IDE...

4. HP-UX

netbeans IDE on Hp-UX

Can netbeans IDE be installed and used on hp-ux? Sorry I know this is more java specific but does anybody have any experience with this? There does not seem to be any specific installation or support from netbeans.

LEARN ABOUT DEBIAN

devel::patchperl::plugin

Devel::PatchPerl::Plugin(3pm)				User Contributed Perl Documentation			     Devel::PatchPerl::Plugin(3pm)

NAME

       Devel::PatchPerl::Plugin - Devel::PatchPerl plugins explained

VERSION

       version 0.72

DESCRIPTION

       This document explains the Devel::PatchPerl plugin system.

       Plugins are a mechanism for providing additional functionality to Devel::PatchPerl.

       Plugins are searched for in the Devel::PatchPerl::Plugin namespace.

INITIALISATION

       The plugin constructor is "patchperl".

       A plugin is specified using the "PERL5_PATCHPERL_PLUGIN" environment variable. It may either be specified in full (ie.
       "Devel::PatchPerl::Plugin::Feegle") or as the short part (ie. "Feegle").

	 $ export PERL5_PATCHPERL_PLUGIN=Devel::PatchPerl::Plugin::Feegle

	 $ export PERL5_PATCHPERL_PLUGIN=Feegle

       When Devel::PatchPerl has identified the perl source patch and done its patching it will attempt to load the plugin identified. It will
       then call the class method "patchperl" for the plugin package, with the following parameters:

	 'version', the Perl version of the source tree;
	 'source', the absolute path to the Perl source tree;
	 'patchexe', the 'patch' utility that can be used;

       Plugins are called with the current working directory being the root of the Perl source tree, ie. "source".

       Summarised:

	 $ENV{PERL5_PATCHPERL_PLUGIN} = 'Devel::PatchPerl::Plugin::Feegle';

	 my $plugin = $ENV{PERL5_PATCHPERL_PLUGIN};

	 eval "require $plugin";

	 eval {
	   $plugin->patchperl( version => $vers, source => $srcdir, patchexe => $patch );
	 };

WHAT CAN PLUGINS DO
?
       Anything you desire to a Perl source tree.

WHY USE AN ENVIRONMENT VARIABLE TO SPECIFY PLUGINS
?
       So that indicating a plugin to use can be specified independently of whatever mechanism is calling Devel::PatchPerl to do its bidding.

       Think perlbrew.

AUTHOR

       Chris Williams <chris@bingosnet.co.uk>

COPYRIGHT AND LICENSE

       This software is copyright (c) 2012 by Chris Williams and Marcus Holland-Moritz.

       This is free software; you can redistribute it and/or modify it under the same terms as the Perl 5 programming language system itself.

perl v5.14.2							    2012-06-04					     Devel::PatchPerl::Plugin(3pm)

Solaris BigAdmin RSS