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.

Bug 104663 - Use WeakReference in generated code
Summary: Use WeakReference in generated code
Status: NEW
Alias: None
Product: javame
Classification: Unclassified
Component: Visual Designer (show other bugs)
Version: 6.x
Hardware: All All
: P1 blocker (vote)
Assignee: Karol Harezlak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-23 22:12 UTC by Martin Ryzl
Modified: 2008-05-05 09:53 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Ryzl 2007-05-23 22:12:23 UTC 
Use WeakReferences in the generated code on CLDC 1.1. Questions to discuss: how
to make sure Visual Designer and project are always in sync regarding CLDC
version, how to turn off the behavior (for instance TextField which should
preserve the value) and also are all the implementations correct?
Comment 1 David Kaspar 2007-05-23 23:18:57 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.
Comment 2 David Kaspar 2007-05-23 23:20:27 UTC 
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.
Comment 3 David Kaspar 2007-06-19 14:18:08 UTC 
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).
Comment 4 David Kaspar 2007-09-17 12:50:31 UTC 
Very likely it is not going to be implemented in 6.0.