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: | Use WeakReference in generated code | ||
---|---|---|---|
Product: | javame | Reporter: | Martin Ryzl <mryzl> |
Component: | Visual Designer | Assignee: | Karol Harezlak <kharezlak> |
Status: | NEW --- | ||
Severity: | blocker | ||
Priority: | P1 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | ENHANCEMENT | Exception Reporter: |
Description
Martin Ryzl
2007-05-23 22:12:23 UTC
Automatic synchronization of generated code style with CLDC version set to a project is hard to implement: 1) All visual files would have to be regenerated while switching CLDC version 2) How to behave with multiple configurations with different CLDC versions? This is very similar to MIDP version synchrozation between project and visual files. It also could be solved the same way - it means: the visual file (means the design root node) would have additional "CLDC version" property. The code would be generated based on its value. P.S.: or instead of "CLDC version" there may be particular general properties that are used for code-generation e.g.: "Use WeakReferences when possible" property. The last proposal: Each Class-based component will have a "Use as a WeakReference". It will be "false" by default. It will not take care about CLDC version at all. It is relatively easy to implement (changes in ClassCD and ClassCode classes only). Very likely it is not going to be implemented in 6.0. |