Comments on: It’s all about the form… http://canoo.com/blog/2008/02/26/ultralightclient-08-new-form-component/ Web 2.0 Technology Blog on Java, AJAX and Flex Thu, 20 Nov 2008 15:40:18 +0000 http://wordpress.org/?v=2.5.1 By: Daniel http://canoo.com/blog/2008/02/26/ultralightclient-08-new-form-component/#comment-9320 Daniel Wed, 27 Feb 2008 16:50:25 +0000 http://canoo.com/blog/2008/02/26/ultralightclient-08-new-form-component/#comment-9320 Hi Tamas, The form component internally uses data types to filter and validate input on the client side. The validateValue() method is meant for server-side validation only. Regards Dany Hi Tamas,

The form component internally uses data types to filter and validate input on the client side. The validateValue() method is meant for server-side validation only.

Regards Dany

]]> By: Daniel http://canoo.com/blog/2008/02/26/ultralightclient-08-new-form-component/#comment-9319 Daniel Wed, 27 Feb 2008 16:47:25 +0000 http://canoo.com/blog/2008/02/26/ultralightclient-08-new-form-component/#comment-9319 Hi Stuart, As said to Thomas we are thinking of giving customization options to the application developer. One aspect is the concrete classes to create for the various addXXX methods. This is work in progress so I can’t say much how this will look like. Regards Dany Hi Stuart,

As said to Thomas we are thinking of giving customization options to the application developer. One aspect is the concrete classes to create for the various addXXX methods. This is work in progress so I can’t say much how this will look like.

Regards Dany

]]> By: Daniel http://canoo.com/blog/2008/02/26/ultralightclient-08-new-form-component/#comment-9318 Daniel Wed, 27 Feb 2008 16:45:22 +0000 http://canoo.com/blog/2008/02/26/ultralightclient-08-new-form-component/#comment-9318 Hi Thomas, First thanx for your feedback! Question 2: For grids we will provide improved support as well. However this is not part of the form component. There will be another high-level component that takes care of grids. More on this in a next blog post! Question 3: The addTextField() method returns the added text field, i.e. it is possible to change the tab order with already existing UltraLightClient API. Question 4: Currently the exclamation mark is hard coded. But we are thinking of giving customization options to the application developer, not only for the error feedback but for other aspects as well (e.g. layout, component types). This is still work in progress so I can't say much how this will look like. Regards Dany Hi Thomas,

First thanx for your feedback!

Question 2: For grids we will provide improved support as well. However this is not part of the form component. There will be another high-level component that takes care of grids. More on this in a next blog post!

Question 3: The addTextField() method returns the added text field, i.e. it is possible to change the tab order with already existing UltraLightClient API.

Question 4: Currently the exclamation mark is hard coded. But we are thinking of giving customization options to the application developer, not only for the error feedback but for other aspects as well (e.g. layout, component types). This is still work in progress so I can’t say much how this will look like.

Regards Dany

]]> By: Tamas KIS http://canoo.com/blog/2008/02/26/ultralightclient-08-new-form-component/#comment-9317 Tamas KIS Wed, 27 Feb 2008 16:34:45 +0000 http://canoo.com/blog/2008/02/26/ultralightclient-08-new-form-component/#comment-9317 Hello, first of all i think the mouseover error message is great. In addition I think it would be nice to show the validation message as pop up bubbles as well... Q1: ULC already has got a concept for validation (see IDataType interface; e.g. ULCDateDataType), will it be extended, or neglected? Best regards, Tamas Hello,

first of all i think the mouseover error message is great. In addition I think it would be nice to show the validation message as pop up bubbles as well…
Q1: ULC already has got a concept for validation (see IDataType interface; e.g. ULCDateDataType), will it be extended, or neglected?

Best regards,
Tamas

]]> By: Stuart Booth http://canoo.com/blog/2008/02/26/ultralightclient-08-new-form-component/#comment-9307 Stuart Booth Wed, 27 Feb 2008 12:34:43 +0000 http://canoo.com/blog/2008/02/26/ultralightclient-08-new-form-component/#comment-9307 Regarding the addTextField method: will it be possible to use subclasses, and can extra params be passed to the constructor? Regarding the addTextField method: will it be possible to use subclasses, and can extra params be passed to the constructor?

]]> By: sandra wendland http://canoo.com/blog/2008/02/26/ultralightclient-08-new-form-component/#comment-9297 sandra wendland Wed, 27 Feb 2008 09:46:08 +0000 http://canoo.com/blog/2008/02/26/ultralightclient-08-new-form-component/#comment-9297 Hi Thomas, thank you for your comments. I'll answer your first question cos it's kind of my idea :-) We'll be using the UltraLightClient 08 image to mark blog posts and new web pages related to the next major release of the Canoo RIA library. Regarding the final version naming, we'll decide on this closer to the date (as was the case in the past). I'll communicate how the new naming corresponds to the current versioning closer to the release date. I guess Daniel will answer your remaining questions. Sandra Hi Thomas,

thank you for your comments. I’ll answer your first question cos it’s kind of my idea :-)

We’ll be using the UltraLightClient 08 image to mark blog posts and new web pages related to the next major release of the Canoo RIA library. Regarding the final version naming, we’ll decide on this closer to the date (as was the case in the past).

I’ll communicate how the new naming corresponds to the current versioning closer to the release date.

I guess Daniel will answer your remaining questions.

Sandra

]]> By: Thomas Ernst http://canoo.com/blog/2008/02/26/ultralightclient-08-new-form-component/#comment-9260 Thomas Ernst Tue, 26 Feb 2008 23:29:34 +0000 http://canoo.com/blog/2008/02/26/ultralightclient-08-new-form-component/#comment-9260 Hi Daniel, nice post! I agree that forms make up a very important part of real-life business applications. I am glad to see that there will be support in the next ULC release. Which brings me to my first question: is UltraLightClient ‘08 a code name / working title for the next ULC release or will the whole release naming change (which I do not expect)? If the naming doesn\'t change, which release is UltraLightClient ‘08 related to? 6.2.2, 6.3, 7.0? Just curious... Question 2: I can see that the new features help in designing label/field combinations of the type ... (as illustrated in the post). However, this is not the design I see most often but merely something like several rows of ..., arranged in a grid. How does the new forms support simplify the design of such layouts? Question 3: The real text fields seem to be hidden, so how can I control the tabbing order of these fields? Question 4: Will it be possible to have other error indicators apart from the exclamation mark, for instance, icons? Regards, Thomas Hi Daniel,
nice post! I agree that forms make up a very important part of real-life business applications. I am glad to see that there will be support in the next ULC release. Which brings me to my first question: is UltraLightClient ‘08 a code name / working title for the next ULC release or will the whole release naming change (which I do not expect)? If the naming doesn\’t change, which release is UltraLightClient ‘08 related to? 6.2.2, 6.3, 7.0? Just curious…
Question 2: I can see that the new features help in designing label/field combinations of the type … (as illustrated in the post). However, this is not the design I see most often but merely something like several rows of …, arranged in a grid. How does the new forms support simplify the design of such layouts?
Question 3: The real text fields seem to be hidden, so how can I control the tabbing order of these fields?
Question 4: Will it be possible to have other error indicators apart from the exclamation mark, for instance, icons?
Regards, Thomas

]]>