rad.controls

8 posts, 0 answers
  1. Tim
    Tim avatar
    39 posts
    Member since:
    Sep 2002

    Posted 19 Apr 2005 Link to this post

    Hi Telerik,

    What controls in the rad.control package will be able to use asp.net v2 features like themes, skins, embedding in formview, acces objectdatasources, etc?
  2. Vassil Petev
    Admin
    Vassil Petev avatar
    1765 posts

    Posted 19 Apr 2005 Link to this post

    Hello Tim.

    We will have exact data on .NET 2.0 beta2 in a week. The new version was released two days ago and we will need to do some extensive tests before we can be certain what exactly is supported currently. Rest assured, we will support .NET 2.0 fully shortly after its official release.


    Regards,
    the telerik team
  3. Tim
    Tim avatar
    39 posts
    Member since:
    Sep 2002

    Posted 20 Apr 2005 Link to this post

    Of course you will :) But before we get to the final release will you release your own "beta2" of the rad.controls? I suppose they need to get "beta tested" as well.

    Anyway, here's the results of my initial testing:

    Rad.controls package:
    - Wont install if you only run vs2005 with the new buildt-in local webserver.

    Rad.Panel (downloaded as zip)
    - Rad.Panel Icon is not shown in toolbox.
    - Cant be themed in design mode.
    - Seems to work in runtime mode.

    Rad.Grid (downloaded as zip)
    - Does not seem to accept datasources, which quickly puts an end to that show.

    In general, it would be nice if the new v2 of these documents, had some better og more elaborate/complete "xcopy" style installation procedures to match the new and more loosely website model of v2.
  4. Tim
    Tim avatar
    39 posts
    Member since:
    Sep 2002

    Posted 20 Apr 2005 Link to this post

    Rad.Editor:
    - It runs, but the toolbars are jolted around !?! and the inputarea is non-existent?
  5. Vassil Petev
    Admin
    Vassil Petev avatar
    1765 posts

    Posted 22 Apr 2005 Link to this post

    We never made any claims that our controls work under 2.0, Tim. As we said in our previous reply, we need to test the controls on 2.0 before we can discuss the topic.

    Still, our grid has been Black-Box tested and it is fully operational. We can only guess what you mean by saying 'Does not seem to accept datasources', but the grid binds quite well with any kind of DataSource, even to such as AccessDataSource, available only in Whidbey. In other words our tests so far show that r.a.d.grid is .NET 2.0 ready.

    About your expectations of .NET 2.0 compliancy: anyone understands that if a web control should support .NET 2.0 features such as themes, data-source controls, etc, this control will not support .NET 1.x. In other words, the control will support 2.0 and 1.x only if it doesn't use the advanced 2.0 features. Thus you cannot expect a 1.1 compliant control to take advantage of 2.0 features.

    This said, rest assured that we will support .NET 2.0 as we finally have a stable GO LIVE version to build on. In a week we will have the results from our internal tests and soon afterwards we will start working on providing 2.0 compliant controls. This takes time as we have 11 ASP.NET controls (4 more in the works), and most of these are offered as standalone ASP.NET controls, as MCMS placeholders and soon we will have SharePoint webparts. Please, bare with us.


    the telerik team
  6. Tim
    Tim avatar
    39 posts
    Member since:
    Sep 2002

    Posted 22 Apr 2005 Link to this post

    "As we said in our previous reply, we need to test the controls on 2.0 before we can discuss the topic. "

    Sure. Simply could not resist trying'em out in v.2. Hope you dont mind the feedback ;)

    "In other words our tests so far show that r.a.d.grid is .NET 2.0 ready"

    I must be mistaken then. I'll give it another try.

    "Please, bare with us. "

    No need to. You guys are doing an excellent job. Really! 

  7. Tim
    Tim avatar
    39 posts
    Member since:
    Sep 2002

    Posted 23 Apr 2005 Link to this post

    "Still, our grid has been Black-Box tested and it is fully operational. We can only guess what you mean by saying 'Does not seem to accept datasources', but the grid binds quite well with any kind of DataSource, even to such as AccessDataSource, available only in Whidbey. In other words our tests so far show that r.a.d.grid is .NET 2.0 ready. "

    Ok. Tried once more. This is what I have done on 2 seperate machines:

    1. Installed VS2005.beta.2. No earlier VS had ever been installed on the machines.

    2. Made a new website. Added a sql2005 DB via the menus. Made a small table. Populated it with some testdata.

    3. Downloaded rad.grid in zipped version. Added it to the toolbox, and copied the bin and rad.controls dir to the website folder root.

    4. Dragged the rad.grid to the default.aspx page. Dragged the table to  default.aspx page (this also creates a std ms grid that show the table columns ok, and run ok).

    5. Went to the rad.grid's tasks.

    6. Tried to click on rad.grid format. This link does nothing. Its inert.

    7. Now, clicked on the last link, the property builder, which opens a window.

    8. Clicked on general settings, and choose the datasource that corresponds to the new table/db I just made above. The dropdowns are empty btw.

    9. Clicks ok on the property builder. I notice that the rad.grid columns does not reflect being bound to my table. The columnsnames are still column0, column1, etc. Btw, the MS grid shows the correct columnnames.

    10. Runs the site. I only see the MS Grid.

    Now, I tried variation of the above. You know, removing the MS grid, dragging the rad.grid *after* the table, and so on. But the result is the same.

    I interpret the results as if the rad.grid is not compatible with the vs2005 designer even though its compatible with asp.net v2 - or - I'm just not doing it right.

    Oh, and this is not meant as a critique. I fullly appreciate that vs2005 has just been released and one cannot expect software of this complexity,  should work on a new platform, straight out of the box.

    VS2005 is however the focus of my attention, which is why I try to get a feeling for the scope of issues confronting early projects on this technology. In that regard, Telerik is ahead of the curve ;-) 
  8. Mike
    Admin
    Mike avatar
    640 posts

    Posted 25 Apr 2005 Link to this post

    Hi Tim, and thank you for your time on testing the grid under VS2005/.NET 2.0.

    We followed your steps however r.a.d.grid would not work because it would not bind itself automatically (as opposed to MS GridView or other 2.0 bound controls) and would not take advantage of the advanced design-time support. This is on par with our previous statement that "...if a web control should support .NET 2.0 features such as themes, data-source controls, etc, this control will not support .NET 1.x. In other words, the control will support 2.0 and 1.x only if it doesn't use the advanced 2.0 features. Thus you cannot expect a 1.1 compliant control to take advantage of 2.0 features."

    Please, try the same approach again, but after step 9 use the following code in the code behind in PageLoad event handler (C#):

    if ( !IsPostBack )
    {
        this.DataBind();
    }


    You should get the grid bound, with all columns auto-generated.

    Again, thanks for your time and for the nice discussion :)


    Best Regards,
    the telerik team


    P.S. We have some preliminary "unofficial" results from our internal .NET 2.0 testing of the navigational suite. It seems that the DOCTYPE of all WebPages by default is strict Xhtml 1.1 which seems to mess the appearance of all our controls. We will need to double check what is going on in this mode and hopefully will fix the problems on the fly. Other issues: themes are not applied in design time; VS2005 changes the default App_Themes folder to App_Themes_Old after converting the sample projects to 2005 format; the control's icon is changed to a generic control icon but drag'and'drop on the form works; the controls are mostly operational but the sample projects do not work properly.
Back to Top