Re: [Sawfish] Re: Porting Sawfish to Racket

[POMPEE William <william.pompee@xxxxxxxxx>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 11/11/2012 04:33, Laurent wrote:
> Dear Sawfish and Racket users,
> 
> After roughly estimating the effort required to port Sawfish to Racket (
> http://sawfish.wikia.com/wiki/Porting_Sawfish_to_Racket ), I found that it
> would be too much work and would probably not be the best option. The
> effort required before having anything usable would just be too big. So I
> started a new project from scratch ( https://github.com/Metaxal/RWind/ ),
> which is currently in a minimal but usable state (for testing purposes).
> Even though it's not Sawfish, it's aimed at being very similar to it
> (extensibility, scripting in Scheme, console, etc.), but of course its
> current state is nowhere near Sawfish.
> 
> However, I believe its development should be greatly simplified thanks to
> Racket and DrRacket and its wonderful debugging messages and facilities
> than using C and Rep. It avoids C altogether thanks to Jon Rafkind's X11
> bindings using the foreign function interface (
> https://github.com/kazzmir/x11-racket , which also provides xlambda, a
> simple rewriting of xmonad, due to Kevin Tew).
> 
> I'm going to run low on spare time, so anyone willing to help (even with
> very small increments) is welcome. And of course I can help anyone wanting
> to get started but doesn't know where to begin. Critics and ideas are also
> welcome (now is a good time for them, later may be too late to change
> things).
> 
> Cheers,
> Laurent
> 
> 
> On Thu, Oct 25, 2012 at 1:12 PM, Laurent <laurent.orseau@xxxxxxxxx> wrote:
> 
>> (cross-post sawfish, racket)
>>
>> Hi all,
>>
>> Only very recently have I discovered the excellent, simple and lispy
>> window manager Sawfish ( http://sawfish.wikia.com/ ), after being
>> frustrated with Compiz and Metacity and wanting to do what I really want to
>> do with my windows (tried xmonad, wished it would force me to learn
>> Haskell, but couldn't stand the syntax. Plus it seemed too constrained to
>> me).
>>
>> However, Sawfish uses an outdated and specific Scheme-like language named
>> Rep, and the maintainers are currently looking for a replacement with less
>> flaws and which would be better and actively maintained.
>> Racket ( http://www.racket-lang.org/ ) has been suggested on several
>> occasions, among other languages (e.g., Chicken, or even Python).
>> I personally love Racket and would be very happy to have it in Sawfish
>> (actually I want a Racket-machine), especially when it comes to debugging
>> (couldn't yet figure out a good way to do that cleanly).
>>
>> Although there is little chance (unfortunately) that I can/will invest a
>> lot of energy and time in trying to port Sawfish to Racket, I figured that
>> if I could help the process a little, things may move slightly faster. So I
>> started a page on Sawfish's wiki to try to evaluate what needs to be done
>> and what are the biggest problems to solve:
>> http://sawfish.wikia.com/wiki/Porting_Sawfish_to_Racket
>>
>> It's currently in a stub state, but I will add information with time as I
>> use and understand Rep (and Racket better). But there are people out there
>> who know one or both of them better than me, so please contribute to the
>> page as you see fit.
>>
>> My $0.02, waiting for the ultimate window manager,
>> Laurent
>>
> 

Hello Laurent,

Why do you think starting from scratch cost less than porting Sawfish to
Racket? Why do you think that a project Racket dependent is better than
being based on Rep? From a language point of view Guile seems to be the
only Scheme interpreter currently bound to GTK+. I don't think it's
really relevant to switch from a Scheme-like interpreter to something
else without gain in portability.

Regards,

POMPEE William
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJQn4XXAAoJED2RVhds6ZJlfocP+gMb9FneqEao2BiizjGrDcA7
fmHvQF8SJHkEL3Nk3DL5ysYc+jlvZOjYf2P6B/3neG7B1+31wWlnGEV0aKHBIR+Y
EGHhp3N10b+GqWsCa316KPC5qYqExej/S6fsqHNisPRJ0G2XSmqIMTIqTZO07eEe
8qsamV2V0mkNSsu4b8OyEErbj8rgwywEW2XQjBWjnf4uk0ORUBietBEsaYs7xelQ
zae53Fhsylwa3GQ25p3VgdUrrbBAxY9Poyls36h8sOnBVkZ6f8evwVroKpm4dGYX
86eaKmchRHz3OilQwF9MGJIyQTXW73TadzZjNVDXA/EPET0flAHYi66b9/LUSQnY
RELgD2SedLJJpzZHHz/GP5OyyRV122FuKnXLDkhUFxTaezJJ99oc8gp5AqTSXHOo
eezUtiwIWwt2KzY5H8aXn0LvFQK6KrTXztA8oiAdsnsMfbYA0nt6vxkTU76jTN36
YUl4leQ5stZB/vMQLb5QOflm3P1vqyqD/S7EAZ6F4Xe4zQXc65SHdEYlXstfQOzl
jXGNLPMxlZumgc9kK66O+UGkGtjzsewFUMmwfCuy/uQ467s624XA5D0wh+U48irn
uC9s8883R1ijpGHFegwGFPfahBHYI+8UYhcCbwpkQIwll3ms7Yl9d2VWQCZEXi9M
LfjL/I2RCGiWl7Ns/NZL
=aNRj
-----END PGP SIGNATURE-----

Attachment: 0x6CE99265.asc
Description: application/pgp-keys

Attachment: 0x6CE99265.asc.sig
Description: PGP signature