Thanks for your help Cris!

I'm not familiar with the concept of Gadgets, I read a doc in the
2.0documentation but not really sure of what they are.

The idea of components to be separable is to have, Widgets and Signals
separated.

Widgets should be used as always, but with the addition  of  some setup
definitions. Such as slot ( position inside the final template ), set of
signals it can receive, and everything related with their setup inside the
system.

The idea is quiet simple, One widget sends an action to other ( others )
trough signals.

Signals match the actions with they corresponding data, and sends this to
the other widget to display it.
They code all necessary steps to get data ( i.e database ) and to store
data.

(i.e. A click on a Navigation bar element, sends the corresponding id to the
Signal, then a method is called inside the signal, the data is gattered (
i.e from a database table ) and then this data is sent to a menu bar to show
the corresponding elements. )


!!!!
The point is to provide an interface to setup wich widgets should be loaded,
the signals it sends, the data it carry and  the target widgets.
And a good set of Signals ready to use.
!!!!

All widgets are Childs of the main "Site" widget. It should deliver the
template automatically just taking a look at the slot attribut of all
contained widgets ( it's pretty easy to do, but i think this can be really
useful ). With this feature, we are packaging all into one Big Widget, and
the only thing we need to pass to the template to render (i.e:
welcome.html) is Site instance.

this is just a silly example..

if we have:

slot ="site.header.logo" ( logo widget )
slot ="site.header.logo.title" ( title widget )

then the Site template should be:

<div id="site">
       <div id="header">
              <div id="logo">
                     ${logo.display()}
                           <div id="title">
                                  ${title.display()}
                           </div>
              </div>
       </div>
</div>

And we got an structural template for ccs positioning.


The real job of all this, is to provide a big set of signals ready to use,
and make a good aproach on what is needed for content managment.

There are a lot of things I'm thinking on, and it's very difficult to
explain some concepts for me; First because I'm not an expert and then
because of my natural Spanish spoken language.

This is an idea, and i would really like to make something like this.
Eventually i can re-think the whole idea if necessary, it's looks pretty
handy for small sites ( portals alike ).

It would be good some pointing directions on Gadgets, and maybe this idea
can evolve to something better.

Hope this help to clarify my ideas !

Thaks for your time !

--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups 
"TurboGears Trunk" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at 
http://groups.google.com/group/turbogears-trunk?hl=en
-~----------~----~----~----~------~----~------~--~---

Reply via email to