BIWUG 01/09/2005 IW Technologies, what's to come in 2006?
•Transferir como PPT, PDF•
0 gostou•2,218 visualizações
![Agenda ,[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object],[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (14)
Destaque
Destaque (18)
Semelhante a BIWUG 01/09/2005 IW Technologies, what's to come in 2006?
Semelhante a BIWUG 01/09/2005 IW Technologies, what's to come in 2006? (20)
Mais de BIWUG
Mais de BIWUG (20)
Último
Último (20)
BIWUG 01/09/2005 IW Technologies, what's to come in 2006?
- 1. IW technologies, what's to come in 2006? Joris Poelmans http://jopx.blogspot.com
- 7. The Ribbon & Galleries
- 19. Office “12” : Server Investments Better empowerment, TCO and developer productivity Next generation e-mail, project management, workflow, blog and wiki support Enhanced SharePoint Portal aggregation and personalization Great relevance with rich people and business data search Server-based forms and workflow with smart client and browser interfaces Server-based spreadsheets plus BI portals built on SQL Server Analysis Services Integrated document, records and Web content management Unified ASP.NET 2.0 workspace foundation for scalability and extensibility Windows SharePoint Services Site Provisioning, Storage, Security, Management, APIs Collaboration Business Intelligence Portal Business Processes Search Content Management
- 30. WSS 3.0 - Extending the UI <Feature Id="0F121A23-C6BC-400F-87E4-E6BBDD999999" Title="Site Actions Menu Customization" Description="Test Site Actions Menu Customization" Version="12.0.0.0" Scope="Site" xmlns="http://schemas.microsoft.com/sharepoint/"> <ElementManifests> <ElementManifest Location="operations.xml" /> </ElementManifests> </Feature> <CustomAction Id="SiteActionsCustomization" Location="Microsoft.SharePoint.StandardMenu" GroupId="SiteActions" Title="SiteActions Menu Customization" ControlAssembly="SiteAction,Version=1.0.2075.32537,Culture=neutral,PublicKeyToken=018d632ecf51b278" ControlClass="SiteAction.SiteActionCustomization"> </CustomAction>
- 31. WSS – Extending the UI public class SiteActionCustomization : WebControl { protected override void CreateChildControls() { base.CreateChildControls(); MenuItemTemplate menuItem = null; ToolBarMenuButton siteActionsControl = ToolBarMenuButton.GetMenuControl(this); menuItem = new MenuItemTemplate(); menuItem.ID = "CustomAction"; menuItem.Text = "Advanced Permissions"; menuItem.Description = "Manage users for this site."; menuItem.Sequence = 400; menuItem.ClientOnClickNavigateUrl = "/_layouts/user.aspx"; Controls.Add(menuItem); } }
- 38. InfoPath 12
Notas do Editor
- Ribbon is that it's the one and only place to look for functionality in the product. If you want to look through Word 2003 to find an unfamiliar command, you need to look through 3 levels of hierarchical menus, open up 31 toolbars and peruse about 20 Task Panes. It's hard to formulate a &quot;hunting&quot; strategy to find the thing you're looking for because there's no logical path through all of the UI. Chunks – set of related commands on the ribbon
- allows for standard compression on all files without user effort (Dramatic file size improvements)
- Tabs, Chunks , Buttons, Menus, SplitButtons ,ToggleButtons, Labels ,EditBoxes,CheckBoxes DropDowns, ComboBoxes, Galleries
- Possibility to limit the number of versions created for lists with versioning enabled, all lists will be version enabled Alerts Filters for more relevant alerts Richer information about item that has changed in the alert Platform for custom formatting, events, and alerts WSS 3.0 has a recyle bin functionality out of the box. This is actually a 2-level recycle bin - even when a user empties his personal recycle bin, an administrator can still recover the documents
- Possible to do actions when a feature is activated/deactivated
- CMSVNext is built on top of Windows SharePoint Services 3.0 - a name mentionned was Office Web Content Management Server. One of the main goals of this new architecture was to take away the divide between functionality in SharePoint and CMS since customers basically require both