[Dynapi-CVS] CVS: dynapi REVISION,1.13,1.14

[Jordi M. <do...@us...>]

Update of /cvsroot/dynapi/dynapi
In directory usw-pr-cvs1:/tmp/cvs-serv1391

Modified Files:
	REVISION 
Log Message:
release


Index: REVISION
===================================================================
RCS file: /cvsroot/dynapi/dynapi/REVISION,v
retrieving revision 1.13
retrieving revision 1.14
diff -C2 -r1.13 -r1.14
*** REVISION	2001/11/06 17:58:53	1.13
--- REVISION	2002/01/15 12:30:37	1.14
***************
*** 15,18 ****
--- 15,50 ----
  [ - Bug Fix                  ]
  
+ 
+ Version 2.5.7
+ -------------
+ This branch ( 2.5.x ) and the newly created 2.9.x ( where new ideas / objects are tested ) are different
+ things and should not be confused.
+ 
+ While they have undergone some bugfixing, it is obvious that the default group of GUI widgets supplied
+ with this distro is too buggy / old / obsolete and need to be rewritten. I plan to rewrite them all
+ for the next release, and probably make them a separate release from the core. This said it is
+ easy to understand that little to no effort has been dedicated to improve the existing widgets for this
+ release, so expect more or less the same flaws ( and even some new ones :) ).
+ 
+ [-] Fixed 2.5.6 drag bug
+ [-] Fixed scrollbar not reaching bottom of the scrolling space when scrolling via 'up' and 'down' buttons
+ [-] Fixed "removeFromParent is destroying the layer" bug.
+ [+] Added disabling contextual menus for each dynlayer ( off by default, example page is provided )
+ [*] By default mouseUps always will happen in the layer were the mousedown happened, even if the mouse
+     was dragged outside the layer ( No more stuck scroll buttons ). This behaviour can be disabled from
+     within mouse.js ( instructions provided inside the file ).
+ [*] Only one event is captured per page. I realized I we were using the event's target properties to determine
+     the dynlayer where it occured, hence with one single event being captured in the document everything works
+     in the same way. Moreover, remember that capturing a layer event was layer.doc.capture....  since all
+     layers share the document ( except NS4 ) we were capturing the same events once and again.
+     Try the strech tests and see how intializacions are a lot faster now. About 4ks of code are gone, as well [:)]
+ [+] You can add layers on load time. Yeap no more waiting for the onload event.
+ [+] Since layers can be added onpage load, they can be made relative.
+     Yep, place them within a table which defines your layout and it will work.
+     Still some flaws ( see example in tests/ directory where a scrollbar is working inside a relative positioned table )
+     but pretty promising. 
+     Please consider this inflow stuff as alpha work and do not consider using it in real projects. It won't work
+ 
+ 
  Version 2.5.6
  -------------