Free who wants software for linux

Search-Engine-Optimized project is a free online resource for anyone who wants to step up their search engine optimization strategies to the next gear.
The web is a constantly changing place, expecially search engines, but there are numerous search engine optimization strategies that are consistant across all the major search engines, and are probably going to be very useful for a long time to come.
Read on to learn what they are and how to employ them in the development of your web site.
Main features:
SEO Rank Checker is a nice little script for checking your keyword status for a few select keywords without going through the trouble of checking the search engine result pages yourself.
- Automated fetching of the top 100 results for MSN, Yahoo and Google to check for your site.
- Easy to read, compare and print output
- Installation is super easy, just upload to your server and youre done!
- Super small script, just a few KBs of space!

libzdt is a free general library aimed at anyone who wants to use it.

Some people may wonder why we need another software library. The answer is simple: What others dont offer, were trying to provide.

This basically meaning, while some of the things included in libzdt are included in other libraries, either we think the implementation isnt perfect, or we just feel it would make a great compliment to what were trying to do which is make life easier for those who want to write software.

While libzdt does not contain any graphical user interface API, it may later (please keep in mind that libzdt is still very pliable in a GUI application depending on what it is, and what the application does).

Anyway, libzdt is just a collection of functions Ive wrote over the years, or someone else has written and Ive just picked em up (you can see the list of people to whom I owe thanks for their code in the Documentation/Authors file). libzdts primary use will be in ZerOS, the operating system myself and a few friends are designing and developing (well, Im doing the development), right now however, its primary use is in custom commercial software my company writes. This version however, is not used in any commercial software, please see further into this document for more information on libzdt itself.

Little note on our coding style, at least myself, I go by the Linux kernel coding standards (which are included in the Documentation/CodingStyle file).

Anyway, back to libzdt itself... Its being rewritten for one reason, and one simple reason only. The version of libzdt that I use myself (not to say I dont use this one, because I do) is private, closed source. Its a library written in Objective-C++ anyway, so only a few platforms can use it (MacOS X, NeXTSTEP/OpenStep are the only platforms that I know have a working ObjC++ compiler), and besides, the code is ugly looking.

To compile libzdt, all you have to do is go into the main directory, which you are no doubt in right now reading this file, and type: make. This will build both the static library and shared library files and place them in the $LIBZDT_ROOT/Objects.x86 directory. In previous versions you had to type: make depend shared static, or something of the such to build all that you can now with just the make command without any arguments. To install libzdt, you must be root (or a user who has permissions to run ldconfig) in order to complete the install process. Simply type: make install.

Hello! Thank you for donating your knowledge and time to our cause. Pariahware, Inc. is currently working on a Bible trivia game that is a cross between the TV game show "Who Wants to be a Millionaire?" and the electronic game series "You Dont Know Jack!" As one might imagine, this can be a daunting task.
That is why we are asking for your help in coming up with some GREAT Bible questions in order to make this game even more fun than we could do by ourselves! When you are finished submitting all of your questions, please e-mail the "qanda.rsd" file back to submissions@pariahware.com. By submitting the questions that you come up with, you agree to the following:
The Legal:
1. You expect no royalty fees or other payment for Pariahware, Inc. using your questions in the game.
2. Any parts of the questions you submit may be altered at will by the members of Pariahware, Inc.
3. Even though you submit a question for the game, that does not necessarily mean it will appear in the game.
4. If your name is included in your e-mail, Pariahware, Inc. has the right to add it as an acknowledgement, unless otherwise noted. You will not be paid as a result of having your name listed.
The How To:
1. Make sure that the Got Word DB Maker application and the "qanda.rsd" file are in the same folder or the program will not work.
2. Double-click the Got Word DB Maker application icon.
3. Select the radio button in the lower-left-hand corner that says "Add new question".
4. There are five text fields. The large one on the top is for the question. The other four are for potential answers. All of these need to be filled.
5. The correct answer needs to be selected by the "drop down" in the upper-right-hand corner.
6. The book of the Bible, in which the question is referencing, needs to be selected in the upper-left-hand corner.
7. Below the book selection is value (points) for the question. This needs to be selected as well.
8. When all of this has been done, the "Save New Question" button will activate. Click it to save your question.
Word of Caution:
To make changes to question that you have already entered, click the "edit existing questions" radio button.
Enhancements:
- Bug Fixes.

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.

BullDog is a powerful but lightweight firewall for heavy use systems. With many features, this firewall can be used by anyone who wants to protect his/her systems. This system allow dynamic and static rules sets for maximum protection and has several advance features.

This firewall will work for the hobbyist or a military base. Generation 7 is a complete rewrite of its predecesors and is redesigned from scratch and still evolving.

Be prepared to spend some time setting this up. If you are looking for a "quick fix", then you are on the wrong site. BullDog is NOT a quick fix, but rather one step in a complete security policy.

Its is covered by the GPL and is FREE and always will be. I encourage and welcome anyone who wants to port and/or provide ideas/code to better this software.

I would like to see this software developed into a new breed of firewall that provides the best of security with ease of use.

This software was developed on Linux v2.2.16-17 and v2.4 with 64 megs to 1 Gig of RAM and supports iptables via the ip_queue kernel module. Bulldog will NOT run on Windows systems.

image-viewer is a very simple Kommander script. But written following one of the 2-3 tutorials you can find on the net. Included in tarball you can find this guide to introduce in Kommander GUI. The site is: http://applications.linux.com/article.pl?sid=04/12/17/2033227&tid=49 and was written in 2004 by Michał Kosmulski

I know people want to use this great program..but documentations are very poor...this example helps people who wants to learn something about simple array, combobox, label and connections between signals and slots..very very important.

So, i hope the guide and the example will be usefull.

CompBio::DB is a Perl module with methods for accessing data stored according to the CompBio base schema.

SYNOPSIS

use CompBio::DB;
my $cbdb = CompBio::DB->new({host => "foo.bar.edu");

my $AR_defs = $cbdb->get_annotation([keys %seqs]);
Example code for parsing the return for a simple print:
my $AR_result = $cbdb->get_aa_seq(@id_list);
foreach my $AR_row (@$AR_result) {
next unless @$AR_row;
print join("t",@$AR_row) , "n";
} # return list

This module and the related database schemas where developed to be used with a MySQL server. Although I would certainly prefer it to be portable, that was not a priority at this time. However, I expect the manual alterations that may be necisary to use this module should be very resonable for someone sufficiently familiar with the new target database server, and I would be happy to collaborate with anyone who wants to work on this!

Most of the methods in this database fetch a type of data from a given id or list of ids. Unless otherwise stated for a specific method, only two arguments are ever used; the id or an array reference to a list of ids, and a hash reference containing any optional arguments. The request will be made against the default database defined when the CompBio::DB object was created, but most methods accept a "database" option to use a different database on the same server.
All methods that return query results return a reference to a 2D array. See the documentaion for specific methods for the order of returned fields.