Forums Ultimate UI for ASP.NET Web Forms
Your Privacy Matters: We use our own and third-party cookies to improve your experience on our website. By continuing to use the website we understand that you accept their use. Cookie Policy
Close
George
40
General Issues with AppStylist
posted

For me the AppStylist although quite powerful has a few issues that leave much to be desired.

  1. The speed on loading or changing style libraries is intolerably slow. part of this appears to be the method in which the program was compiled. I examined the operation of the program using Process Explorer and discovered to my dismay that over 13,000 methods are having to be jitted. this will of course slow any program to a crawl no matter how fast a system you have.
  2. The inability to work with only 1 component.
  3. The program reloading all the styles on even the smallest change. There should be an option to allow manual refreshing as I would like to make several changes before refreshing.
  4. Saving just like loading is intolerably slow. I noticed it says it's making a backup but I have yet to find where this mysterious backup is located.
I find 20 mins to load and begin working rather excessive, and it is adversly affecting my productivity rather then improving it. I would be most appreciative if these issues could be addressed. 

 

Parents
No Data
Reply
  • 40030
    Offline posted

    Hello,

     Thanks for the feedback.

    There is a lot going on behind the scenese of AppStylist. When you open a library, it actually makes a backup in your "My Documents\Infragistics" folder.  This is done, so that we always have a copy that we can revert back to if you accidentally delete something. Saving in memory wasn't an option, so we use a backup directory. However, i agree that there is room for improvment there.

    I have a few tips that should hopefully make working with the tool a little easier.

    If you're only maintaining 1 StyleSet (i.e. Applietini, OfficeBlue, etc) at any given time, create a Library (.wsl) that only contains it. That way, when you open up the library, it will only need to load the specific styleset that you plan on working with.

    Also, if you're creating a styleset, and know that you'll only need certain controls, you can limit the StyleSet to those controls. To do so, Click the "Manage StyleSets" button located in the TopLeft area of the Tool.  Please follow the link below to see a screenshot:

    http://help.infragistics.com/Help/NetAdvantage/NET/2008.1/CLR2.0/html/WebAppStylist_Style_Explorer.html

     In this dialog, you can Add and Remove Stylesets, and also, remove controls from your stylesets. Below is a screenshot of the dialog:

    http://help.infragistics.com/Help/NetAdvantage/NET/2008.1/CLR2.0/html/WebAppStylist_StyleSet_Manager_Dialog_Box.html

    You can uncheck any controls that you don't want, and then click the "OK" button. Note: all stylesheets and control images assoicated with the controls you have chosen to remove, will be removed from the styleset.

    As for your 3rd comment, when you modify a style, for example lets say the background-color of a TreeNode, only the tree's css file should be reloaded, not all the controls. In fact, the canvs itself shouldn't even reload, as it just uses some javascript to cause the css file to refresh.

    Only when  you hit the Refresh button on the top, or modify any shared styles, will all the canvases be reloaded.

    Note, if you're using the TextEditor in the PropertiesPanel: You can hit the F5 key or press the Update button to update your changes.

    http://help.infragistics.com/Help/NetAdvantage/NET/2008.1/CLR2.0/html/WebAppStylist_Text_Editor.html

    I hope this information helps improve your experience with the tool.

    Thanks,

    -SteveZ

     

Children