2 suggestions

5 posts, 0 answers
  1. Cuthahotha
    Cuthahotha avatar
    81 posts
    Member since:
    Sep 2008

    Posted 11 Sep 2008 Link to this post

    I know this may be a bit late but I have a couple of suggestions.

    First is for to make it easier on the developers.  The default namespace for your products is really long.  And hard to type.

    maybe you could shorten it to 2 or 3 letters.  Ala <ASP:  Maybe <TRC:RadWindow>   Many of use prefer to just type in the name space, then grab the item we want off the intellisense. Much easier than searching through the controls tool box.


    Second idea.  With the fact the silverlight controls xap is downloaded from the website, and all dlls are part of that binary, maybe you could seperate each of your controls into thier own binary.  This would allow use to compile in only the binarys we need to support our appcation. 
  2. Valeri Hristov
    Admin
    Valeri Hristov avatar
    2252 posts

    Posted 12 Sep 2008 Link to this post

    Hello Steve,

    Thank you for your feedback. Now, up to the questions:
    1) This is something we definitely want to change for the RTM of RadControls for Silverlight. As far as I know, there are certain problems in the Silverlight parser that prevent us from the implementation, but I hope that they will be fixed soon.

    2) Currently, we have four assemblies, which I suppose is a relatively good compromise between one assembly, which is the easiest to develop and deploy, and a separate assembly for each control, which is optimal for reducing the size of the XAP file. If the application is not very large and does not use all controls, probably you would spare some kilobytes, but generally, the savings will not be very large.

    In this context, I am curious what is the maximum assembly size of third party controls, that you think is reasonable to add in an application? Currently, the assemblies have the following sizes:
     Name Uncompressed  XAP  XAP Recompressed
     Telerik.Windows.Controls

     319,488

     108,797

     86,590

     Telerik.Windows.Controls.Navigation

     442,368

     128,413

     98,523

     Telerik.Windows.Controls.Input

     335,872

     109,061

     84,411

     Telerik.Windows.Controls.MediaPlayer

     131,584

     30,415

     24,935

    TOTAL

     1,229,312

     376,686 

     294,459


    Sincerely yours,
    Valeri Hristov
    the Telerik team

    Check out Telerik Trainer, the state of the art learning tool for Telerik products.
  3. DevCraft banner
  4. Cuthahotha
    Cuthahotha avatar
    81 posts
    Member since:
    Sep 2008

    Posted 12 Sep 2008 Link to this post

    Valeri,

    Thanks for the quick response.  I don't have a max size.  As small as possible would be my best answer.  Were offloading everthing that's practical in order to make the app as small as possible.  Seldom used graphics will be web referenced, creative use of grahics in code instead of jpg/png files as much as possible, etc.

    The tool were building is going to be specifically for developer collaberation.  to disconnected teams all over the world.  Small remote offices and home workers still do not always have excellent web connecitivity.  (heck im on a Hughes Net Satillite and my connection is slow).  So as I build the application I'm very concerned about file size.

    Thanks,
    Steve
  5. Valeri Hristov
    Admin
    Valeri Hristov avatar
    2252 posts

    Posted 15 Sep 2008 Link to this post

    Hi Steve,

    I understand, your point. I was curious what controls are you planning to use in your application. I meant that a medium-large application, that has 500+kB XAP file, would use most of our bigger general purpose controls - treeview, menu, window, tabstrip, combobox and calendar/datepicker, which contribute for most of the size of our assemblies. Not including several small controls, will not make a big difference by reducing the overall size with 30-40kB. Another thing is if you are going to upgrade the controls, you will have to copy several assemblies, which sometimes is a problem, at least for some of our customers. In other words, our experience from the support we are receiving is that less assemblies are better than more, for the majority of our customers.

    Anyway, if you want to optimize your application to the limit, 30-40kB seems like a reasonable reduction of the XAP file size. I will initiate a new discussion on the matter with the rest of the developers here and we will try to think of something that will satisfy your needs.

    Sincerely yours,
    Valeri Hristov
    the Telerik team

    Check out Telerik Trainer, the state of the art learning tool for Telerik products.
  6. Cuthahotha
    Cuthahotha avatar
    81 posts
    Member since:
    Sep 2008

    Posted 15 Sep 2008 Link to this post

    Valeri,

    Again thanks for the repsonse.  I suppose the number of Rad controls I use will be dependent on exactly what Microsoft has when they release the final product.  Right now, because MS's support for controls is so poor, i think I'll end up using most of your controls and a chart control.

    I'm sure in the end that the size, (a few Kb one way or another of your controls won't matter.

    Again, thanks.
    Steve
Back to Top
DevCraft banner