perlwm-develop — Development of perlwm

Re: [perlwm-develop] Re: Hmm... Another roundof patches

[Michael B. <mb...@be...>]

On Tue, 22 Aug 2000, Rich Williams wrote:
> > Okay what is the prefered way of submitting patches for this? Continue
>  > uploading all relavant files?
> Er. I'm not sure. I guess you could just check stuff in if your CVS is
> working. Or maybe we could try and use the patch manager. 

My cvs is working now .. I'm not sure what it was .. but i don't trust the
box i was using before, I didn't set it up so its correctness is questionable in
my mind ... It works on my box at home though, so all is good.

>  > I did notice that on this newer version Clicks to a window don't make it to a
>  > window .... this is a problem :) ...
> Does your config stuff cope with the '+click' stuff. The '+' means pass
> this event through to the client (replay it). Click throughs work for
> me, so that might be it.

That might be it .. i tihnk it might be dropping the "+" .. Ah ... I see my bad
... I'll fix that and get it to ya in the next round.

> Hmm. That's really odd. What version of Perl do you have? It works for
> me, but I'm using 5.6 so the MakeMaker might be a bit broken somehow. 

I never bothered upgrading perl .. I have redhat 6.0 and upgraded everything,
except my compilers ... I've always been under the impression that programs
should compile backwards as well :)

> I still think native perl would be nicer :-) Simple enough format for
> users to learn, they don't need to know perl, since it's fairly
> intuitive :-
> $RootMenu = [ 'XTerm' => 'exec xterm',
> 	      'XEmacs' => 'exec xemacs',
> 	      'Graphics' => [ 'Gimp' => 'exec gimp',
> 			      'xv' => 'exec xv' ] ];
> 
> $Fonts = [ 'title' => 'lucidasans-14',
>            'title_focus' => 'lucidasans-bold-14' ];
> 
> $Colors = [ 'frame' => 'grey75',
> 	    'frame_focus' => 'white' ];

I think we should support both ... I'll put together the code to take striaght
perl for config and menus tonight and finish it up tommorow ... shouldn't be
difficult.

I'm also wanna move the menuing system out ot a module ... (different sytles of
menus should be an easy thing to add via modules i think)... but i think it
should be working first fully first ... 

Only things witht hat i forsee having trouble with is making it pop up at the
mouse pointer and making the windows pop-up next to each other ... I intend to
figue out both of those this week :)

mike 

ps: I'm sorry about my ignorance on things dealing with X ..  And my instance on
details like the menus and config ... I've learned for experience .. that
getting this stuff right from the begining and leaving it open for many options
can only help in the long run.

[perlwm-develop] Re: Hmm... Another roundof patches

[Rich W. <rd...@im...>]

 > Okay what is the prefered way of submitting patches for this? Continue
 > uploading all relavant files?

Er. I'm not sure. I guess you could just check stuff in if your CVS is
working. Or maybe we could try and use the patch manager. 

 > I did notice that on this newer version Clicks to a window don't make it to a
 > window .... this is a problem :) ...

Does your config stuff cope with the '+click' stuff. The '+' means pass
this event through to the client (replay it). Click throughs work for
me, so that might be it.

 > ALSO imlib2-perl : the makefile.pl fails on a build with this error
 > 
 > package ExtUtils::MakeMaker::_version;
 >             no strict;
 > 
 >             local $VERSION;
 >             $VERSION=undef; do {
 >                 our $VERSION = '0.01';
 >             }; $VERSION
 >         ' in Imlib2.pm: Can't modify subroutine entry in scalar
                           assignment at (eval 7) line 7, at EOF

Hmm. That's really odd. What version of Perl do you have? It works for
me, but I'm using 5.6 so the MakeMaker might be a bit broken somehow. 

 > thats all for now ... I'll try to hack out some of the little problem in the
 > windwomanager tonight so i can finisht he menus .. but i have my doubts on
 > success there :)
 > 
 > everything (config wise) seems to load fine ... lemme know what you think of
 > the menu file format ... I'd like to do a simular file to load the other menus
 > .. make it easily user configurable...

I still think native perl would be nicer :-) Simple enough format for
users to learn, they don't need to know perl, since it's fairly
intuitive :-

$RootMenu = [ 'XTerm' => 'exec xterm',
	      'XEmacs' => 'exec xemacs',
	      'Graphics' => [ 'Gimp' => 'exec gimp',
			      'xv' => 'exec xv' ] ];

$Fonts = [ 'title' => 'lucidasans-14',
           'title_focus' => 'lucidasans-bold-14' ];

$Colors = [ 'frame' => 'grey75',
	    'frame_focus' => 'white' ];

Have fun,

Rich

[perlwm-develop] Hmm... Another roundof patches

[Michael B. <mb...@be...>]

Okay what is the prefered way of submitting patches for this? Continue
uploading all relavant files?

Anyway this is the new perlwm.pl with the config file hack and the root menu
hack.

The root menus aren't completely done, mostly because of windwo manager
limitations ... Right now they aren't set up for anything but the root menu,
however it just requires changing a couple lines ... no biggie.

Again .. I changed the split(/ /, $bind) to split on "_"'s again .... If this
is a problem lemme know .. was just trying to save a little work.

I did notice that on this newer version Clicks to a window don't make it to a
window .... this is a problem :) ...

ALSO imlib2-perl : the makefile.pl fails on a build with this error

package ExtUtils::MakeMaker::_version;
            no strict;

            local $VERSION;
            $VERSION=undef; do {
                our $VERSION = '0.01';
            }; $VERSION
        ' in Imlib2.pm: Can't modify subroutine entry in scalar assignment at (eval 7) line 7, at EOF


thats all for now ... I'll try to hack out some of the little problem in the
windwomanager tonight so i can finisht he menus .. but i have my doubts on
success there :)

everything (config wise) seems to load fine ... lemme know what you think of
the menu file format ... I'd like to do a simular file to load the other menus
.. make it easily user configurable...

l8r

mike

[perlwm-develop] Re: X questions

[Rich W. <rd...@im...>]

Michael, 

 > Would that be all that is needed for that action to take place ... or am i 
 > missing something else where?

You missed something, but it wasn't at all obvious. I've added the
extra bits of code to perlwm and checked it in. You might be able to
apply the patch to the old version, but I'm not sure. 

The other bits needed were setting up all the grabs on the root window
and translating the textual button info into the right values. There
were also some bits from all the event testing (couldn't handle an
event which wasn't associated with a client).

Have fun,

Rich

[perlwm-develop] I'm a dumb ass .. X questions continued

[Michael B. <mb...@be...>]

first off, i'm osrry for sending that last email, i'm on a windows box 
rioght now, and it sent it when i hit ctrl+e, meanign to go to the end of 
the line

Okay, for those of you that don't know, my knowledge of how X works is 
lacking considerable ... But i learn fast, os all will be good .. jsut bare 
with me as I learn the basics...
Currently I need to know when the root window is clicked on, and how. From 
looking at the perlwm code, i gather that is handled in this section:

if ($e{event} == $c->{frame}) {
# the event got delivered to the frame
if ($e{child} eq 'None') {
# nobody else was involved
$context = 'frame';
}
else {
# some child window was involved
# TODO: in future, the frame might have more than one child!
$context = 'window';
}
}
elsif ($e{event} == $c->{win}) {
# the event went to the window
$context = 'window';
}
And I need to ad something like:
elsif ($e{event} == $c->{root}) {
# the event went to the root
$context = 'root';
}
....
Then I would need to ad a binding, like:
root => { 'Button1' => 'root_menu'}

then add an action like:

root_menu => {display => \&display_menu}


...

WOuld that be all that is needed for that action to take place ... or am i 
missing something else where?

thanks,

Mike
mb...@be...

[perlwm-develop] X Questions

[Michael B. <mb...@be...>]

Okay, for those of you that don't know, my knowledge of how X works is 
lacking considerable ... But i learn fast, os all will be good .. jsut bare 
with me as I learn the basics...

Currently I need to know when the root window is clicked on, and how. From 
looking at the perlwm code, i gather that is handled in this section:

      if ($e{event} == $c->{frame}) {
       # the event got delivered to the frame
       if ($e{child} eq 'None') {
	# nobody else was involved
	$context = 'frame';
       }
       else {
	# some child window was involved
	# TODO: in future, the frame might have more than one child!
	$context = 'window';
       }
     }
     elsif ($e{event} == $c->{win}) {
       # the event went to the window
       $context = 'window';
     }

And I need to ad something like:

    elsif ($e{event} == $c->{root}) {
       # the event went to the root
       $context = 'root';
     }

....

Then I would need to ad a binding, like:

root => { 'Button1' => 'root_menu'}

[perlwm-develop] hello

[Michael B. <mb...@be...>]

Just a test ... hello all ...

--
mike

mb...@be...

[perlwm-develop] CVS updated

[Rich W. <rd...@im...>]

All,

I've finally updated CVS with my changes. CVS should now reflect the
contents of the tarball in the FTP area.

Have fun,

Rich

[perlwm-develop] Re: Morning

[Rich W. <rd...@im...>]

Jay McCarthy writes:
 > This is my first post.
 > Just letting you know i'm out here.

Excellent. How did you get on with the tarball?

Rich

[perlwm-develop] Morning

[Jay M. <Jay...@c-...>]

This is my first post.
Just letting you know i'm out here.


Jay

[perlwm-develop] Welcome to perlwm-develop!

[Rich W. <rd...@im...>]

Hi,

Welcome to perlwm-develop. This mailing list is for the development of
PerlWM. The project home page is http://perlwm.sourceforge.net/

Have fun,

Rich