Re: [cssed-devel] Just one more thing to cssed 0.3.0

[Iago R. <iag...@hi...>]

On Wed, 2004-09-22 at 11:47, Mich=C3=A8le Garoche wrote:
> Le 22 sept. 2004, =C3=A0 11:38, Iago Rubio a =C3=A9crit :
> >>> I also expect more menu based plugins when I fix menu access, and=20
> >>> more
> >>> non ui plugins as file managers and css dialogs.
> >> Yes, of course, but anyway, all plugins must follow the principle that
> >> their ui must fit on a 640*480 screen. Or 800*600 screen.
> > For this release we will leave a 800x600 requirement. Nwxt version
> > should fix this problem with toolbars.
> > I can also one drop button to put the panels ones into.
> OK, did you commit it?

No, I'm working in the Win32 port - almost done, changes in CVS - and
can not change the two source trees at the same time.

If cssed fits in 800x600 no change will be done before the release. If
doesn't fits in 800x600, will go for the quickest/easiest solution,
instead of rewritting the GUI.

The next release will fix all those issues.

> > There're some functions for that in the API y can compare the width of
> > the GtkToolbar with the width of the given screen (X screen being=20
> > used).
> > The problem is not how but when. In X server platforms, you can use an
> > application and move it throught more than one screen.
> > I mean a user with two - or three - screens can switch the app from one
> > to other. One screen can be running with at 640x480 and other at any
> > other screen resolution supported by the video card.
> > So if I check the length on startup, it can vary when moving throught
> > screens so it'll be bogus.
> > What I don't want to do, is to waste resources checking the length of
> > the screen at any window move/resize.
> Oh, yes, that's too complicated. But if we limit the check to our=20
> 640*800 screen,
Wow !!!

	+----------+
	|          |
	|          |
	|          |
	|          |
	|          |
	|          |
	+----------+

Really strange screens on Macs ;))

> would not it be sufficient? I mean build the toolbars=20
> so that it fits on 640*800. Then no check in code while running.

If we make it fit in the minimun expected resolution (640x480 in our
case). It will be OK, but users of longer screens will see cuted/small
toolbars and a bunch of them.

If we read the resolution on startup and fits the toolbars on it, when
the user moves the windows to another screen it will not fit if it have
a different resolution.

I must think on it.

Right now, the goal for me is to acomodate the main window on < 800x600.
--=20
Iago Rubio  =20
- Home page    * http://www.iagorubio.com=20
- Last project * http://cssed.sourceforge.net        =20
- GPG Keyserv  * pgp.rediris.es id=3D0x909BD4DD