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

Re: [Dynapi-Dev] Scott's Update

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

I know I'm not crazy.

The current DynAPI Core distribution is missing DynAPI.getImage() !

I don't know about the Full distribution.

I just tested IBSBoldLayer and IBSButton and they work fine, so I'm
confused.

IBS Icon doesn't work because of the missing getImage().

Puzzled, continuing to test.

Re: [Dynapi-Dev] Scott's Update

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

Thank you for testing all that.

I have an idea why it breaks some of those (especially the IBS kit);
others I'll have to look at.

scottandrew

Robert Rainwater wrote:
> 
> Here's a list of the examples that Scott's distro seems to have
> broken:
> - core.fx.layerx.htm
> - core.fx.layery.htm
> - core.gui.gridbutton.htm
> - core.gui.popup.htm
> - core.gui.scrollbar.htm
> - core.gui.skin*.htm
> - core.gui.toolbar.htm
> - core.gui.treenode.htm (strange error in ie)
> - core.ibs.*.htm
> 
> Some of these may not have worked before, but several are definately
> caused by Scott's update.  I want to move most of the widgets out
> anyway in the next distribution, but we need to find out why this is
> caused.
> 
> Later,
> Robert <rai...@us...>
> 
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev

[Dynapi-Dev] Scott's Update

[Robert R. <rai...@us...>]

Here's a list of the examples that Scott's distro seems to have
broken:
- core.fx.layerx.htm
- core.fx.layery.htm
- core.gui.gridbutton.htm
- core.gui.popup.htm
- core.gui.scrollbar.htm
- core.gui.skin*.htm
- core.gui.toolbar.htm
- core.gui.treenode.htm (strange error in ie)
- core.ibs.*.htm

Some of these may not have worked before, but several are definately
caused by Scott's update.  I want to move most of the widgets out
anyway in the next distribution, but we need to find out why this is
caused.

Later,
Robert <rai...@us...>

Re[2]: [Dynapi-Dev] improvements, widgets and stuff

[Robert R. <rai...@us...>]

We can setup a the homepage at sourceforge (dynapi.sourceforge.net) to
have links to the different peoples add-ons and to their websites.
Then, they can provide their own documentation and information about
their downloads.  This will make it easier to maintain the main
distribution.


Later,
Robert <rai...@us...>

> I agree.  We should probably separate out the widgets into packages with
> descriptions and make them available as a separate download.  Then new
> users can choose the package they feel most comfortable with.
> 
> I think only the core, ext, and util files should be hard-coded into the
> DynAPI include libraries.  Everything else, like widget libraries, can
> be added by the developer.
> 
> I suggest also moving lite classes out, because they're difficult to
> maintain.  Any patch incorporated into the core has to be added to lite
> classes too.
> 
> Since the only thing that's 'official' about DynAPI2 are the core files,
> I think only those should be available in the core download.

[Dynapi-Dev] DOM support/documentation

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

I apologize for being such a chatterbox today :-)

Someone mentioned that DynAPI2 supports NS6.  But I'm looking through
the distro and only see scattered DOM support.  For example, the code to
create layers in NS6 is there, but the code to move them (moveTo) is
not.  This is the case for a lot of basic methods.

I'm going to do some testing today (it's a slow day) and see what I can
do to help resolve this.  Until then, should we mention NS6/DOM support?

RE Documentation: I am willing to at least start, but maybe the
distribution should be cleaned up first (widgets separated, patches
evalutated and added, etc.)?

Re: [Dynapi-Dev] improvements, widgets and stuff

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

I agree.  We should probably separate out the widgets into packages with
descriptions and make them available as a separate download.  Then new
users can choose the package they feel most comfortable with.

I think only the core, ext, and util files should be hard-coded into the
DynAPI include libraries.  Everything else, like widget libraries, can
be added by the developer.

I suggest also moving lite classes out, because they're difficult to
maintain.  Any patch incorporated into the core has to be added to lite
classes too.

Since the only thing that's 'official' about DynAPI2 are the core files,
I think only those should be available in the core download.


Robert Rainwater wrote:
> 
> Hi,
> 
> I have no problem handling the new releases at sourceforge.  However,
> I think we need some guidelines and some consensus as to what
> additions should be made to releases.  There are always patches
> available in the patches sections, but we need to have more discussion
> as to whether the patches are worthy to be added to the next release.
> 
> Also, I would like to see a lot of the widgets and extra stuff in the
> distro moved out.  Maybe each person can provide there own widget pack
> in a separate download.  This would make the dynapi much less
> confusing to new users, than having 10 different peoples stuff in
> there to everyone.  Especially, since everyone uses a different style
> to create their widgets that new users will be lost when trying to
> learn how to right widgets.  If we provide separate widget packs, then
> users may decide they like one persons over another, but at least they
> will have a choice.  Maybe just include a few basic widgets (that we
> can decide on) and some documentation (we need some api docs anyone?).
> 
> Later,
> Robert <rai...@us...>
> 
> _______________________________________________
> Dynapi-Dev mailing list
> Dyn...@li...
> http://lists.sourceforge.net/mailman/listinfo/dynapi-dev

Re: [Dynapi-Dev] core vs. full?

[Robert R. <rai...@us...>]

> Should we really be maintaining 2 versions?

No, i dont think so.  But, the reason was, the full contains examples
and documentation.  Like I said in an earlier email, I think we should
remove most of the user-contributed widgets from the distro, and make
them available as separate widget packs.  We also need some api
documentation.  If we don't slim down the distro, its just going to be
bloated with everyone's stuff.

Later,
Robert <rai...@us...>

Re[2]: [Dynapi-Dev] improvements, widgets and stuff

[Robert R. <rai...@us...>]

Hi,

I have no problem handling the new releases at sourceforge.  However,
I think we need some guidelines and some consensus as to what
additions should be made to releases.  There are always patches
available in the patches sections, but we need to have more discussion
as to whether the patches are worthy to be added to the next release.

Also, I would like to see a lot of the widgets and extra stuff in the
distro moved out.  Maybe each person can provide there own widget pack
in a separate download.  This would make the dynapi much less
confusing to new users, than having 10 different peoples stuff in
there to everyone.  Especially, since everyone uses a different style
to create their widgets that new users will be lost when trying to
learn how to right widgets.  If we provide separate widget packs, then
users may decide they like one persons over another, but at least they
will have a choice.  Maybe just include a few basic widgets (that we
can decide on) and some documentation (we need some api docs anyone?).

Later,
Robert <rai...@us...>

[Dynapi-Dev] core vs. full?

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

What is the difference between the 'core' and 'full' distributions at
SourceForge?

Should we really be maintaining 2 versions?

RE: [Dynapi-Dev] patches submitted

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

Some SSL or TSL  settings in IE could fix this.. worked for me.

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


-----Oorspronkelijk bericht-----
Van: dyn...@li...
[mailto:dyn...@li...]Namens Scott Andrew
LePera
Verzonden: donderdag 26 oktober 2000 19:09
Aan: dyn...@li...
Onderwerp: [Dynapi-Dev] patches submitted


Okay, I was able to finally get onto SourceForge and submit all my
patches (not the widgets yet).  Have at them.

BTW, has anyone noticed that it's easier to get to/navigate  SourceForge
with NS than IE?
_______________________________________________
Dynapi-Dev mailing list
Dyn...@li...
http://lists.sourceforge.net/mailman/listinfo/dynapi-dev

RE: [Dynapi-Dev] improvements, widgets and stuff

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

FIrst: This mailing list is a good idea, getting the threads into my mailbox
with all messages local, is just so much easier to load.. cheers to Robert
for the idea :)

I totally agree on all your points Scott, we should get a stable version on
there
as soon as possible (no more new stuff, just one stable release..)
Luckily there are now more people working and, more importantly, speaking up
about the API
and the bugs it contains so that should help fix all bugs fast.

I'll take it on me personally (unless somebody else has already started) to
create
a "benchmark" file containing all different basic code. This will NOT
include widget code,
just plain dynlayers and events.

I will see about renaming my release (probably stripping DynAPI and just
name it CoreSomething)
but I was kinda following the linux naming scheme (like redhat linux, corel
linux, etc..)

I think the most important thing is getting a  "point man" at this time..
anybody!?


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



-----Oorspronkelijk bericht-----
Van: dyn...@li...
[mailto:dyn...@li...]Namens Scott Andrew
LePera
Verzonden: donderdag 26 oktober 2000 18:36
Aan: dyn...@li...
Onderwerp: Re: [Dynapi-Dev] improvements, widgets and stuff


(Warning: constructive criticism ahead ;-)

One of the reasons I didn't use the patch manager is because I wasn't
sure my patches would be reviewed by anyone. That's why I asked :-)

Rob was kind enough to put a ZIP of my mods up on sourceforge. You can
grab them at http://dynapi.sourceforge.net/users/scottandrew/

If it makes it any easier for anyone , I can paste my changes into the
patch manager.  But the ZIP file contains documentation as to *why* I
made the changes.

As for maintenance, I have following notes/thoughts:

- We should CHECK RIGHT NOW to make sure that the current release is in
fact stable and not missing anything (see Jack's getDocument() thread.)

- If you make ANY mods/patches or widgets, you should be sure to
download the latest build and work from that.  This is especially
important if several months have passed since you downloaded the core.
You should make sure that your new mods/widgets work with the "official"
release first.

- We really should have a "benchmark" file in the distribution for
testing.  For example, a single HTML page that creates a single
DynLayer, a DynLayer with 1 or more children, a simple widget (like a
label) and a complex widget (like a DynWindow).  When you make
modifications, you should use this page to check that your code does not
break anything in the page, from a simple DynLayer to a huge widget.

This would have come in really handy when I was making my changes; I was
getting ready to submit them when at the last minute I decided to check
if nested DynLayers still worked.  It didn't! And I was able to uncover
a bug that would have seriously broken widgets.  If we had a test file
like I described, we could see immediately what breaks.

- I know that everyone likes to tweak their own copy distribution, and
that's fine.  But make sure your tweaks don't end up in the sourceforge
code unless you follow the patch submission rules.

- Pascal's correct: we need a "point man" to maintain the release.

And, Pascal, I know you maintain a completely separate release at your
site, but I don't think it's clear enough to new users that yours is not
the 'official' release.  Would you consider naming it something else
besides "DynAPI?"  I'm concerned that people will still confuse it with
the SourceForge distribution and then wonder why the widget they grabbed
from SourceForge doesn't work.  I think your distribution is
sufficiently different enough to merit it's own name, and would also
give you license to really do your own thing.  I think that should apply
to anyone who wants to take DynAPI2 and go their own way with it.

Anyway, these are all just my feelings.  We should have a discussion
about some of these issues, because people are starting to discover the
potential of DynAPI2 and we should really get on the same page and get
the distribution up to speed.
_______________________________________________
Dynapi-Dev mailing list
Dyn...@li...
http://lists.sourceforge.net/mailman/listinfo/dynapi-dev

[Dynapi-Dev] patches submitted

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

Okay, I was able to finally get onto SourceForge and submit all my
patches (not the widgets yet).  Have at them.

BTW, has anyone noticed that it's easier to get to/navigate  SourceForge
with NS than IE?

Re: [Dynapi-Dev] improvements, widgets and stuff

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

(Warning: constructive criticism ahead ;-)

One of the reasons I didn't use the patch manager is because I wasn't
sure my patches would be reviewed by anyone. That's why I asked :-)  

Rob was kind enough to put a ZIP of my mods up on sourceforge. You can
grab them at http://dynapi.sourceforge.net/users/scottandrew/

If it makes it any easier for anyone , I can paste my changes into the
patch manager.  But the ZIP file contains documentation as to *why* I
made the changes.

As for maintenance, I have following notes/thoughts:

- We should CHECK RIGHT NOW to make sure that the current release is in
fact stable and not missing anything (see Jack's getDocument() thread.)

- If you make ANY mods/patches or widgets, you should be sure to
download the latest build and work from that.  This is especially
important if several months have passed since you downloaded the core. 
You should make sure that your new mods/widgets work with the "official"
release first.

- We really should have a "benchmark" file in the distribution for
testing.  For example, a single HTML page that creates a single
DynLayer, a DynLayer with 1 or more children, a simple widget (like a
label) and a complex widget (like a DynWindow).  When you make
modifications, you should use this page to check that your code does not
break anything in the page, from a simple DynLayer to a huge widget.

This would have come in really handy when I was making my changes; I was
getting ready to submit them when at the last minute I decided to check
if nested DynLayers still worked.  It didn't! And I was able to uncover
a bug that would have seriously broken widgets.  If we had a test file
like I described, we could see immediately what breaks.

- I know that everyone likes to tweak their own copy distribution, and
that's fine.  But make sure your tweaks don't end up in the sourceforge
code unless you follow the patch submission rules.

- Pascal's correct: we need a "point man" to maintain the release.

And, Pascal, I know you maintain a completely separate release at your
site, but I don't think it's clear enough to new users that yours is not
the 'official' release.  Would you consider naming it something else
besides "DynAPI?"  I'm concerned that people will still confuse it with
the SourceForge distribution and then wonder why the widget they grabbed
from SourceForge doesn't work.  I think your distribution is
sufficiently different enough to merit it's own name, and would also
give you license to really do your own thing.  I think that should apply
to anyone who wants to take DynAPI2 and go their own way with it.

Anyway, these are all just my feelings.  We should have a discussion
about some of these issues, because people are starting to discover the
potential of DynAPI2 and we should really get on the same page and get
the distribution up to speed.

RE: [Dynapi-Dev] improvements, widgets and stuff

[Pascal B. <pb...@oi...>]

Hi,

This is one of the biggest problems at this point: maintaining the release.
I've been doing some update-maintaining, but I don't really feel that's a
good
thing. I got my own distribution to maintain, and somebody else should be
making sure the official release is correctly working and frequently
updated.

If anybody wants to take the job (Ilmaestro or Robert?) please do.. I will
leave
the official download version alone from now (screwed it up to many times :)
so
I will only be helping out with bugs, patches and ofcourse some support.

Scott, do you have access to sourceforge? if so, you can post the patches
there
I'll gladly take a look at them.

greets.

Pascal Bestebroer
pb...@oi...
http://www.oibv.com


-----Oorspronkelijk bericht-----
Van: dyn...@li...
[mailto:dyn...@li...]Namens Scott Andrew
LePera
Verzonden: donderdag 26 oktober 2000 8:43
Aan: dyn...@li...
Onderwerp: [Dynapi-Dev] improvements, widgets and stuff


Hello all,

I've made some (I think) improvements to the DynAPI2:

- better management of all[] arrays
- fewer memory leaks
- better handling of dyndocuments for multiple windows
- a toString method that works (no more eval(this.obj+"=this") crap) for
both DynLayers and DynDocs
- MouseEvent now also catches ctrl-shift-alt modifiers uniformly
- Right-click events captured in MouseEvent (no more "onrtmousedown";
you test for the button in your listener
- DynAPI.addLibrary method allows you to append new libraries onto
DynAPI for inclusion
- plus a few other transparent tweaks

Also, I have some basic widgets, including a pretty cool CollapseMenu
and Tree.

I've documented all my changes and tested them in IE5 and NS4.7.

I need someone to test my changes and I need to know who to submit all
this stuff to.  Or should I just paste it all into the patch manager? I
haven't done this for awhile.

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

RE: [Dynapi-Dev] Right Events

[Pascal B. <pb...@oi...>]

It does work under ie4, but you can't switch off the context-menu, so
it will just always popup.. but you it is possible to catch the right-mouse

greets,

Pascal Bestebroer


-----Oorspronkelijk bericht-----
Van: dyn...@li...
[mailto:dyn...@li...]Namens Robert Rainwater
Verzonden: donderdag 26 oktober 2000 8:43
Aan: DynAPI Dev
Onderwerp: [Dynapi-Dev] Right Events



Hi,

> By: dcpascal
>
> I've included it in my distro. and it seems to work without problems. So
it's
> useable.

Since I don't have access IE 4 anymore, am I to assume that right
click does NOT work for IE 4?  If not, I think it should be documented so
people
will know.

Later,
Robert <rai...@us...>


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

Re: [Dynapi-Dev] some optimization, widgets and stuff

[Robert R. <rai...@us...>]

Hi,

I've uploaded Scott's modifications to the sourceforge server for
everyone to take a look at.

You download it at:
http://dynapi.sourceforge.net/users/scottandrew/dynapi2-sa.zip

Please test away!

Later,
Robert <rai...@us...>

[Dynapi-Dev] some optimization, widgets and stuff

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

Hello all,

I've made some (I think) improvements to the DynAPI2:

- better management of all[] arrays
- fewer memory leaks
- better handling of dyndocuments for multiple windows
- a toString method that works (no more eval(this.obj+"=this") crap) for
both DynLayers and DynDocs
- MouseEvent now also catches ctrl-shift-alt modifiers uniformly
- Right-click events captured in MouseEvent (no more "onrtmousedown";
you test for the button in your listener
- DynAPI.addLibrary method allows you to append new libraries onto
DynAPI for inclusion
- plus a few other transparent tweaks

Also, I have some basic widgets, including a pretty cool CollapseMenu
and Tree.

I've documented all my changes and tested them in IE5 and NS4.7.

I need someone to test my changes (especially in other browsers) and I
need to know who to submit all this stuff to.  Or should I just paste it
all into the patch manager? I haven't done this for awhile.

Best regards,
scottandrew

[Dynapi-Dev] improvements, widgets and stuff

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

Hello all,

I've made some (I think) improvements to the DynAPI2:

- better management of all[] arrays
- fewer memory leaks
- better handling of dyndocuments for multiple windows
- a toString method that works (no more eval(this.obj+"=this") crap) for
both DynLayers and DynDocs
- MouseEvent now also catches ctrl-shift-alt modifiers uniformly
- Right-click events captured in MouseEvent (no more "onrtmousedown";
you test for the button in your listener
- DynAPI.addLibrary method allows you to append new libraries onto
DynAPI for inclusion
- plus a few other transparent tweaks

Also, I have some basic widgets, including a pretty cool CollapseMenu
and Tree.

I've documented all my changes and tested them in IE5 and NS4.7.

I need someone to test my changes and I need to know who to submit all
this stuff to.  Or should I just paste it all into the patch manager? I
haven't done this for awhile.

Best regards,
scottandrew

[Dynapi-Dev] Right Events

[Robert R. <rai...@us...>]

Hi,

> By: dcpascal
> 
> I've included it in my distro. and it seems to work without problems. So it's
> useable.

Since I don't have access IE 4 anymore, am I to assume that right
click does NOT work for IE 4?  If not, I think it should be documented so people
will know.

Later,
Robert <rai...@us...>