Home » Eclipse Projects » DTP » SWT Database widgets
|
| Re: SWT Database widgets [message #2017 is a reply to message #2002] |
Fri, 14 October 2005 13:59   |
Eclipse User |
|
|
|
Originally posted by: jograham.sybase.com
Bahadir Yagan wrote:
> Hi,
> I wonder if DTP project includes data aware widgets for SWT.
> (ie: A Table that is associated with a JDBC resultset or a combo
> displaying all values of a data column)
> Regards,
> Bahadir
Hi Bahadir,
At the moment DTP does not, but I think that people working on the Visual
Editor (VE) project here at Eclipse have been looking at this area. I will
make them aware of this post, and perhaps they can then provide more
information.
Regards,
John Graham
Eclipse Data Tools Platform Project PMC
|
|
| | | | | | | |
| Re: SWT Database widgets [message #3422 is a reply to message #3356] |
Mon, 24 October 2005 19:54 |
 Haris Peco
Messages: 1072
Registered: July 2009 |
Senior Member |
|
|
David J. Orme wrote:
> Haris Peco wrote:
>> i would like test, but nested properties binding is very important for me
>> i don't accept jgoodies binding because haven't nested properties.
>> spring rcp have perfect binding - there is plan for swing independent
>> binding framework
>> i explore jface binding more
>
> Thanks for the feedback. Here are the issues I have uncovered with
> nested property binding. Imagine a table control that is editing a
> Customer object with an embeded Address object. Then the following must
> be true:
>
> 1) Validation has to cascade to the nested objects. This is tricky to
> get right.
>
no, i don't agree.i want validation for bind properties only
for example, if i bind properties customer.address.street then i want
validation only for street in address object
in spring rcp we declare validation for object and properties and it isn't
important where obejcts is used
it isn't perfect because i can do validation but i can't suppress property
change.for example, if field is integer and i type 'a' then spring do
validation and return error, but show 'a' in visual field - i have
workaround for this and my suggestion isn't accepted from spring rcp
> 2) Creating new objects may be tricky, depending on the back-end. Do
> you need to register the new Address object with the persistence layer,
> for example? If the Address object is reachable from multiple places in
> your object graph, how do you make sure that all the object references
> are correctly initialized.
new spring rcp handle null object properties, but i don't use it
i have base bean for form, always and when i create bean object i create
empty object for object's properties automatic with reflection (with
BeanWrapper class from spring framework) - i do it only for bind properties
for example, if i bind customer.address.street (base form bean is customer)
i create empty bean address (empty is one created with no-constructor
argument) - if i don't bind address anywhere then i don't create address
simple, i expect from binding next : when change property visual class i
want that binding framework change bean properties automatic - inverse
change (change bean properties) change visual class only with special call
(value model) - we can't bidirectional changes without listener on setter
and it isn't important (i don't want listeners in POJO - this can be
resolved with AOP, but it is unnecessary) - i change bean properties with
value model
after every changes bean properties framework do validation (i can cancel
validation) - i cancel validation when user search database - user can type
'1%' in integer field for search all rows start with '1' and i don't want
validation for this
> 3) The reverse of (2): When you're deleting a Customer object (okay, you
> probably wouldn't ever delete a customer object, but suppose that this
> is the kind of object you would delete), whose responsibility is it to
> make sure that all references to the Customer object and its Address
> object are correctly released?
>
> How does Spring binding handle this? How would you like it to be done?
>
yes, i want delete (this is database application) and i don't delete
address.
this is many-to-one relation and deleting base object don't delete nested
objects.spring rcp do nothing and it isn't important for me
all crud operation (insert,delete,update,select) are in model and it is
independent from binding
spring rcp have helper method (in form model) setFormObject and i use it for
setting new object after crud operations
spring rcp do next for me :
when i bind visual class A to bean property propA (can be nested) then
every change visual class contents (user type text or choose combo etc)
change bean properties
setting bean properties work with special interface only, like
ValueModel model = formModel.getValueModel("propA");
model.setValue(value);
this construction change contents visual class, but simple
customer.setPropA(value);
change only bean property
formModel.setFormObject(customer)
change all visual classes bind with bean 'customer'
framework do validation automatic, but I can call
formModel.setValidation(false)
or
formModel.validate()
settings validation : i create rules declarative with bean objects and
properties (i add automatic validation for required fields from database or
foreign and primary keys etc, too , but this is part of my framework)
Thanks
|
|
|
| Re: SWT Database widgets [message #3455 is a reply to message #3422] |
Mon, 24 October 2005 18:31 |
Dave Orme
Messages: 424
Registered: July 2009 |
Senior Member |
|
|
Thanks for your feedback.
Best,
Dave Orme
Haris Peco wrote:
> David J. Orme wrote:
>
>
>>Haris Peco wrote:
>>
>>>i would like test, but nested properties binding is very important for me
>>>i don't accept jgoodies binding because haven't nested properties.
>>>spring rcp have perfect binding - there is plan for swing independent
>>>binding framework
>>>i explore jface binding more
>>
>>Thanks for the feedback. Here are the issues I have uncovered with
>>nested property binding. Imagine a table control that is editing a
>>Customer object with an embeded Address object. Then the following must
>>be true:
>>
>>1) Validation has to cascade to the nested objects. This is tricky to
>>get right.
>>
>
>
> no, i don't agree.i want validation for bind properties only
> for example, if i bind properties customer.address.street then i want
> validation only for street in address object
> in spring rcp we declare validation for object and properties and it isn't
> important where obejcts is used
> it isn't perfect because i can do validation but i can't suppress property
> change.for example, if field is integer and i type 'a' then spring do
> validation and return error, but show 'a' in visual field - i have
> workaround for this and my suggestion isn't accepted from spring rcp
>
>
>>2) Creating new objects may be tricky, depending on the back-end. Do
>>you need to register the new Address object with the persistence layer,
>>for example? If the Address object is reachable from multiple places in
>>your object graph, how do you make sure that all the object references
>>are correctly initialized.
>
> new spring rcp handle null object properties, but i don't use it
> i have base bean for form, always and when i create bean object i create
> empty object for object's properties automatic with reflection (with
> BeanWrapper class from spring framework) - i do it only for bind properties
> for example, if i bind customer.address.street (base form bean is customer)
> i create empty bean address (empty is one created with no-constructor
> argument) - if i don't bind address anywhere then i don't create address
>
> simple, i expect from binding next : when change property visual class i
> want that binding framework change bean properties automatic - inverse
> change (change bean properties) change visual class only with special call
> (value model) - we can't bidirectional changes without listener on setter
> and it isn't important (i don't want listeners in POJO - this can be
> resolved with AOP, but it is unnecessary) - i change bean properties with
> value model
> after every changes bean properties framework do validation (i can cancel
> validation) - i cancel validation when user search database - user can type
> '1%' in integer field for search all rows start with '1' and i don't want
> validation for this
>
>>3) The reverse of (2): When you're deleting a Customer object (okay, you
>>probably wouldn't ever delete a customer object, but suppose that this
>>is the kind of object you would delete), whose responsibility is it to
>>make sure that all references to the Customer object and its Address
>>object are correctly released?
>>
>>How does Spring binding handle this? How would you like it to be done?
>>
>
> yes, i want delete (this is database application) and i don't delete
> address.
> this is many-to-one relation and deleting base object don't delete nested
> objects.spring rcp do nothing and it isn't important for me
> all crud operation (insert,delete,update,select) are in model and it is
> independent from binding
> spring rcp have helper method (in form model) setFormObject and i use it for
> setting new object after crud operations
>
> spring rcp do next for me :
>
> when i bind visual class A to bean property propA (can be nested) then
> every change visual class contents (user type text or choose combo etc)
> change bean properties
> setting bean properties work with special interface only, like
>
> ValueModel model = formModel.getValueModel("propA");
> model.setValue(value);
>
> this construction change contents visual class, but simple
> customer.setPropA(value);
> change only bean property
>
> formModel.setFormObject(customer)
> change all visual classes bind with bean 'customer'
>
> framework do validation automatic, but I can call
> formModel.setValidation(false)
> or
> formModel.validate()
>
> settings validation : i create rules declarative with bean objects and
> properties (i add automatic validation for required fields from database or
> foreign and primary keys etc, too , but this is part of my framework)
>
> Thanks
--
Visual Editor Project lead
http://www.db4o.com -- The Open-source Java Object Database
http://xswt.sf.net -- XML-based SWT page description language
|
|
| | | | | | | | |
| Re: SWT Database widgets [message #567383 is a reply to message #3356] |
Mon, 24 October 2005 19:54 |
Haris Peco
Messages: 1072
Registered: July 2009 |
Senior Member |
|
|
David J. Orme wrote:
> Haris Peco wrote:
>> i would like test, but nested properties binding is very important for me
>> i don't accept jgoodies binding because haven't nested properties.
>> spring rcp have perfect binding - there is plan for swing independent
>> binding framework
>> i explore jface binding more
>
> Thanks for the feedback. Here are the issues I have uncovered with
> nested property binding. Imagine a table control that is editing a
> Customer object with an embeded Address object. Then the following must
> be true:
>
> 1) Validation has to cascade to the nested objects. This is tricky to
> get right.
>
no, i don't agree.i want validation for bind properties only
for example, if i bind properties customer.address.street then i want
validation only for street in address object
in spring rcp we declare validation for object and properties and it isn't
important where obejcts is used
it isn't perfect because i can do validation but i can't suppress property
change.for example, if field is integer and i type 'a' then spring do
validation and return error, but show 'a' in visual field - i have
workaround for this and my suggestion isn't accepted from spring rcp
> 2) Creating new objects may be tricky, depending on the back-end. Do
> you need to register the new Address object with the persistence layer,
> for example? If the Address object is reachable from multiple places in
> your object graph, how do you make sure that all the object references
> are correctly initialized.
new spring rcp handle null object properties, but i don't use it
i have base bean for form, always and when i create bean object i create
empty object for object's properties automatic with reflection (with
BeanWrapper class from spring framework) - i do it only for bind properties
for example, if i bind customer.address.street (base form bean is customer)
i create empty bean address (empty is one created with no-constructor
argument) - if i don't bind address anywhere then i don't create address
simple, i expect from binding next : when change property visual class i
want that binding framework change bean properties automatic - inverse
change (change bean properties) change visual class only with special call
(value model) - we can't bidirectional changes without listener on setter
and it isn't important (i don't want listeners in POJO - this can be
resolved with AOP, but it is unnecessary) - i change bean properties with
value model
after every changes bean properties framework do validation (i can cancel
validation) - i cancel validation when user search database - user can type
'1%' in integer field for search all rows start with '1' and i don't want
validation for this
> 3) The reverse of (2): When you're deleting a Customer object (okay, you
> probably wouldn't ever delete a customer object, but suppose that this
> is the kind of object you would delete), whose responsibility is it to
> make sure that all references to the Customer object and its Address
> object are correctly released?
>
> How does Spring binding handle this? How would you like it to be done?
>
yes, i want delete (this is database application) and i don't delete
address.
this is many-to-one relation and deleting base object don't delete nested
objects.spring rcp do nothing and it isn't important for me
all crud operation (insert,delete,update,select) are in model and it is
independent from binding
spring rcp have helper method (in form model) setFormObject and i use it for
setting new object after crud operations
spring rcp do next for me :
when i bind visual class A to bean property propA (can be nested) then
every change visual class contents (user type text or choose combo etc)
change bean properties
setting bean properties work with special interface only, like
ValueModel model = formModel.getValueModel("propA");
model.setValue(value);
this construction change contents visual class, but simple
customer.setPropA(value);
change only bean property
formModel.setFormObject(customer)
change all visual classes bind with bean 'customer'
framework do validation automatic, but I can call
formModel.setValidation(false)
or
formModel.validate()
settings validation : i create rules declarative with bean objects and
properties (i add automatic validation for required fields from database or
foreign and primary keys etc, too , but this is part of my framework)
Thanks
|
|
|
| Re: SWT Database widgets [message #567410 is a reply to message #3422] |
Mon, 24 October 2005 18:31 |
Dave Orme
Messages: 424
Registered: July 2009 |
Senior Member |
|
|
Thanks for your feedback.
Best,
Dave Orme
Haris Peco wrote:
> David J. Orme wrote:
>
>
>>Haris Peco wrote:
>>
>>>i would like test, but nested properties binding is very important for me
>>>i don't accept jgoodies binding because haven't nested properties.
>>>spring rcp have perfect binding - there is plan for swing independent
>>>binding framework
>>>i explore jface binding more
>>
>>Thanks for the feedback. Here are the issues I have uncovered with
>>nested property binding. Imagine a table control that is editing a
>>Customer object with an embeded Address object. Then the following must
>>be true:
>>
>>1) Validation has to cascade to the nested objects. This is tricky to
>>get right.
>>
>
>
> no, i don't agree.i want validation for bind properties only
> for example, if i bind properties customer.address.street then i want
> validation only for street in address object
> in spring rcp we declare validation for object and properties and it isn't
> important where obejcts is used
> it isn't perfect because i can do validation but i can't suppress property
> change.for example, if field is integer and i type 'a' then spring do
> validation and return error, but show 'a' in visual field - i have
> workaround for this and my suggestion isn't accepted from spring rcp
>
>
>>2) Creating new objects may be tricky, depending on the back-end. Do
>>you need to register the new Address object with the persistence layer,
>>for example? If the Address object is reachable from multiple places in
>>your object graph, how do you make sure that all the object references
>>are correctly initialized.
>
> new spring rcp handle null object properties, but i don't use it
> i have base bean for form, always and when i create bean object i create
> empty object for object's properties automatic with reflection (with
> BeanWrapper class from spring framework) - i do it only for bind properties
> for example, if i bind customer.address.street (base form bean is customer)
> i create empty bean address (empty is one created with no-constructor
> argument) - if i don't bind address anywhere then i don't create address
>
> simple, i expect from binding next : when change property visual class i
> want that binding framework change bean properties automatic - inverse
> change (change bean properties) change visual class only with special call
> (value model) - we can't bidirectional changes without listener on setter
> and it isn't important (i don't want listeners in POJO - this can be
> resolved with AOP, but it is unnecessary) - i change bean properties with
> value model
> after every changes bean properties framework do validation (i can cancel
> validation) - i cancel validation when user search database - user can type
> '1%' in integer field for search all rows start with '1' and i don't want
> validation for this
>
>>3) The reverse of (2): When you're deleting a Customer object (okay, you
>>probably wouldn't ever delete a customer object, but suppose that this
>>is the kind of object you would delete), whose responsibility is it to
>>make sure that all references to the Customer object and its Address
>>object are correctly released?
>>
>>How does Spring binding handle this? How would you like it to be done?
>>
>
> yes, i want delete (this is database application) and i don't delete
> address.
> this is many-to-one relation and deleting base object don't delete nested
> objects.spring rcp do nothing and it isn't important for me
> all crud operation (insert,delete,update,select) are in model and it is
> independent from binding
> spring rcp have helper method (in form model) setFormObject and i use it for
> setting new object after crud operations
>
> spring rcp do next for me :
>
> when i bind visual class A to bean property propA (can be nested) then
> every change visual class contents (user type text or choose combo etc)
> change bean properties
> setting bean properties work with special interface only, like
>
> ValueModel model = formModel.getValueModel("propA");
> model.setValue(value);
>
> this construction change contents visual class, but simple
> customer.setPropA(value);
> change only bean property
>
> formModel.setFormObject(customer)
> change all visual classes bind with bean 'customer'
>
> framework do validation automatic, but I can call
> formModel.setValidation(false)
> or
> formModel.validate()
>
> settings validation : i create rules declarative with bean objects and
> properties (i add automatic validation for required fields from database or
> foreign and primary keys etc, too , but this is part of my framework)
>
> Thanks
--
Visual Editor Project lead
http://www.db4o.com -- The Open-source Java Object Database
http://xswt.sf.net -- XML-based SWT page description language
|
|
|
Goto Forum:
Current Time: Fri Dec 27 02:24:13 GMT 2024
Powered by FUDForum. Page generated in 0.05244 seconds |
] 
Search
Help
Register
Login
Home
