EiffelStudio: an EiffelSoftware project - User contributions [en]

Environment Roadmap

2012-08-24T19:20:58Z

Halw:

[[Category:EiffelStudio]]
A [[Language_road_map|separate page]] gives the detailed roadmap for implementation of the '''full ISO/ECMA Eiffel standard'''.

Roadmap information for EiffelStudio releases:

==EiffelStudio long term goals==
===UI===
* Customizable menus and toolbars
* Revisit the project settings window
* Progress bar for degree 6, for C compilation and for automatic precompilation
* Better wizards
* Keyboard support for code browsing/activation - Esc to go to context reference in editor, F9 to set a breakpoint, etc.
* More refactoring
* Smart compiling (The goal is to not have to press the compile button ever).

===Compiler===
* Ability to download libraries/applications from a website directly from EiffelStudio (see [[Configuration_Discovery|Discovering Configuration Files]])
* Add new inheritance clause semantics (rename at the end rather than at the beginning).
* Experimental new catcall mechanism
* Catcall checker

===Debugger===
*Allow editing of variables in debugger
*Expand execution replay mechanism; add possibility of changing values then replaying
*Make sure debugger supports new (ISO/ECMA) mechanisms

===Library===
* Resource library

===Internal===
* Reduce size of C generated in workbench mode

==EiffelStudio 7.1 (15 May 2012)==
===Compiler===
* SCOOP: Add garbage collection of unused SCOOP processors.

===Libraries===
* EiffelVision 2: Make compatible with SCOOP.

==EiffelStudio 7.0 (15 November 2011)==
===Compiler===
* Void safety: "Design mode" will suppress void-safety errors for unreachable code.

===Libraries===
* Library and tool to support creating Microsoft "ribbon" interfaces on Windows based EiffelVision 2 applications.

==EiffelStudio 6.8 (15 May 2011)==
===Compiler===
* SCOOP: Usable implementation of SCOOP model for threads

===Debugger===
* Make debugger "attachable" to and "detachable" from running applications

==EiffelStudio 6.7 (15 November 2010)==
===Compiler===
* Concurrency: implementation of the basic SCOOP model for threads
* Unicode support: accepting UTF-8 Eiffel source file

===Ports===
* EiffelVision: Macintosh native support for COCOA

==EiffelStudio 6.6 (15 May 2010)==
===UI===
* Various improvements to the diagram tool

===Compiler===
* Initial support for QAT and once per object
* New check instruction

===Libraries===
* Default to the void-safe version of the library

==EiffelStudio 6.5 (4th quarter 2009)==
This version will not bring major new functionality. We aim at fixing all the inconveniences that people may have experienced with our previous releases.

===Compiler===
* <del>Added support for new loop construct to iterate over various containers</del>

==EiffelStudio 6.4 (2nd quarter 2009)==
This version will not bring major new functionality. We aim at fixing all the inconveniences that people may have experienced with our previous releases.

===Library===
* <del>Making all libraries void safe</del>
* <del>Added new library for internationalization, diff and encoding</del>
* <del>EiffelNet with IPv6 support</del>

===Testing===
* <del>Improved testing facilities</del>

==EiffelStudio 6.3 (4th quarter 2008)==
===Testing===
* <del>Improved testing tool based on the CDD experiment</del>
* <del>Automatic testing of classes</del>

===Compiler===
* <del>Proper semantics of feature replication and non-conforming inheritance.</del>
* <del>First implementation of void-safety.</del>

==EiffelStudio 6.2 (2nd quarter 2008)==
===UI===
* <del>Contract Editor.</del>
* <del>More intellisense in the editor (snippet, ...)</del>

===Compiler===
* <del>More on attached types and CAPs</del>
* <del>Exception as object</del>

===Documentation===
* <del>Allow reference to external documentation from Eiffel code (external can be: wiki, PDF, Word documents, ...).</del>

==EiffelStudio 6.1 (4th quarter 2007)==
===UI===
* <del>New Errors and Warnings tool</del>

===Compiler===
* <del>Attached mechanism</del>
* <del>Non-conforming inheritance</del>
* <del>Object test syntax support</del>
* <del>Report more than one error at a time</del>
* <del>Added support for MinGW on Windows</del>

===Debugger===
* <del>Execution replay</del>
* <del>Various improvements</del>

==EiffelStudio 6.0 (2nd quarter 2007)==
===UI===
* <del>Improved docking facilities in EiffelStudio to fully control the layout of EiffelStudio</del>
* <del>Configurable pick-and-drop: user can choose between a contextual menu or pick-and-drop within the EiffelStudio environment</del>
* <del>Internationalization support</del>
* <del>Customizable shortcuts</del>

===Compiler===
* <del>Warning/error for changed environment variables used in a project configuration file</del>
* <del>"Hidden" clusters in libraries, clusters that are not accessible if the library is used (like libraries in libraries are not accessible).</del>
* <del>Clean up "inheritance" rules for project settings (e.g. assertion levels of libraries)</del>
* <del>Addition of binary and octal notation for manifest integers</del>

===Internal===
* <del>Clean up delivery, names of tools, directory layout.</del>
* <del>Get rid of *.wb files and store this in the user settings.</del>

==EiffelStudio 5.7 (4th quarter 2006)==
* This is the first open source version of EiffelStudio. Look at the [http://eiffelsoftware.origo.ethz.ch/index.php/EiffelStudio_5.7_Releases release notes of 5.7] for more information.

Main Page

2011-12-14T20:13:16Z

Halw: /* Getting Started */ Removed explicit version reference from "Changelog" entry, substituting redirection

[[Category:General]]__NOTOC__
<h1 class="firstHeading">EiffelStudio Integrated Development Environment</h1>

[[Image:EiffelStudioScreenshot.png|thumb|250px|right|EiffelStudio IDE ([http://eiffel.com/products/studio/screenshots.html more screenshots]) ]]

Welcome to the central resource for EiffelStudio developers and contributors.
==News==
*''28 November 2011'': EiffelStudio 7.0 is available for download at http://www.eiffel.com/downloads
*''25-26 June 2011'': [[Eiffel_Design_Feast_2011 | The Eiffel Design Feast in Zurich]].
*''6 June 2011'': EiffelStudio 6.8 is available for download at http://www.eiffel.com/downloads
*''15 December 2010'': EiffelStudio 6.7 is available for download at http://www.eiffel.com/downloads

==Background==

EiffelStudio is an advanced commercial-grade IDE for the [http://en.wikipedia.org/wiki/Eiffel_programming_language Eiffel programming language]. It is maintained and developed mostly by [http://www.eiffel.com Eiffel Software] and hosted at the [http://se.inf.ethz.ch/ Chair of Software Engineering] at [http://www.ethz.ch/ ETH Zurich].

On April 5th, 2006, Eiffel Software relicensed the EiffelStudio product under the [[Gnu Public License]]. Eiffel Software still offers a commercial variant. Both versions share the same source code.

EiffelStudio is a full-featured IDE offering the following features, many of them unique:

* Complete compiler for the Eiffel programming language, with Design By Contract (DBC) support and both high compile-time speed and high-performance executables, based on the Melting Ice Technology.
* Full portability (including graphics) across Windows, MacOS X, Linux, *BSD, Solaris and other operating systems
* Smart code editor
* Sophisticated multi-view browsing and viewing facilities
* Interactive debugger
* Graphical modeling tool for UML and BON with full roundtrip
* Refactoring support
* GUI development tool (EiffelBuild) and fully portable GUI library (EiffelVision)
* Many other libraries of reusable component.

The Eiffel compiler creates C code that is then handed to a standard C compiler. As a result, Eiffel programs have a run-time performance comparable to those directly written in C or C++, but with the benefits of an advanced object-oriented model and strong typing. EiffelStudio uses a highly efficient compacting garbage collector to free the developer from the burden of memory management.

<center>If you want to know more about the unique features of Eiffel and EiffelStudio, check out our [[Reasons for using Eiffel]] page.</center>

{|style="font-size:80%;" bgcolor=white|
{| cellspacing=8 width="100%"
|- valign="top"
|width="50%" bgcolor="#f6f9fb" style="border:1px solid #8f8f8f;padding:0 .5em .5em .5em;"|

== Getting Started ==

* [[Downloads]]
* [[EiffelStudio Releases|Changelog of current release (release branch)]]
* [http://docs.eiffel.com/book/eiffelstudio/software-installation-eiffelstudio Installing EiffelStudio]
* [[Compiling Hello World]]
|width="50%" bgcolor="#f6f9fb" style="border:1px solid #8f8f8f;padding:0 .5em .5em .5em;"|

== Working with EiffelStudio ==

* [[Frequently Asked Questions]]
* [[Eiffel Glossary]]
* [[Eiffel Compilation Explained]]
* [[EiffelStudio Wish List]]

|- valign="top"
|width="50%" bgcolor="#f6f9fb" style="border:1px solid #8f8f8f;padding:0 .5em .5em .5em;"|
== Contributing! ==

* [[:Category:Projects|How to contribute: the Projects page]]
* [[:Category:Testing|EiffelStudio testing process: you can participate!]]
* [[EiffelStudio 7.0 Releases|Changelog of latest development version, currently 7.0 (development trunk)]]
* [[Repository|Getting the source: Subversion repository]]
* [[Compiling EiffelStudio]]
* [[:Category:Tools|Developer's tools]]
* [[Language_Roadmap|Language roadmap]]
* [[Environment_Roadmap|Environment roadmap]]
* [[Design_and_coding_rules|Design and coding rules]]
|width="50%" bgcolor="#f6f9fb" style="border:1px solid #8f8f8f;padding:0 .5em .5em .5em;"|

== Community ==

* [http://www.eiffelroom.org EiffelRoom]
* [[Spread_the_word|Spread the word]]
* [[Eiffel Sites and Links]]
* [[Mailing Lists]]
* [[:Category:News|News]]
* Join us on IRC at chat.freenode.net #eiffelstudio or through http://community.eiffel.com/irc

|}

Main Page

2011-12-14T20:06:07Z

Halw: /* News */ Added version 7.0

[[Category:General]]__NOTOC__
<h1 class="firstHeading">EiffelStudio Integrated Development Environment</h1>

[[Image:EiffelStudioScreenshot.png|thumb|250px|right|EiffelStudio IDE ([http://eiffel.com/products/studio/screenshots.html more screenshots]) ]]

Welcome to the central resource for EiffelStudio developers and contributors.
==News==
*''28 November 2011'': EiffelStudio 7.0 is available for download at http://www.eiffel.com/downloads
*''25-26 June 2011'': [[Eiffel_Design_Feast_2011 | The Eiffel Design Feast in Zurich]].
*''6 June 2011'': EiffelStudio 6.8 is available for download at http://www.eiffel.com/downloads
*''15 December 2010'': EiffelStudio 6.7 is available for download at http://www.eiffel.com/downloads

==Background==

EiffelStudio is an advanced commercial-grade IDE for the [http://en.wikipedia.org/wiki/Eiffel_programming_language Eiffel programming language]. It is maintained and developed mostly by [http://www.eiffel.com Eiffel Software] and hosted at the [http://se.inf.ethz.ch/ Chair of Software Engineering] at [http://www.ethz.ch/ ETH Zurich].

On April 5th, 2006, Eiffel Software relicensed the EiffelStudio product under the [[Gnu Public License]]. Eiffel Software still offers a commercial variant. Both versions share the same source code.

EiffelStudio is a full-featured IDE offering the following features, many of them unique:

* Complete compiler for the Eiffel programming language, with Design By Contract (DBC) support and both high compile-time speed and high-performance executables, based on the Melting Ice Technology.
* Full portability (including graphics) across Windows, MacOS X, Linux, *BSD, Solaris and other operating systems
* Smart code editor
* Sophisticated multi-view browsing and viewing facilities
* Interactive debugger
* Graphical modeling tool for UML and BON with full roundtrip
* Refactoring support
* GUI development tool (EiffelBuild) and fully portable GUI library (EiffelVision)
* Many other libraries of reusable component.

The Eiffel compiler creates C code that is then handed to a standard C compiler. As a result, Eiffel programs have a run-time performance comparable to those directly written in C or C++, but with the benefits of an advanced object-oriented model and strong typing. EiffelStudio uses a highly efficient compacting garbage collector to free the developer from the burden of memory management.

<center>If you want to know more about the unique features of Eiffel and EiffelStudio, check out our [[Reasons for using Eiffel]] page.</center>

{|style="font-size:80%;" bgcolor=white|
{| cellspacing=8 width="100%"
|- valign="top"
|width="50%" bgcolor="#f6f9fb" style="border:1px solid #8f8f8f;padding:0 .5em .5em .5em;"|

== Getting Started ==

* [[Downloads]]
* [[EiffelStudio 6.8 Releases|Changelog of 6.8 (release branch)]]
* [http://docs.eiffel.com/book/eiffelstudio/software-installation-eiffelstudio Installing EiffelStudio]
* [[Compiling Hello World]]
|width="50%" bgcolor="#f6f9fb" style="border:1px solid #8f8f8f;padding:0 .5em .5em .5em;"|

== Working with EiffelStudio ==

* [[Frequently Asked Questions]]
* [[Eiffel Glossary]]
* [[Eiffel Compilation Explained]]
* [[EiffelStudio Wish List]]

|- valign="top"
|width="50%" bgcolor="#f6f9fb" style="border:1px solid #8f8f8f;padding:0 .5em .5em .5em;"|
== Contributing! ==

* [[:Category:Projects|How to contribute: the Projects page]]
* [[:Category:Testing|EiffelStudio testing process: you can participate!]]
* [[EiffelStudio 7.0 Releases|Changelog of latest development version, currently 7.0 (development trunk)]]
* [[Repository|Getting the source: Subversion repository]]
* [[Compiling EiffelStudio]]
* [[:Category:Tools|Developer's tools]]
* [[Language_Roadmap|Language roadmap]]
* [[Environment_Roadmap|Environment roadmap]]
* [[Design_and_coding_rules|Design and coding rules]]
|width="50%" bgcolor="#f6f9fb" style="border:1px solid #8f8f8f;padding:0 .5em .5em .5em;"|

== Community ==

* [http://www.eiffelroom.org EiffelRoom]
* [[Spread_the_word|Spread the word]]
* [[Eiffel Sites and Links]]
* [[Mailing Lists]]
* [[:Category:News|News]]
* Join us on IRC at chat.freenode.net #eiffelstudio or through http://community.eiffel.com/irc

|}

Downloads

2011-12-04T18:22:08Z

Halw: Updated to redirect to V7.0 releases page and changed 6.x to 7.x

[[Category:EiffelStudio]]
[[Category:Compiler]]
==EiffelStudio 7.x Pre-releases==
We provide versions of EiffelStudio for most popular platforms (Linux, Windows, Solaris, Irix, ...).

You can find the latest builds:
* from the download page of [http://sourceforge.net/project/showfiles.php?group_id=196408 the sourceforge area]
* as well as in [ftp://beta:beta57@ftp.eiffel.com the Eiffel Software beta area] (beware it also includes some nightly build which are untested).
* in [http://eiffelstudio.origo.ethz.ch/download the Origo download area] for the PorterPackage.

Details about new features and bug fixes in the builds are on the [[EiffelStudio_Releases| releases page]].

{{Note|Please be aware that the 7.x versions released through this site are intermediate builds on the road towards official EiffelStudio 7.x. If you are experiencing problems with this release, please use the [http://eiffelstudio.origo.ethz.ch/forum EiffelStudio developer forums] for discussions.}}

The convention used for filenames is the following:
Eiffel70_gpl_$BUILD-$ISE_PLATFORM.[tar.bz2|msi]
Where '''$BUILD''' is a build number, the higher number the more recent release it is, and where '''$ISE_PLATFORM''' is the name of your platform.

Mac OS X builds can be found [[EiffelOnMac|here]].

On Windows, you can use [[Installing_Microsoft_C_compiler|the latest Microsoft C compiler]], but EiffelStudio 6.1 needs [[Installing_Microsoft_C_compiler_6.1_and_older|an older compiler]].

==EiffelStudio 7.x==
You can download the official EiffelStudio 7.x release from [http://www.eiffel.com/downloads/eiffelstudio.html Eiffel Software]. The GPL release can also be downloaded from [http://sourceforge.net/project/showfiles.php?group_id=196408 http://sflogo.sourceforge.net/sflogo.php?group_id=196408.png].

==Doc Builder==
You can download the documentation generation tool for Windows 32-bit with .NET 1.1 installed by extracting the content of [http://download.origo.ethz.ch/eiffelstudio/174/doc_builder.zip doc_builder.zip] (or [http://download.origo.ethz.ch/eiffelstudio/174/doc_builder_64-bit.zip doc_builder_64-bit.zip] for the 64-bit version) onto your hard-drive. Once installed, you can launch the tool by launching the '''doc_builder.exe''' executable.

If you have both .NET 1.1 and .NET 2.0 (or greater), you need to force the loading of .NET 1.1. To do so, edit the file '''doc_builder.exe.config''' so that its content looks like:

<xml>
<configuration>
<startup>
<requiredRuntime version="v1.1.4322" safemode="true"/>
</startup>
<runtime>
<assemblyBinding xmlns="urn:schemas-microsoft-com:asm.v1">
<probing privatePath="Assemblies"/>
</assemblyBinding>
</runtime>
</configuration>
</xml>

EiffelStudio Releases

2011-12-04T18:00:21Z

Halw: Updated to redirect to V7.0 releases page

#REDIRECT [[EiffelStudio 7.0 Releases]]

EiffelStudio Releases

2011-05-17T13:49:27Z

Halw: Updated to redirect to V6.8 releases page

#REDIRECT [[EiffelStudio 6.8 Releases]]

A Simple Guide to Use Internationalization Library

2011-02-27T16:18:10Z

Halw:

[[Category:Internationalization]]

== Overview ==
This page focuses on very simple/general steps to bring i18n library up in your project.

== Steps ==
# Choose and create a directory to put exported translated files (*.mo).
# In your project, initialize a <e>{I18N_LOCALE_MANAGER}</e> using the dir created in step 1.
# Write normal code that uses <e>{I18N_LOCALE}.translation</e> or <e>{I18N_LOCALE}.plural_translation</e> to get translated texts. <e>{I18N_LOCALE}</e> instances can be queried from <e>{I18N_LOCALE_MANAGER}</e>.
# Run [[po_generation_tool]] to extract template file (.pot) to be translated.
# Copy the .pot file to .po files with the name of the language you need. For example, es_ES.po for Spanish, ko_KR.po for Korean.
# Translate .po files using external tools like poEdit for Windows and KBabel or gtranslator for KDE and Gnome.
# Export .mo files using the tools above. And copy them into the directory created in step 1.
# Run the executable, you get translated strings at run-time.

==Process Diagram==

[[Image:I18n process diagram.png]]

File:I18n process diagram.png

2011-02-27T16:15:31Z

Halw: uploaded a new version of "Image:I18n process diagram.png"

File:I18n process diagram.png

2011-02-27T16:08:31Z

Halw:

EiffelStudio Releases

2010-12-31T15:00:53Z

Halw: Updated to redirect to V6.7 releases page

#REDIRECT [[EiffelStudio 6.7 Releases]]

SCOOP-A6: Examples

2010-05-28T16:01:22Z

Halw: Created.

{{UnderConstruction}}
[[Category:Concurrency_(SCOOP)]]
Team: Hal

Objective: Identify a set of SCOOP examples that can be used throughout the development cycle and as examples in the EiffelStudio distribution.

First observations:

A number of examples have been created in an ETHZ project: SCOOP in Practice. The Eiffel Verification Environment (EVE) project includes some of the SCOOP in Practice examples, plus others. Currently the EVE project shows source code for the following examples:

# Baboon Crossing
# Barbershop
# Counter
# Dining Philosophers
# Dining Savages
# Faneuil Hall
# Partree
# Producer/Consumer
# Senate Bus
# Single Element Producer/Consumer

EiffelStudio Releases

2010-03-09T17:57:03Z

Halw: Updated to redirect to V6.6 releases page

#REDIRECT [[EiffelStudio 6.6 Releases]]

Template:ReleaseHistoryHeader

2010-02-02T16:22:27Z

Halw: Fixed link to release notes page to reference Drupal-based docs

Below are not the release notes of EiffelStudio. It is the change log of EiffelStudio intermediate releases and the most important changes are highlighted in red. The release notes of EiffelStudio can be found at the following [http://docs.eiffel.com/book/eiffelstudio/eiffelstudio-release-notes URL]. You can also download the latest revision [http://sourceforge.net/project/showfiles.php?group_id=196408 here]. Information about other version can be found under [[:Category:Releases]].

Category:Projects

2010-01-24T19:05:47Z

Halw: Restructured note to authors

==Contributing to open-source EiffelStudio==
Now that you have [[Spread_the_word|spread the word]] about Eiffel, you feel the urge to contribute to the product itself. There are many ways to help develop EiffelStudio through projects large and small. Check the list of open projects below; if you see one of interest, contact the project members as listed on the corresponding project page. Don't forget to subscribe to the Eiffel developers list (see the [[Mailing_Lists|the mailing lists page]]) where you can post questions about past, current and possible projects.

If you feel none of the current projects covers your special interest, see below how to [[#Adding_your_own_project|add your own project]].

Whatever your contribution, remember that Eiffel is also about style. Make sure you are familiar with the [[Design_and_coding_rules|design and coding rules]] and apply them thoroughly.

{{note| '''To authors of projects available from this page:''' please make sure the project description is up to date and in particular that '''the project members are listed''' and reachable; that's the best way to gain more collaborators. If the project is no longer active please move the entry to [[#Projects_to_be_started_or_restarted|projects to be started or restarted]] section so that someone else may pick it up.}}

__TOC__

== General environment mechanisms ==
There are always new ideas to improve the user experience with EiffelStudio.

* [[Advanced Class and Feature Wizard| Advanced class and feature wizard ]]
::Improve ease of use, for both novice and advanced users, by refining the tools that create classes and features from templates.
*[[Editor|Editor]]
::Improve the EiffelStudio built-in smart editor.
* [[Refactoring|More refactoring mechanisms]]
::While Eiffel doesn't need some of the refactoring mechanisms of other languages, the environment could benefit from new refactoring mechanisms in addition to the ones currently supported.
* [[Eiffel_Mutation_Testing_Tool| Eiffel Mutation Testing Tool]]
::Build a high-quality mutation testing tool (for evaluating the quality of test strategies, fault detectability and redundancy) taking advantage of Eiffel's mechanisms, especially Design by Contract.

{{Note| For tool development check out the [[Tool Integration Development]] page for a quick tutorial on how to integrate a tool window in EiffelStudio.}}

== Graphics and user interface ==
Make the user interface of EiffelStudio more appealing. Much of the work is to be done in the underlying EiffelVision library, with the added benefit that improvements will be available to user applications as well.

*[[Vision2_Accelerator|EiffelVision Accelerators]]
::More keyboard accelerators for EiffelVision applications.
*[[EiffelVision_Unicode|Unicode support for EiffelVision]]
::EiffelVision support for the character set of arbitrary human languages (see also [[Unicode]]).
*[[EiffelBuild_Integration|EiffelBuild Integration]]
::The graphical user interface builder, EiffelBuild, is currently a separate product. Ideally it should be completely integrated with EiffelStudio.
*[[Cocoa_for_EiffelVision2|Cocoa for EiffelVision]]
::Provide EiffelVision with a Carbon back-end to make it truly native on the Mac.
* [[Internationalization|EiffelStudio UI for other languages (internationalization)]]
::EiffelStudio provides support for changing the user interface messages and dialogs to any language. If you are a fluent speaker of a language other than English, you can help the localization into that language.

== Libraries (other than EiffelVision) ==

Eiffel is all about reuse of quality components. The best way to get started as an Eiffel contributor is to extend an existing library, or start a new one to fill a need.

* [[#Graphics_and_user_interface|EiffelVision-related developments appear under graphics and user interface]].
* [[Eiffel_NXT | Eiffel LEGO NXT Commumication Library and EiffelStudio Integration]]
::Remote communication with LEGO NXT Mindstorms "bricks"

== Build infrastructure ==
Developments in this category are intended to help produce new versions of EiffelStudio faster and better.

*[[Build_tool | Build tool]]
::Simplify and streamline the EiffelStudio build process.
*[[Debian_packages | Debian packages]]
::Include EiffelStudio in standard Debian installation
*[[OSX_release_infrastructure|OSX release infrastructure]]
::Script the release of Mac universal binaries for OS X

== Language and compiler ==
This is the heart of the Eiffel environment: providing the best possible implementation of the Eiffel language. See the [[:Category:Compiler|compiler pages]] for detailed information about EiffelStudio's compiling techniques including the Melting Ice Technology.
* [[ECMA Implementation|Full ISO/ECMA support]]
::The Eiffel standard developed by the ECMA TC39-TG4 committee and approved in 2006 by the International Standards Organization is the definitive reference on the Eiffel language. Work is progressing quickly to include all ECMA-ISO mechanisms into the EiffelStudio compiler; you can help fill the remaining gaps.

{{note|On this site you will also find a [[:Category:ECMA|category]] for ECMA pages in which many proposals and other topics are discussed, but are not necessarily approved by the ECMA committee. Refer to the official ISO/ECMA documents for the official word.}}

== Other Stuff ==

* [[ESTeaching | Eiffel Studio for Teaching]]

== Testing ==
Developing is not everything; the results must also be tested for functionality and performance. The EiffelStudio testing process is completely open and follows advanced software engineering standard. Please visit the special [[:Category:Testing|category devoted to EiffelStudio testing]].

== Projects to be started or restarted ==
The projects in this list are mere ideas which may not yet have a project page. Some of them were started but not completed. Feel free to take over! If you do so, move the project to one of the above sections (compiler, libraries etc.). If you have further suggestions you may include them here.
* [[EiffelStudio_Wish_List|EiffelStudio Wish List]]
::Not really the description of a single project, but a collection of ideas of cool things to add to EiffelStudio. Feel free to add to it.
* [[Compilation_Without_Configuration|Compilation without configuration]]
::A mechanism to compile classes without providing a control file.
* [[Wish CHARACTER 16|CHARACTER 16]]
::A request for a new basic type.
*[[Component_standards| Standards and tools for Eiffel-based components]]
::Develop a standard for distributing Eiffel components in binary form, and implement it
* [[Unicode|Unicode support improvement]]
::Improve support for character sets of arbitrary human languages. See also [[EiffelVision_Unicode|EiffelVision Unicode support]].
* [[New_ports|Porting to new platforms (OSX Intel, OpenBSD)]]
::Eiffel is highly portable; a port to a new platform is a moderate effort.
* [[IDE|IDE improvements]]
::This should be replaced by more specific goals, see [[#General_environment_mechanisms|general environment mechanisms]] above.
* [[Extended_static_checking|Extended static checking]]
::See e.g. ESC-Java, Spec#...
* [[Code_checking|Direct code checking (red squiggly lines)]]
::More user-friendly error "non-messages", following the lead of spelling error reporting in MS Word
* [[Learning|Integrated learning support]]
::Support for total beginners
* [[Macros|Editor macro recording and playback]]
::Give EiffelStudio, in particular the editor, a macro facility
* [[Editor_breakpoints|Inserting and navigation of editor breakpoints]]
::Add breakpoints to the editor for better navigation
* [[EMU| Eiffel Multi User]]
::Integrate a repository mechanism
* [[Trace_points|Adding trace points]]
:: Output a trace statement indicating a trace point has been hit, without the need to write code or stop execution
* [[Update_notification|Update notification]]
::An update notification service to let developers know there is a new version available.
* [[Configuration_management|Integrated support for configuration management]]
::Integrate configuration management into EiffelStudio.
*[[Scintilla_component| Multiplatform editor component: Scintilla]]
::Encapsulate Scintilla multi-platform editor
*[[Gecko_component| Multiplatform layout engine component: Mozilla/Gecko]]
::Encapsulate Gecko html multi-platform engine component

== Completed projects ==

* [[AutoTest_Integration|Integrating AutoTest into EiffelStudio]]
::[http://se.ethz.ch/research/autotest/ AutoTest] is an automated testing framework taking advantage of Eiffel's Design by Contract to provide far more automation than current solutions such as JUnit. Currently it is a separate tool; ideally it should be part of EiffelStudio.

== Adding your own project ==
To add your own project:
*Make sure it is not redundant with one of the existing projects. If there is any chance of duplication, please contact the project authors first.
*If you have not already done so, subscribe to the developers' mailing list (see the [[Mailing_Lists|the mailing lists page]]). Post a message to the list explaining your idea and asking for feedback.
*Also check the above [[#Projects_to_be_started_or_restarted|list of "projects to be started or restarted"]], in particular the [[EiffelStudio_Wish_List|EiffelStudio Wish List]]. Some of the pages are just stubs, but others already have a detailed analysis which can serve as a framework for future work on the corresponding features.
*If you decide to go forward, create a page about your project, listing the goals of the project, the rationale (why is this useful?), the issues to be solved, the overall techniques proposed, and a general development strategy. Make sure to include a "project members" section so that people can contact you (for example through your user name on this Wiki).
*Edit the present page so that it includes a link to your project page; select the appropriate category. Below the link, include (as in current entries) a one- or two-line summary of the project's goal.
*Do it!

==See also==
* [[Spread_the_word|Spread the word]]

[[Category:Contributions]]

Category:Projects

2010-01-24T18:59:42Z

Halw: Moved "General environment mechanisms" to the top; Moved "Integrating AutoTest ..." to "Complete projects"

==Contributing to open-source EiffelStudio==
Now that you have [[Spread_the_word|spread the word]] about Eiffel, you feel the urge to contribute to the product itself. There are many ways to help develop EiffelStudio through projects large and small. Check the list of open projects below; if you see one of interest, contact the project members as listed on the corresponding project page. Don't forget to subscribe to the Eiffel developers list (see the [[Mailing_Lists|the mailing lists page]]) where you can post questions about past, current and possible projects.

If you feel none of the current projects covers your special interest, see below how to [[#Adding_your_own_project|add your own project]].

Whatever your contribution, remember that Eiffel is also about style. Make sure you are familiar with the [[Design_and_coding_rules|design and coding rules]] and apply them thoroughly.

'''Note to author of projects''' available from this page: please make sure the project description is up to date and in particular that '''the project members are listed''' and reachable; that's the best way to gain more collaborators. If the project is no longer active please move the entry to [[#Projects_to_be_started_or_restarted|projects to be started or restarted]] section so that someone else may pick it up.
__TOC__

== General environment mechanisms ==
There are always new ideas to improve the user experience with EiffelStudio.

* [[Advanced Class and Feature Wizard| Advanced class and feature wizard ]]
::Improve ease of use, for both novice and advanced users, by refining the tools that create classes and features from templates.
*[[Editor|Editor]]
::Improve the EiffelStudio built-in smart editor.
* [[Refactoring|More refactoring mechanisms]]
::While Eiffel doesn't need some of the refactoring mechanisms of other languages, the environment could benefit from new refactoring mechanisms in addition to the ones currently supported.
* [[Eiffel_Mutation_Testing_Tool| Eiffel Mutation Testing Tool]]
::Build a high-quality mutation testing tool (for evaluating the quality of test strategies, fault detectability and redundancy) taking advantage of Eiffel's mechanisms, especially Design by Contract.

{{Note| For tool development check out the [[Tool Integration Development]] page for a quick tutorial on how to integrate a tool window in EiffelStudio.}}

== Graphics and user interface ==
Make the user interface of EiffelStudio more appealing. Much of the work is to be done in the underlying EiffelVision library, with the added benefit that improvements will be available to user applications as well.

*[[Vision2_Accelerator|EiffelVision Accelerators]]
::More keyboard accelerators for EiffelVision applications.
*[[EiffelVision_Unicode|Unicode support for EiffelVision]]
::EiffelVision support for the character set of arbitrary human languages (see also [[Unicode]]).
*[[EiffelBuild_Integration|EiffelBuild Integration]]
::The graphical user interface builder, EiffelBuild, is currently a separate product. Ideally it should be completely integrated with EiffelStudio.
*[[Cocoa_for_EiffelVision2|Cocoa for EiffelVision]]
::Provide EiffelVision with a Carbon back-end to make it truly native on the Mac.
* [[Internationalization|EiffelStudio UI for other languages (internationalization)]]
::EiffelStudio provides support for changing the user interface messages and dialogs to any language. If you are a fluent speaker of a language other than English, you can help the localization into that language.

== Libraries (other than EiffelVision) ==

Eiffel is all about reuse of quality components. The best way to get started as an Eiffel contributor is to extend an existing library, or start a new one to fill a need.

* [[#Graphics_and_user_interface|EiffelVision-related developments appear under graphics and user interface]].
* [[Eiffel_NXT | Eiffel LEGO NXT Commumication Library and EiffelStudio Integration]]
::Remote communication with LEGO NXT Mindstorms "bricks"

== Build infrastructure ==
Developments in this category are intended to help produce new versions of EiffelStudio faster and better.

*[[Build_tool | Build tool]]
::Simplify and streamline the EiffelStudio build process.
*[[Debian_packages | Debian packages]]
::Include EiffelStudio in standard Debian installation
*[[OSX_release_infrastructure|OSX release infrastructure]]
::Script the release of Mac universal binaries for OS X

== Language and compiler ==
This is the heart of the Eiffel environment: providing the best possible implementation of the Eiffel language. See the [[:Category:Compiler|compiler pages]] for detailed information about EiffelStudio's compiling techniques including the Melting Ice Technology.
* [[ECMA Implementation|Full ISO/ECMA support]]
::The Eiffel standard developed by the ECMA TC39-TG4 committee and approved in 2006 by the International Standards Organization is the definitive reference on the Eiffel language. Work is progressing quickly to include all ECMA-ISO mechanisms into the EiffelStudio compiler; you can help fill the remaining gaps.

{{note|On this site you will also find a [[:Category:ECMA|category]] for ECMA pages in which many proposals and other topics are discussed, but are not necessarily approved by the ECMA committee. Refer to the official ISO/ECMA documents for the official word.}}

== Other Stuff ==

* [[ESTeaching | Eiffel Studio for Teaching]]

== Testing ==
Developing is not everything; the results must also be tested for functionality and performance. The EiffelStudio testing process is completely open and follows advanced software engineering standard. Please visit the special [[:Category:Testing|category devoted to EiffelStudio testing]].

== Projects to be started or restarted ==
The projects in this list are mere ideas which may not yet have a project page. Some of them were started but not completed. Feel free to take over! If you do so, move the project to one of the above sections (compiler, libraries etc.). If you have further suggestions you may include them here.
* [[EiffelStudio_Wish_List|EiffelStudio Wish List]]
::Not really the description of a single project, but a collection of ideas of cool things to add to EiffelStudio. Feel free to add to it.
* [[Compilation_Without_Configuration|Compilation without configuration]]
::A mechanism to compile classes without providing a control file.
* [[Wish CHARACTER 16|CHARACTER 16]]
::A request for a new basic type.
*[[Component_standards| Standards and tools for Eiffel-based components]]
::Develop a standard for distributing Eiffel components in binary form, and implement it
* [[Unicode|Unicode support improvement]]
::Improve support for character sets of arbitrary human languages. See also [[EiffelVision_Unicode|EiffelVision Unicode support]].
* [[New_ports|Porting to new platforms (OSX Intel, OpenBSD)]]
::Eiffel is highly portable; a port to a new platform is a moderate effort.
* [[IDE|IDE improvements]]
::This should be replaced by more specific goals, see [[#General_environment_mechanisms|general environment mechanisms]] above.
* [[Extended_static_checking|Extended static checking]]
::See e.g. ESC-Java, Spec#...
* [[Code_checking|Direct code checking (red squiggly lines)]]
::More user-friendly error "non-messages", following the lead of spelling error reporting in MS Word
* [[Learning|Integrated learning support]]
::Support for total beginners
* [[Macros|Editor macro recording and playback]]
::Give EiffelStudio, in particular the editor, a macro facility
* [[Editor_breakpoints|Inserting and navigation of editor breakpoints]]
::Add breakpoints to the editor for better navigation
* [[EMU| Eiffel Multi User]]
::Integrate a repository mechanism
* [[Trace_points|Adding trace points]]
:: Output a trace statement indicating a trace point has been hit, without the need to write code or stop execution
* [[Update_notification|Update notification]]
::An update notification service to let developers know there is a new version available.
* [[Configuration_management|Integrated support for configuration management]]
::Integrate configuration management into EiffelStudio.
*[[Scintilla_component| Multiplatform editor component: Scintilla]]
::Encapsulate Scintilla multi-platform editor
*[[Gecko_component| Multiplatform layout engine component: Mozilla/Gecko]]
::Encapsulate Gecko html multi-platform engine component

== Completed projects ==

* [[AutoTest_Integration|Integrating AutoTest into EiffelStudio]]
::[http://se.ethz.ch/research/autotest/ AutoTest] is an automated testing framework taking advantage of Eiffel's Design by Contract to provide far more automation than current solutions such as JUnit. Currently it is a separate tool; ideally it should be part of EiffelStudio.

== Adding your own project ==
To add your own project:
*Make sure it is not redundant with one of the existing projects. If there is any chance of duplication, please contact the project authors first.
*If you have not already done so, subscribe to the developers' mailing list (see the [[Mailing_Lists|the mailing lists page]]). Post a message to the list explaining your idea and asking for feedback.
*Also check the above [[#Projects_to_be_started_or_restarted|list of "projects to be started or restarted"]], in particular the [[EiffelStudio_Wish_List|EiffelStudio Wish List]]. Some of the pages are just stubs, but others already have a detailed analysis which can serve as a framework for future work on the corresponding features.
*If you decide to go forward, create a page about your project, listing the goals of the project, the rationale (why is this useful?), the issues to be solved, the overall techniques proposed, and a general development strategy. Make sure to include a "project members" section so that people can contact you (for example through your user name on this Wiki).
*Edit the present page so that it includes a link to your project page; select the appropriate category. Below the link, include (as in current entries) a one- or two-line summary of the project's goal.
*Do it!

==See also==
* [[Spread_the_word|Spread the word]]

[[Category:Contributions]]

Category:Projects

2010-01-24T18:17:04Z

Halw: Reordered project categories; other cosmetic changes.

==Contributing to open-source EiffelStudio==
Now that you have [[Spread_the_word|spread the word]] about Eiffel, you feel the urge to contribute to the product itself. There are many ways to help develop EiffelStudio through projects large and small. Check the list of open projects below; if you see one of interest, contact the project members as listed on the corresponding project page. Don't forget to subscribe to the Eiffel developers list (see the [[Mailing_Lists|the mailing lists page]]) where you can post questions about past, current and possible projects.

If you feel none of the current projects covers your special interest, see below how to [[#Adding_your_own_project|add your own project]].

Whatever your contribution, remember that Eiffel is also about style. Make sure you are familiar with the [[Design_and_coding_rules|design and coding rules]] and apply them thoroughly.

'''Note to author of projects''' available from this page: please make sure the project description is up to date and in particular that '''the project members are listed''' and reachable; that's the best way to gain more collaborators. If the project is no longer active please move the entry to [[#Projects_to_be_started_or_restarted|projects to be started or restarted]] section so that someone else may pick it up.
__TOC__

== Libraries (other than EiffelVision) ==

Eiffel is all about reuse of quality components. The best way to get started as an Eiffel contributor is to extend an existing library, or start a new one to fill a need.

* [[#Graphics_and_user_interface|EiffelVision-related developments appear under graphics and user interface]].
* [[Eiffel_NXT | Eiffel LEGO NXT Commumication Library and EiffelStudio Integration]]
::Remote communication with LEGO NXT Mindstorms "bricks"

== Graphics and user interface ==
Make the user interface of EiffelStudio more appealing. Much of the work is to be done in the underlying EiffelVision library, with the added benefit that improvements will be available to user applications as well.

*[[Vision2_Accelerator|EiffelVision Accelerators]]
::More keyboard accelerators for EiffelVision applications.
*[[EiffelVision_Unicode|Unicode support for EiffelVision]]
::EiffelVision support for the character set of arbitrary human languages (see also [[Unicode]]).
*[[EiffelBuild_Integration|EiffelBuild Integration]]
::The graphical user interface builder, EiffelBuild, is currently a separate product. Ideally it should be completely integrated with EiffelStudio.
*[[Cocoa_for_EiffelVision2|Cocoa for EiffelVision]]
::Provide EiffelVision with a Carbon back-end to make it truly native on the Mac.
* [[Internationalization|EiffelStudio UI for other languages (internationalization)]]
::EiffelStudio provides support for changing the user interface messages and dialogs to any language. If you are a fluent speaker of a language other than English, you can help the localization into that language.

== General environment mechanisms ==
There are always new ideas to improve the user experience with EiffelStudio.

* [[AutoTest_Integration|Integrating AutoTest into EiffelStudio]]
::[http://se.ethz.ch/research/autotest/ AutoTest] is an automated testing framework taking advantage of Eiffel's Design by Contract to provide far more automation than current solutions such as JUnit. Currently it is a separate tool; ideally it should be part of EiffelStudio.
* [[Advanced Class and Feature Wizard| Advanced class and feature wizard ]]
::Improve ease of use, for both novice and advanced users, by refining the tools that create classes and features from templates.
*[[Editor|Editor]]
::Improve the EiffelStudio built-in smart editor.
* [[Refactoring|More refactoring mechanisms]]
::While Eiffel doesn't need some of the refactoring mechanisms of other languages, the environment could benefit from new refactoring mechanisms in addition to the ones currently supported.
* [[Eiffel_Mutation_Testing_Tool| Eiffel Mutation Testing Tool]]
::Build a high-quality mutation testing tool (for evaluating the quality of test strategies, fault detectability and redundancy) taking advantage of Eiffel's mechanisms, especially Design by Contract.

{{Note| For tool development check out the [[Tool Integration Development]] page for a quick tutorial on how to integrate a tool window in EiffelStudio.}}

== Build infrastructure ==
Developments in this category are intended to help produce new versions of EiffelStudio faster and better.

*[[Build_tool | Build tool]]
::Simplify and streamline the EiffelStudio build process.
*[[Debian_packages | Debian packages]]
::Include EiffelStudio in standard Debian installation
*[[OSX_release_infrastructure|OSX release infrastructure]]
::Script the release of Mac universal binaries for OS X

== Language and compiler ==
This is the heart of the Eiffel environment: providing the best possible implementation of the Eiffel language. See the [[:Category:Compiler|compiler pages]] for detailed information about EiffelStudio's compiling techniques including the Melting Ice Technology.
* [[ECMA Implementation|Full ISO/ECMA support]]
::The Eiffel standard developed by the ECMA TC39-TG4 committee and approved in 2006 by the International Standards Organization is the definitive reference on the Eiffel language. Work is progressing quickly to include all ECMA-ISO mechanisms into the EiffelStudio compiler; you can help fill the remaining gaps.

{{note|On this site you will also find a [[:Category:ECMA|category]] for ECMA pages in which many proposals and other topics are discussed, but are not necessarily approved by the ECMA committee. Refer to the official ISO/ECMA documents for the official word.}}

== Other Stuff ==

* [[ESTeaching | Eiffel Studio for Teaching]]

== Testing ==
Developing is not everything; the results must also be tested for functionality and performance. The EiffelStudio testing process is completely open and follows advanced software engineering standard. Please visit the special [[:Category:Testing|category devoted to EiffelStudio testing]].

== Projects to be started or restarted ==
The projects in this list are mere ideas which may not yet have a project page. Some of them were started but not completed. Feel free to take over! If you do so, move the project to one of the above sections (compiler, libraries etc.). If you have further suggestions you may include them here.
* [[EiffelStudio_Wish_List|EiffelStudio Wish List]]
::Not really the description of a single project, but a collection of ideas of cool things to add to EiffelStudio. Feel free to add to it.
* [[Compilation_Without_Configuration|Compilation without configuration]]
::A mechanism to compile classes without providing a control file.
* [[Wish CHARACTER 16|CHARACTER 16]]
::A request for a new basic type.
*[[Component_standards| Standards and tools for Eiffel-based components]]
::Develop a standard for distributing Eiffel components in binary form, and implement it
* [[Unicode|Unicode support improvement]]
::Improve support for character sets of arbitrary human languages. See also [[EiffelVision_Unicode|EiffelVision Unicode support]].
* [[New_ports|Porting to new platforms (OSX Intel, OpenBSD)]]
::Eiffel is highly portable; a port to a new platform is a moderate effort.
* [[IDE|IDE improvements]]
::This should be replaced by more specific goals, see [[#General_environment_mechanisms|general environment mechanisms]] above.
* [[Extended_static_checking|Extended static checking]]
::See e.g. ESC-Java, Spec#...
* [[Code_checking|Direct code checking (red squiggly lines)]]
::More user-friendly error "non-messages", following the lead of spelling error reporting in MS Word
* [[Learning|Integrated learning support]]
::Support for total beginners
* [[Macros|Editor macro recording and playback]]
::Give EiffelStudio, in particular the editor, a macro facility
* [[Editor_breakpoints|Inserting and navigation of editor breakpoints]]
::Add breakpoints to the editor for better navigation
* [[EMU| Eiffel Multi User]]
::Integrate a repository mechanism
* [[Trace_points|Adding trace points]]
:: Output a trace statement indicating a trace point has been hit, without the need to write code or stop execution
* [[Update_notification|Update notification]]
::An update notification service to let developers know there is a new version available.
* [[Configuration_management|Integrated support for configuration management]]
::Integrate configuration management into EiffelStudio.
*[[Scintilla_component| Multiplatform editor component: Scintilla]]
::Encapsulate Scintilla multi-platform editor
*[[Gecko_component| Multiplatform layout engine component: Mozilla/Gecko]]
::Encapsulate Gecko html multi-platform engine component

== Completed projects ==

== Adding your own project ==
To add your own project:
*Make sure it is not redundant with one of the existing projects. If there is any chance of duplication, please contact the project authors first.
*If you have not already done so, subscribe to the developers' mailing list (see the [[Mailing_Lists|the mailing lists page]]). Post a message to the list explaining your idea and asking for feedback.
*Also check the above [[#Projects_to_be_started_or_restarted|list of "projects to be started or restarted"]], in particular the [[EiffelStudio_Wish_List|EiffelStudio Wish List]]. Some of the pages are just stubs, but others already have a detailed analysis which can serve as a framework for future work on the corresponding features.
*If you decide to go forward, create a page about your project, listing the goals of the project, the rationale (why is this useful?), the issues to be solved, the overall techniques proposed, and a general development strategy. Make sure to include a "project members" section so that people can contact you (for example through your user name on this Wiki).
*Edit the present page so that it includes a link to your project page; select the appropriate category. Below the link, include (as in current entries) a one- or two-line summary of the project's goal.
*Do it!

==See also==
* [[Spread_the_word|Spread the word]]

[[Category:Contributions]]

Category:Projects

2010-01-24T18:10:47Z

Halw: Directed ECMA reference to ECMA Implementation page vs. ECMA Category, add note of explanation

==Contributing to open-source EiffelStudio==
Now that you have [[Spread_the_word|spread the word]] about Eiffel, you feel the urge to contribute to the product itself. There are many ways to help develop EiffelStudio through projects large and small. Check the list of open projects below; if you see one of interest, contact the project members as listed on the corresponding project page. Don't forget to subscribe to the Eiffel developers list (see the [[Mailing_Lists|the mailing lists page]]) where you can post questions about past, current and possible projects.

If you feel none of the current projects covers your special interest, see below how to [[#Adding_your_own_project|add your own project]].

Whatever your contribution, remember that Eiffel is also about style. Make sure you are familiar with the [[Design_and_coding_rules|design and coding rules]] and apply them thoroughly.

'''Note to author of projects''' available from this page: please make sure the project description is up to date and in particular that '''the project members are listed''' and reachable; that's the best way to gain more collaborators. If the project is no longer active please move the entry to [[#Projects_to_be_started_or_restarted|projects to be started or restarted]] section so that someone else may pick it up.
__TOC__

== Libraries (other than EiffelVision) ==

Eiffel is all about reuse of quality components. The best way to get started as an Eiffel contributor is to extend an existing library, or start a new one to fill a need.

EiffelVision-related developments appear under [[#Graphics_and_user_interface|graphics and user interface]].
* [[Eiffel_NXT | Eiffel LEGO NXT Commumication Library and EiffelStudio Integration]]
::Remote communication with LEGO NXT Mindstorms "bricks"

== Language and compiler ==
This is the heart of the Eiffel environment: providing the best possible implementation of the Eiffel language. See the [[:Category:Compiler|compiler pages]] for detailed information about EiffelStudio's compiling techniques including the Melting Ice Technology.
* [[ECMA Implementation|Full ISO/ECMA support]]
::The Eiffel standard developed by the ECMA TC39-TG4 committee and approved in 2006 by the International Standards Organization is the definitive reference on the Eiffel language. Work is progressing quickly to include all ECMA-ISO mechanisms into the EiffelStudio compiler; you can help fill the remaining gaps.

{{note|On this site you will also find a [[:Category:ECMA|category]] for ECMA pages in which many proposals and other topics are discussed, but are not necessarily approved by the ECMA committee. Refer to the official ISO/ECMA documents for the official word.}}

== General environment mechanisms ==
There are always new ideas to improve the user experience with EiffelStudio.

* [[AutoTest_Integration|Integrating AutoTest into EiffelStudio]]
::[http://se.ethz.ch/research/autotest/ AutoTest] is an automated testing framework taking advantage of Eiffel's Design by Contract to provide far more automation than current solutions such as JUnit. Currently it is a separate tool; ideally it should be part of EiffelStudio.
* [[Advanced Class and Feature Wizard| Advanced class and feature wizard ]]
::Improve ease of use, for both novice and advanced users, by refining the tools that create classes and features from templates.
*[[Editor|Editor]]
::Improve the EiffelStudio built-in smart editor.
* [[Refactoring|More refactoring mechanisms]]
::While Eiffel doesn't need some of the refactoring mechanisms of other languages, the environment could benefit from new refactoring mechanisms in addition to the ones currently supported.
* [[Eiffel_Mutation_Testing_Tool| Eiffel Mutation Testing Tool]]
::Build a high-quality mutation testing tool (for evaluating the quality of test strategies, fault detectability and redundancy) taking advantage of Eiffel's mechanisms, especially Design by Contract.

{{Note| For tool development check out the [[Tool Integration Development]] page for a quick tutorial on how to integrate a tool window in EiffelStudio.}}

== Graphics and user interface ==
Make the user interface of EiffelStudio more appealing. Much of the work is to be done in the underlying EiffelVision library, with the added benefit that improvements will be available to user applications as well.

*[[Vision2_Accelerator|EiffelVision Accelerators]]
::More keyboard accelerators for EiffelVision applications.
*[[EiffelVision_Unicode|Unicode support for EiffelVision]]
::EiffelVision support for the character set of arbitrary human languages (see also [[Unicode]]).
*[[EiffelBuild_Integration|EiffelBuild Integration]]
::The graphical user interface builder, EiffelBuild, is currently a separate product. Ideally it should be completely integrated with EiffelStudio.
*[[Cocoa_for_EiffelVision2|Cocoa for EiffelVision]]
::Provide EiffelVision with a Carbon back-end to make it truly native on the Mac.
* [[Internationalization|EiffelStudio UI for other languages (internationalization)]]
::EiffelStudio provides support for changing the user interface messages and dialogs to any language. If you are a fluent speaker of a language other than English, you can help the localization into that language.

== Build infrastructure ==
Developments in this category are intended to help produce new versions of EiffelStudio faster and better.

*[[Build_tool | Build tool]]
::Simplify and streamline the EiffelStudio build process.
*[[Debian_packages | Debian packages]]
::Include EiffelStudio in standard Debian installation
*[[OSX_release_infrastructure|OSX release infrastructure]]
::Script the release of Mac universal binaries for OS X

== Other Stuff ==

* [[ESTeaching | Eiffel Studio for Teaching]]

== Testing ==
Developing is not everything; the results must also be tested for functionality and performance. The EiffelStudio testing process is completely open and follows advanced software engineering standard. Please visit the special [[:Category:Testing|category devoted to EiffelStudio testing]].

== Projects to be started or restarted ==
The projects in this list are mere ideas which may not yet have a project page. Some of them were started but not completed. Feel free to take over! If you do so, move the project to one of the above sections (compiler, libraries etc.). If you have further suggestions you may include them here.
* [[EiffelStudio_Wish_List|EiffelStudio Wish List]]
::Not really the description of a single project, but a collection of ideas of cool things to add to EiffelStudio. Feel free to add to it.
* [[Compilation_Without_Configuration|Compilation without configuration]]
::A mechanism to compile classes without providing a control file.
* [[Wish CHARACTER 16|CHARACTER 16]]
::A request for a new basic type.
*[[Component_standards| Standards and tools for Eiffel-based components]]
::Develop a standard for distributing Eiffel components in binary form, and implement it
* [[Unicode|Unicode support improvement]]
::Improve support for character sets of arbitrary human languages. See also [[EiffelVision_Unicode|EiffelVision Unicode support]].
* [[New_ports|Porting to new platforms (OSX Intel, OpenBSD)]]
::Eiffel is highly portable; a port to a new platform is a moderate effort.
* [[IDE|IDE improvements]]
::This should be replaced by more specific goals, see [[#General_environment_mechanisms|general environment mechanisms]] above.
* [[Extended_static_checking|Extended static checking]]
::See e.g. ESC-Java, Spec#...
* [[Code_checking|Direct code checking (red squiggly lines)]]
::More user-friendly error "non-messages", following the lead of spelling error reporting in MS Word
* [[Learning|Integrated learning support]]
::Support for total beginners
* [[Macros|Editor macro recording and playback]]
::Give EiffelStudio, in particular the editor, a macro facility
* [[Editor_breakpoints|Inserting and navigation of editor breakpoints]]
::Add breakpoints to the editor for better navigation
* [[EMU| Eiffel Multi User]]
::Integrate a repository mechanism
* [[Trace_points|Adding trace points]]
:: Output a trace statement indicating a trace point has been hit, without the need to write code or stop execution
* [[Update_notification|Update notification]]
::An update notification service to let developers know there is a new version available.
* [[Configuration_management|Integrated support for configuration management]]
::Integrate configuration management into EiffelStudio.
*[[Scintilla_component| Multiplatform editor component: Scintilla]]
::Encapsulate Scintilla multi-platform editor
*[[Gecko_component| Multiplatform layout engine component: Mozilla/Gecko]]
::Encapsulate Gecko html multi-platform engine component

== Completed projects ==

== Adding your own project ==
To add your own project:
*Make sure it is not redundant with one of the existing projects. If there is any chance of duplication, please contact the project authors first.
*If you have not already done so, subscribe to the developers' mailing list (see the [[Mailing_Lists|the mailing lists page]]). Post a message to the list explaining your idea and asking for feedback.
*Also check the above [[#Projects_to_be_started_or_restarted|list of "projects to be started or restarted"]], in particular the [[EiffelStudio_Wish_List|EiffelStudio Wish List]]. Some of the pages are just stubs, but others already have a detailed analysis which can serve as a framework for future work on the corresponding features.
*If you decide to go forward, create a page about your project, listing the goals of the project, the rationale (why is this useful?), the issues to be solved, the overall techniques proposed, and a general development strategy. Make sure to include a "project members" section so that people can contact you (for example through your user name on this Wiki).
*Edit the present page so that it includes a link to your project page; select the appropriate category. Below the link, include (as in current entries) a one- or two-line summary of the project's goal.
*Do it!

==See also==
* [[Spread_the_word|Spread the word]]

[[Category:Contributions]]

Category:Projects

2010-01-24T18:08:09Z

Halw: Directed ECMA reference to ECMA Implementation page vs. ECMA Category, add note of explanation

==Contributing to open-source EiffelStudio==
Now that you have [[Spread_the_word|spread the word]] about Eiffel, you feel the urge to contribute to the product itself. There are many ways to help develop EiffelStudio through projects large and small. Check the list of open projects below; if you see one of interest, contact the project members as listed on the corresponding project page. Don't forget to subscribe to the Eiffel developers list (see the [[Mailing_Lists|the mailing lists page]]) where you can post questions about past, current and possible projects.

If you feel none of the current projects covers your special interest, see below how to [[#Adding_your_own_project|add your own project]].

Whatever your contribution, remember that Eiffel is also about style. Make sure you are familiar with the [[Design_and_coding_rules|design and coding rules]] and apply them thoroughly.

'''Note to author of projects''' available from this page: please make sure the project description is up to date and in particular that '''the project members are listed''' and reachable; that's the best way to gain more collaborators. If the project is no longer active please move the entry to [[#Projects_to_be_started_or_restarted|projects to be started or restarted]] section so that someone else may pick it up.
__TOC__

== Libraries (other than EiffelVision) ==

Eiffel is all about reuse of quality components. The best way to get started as an Eiffel contributor is to extend an existing library, or start a new one to fill a need.

EiffelVision-related developments appear under [[#Graphics_and_user_interface|graphics and user interface]].
* [[Eiffel_NXT | Eiffel LEGO NXT Commumication Library and EiffelStudio Integration]]
::Remote communication with LEGO NXT Mindstorms "bricks"

== Language and compiler ==
This is the heart of the Eiffel environment: providing the best possible implementation of the Eiffel language. See the [[:Category:Compiler|compiler pages]] for detailed information about EiffelStudio's compiling techniques including the Melting Ice Technology.
* [[ECMA Implementation|Full ISO/ECMA support]]
::The Eiffel standard developed by the ECMA TC39-TG4 committee and approved in 2006 by the International Standards Organization is the definitive reference on the Eiffel language. Work is progressing quickly to include all ECMA-ISO mechanisms into the EiffelStudio compiler; you can help fill the remaining gaps.

{{note|On this site you will also find a [[:Category:ECMA|category]] for ECMA pages in which many proposals and other topics are discussed, but are not necessarily approved by the ECMA committee.}}

== General environment mechanisms ==
There are always new ideas to improve the user experience with EiffelStudio.

* [[AutoTest_Integration|Integrating AutoTest into EiffelStudio]]
::[http://se.ethz.ch/research/autotest/ AutoTest] is an automated testing framework taking advantage of Eiffel's Design by Contract to provide far more automation than current solutions such as JUnit. Currently it is a separate tool; ideally it should be part of EiffelStudio.
* [[Advanced Class and Feature Wizard| Advanced class and feature wizard ]]
::Improve ease of use, for both novice and advanced users, by refining the tools that create classes and features from templates.
*[[Editor|Editor]]
::Improve the EiffelStudio built-in smart editor.
* [[Refactoring|More refactoring mechanisms]]
::While Eiffel doesn't need some of the refactoring mechanisms of other languages, the environment could benefit from new refactoring mechanisms in addition to the ones currently supported.
* [[Eiffel_Mutation_Testing_Tool| Eiffel Mutation Testing Tool]]
::Build a high-quality mutation testing tool (for evaluating the quality of test strategies, fault detectability and redundancy) taking advantage of Eiffel's mechanisms, especially Design by Contract.

{{Note| For tool development check out the [[Tool Integration Development]] page for a quick tutorial on how to integrate a tool window in EiffelStudio.}}

== Graphics and user interface ==
Make the user interface of EiffelStudio more appealing. Much of the work is to be done in the underlying EiffelVision library, with the added benefit that improvements will be available to user applications as well.

*[[Vision2_Accelerator|EiffelVision Accelerators]]
::More keyboard accelerators for EiffelVision applications.
*[[EiffelVision_Unicode|Unicode support for EiffelVision]]
::EiffelVision support for the character set of arbitrary human languages (see also [[Unicode]]).
*[[EiffelBuild_Integration|EiffelBuild Integration]]
::The graphical user interface builder, EiffelBuild, is currently a separate product. Ideally it should be completely integrated with EiffelStudio.
*[[Cocoa_for_EiffelVision2|Cocoa for EiffelVision]]
::Provide EiffelVision with a Carbon back-end to make it truly native on the Mac.
* [[Internationalization|EiffelStudio UI for other languages (internationalization)]]
::EiffelStudio provides support for changing the user interface messages and dialogs to any language. If you are a fluent speaker of a language other than English, you can help the localization into that language.

== Build infrastructure ==
Developments in this category are intended to help produce new versions of EiffelStudio faster and better.

*[[Build_tool | Build tool]]
::Simplify and streamline the EiffelStudio build process.
*[[Debian_packages | Debian packages]]
::Include EiffelStudio in standard Debian installation
*[[OSX_release_infrastructure|OSX release infrastructure]]
::Script the release of Mac universal binaries for OS X

== Other Stuff ==

* [[ESTeaching | Eiffel Studio for Teaching]]

== Testing ==
Developing is not everything; the results must also be tested for functionality and performance. The EiffelStudio testing process is completely open and follows advanced software engineering standard. Please visit the special [[:Category:Testing|category devoted to EiffelStudio testing]].

== Projects to be started or restarted ==
The projects in this list are mere ideas which may not yet have a project page. Some of them were started but not completed. Feel free to take over! If you do so, move the project to one of the above sections (compiler, libraries etc.). If you have further suggestions you may include them here.
* [[EiffelStudio_Wish_List|EiffelStudio Wish List]]
::Not really the description of a single project, but a collection of ideas of cool things to add to EiffelStudio. Feel free to add to it.
* [[Compilation_Without_Configuration|Compilation without configuration]]
::A mechanism to compile classes without providing a control file.
* [[Wish CHARACTER 16|CHARACTER 16]]
::A request for a new basic type.
*[[Component_standards| Standards and tools for Eiffel-based components]]
::Develop a standard for distributing Eiffel components in binary form, and implement it
* [[Unicode|Unicode support improvement]]
::Improve support for character sets of arbitrary human languages. See also [[EiffelVision_Unicode|EiffelVision Unicode support]].
* [[New_ports|Porting to new platforms (OSX Intel, OpenBSD)]]
::Eiffel is highly portable; a port to a new platform is a moderate effort.
* [[IDE|IDE improvements]]
::This should be replaced by more specific goals, see [[#General_environment_mechanisms|general environment mechanisms]] above.
* [[Extended_static_checking|Extended static checking]]
::See e.g. ESC-Java, Spec#...
* [[Code_checking|Direct code checking (red squiggly lines)]]
::More user-friendly error "non-messages", following the lead of spelling error reporting in MS Word
* [[Learning|Integrated learning support]]
::Support for total beginners
* [[Macros|Editor macro recording and playback]]
::Give EiffelStudio, in particular the editor, a macro facility
* [[Editor_breakpoints|Inserting and navigation of editor breakpoints]]
::Add breakpoints to the editor for better navigation
* [[EMU| Eiffel Multi User]]
::Integrate a repository mechanism
* [[Trace_points|Adding trace points]]
:: Output a trace statement indicating a trace point has been hit, without the need to write code or stop execution
* [[Update_notification|Update notification]]
::An update notification service to let developers know there is a new version available.
* [[Configuration_management|Integrated support for configuration management]]
::Integrate configuration management into EiffelStudio.
*[[Scintilla_component| Multiplatform editor component: Scintilla]]
::Encapsulate Scintilla multi-platform editor
*[[Gecko_component| Multiplatform layout engine component: Mozilla/Gecko]]
::Encapsulate Gecko html multi-platform engine component

== Completed projects ==

== Adding your own project ==
To add your own project:
*Make sure it is not redundant with one of the existing projects. If there is any chance of duplication, please contact the project authors first.
*If you have not already done so, subscribe to the developers' mailing list (see the [[Mailing_Lists|the mailing lists page]]). Post a message to the list explaining your idea and asking for feedback.
*Also check the above [[#Projects_to_be_started_or_restarted|list of "projects to be started or restarted"]], in particular the [[EiffelStudio_Wish_List|EiffelStudio Wish List]]. Some of the pages are just stubs, but others already have a detailed analysis which can serve as a framework for future work on the corresponding features.
*If you decide to go forward, create a page about your project, listing the goals of the project, the rationale (why is this useful?), the issues to be solved, the overall techniques proposed, and a general development strategy. Make sure to include a "project members" section so that people can contact you (for example through your user name on this Wiki).
*Edit the present page so that it includes a link to your project page; select the appropriate category. Below the link, include (as in current entries) a one- or two-line summary of the project's goal.
*Do it!

==See also==
* [[Spread_the_word|Spread the word]]

[[Category:Contributions]]

Void-Safe Library Status

2009-03-13T13:00:20Z

Halw: /* Rules */

[[Category:Releases]]

During the [[:Category:EiffelStudio|EiffelStudio]] [[EiffelStudio 6.4 Releases|6.4]] development cycle Eiffel Software and any willing third-party contributors are updating the Eiffel stock [[:Category:Library|libraries]] to be Void-Safe. The libraries will still compile in non-Void-Safe contexts so your code will not be broken. The status reflects work completed so you may start migrating your own code to ensure Void-safety.

Make sure to follow the general rules given below, and ask the community for guidance if you run into any problems or uncertainties.

== Completion Status ==

To better hightlight the usefulness of the void-safety mechanism, we have put together a [[Void-Safe_Library_Results|non-exhaustive list]] of bugs found during the conversion process.

{| class="wikitable"
|-
! width="200"|Library Name
! width="250"|Status
! width="200"|Credits
|-
| EiffelBase
| Done
| Eiffel Software
|-
| EiffelBase extension
| Done
| Eiffel Software (Larry)
|-
| EiffelTime
| Done
| Eiffel Software (Ted, Ian)
|-
| EiffelThread
| Done (classic)
| Eiffel Software (Arno)
|-
| EiffelUUID
| Done
| Eiffel Software ([[User:paulb|Paul]])
|-
| Eiffel2Java
| Done
| Eiffel Software (Ted, Ian)
|-
| WEL
| Done
| Eiffel Software (Manu)
|-
| EiffelVision2
|
|
|-
| EiffelVision2 extension
|
|
|-
| EiffelProcess
| Done (classic)
| Eiffel Software (Arno)
|-
| Argument parser
| Done
| Eiffel Software ([[User:paulb|Paul]])
|-
| EiffelLex
| Done
| Eiffel Software ([[User:paulb|Paul]])
|-
| EiffelParse
| In progress
| Eiffel Software (Ted, Ian)
|-
| EiffelNet
| Done
| Eiffel Software (Manu)
|-
| EiffelNet IPv6
| Done
| Eiffel Software (Manu)
|-
| EiffelCurl
| Done
| Eiffel Software (Manu)
|-
| Encoding
| Done
| Eiffel Software (Ted, Ian)
|-
| EiffelCOM
|
|
|-
| EiffelStore
|
|
|-
| EiffelTesting
| Done
| Eiffel Software (Arno)
|-
| EiffelWeb
| Done
| Eiffel Software (Manu)
|-
| Gobo
| In progress <br> - kernel (done)
| Eiffel Software ([[User:jfiat|Jocelyn]],Larry) + GoboSoft (Eric)
|-
| Docking
|
|
|-
| Gobo extension
| Done
| Eiffel Software ([[User:jfiat|Jocelyn]])
|-
| EiffelGraph
|
|
|-
| Memory Analyzer
|
|
|-
| EiffelPreferences
| Batch done, Remaining Graphical part.
| Eiffel Software ([[User:jfiat|Jocelyn]])
|-
| Diff
| Done
| Eiffel Software ([[User:paulb|Paul]])
|}

== Contributing ==
EiffelStudio is open source and welcomes the Eiffel community contributions to speed up the adaptation process. If you are interested in participating please put a comment on the discussion board with your contact details.

==Rules to be applied ==

Please observe the following guidelines carefully to guarantee a quality result.

=== Examples ===
For examples of libraries already adapted, see UUID (for a small example) and EiffelBase (for a larger one).

=== Overall process ===

# First compile with the `full_class_checking' option on. Then enable the void-safe option.
# Compile libraries on all of Windows/.NET/Unix to ensure it is sound.
# Minimize modifications; types should be attached by default if it makes sense, otherwise it has to be detachable by default.
# Use the convention library-safe.ecf for naming void-safe libraries for now. All library references should be using the -safe.ecf variants.
# Use the same UUIDs for void-safe and non-void-safe libraries.
# Before any modifications add a library.lic and library-safe.lic (replace library with the name of the ECF minus the .ecf extension) next to the ECFs of the same name containing only the single line reference:forum2.
# Update all samples to use the void-safe ecfs and update them.

=== Rules ===
# DO NOT USE '''!''' (attached mark).
# MINIMIZE USE OF OBJECT TEST; ideally, don't use object test unless there was an assignment attempt in the original library.
# When a precondition expects a Void argument, use '''?''' if attached by default.
# When a precondition expects a non-Void argument, use '''!''' if detachable by default.
# Libraries should compile in both void-safe and non-void-safe mode.
# Only use the '''attribute''' keyword when it is impossible to initialize an attribute in the creation procedure. Never use it for lazy evaluation.
# You may include preconditions x /= Void, but it will have to be removed in the end (helped by a compiler warning that says this is not needed for attached x).

=== General cleanup ===
The void-safe adaptation process should be accompanied by a general upgrade to ISO/ECMA Eiffel:

* Remove uses of is_equal and equal to compare objects. (They can cause catcalls.) Replace them with the tilde operator, i.e. a ~ b instead of equal (a, b) or a.is_equal (b). Be careful to preserve the semantics (~ always returns false in the case of non-identical types).
* Replace the '''indexing''' keyword with '''note'''.
* Remove the '''is''' keyword in routines. Use the Replace tool with the regex '''\ is[ \t]*$'''. (Be careful not to use replace all, because comments and multi-line strings may have "is" text!)
* Replace the '''is''' keyword in constants with '''='''.

=== Test authoring ===
1. Create a cluster called 'tests' in the library root folder. E.g., for the UUID library the 'tests' folder exists at '$ISE_LIBRARY/uuid/tests'.

2. In the library ECFs, exclude the 'tests' cluster because it contains testing code and not library code.

3. Add a testing 'tests.ecf' in the 'tests' folder. (See the UUID library for an example ECF.) Be sure to create a library ECF and change the UUID. The library should also use the void-safe options found in the associated library's ECF.

4. Create test class names using the library name along with TEST as a prefix:
EiffelBase = BASE_TEST_
EiffelThread = THREAD_TEST_
EiffelVision2 = EV_TEST_ or VISION2_TEST_

=== Improving this page ===

As you encounter problems and devise your solutions, please include the results of your experience here.

Void-Safe Library Status

2009-03-13T12:59:38Z

Halw: /* Overall process */

[[Category:Releases]]

During the [[:Category:EiffelStudio|EiffelStudio]] [[EiffelStudio 6.4 Releases|6.4]] development cycle Eiffel Software and any willing third-party contributors are updating the Eiffel stock [[:Category:Library|libraries]] to be Void-Safe. The libraries will still compile in non-Void-Safe contexts so your code will not be broken. The status reflects work completed so you may start migrating your own code to ensure Void-safety.

Make sure to follow the general rules given below, and ask the community for guidance if you run into any problems or uncertainties.

== Completion Status ==

To better hightlight the usefulness of the void-safety mechanism, we have put together a [[Void-Safe_Library_Results|non-exhaustive list]] of bugs found during the conversion process.

{| class="wikitable"
|-
! width="200"|Library Name
! width="250"|Status
! width="200"|Credits
|-
| EiffelBase
| Done
| Eiffel Software
|-
| EiffelBase extension
| Done
| Eiffel Software (Larry)
|-
| EiffelTime
| Done
| Eiffel Software (Ted, Ian)
|-
| EiffelThread
| Done (classic)
| Eiffel Software (Arno)
|-
| EiffelUUID
| Done
| Eiffel Software ([[User:paulb|Paul]])
|-
| Eiffel2Java
| Done
| Eiffel Software (Ted, Ian)
|-
| WEL
| Done
| Eiffel Software (Manu)
|-
| EiffelVision2
|
|
|-
| EiffelVision2 extension
|
|
|-
| EiffelProcess
| Done (classic)
| Eiffel Software (Arno)
|-
| Argument parser
| Done
| Eiffel Software ([[User:paulb|Paul]])
|-
| EiffelLex
| Done
| Eiffel Software ([[User:paulb|Paul]])
|-
| EiffelParse
| In progress
| Eiffel Software (Ted, Ian)
|-
| EiffelNet
| Done
| Eiffel Software (Manu)
|-
| EiffelNet IPv6
| Done
| Eiffel Software (Manu)
|-
| EiffelCurl
| Done
| Eiffel Software (Manu)
|-
| Encoding
| Done
| Eiffel Software (Ted, Ian)
|-
| EiffelCOM
|
|
|-
| EiffelStore
|
|
|-
| EiffelTesting
| Done
| Eiffel Software (Arno)
|-
| EiffelWeb
| Done
| Eiffel Software (Manu)
|-
| Gobo
| In progress <br> - kernel (done)
| Eiffel Software ([[User:jfiat|Jocelyn]],Larry) + GoboSoft (Eric)
|-
| Docking
|
|
|-
| Gobo extension
| Done
| Eiffel Software ([[User:jfiat|Jocelyn]])
|-
| EiffelGraph
|
|
|-
| Memory Analyzer
|
|
|-
| EiffelPreferences
| Batch done, Remaining Graphical part.
| Eiffel Software ([[User:jfiat|Jocelyn]])
|-
| Diff
| Done
| Eiffel Software ([[User:paulb|Paul]])
|}

== Contributing ==
EiffelStudio is open source and welcomes the Eiffel community contributions to speed up the adaptation process. If you are interested in participating please put a comment on the discussion board with your contact details.

==Rules to be applied ==

Please observe the following guidelines carefully to guarantee a quality result.

=== Examples ===
For examples of libraries already adapted, see UUID (for a small example) and EiffelBase (for a larger one).

=== Overall process ===

# First compile with the `full_class_checking' option on. Then enable the void-safe option.
# Compile libraries on all of Windows/.NET/Unix to ensure it is sound.
# Minimize modifications; types should be attached by default if it makes sense, otherwise it has to be detachable by default.
# Use the convention library-safe.ecf for naming void-safe libraries for now. All library references should be using the -safe.ecf variants.
# Use the same UUIDs for void-safe and non-void-safe libraries.
# Before any modifications add a library.lic and library-safe.lic (replace library with the name of the ECF minus the .ecf extension) next to the ECFs of the same name containing only the single line reference:forum2.
# Update all samples to use the void-safe ecfs and update them.

=== Rules ===
* DO NOT USE '''!''' (attached mark).
* MINIMIZE USE OF OBJECT TEST; ideally, don't use object test unless there was an assignment attempt in the original library.
* When a precondition expects a Void argument, use '''?''' if attached by default.
* When a precondition expects a non-Void argument, use '''!''' if detachable by default.
* Libraries should compile in both void-safe and non-void-safe mode.
* Only use the '''attribute''' keyword when it is impossible to initialize an attribute in the creation procedure. Never use it for lazy evaluation.
* You may include preconditions x /= Void, but it will have to be removed in the end (helped by a compiler warning that says this is not needed for attached x).

=== General cleanup ===
The void-safe adaptation process should be accompanied by a general upgrade to ISO/ECMA Eiffel:

* Remove uses of is_equal and equal to compare objects. (They can cause catcalls.) Replace them with the tilde operator, i.e. a ~ b instead of equal (a, b) or a.is_equal (b). Be careful to preserve the semantics (~ always returns false in the case of non-identical types).
* Replace the '''indexing''' keyword with '''note'''.
* Remove the '''is''' keyword in routines. Use the Replace tool with the regex '''\ is[ \t]*$'''. (Be careful not to use replace all, because comments and multi-line strings may have "is" text!)
* Replace the '''is''' keyword in constants with '''='''.

=== Test authoring ===
1. Create a cluster called 'tests' in the library root folder. E.g., for the UUID library the 'tests' folder exists at '$ISE_LIBRARY/uuid/tests'.

2. In the library ECFs, exclude the 'tests' cluster because it contains testing code and not library code.

3. Add a testing 'tests.ecf' in the 'tests' folder. (See the UUID library for an example ECF.) Be sure to create a library ECF and change the UUID. The library should also use the void-safe options found in the associated library's ECF.

4. Create test class names using the library name along with TEST as a prefix:
EiffelBase = BASE_TEST_
EiffelThread = THREAD_TEST_
EiffelVision2 = EV_TEST_ or VISION2_TEST_

=== Improving this page ===

As you encounter problems and devise your solutions, please include the results of your experience here.

Void-Safe Library Status

2009-03-13T12:45:00Z

Halw: /* Overall process */

[[Category:Releases]]

During the [[:Category:EiffelStudio|EiffelStudio]] [[EiffelStudio 6.4 Releases|6.4]] development cycle Eiffel Software and any willing third-party contributors are updating the Eiffel stock [[:Category:Library|libraries]] to be Void-Safe. The libraries will still compile in non-Void-Safe contexts so your code will not be broken. The status reflects work completed so you may start migrating your own code to ensure Void-safety.

Make sure to follow the general rules given below, and ask the community for guidance if you run into any problems or uncertainties.

== Completion Status ==

To better hightlight the usefulness of the void-safety mechanism, we have put together a [[Void-Safe_Library_Results|non-exhaustive list]] of bugs found during the conversion process.

{| class="wikitable"
|-
! width="200"|Library Name
! width="250"|Status
! width="200"|Credits
|-
| EiffelBase
| Done
| Eiffel Software
|-
| EiffelBase extension
| Done
| Eiffel Software (Larry)
|-
| EiffelTime
| Done
| Eiffel Software (Ted, Ian)
|-
| EiffelThread
| Done (classic)
| Eiffel Software (Arno)
|-
| EiffelUUID
| Done
| Eiffel Software ([[User:paulb|Paul]])
|-
| Eiffel2Java
| Done
| Eiffel Software (Ted, Ian)
|-
| WEL
| Done
| Eiffel Software (Manu)
|-
| EiffelVision2
|
|
|-
| EiffelVision2 extension
|
|
|-
| EiffelProcess
| Done (classic)
| Eiffel Software (Arno)
|-
| Argument parser
| Done
| Eiffel Software ([[User:paulb|Paul]])
|-
| EiffelLex
| Done
| Eiffel Software ([[User:paulb|Paul]])
|-
| EiffelParse
| In progress
| Eiffel Software (Ted, Ian)
|-
| EiffelNet
| Done
| Eiffel Software (Manu)
|-
| EiffelNet IPv6
| Done
| Eiffel Software (Manu)
|-
| EiffelCurl
| Done
| Eiffel Software (Manu)
|-
| Encoding
| Done
| Eiffel Software (Ted, Ian)
|-
| EiffelCOM
|
|
|-
| EiffelStore
|
|
|-
| EiffelTesting
| Done
| Eiffel Software (Arno)
|-
| EiffelWeb
| Done
| Eiffel Software (Manu)
|-
| Gobo
| In progress <br> - kernel (done)
| Eiffel Software ([[User:jfiat|Jocelyn]],Larry) + GoboSoft (Eric)
|-
| Docking
|
|
|-
| Gobo extension
| Done
| Eiffel Software ([[User:jfiat|Jocelyn]])
|-
| EiffelGraph
|
|
|-
| Memory Analyzer
|
|
|-
| EiffelPreferences
| Batch done, Remaining Graphical part.
| Eiffel Software ([[User:jfiat|Jocelyn]])
|-
| Diff
| Done
| Eiffel Software ([[User:paulb|Paul]])
|}

== Contributing ==
EiffelStudio is open source and welcomes the Eiffel community contributions to speed up the adaptation process. If you are interested in participating please put a comment on the discussion board with your contact details.

==Rules to be applied ==

Please observe the following guidelines carefully to guarantee a quality result.

=== Examples ===
For examples of libraries already adapted, see UUID (for a small example) and EiffelBase (for a larger one).

=== Overall process ===

# First compile with the `full_class_checking' option on. Then enable the void-safe option.
# Compile libraries on all of Windows/.NET/Unix to ensure it is sound.

# Minimize modifications; types should be attached by default if it makes sense, otherwise it has to be detachable by default.
# Use the convention library-safe.ecf for naming void-safe libraries for now. All library references should be using the -safe.ecf variants.
# Use the same UUIDs for void-safe and non-void-safe libraries.
# Before any modifications add a library.lic and library-safe.lic (replace library with the name of the ECF minus the .ecf extension) next to the ECFs of the same name containing only the single line reference:forum2.
# Update all samples to use the void-safe ecfs and update them.

=== Rules ===
* DO NOT USE '''!''' (attached mark).
* MINIMIZE USE OF OBJECT TEST; ideally, don't use object test unless there was an assignment attempt in the original library.
* When a precondition expects a Void argument, use '''?''' if attached by default.
* When a precondition expects a non-Void argument, use '''!''' if detachable by default.
* Libraries should compile in both void-safe and non-void-safe mode.
* Only use the '''attribute''' keyword when it is impossible to initialize an attribute in the creation procedure. Never use it for lazy evaluation.
* You may include preconditions x /= Void, but it will have to be removed in the end (helped by a compiler warning that says this is not needed for attached x).

=== General cleanup ===
The void-safe adaptation process should be accompanied by a general upgrade to ISO/ECMA Eiffel:

* Remove uses of is_equal and equal to compare objects. (They can cause catcalls.) Replace them with the tilde operator, i.e. a ~ b instead of equal (a, b) or a.is_equal (b). Be careful to preserve the semantics (~ always returns false in the case of non-identical types).
* Replace the '''indexing''' keyword with '''note'''.
* Remove the '''is''' keyword in routines. Use the Replace tool with the regex '''\ is[ \t]*$'''. (Be careful not to use replace all, because comments and multi-line strings may have "is" text!)
* Replace the '''is''' keyword in constants with '''='''.

=== Test authoring ===
1. Create a cluster called 'tests' in the library root folder. E.g., for the UUID library the 'tests' folder exists at '$ISE_LIBRARY/uuid/tests'.

2. In the library ECFs, exclude the 'tests' cluster because it contains testing code and not library code.

3. Add a testing 'tests.ecf' in the 'tests' folder. (See the UUID library for an example ECF.) Be sure to create a library ECF and change the UUID. The library should also use the void-safe options found in the associated library's ECF.

4. Create test class names using the library name along with TEST as a prefix:
EiffelBase = BASE_TEST_
EiffelThread = THREAD_TEST_
EiffelVision2 = EV_TEST_ or VISION2_TEST_

=== Improving this page ===

As you encounter problems and devise your solutions, please include the results of your experience here.

EiffelStudio: an EiffelSoftware project:About

2008-12-27T14:57:31Z

Halw: Corrected Eiffel Software company name

Welcome to the home page and Wiki of the EiffelStudio IDE open-source project. EiffelStudio is a full-featured, commercial grade IDE for the [http://en.wikipedia.org/wiki/Eiffel_programming_language Eiffel programming language]. It is maintained and developed by [http://www.eiffel.com Eiffel Software] and hosted at the [http://se.inf.ethz.ch/ Chair of Software Engineering] at the [http://www.ethz.ch/ ETH Zurich].

Eiffel Sites and Links

2008-12-27T14:54:02Z

Halw:

[[Category:General]]
On this page, we would like to capture important resources on the internet concerning Eiffel. Please feel free to add you own links and to remove not-working links. Please always add a small description.

== Tools ==

* [http://www.eiffel.com/ Eiffel Software], the company behind EiffelStudio and major developer of the compiler and the IDE.
* [http://www.gobosoft.com/ GOBO tool chain and libraries], a project to create a high-quality and portable set of libraries for Eiffel.

== Libraries ==

* [http://eiffelzone.com/esd/index.html Eiffel Software Directory], a well-maintained directory of libraries for all Eiffel compilers. The first address to browse to if you are looking for some functionality that you do not want to implement youself.

== Howtos and Guides ==

* [http://docs.eiffel.com/ Online Eiffel Documentation], user guide and library reference for EiffelStudio.
* [http://docs.eiffel.com/eiffelstudio/general/guided_tour/ Getting started with the Eiffel method and language], two articles provided by Eiffel Software.

Collaborative Documentation using Drupal

2008-09-13T14:10:12Z

Halw: Fixed typo

{{UnderConstruction}}
[[Category:Documentation]]
=Plan=

= Things to do=
== Import feature==
Importing content into Drupal's CMS and apply book structure
*<strike>[C1] Convert previous xmldoc (ISE) content, into importable content for Drupal's CMS (Wiki based + meta data)</strike>
*<strike>[L1] Import this specific format + meta data such as parent's page, page order ...</strike>
*[L2] Import documentation of eiffel libraries generated by EiffelStudio

== Export feature==
Export book's content, in order to be able to import them back. This will also be used to store the documentation into subversion
*[S1] export to the importable content (Wiki based + meta data)
*[S2] export to docbook|DITA or similar to generate the PDF output

== CMS feature ==
*[E1] Wysiwyg editor ... for the wikitext, there is a mediawiki extension based on FCKEditor (try to port it to Drupal)
*<strike>[E2] resolve the wiki link inside the drupal CMS (wikitool .. but find a hack to work without unique title ...)</strike>.
*[E3] build a dedicated drupal theme for the documentation site

* About [E2]: For unique title, this is more a hack or workaround, you can have non unique title, but you should avoid.
* About [E1]: this sounds quite tricky to port FCKeditor/Wikitext to drupal. Tricky .. or long, but we'll see...

= Priority =
* <strike>C1, L1</strike>
* E2
* S1
* L2

= Roadmap =
* ~10 Sept: provide intranet Drupal-CMS to edit the documentation online using wikitext on drupal
* end of Sept: make this "intranet" site public, thus ... Internet accessible by the Eiffel community. But let's keep quiet on this. Since it will be between alpha and beta quality. Need dedicated theme, better integration with existing Eiffel websites
* Mid October: Announce, and allow people to become editor if they wish to contribute (they'll have to request this privilege)

== Details ==
* Todo: integrate generated eiffel documentation from EiffelStudio .. (i.e: static html). The way to reference it from drupal is done using [[ref:....|title]] syntax (interwiki)
* Todo: customize the site's theme
* Todo: implement the export to wikitext from Drupal
* Todo: implement the export to PDF ... or whatever

= Misc =
* Wikitext syntax: [http://en.wikipedia.org/wiki/Wikipedia:Cheatsheet Cheatsheet]
* How to edit a wikitext page: http://en.wikipedia.org/wiki/Wikipedia:How_to_edit_a_page

Candidates for FAQs, Tips, and Tricks

2008-07-07T23:20:56Z

Halw:

Here you will find a list of topics and references which are candidates for inclusion in the category EiffelStudio FAQs, Tips, and Tricks. Feel free to add any topics or links that you think are appropriate or to edit the candidates listed here.

==Protecting Eiffel Objects in the presence of C==

Eiffel objects can become exposed to danger when interfacing with C. This short tutorial helps you understand what you need to know to keep your objects safe.

[http://www.eiffelroom.com/article/protecting_objects Protecting Objects]

==C/C++ Call and Callback Examples==

Examples of Calls and Callbacks in C and C++

[http://www.eiffelroom.com/article/c_c_calls_and_callbacks C/C++ calls and callbacks]

==Creating .Net Properties in Eiffel==

When C# and VB.Net programmers work with .Net assemblies, they expect to see .Net properties exposed. But Eiffel does not have explicit support for .Net properties. However it is possible to build Eiffel code that when compiled into an assembly will expose attributes as properties. Here is how it is done:

[http://www.eiffelroom.com/article/create_net_properties_in_eiffel Create .Net Properties in Eiffel]

==EiffelVision 2 How To's==

Here are the answers to several questions commonly posed by EiffelVision 2 developers:

[http://www.eiffelroom.com/article/eiffelvision_2_howtos EiffelVision 2 HowTo's]

==Eiffel Image Embedder==

A tool has been developed to allow the embedding of target graphical image files (png, jpg, etc.) directly into an Eiffel executable. This means that the image files no longer have to be included in the application's distribution. See the tool described at:

[http://www.eiffelroom.com/blog/larryliuming/eiffel_image_embedder_tool Eiffel Image Embedder]

==Object Serialization to a String==

The Serialization cluster provides serialization and deserialization to memory. But the memory in question is a C-style buffer, not an instance of Eiffel class STRING. This short tutorial shows how to use the SED classes to serialize and deserialize Eiffel objects to and from instances of class STRING.

[http://www.eiffelroom.com/article/serialization_to_string Serialization to string]

[[Category:EiffelStudio_FAQs,_Tips,_and_Tricks]]

Category:EiffelStudio FAQs, Tips, and Tricks

2008-06-30T15:49:19Z

Halw:

Pages in this category contain information which may help EiffelStudio users solve problems and acquire techniques that are either not included or not obvious in the standard EiffelStudio documentation.

Here you will find:

*Answers to frequently asked questions.
*Solutions to situations in which EiffelStudio or your projects exhibit odd behavior.
*Potential pitfalls and how to avoid them.
*Secrets of the EiffelStudio masters.

Category:EiffelStudio FAQs, Tips, and Tricks

2008-06-30T15:45:11Z

Halw:

Pages in this category contain information which may help EiffelStudio users solve problems and acquire techniques that may not be included or obvious in the standard EiffelStudio documentation.

Here you will find:

*Answers to frequently asked questions.
*Solutions to situations in which EiffelStudio or your projects exhibit odd behavior.
*Potential pitfalls and how to avoid them.
*Secrets of the EiffelStudio masters.

Restore EiffelStudio Layout

2008-06-30T15:32:08Z

Halw:

==Problem==
While using EiffelStudio you may occasionally lose visibility of a tool pane. This can happen if you close the tool pane, either intentionally or inadvertently. It can also happen in the rare case in which the EiffelStudio tool layout becomes corrupt.

==Solution==
The methods that you can use to restore your lost tool are explained in this article:

[http://eiffelstudio.origo.ethz.ch/node/34 How-to: restore EiffelStudio's layout]

[[Category:EiffelStudio_FAQs,_Tips,_and_Tricks]]

Reasons for using Eiffel

2008-06-29T16:23:04Z

Halw: /* Reasons for Eiffel */

[[Category:General]]
The step away from the main stream of languages is a difficult one. Leaving common ground is worrying. There is always the need to justify unorthodox decisions. This page tries to capture reasons to convince you, your friends, your boss, your client or your grandmother to use Eiffel and EiffelStudio.

You can also read the following articles from Eiffel Software for more reasons:
* [http://docs.eiffel.com/eiffelstudio/general/guided_tour/other/why_eiffel.html Why your next project should use Eiffel]
* [http://docs.eiffel.com/eiffelstudio/general/guided_tour/other/one_minute.html 1-Minute Summary]

== Reasons for Eiffel ==

; Eiffel is object-oriented : While you might think that every modern language is calls itself object-oriented, there are very few languages that have the object-oriented paradigm so deeply integrated into the language as in Eiffel. Eiffel was built around object-orientation. Objects just feel right in Eiffel. Contracts make you understand inheritance. Even if you will change to another language later, object-orientation will never be the same to you once you have developed in Eiffel.

; Eiffel is fast : Eiffel compiles to C, which is then directly translated to the machine code of your target platform. With that you can exploit the full speed of your target architecture. Eiffel can be used in embedded environments or on mainframes. Eiffel competes with C and C++ in terms of speed, not with Java or C#.

; Eiffel has a garbage collector : Memory management is very error prone. Detecting memory leaks is a tedious job that can endanger the reliability of the application. Eiffel was designed from the start to be a language that uses garbage collection. That way, developers do not have to free memory explicitly. EiffelStudio offers a fast moving garbage collector.

; Eiffel is mature : Development on Eiffel started in 1985, long before Java (1991) or C# (2001). During more than two decades, Eiffel has been constantly improved and revised.

; Eiffel is standard : Eiffel is standardized by ECMA standard 367, ISO/IEC DIS 25436

; Eiffel is strongly typed : Eiffel offers a static type system. By this, it can detect conceptual errors much easier than with language with a weak or no type system like C++ or Smalltalk.

; Eiffel has powerful constructs : Eiffel offers constructs like generics (somewhat like Templates) and agents (similar to delegates in .Net), constructs that were only recently added to Java 1.5 or C# 2.0. Also, Eiffel has some unique concepts like Design by Contract and full-featured multiple inheritance.

; Eiffel is highly portable : EiffelStudio has been ported to nearly all major operating systems, from Windows, MacOS X, Linux, FreeBSD to VMS. Portable libraries like EiffelVision2 make it possible to write applications for one platform and compile it for any other platform.

; Eiffel is built on 'Design by Contract' : Design by Contract (DbC) is what made Eiffel famous. Using DbC, you can clearly define what your implementation expects from and what it provides to the caller. This behavior is checked at run-time, making it much easier to find bugs. The contracts are also used from documentation and play an important role for inheritance.

; Eiffel has received the ACM Software System award.

== Reasons for EiffelStudio ==

; EiffelStudio is open-source : EiffelStudio has been released under the well-known Gnu Public License, making sure that the source code will be available in the future and giving you the power to read and modify the system if you need.

; EiffelStudio is supported by a company : Eiffel Software remains the driving force behind EiffelStudio. A horde of full-time employees are working to improve EiffelStudio, react on your questions and provide commercial support if needed.

; EiffelStudio has a power IDE : EiffelStudio features everything that you can expect from a modern IDE, starting with syntax highlighting, organization of your classes, interface extraction of features and classes, hypertext-like browsing, refactoring, and many more.

; EiffelStudio offers incremental compilation : Changed just a single line in your huge system ? No need to wait for minutes or even hours for a recompilation. Even for a million lines of code, recompilation is a matter of seconds.

; EiffelStudio adds run-time checking : Run-time checks of contracts and assertions are an inherit part of Design by Contract. With EiffelStudio, you get a tool for enabling efficient checks for just parts, or for the full system. Problems get reported where they happen, when they happen.

; EiffelStudio has a powerful interactive debugger : The IDE integrates a full-featured debugger that makes it easy to trace what is really happening during execution.

; EiffelStudio allows you to draw UML and BON diagrams : Sometimes a picture can say more than a 1000 words. EiffelStudio integrates an interactive tool to draw UML and BON diagrams. The tool features full round-trip engineering: Any change in the diagram is directly reflected in the code, and any change in the code is directly reflected in the diagram. So, your diagrams never become outdated.