{#} Replies are directed back to [EMAIL PROTECTED]
{#} To reply to the author, write to Eric Peyton <[EMAIL PROTECTED]>
This is very similar to the way that Proteus now works. If someone
wants to go and steal back all the code that Proteus took from Fire and
then turn their back end into our back end, fine, but neither Colter nor
I have had the time to do so yet ...
(Fire is built in a modular way, but the bundles have become somewhat
integral to the functioning of the app now ...)
Eric
On Friday, April 12, 2002, at 04:31 PM, David Remahl wrote:
> {#} Replies are directed back to [EMAIL PROTECTED]
> {#} To reply to the author, write to David Remahl <[EMAIL PROTECTED]>
>
>> Hey all,
>> I just had kind of a wacky idea while I was using screen. Screen is a
>> great program that enables me to leave an IRC client running, then ssh
>> from my work machine into my home machine and attach to it. My ability
>> to do the same on my Treo (with TGssh) led me to wish there were some
>> way to attach to a Fire session. That, in turn, led to a wacky idea:
>> Would it be possible to split Fire into two pieces, a "back end" that
>> ran and connected to the various services, and then an interchangeable
>> "front end", consisting of, for instance, Fire's current GUI, a Palm
>> interface, a console interface, etcetera? This would allow, for
>> example,
>> someone to leave the back end running, and then connect into one's
>> sessions from a remote machine.
>> It'd obviously be difficult to implement from where Fire is now, but I
>> just thought it'd be interesting to ponder.
>> Charlie
>
> The linux IRC client licq is designed in this modal way. Most
> everything is
> a plugin. It is as you say very cool and powerful, and allows for great
> customizability and removes bloat. However, as you say, it would be a
> pain
> to implement as things currently are.
>
> / David
>
>
> {#} ----------------------------------------------------+[ fire ]+---
>
>
{#} ----------------------------------------------------+[ fire ]+---
