introducing the new ide - intersystems · introducing the new ide bill mccormick ... •features...
TRANSCRIPT
You’ll make breakthroughsYou’ll make breakthroughs
Introducing the New IDEBill McCormick
Product Manager
You’ll make breakthroughs
• Cross Platform
• Open Source
• Modern Experience
• Ecosystem
• Source Control
• Debugging
• Refactoring
• Unit Testing
• Code Analysis
Why?
You’ll make breakthroughs
• We are not turning in to a Java shop
• Is it still relevant?
• Why not browser based?
• In the end its the Ecosystem and Framework
Why Eclipse?
You’ll make breakthroughs
• Started last summer
• We had a lot of questions
• Source?
• Presentation?
• Server or client centric?
• What protocol for communication?
Project Launch
You’ll make breakthroughs
• Source Control is the ONLY source of truth
• We provide a database, not a source control system
• Why should the presentation of code differ from what is stored in
source control
• We should preserve user formatting in the class
• We will make this open and extendable
General Concepts
You’ll make breakthroughs
• 27 supported plugins for Eclipse are available last time I checked
• Built in support for GitHub
• Operates on the source files in the client repository
• We will provide the ability to export your code from the server into
the client repository for the case where no source control is
available
• Studio Hooks will still be available as an option for managing
source but not the default
Source Control
You’ll make breakthroughs
• The default presentation code in the editor will remain UDL
• This will also be the presentation preserved in Source Control
• Some changes here will trickle down in to Studio as well like…
• Storage is a fully defined class member now
• Some new syntaxes still to come
UDL
You’ll make breakthroughs
• We spent a lot of time on this subject
• COS presents challenges to being expressed as a grammar due
to code ambiguities
• We have implemented parsers for the 3-4 specific languages
unique to us like COS and intend to use standard parsers for
things like where we allow javascript
• These parsers do construct standard Eclipse ASTs
Grammar or Parsers?
You’ll make breakthroughs
• Client Side
• AST
• Refactoring
• Search
• Diff
• Workspace and Projects
• Project is linked to a server instance
• IP Address, Web Server Port, Namespace
• Multiple projects can contain the same file and be compiled
and tested across any number of namespaces
Architecture
You’ll make breakthroughs
• RESTful interface for interaction with the client for
• Exploration
• Compilation
• Synchronization
• PUBLIC!
• Debugging is managed through a Web Sockets layer
• We will also have an integrated telnet client
Server Side Architecture
You’ll make breakthroughs
• Features check list before a beta program
• Code Parsing - COS Language
• Class Support
• Routine Support
• Debugging
• Intellisense
• Conversion Plan for moving from XML to UDL in source
• Late Summer
What’s the rollout plan?
You’ll make breakthroughs
Beta Rollout
• Phased plan
• SE Kit - May 1
• Internal Beta Test for ISC Source
• End of May
• One small side project
• Private Customer Beta
• June
• Public Beta
• With 2015.3
• Full Release for 2016.1
• At release time we would hope to convert over latest to UDL
You’ll make breakthroughs
• Define a connection to an instance
• Atelier Explorer
• Export class from Server to Project in UDL format
• Atelier Project
• Tied to Namespace
• Can add new routine or class and compile
• Can launch and debug from Eclipse
• Can check in to Source Control
• Partial COS parser
• No Intellisense
• Full Debugging environment
SE Kit Features
You’ll make breakthroughs
You’ll make breakthroughs
Bill McCormickProduct Manager
@BillMcCormickPM