This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.
Summary: | Support an "event" for Forms | ||
---|---|---|---|
Product: | javame | Reporter: | bht <bht> |
Component: | Visual Designer | Assignee: | Karol Harezlak <kharezlak> |
Status: | NEW --- | ||
Severity: | blocker | ||
Priority: | P2 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | Windows ME/2000 | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
bht
2008-10-18 11:07:11 UTC
I did not initially see the full importance of this. Lazy initialized or not, forms created by the Visual designer require more functionality to reduce the amount of code and duplication. If, for example, a form is accessed via multiple paths, one is forced anyway to write/generate a method that accesses the form and that populates the field, so that no code duplication occurs. So there is a requirement for an accessor method for the form object even in the eager initialized mode, because how otherwise can the developer centralize the code that populates form text items or text fields with fresh data every time the form is displayed? So there might be a check box "accessor method" in the form object's property sheet, that creates a new combination for eager initialized forms. In addition, one might extend my initial suggestion to form fields so their population with data is closer to the code where it belongs. |