From: | paul |
Date: | 23 Apr 2001 at 13:24:21 |
Subject: | Common misconception (was Re: Voyager Image Decoders) |
--- In amigactive@y..., Matt Sealey <matt@k...> wrote:
> Hello paul@l...
>
> On 23-Apr-01, you wrote:
>
> >> GPL schmePL. Zapek has an agreement with Olivier. As for "99%
> >> of his work", I think you'll find that it's been ported and
modified
> >> so much to work on an Amiga and inside the browser (although
> >> the plugin is quite capable of being standalone) that there are
> >> enough changes to make it 99% Zapek's work.
> >
> > Haha! Yeah, right! I know Oliviers code pretty well. It's well
> > written and would require *no changes* (but the latest versions
> > has an 'interesting' endian bug... :) - even if you needed to
> > embed it into a browser (in fact it comes with a NS plugin
> > example).
>
> Right. Remove every single function that relies on a POSIX library
> like ixemul. That's work.
It doesn't use any. ixemul is *not* needed (it compiles just fine
with libnix).
The player needs GetTimeOfDay() but that's often supported in the C
library or easily emulated via the timer.device.
> Modify it so that it can work with Amiga bitmaps like AGA by
> implementing fast chunkytoplanar. That's work.
WritePixelArray() is pretty fast (when patched :). Or use one of the
hundreds of C2P algoritms floating around and blit it into the
window. Not exactly hard stuff.
> Add some new features. You're right - change all those nasty endian-
> specific bits.
There isn't any. Except in the newer versions (and only in the
16/24/32bit mode - it assumes the data is stored GBR instead of
RGB). In fact the newer versions of the flash library don't support
anything less than 16bit!
> Use Amiga library functions, leverage the Voyager plugin API for
> things like colour specifications..
Oooh. That must be hard.
> .. you COULD compile an ixemul-requiring resource hungry, non
> plugged in application. In fact, that's what the plugin WAS in very
> early versions. As it stands, it's not that anymore.
As I said. It doesn't need ixemul. The X11 player uses precisely 1
function that is not implementated in GCC's standard C library
(ignoring the X11 stuff, which needs stripping out anyway).
> >>> IBrowse would have had a shockwave plugin 2 years ago if the
> >>> plugin API was released (that's assuming it's functional in
> >>> 2.2...).
> >>
> >> What "plugin API"? I didn't think there was one.. certainly
> >> nobody ever said anything of one.
> >
> > Indeed it has. I have some old source code that came with an old
> > beta IBrowse 2.0 (or 2.1?) but it's changed since.
> >
> > If you create a plugins directory and put a file there (with an
> > icon, contains settings) IBrowse at least trys to load it. Under
> > some circumstances anyway...
>
> Hmmn.. someone should poke Stefan to release this, no?
I have been for the past 2 years. I have a feeling that the plugin
stuff is incomplete in 2.2. 2.3 is supposed to have NetScape
compatable API (but I've not seen 2.3...).
Quote carefully and read all ADMIN:README mails
Your use of Yahoo! Groups is subject to http://docs.yahoo.com/info/terms/