transcalc-devel — Developer mailing list for Transcalc - Transmission line calculator

[Transcalc-devel] Transcalc 0.14

[Claudio G. <in...@qs...>]

Gopal wrote:
> I think it would be a good idea to have win32 release. Many engineers
> do use windows and it would benefit them to use transcalc. The other
> point here is gdkimlib. Did you  have that work in windows?
No, not yet. I'm trying to locate some precompiled imlib dlls, there seems not to 
be an "official" release of imlib for win32. At worst, I could try to compile 
imlib myself... 8-(

> > BTW, the latest version from CVS has problems with win32, regarding the code
> > in transcalc.c to determine the home directory and config directory creation
> > at startup. I'll try to fix that.
> 
> Right, the concept of home directory is absent in normal
> windows. However, we can use the HOME environment variable. The
> windows user just needs to set that to some path, and transcalc could
> be made to use the HOME env variable.
Yes, in case HOME is not defined we could use "C:\" (ugly, but I saw some 
programs doing this) or, slightly better, write the file in the program 
installation directory.

> > I've changed the version number to 0.14 and added some points to the TODO.
> > In the saved file I have added also the transcalc version, should we change
> > the format and have to recognize old files and translate to a new format.
> > (too forward looking 8-) ? )
> 
> That makes sense. Sure. Have you committed those changes back ? I do
> not see it reflected in the cvs archive yet?
Well, actually I wrote that before committing the changes, should be there right 
now. Details of the mods are in the Changelog.

> > Another things that may be useful is a description of the transmission line
> > saved in the trc files; no matter how descriptive are the filenames I have
> > problems remembering what a transmission line was about just looking at the
> > filenames with linecalc. This description could be shown in the file load
> > window, in a sort of preview frame.
> 
> Again, nice idea. It might be simplest to write the transmission line
> type as a comment in the first line, and the "preview" mode in the
> file load window could just read the first line to report what type 
> of transmission line is contained in the file.

Yes, the idea was to display the transmission line type and a description string 
typed in by the user in the save file dialog, or in the main window.

Regards,

                            Claudio

[Transcalc-devel] Re: Transcalc 0.13

[Gopal N. <go...@as...>]

On Wed, Jul 24, 2002 at 08:24:42AM +0100, Claudio Girardi wrote:
> Gopal wrote:
> > I have now committed a few more changes. transcalc now has a Print
> > menu option. It produces a text output of all the results, which can
> > be piped to lpr or saved to file. Try it out. In doing this, I think I
> > may have fixed a couple of the bugs you told me about in an earlier
> > email. I know I was supposed to let you fix that, but there ought to
> > be more of such bugs in the source, so please go ahead.
> 
> Hi Gopal,
> I've mixed the comments of a couple of your mail below:
> I received your mail from SF, and I did a checkout yesterday evening. I tried 
> quickly the Print menu option and it seemed to work well, nice work. I've also 
> subscribe to transcalc-devel and transcalc-commit, but es, I don't know if this 
> latter is actually used. No problem for you doing the bug fixes, the important is 
> the program working well now. 
> 

Claudio,

Okay. I will have to setup the commit list. I will let you know once I
am done. I am cc'ing this message to the transcalc-devel list.


> [about transcalc for Win32]
> > Great. But please make sure to test it so that it does not break the
> > unix functionality. What OS do you run normally?
> 
> At home I use Linux 99.9% of the time, so it is the platform I normally use for 
> compiling transcalc; actually the only reason to use *indows in the past few 
> weeks was just to try to compile transcalc under Win32 after modifying the 
> sources with Linux (btw, it is a Slackware 8.0 with kernel 2.4.18). For sure the 
> main goal is to have a stable release for Linux, hoping it will be ok also for 
> Win32; I compiled transcalc with GTK+1.3 for Win32 and all went smoothly, no 
> warnings, no problems and, even more surprising, no crashes 8-). It seems that 
> using GTK+1.3 only a couple of DLLs are needed, so I'll probably send you the exe 
> in the next few days. Do you think it will be a good idea to put an exe for Win32 
> available for download on the transcalc home page?

I think it would be a good idea to have win32 release. Many engineers
do use windows and it would benefit them to use transcalc. The other
point here is gdkimlib. Did you  have that work in windows?

> 
> BTW, the latest version from CVS has problems with win32, regarding the code in 
> transcalc.c to determine the home directory and config directory creation at 
> startup. I'll try to fix that.
> 

Right, the concept of home directory is absent in normal
windows. However, we can use the HOME environment variable. The
windows user just needs to set that to some path, and transcalc could
be made to use the HOME env variable.

> [about warning window and transmission lines calculations library]
> > Again, an excellent idea. Please add it to the TODO file and cvs
> > commit it back. One other minor point - let us bump the version number
> > in configure.in to 0.14, but let's wait to declare a release in
> > ChangeLog until we are ready to release to public.
> 
> I've changed the version number to 0.14 and added some points to the TODO.
> In the saved file I have added also the transcalc version, should we change the 
> format and have to recognize old files and translate to a new format.
> (too forward looking 8-) ? )
> 

That makes sense. Sure. Have you committed those changes back ? I do
not see it reflected in the cvs archive yet?

> Another things that may be useful is a description of the transmission line saved 
> in the trc files; no matter how descriptive are the filenames I have problems 
> remembering what a transmission line was about just looking at the filenames with 
> linecalc. This description could be shown in the file load window, in a sort of 
> preview frame.

Again, nice idea. It might be simplest to write the transmission line
type as a comment in the first line, and the "preview" mode in the
file load window could just read the first line to report what type 
of transmission line is contained in the file.

Gopal.

[Transcalc-devel] Test

[Gopal N. <go...@as...>]

Hello!
Just testing the devel list
Gopal.