[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kde-panel-devel
Subject:    Re: [Panel-devel] Sensors and Meters in SK
From:       Richard Moore <richmoore44 () gmail ! com>
Date:       2005-09-11 11:14:02
Message-ID: 5491a51505091104147ccb0a8e () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


On 9/11/05, Aaron J. Seigo <aseigo@kde.org> wrote: 
> 
> hell if you _really_ wanted to you could make Meter an interface only and
> require multiple inheritance (e.g. MyMeter : public QWidget, public
> Plasma:Meter) at which point a sensor could be used with "anything". 
> granted
> MI isn't the prettiest thing, but it may be just what the doc ordered 
> here.
> my primary concern is scripting languages that don't allow for MI, such as
> Ruby. though Ruby could probably use mix ins instead to include the 
> MyMeter
> interface. still, i'd be a bit concerned about requiring some sort of
> multiple inheritence / implementation scheme and not bother.

 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 *.
 Rich.

[Attachment #5 (text/html)]

<br><br>
<div><span class="gmail_quote">On 9/11/05, <b class="gmail_sendername">Aaron J. Seigo</b> &lt;<a \
href="mailto:aseigo@kde.org">aseigo@kde.org</a>&gt; 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 &quot;anything&quot;. \
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>&nbsp;</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>&nbsp;</div>
<div>Rich.</div>
<div>&nbsp;</div><br>&nbsp;</div>



_______________________________________________
Panel-devel mailing list
Panel-devel@kde.org
https://mail.kde.org/mailman/listinfo/panel-devel


[prev in list] [next in list] [prev in thread] [next in thread]