Free flickr add referrer into comments software for linux

An annoying thing on flickr is that you never know where people that visit your photo have found it.

Flickr: Add referrer into comments a small script that will add a small text at the end of your comment saying where you come from. If everyone starts using this script, then it will be easy to see where the people have found your photos and how they got to comment on it.

Installation:

Get Firefox
Install GreaseMonkey
restart Firefox

Click on the following icon and select Install greasemonkey - 12 kb

Usage:

the comments will be added automatically to the end of your message.

The Geo Radar released by .CK reminded me of an idea I had had a while ago and provided me with the tools to implement it quickly.

This greasemonkey is a simpler version of the radar that displays the 8 closest photos to the actual one in the directions: N, NE, E, SE, S, SW, W, NW.

Flickr Photo Compass is a simple tool to browse photos of some place. By clicking on the direction icons, you can move around and find other photos.

Pod::InComments is a Perl extension for extracting POD documentation from comments in config file.

SYNOPSIS

use Pod::InComments;
my $podparser = Pod::InComments->new( comment => ; );
$podparser->ParseFile( $my_config_file );
$podparser->Pod2Hash();

my $helptext = $podparser->Pod4Section( $section , $key );

This module was written to solve the problem of describing numerous parameters in a config file. When you add comments to the config file, it becomes a mess quickly. And no-one will take the time to properly read them. You can not add POD directly. So..... here is Pod::InComments.

It was developed when using Config::IniFiles format, so lets take that as the basis. The Config::IniFiles module lets you use config files in the form of the popular windows ini file. That is, they look like

[section]
param1=some value
param2 = another value
param3=20.00

; this is a comment
[operating system]
preferred=Linux
using=Windows XP Pro

METHODS

new( comment => # )

Constructor of the class. Specify the comment character(s) used in the config file. Defaults to ;. You can use whatever you like here. So #### is valid as well, but requires more typing in the config.

ParseFile( $config_file )

Parses the $config_file and extracts all the comment lines. The comment character(s) are stripped of each line. It returns a string with all the POD.

Pod2Hash()

After parsing a config file, you will need to call this function to convert the POD into a hash. The keys of the hash are the head1 titles. If head2 elements are present, they will be subkeys of the hash.

Pod4Section( $section, $param )

Returns the POD belonging to the $section, or to $param of $section.

E.g., when your config file looks like:

;=head1 cpu
;
;Specifies cpu settings for normal boxes
;note that these will override factory settings!
;
;=head2 maxload
;
;The maxload setting gives an upperbound on how hard
;the CPU can be pushed.

[cpu]
maxload=4.0

then doing:

my $pod = $podparser->Pod4Section( cpu, maxload );

will give you:

The maxload setting gives an upperbound on how hard the CPU can be pushed.

SavePod( $file )

Saves the extracted pod to the $file. If you omit a file name, it will append .pod to the config file you parsed and saves to that file.

GetPod()

Returns the entire POD formatted in text.

DisplayPod()

Prints the entire extracted POD documentation to STDOUT.

Smart::Comments are comments that do more than just sit there.

SYNOPSIS

use Smart::Comments;

my $var = suspect_value();

### $var

### got: $var

### Now computing value...

# and when looping:

for my $big_num (@big_nums) { ### Factoring... done
factor($big_num);
}

while ($error > $tolerance) { ### Refining---> done
refine_approximation()
}

for (my $i=0; $i<<less