Beefy Boxes and Bandwidth Generously Provided by pair Networks
P is for Practical
 
PerlMonks  

comment on

( [id://3333]=superdoc: print w/replies, xml ) Need Help??
Ideally, it depends on how OO you want to be.
A good genalized version would be something like:

Entity (approximately a row in a database)
EntityHTML (HTML display class for Entities)

Person ISA Entity
PersonHTML ISA Person, ISA EntityHTML

In javaspeak, PersonHTML ISA Person, Implements EntityHTML.

Since your talking about RL, Person->new() should take a database ID, or an $Entity::NEWOB (a constant), or be created in Person::new_by_name('bob').

You'll want some way to flush the object back to the database, probably save(). But since (again in RL) you are talking about stuff in a database skip the save() and instead use add() and update() (or your synonyms). Trust me, it saves alot of confusion when reading code versus making save() 'smart'. Low-level things should be dumb, high level things should be smart. Don't forget delete()

A PersonHTML object just knows how to display a person - and nothing about the database - as an HTML form, or as a row on a list. Depending on your data you can throw in EntityPDF or EntityPNG as well. EntityPerl might be a neat one, but you probably just mean serialize().

There is lots of other stuff to think about, Factory classes and such, but tackle those when you need them :)

-jackdied


In reply to Re: OO Application Design by jackdied
in thread OO Application Design by Nomis52

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post; it's "PerlMonks-approved HTML":



  • 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.
Log In?
Username:
Password:

What's my password?
Create A New User
Domain Nodelet?
Chatterbox?
and the web crawler heard nothing...

How do I use this?Last hourOther CB clients
Other Users?
Others sharing their wisdom with the Monastery: (5)
As of 2024-04-25 14:06 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?

    No recent polls found