Re: [lyntin-devl] Anyone still using or working on Lyntin?

[will <wi...@bl...>]

I think what Brazen is doing is really neat.  Lyntin really sucks at 
multi-line handling.  It's one of the reasons that building an 
automapper is so difficult.  Josh wrote a plugin that does a herculean 
effort to connect commands with responses, but it's the kind of thing 
that would be better integrated in the core.  Also, Lyntin's handling of 
telnet sucked (for good reasons, but it still sucked) and makes things 
like ssh connections and handling for MCCP, MIP and other mud "markup" 
things difficult.

I'm psyched that someone is experimenting with these things.  I've 
submitted a patch to Leanlyn already and am watching the bzr repository 
on Launchpad.  I'll keep helping in the future, too.  For one thing, I'm 
very interested in building a curses ui.

As an aside, I'm really sorry that the Lyntin web-site sucks and that I 
haven't done anything Lyntin-wise in years.  I haven't mudded much in 
years either, so that's one of the reasons.  The other big reason is 
that nowadays, all my time is currently spent working on Miro 
<http://getmiro.com/> and PyBlosxom <http://pyblosxom.sourceforge.net/>.

/will


Brazen wrote:
> Many more people use lyntin than my client (i.e. more than just me).  So writing a lyntin plugin is a safe way to go.
> 
> As for why: I had piled enough stuff on top of lyntin that I had almost an entirely new client so I went and turned it into a new client.  The idea is to have a very small core API that is python calls all the way down.  The #command processor uses the same API as any input triggers you write (it just happens to have a higher priority by default).
> 
> Most lyntin commands aren't implemented because I don't use them.  If you send me your startup files I'd be happy to implement the ones you do use so you could give leanlyn a try.
> 
> -Brazen
> 
> --- On Tue, 6/23/09, Andre Miller <an...@an...> wrote:
> 
>> From: Andre Miller <an...@an...>
>> Subject: Re: [lyntin-devl] Anyone still using or working on Lyntin?
>> To: "Brazen" <odb...@ya...>
>> Cc: lyn...@li...
>> Date: Tuesday, June 23, 2009, 4:57 AM
>> Hi Brazen,
>> What was the design decisions for creating a
>> fork rather than creating a new UI and/or plugins for the
>> current Lyntin package? I very much like how Lyntin is
>> designed in that the engine is decoupled from the UI and
>> other modules which makes it very extensible. Is Leanlyn
>> also structured in such a way?
>>
>> What I'm actually asking is should I rather
>> be focusing my efforts into creating plugins for your
>> version of Leanlyn or the original Lyntin?
>> Regards,Andre'
>>
>> 2009/6/23 Brazen <odb...@ya...>
>>
>>
>>
>> I'm still working on a fork of Lyntin and I'm
>> publishing only so often as interest requires (Willg
>> contributed a patch, much appreciated).  You can find it
>> here
>>
>>
>>
>> https://code.launchpad.net/~odbrazen/leanlyn/trunk
>>
>>
>>
>> It currently only works with Tk and doesn't have good
>> trigger support.  About the latter: anyone could add it in
>> 20 lines of python but I don't need it so it doesn't
>> exist.
>>
>>
>>
>> The sexiest parts (automatic updating of player status)
>> currently only apply to three kingdoms and overdrive and
>> I've only partially migrated the custom code into robust
>> catchers ["catchers" being the token name for
>> multi-line screen scraping regexps].
>>
>>
>>
>>
>>
>>
>> Feel free to run it and give feedback.   I'm likely to
>> tackle any short task that makes somebody more likely to use
>> and/or contribute back to the core even if it is just a
>> couple screen scraping regexps for the /mudpacks directory.
>>
>>
>>
>>
>> -Brazen