Oniro outputs and outcomes, consolidating the Oniro brand as a reference in its field. The Oniro Working Group will support the developer community focusing on, at least, the following actions:Įstablish and drive a funding model that enables this working group and its community to operateĭesign and execute a branding, communication, and promotion strategy raising awareness about
#ECLIPSE DEVELOPMENT GROUP SOFTWARE#
Drive the commercial success of this software platform.Support the Oniro developer community in the creation and evolution of the software platform.The Oniro Working Group’s mission is accomplished through two strategic goals: Vendor-neutrality, transparency, and openness. Its ecosystem will be developed in anĮnvironment where collaboration is promoted via the core Eclipse Foundation principles of Oriented, modular, and multikernel open source software platform. In the production and evolution of the Oniro operating system and platform. The Oniro Working Group's mission is to foster an ecosystem of organizations that supports the community
Significantly wider range and number of connected devices, while granting developers a simpler and moreĬurated development experience, enabling them to provide consumers a significantly better user experience. Oniro envisions an evolution in the operating system front that will foster more modular platforms covering a Operating systems to manage the increasing hardware complexity and diversity have not. Hardware has evolved dramatically during the last 30 years. Secondly I've been told that the Eclipse for ABAP platform was developed primarily for SAP Business One development, not ERP development - again this is a point that I can't argue with due to lack of domain knowledge, but the foolishly optimistic side of me wants it to be not true surely ABAP is ABAP whatever you are developing with it.Version 0.4 - Revision history at end of document Vision and Scope
#ECLIPSE DEVELOPMENT GROUP TRIAL#
Having broached this topic with the Lead Dev, I'm not satisfied with the reasons given for not allowing me to trial Eclipse - not that I don't believe them, just my lack of familiarity with ABAP and SAP means I don't understand them fully.įor example, one of the reasons I'm being dissuaded from Eclipse is "it's actually going to cause other issues, like the way SAP handles their lock objects." At the moment this all Greek to me, but I'd expect this either to be a known issue with well understood workarounds/good practices to mitigate it or that this is a fundamental issue dissuading all but the most bleeding edge technologists from adopting Eclipse. Understandably I start as an 'I want to stick to what I know because I'm very productive/comfortable with it' proponent.
Just to give you my initial position on this subject I am brand new to SAP/ABAP (2 months in) and come from a Java background. can different members of a development team chose to work predominantly in Eclipse and others stick solely to the workbench. As well as whether it can be used in parallel, e.g. I understand there are always two significant reasons for not changing aspects development methodology within a company ġ: From a company perspective change has an up front cost in time and complexityĢ: From an employee perspective some people like to stick with what they know and are comfortable/productive with.Ĭonversely there are the two often touted reasons for adopting change:ġ: It will save time (money) in the future.Ģ: Some people always want the latest thing/want to make everyone use the thing they had at their last place because they are productive/comfortable with it.ĭisregarding those reasons for the purpose of this discussion, I'd like to get a balanced view on where eclipse is worth adopting and where it (currently) brings no benefit.