You can subscribe to this list here.
2000 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(11) |
---|---|---|---|---|---|---|---|---|---|---|---|---|
2001 |
Jan
(66) |
Feb
(52) |
Mar
(88) |
Apr
(27) |
May
(17) |
Jun
(18) |
Jul
(5) |
Aug
(12) |
Sep
(4) |
Oct
(4) |
Nov
(3) |
Dec
(3) |
2002 |
Jan
(6) |
Feb
|
Mar
|
Apr
(1) |
May
(5) |
Jun
(8) |
Jul
(8) |
Aug
(5) |
Sep
(8) |
Oct
(16) |
Nov
(6) |
Dec
(4) |
2003 |
Jan
(9) |
Feb
(5) |
Mar
(7) |
Apr
(6) |
May
(7) |
Jun
(12) |
Jul
(15) |
Aug
(17) |
Sep
(12) |
Oct
(16) |
Nov
(29) |
Dec
(27) |
2004 |
Jan
(65) |
Feb
(120) |
Mar
(50) |
Apr
(36) |
May
(21) |
Jun
(11) |
Jul
(20) |
Aug
(16) |
Sep
(11) |
Oct
(25) |
Nov
(22) |
Dec
(36) |
2005 |
Jan
(11) |
Feb
(25) |
Mar
(41) |
Apr
(7) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(4) |
Dec
|
2006 |
Jan
(1) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
From: Volker R. <Vol...@bi...> - 2001-02-23 10:25:29
|
Hi there, started to develop my first widget. it is kind of a bubblehelp that works like the alt-tag in images. with the mouseover a description is shown. There is still some work to be done to make it a widget (maybe some day). Are there any people interested in it? i would then keep on working it to get a usable tool. you find a demo at www.web-dizain.de/bubblehelp/ Just move your cursor over the links and see.... volker P.S.: i was trying to do an implementation of the maybe known overlib.js into dynapi2... |
From: David C. <dle...@ya...> - 2001-02-22 16:08:26
|
Greetings, regarding the delay of the onmouseout in buttonimage (does not fire till the second mouseover): I traced the problem back to the code where it changes the .src of the image. The image for the button is set with a setHTML call and is named. The program code then uses the name to change the source (.src). If the code is given a setTimeout and then the images are swapped in the initial setup, it works normally. It seems to be hanging when the following code is executed the first time: ButtonImage.prototype.change = function(img) { if (img) this.doc.images[this.id+"Image"].src = img.src; }; Is this a problem with the setHTML method, the dynimage code or a problem with the images array in NN6? Anybody have any ideas? Cheers, Dave C. "You Changed What?!?" __________________________________________________ Do You Yahoo!? Yahoo! Auctions - Buy the things you want at great prices! http://auctions.yahoo.com/ |
From: Pascal <pb...@oi...> - 2001-02-22 07:40:15
|
you are aware of the popup menu right? use a toolbar with a button.. when the button is pressed display the popup.. just an idea. Pascal Bestebroer (pb...@oi...) Software ontwikkelaar Oberon Informatiesystemen b.v. http://www.oibv.com > -----Oorspronkelijk bericht----- > Van: dyn...@li... > [mailto:dyn...@li...]Namens Ken Ono > Verzonden: donderdag 22 februari 2001 8:32 > Aan: dyn...@li... > Onderwerp: RE: [Dynapi-Widgetdev] Pulldown menu widget (1st attempt > failed) > > > I've changed my approach. Instead of trying to extend CoreButton and > CoreToolBar, i copied the code and changed it. This seem to be going > better. > > Don't waste your time looking at this. > > Thanks anyways. > > Ken > > > > -----Original Message----- > > From: dyn...@li... > > [mailto:dyn...@li...]On > Behalf Of Ken > > Ono > > Sent: Wednesday, February 21, 2001 12:54 PM > > To: dyn...@li... > > Subject: [Dynapi-Widgetdev] Pulldown menu widget (1st > attempt failed) > > > > > > Hello, > > > > Attached is my first attempt at creating a pulldown menu > widget. Any help > > would be greatly appreciated. > > > > My approach was to build the pulldown menus as a series of > toolbars and > > buttons. I attempted to extend CoreToolBar and CoreButton. > The code > > currently simply creates the buttons and tools bars. Event > handling stuff > > is not present. > > > > Anyway, addChild is complaining about something. I'm doing > > something wrong > > (hopefully not too stupid) and I'm now i'm starting to step > > through reams of > > dynlayer code and I bet it's something an expert can answer quickly. > > > > I also ran into a null reference problem. On line 155 of > > dynlayer.js of the > > 01-25 release, child.css was null. Could be a symptom, but > in any event I > > changed it (without an understanding of what's going on) to the > > following to > > get to the next problem. > > > > if (child.z!=null && child.css!=null) child.css.zIndex=child.z; > > > > BTW, is anybody else developing a pulldown menu widget? > > > > Regards, > > > > Ken > > > > > _______________________________________________ > Dynapi-Widgetdev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-widgetdev > |
From: Ken O. <ko...@an...> - 2001-02-21 23:03:48
|
I've changed my approach. Instead of trying to extend CoreButton and CoreToolBar, i copied the code and changed it. This seem to be going better. Don't waste your time looking at this. Thanks anyways. Ken > -----Original Message----- > From: dyn...@li... > [mailto:dyn...@li...]On Behalf Of Ken > Ono > Sent: Wednesday, February 21, 2001 12:54 PM > To: dyn...@li... > Subject: [Dynapi-Widgetdev] Pulldown menu widget (1st attempt failed) > > > Hello, > > Attached is my first attempt at creating a pulldown menu widget. Any help > would be greatly appreciated. > > My approach was to build the pulldown menus as a series of toolbars and > buttons. I attempted to extend CoreToolBar and CoreButton. The code > currently simply creates the buttons and tools bars. Event handling stuff > is not present. > > Anyway, addChild is complaining about something. I'm doing > something wrong > (hopefully not too stupid) and I'm now i'm starting to step > through reams of > dynlayer code and I bet it's something an expert can answer quickly. > > I also ran into a null reference problem. On line 155 of > dynlayer.js of the > 01-25 release, child.css was null. Could be a symptom, but in any event I > changed it (without an understanding of what's going on) to the > following to > get to the next problem. > > if (child.z!=null && child.css!=null) child.css.zIndex=child.z; > > BTW, is anybody else developing a pulldown menu widget? > > Regards, > > Ken > |
From: Ken O. <ko...@an...> - 2001-02-21 17:52:45
|
Hello, Attached is my first attempt at creating a pulldown menu widget. Any help would be greatly appreciated. My approach was to build the pulldown menus as a series of toolbars and buttons. I attempted to extend CoreToolBar and CoreButton. The code currently simply creates the buttons and tools bars. Event handling stuff is not present. Anyway, addChild is complaining about something. I'm doing something wrong (hopefully not too stupid) and I'm now i'm starting to step through reams of dynlayer code and I bet it's something an expert can answer quickly. I also ran into a null reference problem. On line 155 of dynlayer.js of the 01-25 release, child.css was null. Could be a symptom, but in any event I changed it (without an understanding of what's going on) to the following to get to the next problem. if (child.z!=null && child.css!=null) child.css.zIndex=child.z; BTW, is anybody else developing a pulldown menu widget? Regards, Ken |
From: Darin K. <dka...@ef...> - 2001-02-20 20:12:44
|
-------------------------------------------------- Darin Kadrioski Applications/Internet Developer > Electronic Freight Exchange, Corp. dka...@ef... (916) 933-0724 x315 |
From: Robert R. <rra...@ya...> - 2001-02-20 07:27:18
|
I find the examples a great tool. Too often than not, there are bugs that are posted with widgets and it is very difficult to debug dynapi bugs in complex widgets. The examples demonstrate the core functionality. I tested the events using the example included w/ the dynapi except I added nested layers. Tests like these are more valuable when you are trying to test bugs in the dynlayer events. If you can prove whether a bug is a dynlayer bug or not, then you can save yourself a lot of time that you can waste debugging widgets. -- // Robert Rainwater On 2/20/2001, 2:02:29 AM EST, Eytan wrote about "[Dynapi-Widgetdev] NN6 onmouseout delay?": > Just as a general note the examples in the DynAPI are just examples and are > not real world tests. > 8an > _______________________________________________ > Dynapi-Widgetdev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-widgetdev |
From: Eytan H. <ey...@tr...> - 2001-02-20 07:02:27
|
Just as a general note the examples in the DynAPI are just examples and are not real world tests. 8an |
From: David C. <dle...@ya...> - 2001-02-20 05:55:29
|
Hey Robert, I stripped the page down to just the bare code creating the buttonimage and got the same results. I also checked the mouse events example and it was normal. code: <script language="Javascript" src="../src/dynapi.js"></script> <script language="Javascript"> DynAPI.setLibraryPath('../src/lib/') DynAPI.include('dynapi.api.*'); DynAPI.include('dynapi.gui.dynimage'); DynAPI.include('dynapi.gui.buttonimage'); DynAPI.onLoad=function() { p1uimg = DynImage.getImage('butovu.gif',100,35); p1oimg = DynImage.getImage('butovh.gif'); p1dimg = DynImage.getImage('butovs.gif'); p1rimg = DynImage.getImage('butovh2.gif'); buti01 = new ButtonImage(); buti01.moveTo(40,100); DynAPI.document.addChild(buti01); DynImage.onLoaderDone=function() { buti01.setImages(p1uimg,p1oimg,p1dimg,p1rimg); } }; </script> see this here: http://www.merlinsworld.net/dynapi_ri_dcexamples/image_button2.html I will look for problems in buttonimage.js tomorrow. If you see something wrong in how I am creating the button, let me know please? Cheers, Dave C. "You Changed What?!?" __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/ |
From: Robert R. <rra...@ya...> - 2001-02-20 02:31:54
|
I noticed the same with your example in Mozilla, but it seems to be a glitch somewhere in your code. Using the examples included with the dynapi, the onmouseout event seems to be firing correctly. -- // Robert Rainwater On 2/19/2001, 9:11:56 PM EST, David wrote about "[Dynapi-Widgetdev] NN6 onmouseout delay?": > Greetings, > Has anyone noticed a "glitch" in NN6 and DynAPI > where the onmouseout does not fire till the second > time you pass over the object? I was looking at > compatibility problems with my image menu and started > checking out the individual sections. I tested the > normal buttonimage and found this happenning. Maybe > it is in my code, but it seems to be repeatable in > other examples as well. After passing over the object > a second time (second onmouseover) the onmouseout > starts working normally. > See it here: > http://www.merlinsworld.net/dynapi_ri_dcexamples/image_button.html > Comments? Suggestions? > Cheers, > Dave C. "You Changed What?!?" > __________________________________________________ > Do You Yahoo!? > Get personalized email addresses from Yahoo! Mail - only $35 > a year! http://personal.mail.yahoo.com/ > _______________________________________________ > Dynapi-Widgetdev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-widgetdev |
From: David C. <dle...@ya...> - 2001-02-20 02:11:02
|
Greetings, Has anyone noticed a "glitch" in NN6 and DynAPI where the onmouseout does not fire till the second time you pass over the object? I was looking at compatibility problems with my image menu and started checking out the individual sections. I tested the normal buttonimage and found this happenning. Maybe it is in my code, but it seems to be repeatable in other examples as well. After passing over the object a second time (second onmouseover) the onmouseout starts working normally. See it here: http://www.merlinsworld.net/dynapi_ri_dcexamples/image_button.html Comments? Suggestions? Cheers, Dave C. "You Changed What?!?" __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/ |
From: Michael P. <mp...@ph...> - 2001-02-20 00:42:05
|
here's the core set of files for the gui components. the api can be replaced with the dynapi code. "Henrik Våglin" wrote: > It sounds interesting, but I'm missing quite a few items from the afroapi pack. Do you have an update zipfile you could post maybe? > > Henrik Våglin [ hv...@ya... ] > > ----- Original Message ----- > From: "Michael Pemberton" <mp...@ph...> > To: <dyn...@li...> > Sent: Monday, February 19, 2001 3:58 PM > Subject: [Dynapi-Widgetdev] additional Popup Functionality > > > I've added the ability to place Icons on my Popup menu. It's attached. > > > > -- > > Michael Pemberton > > mp...@ph... > > ICQ: 12107010 > > > > > > _________________________________________________________ > Do You Yahoo!? > Get your free @yahoo.com address at http://mail.yahoo.com > > _______________________________________________ > Dynapi-Widgetdev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-widgetdev -- Michael Pemberton mp...@ph... ICQ: 12107010 |
From: Nicola M. <nic...@ho...> - 2001-02-19 21:59:21
|
ie 6 is way far to the final release a lot of stuff is not working yet so forget about that but the ns 6 problem looks like something it's wrong in the code since i had stuff similar to that working with no problem in ns 6 even with the old release of DynAPI 2 ciao Y _________________________________________________________________ Get your FREE download of MSN Explorer at http://explorer.msn.com |
From: Lujan I. F. <lu...@sa...> - 2001-02-19 21:36:34
|
I tried the address provided by David Cushman at http://www.merlinsworld.net/dynapi_ri_dcexamples/button_menu.html and it worked OK in Netscape 4.7 and IE 5.5, but it worked extremely slow using Netscape 6.0 and it didn't work at all using IE 6.0 beta. The images (buttons) didn't display at using IE 6.0. Maybe we shouldn't be concerned with IE 6.0 since it is a beta product, but it wouldn't be acceptable using Netscape 6.0 since it is soooo very slow. I don't think it's my processor since I'm using a 550 processor. The only other thing I noticed (both IE 5.5 and NN 4.7) is that the menu off the first "Button 2" seemed a little bit sluggish where it would take several seconds to go to another button after you left that drop down. Thanks Frank -----Original Message----- From: dyn...@li... [mailto:dyn...@li...] Sent: February 17, 2001 1:01 PM To: dyn...@li... Subject: Dynapi-Widgetdev digest, Vol 1 #30 - 6 msgs Send Dynapi-Widgetdev mailing list submissions to dyn...@li... To subscribe or unsubscribe via the World Wide Web, visit http://lists.sourceforge.net/lists/listinfo/dynapi-widgetdev or, via email, send a message with subject or body 'help' to dyn...@li... You can reach the person managing the list at dyn...@li... When replying, please edit your Subject line so it is more specific than "Re: Contents of Dynapi-Widgetdev digest..." Today's Topics: 1. Re: Collapse Menu (David Cushman) 2. Re: Collapse Menu (Richard Bennett) 3. RE: RE: [Dynapi-Help] Widget test Image button menu (Ken Ono) 4. Re: RE: RE: [Dynapi-Help] Widget test Image button menu (David Cushman) 5. NN6 and too many event listeners (David Cushman) 6. RE: NN6 and too many event listeners (Pascal Bestebroer) --__--__-- Message: 1 Date: Fri, 16 Feb 2001 13:09:32 -0800 (PST) From: David Cushman <dle...@ya...> Subject: Re: [Dynapi-Widgetdev] Collapse Menu To: Dyn...@li... Reply-To: dyn...@li... Hey Frank, Not sure how the original worked, but I posted a widget that does wipe and slide of the first main menu, using an image button as the trigger. Take a look and if it does not do what you want, tell me what things it does not do and I will see if I can do a mod. Example: http://www.merlinsworld.net/dynapi_ri_dcexamples/button_menu.html Cheers, Dave C. "You Changed What?!?" "Does anyone know if someone has created a Collapse Menu with the sliding feature (that works with IE4+ and Netscape 4+ for Dynapi II) as was available on the Dynapi I site under Widgets? Thanks Frank" __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/ --__--__-- Message: 2 From: "Richard Bennett" <ma...@ri...> To: <dyn...@li...> Subject: Re: [Dynapi-Widgetdev] Collapse Menu Date: Sat, 17 Feb 2001 01:04:55 +0100 Reply-To: dyn...@li... No, that one is still missing from our collection :O( Cheers, Richard Bennett ma...@ri... www.richardinfo.com (Everything running on, and ported to the 19/12/2000 snapshot of DynAPI2) Find the DynAPI faq here: http://sourceforge.net/docman/display_doc.php?docid=656&group_id=5757 Browse the mailinglist here: http://www.mail-archive.com/index.php3?hunt=dynapi ----- Original Message ----- From: "Lujan III, Frank" <lu...@sa...> To: <dyn...@li...> Sent: Friday, February 16, 2001 6:58 PM Subject: [Dynapi-Widgetdev] Collapse Menu > Does anyone know if someone has created a Collapse Menu with the sliding > feature (that works with IE4+ and Netscape 4+ for Dynapi II) as was > available on the Dynapi I site under Widgets? > > Thanks > Frank > > > _______________________________________________ > Dynapi-Widgetdev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-widgetdev > ____________________________________________________________ > Get your free domain name and domain-based e-mail from > Namezero.com. New! Namezero Plus domains now available. > Find out more at: http://www.namezero.com > --__--__-- Message: 3 From: "Ken Ono" <ko...@an...> To: <Dyn...@li...> Date: Sat, 17 Feb 2001 06:29:19 -0500 Subject: [Dynapi-Widgetdev] RE: RE: [Dynapi-Help] Widget test Image button menu Reply-To: dyn...@li... David, > I found the API, well, akward, at least for my purposes. I've been doing some thinking on what the interface could be. What are your thoughts on something like: menuName.addMenuItem( id, type, menuItem, [data], [parent id], [before id], [group] ) id = a unique identifier type = "menu", "command", "seperator", "blank" menuItem = another object with visual info or just a string (in which case a menuItem is generated) [data] = some data to store that is passed pack when menu selected (i.e. the URL) [parent id] = the ID of the parent if it is not on the root [before id] = the ID of the item for this choice to be insert before. If empty, add to the end [group]= a way of grouping commands - (can be used to diable commands in groups) menuItem Class: .caption = text to display (with & notation for key accelerators (e.g &File) .defaultButtonImage (optional - image for whole cell) .rolloverButtonImage (optional - image for whole cell) .mouseButtonDownImage (optional - image for whole cell) .selectedButtonImage (optional - image for whole cell) .disabledButtonImange (optionl - image when cell disable) .defaultClass (optional - for CSS link and text cells) .selectedClass (optional - CSS class when selected) .disabledClass (optional - CSS class when disabled) .buttonDownClass (optional - CSS class when pressed) .rolloverClass(optional - CSS class when mouse on) .iconSmallImage (optional - small icon to be displayed to left of caption - just like Windows) .iconLarge (optional - a bigger icon for ?) .text (optional string for tool tips or status bar text) .<positioning info> (optional - to allow for funky menus) A user would create a menu object (opposed to number of buttons) and then add menus and choices. For example (to use some familar menu structures): myMenu = New NavigationWidget(size & positioning stuff for menu) myMenu.addMenuItem("file", "menu", "&File"); // Create a file menu myMenu.addMenuItem("filesave", "command", "Save", "FileSave.htm", "file"); // Add choice to menu myMenu.addMenuItem("edit", "menu", "&Edit"); // Create edit menu myMenu.addMenuItem("editcopy", "command", "&Copy", "EditCopy.htm", "edit"); myMenu.addMenuItem("view", "menu", "&View"); // Create view menu myMenu.addMenuItem("next", "menu", "&Next", "view"); // Create sub menu myMenu.addMenuItem("nextmessage", "command", "&Message", "next", "ViewNextMessage.htm"); // Add a choice to sub menu The widget should fire an event and pass the "id" and "data" (URL) when a choice is selected. To do something fancier: myCell = New menuItem("some text", myImage1, myimage2, positions, etc); myMenu.AddMenuItem("id", "menu", myCell) I haven't begun to consider implementation (although I've done similar things in other languages). At the moment, I'm only looking at it from an interface point of view. If we nail a good interface, other developers might adopt it. It would be great if one had a choice of many different menu systems and it was trivial to switch between them. What are your thoughts? Regards, Ken --__--__-- Message: 4 Date: Sat, 17 Feb 2001 08:40:58 -0800 (PST) From: David Cushman <dle...@ya...> Subject: Re: [Dynapi-Widgetdev] RE: RE: [Dynapi-Help] Widget test Image button menu To: dynapi widget <dyn...@li...> Reply-To: dyn...@li... Hey Ken, Some good stuff there. Let me start out by explaining the goal of the original widget. I wanted to be able to use the wipe.js to make the popup.js appear when triggered by an image button (based on buttonimage.js). I wanted to use the popup.js as is for compatibility purposes (have made changes now as noted below). Second, I wanted to have several instances on the page that would not interfere with each other. Changes to popup.js: Altered the create listener to make it precreate added line to precreate listener to remove itself NN6 has a real problem with execution speed when too many listeners are active added lines to mouse item events to ignore submenu items and blank items. To address your comments (just why they are what they are, not that they cannot be changed) "Also, it seems unreasonable to to provide information like menu depth and number of submenus when it has all the info necessary to to figure that stuff out." number of submenus: The structure is that it names the main menu (the one with the effect) "menu" nad each submenu "MenuSub[]" as part of an array. This uniform naming allows the resizing and assigning of submenus to be done with just a number. I could have assigned the submenus as they were initialized also. That may be a good change. The menu depth is left over code, not removed yet. The widget now calculates the total display width of the menu system for the "trapping" layer. Other items in the initial setup "items below main" I am working on having the widget calculate this I am having problems understanding what the goals of your code are. However I have just started looking at it and will probably understand better after going over it a few times. If you have time, could you write out what it is supposed to do? Maybe the fasttreenode.js or treenode.js is closer to what you are trying to do? They are available at Richard's site under Richard's examples. http://www.resass.f2s.com/dynapi/php/index2.php For everyone else, we are discussing my image button menu widget. Viewable here: http://www.merlinsworld.net/dynapi_ri_dcexamples/button_menu.html Cheers Dave C. "You Changed What?!?" __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/ --__--__-- Message: 5 Date: Sat, 17 Feb 2001 09:52:49 -0800 (PST) From: David Cushman <dle...@ya...> To: dynapi widget <dyn...@li...> Subject: [Dynapi-Widgetdev] NN6 and too many event listeners Reply-To: dyn...@li... Greetings, First I know that we are not compatible with NN6 yet, but I still test my pages and widgets under NN6. NN6 has a tendancy to slow down to a crawl with complicated DynAPI examples. One thing I have noticed and tested is that the more active event listeners on the page, the slower (or not at all) it goes. On my menu widget, I started adding code in that removes the event listeners when they are not needed. The precreate listeners include a line at the end to remove themeselves and the menu item listeners are also removed and added when active. Question 1 Has anyone else noticed this or has a better understanding of what is happenning? Question 2 Does removing and adding event listeners increase the browsers footprint in memory each time the add is executed? Question 3 Can anyone suggest a good utility to monitor the browsers footprint in memory? Cheers, Dave C. "You Changed What?!?" __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/ --__--__-- Message: 6 From: "Pascal Bestebroer" <pa...@dy...> To: <dyn...@li...> Subject: RE: [Dynapi-Widgetdev] NN6 and too many event listeners Date: Sat, 17 Feb 2001 19:02:11 +0100 Reply-To: dyn...@li... It would be strange if eventlisteners slow things down.. you would need alot of eventlisteners. Note that even though we call them listeners, there not listening all the time.. they are more handlers (and no, we're not renaming them) Everytime an invokeEvent('eventname') is done, the invokeevent function will walk thru the array of eventlisteners (just a simple array of objects) and see if the corresponding event is attached to it.. if it is, it will call that method of that eventlistener object. It doesn't make sense that it slows down so noticeable, do you have a url we can check to see it? q2. It might, not sure if normal javascript objects also increase the footprint (or just dynamically generated html objects). q3. Taskinfo seems to be a complete tool for memory/cpu timing: http://www.iarsn.com/ Pascal Bestebroer pa...@dy... http://www.dynamic-core.net > -----Oorspronkelijk bericht----- > Van: dyn...@li... > [mailto:dyn...@li...]Namens David > Cushman > Verzonden: zaterdag 17 februari 2001 18:53 > Aan: dynapi widget > Onderwerp: [Dynapi-Widgetdev] NN6 and too many event listeners > > > Greetings, > First I know that we are not compatible with NN6 > yet, but I still test my pages and widgets under NN6. > NN6 has a tendancy to slow down to a crawl with > complicated DynAPI examples. One thing I have noticed > and tested is that the more active event listeners on > the page, the slower (or not at all) it goes. On my > menu widget, I started adding code in that removes the > event listeners when they are not needed. The > precreate listeners include a line at the end to > remove themeselves and the menu item listeners are > also removed and added when active. > Question 1 Has anyone else noticed this or has a > better understanding of what is happenning? > Question 2 Does removing and adding event listeners > increase the browsers footprint in memory each time > the add is executed? > Question 3 Can anyone suggest a good utility to > monitor the browsers footprint in memory? > > Cheers, > Dave C. "You Changed What?!?" > > __________________________________________________ > Do You Yahoo!? > Get personalized email addresses from Yahoo! Mail - only $35 > a year! http://personal.mail.yahoo.com/ > > _______________________________________________ > Dynapi-Widgetdev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-widgetdev > --__--__-- _______________________________________________ Dynapi-Widgetdev mailing list Dyn...@li... http://lists.sourceforge.net/lists/listinfo/dynapi-widgetdev End of Dynapi-Widgetdev Digest |
From: Henrik V. <hv...@ya...> - 2001-02-19 17:23:49
|
It sounds interesting, but I'm missing quite a few items from the = afroapi pack. Do you have an update zipfile you could post maybe? Henrik V=E5glin [ hv...@ya... ] ----- Original Message -----=20 From: "Michael Pemberton" <mp...@ph...> To: <dyn...@li...> Sent: Monday, February 19, 2001 3:58 PM Subject: [Dynapi-Widgetdev] additional Popup Functionality > I've added the ability to place Icons on my Popup menu. It's = attached. >=20 > -- > Michael Pemberton > mp...@ph... > ICQ: 12107010 >=20 >=20 _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com |
From: Michael P. <mp...@ph...> - 2001-02-19 15:01:17
|
I've added the ability to place Icons on my Popup menu. It's attached. -- Michael Pemberton mp...@ph... ICQ: 12107010 |
From: Michael P. <mp...@ph...> - 2001-02-18 12:15:36
|
my cell is just a layer that adds the border effect to make it look more windozish. it only effects the base menu canvas. it does not effect the indiividual menu items. Ken Ono wrote: > Hi Dave, > > Thanks for the pointer to the tree widgets. I hadn't had a look at those > yet. (I only discovered DYN API last Wednesday - and I've been hooked ever > since.) > > Anyway, that interface is more or less what I was trying to achieve. It's > doing things in a slightly different way. (I think in a better way - but > I'm not sure yet.) So essentially my code example was simply defining a > hierarchical menu structure in a similar way to the various tree examples. > > Some of my goals are: > > * To be able to build multi-level pull down menus (like Windows applications > or the microsoft web site) > * Have a standardized (and extendable) interface for a variety of > hierarchical selection objects such as pulldown menus, tree selectors, > outlook sytle menus, bottom based menus, anything imaginable > * Higher level tools (akin to Razor) could use this common interface afford > a lot of flexability for skins. For example, one skin chould have pulldown > menus. Another skin could have a slide in tree. Another skin could have > lamp posts. > * As way of quickly wacking out these applications and easily maintaining > them something like the XML and XSLT example I posted could be used. > > Another thought that occurred to me, is that things may be nicely rounded > out if popup.js used buttonimage.js as its individual choices. Michael > Pemberton had a post very similar to this recently that changed popup.js to > use a cell.js. A pulldown menu can be a toolbar that aggregates buttons > that spawn popups that aggregates buttons that spawn popups and so on. > > As a general question, is there any good reason that more widgets aren't > part of the 01-25 release? One of the more difficult tasks I'm having > ramping up is knowning what widgets are there, what works with what etc. > Also, pulling in multiple widgets from multiple people is starting to be > confusing. I very much appreciate Richard's ongoing directory standard > structure efforts. Are the widgets going to be part of the release in the > future (and in CVS)? > > TTFN > > Ken > > _______________________________________________ > Dynapi-Widgetdev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-widgetdev -- Michael Pemberton mp...@ph... ICQ: 12107010 |
From: Ken O. <ko...@an...> - 2001-02-17 21:30:30
|
Hi Dave, Thanks for the pointer to the tree widgets. I hadn't had a look at those yet. (I only discovered DYN API last Wednesday - and I've been hooked ever since.) Anyway, that interface is more or less what I was trying to achieve. It's doing things in a slightly different way. (I think in a better way - but I'm not sure yet.) So essentially my code example was simply defining a hierarchical menu structure in a similar way to the various tree examples. Some of my goals are: * To be able to build multi-level pull down menus (like Windows applications or the microsoft web site) * Have a standardized (and extendable) interface for a variety of hierarchical selection objects such as pulldown menus, tree selectors, outlook sytle menus, bottom based menus, anything imaginable * Higher level tools (akin to Razor) could use this common interface afford a lot of flexability for skins. For example, one skin chould have pulldown menus. Another skin could have a slide in tree. Another skin could have lamp posts. * As way of quickly wacking out these applications and easily maintaining them something like the XML and XSLT example I posted could be used. Another thought that occurred to me, is that things may be nicely rounded out if popup.js used buttonimage.js as its individual choices. Michael Pemberton had a post very similar to this recently that changed popup.js to use a cell.js. A pulldown menu can be a toolbar that aggregates buttons that spawn popups that aggregates buttons that spawn popups and so on. As a general question, is there any good reason that more widgets aren't part of the 01-25 release? One of the more difficult tasks I'm having ramping up is knowning what widgets are there, what works with what etc. Also, pulling in multiple widgets from multiple people is starting to be confusing. I very much appreciate Richard's ongoing directory standard structure efforts. Are the widgets going to be part of the release in the future (and in CVS)? TTFN Ken |
From: Pascal B. <pa...@dy...> - 2001-02-17 18:01:48
|
It would be strange if eventlisteners slow things down.. you would need alot of eventlisteners. Note that even though we call them listeners, there not listening all the time.. they are more handlers (and no, we're not renaming them) Everytime an invokeEvent('eventname') is done, the invokeevent function will walk thru the array of eventlisteners (just a simple array of objects) and see if the corresponding event is attached to it.. if it is, it will call that method of that eventlistener object. It doesn't make sense that it slows down so noticeable, do you have a url we can check to see it? q2. It might, not sure if normal javascript objects also increase the footprint (or just dynamically generated html objects). q3. Taskinfo seems to be a complete tool for memory/cpu timing: http://www.iarsn.com/ Pascal Bestebroer pa...@dy... http://www.dynamic-core.net > -----Oorspronkelijk bericht----- > Van: dyn...@li... > [mailto:dyn...@li...]Namens David > Cushman > Verzonden: zaterdag 17 februari 2001 18:53 > Aan: dynapi widget > Onderwerp: [Dynapi-Widgetdev] NN6 and too many event listeners > > > Greetings, > First I know that we are not compatible with NN6 > yet, but I still test my pages and widgets under NN6. > NN6 has a tendancy to slow down to a crawl with > complicated DynAPI examples. One thing I have noticed > and tested is that the more active event listeners on > the page, the slower (or not at all) it goes. On my > menu widget, I started adding code in that removes the > event listeners when they are not needed. The > precreate listeners include a line at the end to > remove themeselves and the menu item listeners are > also removed and added when active. > Question 1 Has anyone else noticed this or has a > better understanding of what is happenning? > Question 2 Does removing and adding event listeners > increase the browsers footprint in memory each time > the add is executed? > Question 3 Can anyone suggest a good utility to > monitor the browsers footprint in memory? > > Cheers, > Dave C. "You Changed What?!?" > > __________________________________________________ > Do You Yahoo!? > Get personalized email addresses from Yahoo! Mail - only $35 > a year! http://personal.mail.yahoo.com/ > > _______________________________________________ > Dynapi-Widgetdev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-widgetdev > |
From: David C. <dle...@ya...> - 2001-02-17 17:51:59
|
Greetings, First I know that we are not compatible with NN6 yet, but I still test my pages and widgets under NN6. NN6 has a tendancy to slow down to a crawl with complicated DynAPI examples. One thing I have noticed and tested is that the more active event listeners on the page, the slower (or not at all) it goes. On my menu widget, I started adding code in that removes the event listeners when they are not needed. The precreate listeners include a line at the end to remove themeselves and the menu item listeners are also removed and added when active. Question 1 Has anyone else noticed this or has a better understanding of what is happenning? Question 2 Does removing and adding event listeners increase the browsers footprint in memory each time the add is executed? Question 3 Can anyone suggest a good utility to monitor the browsers footprint in memory? Cheers, Dave C. "You Changed What?!?" __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/ |
From: David C. <dle...@ya...> - 2001-02-17 16:40:08
|
Hey Ken, Some good stuff there. Let me start out by explaining the goal of the original widget. I wanted to be able to use the wipe.js to make the popup.js appear when triggered by an image button (based on buttonimage.js). I wanted to use the popup.js as is for compatibility purposes (have made changes now as noted below). Second, I wanted to have several instances on the page that would not interfere with each other. Changes to popup.js: Altered the create listener to make it precreate added line to precreate listener to remove itself NN6 has a real problem with execution speed when too many listeners are active added lines to mouse item events to ignore submenu items and blank items. To address your comments (just why they are what they are, not that they cannot be changed) "Also, it seems unreasonable to to provide information like menu depth and number of submenus when it has all the info necessary to to figure that stuff out." number of submenus: The structure is that it names the main menu (the one with the effect) "menu" nad each submenu "MenuSub[]" as part of an array. This uniform naming allows the resizing and assigning of submenus to be done with just a number. I could have assigned the submenus as they were initialized also. That may be a good change. The menu depth is left over code, not removed yet. The widget now calculates the total display width of the menu system for the "trapping" layer. Other items in the initial setup "items below main" I am working on having the widget calculate this I am having problems understanding what the goals of your code are. However I have just started looking at it and will probably understand better after going over it a few times. If you have time, could you write out what it is supposed to do? Maybe the fasttreenode.js or treenode.js is closer to what you are trying to do? They are available at Richard's site under Richard's examples. http://www.resass.f2s.com/dynapi/php/index2.php For everyone else, we are discussing my image button menu widget. Viewable here: http://www.merlinsworld.net/dynapi_ri_dcexamples/button_menu.html Cheers Dave C. "You Changed What?!?" __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/ |
From: Ken O. <ko...@an...> - 2001-02-17 11:28:27
|
David, > I found the API, well, akward, at least for my purposes. I've been doing some thinking on what the interface could be. What are your thoughts on something like: menuName.addMenuItem( id, type, menuItem, [data], [parent id], [before id], [group] ) id = a unique identifier type = "menu", "command", "seperator", "blank" menuItem = another object with visual info or just a string (in which case a menuItem is generated) [data] = some data to store that is passed pack when menu selected (i.e. the URL) [parent id] = the ID of the parent if it is not on the root [before id] = the ID of the item for this choice to be insert before. If empty, add to the end [group]= a way of grouping commands - (can be used to diable commands in groups) menuItem Class: .caption = text to display (with & notation for key accelerators (e.g &File) .defaultButtonImage (optional - image for whole cell) .rolloverButtonImage (optional - image for whole cell) .mouseButtonDownImage (optional - image for whole cell) .selectedButtonImage (optional - image for whole cell) .disabledButtonImange (optionl - image when cell disable) .defaultClass (optional - for CSS link and text cells) .selectedClass (optional - CSS class when selected) .disabledClass (optional - CSS class when disabled) .buttonDownClass (optional - CSS class when pressed) .rolloverClass(optional - CSS class when mouse on) .iconSmallImage (optional - small icon to be displayed to left of caption - just like Windows) .iconLarge (optional - a bigger icon for ?) .text (optional string for tool tips or status bar text) .<positioning info> (optional - to allow for funky menus) A user would create a menu object (opposed to number of buttons) and then add menus and choices. For example (to use some familar menu structures): myMenu = New NavigationWidget(size & positioning stuff for menu) myMenu.addMenuItem("file", "menu", "&File"); // Create a file menu myMenu.addMenuItem("filesave", "command", "Save", "FileSave.htm", "file"); // Add choice to menu myMenu.addMenuItem("edit", "menu", "&Edit"); // Create edit menu myMenu.addMenuItem("editcopy", "command", "&Copy", "EditCopy.htm", "edit"); myMenu.addMenuItem("view", "menu", "&View"); // Create view menu myMenu.addMenuItem("next", "menu", "&Next", "view"); // Create sub menu myMenu.addMenuItem("nextmessage", "command", "&Message", "next", "ViewNextMessage.htm"); // Add a choice to sub menu The widget should fire an event and pass the "id" and "data" (URL) when a choice is selected. To do something fancier: myCell = New menuItem("some text", myImage1, myimage2, positions, etc); myMenu.AddMenuItem("id", "menu", myCell) I haven't begun to consider implementation (although I've done similar things in other languages). At the moment, I'm only looking at it from an interface point of view. If we nail a good interface, other developers might adopt it. It would be great if one had a choice of many different menu systems and it was trivial to switch between them. What are your thoughts? Regards, Ken |
From: Richard B. <ma...@ri...> - 2001-02-17 00:04:23
|
No, that one is still missing from our collection :O( Cheers, Richard Bennett ma...@ri... www.richardinfo.com (Everything running on, and ported to the 19/12/2000 snapshot of DynAPI2) Find the DynAPI faq here: http://sourceforge.net/docman/display_doc.php?docid=656&group_id=5757 Browse the mailinglist here: http://www.mail-archive.com/index.php3?hunt=dynapi ----- Original Message ----- From: "Lujan III, Frank" <lu...@sa...> To: <dyn...@li...> Sent: Friday, February 16, 2001 6:58 PM Subject: [Dynapi-Widgetdev] Collapse Menu > Does anyone know if someone has created a Collapse Menu with the sliding > feature (that works with IE4+ and Netscape 4+ for Dynapi II) as was > available on the Dynapi I site under Widgets? > > Thanks > Frank > > > _______________________________________________ > Dynapi-Widgetdev mailing list > Dyn...@li... > http://lists.sourceforge.net/lists/listinfo/dynapi-widgetdev > ____________________________________________________________ > Get your free domain name and domain-based e-mail from > Namezero.com. New! Namezero Plus domains now available. > Find out more at: http://www.namezero.com > |
From: David C. <dle...@ya...> - 2001-02-16 21:08:45
|
Hey Frank, Not sure how the original worked, but I posted a widget that does wipe and slide of the first main menu, using an image button as the trigger. Take a look and if it does not do what you want, tell me what things it does not do and I will see if I can do a mod. Example: http://www.merlinsworld.net/dynapi_ri_dcexamples/button_menu.html Cheers, Dave C. "You Changed What?!?" "Does anyone know if someone has created a Collapse Menu with the sliding feature (that works with IE4+ and Netscape 4+ for Dynapi II) as was available on the Dynapi I site under Widgets? Thanks Frank" __________________________________________________ Do You Yahoo!? Get personalized email addresses from Yahoo! Mail - only $35 a year! http://personal.mail.yahoo.com/ |
From: Lujan I. F. <lu...@sa...> - 2001-02-16 17:57:59
|
Does anyone know if someone has created a Collapse Menu with the sliding feature (that works with IE4+ and Netscape 4+ for Dynapi II) as was available on the Dynapi I site under Widgets? Thanks Frank |