We have all these + more, except Panel
Normally the widget model seems to have gravitated towards what it is now,
the changes between last release and this one where not accidental, the
precreation code was introduced to speed loading time/memory use, once the
API stabilizes, the changes will indeed become less dramatic.
You are not comparing DynaCore (http://www.dynamic-core.net/) with DynAPI by
any chance? (which have different widgets)
Cheers,
Richard Bennett
[EMAIL PROTECTED]
www.richardinfo.com
(Everything running on, and ported to the 19/12/2000 snapshot of DynAPI2)
----- Original Message -----
From: "Alex Chong" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, February 09, 2001 4:05 AM
Subject: Re: [Dynapi-Help] true 9 browser support with dynAPI 2?
> Hi, thanks for the feedback.
>
> But the core set of widgets changes from release to release! More
importantly,
> the core set of widgets are incomplete and does not anticipate for widget
> development. A more concrete suggestion is to include most of the
'widgets'
> found in the AWT library of Java. For examples:
>
> 1. Button
> 2. Label
> 3. Panel
> 4. Scrollbar
> 5. Scrollpane
> 6. Window
>
> 7. LoadPane (which Dynapi already has)
>
> and most important of all, whereas the implementation of the core widgets
can
> change, the interface/functions of the widgets must never change.
>
> Alex Chong
>
> Richard Bennett wrote:
>
> > Well yes, of course you are right, but isn't that what we are doing?
> > There IS a base set of widgets included with the release, which have
been
> > updated, (button, list, dynimage, label, loadpanel, pushpanel,
scrollbar,
> > scrollpane, viewport etc)
> > <<or you can tag it as 'deprecated' like in Java
> > This is done already, for instance in the source of sprite.js.(in other
> > wording)
> >
> > Cheers,
> > Richard Bennett
> >
> > [EMAIL PROTECTED]
> > www.richardinfo.com
> > (Everything running on, and ported to the 19/12/2000 snapshot of
DynAPI2)
> >
> > ----- Original Message -----
> > From: "Alex Chong" <[EMAIL PROTECTED]>
> > To: <[EMAIL PROTECTED]>
> > Sent: Friday, February 09, 2001 3:18 AM
> > Subject: Re: [Dynapi-Help] true 9 browser support with dynAPI 2?
> >
> > >
> > > Hi,
> > >
> > > Ok, frankly speaking, I was discouraged by Dynapi sometimes but I do
have
> > high
> > > hopes for it. Before I put up my ideas, I would like to make clear
that I
> > have
> > > been following the forum discussion and read the f.a.q. (more than 2
times
> > for
> > > the faq).
> > >
> > > Here's my 5 cents worth: I think the frequent updates of the library
is
> > not a
> > > problem. The problem is actually the huge impact on the widgets when
> > Dynapi
> > > changes because every widgets extends/inherrits Dynlayer, which in
turn
> > uses the
> > > events....etc. There are many 'design patterns' that we can apply to
> > minimize
> > > the impact but since Pascal officially 'warned' me not to go into the
> > discussion
> > > of superclasses (Object Oriented Programming), I will avoid this
issues.
> > >
> > > How about this, we can define a set of widgets, let us call them the
Core
> > > Widgets. For each release of Dynapi2, we make sure that this set of
Core
> > > Widgets get updated. In this case, developers (like me, at least) can
> > use, not
> > > only Dynlayer, but also the Core Widgets as a foundation to build
other
> > fancy
> > > widgets.
> > >
> > > State for example, the Core Widgets can be: DynButton, DynLabel,
> > DynScrollbar,
> > > DynPanel...etc.
> > > Then I can build a calendar widgets that inherrits DynPanel, and uses
lots
> > of
> > > DynButtons in it so that when user clicks on a day, the particular day
> > will be
> > > highlighted and so on. In this case, even if there are major changes
to
> > the
> > > events and Dynlayer, my calendar widgets will still work, as long as
the
> > new
> > > release of the library comes with the corresponding set of
CoreWidgets.
> > >
> > > This idea can then be extended to having a DynLayerInterface class
which
> > > internally uses DynLayer. In this case, DynLayer will do all the
dirty
> > works
> > > trying to perform different operations for different browsers.
> > > DynLayerInterface on the other hand, have a set of functions like
setSize,
> > > setWidth, addMoustListener....etc that never change (because all these
> > functions
> > > do is to call the equivalent functions in DynLayer). As a widget
> > developer, all
> > > we do is that we inherrit from DynLayerInterface rather than DynLayer.
> > From
> > > time to time, DynLayerInterface may have added functions but the old
ones
> > > definitely remains (or you can tag it as 'deprecated' like in Java).
Then
> > at
> > > least we know that our widgets will work for at least a few release of
> > future
> > > DynApi2.
> > >
> > > Comments appreciated.
> > >
> > > Alex Chong
> > >
> > > Pascal Bestebroer wrote:
> > >
> > > > For one, Mac browsers are not fully supported (Mac problems)
> > > >
> > > > Alot of the widgets and other examples might actually brake because
of
> > > > problems with the Widgets.
> > > > I understand that most people still think Widgets ARE the DynAPI,
but at
> > > > this point Widgets are extensions / examples of DynAPI code. Seeing
that
> > the
> > > > DynAPI code is still being worked on and changed/modified/updated
> > Widgets
> > > > might work one day , and fail another.
> > > >
> > > > I don't think that making comments like "this is very discouraging"
do
> > > > anything at all (at least not for me) this is Opensource, so
EVERYONE
> > could
> > > > help fix problems.. There are some very skilled developers working
on
> > this
> > > > project, and I truly believe that eventually a 100% working DynAPI
will
> > be
> > > > produced.... for v5- browsers.. v6+ browser will then be the next
> > problem to
> > > > tackle.
> > > >
> > > > Another thing about your mail, if you make comments like these,
please
> > show
> > > > us the problems your having.. and make sure to have read the f.a.q.
and
> > > > tutorials. (maybe we should make these things available as the first
> > thing
> > > > people see on the dynapi site)
> > > >
> > > > anyway for now read the faq at
> > > > http://www.dynamic-core.net/core/files/faq.dynapi2.html for more
info on
> > the
> > > > DynAPI2.
> > > > there are also tutorials available at sourceforge, but they seem to
be
> > > > broken because of sourceforge.
> > > >
> > > > And I can safely say that the main core of the code will work on
> > > > IE4,5,NS4,NS6 at least on Windows (and I think Linux) .. there will
> > ofcourse
> > > > be bugs, but without the DynAPI code you'll have a much harder time
> > getting
> > > > things to work cross-browser.. because browsers are very
discouraging.
> > > >
> > > > (guess these comments DO get to me :)
> > > >
> > > > Pascal Bestebroer
> > > > [EMAIL PROTECTED]
> > > > http://www.dynamic-core.net
> > > >
> > > > > -----Oorspronkelijk bericht-----
> > > > > Van: [EMAIL PROTECTED]
> > > > > [mailto:[EMAIL PROTECTED]]Namens Elisabet
Frazer
> > > > > Verzonden: donderdag 8 februari 2001 17:32
> > > > > Aan: dynAPI help
> > > > > Onderwerp: [Dynapi-Help] true 9 browser support with dynAPI 2?
> > > > >
> > > > >
> > > > >
> > > > >
> > > > > Hello,
> > > > >
> > > > > What I don't get is if and if not (and if not, so why not), the
aim
> > for
> > > > > dynAPI 2 is to support major functionality in (at least)
> > > > >
> > > > > Internet Explorer 4 Windows
> > > > > Internet Explorer 4.x Mac (4.0 can be omitted in IMHO)
> > > > > Netscape 4 Windows
> > > > > Netscape 4 Mac
> > > > > Internet Explorer 5 Windows
> > > > > Internet Explorer 5 Mac
> > > > > Internet Explorer 5.5 Windows
> > > > > Netscape 6 Windows
> > > > > Netscape 6 Mac (More or less the same?)
> > > > >
> > > > > I regard Opera and iCab support as luxury at the time being.
> > > > >
> > > > > Why do I get the impression most people really don't care to tell
> > which
> > > > > browser can't show a specific implementation of dynAPI 2? So many
> > > > > examples break without comment and this is very discouraging.
> > > > >
> > > > > WonderGirl
> > > > >
> > > > > Elisabet
> > > > >
> > > > >
> > > > > _______________________________________________
> > > > > Dynapi-Help mailing list
> > > > > [EMAIL PROTECTED]
> > > > > http://lists.sourceforge.net/lists/listinfo/dynapi-help
> > > > >
> > > >
> > > > _______________________________________________
> > > > Dynapi-Help mailing list
> > > > [EMAIL PROTECTED]
> > > > http://lists.sourceforge.net/lists/listinfo/dynapi-help
> > >
> > >
> > > _______________________________________________
> > > Dynapi-Help mailing list
> > > [EMAIL PROTECTED]
> > > http://lists.sourceforge.net/lists/listinfo/dynapi-help
> > > ____________________________________________________________
> > > Get your free domain name and domain-based e-mail from
> > > Namezero.com. New! Namezero Plus domains now available.
> > > Find out more at: http://www.namezero.com
> > >
> >
> > _______________________________________________
> > Dynapi-Help mailing list
> > [EMAIL PROTECTED]
> > http://lists.sourceforge.net/lists/listinfo/dynapi-help
>
>
> _______________________________________________
> Dynapi-Help mailing list
> [EMAIL PROTECTED]
> http://lists.sourceforge.net/lists/listinfo/dynapi-help
> ____________________________________________________________
> Get your free domain name and domain-based e-mail from
> Namezero.com. New! Namezero Plus domains now available.
> Find out more at: http://www.namezero.com
>
_______________________________________________
Dynapi-Help mailing list
[EMAIL PROTECTED]
http://lists.sourceforge.net/lists/listinfo/dynapi-help
