Break it up into pieces.
- You can write one module that controls access to the database. This should have add, delete, update, and list methods.
- The quotes themselves could be objects with methods to provide the quote itself, its author, etc.
- The web interface could be modularized depending on how you intend to implement it and what webserver and application framework you're working with.
Doing the database as a module allows you to easily substitute another implementation that saves to text files, a different database, db files, or whatever.
Doing the quotes as an object allows you to write a command line utility that accesses the quotes.
Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
Read Where should I post X? if you're not absolutely sure you're posting in the right place.
Please read these before you post! —
Posts may use any of the Perl Monks Approved HTML tags:
- a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
Outside of code tags, you may need to use entities for some characters:
| |
For: |
|
Use: |
| & | | & |
| < | | < |
| > | | > |
| [ | | [ |
| ] | | ] |
Link using PerlMonks shortcuts! What shortcuts can I use for linking?
See Writeup Formatting Tips and other pages linked from there for more info.
|
|
