And it has to have bluetooth & java….
- Visible connections They clutter up the field
- Invisible text boxes
e.g. when you set the border to be invisible, they become invisible on the designer
- Zero width widgets
The designer should give everything a minimum width even if the widget will be zero width in runtime.
- Default trash text
Default names are ok. Default properties, like value = “text1″ is a pain
- Absolute positioning
Who has time to bump around every single widget!
- Inconsistent property names
This control returns values with .value, that one with .text
- Non extendable controls
Give the using programmer’s a chance to fix the base controls defects. And give us at least 3 different ways to extend a control. (By adding new properties, overriding exiting behavior or properties, or making it easy to pass control through a subroutine each time before use for repair)
- GUI only edits
Maybe someone already has.
If you want to call some one who has an answering machine, 2 voice mail accounts, a secretary, three phone lines, two email accounts and SMS messaging, there should be a single entry point to get through to the person if they are at the end of any one of these connection points. The caller would call one number, then the application would begin calling all three phones until it got a live person and would patch the live person through to the caller. This probably would be some sort of smart JavaPhone application.
Likewise, the person being called should have one aggregator application that would fetch all SMS messages, emails, voicemails and call up the secretary on a regular basis to ask them to read off the day’s messages.