Free crc handbook software for linux

DocBook Doclet project creates DocBook XML from Java source documentation or HTML files. It is helpful if you want to create reference handbooks of your API.

Normally it is used with the Javadoc tool but it can also be used as a standalone application to convert HTML to DocBook.

Additionally it comes with a Swing application to manage documentation projects and to transform the resulting DocBook files to PDF, Postscript, HTML, or JavaHelp.

Hardware::iButton is a Perl module that allows to talk to DalSemi iButtons via a DS2480 serial widget.

SYNOPSIS

use Hardware::iButton::Connection;
$c = new Hardware::iButton::Connection "/dev/ttyS0";
@b = $c->scan();
foreach $b (@b) {
print "family: ",$b->family(), "serial number: ", $b->serial(),"n";
print "id: ",$b->id(),"n"; # id = family . serial . crc
print "reg0: ",$b->readreg(0),"n";
}

This module talks to iButtons via the "active" serial interface (anything using the DS2480, including the DS1411k and the DS 9097U). It builds up a list of devices available, lets you read and write their registers, etc.

The connection object is an Hardware::iButton::Connection. The main user-visible purpose of it is to provide a list of Hardware::iButton::Device objects. These can be subclassed once their family codes are known to provide specialized methods unique to the capabilities of that device. Those devices will then be Hardware::iButton::Device::DS1920, etc.

iButtons and solder-mount Touch Memory devices are each identified with a unique 64-bit number. This is broken up into 8 bits of a "family code", which specifies the part number (and consequently the capabilities), then 48 bits of device ID (which Dallas insures is globally unique), then 8 bits of CRC. When you pass these IDs to and from this package, use hex strings like "0123456789ab".

Acme::OneHundredNotOut is a raise of the bat, a tip of the hat.

I have just released my 100th module to CPAN, the first time that anyone has reached that target. As some of you may know, I am getting ready to go back to college and reinvent myself from being a programmer into being a missionary. I dont forsee that many more Perl modules coming out of this.

Of course, this doesnt mean that Im going to abjure usage of Perl forever; any time theres a computer and something I need automated, out will come the Swiss Army Chainsaw and the job will get done. In fact, we recently needed to manipulate some text from a mission handbook to translate it into Japanese, and Perl was there handling and collating all that.

But 100 modules is a convenient place to stop and take stock, and I hope that those of you who have benefitted from my modules, programs or writing about Perl will forgive me a certain spot of self-indulgence as I look back over my CPAN career, especially since I feel that the diversity of modules that Ive produced is a good indication of the diversity of what can be done with Perl.

Lets begin, then, with some humble beginnings, and then catch up on recent history.
The Embarrassing Past

Contrary to popular belief, I was not always a CPAN author. I started writing modules in 1998, immediately after reading the first edition of the Perl Cookbook - yes, you can blame Nat and Tom for all this. The first module that I released was Tie::DiscoveryHash, since Id just learnt about tied hashes. As with many of my modules, it was an integral part of another software project which I actually never finished, and now cant find.

The first module that I ever wrote (but, by a curious quirk of fate, precisely the fiftieth module I released) was called String::Tokeniser, which is still a reasonably handy way of getting an iterator over tokenising a string. (Someone recently released String::Tokenizer, which makes me laugh.) This too was for an abortive project, webperl, an application of Don Knuths WEB system of structured documentation to Perl. However, given the code quality of these two modules, its perhaps just as well that the projects never saw the light of day.

There are a few other modules Id rather like to forget, too. Devel::Pointer was a sick joke that went badly wrong - it allowed people to use pointers in Perl. Some people failed to notice that referring to memory locations directly in an extremely high-level language was a dangerous and silly thing to do, and actually used the damned thing, and I started getting requests for support for it. Then at some point in 2001, when I should really have known better, I developed an interest in Microsofts .NET and the C# language, which I still think is pretty neat; but I decided it might be a good idea to translate the Mono projects tokenizer and parser into Perl, ending up with C::Sharp. I never got around to doing the parser part, or indeed anything else with it, and so it died a lonely death in a dark corner of CPAN. GTK::HandyClist was my foray into programming graphical applications, which started and ended there.

Bundle::SDK::SIMON was actually the slides from a talk on my top ten favourite CPAN modules - except that this changes so quickly over time, it doesnt really make much sense any more.

Finally, Array::FileReader was an attempt to optimize a file access process. Unfortunately, my "optimization" ended up introducing more overheads than the naive solution. It all goes to show. Since then, Mark-Jason Dominus, another huge influence in the development of my CPAN career, has written Tie::File, which not only has a better name but is actually efficient too.

The Internals Phase

1999-2000 were disastrous years for me personally but magnificent years Perl-sonally. Stuck in a boring job and a tiny flat in the middle of Tokyo, I had plenty of time to get stuck into more Perl development. I felt that getting involved with perl5-porters would be a good way of gettting to know more about Perl, and so I needed a hobby horse - an issue of Perls development that I cared about. Since I was in Japan and working a lot with non-Latin text, Unicode support seemed a good thing to work on, and so Unicode::Decompose appeared, while I fixed up a substantial part of the post-5.6 core Unicode support.

Id recommend this way to anyone who wants to get more involved in the Perl community, although I was very lucky in terms of who else happened to be around at the time: Gurusamy Sarathy was extremely gracious in helping me turn my fledgling C code into something fit for the Perl core, and he also helped me understand the perl5-porters etiquette (yes, there was some at the time) and what makes a good patch, while Jarkko Hietaniemi was always good for suggestions of interesting things for keen people to work on. Seriously, get involved. If I can do it, anyone can.
Anyway, this fixation with understanding the Perl 5 internals, and especially the Perl 5 compiler, (due to yet another of my Perl influences, the great Malcolm Beattie) led to quite a torrent of modules, from ByteCache, an implementation of just-in-time compilation for Perl modules, through B::Flags and B::Tree to help visualising the Perl op tree, to uninit, B::Generate, optimizer and B::Utils for modifying it.

Perl About The House

Now we abandon chronological order somewhat and take a look at the various areas in which Ive used Perl. One of these areas has been the automation of everyday life: checking my bank balance with Finance::Bank::LloydsTSB (the first Perl module to interface to personal internet banking, no less) and my phone bill with a release of Tony Bowdens Data::BT::PhoneBill.

Finance::Bank::LloydsTSB was meant to go with Finance::QIF, my Quicken file parser, to produce another now-abandoned idea, a Perl finances manager. It seemed that Im only capable of producing modules, not full standalone applications - or at least, it seemed that way until I produced Bryar, my blogging software, based on the concepts from Rael Dornfests blosxom and beginning my adventures with Andy Wardleys Template Toolkit. Bryar also tuned me in to the Model-View-Controller framework idea, of which more later.

Another project I briefly played with was a personal robot, using the Sphinx/Festival speech handling and recognition modules from Cepstral and Kevin Lenzo. I didnt have X10, so I couldnt shout "lights" into the air in a wonderfully scifi way, but I could shout "mail" and have a summary of my inbox read to me, "news" to get the latest BBC news headlines, and "time" to hear the time. Of course, getting computers to tell the time nicely takes a little bit of work. I dont like "Its eleven oh-three pee em", since thats not what someone would say if you asked them the time. I wanted my robot to say "Its just after eleven", and thats what Time::Human does. Shame about the localisation.

Graidle (Graph aid), is a project that is proposed to create an application web for the realization of graph; it comes divided in four parts:
Graidle Fx proposed like didactic instrument for the visualization of diagrams of function to one variable;
Graidle SQL Friendly assists the creation of a graph starting from one query;
Graidle FrontEnd supplies to the user a graph personalized second every own requirement;
Graidle Class is the class that comes supplied for the development;
The realization of the site is apt to the demonstration of the operation of the same application, that it can be more complete visualizing sources releasable liberations in the appropriate Download section. We will have therefore one dedicated section to every part of the plan: In Function the customer will insert the number of functions to visualize, the interval and the quality of the curve and will come created a diagram to the flight; With the FronEnd they will be able to be inserted until to nine series give to you, choosing of the type, the name, the options like the colors, the title it, maximum and minimal, the lines grid etc... the customer will be able to save the just graphical one and to insert it in situated presentations or web; From SQL is a pure demonstrative and educational section, that it concurs to create given diagram of one query SQL; between the multiple usefullnesses there is that one of being able to visualize in realtime the graph of some give you present in database without or that one of being able to enclose to the tables of resultset a diagram that can clarify the visualization of gives to you; the handbook for who is available also wanted to externally use the class to this situated one;
The Graidle project is realized in PHP with the aid of GD2 library.
Enhancements:
- Introducing of Horizontal Histogram graph type;
- Introducing of Extended Legend for Horizontal Histogram;
- Introducing of new legend management system for a better visualization of all type of strings;
- Introducing of Selection standard CSS color on setValue function;
- New setMultiColor() to visualize different color on same value serie ;
- New setColors() to add one or more colors;
- New Bold Font type ;
- New setFontBD() method;
- Modified carry2file() for select patch and filename;

savIRC project is an IRC client for Linux and Windows.
Main features:
- multiple server connections
- CTCP
- DCC also "passive"
- SOCK5 for servers and DCCs
- ignore and notify lists
- mIRC colors
- URL caption
- Tabbed-MDI
- scripting in TCL/Tk!
Enhancements:
- The savIRC handbook has been updated and converted to docbook.
- The source code has begun to be documented with ROBOdoc.
- A checkbox to hide automatic serverpings was added. /disconnect now stops autoreconnect.
- Chunks of text are broken into 400 chars or less and will be sent with a delay to prevent flooding.
- An alternate nick is used if the one tried is erroneous on the current ircd.

RefDB is a reference database and bibliography tool for SGML, XML, and LaTeX/BibTeX documents.
RefDB allows users to share databases over a network. RefDB is lightweight and portable to basically all platforms with a decent C compiler. And its released under the GNU General Public License.
RefDB appears to be the only available tool to create HTML, PostScript, PDF, DVI, MIF, or RTF output from DocBook or TEI sources with fully formatted citations and bibliographies according to publishers specifications (check out some examples). Additional document types can be easily added.
Main features:
- RefDB is a reference/notes database and bibliography tool for SGML, XML, and LaTeX documents.
- RefDB is mainly implemented in C, with a few Perl scripts inbetween, as well as shell scripts as "glue". It can be compiled on all platforms with a decent C compiler (a small amount of porting may be required). It builds and runs out of the box on Linux, FreeBSD, NetBSD, Solaris, OSX, Darwin, and Windows/Cygwin.
- RefDB is modular and accessible. You can plug in a variety of database engines to store your data, and you can choose between a variety of interfaces for interactive work. You can use RefDB in your projects through shell scripts or from Perl programs.
- The RefDB handbook (more than 300 printed pages) helps you to get RefDB up and running quickly and explains how to use the software for both administrators and users in great detail. In addition there is a tutorial targeted at plain users.
- RefDB uses a SQL database engine to store the references, notes, and the bibliography styles. Choose either an external database server for optimum performance and flexibility, or an embedded database engine for convenience (see below for supported database engines).
- Both reference and bibliography style databases use the relational features of SQL databases extensively to consolidate information and to save storage space.
- RefDB employs a three-tier architecture with lots of flexibility: clients, an application server that can run as a daemon, and the database server. If you prefer the embedded SQL engine, therell be a two-tier setup. In both cases, all tiers may run on a single workstation for individual use.
- The application server can generate log messages to monitor its operation.
- RefDB contains two standard interfaces: a command line interface for terminal addicts and for use in scripts, and a PHP-based web interface for a more visual approach. In addition, both Emacs and Vim users can access RefDB from the editing environment theyre used to. Finally, there is also a Perl client module to integrate RefDB functionality into your own Perl programs.
- The main input format for bibliographic data is RIS which can be generated and imported by all major reference databases on Windows (Reference Manager, EndNote and the like). An XML representation of RIS using the risx DTD is also supported as a native format. The latter is well suited as a means to import SGML or XML bibliographic data.
- Import filters are provided for Medline (tagged and XML), BibTeX, MARC, and DocBook.
- The data can be retrieved as simple text, formatted as HTML, formatted as a DocBook bibliography element (SGML or XML), formatted as a TEI listBibl element (XML), formatted as BibTeX reference list, or formatted as RIS or risx files.
- All character encodings supported by your platform can be used both for data input and for data export. This includes European character sets like Latin-1 and of course Unicode.
- Extended notes can be linked to one or more references, authors, periodicals, or keywords to create topics or material collections. These are more powerful and flexible than folder systems and the like.
- The query language is fairly simple yet powerful. You can use booleans to combine queries on any combination of fields. You can use brackets to group queries. You can use Unix-style regular expressions to formulate advanced queries.
Enhancements:
- A problem was fixed with the addref/updateref command, which would occasionally report an error although the command in fact succeeded.
- A possible segfault in the checkref command was fixed too.
- Bibliographies now accept references without any titles.

ROMBrowser project is a tool for organizing emulator ROMs.
It will identify rom files by their CRC, give information about their characteristics (game title, parent rom, etc), and organize those ROMs with different filters.
If you like to play with emulation and emulators, you know the pain of keeping track of your thousands of ROM files, not to mention figuring out what it is youve just downloaded. Thats what ROMBrowser is for. Eventually I hope to have a system that works somewhat like romcenter, but is java based and GPLd.
I also am planning on developing a schema for storing meta-data related to ROM files. There are currently several databases out there that have information about ROM files, usually keyed by the files CRC32. Part of the ROMBrowser project will be to develop an open standard for that kind of data (probably an XML DTD) and a plan for the distributed classification of ROM files, so users can classify unknown ROMs and distribute that information.
Enhancements:
- Added Super Nintendo rom handler for SMC files. It doesnt handle interleaved files yet.
- Separated out datafiles from main distribution, added credits tag to xml database, to give credit to the rom database maintainers (just using conversions of cowerings goodtools for now).
- Changed rom info viewer to table view. Added ability to modify rom data, changes will be saved in knownfiles.xml
- Changed how file searching works, now only files that have romhandlers (nes and smc currently) get processed, all others are ignored.
- Made file converter work better for converting romcenter dat files (use net.sourceforge.rombrowser.util.ROMDatabaseFileConverter
- Deleting specific roms from the treeview will remove them from knownfiles, and will also delete them from the filesystem if delete-on-remove is true.
- Deleting folders from the treeview will still not remove their child entries from knowfiles or delete the foders or their children.
- Changed the way rominfo files are handled, now if the datafile property has colons in it, it will treat it as a list of datafiles, eg: "goodnes.xml.gz:goodsnes.xml.gz" would look for both goodnes and goodsnes in the rombrowser home folder

ulxmlrpcpp is a library to call methods on a remote server. ulxmlrpcpps main goal is to be as easy to use as possible but be fully compliant. It is object oriented and written in C++.
ulxmlrpcpp is a library to perform calls via XML-RPC in an object oriented approach implemented in C++. It is intended to have simple interfaces and to be easy to learn. But it shall still be fully compliant to the standards and safe in its use.
Unlike other implementations is does not insist on HTTP for transportation but might also accept other ways. For example a simple serial line with a user defined protocol.
This library uses expat as xml parser. In the unlikely case that you dont have it on your system download it from http://expat.sourceforge.net.
The following files are useful to learn more about this library:
- contrib/*
Contributed demos or other useful stuff
- ulxmlrpcpp/tests/*
Validators and test applications. Intended mainly for visual checking.
For the expected output see the according *.out.
val1_[server|client] are most important since they check most of the
functionality several thousand times.
secure_[server|client] demonstrates an approach to send and receive secure calls.
But dont take the encryption algorithm to serious, it is just to show how to do it
basically :-) Replace it by your favourite encryption algorithm.
mt_[server|client] does all the processing in parallel using threads.
- ulxmlrpcpp/apps/*
More or less useful applications in the real world
- ulxmlrpcpp/docs/en/index.html
The handbook with an introduction.
- ulxmlrpcpp/docs/api/html/index.html
The api docs. They are not part of the source distribution. Either download
them from the same place or generate yourself if you have doxygen installed.
Just type "make apidoc" in the the source directory.
In ulxr_config.h/ulxr_config-bcb5.h/ulxr_config-msvc.h/... there are some #defines that might be useful on non-autoconf systems or when you need to set up some things manually after running "configure".
There is also a directory for Borland BCB5 or M$VC++ users with project files. See "bcb5" resp. msvc and its subdirectories with the READMEs.
BCB5 users will want to turn off CodeGuard to increase the speed after they have verified that everything is working correctly with their applications.
ulxmlrpcpp is known to run fine on Linux, OpenBSD and Solaris, Windoze ports are working but not very reliably (BCB5 is ok from my point of view).
Enhancements:
- This release contains several fixes regarding SSL, timeout handling, and code generation.
- There are now more possibilities to create client and server code from sources as well as from introspection.
- The documentation contains examples on how to use the generated files.