From mint-bounce@lists.fishpool.fi Thu Feb 4 02:47:54 2010 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=DXZhAHGq7gf2qE7FYrAoGdnPsbcCSnhYvqm0fd/Lmtk=; b=qN2OGAdol6/LNBFzf/+O/Bp0C79sZXxwz10ysnj2b2AlaK9KzaLHwO0Q9YHe8kGmHb UpQKSrJQSblR/jZ0lsw6gQFiL+v+MfLNaQU92j3rljx8qOe686io+kytIaOrkFSXP6PR zWkE3WUyZWybrXIlCRR0b6lsOZE5/QrgCGl/M= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=D3w3Bu5zfzQJlCfcfqpz+Q+lU+jLuGf6LGUEpwt2qliQA0Uo4XXVDzjqRDBf7557gz ffg1YbTmP1pNv+6dvWOvyYxXDYBdI10/gsmhFJCxRUwxDPT0sk3w2e1hdh1zB4ul1uE6 RCmv0Hf72aY438oQFfvmA5P2jG+PeTYg1QOXg= MIME-Version: 1.0 In-Reply-To: <4B69F3D9.5020009@online.no> References: <00033c8b.019e5d1c981c@mail.gmx.net> <4B69EE78.4020305@online.no> <4B69F3D9.5020009@online.no> Date: Thu, 4 Feb 2010 01:45:56 -0600 Message-ID: <11a6f2b11002032345t70af749du78457068a4360c8f@mail.gmail.com> Subject: Re: [MiNT] Daily freemint kernel builds From: Paul Wratt To: mint Content-Type: text/plain; charset=ISO-8859-1 X-ecartis-version: Ecartis v1.0.0 Sender: mint-bounce@lists.fishpool.fi Errors-to: mint-bounce@lists.fishpool.fi X-original-sender: paul.wratt@gmail.com Precedence: bulk List-help: List-unsubscribe: List-Id: X-List-ID: List-subscribe: List-owner: List-post: On Wed, Feb 3, 2010 at 4:08 PM, Jo Even Skarstein wrote: > Helmut Karlowski wrote: > >> I don't know much about that protocol but then I'd prefer to remove any >> blocks when the fileselector is called, seems more efficient: a few new >> lines of code vs. a new protocol ... > > True, but the big difference is that the Selectric protocol allows > multiple files to be selected. Personally I find myself using drag'n > drop (or the AV-protocol) more than the fileselector, so for me it > doesn't make much difference :-) > > Jo Even > Also, according to the code, XaAES de activates thrid party FS, so at least allowing for Selectric would allow for certain other FS by default. I would still look at the unblocking too, as MyAES does. But there is also quite a bit of work needed on enhancing the FS itself So again, its not about any one solution, obviously some work is more extensive that others, but ultimately, all is needed, to bring up the compatibility BTW some similar steps need to be taken with AES calls and AES objects, but that is for another thread Paul