fpwm-devel — About the development of fpwm

Re: [Fpwm-devel] lpi file change

[Felipe M. de C. <fel...@gm...>]

Hi,

I removed many old files from fpwm. There are still some old files.

fpGUI will undergo many changes on the next few days, just warning.
Even base class names may change.

-- 
Felipe Monteiro de Carvalho

[Fpwm-devel] General development ideas

[Felipe M. de C. <fel...@gm...>]

Hello all,

Well, first I would like to say that starting with karmen was a big
mistake. The code is huge, because it=B4s X11 based, procedural and
generally speaking a mess.

So Daniel, you can stop converting those horrible files now =3D)

Basically drewski started from zero, and that isn=B4t a bad idea.

Also, I found a very simple wm made on Qt that can help us. Here is
the source code:

http://integrity.cvs.sourceforge.net/integrity/integrity/src/

or  sourceforge.net/projects/integrity/

fpGUI is very similar to Qt, so we can use it to find out which
special tricks were included on Qt to make it able to write WMs. Then
we can add those same tricks on fpGUI.

--=20
Felipe Monteiro de Carvalho

[Fpwm-devel] fpgui

[Andrew H. <And...@ao...>]

Hi,

I am going to make some patches for fpgui so we can more fully use the
widgets available and use it's event loop.

After I've done that. I'll start work on ICCCM and Freedesktop.org
window hints.



Andrew

[Fpwm-devel] lpi file change

[Felipe M. de C. <fel...@gm...>]

Hello,

I changed fpwm.lpi file. I checked for it to store local stuff (like
files open on the editor) on a separate lps file.

This avoids conflicts when commiting things, because the lpi changed
unecessarely.

so please upgrade,

thanks,
-- 
Felipe Monteiro de Carvalho

[Fpwm-devel] Framework added

[Andrew H. <And...@ao...>]

Ok, I added what I've been working on the last day or so. It doesn't do
much but it does something :)

I've been testing it in Xnest.

Andrew

Re: [Fpwm-devel] Proposal

[Daniel F. <dan...@gm...>]

>
> Hi, I'm proposing the following structure for a window manager:
>
>
>  TWindowManager
>    TXWindowManager  // subclasses take care of the painting
>      TfpGuiWindowManager
>      TWhateverToolKitWindowManager
>
>
>  I'd like the feature of MDI
>
>
X Window is known for its lack of MDI....Kylix tried it with a hack....i
think we can do better....i kinda like the proposal altough my limited X
architecture knowledge does not allow me to give some sort of suggestion to
improve it...i will read something about it in the next days (holiday here
in Brazil)...any suggestions on this reading?!?!?

 Currently it is possible that a X11 server will have multiple screens.
>
>  To manage the windows the RootWindow of a screen is 'grabbed' by a
>  program (fpwm) to recieve map and other requests by possible clients.
>  Using objects I think it is possible to fairly easily add the capability
>  to manage windows within a client application.
>
>  Something like:
>
>  TRootWindow.Create(AScreen: PXScreen; AWindow: TWindow);
>
>  So AWindow can be the RootWindow of the screen or can be a TWindow
>  within an application. An application will have to send some sort of
>  request to make a window it owns a MDI parent or similar.
>
>
>  TXWindowManager will have a list of TRootWindows.
>
>  Thoughts?
>
>  Andrew Haines
>
>
-- 
Daniel

"Let us change our traditional attitude to the construction of programs.
Instead of imagining that our main task is to instruct a computer what to
do, let us concentrate rather on explaining to human beings what we want a
computer to do." (Donald Knuth)

"Yes, technogeeks can be funny, even if only to each other." (
http://www.boogieonline.com/revolution/science/humor/)"

"Man is driven to create; I know I really love to create things. And while
I'm not good at painting, drawing, or music, I can write software."
(Yukihiro Matsumoto, a.k.a. ``Matz'')

[Fpwm-devel] Proposal

[Andrew H. <And...@ao...>]

Hi, I'm proposing the following structure for a window manager:


TWindowManager
  TXWindowManager  // subclasses take care of the painting
    TfpGuiWindowManager
    TWhateverToolKitWindowManager


I'd like the feature of MDI

Currently it is possible that a X11 server will have multiple screens.

To manage the windows the RootWindow of a screen is 'grabbed' by a
program (fpwm) to recieve map and other requests by possible clients.
Using objects I think it is possible to fairly easily add the capability
to manage windows within a client application.

Something like:

TRootWindow.Create(AScreen: PXScreen; AWindow: TWindow);

So AWindow can be the RootWindow of the screen or can be a TWindow
within an application. An application will have to send some sort of
request to make a window it owns a MDI parent or similar.


TXWindowManager will have a list of TRootWindows.

Thoughts?

Andrew Haines