[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] BubbleGEM

To: Jo Even Skarstein <joska@online.no>
Subject: Re: [MiNT] BubbleGEM
From: Peter Persson <pep.fishmoose@gmail.com>
Date: Sat, 8 Jan 2011 13:23:22 +0100
Cc: mint@lists.fishpool.fi
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:received:received:subject:mime-version :content-type:from:in-reply-to:date:cc:content-transfer-encoding :message-id:references:to:x-mailer; bh=ak/OfBqq/+Ni+t925lQps6+3hYGFFZUxQybiamCTbH0=; b=mHfXh6Es78MQyspm2HeXy/ISyAWjAjCNn+uAMoc83l3AOswEaa5L+9EdZLQzlzMAkC vL27iBsnl8VBADCEXLbVdenO0YEhMZKAD0d663ZSZzs92h22yMDpyNP8+HxMI7XPGeP7 YfTt+r8XFxaWj3ltvWyN3RsZVaty87fpq6eEw=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=subject:mime-version:content-type:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to:x-mailer; b=DItPDvYSfp+y7g8Q//dSnakb71mgOdGnWlr9Vs3I6dawTftJVhtgRlWCmYMozB0y85 MxMt+xewMrMo1ZLiQQtoNrOXHlfHLi+h1LcDlCtbjuNdwjawl5QeFXoZPjLAFtOvv4zW /JJKLfl1YL3HW0Kdwrd9D1m8cTqzOpziw4q8s=
In-reply-to: <1294468582.1863.7.camel@sterkenils>
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-id: <mint.lists.fishpool.fi>
List-owner: <mailto:tjhukkan@fishpool.fi>
List-post: <mailto:mint@lists.fishpool.fi>
List-subscribe: <mailto:mint-request@lists.fishpool.fi?Subject=subscribe>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
References: <000a2c33.01c775f81911@smtp.freeola.net> <1294435619.2018.28.camel@sterkenils> <AC5BE0D6-E2F2-49BB-A485-D5C8EFFCFEF4@gmail.com> <1294468582.1863.7.camel@sterkenils>
Sender: mint-bounce@lists.fishpool.fi

8 jan 2011 kl. 07.36 skrev Jo Even Skarstein:

> On Sat, 2011-01-08 at 00:58 +0100, Peter Persson wrote:
> 
>>> Is there an advantage of integrating it with the AES? A windowed
>>> replacement shouldn't be hard to write, after all it's just a matter of
>>> displaying up to 256 characters of plain text.
>> 
>> There are a few standard add-ons on the platform for which there are well defined protocols. I think it would be nice to have those things in the AES, since they're defacto standard. However, I'm not asking anyone to do that for me :) I'm just saying it would be nice.
> 
> What is the advantage? IMO a BubbleGEM-replacement doesn't belong inside
> the AES anymore than e.g. TosWin does. Tooltip-functionality in the AES
> would be nice, but then implemented properly and not as a kludge.

I'm not familiar with the inner workings of BubbleGEM. Is it a kludge because the protocol/API itself is bad, or because of a bad implementation?

-- PeP

Follow-Ups:
- Re: [MiNT] BubbleGEM
  - From: Jo Even Skarstein <joska@online.no>

References:
- [MiNT] BubbleGEM
  - From: Peter Slegg <p.slegg@scubadivers.co.uk>
- Re: [MiNT] BubbleGEM
  - From: Jo Even Skarstein <joska@online.no>
- Re: [MiNT] BubbleGEM
  - From: Peter Persson <pep.fishmoose@gmail.com>
- Re: [MiNT] BubbleGEM
  - From: Jo Even Skarstein <joska@online.no>

Prev by Date: Re: [MiNT] IRC channel for MINT / Coldfire / ARanyM?
Next by Date: Re: [MiNT] wiki-conversion
Previous by thread: Re: [MiNT] BubbleGEM
Next by thread: Re: [MiNT] BubbleGEM
Index(es):
- Date
- Thread