With a little bit of work, was able to build a nice "Wuhan Coronavirus Status" app using MQTT and the IoT-OnOff app. More on this technique here:
ESP32 (ESP-WROOM-32) as an MQTT Client Subscribed to Linux Server Load Average Messages
The result turned out nice, I think. I like the look and... (10 Replies)
Hello All,
Want to share here an article for Whats app users that team whats app is requesting users to upgrade to its latest version since they have found a vulnerability; where Hacker could turn on a cell's camera, mic and scan messages and emails.
Here is an article from "THE VERGE" for... (1 Reply)
Hi to all
Like in the subject, i got the problem with camera ID 0c45:613b Microdia Win2 PC Camera under Ubuntu. When i plug in camera to USB, Ubuntu put in sn9c102 module, but on this site Linux Kernel Driver Database: CONFIG_USB_GSPCA_SONIXJ: SONIX JPEG USB Camera Driver is information that... (0 Replies)
I need to realize the user login name after he/she used the 'su' command to log under another name (for specific privileges.)
I am on SunOS v5.6, and here by now I could not find a way to figured it out.
In another Thread I've get an advise from Linux user to use 'ps afxj' that display a... (3 Replies)
App::Cmd::Setup(3pm) User Contributed Perl Documentation App::Cmd::Setup(3pm)NAME
App::Cmd::Setup - helper for setting up App::Cmd classes
VERSION
version 0.318
OVERVIEW
App::Cmd::Setup is a helper library, used to set up base classes that will be used as part of an App::Cmd program. For the most part you
should refer to the tutorial for how you should use this library.
This class is useful in three scenarios:
when writing your App::Cmd subclass
Instead of writing:
package MyApp;
use base 'App::Cmd';
...you can write:
package MyApp;
use App::Cmd::Setup -app;
The benefits of doing this are mostly minor, and relate to sanity-checking your class. The significant benefit is that this form
allows you to specify plugins, as in:
package MyApp;
use App::Cmd::Setup -app => { plugins => [ 'Prompt' ] };
Plugins are described in App::Cmd::Tutorial and App::Cmd::Plugin.
when writing abstract base classes for commands
That is: when you write a subclass of App::Cmd::Command that is intended for other commands to use as their base class, you should use
App::Cmd::Setup. For example, if you want all the commands in MyApp to inherit from MyApp::Command, you may want to write that package
like this:
package MyApp::Command;
use App::Cmd::Setup -command;
Do not confuse this with the way you will write specific commands:
package MyApp::Command::mycmd;
use MyApp -command;
Again, this form mostly performs some validation and setup behind the scenes for you. You can use "base" if you prefer.
when writing App::Cmd plugins
App::Cmd::Plugin is a mechanism that allows an App::Cmd class to inject code into all its command classes, providing them with utility
routines.
To write a plugin, you must use App::Cmd::Setup. As seen above, you must also use App::Cmd::Setup to set up your App::Cmd subclass if
you wish to consume plugins.
For more information on writing plugins, see App::Cmd::Manual and App::Cmd::Plugin.
AUTHOR
Ricardo Signes <rjbs@cpan.org>
COPYRIGHT AND LICENSE
This software is copyright (c) 2012 by Ricardo Signes.
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-05-05 App::Cmd::Setup(3pm)