This post is not meant to be a complaint, it is meant to suggest what I feel is the perspective of the typical end-user - the one who actually needs and uses the various demos. I suggest that each "feature" be self-contained and easy-to-follow.
DEVEXPRESS LAYOUT CONTROL CODE
Most users (I suspect) want to see the all the code in one spot, where they can follow the logic, where they don't chase down inheritance, and where they don't get confused where pieces of the puzzle aren't even located within the demo. This really screams or demands that code is NOT inherited. Well, I suspect most users look at the choices within a Demo or the "Features" such as Validating, Localization, Image Layout, etc and they just want to understand that specific feature. To understand: if someone adds a DevExpress LayoutControl to a base user control or form and then tries to inherit or derive a form from that base, the LayoutControl would be unusable in the designer because Visual Studio does not support adding, removing, or changing collections via the designer in a derived form when the source collection is in a base class.
DEVEXPRESS LAYOUT CONTROL HOW TO
For example, I was trying to understand how to properly deal with Visual Inheritance and understand Visual Studio's problem with collection members in inherited or derived forms. Third (Isolation): These demos, obviously, offer many benefits. Why is the "TutorialControl" and the "LayoutAppearanceMenu" contained in DemoControls? I don't see the logical relationship here. Grouping classes into files without clear understanding of any reasoning for grouping them makes the code more difficult to understand. A possible simple approach I might recommend would be a file for every class. There really needs to be some organization and logic followed to make it easy to locate objects. What I am getting at is that there is a very difficult to follow pattern for why certain classes are located within certain files. However, for some reason the LayoutAppearanceMenu is also located in the DemoControls.cs file. Second (organization): I started "browsing" the code and looked at the "BaseControl" which inherits from some TutorialControl which is located in a file named DemoControls.cs yet the BaseControl is not part of DemoControls, it is special and gets its own file. Why is this "frmMain" not part of the demo solution? I certainly can understand that some elements are common to many demo solutions, but they should simply be referenced as a separate "common" project, should they not? The common projects should be included DIRECTLY in each demo solution. I found numerous objects that inherit from classes that are not contained directly in the demo.ĭevExpress: Please, do NOT create a demo that utilizes custom controls or features that are hidden within your source code library! I am fairly certain that the base class "frmMain" is not a standard control for your library and I am also certain that this confuses users and does not help them. Isn't a demo supposed to include the code? Inheriting from classes that are not included is not the best choice (IMO). the base or inherited class I chased down (the very first step I took to understand the demo code) is "FROM METADATA" and this is just "wrong" (IMO) - for any demo. so I click on "Go to Definition" and this is what I get:įirst (metatdata): Notice. Can you see it in the rectangle? Its a little frustrating to chase down code in a demo, but hey. I highlighted where the form inherits from a base form "". there are a LOT of custom User Controls and I start looking/ learning (as I suspect most users may) by looking at the main form (frmMain) and attempt to "go backwards" through the code. Its a nice demo - I want to learn from it, and so I open the source code for the demo that is included with my subscription where I see something in VS2005 similar to this: If I click a feature, such as Validating, I get a screen shot similar to this: Here is a screen shot of the Developer Express Layout Control Main Demo: Non-tabbed layout groups are useful to visually separate and group a form's sections without using tabs.īefore the v18.1 release, you would need several Form Layout controls to create non-tabbed layout groups.Technorati Tags: C#, Programming, DevExpress, Developer Express, Layout Control, Feedback For example, here the layout changes column count based on the width: This allows you to define different values depending on the current screen resolution. To help you make your layouts more adaptive, some of the layout items support BootstrapLayoutItem.ColSpanXl / ColSpanLg / ColSpanMd / ColSpanSm / ColSpanXs properties. The DevExpress Bootstrap controls help you to leverage these features of the Bootstrap Grid system. The Bootstrap Grid system provides classes for different screen sizes.
0 kommentar(er)
