A Need for Better Class Documentation

2 posts, 0 answers
  1. Aaron Lewis
    Aaron Lewis avatar
    22 posts
    Member since:
    Jan 2003

    Posted 26 Feb 2010 Link to this post

    Hello there,

    At GuildPortal we host guild sites for people who play massively multi-player online games (like World of Warcraft).  All of the code is custom. The back-end administration piece (for guild administrators) uses the Telerik ASP.Net AJAX components for the user interface.  The only thing we are currently using that the vast majority of our users see (the guild members, not admins) is the WYSIWYG editor.

    We'd really like to use more of the suite in the guild pages, but in order to do that, we'd need some kind of uniform approach to the components.  Just looking at the multitude of styles across all the various controls, including inline styles, doesn't give me much confidence that this will work out, but...

    I don't suppose you folks have anything in the pipeline for diagramming all of the controls and the styles that apply to them?  I've seen some of these types of things in your documentation for various controls, but they're not there for all of them.  Our users require a high degree of customizability, so the only way we can provide that and still use your suite to its fullest is if we have some kind of sane approach to overriding the appearance of your controls, dynamically, at run-time.
  2. Dimo
    Dimo avatar
    8406 posts

    Posted 02 Mar 2010 Link to this post

    Hi Aaron,

    What do you mean by "uniform approach"? It sounds like you would like to modify the appearance of all controls in a similar manner, however, I am afraid this is not possible, as each control has different HTML rendering and CSS classes.

    The styles, which we set as inline styles are usually required and should not be changed.

    Most controls have a help article, which lists all CSS classes and describes the purpose of each class, for example:


    In addition, you are able to inspect the non-embedded versions of our skins by browsing the "Skins" folder inside the RadControls installation location (or ZIP).

    Each control provides different means to customize its appearance declaratively or programmatically, for example:


    If you want to customize the appearance of our controls while still using the embedded skins, I recommend reading this:


    Let us know if you need specific information regarding a certain control.

    Sincerely yours,
    the Telerik team

    Do you want to have your say when we set our development plans? Do you want to know when a feature you care about is added or when a bug fixed? Explore the Telerik Public Issue Tracking system and vote to affect the priority of the items.
Back to Top