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

List:       kde-devel
Subject:    Using Solid
From:       David Hubner <hubnerd () ntlworld ! com>
Date:       2009-10-21 18:10:35
Message-ID: 4ADF4E9B.7000403 () ntlworld ! com
[Download RAW message or body]

Hi,

After programming in Solid for a while, i would just like to add my two 
cents to the API. Solid is great to use but i would like to make a few 
questions, recommendations + wishes :)

Wishes:

1. It would be nice if there was a Solid::Computer class with 
information about the motherboard etc etc. Example the HAL "Computer" 
object.

2. It would be extra nice if there was a used property as well as a size 
property in StorageVolume. I don't know if this is possible as HAL does 
not have this either. Probably out of the scope of a hardware framework.

3. Would be nice if it was possible to check connected status on each 
NetworkInterface rather than global, or the Solid::Networking:Notifier 
statusChanged function to say which NetworkInterface caused the status 
change.

3. It would nice if fetching devices with the type 
Solid::DeviceInterface::Unknown would not show devices already in other 
categories, or maybe, have a new enum type for that kind of function.

Recommendations:

1. Most classes have a slight description in the method name when it 
comes to the method type, for example, fsType in StorageVolume but some 
classes just have this methods listed as type, example, Battery + Button 
classes. Its kind of inconsistent.

Questions:

1. What is the direction of Solid? Is it aiming to become a complete 
device framework to interact with/show all devices in the users 
computer, or, just devices that show some kind of status. For example 
will it show system devices like PCI-PCI buses or motherboard resources?

Thanks
David Hubner
 
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
[prev in list] [next in list] [prev in thread] [next in thread]