Re: [circle] about separation between gui and core

[Thomas Mangin]

Hello Thomas V,

And good year 2004. I am happy to see that some of you still have some 
time to hack on circle .. Thank you for founding this lstrip bug in 
magic.py .. As it seems that no one complained since the last version, I 
will assume that it mean that the code finally work and will fix my own 
version of the code. I will still accept bug report for this part of the 
code but my I am sorry to report that it is now some time that I do not 
have any time for non-work-related projects.

I will give you my point of view, but feel free to do whatever you want 
with it as I will not have any time available to help anyone with some 
code anytime soon.

IMHO, circle primitive should be exported through a python module that 
any GUI (text, gtk, etc) can simply import. I can not see any reason for 
a socket. Having the code "available on request" is a bad idea as it 
mean that you still have the dependency within the circle core. I 
noticed that a python with threaded capacity is required to run circle, 
which make it impossible to use it even with the text interface under 
cygwin due to GTK.

As you may know I looked at http://www.twisted-matrix.org/ when I wanted 
to help and split the core from the GUI. Twisted does have a *superb* 
(and I mean it) design and event handling. Should you may want to have a 
look to save lots of time. But this is not my call. You may want to know 
that I am using twisted at work and that my colleague and I are more 
than happy with it.

For the nameserver, I would  take another approach as AFAIK the chat and 
nameserver are GUI independent. You only need to initialise the code 
when you need it. So the initialisation of the code could be done within 
the GUI but the module themselves could be in core.

Good luck

Thomas Mangin