As for Ebola, I suspecting now that you mean I should rewrite that as a routine for the img alt attribute substitution.
I'll try to explain about Ebola, I'll try be clear.
In Re^3: Trying to Insert Alt Tags Programmatically you posted this (I've run it through perltidy )
Every time you write repetitive stuff like that
$newtitleh1 ...
$newtitleastexth1 ...
$newtitleastexth1clipped ...
$html->push_content ...
...
$newtitleh2 ...
$newtitleastexth2 ...
$newtitleastexth2clipped ...
$html->push_content ...
you should turn it into a subroutine, which I did, and I called it Ebola (surely you noticed substr/push_content).
To learn to Ebola you would write a program like this (Ebola.pl)
#!/usr/bin/perl --
# Ebola.pl
use strict;
use warnings;
use HTML::Tree;
Main( @ARGV );
exit( 0 );
sub Main {
my $t = HTML::TreeBuilder->new_from_content(join'','<h4>',0..9,'<h
+4>');
my $f = HTML::TreeBuilder->new_from_content('<title>f</title>');
my $B = $f->look_down( qw' _tag body ' );
print $t->as_HTML, "\n\n";
print '-'x33, "\n\n";
if ( Ebola( $B, 5, eval{ $t->look_down(qw'_tag h1')->as_text } ) )
+ {
print "Using h1\n";
} elsif ( Ebola( $B, 5, eval{ $t->look_down(qw'_tag h2')->as_text
+} ) ) {
print "Using h2\n";
} elsif ( Ebola( $B, 5, eval{ $t->look_down(qw'_tag h3')->as_text
+} ) ) {
print "Using h3\n";
} elsif ( Ebola( $B, 5, eval{ $t->look_down(qw'_tag h4')->as_text
+} ) ) {
print "Using h4\n\n";
}
print '-' x 33, "\n\n";
print $f->as_HTML, "\n\n";
} ## end sub Main
sub Ebola {
my ( $html, $clip, $text ) = @_;
if ( defined $text and length $text ) {
$text = substr $text, 0, $clip;
$html->push_content($text);
}
} ## end sub Ebola
__END__
And the output of this program is
<html><head></head><body><h4>0123456789</h4><h4></h4></body></html>
---------------------------------
Using h4
---------------------------------
<html><head><title>f</title></head><body>01234</body></html>
This is how you learn to Ebola, by writing a small program (Ebola.pl) to explore how HTML::TreeBuilder/HTML::Element objects behave.
For the next step in the process, you write a program called Ebola.t
sub Main {
AsdfQwerty( '<h1>0123456789</h1>', '01234' );
AsdfQwerty( '<h1>0123456789</h2>', '01234' );
AsdfQwerty( '<h3>0123456789</h3>', '01234' );
AsdfQwerty( '<h4>0123456789</h4>', '01234' );
AsdfQwerty( '<h5>0123456789</h5>', '01234' );
AsdfQwerty( '<p>0123456789</p>', '01234' );
}
Where AsdfQwerty(), like Ebola.pl, puts Ebola() through its paces.
That is, AsdfQwerty(), tests Ebola(), by feeding Ebola() various inputs, and checking that the output Ebola() produces meets your expectations.
Problems are easier to spot and fix in very small programs.
Forget about your big task (SEO Fixer) for the moment,
write 5 or 10 of these little programs, each dealing with a single small task, a single function (Ebola).
But don't call it Ebola, Ebola isn't descriptive, it doesn't explain or even hint at what the subroutine is supposed to accomplish or demonstrate/teach you.
Do you follow what I'm saying?
The reason I chose names like Ebola is because you're supposed to change them. Learning to program is hard, there is a lot of information you have to juggle inside your head, and only sticks if you write/rewrite code yourself.
You still have part of my demo prog in this post i'm replying to
local $\ = $/;
print $_->as_HTML
for $tree->look_down( '_tag', 'img ',
sub { not defined $_[0]->attr('alt') } );
print '---';
print $_->as_HTML
for $tree->look_down( qw' _tag img ',
sub { not length $_[0]->attr('alt') } );
print '---';
$_->attr( alt => MAlt($_) )
for $tree->look_down( qw' _tag img ',
sub { not length $_[0]->attr('alt') } );
print $_->as_HTML for $tree->look_down(qw' _tag img ');
print $tree->as_HTML;
$tree = $tree->delete;
This code was supposed to demonstrate/teach how look_down works, and how to modify any tags you might find, it wasn't meant for direct inclusion in your program, after all, I'm not writing your program :)
Its like learning to juggle
- First you start with one ball
- and then practice with two balls
- and two in one hand
- then three balls.
- Next you start with one bowling pin
- and then two bowling pins
- and then two bowling pins in one hand
- and then three bowling pins
- Next you start with one ball and one bowling pin
- and then one ball and one bowling pin in one hand
- and then two balls and one bowling pin
- Next you start with one two bowling pin and one ball
- And then you start with one knife
- and then two knives
- then two knives in one hand
- and then three knives
- Again you start with one ball and one knife
- then one ball and one knife in one hand
- then one knife and two balls
- Eventually you work your way up to three chainsaws, two bowling pins, two knives, and four tennis balls
In this analogy, each juggling session is a new small program you've written.
The more of them you write, the easier they get to write, the easier they get to combine, and if you forget how something works, you've got tons of little programs to show you.
I know this must seem overwhelming (hey, I'm typing my fingers bloody here :D) so here is the last surprise, AsdfQwerty is better written using Test::More, like http://cpansearch.perl.org/src/PETEK/HTML-Tree-3.23/t/attributes.t
But it isn't necessary, its just motorized equipment, chainsaw versus handsaw.
Good luck. | 