> IMHO we can specify restrictions, e.g. an icon has to be <= 50x50
> pixels,a label not more than #num characters and so on. It cannot
> be expected
Not a bad idea, but the biggest problem I've seen yet is that some
themes don't play so nice with it - I think it's the font size
difference; If the individual launch pads (or whatever) where limited
to 80x80 (well, probably less) then it might behave nicer. Or we can
force the font size down maybe?
> that we deal with every possible and maybe insane combination.
> On the other hand it should still be as flexible as possible for
> exampleto be able to change aspect ratios (landscape <-> portrait)
> or other
> resolutions. The goal should be a system that can also run on new PDAs
> with bigger/smaller screens, other color depths, etc. (for example
> something like a web-pad or new mobile phones or ...).
Give it time, it's been around less than a week ;-)
I definitely agree with all of those points though.
Maybe we could use the VBox/HBox auto sizing thingy widget that the
gimp uses for its toolbox? That might solve all of the problems at
once...
> > > Oh, and it might be nice if it popped up some kind of error dialog
> > when it
> > > fails to launch an application.
> > It can't atm, it only calls system("program &") which always
> returns 0.
> > Later, it will. Or someone can do a patch and save me the
> trouble ;-)
>
> OK, I'll have a look at it. I already noticed that every started
> programis accompanied by an instance of "sh". A normal fork/exec
> cycle would be
> much better and not hard to add.
> I'll se what I can do and so you a patch ASAP ;)
That'd be great, thanks - I haven't ever looked into the exec*
functions much 'cos I'm slack and haven't ever needed more than system
().
mibus
Received on Mon Dec 31 09:03:15 2001
This archive was generated by hypermail 2.1.8 : Tue May 04 2004 - 09:41:27 EDT