[Development] Proposal: reorganization of QtSystems module, since Qt5.x

Denis Shienkov scapig2 at yandex.ru
Thu Sep 13 15:54:27 CEST 2012


> Alberto Mardegan wrote:

> BTW, one small thing you might want to change in your proposed
> implementation is switching from "device type" to "capability". It's
> sometimes very difficult to say what kind of device something is, but
> you can always say that it's capable of this and that (for example, a
> graphics card which provides HDMI audio).

Why? After all, if the video card has HDMI audio, then the OS will be two entities: 
one - the video card, 
other - audio device with capability HDMI. 

So I disagree with you.

The more so that the device OS divided into separate classes. Here is information 
on these classes of devices and need to displayed. I.e. divide the devices by classes, 
but not types, like:

enum ClassOfDevice {  ....  }

For example, 
on Windows: http://msdn.microsoft.com/en-us/library/windows/hardware/ff553426%28v=vs.85%29.aspx
on Linux, like: http://www.mjmwired.net/kernel/Documentation/driver-model/class.txt
on MacOSX, like: similary

Regards,
Denis






13.09.2012, 16:47, "Alberto Mardegan" <mardy at users.sourceforge.net>:
> On 09/13/2012 01:27 PM, Denis Shienkov wrote:
>
>>  For a start here can add only the basic types of devices (already implemented),
>>  and then on future can add new supported device types (step-by-step).
>>
>>  This is just pseudocode, I know that it contains errors. I just proposed the idea,
>>  so please do not judge strictly.
>
> Your API seems ideal for someone who has to implement a device manager
> application; however, as an application developer I'd expect that if I
> have to use a printer, mouse, or access the network, I would find all
> the needed functionality in the modules that handle these classes.
>
> I would expect to need to use QtSystems only if I need to access some
> very low-level data about the hardware.
>
> BTW, one small thing you might want to change in your proposed
> implementation is switching from "device type" to "capability". It's
> sometimes very difficult to say what kind of device something is, but
> you can always say that it's capable of this and that (for example, a
> graphics card which provides HDMI audio).
>
> Ciao,
>   Alberto
>
> --
> http://blog.mardy.it <- geek in un lingua international!
> _______________________________________________
> Development mailing list
> Development at qt-project.org
> http://lists.qt-project.org/mailman/listinfo/development



More information about the Development mailing list