Skip to main content

70-562 Themes

Theme applies to on the server side on the aspnet control while css client side by the browser
themes are located in teh app_themes folder and defined in skin folders contained in subfolders of the app_theme name of the folder defines the name of the theme

To make a label skin, you take a control markup(or style it through the UI first) and remove everything that's specific to the single control, because it's going to be reused for all control of that type, but it's possible to created named instances of a theme to apply to one instance of a control it is applied to the page, on the docuemnt(or page object?) object and theme property, can also be set in teh page directive, can also be set at runtime in teh preInit event by setting the Theme or StyleSheetTheme property, allowing the user to pick a theme, if you set in the session vairable is good, Page.Theme = Session{"SelecteTheme"].ToString(); to fill a listbox with themes, you do a DirectoryInfo dirThemes = DirectoryInfo(Server.MapPath("App_Themes")) then set the ddl.DataSource = dirThemes.GetDirectories(); ddlThemes.DataBind(); you can aslo set the ddl.SelectedValue = Page.Theme to show the current theme as default in the ddl.

You can put the selected value in Session["SelectedTheme"] = ddlThemes.SelectedValue; and refresh teh page with Server.Transfer(Request.FilePath); the stylesheettheme property of the page(document?) treats the theme as a stylesheet, normaly a theme overrides properies set at design time the EnableTheming property of any control can be set to false.

For named themes create the theme with a SkinID and set this SkinID on the control, so within a skin file you can have both a default skin for the label control and a one with a SkinID attribute, you can have more than one
control use a the named skin, for any page that uses that theme if you specify an imageUrl of an image button in the theme, the path to the image are always relative to the theme folder. If the theme folder includes a css file, this one is also applied.

A theme can be applied at the site level to the whole site.

Comments

Popular posts from this blog

Rxjs Forkjoin vs Zip

These Rxjs combination operators are handy to make Rest calls in parallel and combine their results. Both take n observables and will return the results, with the difference that forkJoin will complete even if one of the nested observables errors of completes.

React JS Patterns

React JS is always evolving, and evolving quickly. These evolutions can be very significant ones, for example, the addition of hooks. React has a lot of code patterns, often these patterns are motivated by the DRY and/or the open-close principle. These patterns sometimes come in to replace a previous one, yet the previous ones still stays in use, as a consequence, the list of patterns keep growing. The goal of the next few posts will be to list the patterns commonly used in React JS developpement. Some patterns are more specific to JSX and I will start with these, and maybe add patterns specific to Redux.

Object.create vs. Object.Assign

The two functions return a new Object but with a difference. Object.assign will go through an enumerable and copy it's properties. Object.create will create a new empty object but link it's proto chain to the old object. One way to view this is with JSON.stringify(newCreatedObject) this would return an empty object, since all the properties are not part of the object's own properties, but inherited through prototype inheritance. In both case, the advantage is it allows to extended existing objects without modifying the original. This is particularly important when receiving arguments from a caller, in this case it's better to use these methods instead of modifying the caller's object since he might have planned to use it again later, expecting it to be in it's original state.