If you have RKRM: Libraries (there are HTML and AmigaGuide versions of the RKRMS on the developer CD) it contains information on how to write the dispatcher as well as an example of a gadget class.
The methods a gadget needs to implement: OM_NEW OM_DISPOSE OM_GET (only if it has gettable attributes of its own) OM_UPDATE OM_SET GM_DOMAIN GM_LAYOUT GM_RENDER GM_HITTEST GM_GOACTIVE GM_HANDLEINPUT GM_GOINACTIVE
Unsupported methods should simply be referred to the class's superclass (for a gadget this is normally "gadgetclass").
Well please do. However if no feedback is received i'll assume that it won't be done and repost this thread ;) (I don't like when things end up in limbo)
Openamiga.org isn't a bounty page btw. The link at the start of this thread links to a project page. Openamiga.org isn't to be confused by amigabounty or similar.
I'm not sure if you are aware, but that diagram you posted is possible to do right now with the current listbrowser gadget. Simply create a label.image object with the required text and pictures in it, and supply that to the listbrowser as the node contents...
I'm not going to reiterate the whole project description here.
Please reread it and tell me if that is still your opinion. The diagram above does not describe the whole project, only the layout of a single cell.
Afaik the listbrowser gadget does not have a flow layout mode. Without that basic requirement it's not of much use for this purpose.
And on top of that the whole point of the project is that you are able to switch between the two modes (either by reusing the list between two different gadgets or just setting a mode switch in the gadget class) without doing tons of manual data rearrangement and layout management.