Free proguard acquisition corp pgrd stock quote software for linux

The NSCL Data Acquisition system is a general purpose nuclear physics data acquisition system for small to medium scale nuclear physics experiments.
NSCL Data Acquisition System can be combined with NSCL SpecTcl to form a powerful online/offline data handling system. It is in use at several university labs and, of course, the National Superconducting Cyclotron Laboratory at Michigan State University.
Whats New in 8.1-pre4 Development Release:
- The way the experimental files work has been reorganized.
- Issues in controplush have been fixed.
- More hardware support has been added (preliminary VM-USB support).
Whats New in 8.0-01 Stable Release:
- Make event files readonly as they get finalized.
- Make ~stagearea/complete write protected except when it has to be.
- Fix up 2.6 build so that lib and include get installed... and can be cleaned.
- Fix a bunch of stuff with the 2.6 build that arises on make dist and building from the tarball. (mostly copying stuff from the 8.1 build files.
- Make sure the right compilers link the readout skels.
- Adjust the framework makefile so that template class implementations will get installed in the include directory to allow them to be used in application software.
- Ensure the SBS driver is identical to the 2.6 version of the drive in the 8.1 branch.

ProGuard is a free Java class file shrinker, optimizer, and obfuscator. ProGuard project can detect and remove unused classes, fields, methods, and attributes. It can then optimize bytecode and remove unused instructions.
Finally, it can rename the remaining classes, fields, and methods using short meaningless names. The resulting jars are smaller and harder to reverse-engineer.
More compact jar files also means smaller storage requirements, faster transfer of applications across networks, faster loading, and smaller memory footprints.
ProGuards main advantage compared to other Java obfuscators is probably its compact template-based configuration. A few intuitive command line options or a simple configuration file are usually sufficient. For instance, the following configuration option preserves all applets in a jar:
-keep public class * extends java.applet.Applet
The user manual explains all available options and shows more examples of this powerful configuration style.
ProGuard is fast. It only takes seconds to process programs and libraries of several megabytes. The results section presents actual figures for a number of applications.
ProGuard is a command-line tool with an optional graphical user interface. It also comes with plugins for Ant and for the J2ME Wireless Toolkit.
ProGuard is a Java class file shrinker, optimizer, and obfuscator. The shrinking step detects and removes unused classes, fields, methods, and attributes. The optimization step analyzes and optimizes the bytecode of the methods. The obfuscation step renames the remaining classes, fields, and methods using short meaningless names. The resulting jars are smaller and harder to reverse-engineer.
ProGuard can also be used to list unused fields and methods in an application, and to print out the internal structure of class files.
ProGuard typically reads the input jars (or wars, ears, zips, or directories). It then shrinks, optimizes, and obfuscates them. It then writes the results to one or more output jars (or wars, ears, zips, or directories). The input jars can optionally contain resource files. ProGuard copies all non-class resource files from the input jars to the output jars. Their names and contents remain unchanged.
ProGuard requires the library jars (or wars, ears, zips, or directories) of the input jars to be specified. It can then reconstruct class hierarchies and other class dependencies, which are necessary for proper shrinking, optimization, and obfuscation. The library jars themselves always remain unchanged. You should still put them in the class path of your final application.
In order to determine which code has to be preserved and which code can be discarded or obfuscated, you have to specify one or more entry points to your code. These entry points are typically classes with main methods, applets, midlets, etc.
- In the shrinking step, ProGuard starts from these seeds and recursively determines which classes and class members are used. All other classes and class members are discarded.
- In the optimization step, ProGuard further optimizes the code. Among other optimizations, classes and methods that are not entry points can be made final, and some methods may be inlined.
- In the obfuscation step, ProGuard renames classes and class members that are not entry points. In this entire process, keeping the entry points ensures that they can still be accessed by their original names.
Any classes or class members of your code that are created or invoked dynamically (that is, by name) have to be specified as entry points too. It is generally impossible to determine these cases automatically, but ProGuard will offer some suggestions if keeping some classes or class members appears necessary. For proper results, you should at least be somewhat familiar with the code that you are processing.
ProGuard does handle Class.forName("SomeClass") and SomeClass.class constructs automatically. The referenced classes are preserved in the shrinking phase, and the string arguments are properly replaced in the obfuscation phase. With variable string arguments, it is generally impossible to determine their possible values (they might be read from a configuration file, for instance).
However, as mentioned, ProGuard will note constructs like "(SomeClass)Class.forName(variable).newInstance()". These might be an indication that the class or interface SomeClass and/or its implementations may need to be preserved. You can then adapt your configuration accordingly.
Whats New in 3.9 Stable Release:
- This release fixes a number of bugs.
- Notably, ".class" constructs compiled in Java 6 are now handled correctly.
- The optimization step now avoids a possible division by 0 and correctly processes local variables with indices larger than 255.
- The documentation and examples have been updated.
Whats New in 4.0 Beta Development Release:
- Added preverifier for Java 6 and Java Micro Edition, with new option -dontpreverify.
- Added new option -target to modify java version of processed class files.
- Made -keep options more orthogonal and flexible, with option modifiers allowshrinking, allowoptimization, and allowobfuscation.
- Added support for configuration by means of annotations.
- Improved shrinking of unused annotations.
- Added check on modification times of input and output, to avoid unnecessary processing, with new option -forceprocessing.
- Added new options -flattenpackagehierarchy and -repackageclasses (replacing -defaultpackage) to control obfuscation of packages names.
- Added new options -adaptresourcefilenames and -adaptresourcefilecontents, with file filters, to update resource files corresponding to obfuscated class names.
- Now respecting naming rule for nested class names (EnclosingClass$InnerClass) in obfuscation step, if InnerClasses attributes or EnclosingMethod attributes are being kept.
- Added new inter-procedural optimizations: method inlining and propagation of constant fields, constant arguments, and constant return values.
- Added optimized local variable allocation.
- Added over 250 new peephole optimizations.
- Improved making classes and class members public or protected.
- Now printing notes on suspiciously unkept classes in parameters of specified methods.
- Now printing notes for class names that dont seem to be fully qualified.
- Added support for uppercase filename extensions.
- Rewritten class file I/O code.
- Updated documentation and examples.

Advanced Stock Tracking System provides the individual investor with a powerful set of tools for making financial decisions and tracking securities.

This project features a portfolio with dividend tracking, worksheet to keep track of prospects, a stock comparison utility, a search engine for the stock market and an alert engine to email you about key events in your securities.

Finance::YahooQuote is a Perl module that can get stock quotes from Yahoo! Finance.

SYNOPSIS

use Finance::YahooQuote;
# setting TIMEOUT and PROXY is optional
$Finance::YahooQuote::TIMEOUT = 60;
$Finance::YahooQuote::PROXY = "http://some.where.net:8080";
@quote = getonequote $symbol; # Get a quote for a single symbol
@quotes = getquote @symbols; # Get quotes for a bunch of symbols
useExtendedQueryFormat(); # switch to extended query format
useRealtimeQueryFormat(); # switch to real-time query format
@quotes = getquote @symbols; # Get quotes for a bunch of symbols
@quotes = getcustomquote(["DELL","IBM"], # using custom format
["Name","Book Value"]); # note array refs

This module gets stock quotes from Yahoo! Finance. The getonequote function will return a quote for a single stock symbol, while the getquote function will return a quote for each of the stock symbols passed to it. getcustomquote allows to specify a format other than the default to take advantage of the extended range of available information.

The download operation is efficient: only one request is made even if several symbols are requested at once. The return value of getonequote is an array, with the following elements:

0 Symbol
1 Company Name
2 Last Price
3 Last Trade Date
4 Last Trade Time
5 Change
6 Percent Change
7 Volume
8 Average Daily Vol
9 Bid
10 Ask
11 Previous Close
12 Todays Open
13 Days Range
14 52-Week Range
15 Earnings per Share
16 P/E Ratio
17 Dividend Pay Date
18 Dividend per Share
19 Dividend Yield
20 Market Capitalization
21 Stock Exchange

If the extended format has been selected, the following fields are also retrieved:

22 Short ratio
23 1yr Target Price
24 EPS Est. Current Yr
25 EPS Est. Next Year
26 EPS Est. Next Quarter
27 Price/EPS Est. Current Yr
28 Price/EPS Est. Next Yr
29 PEG Ratio
30 Book Value
31 Price/Book
32 Price/Sales
33 EBITDA
34 50-day Moving Avg
35 200-day Moving Avg
If the real-time format has been selected, the following fields are also retrieved:
36 Ask (real-time)
37 Bid (real-time)
38 Change in Percent (real-time)
39 Last trade with time (real-time)
40 Change (real-time)
41 Day range (real-time)
42 Market-cap (real-time)

The getquote function returns an array of pointers to arrays with the above structure.
The getonequote function returns just one quote, rather than an array. It returns a simple array of values for the given symbol.

The setQueryString permits to supply a new query string that will be used for subsequent data requests.

The useExtendedQueryFormat and useRealtimeQueryFormat are simpler interfaces which append symbols to the default quote string, as detailed above.

The getcustomquote returns an array of quotes corresponding to values for the symbols supplied in the first array reference, and the custom fields supplied in the second array reference. Here the custom fields correspond to the named fields of the list below.

Beyond stock quotes, Finance::YahooQuote can also obtain quotes for currencies (from the Philadephia exchange -- however Yahoo! appears to have stopped to support the currency symbols in a reliable manner), US mutual funds, options on US stocks, several precious metals and quite possibly more; see the Yahoo! Finance website for full information. Finance::YahooQuote can be used for stocks from the USA, Canada, various European exchanges, various Asian exchanges (Singapore, Taiwan, HongKong, Kuala Lumpur, ...) Australia and New Zealand. It should work for other markets supported by Yahoo.

You may optionally override the default LWP timeout of 180 seconds by setting $Finance::YahooQuote::TIMEOUT to your preferred value.

You may also provide a proxy (for the required http connection) by using the variable $Finance::YahooQuote::PROXY. Furthermore, authentication-based proxies can be used by setting the proxy user and password via the variables $Finance::YahooQuote::PROXYUSER and $Finance::YahooQuote::PROXYPASSWD.

Two example scripts are provided to help with the mapping a stock symbols as well as with Yahoo! Finance server codes. The regression tests scripts in the t/ subdirectory of the source distribution also contain simple examples.

Program Guard allows the user of a Linux workstation to specify which application programs that are allowed TCP/IP connections to the Internet (Internet addresses are defined as any IP address not in the range of 10.0.0.0/24 or 192.168.0.0/16).

The application program names can be specified by listing them in a file (Static Mode) by querying the user (Query Mode). In Query Mode, when a program that is unknown to Program Guard attempts to access an Internet IP address, Program Guard displays the Program Guard Dialog Box.

In addition to providing connection information, this dialog box gives the workstation user the option of allowing the program to access the Internet or to be blocked from accessing the Internet. This can be done either for the current instance of the program or for this and all future instances of the program (Make Persistent checkbox).

Currently, the program names that are allowed or denied Internet access apply to all users of the workstation rather than on a per user basis. For example, if Program Guard is running in Query Mode and user A invokes a program previously blocked from Internet access by user B, the program will be blocked from Internet access for User A as well.

Connections blocked by Program Guard are logged to the Program Guard log file pgrd.log. It is located in the /var/log/pgrd directory. If desired, Program Guard can be configured to log all Internet connection attempts rather than just those that have been blocked.

Program Guard was tested on Fedora Core 1 and Fedora Core 3 on single processor 32 bit X86 Intel processors. It has not been tested on other distributions or on multi-processor machines. While it works on Fedora Core 1, it will not build on a standard Linux 2.4.x kernel due to task_struct definitions that were not made until Linux 2.6. If there is enough interest, a version that runs under a standard Linux 2.4 kernel may be made available.

To run in Query Mode, Gnome 2.x and Glade 2.x are required. There are no prerequisites for Static Mode.

Installation:

Program Guard consists of three components: a kernel module; a daemon; and a Gnome GUI user interface component. All files needed to build the components are in the pgrd.tgz file. An installation shell script install-pgrd is provided for Fedora distributions.

It will build/install (or remove) the kernel module and daemon as well as configure them to be started automatically when the system is booted. To invoke it, type install-pgrd < install | remove >. This script may or may not be useable as is for other Linux distributions.

If you modify the install script, please note that the module, daemon and various support files must be installed in the /opt/pgrd directory for Program Guard to work properly (this is already handled when using the install script as provided). To run in Query Mode, each user must be configured by invoking the install-pgrd_user < username > script. And by going to the Preferences->More Preferences->Sessions selection in the Fedora Main Menu and adding pgrdgui to the Startup Programs tab.

Program Guard will be started the next time the machine is rebooted. If you do not wish to reboot, you may start Program Guard manually as described below in Manual Starting And Stopping. Note: If starting manually and using Query Mode, once the daemon and kernel module are started, make sure that you log out and log back in.

Afghan Hound Quote of the Day Daemon project is a TCP/UDP quote-of-the-day server.
Afghan Hound Quote of the Day Daemon uses both TCP and UDP port 17 to return a random quote from fortune(6) style quote files. It has performance benefits over other programs which use fortune(6) to source their quotes.
The server also includes the ability to limit the number of client connections per second. Client and benchmarking programs are included in the package.
Main features:
- RFC865 compatibility - The official standard for qotd (port 17) services.
- Only needs root if listening on ports lower than 1024, however it should drop root as soon as possible.
- Uses standard fortune(6) text-file, text-file.dat style quote files.
- All new code to read and create fortune files.
- Listens on both TCP and UDP user specifiable ports.
- Can limit returned quotes to lie in a max-size, min-size range.
- Can limit maximum number of connections per second independently on both TCP and UDP.
- Can log connections, optionally recording hostname and ident information.
- Logging can either be to a specified log file, or to syslog
- Handles rot13-encoded (offensive) quotes, which can be enabled or disabled.
- Many configuration items can be changed at run-time.
- Known to compile on Solaris 2.5 (Ultra SPARC) and Linux 2.2.16 (Intel and sparc32). (With gcc everywhere and Suns cc on Solaris.)
Enhancements:
- Bug fixes: signal.c:
- client.c: Added gcc __attribute__ thing to signal handlers, elimiates warning.
- Added F_NOTIFY to allow auto reloading if fortune files change.

Gnome::StockIcons is a Gnome 1.4 stock icons in XPM format.

SYNOPSIS

use Gtk;
use Gnome::StockIcons;

my ( $pixmap, $mask ) = Gtk::Gdk::Pixmap->create_from_xpm_d( $window->window,
$style,
@stock_help );

These are the Gnome 1.4 stock icons. The original PNG files are in gnome-libs-1.4.1.2.90/libgnomeui/pixmaps. All names are identical but - is replaced by _. Currenlty, this only affects calculator-font.png (@calculator_font).
The module does not strictly speaking require Gtk, but its not much use without.

EXPORT

All icons are exported as arrays. See the source for a full list

Finance::Quote is a Perl module to get stock and mutual fund quotes from various exchanges.

SYNOPSIS

use Finance::Quote;
$q = Finance::Quote->new;

$q->timeout(60);

$conversion_rate = $q->currency("AUD","USD");
$q->set_currency("EUR"); # Return all info in Euros.

$q->require_labels(qw/price date high low volume/);

$q->failover(1); # Set failover support (on by default).

%quotes = $q->fetch("nasdaq",@stocks);
$hashref = $q->fetch("nyse",@stocks);

This module gets stock quotes from various internet sources, including Yahoo! Finance, Fidelity Investments, and the Australian Stock Exchange. There are two methods of using this module -- a functional interface that is depreciated, and an object-orientated method that provides greater flexibility and stability.

With the exception of straight currency exchange rates, all information is returned as a two-dimensional hash (or a reference to such a hash, if called in a scalar context). For example:

%info = $q->fetch("australia","CML");
print "The price of CML is ".$info{"CML","price"};

The first part of the hash (eg, "CML") is referred to as the stock. The second part (in this case, "price") is referred to as the label.