gnupic@linuxhacker.org

On Wed, 26 Jan 2000, Ralf Forsberg wrote:

> Is is possible to have tooltips for non-widget things like drawables
> and clists? Is it possible to force tooltips to appear when you want
> them to?

Don't know...

> 
> >Last weekend, i spent a couple of hours hacking grpn (an rpn calculator)  
> >to get the damn ui to allow me to easily switch from hex to decimal
> >(something I spend way too much time doing). To make a long story short,
> >it got me thinking about how to go about and creating an LCD. As soon as
> >18.0 is out, I might begin doing this. The goal would be to create a
> >'module' separate from gpsim.
> 
> Are you going to have seperate processes or use dlopen and friends,
> or some other way?

The part I've only thought about was how to create the LCD background, map
characters to the display, define the display attributes, and interfacing
to an LCD header.

The LCD header will be a bitmap of the LCD header's I/O pins. In
other words, one pin on the header will correspond to one bit. Data is
written into the module much the same as it is in a real device: data
placed onto the data bus and is clocked in. 

I do not yet know how to make this data port interface to other modules,
such as gpsim. Alternatives that I've though about:

1) Link directly in with gpsim's gui.
   - Perhaps the module could be a subdirectory off of gpsim/gui/ 

2) A separate application that's placed into a library and linked with
gpsim. Essentially the module would be developed and maintained separate
from gpsim. However, when gpsim is compiled, the module would be linked in
much the same way that gtk+-extra is now.

3) A separate application that interfaces to gpsim through a formal IPC
interface. A simple socket interface should be sufficient. But if there's
a corba expert among us willing to donate their services, well please step
forward and give us some guidance here. 


Initially I'll do step (1). Ultimately I'd like to implement (3). 

--------------
But I'm getting way ahead of my self. I definitely want to focus on
gpsim-0.18.0. I'd like to get a release out asap. If you want to add the
pins stuff that would be great. I'm right now in the middle of
implementing the config word for the 18cxxx devices. I found a deficiency
in gpasm's .cod file logic that prohibits the config word from being at an
address above 64k. (Actually, the .cod logic prohibits anything from being
at 64k. I've gpasm torn to pieces right now and am slowly putting it back
together. New versions of gpasm and vc should be coming out shortly.)

Scott