Beefy Boxes and Bandwidth Generously Provided by pair Networks
XP is just a number
 
PerlMonks  

Re: HTML - sharing design and logic

by dfaure (Chaplain)
on Jul 01, 2004 at 12:59 UTC ( #371065=note: print w/replies, xml ) Need Help??


in reply to HTML - separating design and logic

I think it is never trully possible to seperate design and logic

IMHO, you should take care to differentiate applicative-logic and GUI-logic, and consider 3 abstraction layers:

  1. HTML-Template data, aka GUI elements, look-and-feel, skins, whatever you call it.
  2. GUI-logic, tiny code elements, totally dedicated to data appearance. There you'll use HTML::Template modules or equivalent to handle HTML data from above layer. Taking an OO-approach, you may define here a "widgets" hierarchy of specialized objects.
  3. Lastly, You'll have applicative-logic dedicated to manage applicative-datas and providing them to users through the help of above layer functionnalities.
+-------+ | Users | +-------+ ^ | v +------------+ +-----------+ | HTML-Datas |-->| GUI-logic | +------------+ +-----------+ ^ | v +-------------------+ | Applicative-logic | +-------------------+ ^ | v +-------+ | Datas | +-------+

Pro: Design and logic are separated.

Cons: You'll have to stricly follow the rules of responsability separation when developping the differents layers. Anyway, you'll have a bit more code to produce and support all caveats involvde (more code => more bugs => more tests required => less time).

This kind of slicing gives you the basements to build applications decribed as 'Model-View-Controller' in Design-Pattern litteracy.

Updated:corrected some typos and added schematic.

____
HTH, Dominique
My two favorites:
If the only tool you have is a hammer, you will see every problem as a nail. --Abraham Maslow
Bien faire, et le faire savoir...

Log In?
Username:
Password:

What's my password?
Create A New User
Node Status?
node history
Node Type: note [id://371065]
help
Chatterbox?
[dazz]: Hi I have grabbed an image from an IP camera with Image::Grab. I then want to pass that image object to a subroutine where I do a read-only test on the image with Image:Magick.
[dazz]: How do I pass an image object to a subroutine and then apply a Image::Magick a read-only method to the image object???
[dazz]: Also, I want to use Image::Magick to annotate and composite (not in a sub). How do I take a Image::Grab object and apply Image::Magick write methods to it??

How do I use this? | Other CB clients
Other Users?
Others taking refuge in the Monastery: (7)
As of 2017-03-27 07:38 GMT
Sections?
Information?
Find Nodes?
Leftovers?
    Voting Booth?
    Should Pluto Get Its Planethood Back?



    Results (317 votes). Check out past polls.