-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
ACS development tools #32
Comments
In an attempt to gain some understanding and thus be able to contribute in the solution of this issue, I've rephrased the description above and posed some questions: Integrated Development Environments (IDEs) ease the development of code in general and within complex frameworks in particular. They also have the potential to lower the learning curve of newcomers. While ACS ships Eclipse as its default IDE, it does not currently provide any integration. 1 - Identify a suitable IDE for all ACS-supported languages. A working prototype of a Java plugin for Eclipse is currently available from a third-party repository. QUESTIONS Best, |
@javarias is the best person to answer specifics on the existing Eclipse plugin. In my opinion, the steps as enumerated are in correct order of priority; I would separate code generation into its own item though. Eclipse has been so far the default IDE shipped with ACS (and historically most popular one among ALMA developers). Which IDE(s) to support should depend on what is currently used within the community. It would be easy to do a quick survey through some of the existing mailing lists. Alternatively, implementing this for an IDE with limited use might lead to limited user testing and feedback. Here are some essentials I think Step 2 (IDE development plugin) should include.
|
…188-acstime-fix to master ICT-10188: Merging since the verification phase was successful. * commit '92be74876db0a881897d3a649d7d0636d2e42809': acstime fix for newer g++
Identify a suitable IDE for all ACS-supported languages. Create plugins to integrate the ACS development environment and generate component code skeletons (see "code generation" project). Provide support for an automated ACS testing environment (ACS component code execution), e.g. integrating an acscommandcenter-like GUI, generating xUnit code skeletons, etc. Support easy deployment into target embedded systems (see "embedded platforms" project).
Integrated Development Environments (IDEs) ease the development of code in general and within complex frameworks in particular. They also have the potential to lower the learning curve of newcomers. While ACS ships Eclipse as its default IDE, it does not currently provide any integration. A working prototype of a Java plugin for Eclipse is currently available from a third-party repository.
The text was updated successfully, but these errors were encountered: