[Kst] extragear/graphics/kst/src/datasources

barth.netterfield at utoronto.ca barth.netterfield at utoronto.ca
Wed May 31 23:24:28 CEST 2006


Is there a good way to differentiate an lfi file from any other fits file?


Quoting Andrew Walker <arwalker at sumusltd.com>:

> At this point lfiio should remain as is, as it will shortly be using
> a database interface to the LFI data. It sounds as if you should simply
> take the elements of lfiio that you need and move them to your all-in-one
> datasource.
> 
> Thanks,
> 
> Andrew
> 
> -----Original Message-----
> From: Theodore Kisner [mailto:tskisner.public at gmail.com]
> Sent: Wednesday, May 31, 2006 11:03 AM
> To: kst at kde.org
> Subject: Re: [Kst] extragear/graphics/kst/src/datasources
> 
> 
> On Wednesday 31 May 2006 10:24, George Staikos wrote:
> |   If you are going to hack up a datasource that's in production use, it's
> | best done in a branch, but the library is self-contained so it's fine in
> | trunk.
> 
> ok, I will develop the libfitstools library and fitsgeneral datasource in
> trunk, but leave them disabled until they are working well.
> 
> After that, I will need to convert the healpix and lfiio datasources to use
> libfitstools.  I will either do this in a branch or at the beginning of a
> development cycle (this datasource code is fairly simple, so I think any
> problems can be resolved quickly).
> 
> So the 1.3 release is planned for the next couple weeks?  I suspect that
> these
> datasource changes won't be released until 1.4 in order to make sure that
> no
> regressions are introduced.
> 
> -Ted
> 
> _______________________________________________
> Kst mailing list
> Kst at kde.org
> https://mail.kde.org/mailman/listinfo/kst
> 
> _______________________________________________
> Kst mailing list
> Kst at kde.org
> https://mail.kde.org/mailman/listinfo/kst
> 




More information about the Kst mailing list