[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [TASS] TASS Software version control
I was wandering about the ip library. I am writing a Windows 95/98/NT GUI to allow any one to do amateur sky survey work with the Mark IV's (I am also trying to include parallel port dll's from SBIG to control the ST-7 and 8 cameras for a majority of amateurs). I guess what I am really doing is just writing a Mark IV "client" computer, and will include the ip library to run as a seperate image processing program run in MDI interface mode inside of my program.
I am hoping that the Windows program that I'm writing could be used by most Microsoft users, because even the database system I can access.
Is the IP library readily accessed for Windows 95 and above?
On Fri, 10 Dec 1999 13:50:19 Chris Albertson wrote:
>> Like Tom I'm wedded to Microsoft, certainly not by choice but by
>> professional necessity. I would strongly encourage us to write the code we
>> use in such a way that most would be portable to different systems. That's
>> why the ip library that I used for Dark, Flat, Star, FlatComp, etc. was as
>> easily ported to Linux as it was. The ip library contains about 90% of the
>> code that's used in the above programs. Glenn made some changes to make it
>> work under the gcc/Linux combination and I'd like to fold those changes into
>> the MS Windows version so we use the same source code. The only parts that
>> are MS specific are the user interfaces for the most part.
>I've notice that the way the Linux version is built, the ip library
>is not a library. All the code is in one directory and gets
>linked to together at once. I can make the change to the makefile
>to first build a library then use it to build the executable.
>If you could list out which source files belong in the ip library
>and suggest a name for the library I'll re-package it and post
>a new tar file.
>Most of the code we write will be portable if we make an effort
>not to use non portable, non-free tools (Wow, a triple negative.)
>OK, Our code will be portable if we use portable, free tools
>That said, some software is going to be restricted to certain
>systems. My real-time driver is not intended to be run on
>someone's desktop home PC. It runs on a PC that is dedicated to
>controlling a Mark IV. So I figure it does not need to be
>portable. Same goes for Database server side software. Other
>stuff, anything that talks to a user and runs on his desktop
>and uses a GUI or command line should be portable.
> Chris Albertson
> firstname.lastname@example.org Voice: 626-351-0089 X127
> Logicon, Pasadena California Fax: 626-351-0699
HotBot - Search smarter.