Guys,
One thing that I have found very useful in KDE3 was the ability to view and use medical image file formats (MRI,CT,etc..). The functionality is provided through libksquirrel. However, the xmedcon library must be present on the system for libksquirrel to provide this capability. I have tested and built xmedcon with current (bleeding edge) libraries and it works fine. For TDE to be able to handle medical image formats -> that's a pretty good feather in it's cap :)
source=('http://downloads.sourceforge.net/project/xmedcon/XMedCon-Source/0.11.0/xmedc...') md5sums=('99646261a5cfa4898956de876e99abeb')
_prefix=/usr
./configure \ --prefix=${_prefix} \ --sysconfdir=/etc \ --localstatedir=/var \ --libdir=/usr/lib
make
Simple build. I'll test later today or tomorrow. I'll have to pull CTs from closed files to test with the medical images, but I don't anticipate problems.
There are a few other file formats that I have to work on (CAD DXF, etc..), but I would like to see TDE ship with all capabilities working (or at least be able to have all of them working)
One thing that I have found very useful in KDE3 was the ability to view and use medical image file formats (MRI,CT,etc..). The functionality is provided through libksquirrel. However, the xmedcon library must be present on the system for libksquirrel to provide this capability. I have tested and built xmedcon with current (bleeding edge) libraries and it works fine. For TDE to be able to handle medical image formats -> that's a pretty good feather in it's cap :)
source=('http://downloads.sourceforge.net/project/xmedcon/XMedCon-Source/0.11.0/xmedc...') md5sums=('99646261a5cfa4898956de876e99abeb')
_prefix=/usr
./configure \ --prefix=${_prefix} \ --sysconfdir=/etc \ --localstatedir=/var \ --libdir=/usr/lib
make
Simple build. I'll test later today or tomorrow. I'll have to pull CTs from closed files to test with the medical images, but I don't anticipate problems.
There are a few other file formats that I have to work on (CAD DXF, etc..), but I would like to see TDE ship with all capabilities working (or at least be able to have all of them working)
Nice ideas. :)
Looks like xmedcon is actively maintained. As Trinity provides libksquirrel and ksquirrel packages, seems a how-to article in the community section of the wiki is appropriate for providing this type of extended support.
Darrell
On 03/26/2012 02:27 PM, Darrell Anderson wrote:
Nice ideas. :)
Looks like xmedcon is actively maintained. As Trinity provides libksquirrel and ksquirrel packages, seems a how-to article in the community section of the wiki is appropriate for providing this type of extended support.
Darrell
OK - on my plate :)
On 03/26/2012 02:40 PM, David C. Rankin wrote:
On 03/26/2012 02:27 PM, Darrell Anderson wrote:
Nice ideas. :)
Looks like xmedcon is actively maintained. As Trinity provides libksquirrel and ksquirrel packages, seems a how-to article in the community section of the wiki is appropriate for providing this type of extended support.
Darrell
OK - on my plate :)
It didn't really fit in an existing community page, so I just dropped a note on the HowToBuild under Section 8.:
libksquirrel: required by ksquirrel (TDE swiss-army-knife for graphic file formats, also supports medical image formats if xmedcon is provided)
We will have to determine how we want to break-up and provide this type of information on the wiki. I think another developer page to supplement HowToBuild would work. Something like BuildingWithFullFeatures or BuildingExtraFeatures....
-
Darrell Anderson -
David C. Rankin