WebElement and WebComponent

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

WebElement and WebComponent

Nicolas Petton
For now, WebComponent is an empty subclass of WebElement.
To differentiate them, we should probably add some useful methods to
WebComponent.

My idea is to override WebComponent class>>initialize to call a #build
method, then add an empty #build method. That way the trick (often used)

printHTMLPageOn: aStream forSession: aSession

        self build.
        ^super printHTMLPageOn: aStream forSession: aSession.

Won't be necessary.

What do you think ?

Nico
--
Nicolas Petton
http://nico.bioskop.fr
            ___
          ooooooo
         OOOOOOOOO
        |Smalltalk|
         OOOOOOOOO
          ooooooo
           \   /
            [|]
--------------------------------
Ma clé PGP est disponible ici :
http://nico.bioskop.fr/pgp-key.html

_______________________________________________
Aida mailing list
[hidden email]
http://lists.aidaweb.si/mailman/listinfo/aida

signature.asc (196 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: WebElement and WebComponent

Rob Rothwell
#build makes sense to me, as in "build the component out of it's constituent WebElements."

Is that what you were thinking?

Rob

On Fri, Apr 18, 2008 at 5:18 PM, Nicolas Petton <[hidden email]> wrote:
For now, WebComponent is an empty subclass of WebElement.
To differentiate them, we should probably add some useful methods to
WebComponent.

My idea is to override WebComponent class>>initialize to call a #build
method, then add an empty #build method. That way the trick (often used)

printHTMLPageOn: aStream forSession: aSession

       self build.
       ^super printHTMLPageOn: aStream forSession: aSession.

Won't be necessary.

What do you think ?

Nico
--
Nicolas Petton
http://nico.bioskop.fr
           ___
         ooooooo
        OOOOOOOOO
       |Smalltalk|
        OOOOOOOOO
         ooooooo
          \   /
           [|]
--------------------------------
Ma clé PGP est disponible ici :
http://nico.bioskop.fr/pgp-key.html

_______________________________________________
Aida mailing list
[hidden email]
http://lists.aidaweb.si/mailman/listinfo/aida



_______________________________________________
Aida mailing list
[hidden email]
http://lists.aidaweb.si/mailman/listinfo/aida
Reply | Threaded
Open this post in threaded view
|

Re: WebElement and WebComponent

Janko Mivšek
Rob Rothwell wrote:
> #build makes sense to me, as in "build the component out of it's
> constituent WebElements."
>
> Is that what you were thinking?

That's an intentions of #build method, yes. It is meant to build an
object tree of a component, just as #viewMain do for a whole page.

Component can be namely built once only and then is "cached", or every
time a page with that component is shown, or when Ajax refresh request
comes. All three ways use the same #build method.

Janko


>
> Rob
>
> On Fri, Apr 18, 2008 at 5:18 PM, Nicolas Petton
> <[hidden email] <mailto:[hidden email]>> wrote:
>
>     For now, WebComponent is an empty subclass of WebElement.
>     To differentiate them, we should probably add some useful methods to
>     WebComponent.
>
>     My idea is to override WebComponent class>>initialize to call a #build
>     method, then add an empty #build method. That way the trick (often used)
>
>     printHTMLPageOn: aStream forSession: aSession
>
>            self build.
>            ^super printHTMLPageOn: aStream forSession: aSession.
>
>     Won't be necessary.
>
>     What do you think ?
>
>     Nico
>     --
>     Nicolas Petton
>     http://nico.bioskop.fr
>                ___
>              ooooooo
>             OOOOOOOOO
>            |Smalltalk|
>             OOOOOOOOO
>              ooooooo
>               \   /
>                [|]
>     --------------------------------
>     Ma clé PGP est disponible ici :
>     http://nico.bioskop.fr/pgp-key.html
>
>     _______________________________________________
>     Aida mailing list
>     [hidden email] <mailto:[hidden email]>
>     http://lists.aidaweb.si/mailman/listinfo/aida
>
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Aida mailing list
> [hidden email]
> http://lists.aidaweb.si/mailman/listinfo/aida

--
Janko Mivšek
AIDA/Web
Smalltalk Web Application Server
http://www.aidaweb.si
_______________________________________________
Aida mailing list
[hidden email]
http://lists.aidaweb.si/mailman/listinfo/aida
Reply | Threaded
Open this post in threaded view
|

Re: WebElement and WebComponent

Janko Mivšek
In reply to this post by Nicolas Petton
Nicolas Petton wrote:
> For now, WebComponent is an empty subclass of WebElement.
> To differentiate them, we should probably add some useful methods to
> WebComponent.
>
> My idea is to override WebComponent class>>initialize to call a #build
> method, then add an empty #build method. That way the trick (often used)

Agree. Also comment all that methods well to help implementers better
extending them. Also don't forget on Ajax registration for the #build
method in initialize.

Janko




>
> printHTMLPageOn: aStream forSession: aSession
>
> self build.
> ^super printHTMLPageOn: aStream forSession: aSession.
>
> Won't be necessary.
>
> What do you think ?
>
> Nico
>
>
> ------------------------------------------------------------------------
>
> _______________________________________________
> Aida mailing list
> [hidden email]
> http://lists.aidaweb.si/mailman/listinfo/aida

--
Janko Mivšek
AIDA/Web
Smalltalk Web Application Server
http://www.aidaweb.si
_______________________________________________
Aida mailing list
[hidden email]
http://lists.aidaweb.si/mailman/listinfo/aida