dynapi-dev — List related to the current DynAPI Core development

RE: [Dynapi-Dev] inheritance crusade / SuperClass stuff

[<abe...@al...>]

> But isn't it better to use optimised versions for the browser, not
> the one for all?

It sound very interesting indeed Alexey... then you can also create new js
for newer browsers whithout any need to touch other js (just like dlls or
device drivers, you'll load what you need); it will allow you to reduce the
amount of code that the client most download and most important than that is
the fact that this code will be really very optimised. However this has an
important drawback that we most consider:

Doing this means an extra work in trying to maintain standardized all the
APIS for diferent platforms and diferent browsers, id est, if we add
something to an API we must add the same functionality to all other; and not
just that, separating everything so you can then optimize a lot, could make
easy a loss of control in what is disponible for what platform.

Im sure we don't want a DynAPI that says: "this is disponible only for NS"
or vice versa, then we most work a lot to keep things in the right path.

Any opinions or sugestions about this matter?, there is a lot of advantages
and drawbacks in a schema like this...

-----Original Message-----
From: dyn...@li...
[mailto:dyn...@li...]On Behalf Of Alexey
Medvedev
Sent: Jueves, 30 de Noviembre de 2000 10:42 a.m.
To: dyn...@li...
Subject: Re: Re: Re: [Dynapi-Dev] inheritance crusade / SuperClass stuff


On Thu, 30 Nov 2000, Barre Bizon wrote:

	Yes - I told it is JS_1.3_

> Another thing... neither the function.call() nor the
> function.apply() method work under IE4+.
> Unfortunately.

	Also add .watch() to the list :-/

 But isn't it better to use optimised versions for the brouser, not
 the one for all?

  So main "dynapi" whould be a selector of "dynlayer_ns4.js"
or "dynlayer_ie4.js" but keeping same API?

	I thinks using "new Layer" in NN4 is better then creating
 lots of CSS and <div>-s (memory usage and resistance to Resize):

	http://deep.kiev.ua/JS/WebGram/ - resize resistant without
 any reloads.

ps. last one i need to make site as one page , with changed layers
	Same as www.htmlguru.com is.

				Malx

_______________________________________________
Dynapi-Dev mailing list
Dyn...@li...
http://lists.sourceforge.net/mailman/listinfo/dynapi-dev

Re: AW: Re: [Dynapi-Dev] inheritance crusade / SuperClass stuff

[Scott A. L. <sc...@sc...>]

I hate to beat a dead horse here, but...:-)

Pascal's WidgetX model is perfectly fine for most applications of
DynAPI2.  For most apps there's really no need to go deeper than that. 
Most widgets I've seen inherit directly from DynLayer and go no further
than that, anyway.  It's well-documented and easy to understand.

On the other hand, if you prefer a stricter, Java-like inheritance model
without worrying about having to preserve methods and properties, try
using the SuperClass object.  It simulates OO very well, tracks class
instances, and manages super methods.  But it's a little more difficult
to use.

So there is a choice, and you're free to choose whatever suits your
task, or create an approach of your own.  I myself like the
possibilities of SuperClass but more often than not WidgetX suits my
needs just fine.  And I agree that bug fixing the API is more important
at this point than choosing "one true path" for a widget model.  A
correct widget model is one that works.

-- 
scott andrew lepera
-----------------------------------
web stuff:     www.scottandrew.com
music stuff:   www.walkingbirds.com

RE: [Dynapi-Dev] Widgit creation - Tab and Focus

[<abe...@al...>]

netscape...   yes you are right, it doesn't works in ns as it is now; but
let me see, maybe there is a way!
im working on it right now...

And dynamic objects can use this technic; if not, what is the purpose of
discussing this in the list?
However, if after some investigation it seems not possible to do something
similar in every browser supported by DynAPI then i'll just abdicate and
start over again with another idea. By principle, im just trying not to
overcharge things.

-----Original Message-----
From: dyn...@li...
[mailto:dyn...@li...]On Behalf Of Brandon Myers
Sent: Miércoles, 29 de Noviembre de 2000 09:54 p.m.
To: dyn...@li...
Subject: Re: [Dynapi-Dev] Widgit creation - Tab and Focus


  of course, that only works in IE. What about netscape? And what about
focusing dynamic objects?

  Let's work with the problem presented, and not provide a solution that
can't be used.

  Focus manager is easy when there is a "Helper" event watcher that will
capture events on all objects of a specific class.
    ----- Original Message -----
    From: Abel Eduardo Cantú Salas
    To: dyn...@li...
    Sent: Wednesday, November 29, 2000 10:09 PM
    Subject: RE: [Dynapi-Dev] Widgit creation - Tab and Focus


    Ups! this is a better version of test.htm     :D

    -----Original Message-----
    From: dyn...@li...
    [mailto:dyn...@li...]On Behalf Of Abel Eduardo
    Cantú Salas
    Sent: Miércoles, 29 de Noviembre de 2000 08:31 p.m.
    To: dyn...@li...
    Subject: RE: [Dynapi-Dev] Widgit creation - Tab and Focus


    related to the management of keystrokes, focus and blur events in
events.js
    ------------------------------------------------------------------------
----

    My idea is less complicated (i think) and requires fewer code. Instead
of
    creating a more complex object that manages a list of widgets and
bubbles
    the focus events, just leave the browser window take care of it.

    Here is an example using dhtm (not dynapi) IMPORTANT: it works only in
ie 5
    (i not warrant that this html will look fine in other browser, but maybe
ie
    5.5 or 4.x):

    see attached file.
    ------------------

    what im doing right now with dynapi is something like this:

    1) saving the original DynLayer createElement in a separated pointer
       (inherited_createElement) on my widget.
    2) overwriting this createElement method
    2.1) in this overwrote method i call the inherited_createElement
    2.2) after that, i add the anchor tag using insertAdjacentHTML method

    3) i think thats it!

    Everybody requiring this functionality just will need to base their own
    widgets on this one and Presto!, we have widgets that can take focus not
    just by clicking but using the tab key also.

    However we need to review events.js and add the capability to manage
focus,
    blur and keydown events so we can do everything just using common
    eventListeners, im still having problems there because it stills working
    only in ie. But i hope that somebody more familiar to ns will solve
these
    problems someday... What i need for now is get this thing working on IE
    under a Win environment a soon as posible: A widget that copies the
behavior
    of a TStringGrid (developers familiar with Delphi will know whats that)
and
    time is almost over!

    cheers guys!

    -----Original Message-----
    From: dyn...@li...
    [mailto:dyn...@li...]On Behalf Of Darin
    Kadrioski
    Sent: Miércoles, 29 de Noviembre de 2000 05:57 p.m.
    To: DynAPI Dev (E-mail)
    Subject: [Dynapi-Dev] Widgit creation - Tab and Focus



    Heya guys,

    Scott and I had a brief thread going last spring about having the
concept of
    "focus" shared amongst many widgits on the same page.
    This is to facilitate "tabbing" between controls and the blinking of
    "carets" for edits, etc...

    One thought was to have a global constructor that each widgit would
    "register" with.  The Dynapi would keep a list of the widgits in the
order
    they were created, this then becomes the "tab order".  Assuming we can
    successfully trap the tab key in both browsers, the dynapi would catch
it
    first before bubbling it to the widgets.  It would then send an OnBlur()
    event to whichever control currently had focus and an OnFocus() event to
the
    next in the list.

    Any thoughts on if this could be acheived?  Anyone else see the need for
it?

    Also, how about a "standard" construction call for widgit builders to
use?
    Something like create(x,y,w,h,fgcolor,bgcolor,skin)

    And maybe a set of standard events.
    refresh() comes to mind.


    -cheers!

    --------------------------------------------------
    Darin Kadrioski
    Applications/Internet Developer

    > Electronic Freight Exchange, Corp.
    dka...@ef...
    (916) 933-0724 x315

    _______________________________________________
    Dynapi-Dev mailing list
    Dyn...@li...
    http://lists.sourceforge.net/mailman/listinfo/dynapi-dev

Re: Re: Re: [Dynapi-Dev] inheritance crusade / SuperClass stuff

[Alexey M. <ma...@ca...>]

On Thu, 30 Nov 2000, Barre Bizon wrote:

	Yes - I told it is JS_1.3_

> Another thing... neither the function.call() nor the 
> function.apply() method work under IE4+.
> Unfortunately.

	Also add .watch() to the list :-/

 But isn't it better to use optimised versions for the brouser, not
 the one for all?

  So main "dynapi" whould be a selector of "dynlayer_ns4.js" 
or "dynlayer_ie4.js" but keeping same API?

	I thinks using "new Layer" in NN4 is better then creating
 lots of CSS and <div>-s (memory usage and resistance to Resize):

	http://deep.kiev.ua/JS/WebGram/ - resize resistant without
 any reloads.

ps. last one i need to make site as one page , with changed layers
	Same as www.htmlguru.com is.

				Malx

Re: Re: Re: [Dynapi-Dev] inheritance crusade / SuperClass stuff

[Alexey M. <ma...@ca...>]

On Thu, 30 Nov 2000, Barre Bizon wrote:

> didn't read my previous posts...

	sorry , I'm new here. Just look in some archive posts...

> Object orientation exists for a purpose, and no, Javascript 
> isn't  "true" OOP, but close enough to be able to use the 

	I am telling you that JavaScript is no _OOP_
 it is _OP_.
	It is not "oriented". It is true Object language.
 Ok - It is IMHO of course :)))
	But repaeting - JS is much more powerfull then Java/C++ OOP.
 So - I am very upset you trying to limit it to OOP you know how
 to work with instead of learning JS!!!  :-/

> I thought creating a constructor method was a clean and 
> easy way of doing "extended" functions initialization.

	As for OOP - the only way.
  As for JavaScript - the worst way. Yes it is included in JS1.3
 for thouse who likes "Java" , but....

> But sure, assigning DynLayer as a method and then calling 
> it works too... :)

	So the question is - which way is better and why :)))

				Malx

Re: Re: Re: [Dynapi-Dev] inheritance crusade / SuperClass stuff

[Barre B. <ba...@ho...>]

Another thing... neither the function.call() nor the 
function.apply() method work under IE4+.
Unfortunately.

/ Bart


> On Wed, 29 Nov 2000, Barre Bizon wrote:
> 
> 
> 	I thinks you have learned too much of OOP languages 
like 
> Java C++ etc.
> 	JavaScript is not OOP - it is Object Language - not 
> just merely OO :)
> 
> 	I would recomend to look deeper into JavaScript.
>  If i'm not mistaken - DunAPI never uses such thing 
as "with"
> 
> 	Also ... If only Netscape4 would be standart.... 
and JavaScrip1.3
> with it:
> ----------------------
> You can use call to chain constructors for an object,
> similar to Java. In the following example, the constructor
> for the product object is defined with two parameters,
> name and value. Another object, prod_dept, initializes its
> unique variable (dept) and calls the constructor for
> product in its constructor to initialize the other 
variables.
> 
> function product(name, value){
>    this.name = name;
>    if(value > 1000)
>       this.value = 999;
>    else
>       this.value = value;
> }
> 
> function prod_dept(name, value, dept){
>    this.dept = dept;
>    product.call(this, name, value);
> }
> 
> prod_dept.prototype = new product();
> 
> // since 5 is less than 100 value is set
> cheese = new prod_dept("feta", 5, "food");
> 
> // since 5000 is above 1000, value will be 999
> car = new prod_dept("honda", 5000, "auto");
> 
> ---------  from JS1.3 documentation.
> 
> 
> 	Also I like "watch" method alot. but it is Netscape 
only :-/
>  It allows you to get rid of methods..
> 	Just  mylayer.x=12 would move the layer.
> 
> 
> 	And... why you need to create object , based
>  on something but not to extend the one you have?!
> 
> ps. In the past you have had ability to make errors...
> 	Now ! with C++ - you could inherit them! :)
> 
> 				Malx
> 
> > Hmm.. but how about wanting widgets to fully extend 
> > Dynlayer.. i.e. supporting exactly the same 
initialization 
> > as Dynlayer has without writing the code over again.
> > 
> > Do you not think that a construct() method would be a 
good 
> > idea? As per my previous posts... 
> > It wouldn't alter anything in essence.. nor complicate 
> > anything. Just how the Dynlayer is initialized, 
allowing 
> > widgets to (easily) do a general DynLayer 
initialization.
> > Apart from widget specific initialization...
> > 
> > / Bart
> > 
> > > I absolutely agree. Things are already complicated 
> > enought and I don't want to add one single line of code 
> > there.
> > > 
> > > 
> > > Dan Steinman wrote:
> > > 
> > > > It is both mine and Pascal's opinion that no 
special 
> > inheritance system is needed for DynAPI.  Just make 
careful 
> > attention, and structure using basic prototypes and you 
can 
> > do everything (except doing multiple inheritance).  
Don't 
> > overwrite variables, and you don't even necessarily 
need to 
> > overwrite methods, and everything works perfectly.  The 
> > most simplistic solution is often the best, and I 
believe 
> > that is the case here.
> > > >
> > > > Dan
> > > >
> > > 
> > > _______________________________________________
> > > 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
> > 
> 
> 
>                  
^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^   
>           /        Word is not a color, but a 
picture.           \
>      _ _ /    To understand it you must draw it by 
yourself. ___  \ _ _
>          \   -------  __  -- |^     malvin@cad.ntu-
kpi.kiev.ua    / 
>           \       ---  ---   | http://cad.ntu-
kpi.kiev.ua/~malvin/   
> 
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev

AW: Re: [Dynapi-Dev] inheritance crusade / SuperClass stuff

[Stephan R. <SR...@la...>]

I agree perfectly with Abel, particulary concerning the commenting (this was
the tenor of my postings some weeks ago).
For the OO discussion: Objects should be a way to simplify book keeping and
thus to enable more and more complex models, not a purpose by themselves.
We should consider using an OO model if it's sure that this simplifies
further evolution of the DynAPI. Taking into account the changes in the
present implementation, may be its better to delay this until DynAPI version
3 or 4 and to concentrate to debug the present version ;-o.
Also, I do not think that the widget discussion should get to much space.
Widgets are "only" an application of the DynAPI and I read enough about
problems with the API itself.
Stephan



>
> I think we must stop thinking: "Add more and more to DynLayer", "Expand
> DynLayer thru prototype property", etc, etc. As i can see, things
> are going
> far and the basis for all this effort must be clear, simple and almost
> untouchable (im talking about the interfaces only, not the functionality).
>
> It is very important a release of DynAPI that includes numerous comments
> explaining the way in which every core js works, this just to
> facilitate the
> learning process; and also its indispensable to make a more
> extensive tutor
> about creating widgets, including widgets based on other widgets, just to
> clarify how things should work when more complex processes are needed.
>
> Im not having problems extending functionality of DynAPI bassing a widget
> onto a more complex object than a DynLayer, it can also seams posible to
> continue the inheritance mechanism provided by the current widget model
> until the end of life.
>
> Why not to take Delphi Object Hierarchy (for instance) as a model for the
> development of components? i was doing that when i was suddenly forced to
> take over another project...
>
> Salutes!
>
> -----Original Message-----
> From: dyn...@li...
> [mailto:dyn...@li...]On Behalf Of Alexey
> Medvedev
> Sent: Miercoles, 29 de Noviembre de 2000 04:50 p.m.
> To: dyn...@li...
> Subject: Re: Re: [Dynapi-Dev] inheritance crusade / SuperClass stuff
>
>
> On Wed, 29 Nov 2000, Barre Bizon wrote:
>
>
> 	I thinks you have learned too much of OOP languages like
> Java C++ etc.
> 	JavaScript is not OOP - it is Object Language - not
> just merely OO :)
>
> 	I would recomend to look deeper into JavaScript.
>  If i'm not mistaken - DunAPI never uses such thing as "with"
>
> 	Also ... If only Netscape4 would be standart.... and JavaScrip1.3
> with it:
> ----------------------
> You can use call to chain constructors for an object,
> similar to Java. In the following example, the constructor
> for the product object is defined with two parameters,
> name and value. Another object, prod_dept, initializes its
> unique variable (dept) and calls the constructor for
> product in its constructor to initialize the other variables.
>
> function product(name, value){
>    this.name = name;
>    if(value > 1000)
>       this.value = 999;
>    else
>       this.value = value;
> }
>
> function prod_dept(name, value, dept){
>    this.dept = dept;
>    product.call(this, name, value);
> }
>
> prod_dept.prototype = new product();
>
> // since 5 is less than 100 value is set
> cheese = new prod_dept("feta", 5, "food");
>
> // since 5000 is above 1000, value will be 999
> car = new prod_dept("honda", 5000, "auto");
>
> ---------  from JS1.3 documentation.
>
>
> 	Also I like "watch" method alot. but it is Netscape only :-/
>  It allows you to get rid of methods..
> 	Just  mylayer.x=12 would move the layer.
>
>
> 	And... why you need to create object , based
>  on something but not to extend the one you have?!
>
> ps. In the past you have had ability to make errors...
> 	Now ! with C++ - you could inherit them! :)
>
> 				Malx
>
> > Hmm.. but how about wanting widgets to fully extend
> > Dynlayer.. i.e. supporting exactly the same initialization
> > as Dynlayer has without writing the code over again.
> >
> > Do you not think that a construct() method would be a good
> > idea? As per my previous posts...
> > It wouldn't alter anything in essence.. nor complicate
> > anything. Just how the Dynlayer is initialized, allowing
> > widgets to (easily) do a general DynLayer initialization.
> > Apart from widget specific initialization...
> >
> > / Bart
> >
> > > I absolutely agree. Things are already complicated
> > enought and I don't want to add one single line of code
> > there.
> > >
> > >
> > > Dan Steinman wrote:
> > >
> > > > It is both mine and Pascal's opinion that no special
> > inheritance system is needed for DynAPI.  Just make careful
> > attention, and structure using basic prototypes and you can
> > do everything (except doing multiple inheritance).  Don't
> > overwrite variables, and you don't even necessarily need to
> > overwrite methods, and everything works perfectly.  The
> > most simplistic solution is often the best, and I believe
> > that is the case here.
> > > >
> > > > Dan
> > > >
> > >
> > > _______________________________________________
> > > 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
> >
>
>
>                  ^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^
>           /        Word is not a color, but a picture.           \
>      _ _ /    To understand it you must draw it by yourself. ___  \ _ _
>          \   -------  __  -- |^     ma...@ca...    /
>           \       ---  ---   | http://cad.ntu-kpi.kiev.ua/~malvin/
>
> _______________________________________________
> 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

Re: Re: Re: [Dynapi-Dev] inheritance crusade / SuperClass stuff

[Barre B. <ba...@ho...>]

Well thanks for the tutorial man... but you obviously 
didn't read my previous posts...

Object orientation exists for a purpose, and no, Javascript 
isn't  "true" OOP, but close enough to be able to use the 
most fundamental principles of OOP, for self explanatory 
reasons.
I guess it comes down to a matter of taste and preference.
I thought creating a constructor method was a clean and 
easy way of doing "extended" functions initialization.
But sure, assigning DynLayer as a method and then calling 
it works too... :)

/ Bart

 > On Wed, 29 Nov 2000, Barre Bizon wrote:
> 
> 
> 	I thinks you have learned too much of OOP languages 
like 
> Java C++ etc.
> 	JavaScript is not OOP - it is Object Language - not 
> just merely OO :)
> 
> 	I would recomend to look deeper into JavaScript.
>  If i'm not mistaken - DunAPI never uses such thing 
as "with"
> 
> 	Also ... If only Netscape4 would be standart.... 
and JavaScrip1.3
> with it:
> ----------------------
> You can use call to chain constructors for an object,
> similar to Java. In the following example, the constructor
> for the product object is defined with two parameters,
> name and value. Another object, prod_dept, initializes its
> unique variable (dept) and calls the constructor for
> product in its constructor to initialize the other 
variables.
> 
> function product(name, value){
>    this.name = name;
>    if(value > 1000)
>       this.value = 999;
>    else
>       this.value = value;
> }
> 
> function prod_dept(name, value, dept){
>    this.dept = dept;
>    product.call(this, name, value);
> }
> 
> prod_dept.prototype = new product();
> 
> // since 5 is less than 100 value is set
> cheese = new prod_dept("feta", 5, "food");
> 
> // since 5000 is above 1000, value will be 999
> car = new prod_dept("honda", 5000, "auto");
> 
> ---------  from JS1.3 documentation.
> 
> 
> 	Also I like "watch" method alot. but it is Netscape 
only :-/
>  It allows you to get rid of methods..
> 	Just  mylayer.x=12 would move the layer.
> 
> 
> 	And... why you need to create object , based
>  on something but not to extend the one you have?!
> 
> ps. In the past you have had ability to make errors...
> 	Now ! with C++ - you could inherit them! :)
> 
> 				Malx
> 
> > Hmm.. but how about wanting widgets to fully extend 
> > Dynlayer.. i.e. supporting exactly the same 
initialization 
> > as Dynlayer has without writing the code over again.
> > 
> > Do you not think that a construct() method would be a 
good 
> > idea? As per my previous posts... 
> > It wouldn't alter anything in essence.. nor complicate 
> > anything. Just how the Dynlayer is initialized, 
allowing 
> > widgets to (easily) do a general DynLayer 
initialization.
> > Apart from widget specific initialization...
> > 
> > / Bart
> > 
> > > I absolutely agree. Things are already complicated 
> > enought and I don't want to add one single line of code 
> > there.
> > > 
> > > 
> > > Dan Steinman wrote:
> > > 
> > > > It is both mine and Pascal's opinion that no 
special 
> > inheritance system is needed for DynAPI.  Just make 
careful 
> > attention, and structure using basic prototypes and you 
can 
> > do everything (except doing multiple inheritance).  
Don't 
> > overwrite variables, and you don't even necessarily 
need to 
> > overwrite methods, and everything works perfectly.  The 
> > most simplistic solution is often the best, and I 
believe 
> > that is the case here.
> > > >
> > > > Dan
> > > >
> > > 
> > > _______________________________________________
> > > 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
> > 
> 
> 
>                  
^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^   
>           /        Word is not a color, but a 
picture.           \
>      _ _ /    To understand it you must draw it by 
yourself. ___  \ _ _
>          \   -------  __  -- |^     malvin@cad.ntu-
kpi.kiev.ua    / 
>           \       ---  ---   | http://cad.ntu-
kpi.kiev.ua/~malvin/   
> 
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev

Re: [Dynapi-Dev] Updated Release, fixes/changes

[Scott A. L. <sc...@sc...>]

<snip>
It's entirely possible have the DynLayer generate LAYER and DIV tags (ala
dynapi1) this would allow you to insert Dynlayers before onLoad, as well you
can get an enormous boost in drawing time in Netscape by writing all the
children layers as layer/div's at the same time in one document.write().
</snip>

I imagine this could help IE, too.  IE rendering is *extremely* slow when
generating lots of DynLayers.  I think Netscape handles it better, because
the JS evaluation and rendering happen separately and simultaneously, while
IE has to wait for one process to complete before starting the other.  A
document.write might be quicker and cleaner in IE.

scottandrew

RE: Re: [Dynapi-Dev] inheritance crusade / SuperClass stuff

[<abe...@al...>]

I think we must stop thinking: "Add more and more to DynLayer", "Expand
DynLayer thru prototype property", etc, etc. As i can see, things are going
far and the basis for all this effort must be clear, simple and almost
untouchable (im talking about the interfaces only, not the functionality).

It is very important a release of DynAPI that includes numerous comments
explaining the way in which every core js works, this just to facilitate the
learning process; and also its indispensable to make a more extensive tutor
about creating widgets, including widgets based on other widgets, just to
clarify how things should work when more complex processes are needed.

Im not having problems extending functionality of DynAPI bassing a widget
onto a more complex object than a DynLayer, it can also seams posible to
continue the inheritance mechanism provided by the current widget model
until the end of life.

Why not to take Delphi Object Hierarchy (for instance) as a model for the
development of components? i was doing that when i was suddenly forced to
take over another project...

Salutes!

-----Original Message-----
From: dyn...@li...
[mailto:dyn...@li...]On Behalf Of Alexey
Medvedev
Sent: Miercoles, 29 de Noviembre de 2000 04:50 p.m.
To: dyn...@li...
Subject: Re: Re: [Dynapi-Dev] inheritance crusade / SuperClass stuff


On Wed, 29 Nov 2000, Barre Bizon wrote:


	I thinks you have learned too much of OOP languages like
Java C++ etc.
	JavaScript is not OOP - it is Object Language - not
just merely OO :)

	I would recomend to look deeper into JavaScript.
 If i'm not mistaken - DunAPI never uses such thing as "with"

	Also ... If only Netscape4 would be standart.... and JavaScrip1.3
with it:
----------------------
You can use call to chain constructors for an object,
similar to Java. In the following example, the constructor
for the product object is defined with two parameters,
name and value. Another object, prod_dept, initializes its
unique variable (dept) and calls the constructor for
product in its constructor to initialize the other variables.

function product(name, value){
   this.name = name;
   if(value > 1000)
      this.value = 999;
   else
      this.value = value;
}

function prod_dept(name, value, dept){
   this.dept = dept;
   product.call(this, name, value);
}

prod_dept.prototype = new product();

// since 5 is less than 100 value is set
cheese = new prod_dept("feta", 5, "food");

// since 5000 is above 1000, value will be 999
car = new prod_dept("honda", 5000, "auto");

---------  from JS1.3 documentation.


	Also I like "watch" method alot. but it is Netscape only :-/
 It allows you to get rid of methods..
	Just  mylayer.x=12 would move the layer.


	And... why you need to create object , based
 on something but not to extend the one you have?!

ps. In the past you have had ability to make errors...
	Now ! with C++ - you could inherit them! :)

				Malx

> Hmm.. but how about wanting widgets to fully extend
> Dynlayer.. i.e. supporting exactly the same initialization
> as Dynlayer has without writing the code over again.
>
> Do you not think that a construct() method would be a good
> idea? As per my previous posts...
> It wouldn't alter anything in essence.. nor complicate
> anything. Just how the Dynlayer is initialized, allowing
> widgets to (easily) do a general DynLayer initialization.
> Apart from widget specific initialization...
>
> / Bart
>
> > I absolutely agree. Things are already complicated
> enought and I don't want to add one single line of code
> there.
> >
> >
> > Dan Steinman wrote:
> >
> > > It is both mine and Pascal's opinion that no special
> inheritance system is needed for DynAPI.  Just make careful
> attention, and structure using basic prototypes and you can
> do everything (except doing multiple inheritance).  Don't
> overwrite variables, and you don't even necessarily need to
> overwrite methods, and everything works perfectly.  The
> most simplistic solution is often the best, and I believe
> that is the case here.
> > >
> > > Dan
> > >
> >
> > _______________________________________________
> > 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
>


                 ^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^
          /        Word is not a color, but a picture.           \
     _ _ /    To understand it you must draw it by yourself. ___  \ _ _
         \   -------  __  -- |^     ma...@ca...    /
          \       ---  ---   | http://cad.ntu-kpi.kiev.ua/~malvin/

_______________________________________________
Dynapi-Dev mailing list
Dyn...@li...
http://lists.sourceforge.net/mailman/listinfo/dynapi-dev

Re: [Dynapi-Dev] Updated Release, fixes/changes

[Dan S. <dy...@fu...>]

First, a fix to the beta release, Insert the following into line 357 in dynlayer.js: 
if (!this.created) return;

Second, I see a need to have a "precreate" event which gets called before any of the layer properties have been changed.  In a widget, you can use the precreate to do your final initialization of the object.  It's more effecient to do this because instead of setting the size of all the layers first to 0x0, and then waiting for the create method and going back again to resize all the children, you could get everything done in one shot so as soon as the DynLayer.create() is done you already have the final properties.  It saves an extra step.  

Also this method will be needed for a possible future addition to the Dynlayer creation system.  It's entirely possible have the DynLayer generate LAYER and DIV tags (ala dynapi1) this would allow you to insert Dynlayers before onLoad, as well you can get an enormous boost in drawing time in Netscape by writing all the children layers as layer/div's at the same time in one document.write().

Anyways, for a precreate event insert the following immediately after the this.assignElement() in dynlayer.js (line 149):

this.invokeEvent('precreate');

I am already using this event in some new code I am working on.  

Also, I think there should be a few more directories in the dynapi structure:

/js/lib/dynapi/images/  (where all widget images are stored)
/js/lib/dynapi/util/  (contains standalone objects which are not widgets)
/js/lib/dynapi/ext/  (should only contain extensions to dynlayer or other files or removed because everything could be thought of as extension)
/js/lib/dynapi/gui/  (only dynlayer based widgets)

In my working copy I have moved:
- LoadPanel to /gui/ because it is a widget, not an extension.
- cookies.js, debug.js to /util/, I will be adding some new stuff to this directory

New code coming:

A new fully working slide/path/gif animation system, it works really good.  I made a few major changes to it this evening so I just need to go back and update a few things before releasing it officially.  It converts slide animations into a paths on the fly, and they're all based on "threads" which can be combined together into one master thread so you can do mutliple animations in the same Interval loop.  I also built Circle and Hover animation objects, and rewrote my Solar System and BumbleBee dynduo demos based on this new code and it all works splendidly.  I'll have em ready to use tomorrow.

Dan


On Wed, Nov 29, 2000 at 04:57:30PM -0500, Robert Rainwater wrote:
> 
> I wanted to create a new release of the DynAPI, but because I havent
> been able to keep up with the list lately I've gotten behind.  So,
> instead of having to wade through all of the posts, I wanted to start
> this thread so that every one can reply with the changes/fixes that need
> to be made to the next release.  I am specifically refering any fixes to
> the latest beta located at
> http://dynapi.sourceforge.net/beta/dynapi-11.12-beta.zip and Dan's
> widgets that he posted earlier.
> 
> The next release should include the fully working set of Dan's widgets
> along with any other fixes.
> 
> Please post any fixes to this thread.
> 
> -- 
> // Robert Rainwater
> 
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev

Re: [Dynapi-Dev] Widgit creation - Tab and Focus

[Brandon M. <bnd...@ho...>]

of course, that only works in IE. What about netscape? And what about =
focusing dynamic objects?

Let's work with the problem presented, and not provide a solution that =
can't be used.

Focus manager is easy when there is a "Helper" event watcher that will =
capture events on all objects of a specific class.
  ----- Original Message -----=20
  From: Abel Eduardo Cant=FA Salas=20
  To: dyn...@li...=20
  Sent: Wednesday, November 29, 2000 10:09 PM
  Subject: RE: [Dynapi-Dev] Widgit creation - Tab and Focus


  Ups! this is a better version of test.htm     :D

  -----Original Message-----
  From: dyn...@li...
  [mailto:dyn...@li...]On Behalf Of Abel =
Eduardo
  Cant=FA Salas
  Sent: Mi=E9rcoles, 29 de Noviembre de 2000 08:31 p.m.
  To: dyn...@li...
  Subject: RE: [Dynapi-Dev] Widgit creation - Tab and Focus


  related to the management of keystrokes, focus and blur events in =
events.js
  =
-------------------------------------------------------------------------=
---

  My idea is less complicated (i think) and requires fewer code. Instead =
of
  creating a more complex object that manages a list of widgets and =
bubbles
  the focus events, just leave the browser window take care of it.

  Here is an example using dhtm (not dynapi) IMPORTANT: it works only in =
ie 5
  (i not warrant that this html will look fine in other browser, but =
maybe ie
  5.5 or 4.x):

  see attached file.
  ------------------

  what im doing right now with dynapi is something like this:

  1) saving the original DynLayer createElement in a separated pointer
     (inherited_createElement) on my widget.
  2) overwriting this createElement method
  2.1) in this overwrote method i call the inherited_createElement
  2.2) after that, i add the anchor tag using insertAdjacentHTML method

  3) i think thats it!

  Everybody requiring this functionality just will need to base their =
own
  widgets on this one and Presto!, we have widgets that can take focus =
not
  just by clicking but using the tab key also.

  However we need to review events.js and add the capability to manage =
focus,
  blur and keydown events so we can do everything just using common
  eventListeners, im still having problems there because it stills =
working
  only in ie. But i hope that somebody more familiar to ns will solve =
these
  problems someday... What i need for now is get this thing working on =
IE
  under a Win environment a soon as posible: A widget that copies the =
behavior
  of a TStringGrid (developers familiar with Delphi will know whats =
that) and
  time is almost over!

  cheers guys!

  -----Original Message-----
  From: dyn...@li...
  [mailto:dyn...@li...]On Behalf Of Darin
  Kadrioski
  Sent: Mi=E9rcoles, 29 de Noviembre de 2000 05:57 p.m.
  To: DynAPI Dev (E-mail)
  Subject: [Dynapi-Dev] Widgit creation - Tab and Focus



  Heya guys,

  Scott and I had a brief thread going last spring about having the =
concept of
  "focus" shared amongst many widgits on the same page.
  This is to facilitate "tabbing" between controls and the blinking of
  "carets" for edits, etc...

  One thought was to have a global constructor that each widgit would
  "register" with.  The Dynapi would keep a list of the widgits in the =
order
  they were created, this then becomes the "tab order".  Assuming we can
  successfully trap the tab key in both browsers, the dynapi would catch =
it
  first before bubbling it to the widgets.  It would then send an =
OnBlur()
  event to whichever control currently had focus and an OnFocus() event =
to the
  next in the list.

  Any thoughts on if this could be acheived?  Anyone else see the need =
for it?

  Also, how about a "standard" construction call for widgit builders to =
use?
  Something like create(x,y,w,h,fgcolor,bgcolor,skin)

  And maybe a set of standard events.
  refresh() comes to mind.


  -cheers!

  --------------------------------------------------
  Darin Kadrioski
  Applications/Internet Developer

  > Electronic Freight Exchange, Corp.
  dka...@ef...
  (916) 933-0724 x315

  _______________________________________________
  Dynapi-Dev mailing list
  Dyn...@li...
  http://lists.sourceforge.net/mailman/listinfo/dynapi-dev

RE: [Dynapi-Dev] Widgit creation - Tab and Focus

[<abe...@al...>]

Ups! this is a better version of test.htm     :D

-----Original Message-----
From: dyn...@li...
[mailto:dyn...@li...]On Behalf Of Abel Eduardo
Cantú Salas
Sent: Miércoles, 29 de Noviembre de 2000 08:31 p.m.
To: dyn...@li...
Subject: RE: [Dynapi-Dev] Widgit creation - Tab and Focus


related to the management of keystrokes, focus and blur events in events.js
----------------------------------------------------------------------------

My idea is less complicated (i think) and requires fewer code. Instead of
creating a more complex object that manages a list of widgets and bubbles
the focus events, just leave the browser window take care of it.

Here is an example using dhtm (not dynapi) IMPORTANT: it works only in ie 5
(i not warrant that this html will look fine in other browser, but maybe ie
5.5 or 4.x):

see attached file.
------------------

what im doing right now with dynapi is something like this:

1) saving the original DynLayer createElement in a separated pointer
   (inherited_createElement) on my widget.
2) overwriting this createElement method
	2.1) in this overwrote method i call the inherited_createElement
	2.2) after that, i add the anchor tag using insertAdjacentHTML method

3) i think thats it!

Everybody requiring this functionality just will need to base their own
widgets on this one and Presto!, we have widgets that can take focus not
just by clicking but using the tab key also.

However we need to review events.js and add the capability to manage focus,
blur and keydown events so we can do everything just using common
eventListeners, im still having problems there because it stills working
only in ie. But i hope that somebody more familiar to ns will solve these
problems someday... What i need for now is get this thing working on IE
under a Win environment a soon as posible: A widget that copies the behavior
of a TStringGrid (developers familiar with Delphi will know whats that) and
time is almost over!

cheers guys!

-----Original Message-----
From: dyn...@li...
[mailto:dyn...@li...]On Behalf Of Darin
Kadrioski
Sent: Miércoles, 29 de Noviembre de 2000 05:57 p.m.
To: DynAPI Dev (E-mail)
Subject: [Dynapi-Dev] Widgit creation - Tab and Focus



Heya guys,

Scott and I had a brief thread going last spring about having the concept of
"focus" shared amongst many widgits on the same page.
This is to facilitate "tabbing" between controls and the blinking of
"carets" for edits, etc...

One thought was to have a global constructor that each widgit would
"register" with.  The Dynapi would keep a list of the widgits in the order
they were created, this then becomes the "tab order".  Assuming we can
successfully trap the tab key in both browsers, the dynapi would catch it
first before bubbling it to the widgets.  It would then send an OnBlur()
event to whichever control currently had focus and an OnFocus() event to the
next in the list.

Any thoughts on if this could be acheived?  Anyone else see the need for it?

Also, how about a "standard" construction call for widgit builders to use?
Something like create(x,y,w,h,fgcolor,bgcolor,skin)

And maybe a set of standard events.
refresh() comes to mind.


-cheers!

--------------------------------------------------
Darin Kadrioski
Applications/Internet Developer

> Electronic Freight Exchange, Corp.
dka...@ef...
(916) 933-0724 x315

_______________________________________________
Dynapi-Dev mailing list
Dyn...@li...
http://lists.sourceforge.net/mailman/listinfo/dynapi-dev

RE: [Dynapi-Dev] Widgit creation - Tab and Focus

[<abe...@al...>]

related to the management of keystrokes, focus and blur events in events.js
----------------------------------------------------------------------------

My idea is less complicated (i think) and requires fewer code. Instead of
creating a more complex object that manages a list of widgets and bubbles
the focus events, just leave the browser window take care of it.

Here is an example using dhtm (not dynapi) IMPORTANT: it works only in ie 5
(i not warrant that this html will look fine in other browser, but maybe ie
5.5 or 4.x):

see attached file.
------------------

what im doing right now with dynapi is something like this:

1) saving the original DynLayer createElement in a separated pointer
   (inherited_createElement) on my widget.
2) overwriting this createElement method
	2.1) in this overwrote method i call the inherited_createElement
	2.2) after that, i add the anchor tag using insertAdjacentHTML method

3) i think thats it!

Everybody requiring this functionality just will need to base their own
widgets on this one and Presto!, we have widgets that can take focus not
just by clicking but using the tab key also.

However we need to review events.js and add the capability to manage focus,
blur and keydown events so we can do everything just using common
eventListeners, im still having problems there because it stills working
only in ie. But i hope that somebody more familiar to ns will solve these
problems someday... What i need for now is get this thing working on IE
under a Win environment a soon as posible: A widget that copies the behavior
of a TStringGrid (developers familiar with Delphi will know whats that) and
time is almost over!

cheers guys!

-----Original Message-----
From: dyn...@li...
[mailto:dyn...@li...]On Behalf Of Darin
Kadrioski
Sent: Miércoles, 29 de Noviembre de 2000 05:57 p.m.
To: DynAPI Dev (E-mail)
Subject: [Dynapi-Dev] Widgit creation - Tab and Focus



Heya guys,

Scott and I had a brief thread going last spring about having the concept of
"focus" shared amongst many widgits on the same page.
This is to facilitate "tabbing" between controls and the blinking of
"carets" for edits, etc...

One thought was to have a global constructor that each widgit would
"register" with.  The Dynapi would keep a list of the widgits in the order
they were created, this then becomes the "tab order".  Assuming we can
successfully trap the tab key in both browsers, the dynapi would catch it
first before bubbling it to the widgets.  It would then send an OnBlur()
event to whichever control currently had focus and an OnFocus() event to the
next in the list.

Any thoughts on if this could be acheived?  Anyone else see the need for it?

Also, how about a "standard" construction call for widgit builders to use?
Something like create(x,y,w,h,fgcolor,bgcolor,skin)

And maybe a set of standard events.
refresh() comes to mind.


-cheers!

--------------------------------------------------
Darin Kadrioski
Applications/Internet Developer

> Electronic Freight Exchange, Corp.
dka...@ef...
(916) 933-0724 x315

_______________________________________________
Dynapi-Dev mailing list
Dyn...@li...
http://lists.sourceforge.net/mailman/listinfo/dynapi-dev

[Dynapi-Dev] Widgit creation - Tab and Focus

[Darin K. <dka...@ef...>]

Heya guys,

Scott and I had a brief thread going last spring about having the concept of
"focus" shared amongst many widgits on the same page.
This is to facilitate "tabbing" between controls and the blinking of
"carets" for edits, etc...

One thought was to have a global constructor that each widgit would
"register" with.  The Dynapi would keep a list of the widgits in the order
they were created, this then becomes the "tab order".  Assuming we can
successfully trap the tab key in both browsers, the dynapi would catch it
first before bubbling it to the widgets.  It would then send an OnBlur()
event to whichever control currently had focus and an OnFocus() event to the
next in the list.

Any thoughts on if this could be acheived?  Anyone else see the need for it?

Also, how about a "standard" construction call for widgit builders to use?
Something like create(x,y,w,h,fgcolor,bgcolor,skin)

And maybe a set of standard events.
refresh() comes to mind.


-cheers!

--------------------------------------------------
Darin Kadrioski
Applications/Internet Developer

> Electronic Freight Exchange, Corp.
dka...@ef...
(916) 933-0724 x315

Re: Re: [Dynapi-Dev] Re: [Dynapi-Help] Repeat - mem leak question

[Barre B. <ba...@ho...>]

Yup .. thats right. On a PC.
On a mac the default memory setting for both ie and ns is 
pretty low. And when that runs out, your out of memory.
Offcourse you can set that to a higher value yourself 
pretty easily.. but the defaut user probably doesn't.

I had that problem when constructing a menu in dynAPI1.
Running out of memory the whole time...
Had to redo it and drastically decrease the amount of Layers
from around 100-200 to around 30.
But I believe that DynAPI2 is a lot better at memory usage. 
There's still some room for improvement, though :)

BTW, anyone has an idea about how to flush memory on PC for 
IE..? It seems that it allocates memory for each new page 
load.

/ Bart

> I got to 7000 layers then hit the back button.  It hung 
at that point.
> Suceeded with back button at 4000 layers
> use freemem pro, probably helped.  But 6000+ layers is 
insane...
> 
> ----- Original Message -----
> From: "Alexey Medvedev" <ma...@ca...>
> To: <dyn...@li...>
> Sent: Tuesday, November 28, 2000 3:19 AM
> Subject: [Dynapi-Dev] Re: [Dynapi-Help] Repeat - mem leak 
question
> 
> 
> > On Mon, 27 Nov 2000, Andrew Forber wrote:
> >
> > Hello!
> > --
> > First of all - I'm first time here. I'm very interested 
in DHTML
> > and have tryes to use old Dan's library. Current my 
work is depends
> > on dhtml so , I hope , will contribute something.
> > --
> >
> > > time Internet Explorer 5.5 uses about 2 megs more of 
RAM. After loading
> the
> >
> > I'm very courius about lots of layers used in lib and 
about
> >  LongNameOfParameters. Have anyone tries to make memory 
tests?
> >  I thinks it have less memory to insert number of 
images in one layer
> >  then to make one layer for every one (as , i thinks , 
now is with
> widgets)
> >
> > Try to see how much layers you computer could drow (NN 
only :-/:
> >
> > http://deep.kiev.ua/JS/garbage/js1/test_layers.html
> >
> >   Just now NN4/unix crashed on ~400 layers + Back 
button press :)
> >
> > When I leave it to draw ~4000 layers it hang X Window 
at all :-/
> >
> >  And - is there some way to insert memory checks into 
debug version of
> > DynAPI? (the one without comments and other striped)
> >  I this JS will not permit this , but in NN you could 
utilise LiveConnect
> > to Java and IE have ActiveX embadable.
> >
> > Also some sort of events/calls loging would be nice to 
have
> >  in debug version - it's hard to figure source of 
browser crashes :-/
> >
> > Malx
> > --
> > There is no thing in the world, which is more 
powerfull, than default
> >
> >
> > _______________________________________________
> > 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

Re: Re: [Dynapi-Dev] inheritance crusade / SuperClass stuff

[Alexey M. <ma...@ca...>]

On Wed, 29 Nov 2000, Barre Bizon wrote:


	I thinks you have learned too much of OOP languages like 
Java C++ etc.
	JavaScript is not OOP - it is Object Language - not 
just merely OO :)

	I would recomend to look deeper into JavaScript.
 If i'm not mistaken - DunAPI never uses such thing as "with"

	Also ... If only Netscape4 would be standart.... and JavaScrip1.3
with it:
----------------------
You can use call to chain constructors for an object,
similar to Java. In the following example, the constructor
for the product object is defined with two parameters,
name and value. Another object, prod_dept, initializes its
unique variable (dept) and calls the constructor for
product in its constructor to initialize the other variables.

function product(name, value){
   this.name = name;
   if(value > 1000)
      this.value = 999;
   else
      this.value = value;
}

function prod_dept(name, value, dept){
   this.dept = dept;
   product.call(this, name, value);
}

prod_dept.prototype = new product();

// since 5 is less than 100 value is set
cheese = new prod_dept("feta", 5, "food");

// since 5000 is above 1000, value will be 999
car = new prod_dept("honda", 5000, "auto");

---------  from JS1.3 documentation.


	Also I like "watch" method alot. but it is Netscape only :-/
 It allows you to get rid of methods..
	Just  mylayer.x=12 would move the layer.


	And... why you need to create object , based
 on something but not to extend the one you have?!

ps. In the past you have had ability to make errors...
	Now ! with C++ - you could inherit them! :)

				Malx

> Hmm.. but how about wanting widgets to fully extend 
> Dynlayer.. i.e. supporting exactly the same initialization 
> as Dynlayer has without writing the code over again.
> 
> Do you not think that a construct() method would be a good 
> idea? As per my previous posts... 
> It wouldn't alter anything in essence.. nor complicate 
> anything. Just how the Dynlayer is initialized, allowing 
> widgets to (easily) do a general DynLayer initialization.
> Apart from widget specific initialization...
> 
> / Bart
> 
> > I absolutely agree. Things are already complicated 
> enought and I don't want to add one single line of code 
> there.
> > 
> > 
> > Dan Steinman wrote:
> > 
> > > It is both mine and Pascal's opinion that no special 
> inheritance system is needed for DynAPI.  Just make careful 
> attention, and structure using basic prototypes and you can 
> do everything (except doing multiple inheritance).  Don't 
> overwrite variables, and you don't even necessarily need to 
> overwrite methods, and everything works perfectly.  The 
> most simplistic solution is often the best, and I believe 
> that is the case here.
> > >
> > > Dan
> > >
> > 
> > _______________________________________________
> > 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
> 


                 ^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^~^   
          /        Word is not a color, but a picture.           \
     _ _ /    To understand it you must draw it by yourself. ___  \ _ _
         \   -------  __  -- |^     ma...@ca...    / 
          \       ---  ---   | http://cad.ntu-kpi.kiev.ua/~malvin/   

[Dynapi-Dev] Updated Release

[Robert R. <rra...@ya...>]

I wanted to create a new release of the DynAPI, but because I havent
been able to keep up with the list lately I've gotten behind.  So,
instead of having to wade through all of the posts, I wanted to start
this thread so that every one can reply with the changes/fixes that need
to be made to the next release.  I am specifically refering any fixes to
the latest beta located at
http://dynapi.sourceforge.net/beta/dynapi-11.12-beta.zip and Dan's
widgets that he posted earlier.

The next release should include the fully working set of Dan's widgets
along with any other fixes.

Please post any fixes to this thread.

-- 
// Robert Rainwater

RE: Re: [Dynapi-Dev] inheritance crusade / SuperClass stuff

[Pascal B. <pa...@dy...>]

please note that if you really want to extend the dynlayer you should write
it as an extension.. not a widget.  So that would mean using
DynLayer.prototype.extension as your code, not creating a new object.

also it's not that much code to type when wanting to pass arguments to the
DynLayer constructor:

function myWidget(id,x,y,w,h) {
	this.DynLayer=DynLayer
	this.DynLayer(id,x,y,w,h)
	return this
}

that's all.. you simply pass the parameters to the DynLayer, no need to do
every initialisation the DynLayer does (unless you want to change or check
values first)


Pascal Bestebroer
pa...@dy...
http://www.dynamic-core.net

> -----Oorspronkelijk bericht-----
> Van: dyn...@li...
> [mailto:dyn...@li...]Namens Barre Bizon
> Verzonden: woensdag 29 november 2000 19:43
> Aan: dyn...@li...
> Onderwerp: Re: Re: [Dynapi-Dev] inheritance crusade / SuperClass stuff
>
>
> Hmm.. but how about wanting widgets to fully extend
> Dynlayer.. i.e. supporting exactly the same initialization
> as Dynlayer has without writing the code over again.
>
> Do you not think that a construct() method would be a good
> idea? As per my previous posts...
> It wouldn't alter anything in essence.. nor complicate
> anything. Just how the Dynlayer is initialized, allowing
> widgets to (easily) do a general DynLayer initialization.
> Apart from widget specific initialization...
>
> / Bart
>
> > I absolutely agree. Things are already complicated
> enought and I don't want to add one single line of code
> there.
> >
> >
> > Dan Steinman wrote:
> >
> > > It is both mine and Pascal's opinion that no special
> inheritance system is needed for DynAPI.  Just make careful
> attention, and structure using basic prototypes and you can
> do everything (except doing multiple inheritance).  Don't
> overwrite variables, and you don't even necessarily need to
> overwrite methods, and everything works perfectly.  The
> most simplistic solution is often the best, and I believe
> that is the case here.
> > >
> > > Dan
> > >
> >
> > _______________________________________________
> > 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
>

Re: [Dynapi-Dev] inheritance crusade / SuperClass stuff

[Scott A. L. <sc...@sc...>]

I think it's a matter of personal preference at this point.  There
doesn't seem to be a consensus on what the 'correct' model should be, so
maybe it's best if it's left open for you to choose (or create) an
approach that suits your tastes.

-- 
scott andrew lepera
-----------------------------------
web stuff:     www.scottandrew.com
music stuff:   www.walkingbirds.com


Barre Bizon wrote:
> 
> Hmm.. but how about wanting widgets to fully extend
> Dynlayer.. i.e. supporting exactly the same initialization
> as Dynlayer has without writing the code over again.
> 
> Do you not think that a construct() method would be a good
> idea? As per my previous posts...
> It wouldn't alter anything in essence.. nor complicate
> anything. Just how the Dynlayer is initialized, allowing
> widgets to (easily) do a general DynLayer initialization.
> Apart from widget specific initialization...
> 
> / Bart
> 
> > I absolutely agree. Things are already complicated
> enought and I don't want to add one single line of code
> there.
> >
> >
> > Dan Steinman wrote:
> >
> > > It is both mine and Pascal's opinion that no special
> inheritance system is needed for DynAPI.  Just make careful
> attention, and structure using basic prototypes and you can
> do everything (except doing multiple inheritance).  Don't
> overwrite variables, and you don't even necessarily need to
> overwrite methods, and everything works perfectly.  The
> most simplistic solution is often the best, and I believe
> that is the case here.
> > >
> > > Dan
> > >
> >
> > _______________________________________________
> > 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

Re: Re: [Dynapi-Dev] inheritance crusade / SuperClass stuff

[Barre B. <ba...@ho...>]

Hmm.. but how about wanting widgets to fully extend 
Dynlayer.. i.e. supporting exactly the same initialization 
as Dynlayer has without writing the code over again.

Do you not think that a construct() method would be a good 
idea? As per my previous posts... 
It wouldn't alter anything in essence.. nor complicate 
anything. Just how the Dynlayer is initialized, allowing 
widgets to (easily) do a general DynLayer initialization.
Apart from widget specific initialization...

/ Bart

> I absolutely agree. Things are already complicated 
enought and I don't want to add one single line of code 
there.
> 
> 
> Dan Steinman wrote:
> 
> > It is both mine and Pascal's opinion that no special 
inheritance system is needed for DynAPI.  Just make careful 
attention, and structure using basic prototypes and you can 
do everything (except doing multiple inheritance).  Don't 
overwrite variables, and you don't even necessarily need to 
overwrite methods, and everything works perfectly.  The 
most simplistic solution is often the best, and I believe 
that is the case here.
> >
> > Dan
> >
> 
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev

RE: [Dynapi-Dev] Faking Events

[Tim R. <ti...@my...>]

He he... yes, the things you mentione are definitely ones we've run across.
The Flash objects with the transparency parameter on the OBJECT tag enabled
actually allow for drag events on the parts of the DIV behind the Flash
object that are not obscured by the Flash object itself. Also, though, the
mouseup *does*, as you suggest, become a problem in that if not triggered,
the flash object suddenly becomes affixed to teh mouse cursor, driving
people batty. I rather liked it myself, it was fun to watch the testers
during that phase. :)

That's why I wanted a "drag" solution right in the Flash object, since it
tended to 'eat' the mouse messages when the cursor was over it. If Flash
started the drag, perhaps Flash would be better at *ending* the drag.
Fortunately, if I can't make it worth well enough, I'm gonna drop the
feature entirely.

The Flash stuff could probably be replaced with DHTML, but it has one HUGE
advantage over DHTML for the specific purpose we've chosen it for: it can
make calls for data to the server without having to refresh the entire page.
So my headlines flash object can be sent a parameter (say, 'NBA'), and
silently make a call to the server to retrieve the headlines for the nba
without reloading anything. It makes my server requests for that content
under 2K, and cuts down on bandwidth...

To accomplish that task on DHTML, I'd have to make a DynLayer or a component
based on a Dynlayer, but associate it with a hidden IFRAME or LAYER. I'd
need to make a call to the server in that hidden frame that retrieved
headlines, and then returned client side javascript commands on the
returning page to the hidden IFRAME that then manipulated the visible
headlines DynLayer properties. Achievable, but a tad more messy (and
verbose).

Personally, I hate Flash. Always have. I've always figured people should do
as much within the confines of the native browser logic as possible. But I'm
forced to admit that when it comes to download size for complex animation,
smoothness of animation, and the issue above of tiny dynamci updates to
Flash files, it does hold its own in given circumstances. And the clincher:
we have one web developer, a misplaced database developer playing out of
position (me. :) ), and one Flash dude. Gee, what to do. :)

But I still hate Flash. Most of all, I hate sites that are all Flash and no
substance. Chuckle.

Thanks for the comments.

Tim

-----Original Message-----
From: dyn...@li...
[mailto:dyn...@li...]On Behalf Of Raymond
Smith
Sent: Wednesday, November 29, 2000 3:44 AM
To: dyn...@li...
Subject: Re: [Dynapi-Dev] Faking Events


Flash embedded in a layer, moves with the layer....

It just ignores Z relationships as it is moved.  It also blinds drag event
handlers and can cause havoc if the main doc misses a 'mouseup' that happens
over the swf movie.

Which, in general is why flash needs to be subrogated to some obscure part
of your page or managed very carefully, i.e... if this dynlayer moves, that
swf (dom violating) layer;setVisible=false.

Personally, I think as libraries like this evolve you will see flash
dissolve more and more into a 'background' roll that serves very explicit
and temporal functions...  SWF will never be about interface in the
long-run.  Though integrated SVG may.

Besides... planet earth grows tired of the 'wiggling line' already.  It was
vogue, it became soooo pervasive that it's vogue not to have it now.

Cheers


----- Original Message -----
From: "Jordi 'IlMaestro' Ministral" <jmi...@or...>
To: <dyn...@li...>
Sent: Wednesday, November 29, 2000 1:39 AM
Subject: Re: [Dynapi-Dev] Faking Events


> If you only want to drag the Flash place keep a pair of variables inside
your
> Movie.
>
> oldX oldY
>
> and then, when you detect movement inside the movie and the mouse is
pressed:
>
>
GetURL("javascript:myHolder.moveBy("+(_xmouse-oldX)+","+(_ymouse-oldY)+")")
> oldX = _xmouse
> oldY = _ymouse
>
> It should do the trick. I think
>
> I hope my Flash knowledge doesn't get me banned from the project :)
>
> Tim Royal wrote:
>
> > Howdy howdy.
> >
> > Anyone have an idea how to create an event and pass it to an object
through
> > the DynAPI events stuff? Here's what I'm trying to do. I have draggable
> > layers that can be moved around and set by the user. There are three
layers.
> > Each one has a Flash object imbedded in it (hence, moving around Flash
> > objects on the screen). We used Flash because of its smoother animation
and
> > its smaller size.
> >
> > The problem is that as we drag, the mouse moves over the Flash object
and
> > the events are no longered triggered by the browser (instead, the Flash
> > object itself 'eats' the event). This makes dragging a tricky, not so
fun
> > process.
> >
> > What I'd *like* to happen is to have the user be able to click on  the
Flash
> > file background, and when the mouse moves (with the LMB depressed), have
the
> > Flash object send out a message to a function which creates a drag event
on
> > the housing DynLayer and moves the Flash object.
> >
> > Any thoughts?
> >
> > Thanks!
> > Tim
> >
> > _______________________________________________
> > 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

RE: [Dynapi-Dev] Faking Events

[Tim R. <ti...@my...>]

whoa. that's the best idea yet. (I tried the earlier idea fo the cover DIV,
but didn't get too far (though I didn't pursue it to a final conclusion,
either)).

This... This is great! AT least, in theory, it's great. I'll try it today
and see what happens.

Thanks big time!
tim

-----Original Message-----
From: dyn...@li...
[mailto:dyn...@li...]On Behalf Of Jordi
'IlMaestro' Ministral
Sent: Wednesday, November 29, 2000 1:40 AM
To: dyn...@li...
Subject: Re: [Dynapi-Dev] Faking Events


If you only want to drag the Flash place keep a pair of variables inside
your
Movie.

oldX oldY

and then, when you detect movement inside the movie and the mouse is
pressed:

GetURL("javascript:myHolder.moveBy("+(_xmouse-oldX)+","+(_ymouse-oldY)+")")
oldX = _xmouse
oldY = _ymouse

It should do the trick. I think

I hope my Flash knowledge doesn't get me banned from the project :)

Tim Royal wrote:

> Howdy howdy.
>
> Anyone have an idea how to create an event and pass it to an object
through
> the DynAPI events stuff? Here's what I'm trying to do. I have draggable
> layers that can be moved around and set by the user. There are three
layers.
> Each one has a Flash object imbedded in it (hence, moving around Flash
> objects on the screen). We used Flash because of its smoother animation
and
> its smaller size.
>
> The problem is that as we drag, the mouse moves over the Flash object and
> the events are no longered triggered by the browser (instead, the Flash
> object itself 'eats' the event). This makes dragging a tricky, not so fun
> process.
>
> What I'd *like* to happen is to have the user be able to click on  the
Flash
> file background, and when the mouse moves (with the LMB depressed), have
the
> Flash object send out a message to a function which creates a drag event
on
> the housing DynLayer and moves the Flash object.
>
> Any thoughts?
>
> Thanks!
> Tim
>
> _______________________________________________
> 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

Re: [Dynapi-Dev] documentation?

[Juanan <jpe...@ar...>]

I can try to help with this documentation effort (like a beta tester of the
examples in a Linux with Netscape / Mozilla environment), but I don't know
where the documentation site is located.
Have you got any URL or is it in a cvs?

Juanan
jpe...@ar...

[Dynapi-Dev] I have updated (sort of)

[Jordi 'I. M. <jmi...@or...>]

I am currently uploading my website's update. If you already knew what was there
then no need to look at it again. It basically contains updated versions of all my
widgets ( downloadable from the download section ) and a few spelling corrections.

http://www.cantir.com/dynapi

I'll try to include some new extensions soon but as usual you never can tell.