Location via proxy:   [ UP ]  
[Report a bug]   [Manage cookies]                
SlideShare a Scribd company logo

Aras PLM's Browser Neutral Client

•
•
Aras
Aras

Aras is developing a new browser-neutral client for its product Aras Innovator using Dojo and HTML5. The new client will support multiple browsers including IE, Firefox, and Safari on Windows and MacOS. It is currently in beta testing and will be fully released in April 2013 as part of Aras Innovator 10.0, replacing the existing .NET client. The new client is part of Aras' goal to deliver customizable client components that can be used across browsers, mobile, and native platforms.

1 of 11
BEDIFFERENT ACE GERMANY Copyright © 2012 Aras. All Rights Reserved. aras.com
ACE Germany Browser Neutral Client Rob McAveney Director of Product Management Aras Corp Copyright © 2012 Aras. All Rights Reserved. aras.com
Background  Internet Explorer has been the primary browser for Aras Innovator since the beginning  Initially the only browser in mainstream use  Until recently, IE was the only browser that could handle the controls needed for the Aras UI  Corporate adoption of alternate browsers and operating systems has trailed consumer adoption  Controls (grid, toolbar, etc.) built using .NET  Allows for UI similar to a desktop application  Inherently Windows-only  Require .NET security settings to work properly Copyright © 2012 Aras. All Rights Reserved. Slide 3 aras.com
ECCO Project  Aras subscriber ECCO decided to sponsored a project to provide an Aras client to their Mac OS X users  Launched in late 2011 in cooperation with Aras partner Minerva  Direct port of existing client to preserve familiar screens and functions  All customizations needed to work cross-browser  Required a path forward to standard product when released  No support of Aras solutions or admin functions required  Separate clients for IE users and Firefox users  Currently live and stable in production Copyright © 2012 Aras. All Rights Reserved. Slide 4 aras.com
Technology Decisions  Multiple options considered  Cross-platform .NET implementations (Mono, etc.)  Compiled RIA technologies (Flash, Silverlight)  Pure HTML5 vs. HTML5 with a framework  JQuery vs. Dojo  Engaged outside expertise for advice  Prototyped controls using both technologies  Dojo selected • Better suited for web applications (not web sites) • More consistent control library • Fits better with existing code style • Less pervasive than JQuery, but still widely adopted Copyright © 2012 Aras. All Rights Reserved. Slide 5 aras.com
Dojo-based Controls  Aras controls are mostly Aras TreeGrid wrappers around Aras Control API existing Dojo controls Legacy API  Implement behaviors Dojo not present in DataGrid standard Dojo controls  Implement the legacy control API to maintain compatibility  Create a new Aras control API that is more modern, more complete and better documented  Dojo APIs still accessible if necessary Copyright © 2012 Aras. All Rights Reserved. Slide 6 aras.com
Productization Process  Begin with codebase from the ECCO project  Rewrite and refactor most of the existing Javascript code used by the IE client  Create Aras controls and APIs  Add support for solutions and administrative features  Build a foundation for a proper client API  Test extensively on all supported platforms  Converge on a stable build  Document, package and release Copyright © 2012 Aras. All Rights Reserved. Slide 7 aras.com
Roadmap  Beta to be available in the next few days  Currently in final packaging  Installs as a separate instance for testing purposes only  No upgrade path from existing db to beta or from beta db to final release  Additional beta version likely in early 2013  Depends on customer demand  Final release as Aras Innovator 10.0 in April, 2013  New client only – no more .NET client  Upgrades expected to be both popular and time consuming  Advance planning required for a smooth upgrade Copyright © 2012 Aras. All Rights Reserved. Slide 8 aras.com
Platform Support  Aras Innovator 9.4  .NET Client only  Browser Support: IE7, IE8, IE9, IE10  Client OS Support: XP, Vista, Windows 7, Windows 8  Server OS Support: Windows Server 2003 +  Aras Innovator 10.0  HTML5 Client only  .NET security policies no longer required  Browser Support: IE9, IE10, Firefox (Latest)  Client OS Support: Windows 7, Windows 8, OS X (Latest)  Server OS Support: Windows Server 2008 + Copyright © 2012 Aras. All Rights Reserved. Slide 9 aras.com
Path Forward  Long term goal to deliver a set of client building blocks  Drag and drop interface to combine UI elements  Deploy to browser, mobile or native platforms  PLM data to appear in many places, not just a monolithic client  Four step process to move forward Modeled User Browser Client UI Interface Neutral APIs Elements Builder  Aras is aggressively adding development resources  Momentum is growing… Copyright © 2012 Aras. All Rights Reserved. Slide 10 aras.com
ACE Germany Questions ? Rob McAveney Director of Product Management Aras Corp Copyright © 2012 Aras. All Rights Reserved. aras.com

More Related Content

Aras PLM's Browser Neutral Client

  • 1. BEDIFFERENT ACE GERMANY Copyright © 2012 Aras. All Rights Reserved. aras.com
  • 2. ACE Germany Browser Neutral Client Rob McAveney Director of Product Management Aras Corp Copyright © 2012 Aras. All Rights Reserved. aras.com
  • 3. Background  Internet Explorer has been the primary browser for Aras Innovator since the beginning  Initially the only browser in mainstream use  Until recently, IE was the only browser that could handle the controls needed for the Aras UI  Corporate adoption of alternate browsers and operating systems has trailed consumer adoption  Controls (grid, toolbar, etc.) built using .NET  Allows for UI similar to a desktop application  Inherently Windows-only  Require .NET security settings to work properly Copyright © 2012 Aras. All Rights Reserved. Slide 3 aras.com
  • 4. ECCO Project  Aras subscriber ECCO decided to sponsored a project to provide an Aras client to their Mac OS X users  Launched in late 2011 in cooperation with Aras partner Minerva  Direct port of existing client to preserve familiar screens and functions  All customizations needed to work cross-browser  Required a path forward to standard product when released  No support of Aras solutions or admin functions required  Separate clients for IE users and Firefox users  Currently live and stable in production Copyright © 2012 Aras. All Rights Reserved. Slide 4 aras.com
  • 5. Technology Decisions  Multiple options considered  Cross-platform .NET implementations (Mono, etc.)  Compiled RIA technologies (Flash, Silverlight)  Pure HTML5 vs. HTML5 with a framework  JQuery vs. Dojo  Engaged outside expertise for advice  Prototyped controls using both technologies  Dojo selected • Better suited for web applications (not web sites) • More consistent control library • Fits better with existing code style • Less pervasive than JQuery, but still widely adopted Copyright © 2012 Aras. All Rights Reserved. Slide 5 aras.com
  • 6. Dojo-based Controls  Aras controls are mostly Aras TreeGrid wrappers around Aras Control API existing Dojo controls Legacy API  Implement behaviors Dojo not present in DataGrid standard Dojo controls  Implement the legacy control API to maintain compatibility  Create a new Aras control API that is more modern, more complete and better documented  Dojo APIs still accessible if necessary Copyright © 2012 Aras. All Rights Reserved. Slide 6 aras.com
  • 7. Productization Process  Begin with codebase from the ECCO project  Rewrite and refactor most of the existing Javascript code used by the IE client  Create Aras controls and APIs  Add support for solutions and administrative features  Build a foundation for a proper client API  Test extensively on all supported platforms  Converge on a stable build  Document, package and release Copyright © 2012 Aras. All Rights Reserved. Slide 7 aras.com
  • 8. Roadmap  Beta to be available in the next few days  Currently in final packaging  Installs as a separate instance for testing purposes only  No upgrade path from existing db to beta or from beta db to final release  Additional beta version likely in early 2013  Depends on customer demand  Final release as Aras Innovator 10.0 in April, 2013  New client only – no more .NET client  Upgrades expected to be both popular and time consuming  Advance planning required for a smooth upgrade Copyright © 2012 Aras. All Rights Reserved. Slide 8 aras.com
  • 9. Platform Support  Aras Innovator 9.4  .NET Client only  Browser Support: IE7, IE8, IE9, IE10  Client OS Support: XP, Vista, Windows 7, Windows 8  Server OS Support: Windows Server 2003 +  Aras Innovator 10.0  HTML5 Client only  .NET security policies no longer required  Browser Support: IE9, IE10, Firefox (Latest)  Client OS Support: Windows 7, Windows 8, OS X (Latest)  Server OS Support: Windows Server 2008 + Copyright © 2012 Aras. All Rights Reserved. Slide 9 aras.com
  • 10. Path Forward  Long term goal to deliver a set of client building blocks  Drag and drop interface to combine UI elements  Deploy to browser, mobile or native platforms  PLM data to appear in many places, not just a monolithic client  Four step process to move forward Modeled User Browser Client UI Interface Neutral APIs Elements Builder  Aras is aggressively adding development resources  Momentum is growing… Copyright © 2012 Aras. All Rights Reserved. Slide 10 aras.com
  • 11. ACE Germany Questions ? Rob McAveney Director of Product Management Aras Corp Copyright © 2012 Aras. All Rights Reserved. aras.com