Message: previous - next
Month: August 2013

Re: [trinity-devel] Moving tdehwlib to a standalone library

From: "Timothy Pearson" <kb9vqf@...>
Date: Tue, 6 Aug 2013 09:45:50 -0500
> 2013/8/6 Darrell Anderson <darrella@...>
>> I don't pretend to understand the programming reasons cited above.
>> Yet seems to me this topic needs to be discussed here.
>> I've probably done the most user testing with Tim. I've been using
>> GIT pre-R14 for many months and I am not seeing any serious
>> problems with tdehwlib. Whether the sources need to be moved to a
>> separate module ultimately gets decided by Tim as he is the owner
>> of that code.
> Everything I wrote is my plans and view of the situation. I've just
> intended to start a discussion...
> Sorry if it was sound too strongly.

No problem.  I personally would like to keep the hardware module in
tdecore (at least for now), as part of the original idea was to make
hardware functions extremely easy for TDE applications to access.  In my
experience, unless something is easy to access, very few people will use
it. :-)

Otherwise, I am fully in agreement with splitting up the monolithic
tdehardwaredevices.cpp file into a number of smaller files (this could be
theoretically be done for R14.0.0 as it is a cosmetic change), and also
adding pluggable module support (this will likely have to wait for R14.1.0