Intersoft Community - ClientUI - Naming convention of Silverlight/WPF controls

Naming convention of Silverlight/WPF controls

technical@intersoftpt.com — Thu, 08 Jul 2010 10:21:24 GMT

Dear John,

I apologize for not stating it more clearly. Although most controls without UX are more basic and simpler in functions, they still fully comply to MVVM principles and consistently support standards-compliance user experiences.

Yes, please submit bug reports and feedback in this forum. We'll include the bug fixes in the upcoming RTM release.

- Support

Naming convention of Silverlight/WPF controls

JohnV — Thu, 08 Jul 2010 06:40:41 GMT

Dear,

Thanks for the quick reply.
If I understand you correctly, does it mean that the controls without UX-prefix do not fully
comply to the MVVM 'principles', Routed events, Focus Management, Default focus ...
as shown in the demo and the blog -entry from Jimmy :

ClientUI Part 3 – Comprehensive MVVM Framework for Silverlight Development

I think for instance at the ListPresenter Control.

On a side note : Can this forum also used to report bugs for the ClientUI2010 RC ?

Kind regards,

JohnV

Naming convention of Silverlight/WPF controls

technical@intersoftpt.com — Wed, 07 Jul 2010 04:50:07 GMT

Hello, thank you for joining ClientUI forum.

Most controls that aren't available yet in Silverlight are named without UX. These controls are basically serve as their basic purpose, another examples are WrapPanel, GlassButton, etc.

The controls with prefix UX commonly have higher standards in their features, most of them already include built-in UX features. For instances, UXGridPanel, UXToolBar, UXListBox, and more -- support visual drag-drop and numerous interactivity features.

Let me know if you have other questions.

Regards,
Support.

Naming convention of Silverlight/WPF controls

JohnV — Wed, 07 Jul 2010 01:33:59 GMT

Some controls start with the prefix UX while others not (e.g. DockPanel).

What's the difference ?