Ok.. will do.
Yeah, that widget test thingy seems pretty good to work
with... I will try it.
Thx, Bart
> I think the easiest way would be that you simply mail
your patches to this
> mailing list, or use the patch area at sourceforge.. We
can then see if the
> patch isn't breaking any windows/linux code and then use
it in the DynAPI.
>
>
> You could use the test code I mailed to this list a few
days ago and see how
> far things run on the Mac.. still some "deeper" code
isn't included in the
> test so they would need other testing, but using the
different widgets
> usually seem to be a good way of testing things aswell.
>
>
> Pascal Bestebroer
> pb...@oi...
> http://www.oibv.com
>
>
> -----Oorspronkelijk bericht-----
> Van: dyn...@li...
> [mailto:dyn...@li...]Namens
Barre Bizon
> Verzonden: donderdag 16 november 2000 14:40
> Aan: dyn...@li...
> Onderwerp: Re: RE: [Dynapi-Dev] Default
>
>
> Yeah.. I see what you mean :)
>
> Sure, as I say I have a mac at work and I am in the
process
> of converting to dynapi2.
> Although I am not too fond of the mac and especially all
> the f***** problems/bugs that browsers on that platform
> have, I am quite cabable of debugging stuff on it; as it
is
> part of my job :)
> So I'm totally up for hacking the mac to pieces.
Literally.
> Heh
> I will however try stuff on a PC first and foremost.
>
> Anyway, how do you want me to go about it, sending reports
> or files or whatever?
>
> /Bart
>
> >
> > Answer:
> > Yes it is an integral part, but as you already mentioned
> > there is modularity, and also the fact that you might
want
> > to use your own browser detection or another browser
> detection
> > in the future (just an idea :)
> >
> >
> > It's great that you have a Mac, and hopefully you'r
> capable
> > of debugging javascript because I tried to do it a
couple
> of
> > times with people who own a Mac, they would tell me the
> errors
> > and I'd try to fix them one by one... and that doesn't
> work, so
> > we really need someone who can hack it on a Mac.
> >
> >
> >
> > Pascal Bestebroer
> > pb...@oi...
> > http://www.oibv.com
> >
> >
> > -----Oorspronkelijk bericht-----
> > Van: dyn...@li...
> > [mailto:dyn...@li...]Namens
> Barre Bizon
> > Verzonden: maandag 13 november 2000 13:47
> > Aan: dyn...@li...
> > Onderwerp: [Dynapi-Dev] Default
> >
> >
> >
> > Question:
> > Shouldn't browser.js be included by default when you
> create
> > dynlayers?
> > I mean it is an integral part of the DynAPI and cannot
be
> > left out...
> > And as far as keeping modularity.. ok.. but it really
> seems
> > reduntant to always include browser.js as practically
> > nothing will work without it...
> >
> > Maybe I'm missing something, though, as I'm just
starting
> > to check DynAPI2 out. :)
> >
> > Oh and by the way,I have access to a mac (I have it as a
> > testcomputer at my work desk) so I could help with the
> > development for mac.
> > I have worked extensivly with a modified version of the
> > first dynapi before, including the creation of a text
> > dropdown menu with extensive platform support.
> > I even made a simplified scroll that works with mac.
> >
> > checkout
> > http://www.saabusa.com/home/US/en/95_intro.xml
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
> >
> > _______________________________________________
> > Dynapi-Dev mailing list
> > Dyn...@li...
> > http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
> >
>
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
>
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev
|
