dynapi-widgetdev

Re: [Dynapi-Widgetdev] RE: RE: [Dynapi-Help] Widget test Image button menu

[David C. <dle...@ya...>]

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/

RE: [Dynapi-Widgetdev] RE: RE: [Dynapi-Help] Widget test Image button menu

[Ken O. <ko...@an...>]

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

Re: [Dynapi-Widgetdev] RE: RE: [Dynapi-Help] Widget test Image button menu

[Michael P. <mp...@ph...>]

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