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

List:       kde-panel-devel
Subject:    Re: [Panel-devel] Connection of Sensor and Meter
From:       Vinay Khaitan <vkhaitan () gmail ! com>
Date:       2005-09-19 12:15:20
Message-ID: 56c534770509190515708a91dc () mail ! gmail ! com
[Download RAW message or body]

[Attachment #2 (multipart/alternative)]


First thing, the problem is about synchronisation of meters, which uses same 
sensor. It is not possible when using asynchronous update of meters data by 
sensors. And we need asynchronous updates for singleton pattern. So that we 
can support different refresh rate for meters.

We need singleton pattern, because we want to minimise resource uses.
Imagine a scenario, where there are 4 karambas lying with 4 
cpusensors(cpusensor is just an example). All of them updates at 2000 ms 
interval. so within 2 second there would be 4 updates, whereas we could do 
with single update. That's why we need asynchronous update of meter data.
this scenario is possible in cases , where suppose a karamba is lying with 
graph-cpu at bottom of desktop, the other karamba is at the top of desktop 
with bar meter-cpu sensor. and so on.and we want in the future to make 
karambas split by dragging. So singleton patter and asynchronous update is 
inevitable for scaling in future. 

I find meter connection the best thing. If we think from OO viewpoint, you 
want that you require synchro between two meters, which implies that there 
should be made a connection between meters. 


Don't you think, that if you need to workaround a problem with your design,
> it's better changing your design and not introducing strange things?


All the designs has some plus and minus points. We should take that design, 
which is the most suitable.
I differ from the word "strange". in qt world, where signal-signal 
connection is possible, this is normal.

You say it's an easy solution, but I think it's bad since it's a solution
> ad-hoc for a problem you have with your design.

it's not ad-hoc. I find it nicer even in the case, when you dont need them.

If I wouldn't know anything
> about that, I couldn't understand why is needed interconnecting meters. 


That's why I would like to know the viewpoint of other developers.
Please, from next mail onwards, be kinder to me :))

cheers, 
Vinay Khaitan

[Attachment #5 (text/html)]

First thing, the problem is about synchronisation of meters, which uses
same sensor. It is not possible when using asynchronous update of
meters data by sensors. And we need asynchronous updates for singleton
pattern. So that we can support different refresh rate for meters.<br>
<br>
We need singleton pattern, because we want to minimise resource uses.<br>
Imagine a scenario, where there are 4 karambas lying with 4
cpusensors(cpusensor is just an example). All of them updates at 2000
ms interval. so within 2 second there would be 4 updates, whereas we
could do with single update. That's why we need asynchronous update of
meter data.<br>
this scenario is possible in cases , where suppose a karamba is lying
with graph-cpu at bottom of desktop, the other karamba is at the top of
desktop with bar meter-cpu sensor. and so on.and we want in the future
to make karambas split by dragging. So singleton patter and
asynchronous update is inevitable for scaling in future. <br>
<br>
I find meter connection the best thing. If we think from OO viewpoint,
you want that you require synchro between two meters, which implies
that there should be made a connection between meters. <br><br>
<br>
<div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, \
204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Don't you think, that if you \
need to workaround a problem with your design,<br>it's better changing your design \
and not introducing strange things? </blockquote><div><br>
All the designs has some plus and minus points. We should take that design, which is \
the most suitable.<br> I differ from the word &quot;strange&quot;. in qt world, where \
signal-signal connection is possible, this is normal.<br> <br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, \
204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">You say it's an easy solution, \
but I think it's bad since it's a solution<br>ad-hoc for a problem you have with your \
design. </blockquote><div>it's not ad-hoc. I find it nicer even in the case, when you \
dont need them.<br> </div><br><blockquote class="gmail_quote" style="border-left: 1px \
solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"> If I \
wouldn't know anything<br>about that, I couldn't understand why is needed \
interconnecting meters.&nbsp; </blockquote><br><div>That's why I would like to know \
the viewpoint of other developers.<br> Please, from next mail onwards, be kinder to \
me :))<br> <br>
cheers, <br>
Vinay Khaitan<br>
</div></div><br>



_______________________________________________
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]