<br><br>
<div><span class="gmail_quote">On 9/11/05, <b class="gmail_sendername">Aaron J. Seigo</b> <<a href="mailto:aseigo@kde.org">aseigo@kde.org</a>> wrote:</span>
<blockquote class="gmail_quote" style="PADDING-LEFT: 1ex; MARGIN: 0px 0px 0px 0.8ex; BORDER-LEFT: #ccc 1px solid">hell if you _really_ wanted to you could make Meter an interface only and<br>require multiple inheritance (
e.g. MyMeter : public QWidget, public<br>Plasma:Meter) at which point a sensor could be used with "anything". granted<br>MI isn't the prettiest thing, but it may be just what the doc ordered here.<br>my primary concern is scripting languages that don't allow for MI, such as
<br>Ruby. though Ruby could probably use mix ins instead to include the MyMeter<br>interface. still, i'd be a bit concerned about requiring some sort of<br>multiple inheritence / implementation scheme and not bother.</blockquote>
<div> </div>
<div>I think using signals and slot is a much better design than using MI here. MI will cause a number of problems, particularly for any bindings that pass stuff around in a void *.</div>
<div> </div>
<div>Rich.</div>
<div> </div><br> </div>