<br><br><div class="gmail_quote">2008/1/28 Aaron J. Seigo <<a href="mailto:aseigo@kde.org">aseigo@kde.org</a>>:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
On Monday 28 January 2008, Alexis Ménard wrote:<br><br>- list all devices plugged in when the applet is started ;)</blockquote><div><br>Ok i have to update the engine in this case. <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br><div class="Ih2E3d"><br>> -Add the possibility to unmount the device (with right mouse i think for<br>> the taskbar view and with an icon in the desktop view).<br><br></div>making such a radical split between views is going to lead you into problems<br>
as it creates assumptions in your code about how the libplasma using<br>application is behaving. you should try and avoid this if at all possible.<br><br>oh, and right clicks are Evil(tm)</blockquote><div><br>;) so an icon...<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;"><br><div class="Ih2E3d"><br>> -Grouping items by type (usb,CD...).<br><br></div>
cool<br><div class="Ih2E3d"><br>> -Improve Ui config with something more sexy.<br>> -Slipt code in two different classes (desktop view and taksbar view).<br><br></div>what would the split end up with?<br><div class="Ih2E3d">
</div></blockquote><div><br>Actually i have all in one class with differents functions like performUpdateInSysTray and performUpdateInDesktop. The code is different in these two cases : one use a model to display information in a QListView (using Dialog class in Plasma) and other deal with plasma API. My idea was to create just two classes (ie NotifierDesktop and NotifierContainment) and in the main class applet, i just create the good object depending on where is the applet. It was just to simplify...<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;"><div class="Ih2E3d"><br>> The big missing part is a config dialog to set the application associated<br>
> to a kind device. Perhaps we should create a specific dialog in system<br>> settings?<br><br></div>it's not only which application, it's general actions. for instance, when i<br>plug a new usb headset i can select "set as my default sound device". a<br>
configuration dialog would probably be handy in this case.<br><div class="Ih2E3d"><br>> The main problem with this dialog is how we can bring to user the power of<br>> predicates in Solid ?<br><br></div>perhaps start with the use cases. what exactly do you want to allow the user<br>
to do, using actual examples?<br><font color="#888888"></font></blockquote><div><br>Yes, perhaps we can provide a set of standard predicates which filters main kind of devices and provides something to allow user link an application or an action.<br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><font color="#888888"><br>--<br>Aaron J. Seigo<br>humru othro a kohnu se<br>GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43<br>
<br>KDE core developer sponsored by Trolltech<br></font><br>_______________________________________________<br>Panel-devel mailing list<br><a href="mailto:Panel-devel@kde.org">Panel-devel@kde.org</a><br><a href="https://mail.kde.org/mailman/listinfo/panel-devel" target="_blank">https://mail.kde.org/mailman/listinfo/panel-devel</a><br>
<br></blockquote></div><br>