Your SlideShare is downloading. ×
Aras PLM's Browser Neutral Client
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Aras PLM's Browser Neutral Client

527

Published on

Aras PLM's Browser Neutral Client

Aras PLM's Browser Neutral Client

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
527
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. BEDIFFERENT ACE GERMANYCopyright © 2012 Aras. All Rights Reserved. aras.com
  • 2. ACE Germany Browser Neutral Client Rob McAveney Director of Product Management Aras CorpCopyright © 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 properlyCopyright © 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 productionCopyright © 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 adoptedCopyright © 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 necessaryCopyright © 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 releaseCopyright © 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 upgradeCopyright © 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 CorpCopyright © 2012 Aras. All Rights Reserved. aras.com

×