Re: gpe-config-sleep(gpe-isgui) in CVS

--- Pierre Tardy <tardyp@free.fr> wrote:
> On Mon, 19 Aug 2002 06:42:26 -0700 (PDT)
> Erik Karlin <e_karlin@yahoo.com> wrote:
>
> >
> > Alright, I checked it out of CVS and gave it a quick eyeball. It all
> > looks like it integrated fine, though we may want to rethink my popup
> > IRQ dialog box...it just looks out of place now.
> Why ? I dont think so. Including the list into the window may be possible.
> the auto dim level may fit horizontaly, and be replaced bay the IR lists,
> but the interface may become complicated.
>
> > You might want to add /etc/ipaq-sleep.conf into your allowed_file array
> > in gpe-confsuid.c.
> No. The idea to bring the conf file to ~/ is just fine. I sent patch to
> ipaq-sleep so that it look at ~ before /etc
> Maybe I will send another one to add auto dim level change.
>
> And, I you can see, ipaq-confsuid is just an idea to make timeanddate
> work. I dont know if I will continue this way..

Thats fine...I just quickly gave your code the run-through, and those were
issues I had before I released it.

>
>
> > Also, I'm not sure how we can stop and start the
> > ipaq-sleep daemon via /etc/init.d/ipaq-sleep. We may want to rewrite how
> > I do that. I based that stuff on the original isgui.py release.
> this is interesting cause start-stop-demon seems to do a stop if the demon
> was already running.

Well, I figured I'd call the one in init.d so it can do what it's got to do,
rather than trying to run /usr/bin/ipaq-sleep directly. But, it needs root.

>
> >
> > I started implemented reading/writing the backlight values directly, as
> > you can see from the #ifdef READ_BACKLIGHT stuff. Since I don't have the
> > kernel includes yet, I could not even compile that stuff to test it.
> > If/when I get the includes sorted out, I can make those changes in
> > gpe-config-sleep and gpe-conf/sleep if you like.
> Why. /usr/bin/bl is fine. I think you need root privilèges to set the
> backlight.
> keep bl is work.. :-)

Yea, I don't really care...I commented on it in another message to the list.

>
> >
> > Also, at some point we should probably implement setting the debug flag
> > and the X flag currently found in the configuration file, and the newly
> > gpe added battery_level flag. You can see the warnings when the
> > sleep-config initializes.
> > Screen real-estate is getting tight though. I
> > was originally thinking of a standard "main" screen and then an advanced
> > screen.
> I'm sorry, I cant understand the point..:-}

Well, the current version of ipaq-sleep has a configuration file with two
additional fields that weren't implemented in the isgui.py app. I based my code
on the isgui.py app. But, I knew that they were missing from the app. So, I
dump out a warning on stdout about such-and-such not configurable. This also
allows me/you/them to put in more features into the config file, and at least
somewhere notice that they aren't in the GUI. I noticed this when I took a peek
at the ipaq-sleep on the gpe cvs tree. It has a battery-level config option
now.

So, sticking on more toggle buttons all over the place makes the interface
quite cluttered. I was thinking about splitting up the interface to the "normal
- everyday" options, and another "advanced" screen to handle the, well,
advanced options. I'm not sure selecting which IRQ's ipaq-sleep will ignore is
an everyday kind of option.

But, now that "my" app is inside "yours", "we've" got to work out the screen
layouts and such. my/yours/we of course it's all written for "them" and fiddled
with by "all"

I already want to start a game.

__________________________________________________
Do You Yahoo!?
HotJobs - Search Thousands of New Jobs
http://www.hotjobs.com
Received on Mon Aug 19 16:50:17 2002