Hi, On Fri, Nov 02, 2007 at 02:32:49PM +0000, place wrote:
Now I have to send a linkblock ptr around.
Where, what are you working on? Please give me more background.
The right-click menus. I am giving them the linkblock ptr via a_UIcmd_*_popup so that they can call Html_load_images (well, a_Html_load_images now, by way of a_UIcmd_load_images -- if that's the right way to route it.)
After some study and a reimplentation of plain.cc with classes (getting rid of its linkblock and hooking a callback for memory handling), it looks simpler and better. It looks like the same may be done with html.cc. Please check out the CVS. Comments are welcomed. Although the patch is already in CVS, I'm attaching the dw2 patch text so Sebastian can review it easily when he has time. -- Cheers Jorge.-
Jorge wrote:
After some study and a reimplentation of plain.cc with classes (getting rid of its linkblock and hooking a callback for memory handling), it looks simpler and better. It looks like the same may be done with html.cc.
I was just wondering how you weigh the options of adding a callback vs. adding a signal. I had experimented with a destroy signal in my tree recently. It seemed more consistent to me, although I suspect the various child widgets were wasting cycles on signal emission code when they didn't have any receivers...
Hi, On Sat, Nov 03, 2007 at 11:18:36PM +0000, place wrote:
Jorge wrote:
After some study and a reimplentation of plain.cc with classes (getting rid of its linkblock and hooking a callback for memory handling), it looks simpler and better. It looks like the same may be done with html.cc.
I was just wondering how you weigh the options of adding a callback vs. adding a signal. I had experimented with a destroy signal in my tree recently. It seemed more consistent to me, although I suspect the various child widgets were wasting cycles on signal emission code when they didn't have any receivers...
I'd say that for me, the key is simplicity, and elegance. In a sense, accurately captured by this quote: "The key to performance is elegance, not batalions of special cases" -- Jon Bentley and Doug McIlroy In the case of Dillo, I've seen several times the simplicity pay off. When code gets simpler, debugging and improving accelerates. With complexity it stagnates. Elegance helps to keep the design simple and flexible. Having flexibilty in the design, helps to tackle unforeseen problems at the design level, without workarounds, reducing complexity and special cases. -- Cheers Jorge.-
participants (2)
-
jcid＠dillo.org -
place＠gobigwest.com