To continue with my previous observations:
BUTTON EVENTS:
Additional event:
Double-Tap (changes previous tap and hold event to other equivalent, makes this one equivalent to double-click).
NOTE: All visible objects with Horizontal (x) and Vertical (y) properties, must have as part of those properties at least three selectable settings, “Keep Proportions,” “Fill Parent” and “Automatic.” The first of these would maintain the object’s proportions whenever the device’s orientation changes. Thus, an object that was created with a vertical (portrait) orientation that largely filled the screen, would be reduced in size for proper display in a horizontal (landscape) orientation.
Next object:
INPUT
All properties should be able to be set or changed dynamically with constants and variables in code.
Change property label/name from “Input Secret” to “Input Disguised” or something that more clearly describes what is intended. Using “secret” does not indicate whether the input is entirely hidden or visually replaced with some character such *.
Replace “Theme” with “Background Color and use a color picker or input boxes for Red, Blue, Green or both.
Needed additional properties:
Text Horizontal Align (left, center, right, justify)
Text Vertical Align (top, middle, bottom, fill). “Fill” refers to making the height (y) dimension of the text the same as the height (y) dimension of the input box itself.
Font (name chosen from pick list)
Font Size (pick list of point sizes and user entered)
Font Style (bold, italic, bold-italic)
Font Color
Position (x,y)
Width (w, auto, fill-parent, keep proportions)
Height (h, auto, fill-parent, keep proportions)
Visible (yes, no – checkbox)
Enabled (yes, no – checkbox)
TEXTAREA
See INPUT above plus those below:
Modifiable (yes, no checkbox or radio button). The need for this property is because sometimes text to be displayed such as a non-editable description is multilane. At other times it is used as a text entry/editing area.
Background Color (pick list and user supplied R, B, G values).
Transparency (value of 0 to 255 with 0 fully transparent and 255 solid).
Background Image
LABEL
See INPUT and TEXTAREA above.
INPUT, TEXTAREA and LABEL Events:
Include these in the list of events –
Touch and Hold
Double-Click
Swipe
NOTE: A “standard” or “pre-defined” use for the Touch and Hold event could be to call up a Tooltip. If so, then ALL visible objects should have a ToolTip property with a textbox for setting the tooltip.
LINK
See INPUT and TEXTAREA above plus those below:
Un-Tapped Color (replaces the current Color property)
Tapped Color (adds a Color property for when then the Link has been previously activated).
Events:
Tap
Tap and Hold
Double-Tap
Swipe
RADIO BUTTON(S)
Properties for each radio button option:
See INPUT and TEXTAREA above.
Events:
Tap
Tap and Hold
Double-Tap
Swipe
NOTE: All events listed in my previous email as well as those listed here are to be understood as additions rather than the only ones available. For example, pinching is another event that should be another event that could be part of particular objects.