comment on

"But it seems daft to [force] you to copy the data to another instance"

I should have placed $self inside base instead, and allowed the subclasses to format it in some way - but i was trying to keep it simple. The idea is that the base clase contains the data in a Perl data structure and the subclasses are responsible for flitering that data structure into a particular format. Let me try again:

package Factory;

sub create {
   my $class = shift;
   my $obj = 'Base::' . shift;
   return $obj->new();
}

package Base;

sub new {
   my $class = shift;
   my $self = { thing => 'foo' };
   return bless $self,$class;
}

package Base::Bold;
use base 'Base';

sub output {
   my $self = shift;
   return '<b>' . $self->{thing} . '</b>';
}

package Base::Italic;
use base 'Base';

sub output {
   my $self = shift;
   return '<i>' . $self->{thing} . '</i>';
}

package main;

my @things = (
   Factory->create('Bold'),
   Factory->create('Italic'),
);

print $_->output,$/ for @things;
[download]

And an HTML resume is different than a PDF resume: HTML and PDF are adjectives to the noun resume - an adjective qualifies, distinquishes, and specifies - hence, an HTML resume is one kind of resume (Resume::HTML), and a PDF resume is another kind (Resume::PDF). I you don't like this, then how about naming them Resume::AsHTML and Resume::AsPDF instead? ;)

jeffa

L-LL-L--L-LL-L--L-LL-L--
-R--R-RR-R--R-RR-R--R-RR
B--B--B--B--B--B--B--B--
H---H---H---H---H---H---
(the triplet paradiddle with high-hat)

In reply to (jeffa) 3Re: XML Resume Module design by jeffa
in thread XML Resume Module design by rattusillegitimus

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


Syntactic Confectionery Delight
	PerlMonks