70-519 – parte 3a
8:01 | Author: Unknown

Designing the User Experience (17%)

Index

Parte 0 | Parte 1 | Parte 2 

Design the site structure.

This objective may include but is not limited to: designing application segmentation for manageability and security (for example, using areas, shared views, master pages, and nested master pages), appropriate use of style sheets, client-side scripting, themes, client ID generation, rendering element modes, routing engine

Una digresión, leamos un poco sobre UX http://en.wikipedia.org/wiki/User_experience
Materiales

Una pagina interesante para ver los cambios de Asp.Net 4 y que nos va a ayudar a entender un poco mas estos puntos http://www.asp.net/LEARN/whitepapers/aspnet4/default.aspx
Ahora yendo punto por punto vamos buscando mas material que nos pueda servir para prepararnos mejor.

Areas

Areas let you group controllers and views into sections of a large application in relative isolation from other sections. Each area can be implemented as a separate ASP.NET MVC project that can then be referenced by the main application. This helps manage complexity when you build a large application and makes it easier for multiple teams to work together on a single application.


Shared Views
Master Pages
 http://msdn.microsoft.com/en-us/library/wtxbf3hh(VS.100).aspx

Nested Master Pages
http://msdn.microsoft.com/en-us/library/x2b3ktt7(VS.100).aspx

Style Sheets
http://www.adobe.com/devnet/dreamweaver/articles/why_css.html 
http://msdn.microsoft.com/en-us/library/h4kete56(VS.100).aspx

Client-side scripting
http://msdn.microsoft.com/en-us/library/aa479302.aspx
http://msdn.microsoft.com/en-us/library/aa479011.aspx
http://www.chadmyers.com/Blog/archive/2007/12/13/using-jquery-with-asp.net-mvc.aspx

Themes
http://msdn.microsoft.com/en-us/library/ykzx33wh(VS.100).aspx

Client ID generation
http://msdn.microsoft.com/en-us/library/system.web.ui.control.clientid(VS.100).aspx
http://gerardocontijoch.wordpress.com/2009/06/12/generacion-personalizada-de-ids-en-asp-net-4-0/

 

Rendering elements modes

By default, when a Web application or Web site targets the .NET Framework 4, the controlRenderingCompatibilityVersion attribute of the pages element is set to "4.0". This element is defined in the machine-level Web.config file and by default applies to all ASP.NET 4 applications:

 
<system.web> 
  <pages controlRenderingCompatibilityVersion="3.5|4.0"/> 
</system.web>


The value for controlRenderingCompatibility is a string, which allows potential new version definitions in future releases. In the current release, the following values are supported for this property:




  • "3.5". This setting indicates legacy rendering and markup. Markup rendered by controls is 100% backward compatible, and the setting of the xhtmlConformance property is honored.


  • "4.0". If the property has this setting, ASP.NET Web server controls do the following:

    • The xhtmlConformance property is always treated as "Strict". As a result, controls render XHTML 1.0 Strict markup.


    • Disabling non-input controls no longer renders invalid styles.


    • div elements around hidden fields are now styled so they do not interfere with user-created CSS rules.


    • Menu controls render markup that is semantically correct and compliant with accessibility guidelines.


    • Validation controls do not render inline styles.


    • Controls that previously rendered border="0" (controls that derive from the ASP.NET Table control, and the ASP.NET Image control) no longer render this attribute.







Routing engine



http://msdn.microsoft.com/en-us/magazine/dd347546.aspx



Continuara….









    • Plan for cross-browser and/or form factors.


      This objective may include but is not limited to: evaluating the impact on client side behaviors, themes, bandwidth, style sheets (including application design - task based or scaled rendering of existing page), when to apply Browsers file, structural approaches, user agents, different platforms (mobile vs. desktop)




    • Plan for globalization.


      This objective may include but is not limited to: designing to support local, regional, language, or cultural preferences, including UI vs. data localization (for example, implementing at database level or resource level), when to use CurrentCulture vs. CurrentUICulture, globalization rollout plan (for example, setting base default language, planning localization), handling Unicode data (for example, what fields to include, request encoding), right-to-left support, vertical text and non-Latin topographies, calendars, data formatting, sorting












        • , , |
        This entry was posted on 8:01 and is filed under , , . You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.