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 70927 - [50cat] Have a Visual RecordStore Designer
Summary: [50cat] Have a Visual RecordStore Designer
Status: NEW
Alias: None
Product: javame
Classification: Unclassified
Component: Visual Designer (show other bugs)
Version: 5.x
Hardware: PC Windows XP
: P3 blocker with 1 vote (vote)
Assignee: Karol Harezlak
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-01-03 07:10 UTC by ieising
Modified: 2008-11-13 09:28 UTC (History)
0 users

See Also:
Issue Type: ENHANCEMENT
Exception Reporter:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ieising 2006-01-03 07:10:29 UTC
[ JDK VERSION : 1.6 ]

Hi,

I would really like to see a visual designer which allows me to design recordstores as if it where a proper table.
The designer would also generate CRUD (Create, Read, Update, Delete) operations for the recordstore, respecting the type of the fields in a record. It would also allow me to pre-populate the recordstore, and generate the code for it, such that I can have some default values in the recordstore. Possibly only for debug purposes, which I would expect to be an option and accordingly pre-processor statements are added to this code.

Iwan
Comment 1 ieising 2006-01-27 11:00:08 UTC
Hi Lukas, (copied from my comments on Lukas' blog)

I have some ideas, of course since I posted the enhancement.

Let's say that the release notes should say something like this (but not limited
to this obviously).

- It is possible to select a class from your project and right click on the
class' name. You then get the option 'Create Record Store from Class' which
takes you to a dialog that lists all primitive fields of the class. You can
check which fields you want to store in the RS. Than click 'OK' and NB will
generate the code to CRUD the RS and records in the RS. You can select if you
want this code to be generated as methods of the selected class, or a new class
that can handle the appointed class with respect to the RS.

- There is an option 'Generate GUI' available when you right click on the
declaration of a record store (that you've created with the previous feature).
When you select it, you're asked whether you want a single CRUD-screen that
allows you to CRUD a RS, or you can opt to generate several Forms for the
various CRUD operations. Of course you can also select this as an integral part
of the previous feature.

- There is a visual editor to create an RS. It draws an empty box on the screen
when you start it, and from the component palette you can drag fields on the
box. NB will then create a class for the RS with the CRUD methods (or if you
like, the CRUD methods in a separate class). You can then right click on the
visual RS and select 'Generate GUI'.
It is possible to create new RS components by using aggregation. This allows for
a standard combination of fields you might want to use (e.g. Firstname/Surname
combination, Booktitle/ISBN combination, Name/Address combinations etc).
You can also have a RS definition as a component, so you can use the same RS in
different MIDlets.
These components can be packaged and imported in other projects so you can
create component libraries and make a living out of them. In order to get this
to really flourish, you can assign an icon to a component so you can spread your
logo all over the globe. :)

- It is possible to have NB generate code to synchronize the contents of an RS
with a remote Database through a webservice (SOAP) interface or through a plain
old servlet interface. You can limit the amount of records going back and forth.
There is an interface that allows for some custom restrictions, like only those
x number of records that have value y in field z.

- It is possible to have NB generate code to put some default (dummy) data in
the RS. This is handy when put within a pre-processor block, so you can test
your code with minimal effort.

Iwan
Comment 2 Lukas Hasik 2006-06-23 14:42:55 UTC
moving to mobility component