tilp-devel — This list is intended to TiLP's developers, contributors and advanced users.

Re: [TiLP-devel] TiLP ported to FreeBSD

[Julien B. <jb...@jb...>]

Romain Lievin <ro...@ti...> wrote:

>> Do not touch the CVS without asking me first, there's a tilp module
>> that in fact resolves to tilp-osx. I need to remove that before.
>
> I attempted but your cellular phone is not reachable....

Yeah I hit the f*cking wrong key while retrieving the phone :)

I'll be unreachable tonight (from now on), and I've got exams this
week. (sucks)

>> Importing the code for the libs into the CVS will require updating the
>> OSX support for them, otherwise we'll have some license issue.
>
> Really ?

Yeah, need to check whether I made source packages for the latest
binaries I put up on SF.

>> Regarding the read_ico() functions, it is completely unportable. Get
>> rid of it ASAP.
>
> Why are theynon portable ?

You're fread()'ing structs in the .ico file. The problem is that
memory alignment is not guaranteed to be the same depending on the
compiler and the architecture.

It works on i386, but it doesn't work on PowerPC.

That's one problem, the other being endianness.

Remember, that's why I redesigned the skin format a while ago.

> Ok, I will convert them...

convert is your friend :)

JB.

--=20
 CJ> Les censeurs agitent plus de vent que les moulins des Pays Bas.
 Tiens, je savais pas que c'=E9taient les moulins qui cr=E9aient le vent.
 -+- GR in GNU : Dame qui se shoote et sang chaud pensa -+-

Re: [TiLP-devel] TiLP ported to FreeBSD

[Romain L. <ro...@ti...>]

Hi,

> Yeah, but I was specificaly speaking of UNIX platforms, as, we all
> know it, everything else simply sucks :-)

> > It seems that my tree is more recent that yours. Anyways, I'm going to use CVS
> > given that I have an ADSL connection now.
> 
> Do not touch the CVS without asking me first, there's a tilp module
> that in fact resolves to tilp-osx. I need to remove that before.

I attempted but your cellular phone is not reachable....

> 
> Importing the code for the libs into the CVS will require updating the
> OSX support for them, otherwise we'll have some license issue.
> 

Really ?

> Regarding the read_ico() functions, it is completely unportable. Get
> rid of it ASAP.

Why are theynon portable ?
Ok, I will convert them...

> 
> JB.
> 
> -- 
>  Ca fait d?j? plusieurs semaines que j"essaie de correspondre par l"
>  interm?diaire d"un groupe de discussion. Ca ne fait que deux jour que je
>  suis parvenu ? exp?dier un message
>  -+- GM in GNU : Patience et longueur de temps.. -+-
> 
> 

roms.

> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> TiLP-devel mailing list
> TiL...@li...
> https://lists.sourceforge.net/lists/listinfo/tilp-devel

-- 
Romain Lievin, aka 'roms'  	<ro...@ti...>
The TiLP project is on 		<http://www.ti-lpg.org>
"Linux, y'a moins bien mais c'est plus cher !"

Re: [TiLP-devel] TiLP ported to FreeBSD

[Romain L. <ro...@ti...>]

Hi,

>   I also added LIBS="$LIBS $INTLLIBS" in every ./configure. With this

Added.


> ** libticables 3.5.3
> 
>   I added a few lines to ./configure to define __FBSD__. These should be
> added to configure.ac though. I didn't because then I prevented

Added.

>   Further on, the serial devices on FreeBSD are named
> /dev/cuaa(0|1|2|3). The parallel ports are /dev/lpt(0|1|2), but I

You will have to add some defines in cabl_def.h.

>   On another note, FreeBSD doesn't define O_SYNC. With O_FSYNC however,
> things work perfect.
> 

Linux doesn't have O_FSYNC.

> 
> ** libtifiles 0.4.0
> 

> ** libticalcs 4.2.8
> 
>   In src/calc_def.h I replaced <glib-1.2/glib.h> with <glib.h>, since I
> believe the glib-1.2 part is system dependent and ./configure adds a
> proper -I(include) to CFLAGS anyway. The downside is that TiLP's
> configure script chokes when checking for <tilp/calc_def.h>, but this
> can be overcome by adding the proper -I(include) to CPPFLAGS.

I know it's problematic. This problem does not exist any longer with Glib2.0
which is properly detected (pkg-config power !).

> ** tilp 6.00 pre15
> 
>   On some lines in the configure script $(prefix) is used. This gave
> some problems so I replaced them by $prefix. Should there be any
> difference between these two?


replaced by ${prefix}, as emphasized by JB.

>   That should be it. I hope this can be of help to somebody. I'm not
> submitting anything to the FreeBSD ports tree yet as I first want to
> check a few more things, maybe take a look at the usb lib/driver and
> that's all for after exams. At the moment I'm just happy to be able to
> connect to my calc!

Well, I merged some of yours remarks but not at all. I will prefer a complete
patch. If you intend to do this, ask me my latest tree or use the CVS (if I 
manage to use it...).

> 
> Tijl Coosemans
> 
> 

_Thanks_, Romain.

> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> TiLP-devel mailing list
> TiL...@li...
> https://lists.sourceforge.net/lists/listinfo/tilp-devel
> 

-- 
Romain Lievin, aka 'roms'  	<ro...@ti...>
The TiLP project is on 		<http://www.ti-lpg.org>
"Linux, y'a moins bien mais c'est plus cher !"

Re: [TiLP-devel] TiLP ported to FreeBSD

[Julien B. <jb...@jb...>]

Romain Lievin <ro...@ti...> wrote:

>> >   I also added LIBS=3D"$LIBS $INTLLIBS" in every ./configure. With t=
his
>>=20
>> This should already be done, if it isn't then it's a bug.
>
> Yes, some work for me :-(

The autoconf check for libintl should do that.

> I recently migrated to pkg-config. The ti*-config scripts are still gen=
erated
> but pkg-config is more powerful.

Good ! You forgot to notify me...

>> We don't want to rely on GCC specific features, so that TiLP can be
>> built easily on other platforms using other compilers (eg Tru64 with
>> Compaq's CC -- which is crap, for what matters :)).
>
> Such as MSVC even if I stopped the Win32 port.

Yeah, but I was specificaly speaking of UNIX platforms, as, we all
know it, everything else simply sucks :-)

>> >   In src/calc_def.h I replaced <glib-1.2/glib.h> with <glib.h>, sinc=
e I
>>=20
>> *dung*
>>=20
>> /me applies a big LART to Romain
>
> What's LART ?

A Luser Attitude Readjustment Tool. Which is, to say, any object you
can use to hurt somebody with prejudice. :-)

>> >   Related to this, I could comment out a redefinition of
>> > HAVE_TILP_TICALCS_H in TiLP's src/tilibs.h.
>>=20
>> This include file should GO AWAY AND BURN IN HELL, please Romain...
>
> Yeah but I do this due to this fucking problem with tilp/calc_def.h and=
 glib
> (as you mentionned it above).

Nah, you use it to avoid #include'ing every needed header file in each
source file, which results in a big header bloat.

Now that the windows port is gone, we can get rid of it.

>> We definitely need to find some motivation and go on a cleanup spree
>> in TiLP. And I need to go back to the TiLP for Mac OS X port...
>
> JB: as I told you, some guys on the ti-fr forum are using the OS-X vers=
ion and
> are happy with it...

How can they be happy with the buggy piece of shit it is ? There are
obvious bugs, the USB cable support is buggy, and a couple of features
are still lacking.

>> Not speaking of TiEmu :) Oh, well...
>
> Oops ...

I'm still waiting the bugfix to load a flash upgrade :-)

(convert_tib_to_rom() IIRC)

>> My TODO list for TiLP would be :
>>  - use packageconfig instead of ticalc-config & friends (easy)
>
> JB: it has been done ! Maybe I forgotten to tell you ?

Yep.


> It seems that my tree is more recent that yours. Anyways, I'm going to =
use CVS
> given that I have an ADSL connection now.

Do not touch the CVS without asking me first, there's a tilp module
that in fact resolves to tilp-osx. I need to remove that before.

Importing the code for the libs into the CVS will require updating the
OSX support for them, otherwise we'll have some license issue.

Regarding the read_ico() functions, it is completely unportable. Get
rid of it ASAP.

JB.

--=20
 Ca fait d=E9j=E0 plusieurs semaines que j"essaie de correspondre par l"
 interm=E9diaire d"un groupe de discussion. Ca ne fait que deux jour que =
je
 suis parvenu =E0 exp=E9dier un message
 -+- GM in GNU : Patience et longueur de temps.. -+-

Re: [TiLP-devel] TiLP ported to FreeBSD

[Romain L. <ro...@ti...>]

Hi Tilj,

On Sun, Jan 05, 2003 at 12:19:12PM +0100, Julien BLACHE wrote:
> Tijl Coosemans <ti...@ul...> wrote:
> 
> > Hello to all TiLP developers,
> 
> Hi Tilj,
> 
> >   Today I finished porting TiLP to FreeBSD. A set of patches for each
> > package is available at http://tijl.studentenweb.org/tilp/
> 
> Good news :)
> 

Yeah ! Great ! An attempt has been done one day but without any success. I am
very happy you managed to do that...

> >   Currently I only have the Grey TIGL working. I might take a look at
> > the others when I finish my exams at the end of January.
> 
> It shouldn't be too problematic to enable support for the other
> cables. You'll need to figure out the low-level access routines, and
> that's it :)
> 
> For the USB cable, you'll need the libusb which is ported to FreeBSD
> already.
> 
> For the parallel cable, maybe we could use the libieee1284, although
> I'm not sure it would cover our needs.
> 
> > ** General
> >
> >   FreeBSD currently doesn't have <stdint.h>. I believe the upcoming 5.0
> > will support it though. To overcome this I encapsulated each #include
> > <stdint.h> with:
> 
> Argh too bad :/ stdint.h is part of ISO C99...
> 
> >   I also added LIBS="$LIBS $INTLLIBS" in every ./configure. With this
> 
> This should already be done, if it isn't then it's a bug.

Yes, some work for me :-(

> 
> >   Next I noticed the ti*-config scripts had a bug when the --cflags
> > option was given. They returned the dir without the -I prefix.
> 
> Needs to be fixed.
> 

I recently migrated to pkg-config. The ti*-config scripts are still generated
but pkg-config is more powerful.

> > ** libticables 3.5.3
> >
> >   I added a few lines to ./configure to define __FBSD__. These should be
> > added to configure.ac though. I didn't because then I prevented
> > using autoconf/automake/... during compilation. I wonder why you don't
> > use any gcc predefined constants though. I believe either unix or
> > __unix__ is defined on every unix platform. This is what I get on a
> > FreeBSD box.
> 
> We don't want to rely on GCC specific features, so that TiLP can be
> built easily on other platforms using other compilers (eg Tru64 with
> Compaq's CC -- which is crap, for what matters :)).
> 

Such as MSVC even if I stopped the Win32 port.

> > ** libtifiles 0.4.0
> >
> >   No system specific patches were necessary. <stdint.h> is used quite a
> > lot though.
> 
> We should have a specific header file defining our own types using
> whatever is available on the system, preferably stdint.h, falling back
> to inttypes.h or etc...
> 
> > ** libticalcs 4.2.8
> >
> >   In src/calc_def.h I replaced <glib-1.2/glib.h> with <glib.h>, since I
> 
> *dung*
> 
> /me applies a big LART to Romain

What's LART ?

> 
> > believe the glib-1.2 part is system dependent and ./configure adds a
> > proper -I(include) to CFLAGS anyway. The downside is that TiLP's
> > configure script chokes when checking for <tilp/calc_def.h>, but this
> > can be overcome by adding the proper -I(include) to CPPFLAGS.
> 
> configure needs to be fixed wrt this.
> 
> >   At the moment this is done automatically by a Makefile I made for
> > TiLP's entry in the FreeBSD ports tree, but I can imagine it isn't so
> > convenient when you have to run ./configure manually. Probably, some
> > construction can be figured out, like adding a CPPFLAGS= line at the
> > same place as LIBS= CFLAGS= lines currently in there somewhere.
> 
> The autoconf check for libticalcs needs to be fixed to include the
> output of ticalc-config, or something like this.
> 
> >   Related to this, I could comment out a redefinition of
> > HAVE_TILP_TICALCS_H in TiLP's src/tilibs.h.
> 
> This include file should GO AWAY AND BURN IN HELL, please Romain...

Yeah but I do this due to this fucking problem with tilp/calc_def.h and glib
(as you mentionned it above).

> 
> It's one of the reason why TiLP takes so long to build...
> 
> > ** tilp 6.00 pre15
> >
> >   On some lines in the configure script $(prefix) is used. This gave
> > some problems so I replaced them by $prefix. Should there be any
> > difference between these two?
> 
> ${prefix} would be better, needs checking & fixing.
> 
> >   src/term_cb.c wants to include error.h, but there doesn't seem to be
> > any.
> 
> IIRC it was missing in one of the tarballs.
> 
> >   That should be it. I hope this can be of help to somebody. I'm not
> > submitting anything to the FreeBSD ports tree yet as I first want to
> > check a few more things, maybe take a look at the usb lib/driver and
> > that's all for after exams. At the moment I'm just happy to be able to
> > connect to my calc!
> 
> We definitely need to find some motivation and go on a cleanup spree
> in TiLP. And I need to go back to the TiLP for Mac OS X port...

JB: as I told you, some guys on the ti-fr forum are using the OS-X version and
are happy with it...

> 
> Not speaking of TiEmu :) Oh, well...
> 

Oops ...

> 
> My TODO list for TiLP would be :
>  - use packageconfig instead of ticalc-config & friends (easy)

JB: it has been done ! Maybe I forgotten to tell you ?

>  - cleanup the #include mess (not too difficult)
>  - double check the autoconf macros for libti* (not too difficult)
> 
> After that, we could go on with a GTK 2 port.
> 
> Thoughts ?
> 
> JB.
> 

Well, you are welcome to modify TiLP so that it can be ported on FreeBSD.
In a first step, I will try and merge your modifications...

It seems that my tree is more recent that yours. Anyways, I'm going to use CVS
given that I have an ADSL connection now.

> -- 
> Julien BLACHE                                   <http://www.jblache.org> 
> <jb...@jb...> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> TiLP-devel mailing list
> TiL...@li...
> https://lists.sourceforge.net/lists/listinfo/tilp-devel
> 

roms.
-- 
Romain Lievin, aka 'roms'  	<ro...@ti...>
The TiLP project is on 		<http://www.ti-lpg.org>
"Linux, y'a moins bien mais c'est plus cher !"

Re: [TiLP-devel] TiLP ported to FreeBSD

[Julien B. <jb...@jb...>]

Tijl Coosemans <ti...@ul...> wrote:

> Hello to all TiLP developers,

Hi Tilj,

>   Today I finished porting TiLP to FreeBSD. A set of patches for each
> package is available at http://tijl.studentenweb.org/tilp/

Good news :)

>   Currently I only have the Grey TIGL working. I might take a look at
> the others when I finish my exams at the end of January.

It shouldn't be too problematic to enable support for the other
cables. You'll need to figure out the low-level access routines, and
that's it :)

For the USB cable, you'll need the libusb which is ported to FreeBSD
already.

For the parallel cable, maybe we could use the libieee1284, although
I'm not sure it would cover our needs.

> ** General
>
>   FreeBSD currently doesn't have <stdint.h>. I believe the upcoming 5.0
> will support it though. To overcome this I encapsulated each #include
> <stdint.h> with:

Argh too bad :/ stdint.h is part of ISO C99...

>   I also added LIBS="$LIBS $INTLLIBS" in every ./configure. With this

This should already be done, if it isn't then it's a bug.

>   Next I noticed the ti*-config scripts had a bug when the --cflags
> option was given. They returned the dir without the -I prefix.

Needs to be fixed.

> ** libticables 3.5.3
>
>   I added a few lines to ./configure to define __FBSD__. These should be
> added to configure.ac though. I didn't because then I prevented
> using autoconf/automake/... during compilation. I wonder why you don't
> use any gcc predefined constants though. I believe either unix or
> __unix__ is defined on every unix platform. This is what I get on a
> FreeBSD box.

We don't want to rely on GCC specific features, so that TiLP can be
built easily on other platforms using other compilers (eg Tru64 with
Compaq's CC -- which is crap, for what matters :)).

> ** libtifiles 0.4.0
>
>   No system specific patches were necessary. <stdint.h> is used quite a
> lot though.

We should have a specific header file defining our own types using
whatever is available on the system, preferably stdint.h, falling back
to inttypes.h or etc...

> ** libticalcs 4.2.8
>
>   In src/calc_def.h I replaced <glib-1.2/glib.h> with <glib.h>, since I

*dung*

/me applies a big LART to Romain

> believe the glib-1.2 part is system dependent and ./configure adds a
> proper -I(include) to CFLAGS anyway. The downside is that TiLP's
> configure script chokes when checking for <tilp/calc_def.h>, but this
> can be overcome by adding the proper -I(include) to CPPFLAGS.

configure needs to be fixed wrt this.

>   At the moment this is done automatically by a Makefile I made for
> TiLP's entry in the FreeBSD ports tree, but I can imagine it isn't so
> convenient when you have to run ./configure manually. Probably, some
> construction can be figured out, like adding a CPPFLAGS= line at the
> same place as LIBS= CFLAGS= lines currently in there somewhere.

The autoconf check for libticalcs needs to be fixed to include the
output of ticalc-config, or something like this.

>   Related to this, I could comment out a redefinition of
> HAVE_TILP_TICALCS_H in TiLP's src/tilibs.h.

This include file should GO AWAY AND BURN IN HELL, please Romain...

It's one of the reason why TiLP takes so long to build...

> ** tilp 6.00 pre15
>
>   On some lines in the configure script $(prefix) is used. This gave
> some problems so I replaced them by $prefix. Should there be any
> difference between these two?

${prefix} would be better, needs checking & fixing.

>   src/term_cb.c wants to include error.h, but there doesn't seem to be
> any.

IIRC it was missing in one of the tarballs.

>   That should be it. I hope this can be of help to somebody. I'm not
> submitting anything to the FreeBSD ports tree yet as I first want to
> check a few more things, maybe take a look at the usb lib/driver and
> that's all for after exams. At the moment I'm just happy to be able to
> connect to my calc!

We definitely need to find some motivation and go on a cleanup spree
in TiLP. And I need to go back to the TiLP for Mac OS X port...

Not speaking of TiEmu :) Oh, well...


My TODO list for TiLP would be :
 - use packageconfig instead of ticalc-config & friends (easy)
 - cleanup the #include mess (not too difficult)
 - double check the autoconf macros for libti* (not too difficult)

After that, we could go on with a GTK 2 port.

Thoughts ?

JB.

-- 
Julien BLACHE                                   <http://www.jblache.org> 
<jb...@jb...> 

[TiLP-devel] TiLP ported to FreeBSD

[Tijl C. <ti...@ul...>]

Hello to all TiLP developers,

  Today I finished porting TiLP to FreeBSD. A set of patches for each
package is available at http://tijl.studentenweb.org/tilp/
  Currently I only have the Grey TIGL working. I might take a look at
the others when I finish my exams at the end of January.

  What follows are a few notes about the patch sets.


** General

  FreeBSD currently doesn't have <stdint.h>. I believe the upcoming 5.0
will support it though. To overcome this I encapsulated each #include
<stdint.h> with:

+#ifdef HAVE_STDINT_H
 #include <stdint.h>
+#else
+#include <inttypes.h>
+#endif

  Most of the patches just do this. I realise this isn't really a nice
structure to have in your code, so you may not want to apply these.

  I also added LIBS="$LIBS $INTLLIBS" in every ./configure. With this
line each package can be compiled with gettext in libintl in case glib12
isn't available. For libticalcs and tilp this doesn't matter much since
they depend on glib12 anyway.

  Next I noticed the ti*-config scripts had a bug when the --cflags
option was given. They returned the dir without the -I prefix.


** libticables 3.5.3

  I added a few lines to ./configure to define __FBSD__. These should be
added to configure.ac though. I didn't because then I prevented
using autoconf/automake/... during compilation. I wonder why you don't
use any gcc predefined constants though. I believe either unix or
__unix__ is defined on every unix platform. This is what I get on a
FreeBSD box.

tijl tijl% gcc -dM -E - < /dev/null
#define __FreeBSD__ 4 
#define __FreeBSD_cc_version 460001 
#define __i386__ 1 
#define __i386 1 
#define __GNUC_MINOR__ 95 
#define i386 1 
#define __unix 1 
#define __unix__ 1 
#define __GNUC__ 2 
#define __ELF__ 1 
#define unix 1 
tijl tijl%

  Further on, the serial devices on FreeBSD are named
/dev/cuaa(0|1|2|3). The parallel ports are /dev/lpt(0|1|2), but I
haven't added these yet, since the parallel cable isn't supported yet
anyway.

  On another note, FreeBSD doesn't define O_SYNC. With O_FSYNC however,
things work perfect.


** libtifiles 0.4.0

  No system specific patches were necessary. <stdint.h> is used quite a
lot though.

** libticalcs 4.2.8

  In src/calc_def.h I replaced <glib-1.2/glib.h> with <glib.h>, since I
believe the glib-1.2 part is system dependent and ./configure adds a
proper -I(include) to CFLAGS anyway. The downside is that TiLP's
configure script chokes when checking for <tilp/calc_def.h>, but this
can be overcome by adding the proper -I(include) to CPPFLAGS.
  At the moment this is done automatically by a Makefile I made for
TiLP's entry in the FreeBSD ports tree, but I can imagine it isn't so
convenient when you have to run ./configure manually. Probably, some
construction can be figured out, like adding a CPPFLAGS= line at the
same place as LIBS= CFLAGS= lines currently in there somewhere.
  Related to this, I could comment out a redefinition of
HAVE_TILP_TICALCS_H in TiLP's src/tilibs.h.


** tilp 6.00 pre15

  On some lines in the configure script $(prefix) is used. This gave
some problems so I replaced them by $prefix. Should there be any
difference between these two?

  src/term_cb.c wants to include error.h, but there doesn't seem to be
any.


**

  That should be it. I hope this can be of help to somebody. I'm not
submitting anything to the FreeBSD ports tree yet as I first want to
check a few more things, maybe take a look at the usb lib/driver and
that's all for after exams. At the moment I'm just happy to be able to
connect to my calc!

Tijl Coosemans

Re: [TiLP-devel] TiLP problems

[Romain L. <ro...@ti...>]

Hi,

well, you should use the tilp-users mailing-list rather than the tilp-devel one...

On Sun, Dec 22, 2002 at 10:13:38PM +0200, Tero Toikkanen wrote:
> Hi,
> 
> I'm trying to use the TiLP program to communicate with my calculator.
> Here are some details:
> 
> - Windows XP
> - TI Voyage 200 (also tried with TI-85)
> - USB SilverLink
> - TiLP 6.00-pre7
> - SilverLink driver for Windows (driver date seems to be either 28.
> August or 25. May 2002 and I have downloaded the driver today, 22.
> December, as it says on the site that they were updated today)

The page has been updated today but given that I uploaded the driver on ticalc
, it will be available when ticalc will update its file list.

> 
> I have to say that I don't know is the problem in the USB drivers or in
> TiLP. I had lots of problems with installing the driver, but the version
> I downloaded today seemed to install without problems. I can't get the
> program to connect to either TI-85 or Voyage 200. By the way, why are
> there four different I/O ports for USB as well?

Because, we should connect up to 16 cables (in theory) but it's true that TiLP
 can manage just one link (eventhough a teacher asked me to manage more 
cables).

> 
> When I try to set TiLP to connect to Voyage 200, it doesn't highlight
> the V200 setting when selecting calculators. It resets it to TI92. Also

This may be a bug.

> this seems to happen when I set the Link to USB and open advanced
> settings: when I click ok, an error is displayed saying "Msg:
> FreeLibrary error. Unable to release the DLL. Cause: ?? System:
> GetLastError = 127 -> The specified procedure could not be found."

You have a wrong version of the driver.

> Windows XP also likes to think the program has done something bad
> occasionally when I change the settings or try to connect to my calc and
> shuts down TiLP.
> 
> Where do you think the problem might be?
> 

ok, I attached the latest version of the SilverLink driver. You will find on
SourceForge (see the download section) the latest release of TiLP.
Please download it. It you still encouter problems, feel free to mail me.

> Yours,
> 
> Tero Toikkanen
> 
> 

roms.
 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> TiLP-devel mailing list
> TiL...@li...
> https://lists.sourceforge.net/lists/listinfo/tilp-devel
> 

-- 
Romain Lievin, aka 'roms'  	<ro...@ti...>
The TiLP project is on 		<http://www.ti-lpg.org>
"Linux, y'a moins bien mais c'est plus cher !"

[TiLP-devel] TiLP problems

[Tero T. <te...@tt...>]

Hi,

I'm trying to use the TiLP program to communicate with my calculator.
Here are some details:

- Windows XP
- TI Voyage 200 (also tried with TI-85)
- USB SilverLink
- TiLP 6.00-pre7
- SilverLink driver for Windows (driver date seems to be either 28.
August or 25. May 2002 and I have downloaded the driver today, 22.
December, as it says on the site that they were updated today)

I have to say that I don't know is the problem in the USB drivers or in
TiLP. I had lots of problems with installing the driver, but the version
I downloaded today seemed to install without problems. I can't get the
program to connect to either TI-85 or Voyage 200. By the way, why are
there four different I/O ports for USB as well?

When I try to set TiLP to connect to Voyage 200, it doesn't highlight
the V200 setting when selecting calculators. It resets it to TI92. Also
this seems to happen when I set the Link to USB and open advanced
settings: when I click ok, an error is displayed saying "Msg:
FreeLibrary error. Unable to release the DLL. Cause: ?? System:
GetLastError = 127 -> The specified procedure could not be found."
Windows XP also likes to think the program has done something bad
occasionally when I change the settings or try to connect to my calc and
shuts down TiLP.

Where do you think the problem might be?

Yours,

Tero Toikkanen

Re: [TiLP-devel] Usage error on tilp 600-pre9

[Romain L. <rl...@fr...>]

Hi,

On Sun, Nov 03, 2002 at 04:17:54PM +0100, Bernd Eckstein wrote:
> Hi all,
> 
> I just tried, using TiLP 6.00-pre9 with tipar 1.18 or tiser 1.17 always 
> brings up the following console-error:
> 
> Error: unable to open this device: <>
> 
> method is automatic (kernel module)
> 
> Any Hints?
> 

Yes, I noticed this problem. Probably a bug. What you can do: delete the TiLP ini file (~/.tilp), run TiLP, config and save.

> At the moment it works only as root in direct mode for me.
> And only with my TI-92. My TI-85 isn't even detected. :-(
> 
> btw: building the whole package is a lot work. Installing the kernel 
> sources, aquiring and building glib and gtk .... Sorry to say, but 
> windoofs is loads more comfortable.

Because you are compiling packages from source and these ones are devel.
If you want to make your life easier, install a RPM or DEB package.

> 
> But if it runs, it looks really good. Nice work.
>

Thanks for your mail. I am going to investigate the problem...
 
> -- 
> Mit freundlichen Gruessen / Best regards
> 
> B.Eckstein, IVU Traffic Technologies AG
> Elisabethstr. 16, 52062 Aachen
> Telefon: +49 241 47051-0, Telefax: +49 241 47051-89
> mailto:B.E...@iv..., http://www.ivu.de
> 
> 
> 

roms.

> -------------------------------------------------------
> This SF.net email is sponsored by: ApacheCon, November 18-21 in
> Las Vegas (supported by COMDEX), the only Apache event to be
> fully supported by the ASF. http://www.apachecon.com
> _______________________________________________
> TiLP-devel mailing list
> TiL...@li...
> https://lists.sourceforge.net/lists/listinfo/tilp-devel
> 

-- 
Romain Lievin, aka 'roms'  	<ro...@lp...>
Web site 			<http://lpg.ticalc.org/prj_tilp>
"Linux, y'a moins bien mais c'est plus cher !"

[TiLP-devel] Usage error on tilp 600-pre9

[Bernd E. <ec...@iv...>]

Hi all,

I just tried, using TiLP 6.00-pre9 with tipar 1.18 or tiser 1.17 always 
brings up the following console-error:

Error: unable to open this device: <>

method is automatic (kernel module)

Any Hints?

At the moment it works only as root in direct mode for me.
And only with my TI-92. My TI-85 isn't even detected. :-(

btw: building the whole package is a lot work. Installing the kernel 
sources, aquiring and building glib and gtk .... Sorry to say, but 
windoofs is loads more comfortable.

But if it runs, it looks really good. Nice work.

-- 
Mit freundlichen Gruessen / Best regards

B.Eckstein, IVU Traffic Technologies AG
Elisabethstr. 16, 52062 Aachen
Telefon: +49 241 47051-0, Telefax: +49 241 47051-89
mailto:B.E...@iv..., http://www.ivu.de

Re: [TiLP-devel] Still here

[james <ja...@ki...>]

O
> > btw, does the gui on tiemu use glade or is it handwritten?
>
> Glade was used to design the GUI elements, some changes were made to
> the code, though, but it's not a big deal.
>
> > (I recently got a Sharp Zaurus and it is based on Qt Embedded, and Qt
> > designer can import glade files, so getting that ported should be
> > relatively simple, and no calculator program for either pda or desktop
> > seems quite as easy or complete as a TI83(+) or 89)
>
> The GUI uses GTK+ for everything except the calc itself. The calc is
> displayed in an SDL window. I don't know if the SDL is available on
> the Zaurus, but I guess there could be someone working on that ;)
>

Thanks, That should be pretty easy to port then (assuming I have the time to 
really work on it, The University I go to has started up again.) SDL is 
available, unfortunately only in framebuffer mode. (Zaurus uses Qtopia which 
is a version of Qt running on framebuffer that handles the windows itself 
without X or anything else, which allows some programs (mplayer in particular 
to run well (due to it's framebuffer support).) So I don't know if can use 
SDL in combination with Qt for display (importing Glade files to Qt Designer 
is pretty easy). Hmm... I need to look at this some more. 

Thanks,

James L.


> For TiEmu, we plan on doing a native Win32 port and a native OS X
> port, but it is not very high on the todo list at the moment.
>
> JB.

Re: [TiLP-devel] Still here

[Julien B. <jb...@jb...>]

james <ja...@ki...> wrote:

Hi,

> Though Admittedly I haven't done much with ti-calcs lately as my second 
> link-cable, and 73 broke. I would be interested in helping if I have the 
> time. 

Thanks for the reply :)

> btw, does the gui on tiemu use glade or is it handwritten? 

Glade was used to design the GUI elements, some changes were made to
the code, though, but it's not a big deal.

> (I recently got a Sharp Zaurus and it is based on Qt Embedded, and Qt 
> designer can import glade files, so getting that ported should be relatively 
> simple, and no calculator program for either pda or desktop seems quite as 
> easy or complete as a TI83(+) or 89)

The GUI uses GTK+ for everything except the calc itself. The calc is
displayed in an SDL window. I don't know if the SDL is available on
the Zaurus, but I guess there could be someone working on that ;)

For TiEmu, we plan on doing a native Win32 port and a native OS X
port, but it is not very high on the todo list at the moment.

JB.

-- 
Julien BLACHE                                   <http://www.jblache.org> 
<jb...@jb...> 

[TiLP-devel] Still here

[james <ja...@ki...>]

Though Admittedly I haven't done much with ti-calcs lately as my second 
link-cable, and 73 broke. I would be interested in helping if I have the 
time. 

btw, does the gui on tiemu use glade or is it handwritten? 
(I recently got a Sharp Zaurus and it is based on Qt Embedded, and Qt 
designer can import glade files, so getting that ported should be relatively 
simple, and no calculator program for either pda or desktop seems quite as 
easy or complete as a TI83(+) or 89)

James L

[TiLP-devel] Reviving this list, tracking CVS

[Julien B. <jb...@jb...>]

Hi,

I'm sending out this mail to the list to determine whether the 7 or so
subscribers are still alive :)

Romain and I plan to begin using CVS extensively for TiLP's (and TiEmu)
development by the end of the year[1], as we intend a port/partial
rewrite to GTK+ 2 (this affects the Linux/UNIX part of TiLP, but may
affects other ports too).

Basically, I plan to setup the SourceForge CVS so that it will send
out a mail containing the CVS log[2] for each commit to the repository ;
this mail would end up on this list.

As this could generate quite a couple of mails on a good day[3], I'd like
to know if this could be a problem for any of our current
subscribers.

Please reply to the list if it could cause you any trouble. However I
don't expect the CVS mails to generate a very high traffic on the
list, so don't be too afraid :)

This list has been quite unused for the past years (2 messages only
!), we hope it will become active in a couple of months.

We'd like to see some applications around TiLP, mainly variables
editors and such, which would bring the TiLP framework to the level of
the TI-Connect in terms of features.


Thanks,

JB,
Debian Developer maintaining TiLP packages,
TiLP for OS X maintainer,
CVS guru ;P

Notes :
-------

[1] "by the end of the year" means sometime after (probably)
mid-october or even later, time for Romain to let the dust settle on
his job etc... :)

[2] CVS is a development tool tracking changes in the source code,
allowing to rollback changes if needed and helping to track bugs
down. The message will contain a summary of the changes that went in
with the commit.

[3] You won't get dozen of mails every day.

-- 
Julien BLACHE                                   <http://www.jblache.org> 
<jb...@jb...> 

[TiLP-devel] TI-83+ Flash app support in TiLP

[Steven W. <srw...@ya...>]

When can I expect to see support for sending flash apps onto the TI-83+
in TiLP (or any Linux program)?  Is there any work that I can do as a
moderately competent Linux/C programmer to help?
-- 
-Steven
In a time of universal deceit, telling the truth is a revolutionary act.
			-- George Orwell
He's alive.  He's alive!  Oh, that fellow at RadioShack said I was mad!
Well, who's mad now?
			-- Montgomery C. Burns

[TiLP-devel] Windows, DLL and TiLP

[Carlos B. <cj...@so...>]

I was looking for info about how to connect with my TI-92+ via the PC. Then 
I found TiLP but I have some questions..

How can I use the dll's in Delphi? or in C++?
Is there an example (sourcecode) around?

thnxs.