Skip to main content

70-562 Coding Web Parts


Coding Web Parts.

The Web Part framework helps you write code to control all aspects of web parts behavior.

Not all things are automaticaly handled, changing the display mode, changing the personalizing scope, reseting data, creating web parts with custom or user controls, and creating connections.

PersonlizationADministration.FindSharedState method allows to find the personlization data using the FindUserState and ResetUser state.

Web parts can be implement following those typical patterns,
Master/Details(one shows the order, the other the items),
Filter by Form(one shows the order, other allows to edit items,
List/Form
InputDisplay: one to edit, the other to view

A web part can be a data provider, or consumer, or both.

When using provider/consumer, The data is not guaranteed to be final until the prerender event.

Custom controls as web parts allow to add new verbs to web parts, like, Verify.

Specifying whether a control is a provider or cusumer is done in the class using attributes, there are many attributes that allow to specify the scope etc, take time to go through those attributes to see which could be usefull.

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.