07 The Code. Part 1
From: geoffrey.hoffman-spamblock-gmail.com
Subject: Re: [DIRECT-L] Reusable UI framework code. The code part 1.
Date: January 22, 2007 2:39:27 PM CST
To: DIRECT-L-spamblock-LISTSERV.UARK.EDU
Reply-To: DIRECT-L-spamblock-LISTSERV.UARK.EDU
Not that you were looking for feedback... but...
In the list below, the button is referred to as "Item".
Functionality:
- Item needs to have four graphical states and capability for more if
necessary.
- Item's states are Active or clickable, Rollover, Down Disabled.
When you said Four graphical states, I naturally thought of the special four
frame movie clip that makes a Flash button in The Other Program. However, in
reality 'hit region' is their fourth frame whereas you bring up the idea of
'Disabled' state. I like how simple Flash buttons are to create, but there
is no Disabled state ~ you'd have to invent that on your own.
What would be great is if LDMs worked well enough to make an interface full
of full-fledged Director files in the same way you can do it with The Other
Program.
- Item needs a consistent rollover region to define clickable area in
all states.
The rollover region and the click region may not always be the same.
- Item needs to respond to clicks and mouseOvers, mouseDowns and
mouseUps.
...and correctly to mouseDown+rollOutWhileStillDown+mouseUpOutside
and
mouseDownElsewhere+rollIntoWhileStillDown+mouseUpInside
- Item needs to be self aware of itself and all its properties.
- Item needs to respond to questions about itself. Am I enabled?
Have I been clicked? What are my sprites?
- Item needs to allow for elegant extensibility if extra code is
required for more functionality.
- Item needs to be messageable. You have to be able to tell it to do
stuff.
- Item needs to respond properly if it is drawn on a new screen and
the mouse is already over it.
- Item needs to be enabled or disabled through remote code.
- Item should be able to be referred to by name even if it is
dynamically allocated.
- Item should be able to be so modular that more than one type of
task can be performed on a click.
- Performance of the code for all of the above should be prompt.
The user should NOT wait for any of this to happen.
... Item should support 32-bit everything (8bit alpha in other words,
although a 1-bit mask still makes the most sense)
I'm still amazed after all these years, how hard it is to make standard UI
controls (dropdown lists especially) in Director. Flash Components don't
seem to really make it that much easier. Does your idea of a button include
non-button UI controls? ie Dropdown, Radio, Checkbox, etc.
---
Macromedia Director Mailing List (Direct-L)
List Administrator: Eve M. Owens (emowens-spamblock-theserver.uark.edu)
To SUBSCRIBE or to UNSUBSCRIBE go to
and click on
"Join or leave the list (or change settings)"
For list archives
Learning Zav’s Libraries
