EiffelStudio: an EiffelSoftware project - User contributions [en]

TODOs

2006-07-01T06:52:38Z

Bayt:

[[Category:TODOs]]
Here is the list TODOs for the entire project buildup:

* Automatic build scripts (responsible: [[User:Schoelle| Bernd]]) and coordinate with [[User:Baumanda| Daniel]] for Debian uploads.

Main Page

2006-05-18T05:34:05Z

Bayt: removed questionnaire link and announcement

Welcome to [http://www.eiffel.com/ Eiffel Software]'s Wiki, the home page for Eiffel Software's Open Source initiative in collaboration with the [http://se.inf.ethz.ch/ Chair of Software Engineering] at [http://www.ethz.ch| ETH Zurich].

{{block|'''Project ideas''' 

If you'd like to contribute to the progress of Eiffel technology but don't know where to start, be sure to
take a look at the [[:Category:Projects| project suggestion pages]]. They contain lots of great ideas for projects large and small!}}

To download or look at the source code of EiffelStudio, please go to the [[Repository| SVN repository]] page.

To compile the source code, you will need a snapshot of the current development release of EiffelStudio. To get it go to the [[Downloads| Downloads]] page.

=== Wiki Contents ===

* [[:Category:EiffelStudio|EiffelStudio]]
* [[:Category:EiffelBuild|EiffelBuild]]
* [[:Category:Compiler| Eiffel Compiler]]
* [[:Category:Runtime| Eiffel Runtime]]
* [[:Category:Library| Eiffel Libraries]]:
** [[:Category:EiffelBase| EiffelBase]]
** [[:Category:EiffelVision2| EiffelVision2]]
** [[:Category:WEL| WEL]]
* [[:Category:Documentation| Documentation]]
* [[Repository| SVN repository]]
* [[Contributing| How To Contribute?]]
* [[:Category:Projects| Projects and project suggestions]]
* [[URLs| Useful URLs]]
* [[TODOs| Project TODOs]]

Main Page

2006-05-09T08:42:59Z

Bayt:

Welcome to [http://www.eiffel.com/ Eiffel Software]'s Wiki, the home page for Eiffel Software's Open Source initiative in collaboration with the [http://se.inf.ethz.ch/ Chair of Software Engineering] at [http://www.ethz.ch| ETH Zurich].

{{block|'''Questionnaire''' 

Bernd and Till are writing about the progress of the EiffelStudio project and have compiled a questionnaire. It would be great if everyone completed it, so they can gain a comprehensive overview. The questionnaire can be found [http://eiffelsoftware.origo.ethz.ch/questionnaire.html here] - thanks for participating! }}

{{block|'''Project ideas''' 

If you'd like to contribute to the progress of Eiffel technology but don't know where to start, be sure to
take a look at the [[:Category:Projects| project suggestion pages]]. They contain lots of great ideas for projects large and small!}}

To download or look at the source code of EiffelStudio, please go to the [[Repository| SVN repository]] page.

To compile the source code, you will need a snapshot of the current development release of EiffelStudio. To get it go to the [[Downloads| Downloads]] page.

=== Wiki Contents ===

* [[:Category:EiffelStudio|EiffelStudio]]
* [[:Category:EiffelBuild|EiffelBuild]]
* [[:Category:Compiler| Eiffel Compiler]]
* [[:Category:Runtime| Eiffel Runtime]]
* [[:Category:Library| Eiffel Libraries]]:
** [[:Category:EiffelBase| EiffelBase]]
** [[:Category:EiffelVision2| EiffelVision2]]
** [[:Category:WEL| WEL]]
* [[:Category:Documentation| Documentation]]
* [[Repository| SVN repository]]
* [[Contributing| How To Contribute?]]
* [[:Category:Projects| Projects and project suggestions]]
* [[URLs| Useful URLs]]
* [[TODOs| Project TODOs]]

EiffelStudio 5.7 Releases

2006-05-09T06:55:57Z

Bayt: /* 5.7.x */ typo

[[Category:Releases]]
Below are not the release notes of EiffelStudio. It is the change log of EiffelStudio intermediate releases. The release notes of EiffelStudio can be found at the following [http://docs.eiffel.com/eiffelstudio/tools/eiffelstudio/reference/02_what_s_new URL].
= EiffelStudio 5.7.x Releases=
==5.7.x==
Placeholder for new stuff since last intermediate release.
* Added missing configuration file for precompiled libraries.
* Windows installer can now precompile base|wel|vision2 (did not work previously because configuration files were missing).
* Removed splash screen (windows) and text message (unix) for applications built with GPL release of EiffelStudio.
* Fixed a bug in .NET properties code generation that caused Vision2 precompilation to fail.

==5.7.1005==
* All the 5.6 features are present in this release.
* Support for new project configuration file. At this stage the format is still in beta and therefore expect some future changes before the final release of 5.7. The major changes from semantics point of view are that ultimately we are switching from clusters to clusters/libraries paradigm. Classes of a library should be self-contained, no external references allowed. Library also contains necessary external headers and object files. Also in a cluster or a library, only one class with a given name is allowed.
* Diagram tool has been improved to take into account new libraries paradigm.
* Better display of clusters in cluster tree.
* Improved performance of runtime for large heap: for example if you have about 6GB of allocated memory the full collection time went from 10000s down to 30s when you have about 1GB of garbage and a lot of 0-sized objects.
* Documentation includes recent changes in library, but actually contains too much (e.g. implementation classes in Vision2)
* Pick and drop line is now a dashed line.
* Home key now goes to the first non-whitespace character of the line (can be disabled through the "Smart home" preference).

==5.7.0826==
First public release of the open source version of EiffelStudio. This version uses 5.6 Ace file.
* New search facility with quick search bar and project wide search with regular expression.
* New profiling output using EV_GRID.
* Ability to debug multithreaded applications, in particular to switch from one thread to another.
* New refactoring facilities: class and feature renaming, feature pull-up.
* C compilation output now appears in EiffelStudio.
* Compilation progress now appears in status bar.

Talk:Folding support

2006-05-03T17:29:09Z

Bayt: added tips

[[User:Bayt|Bayt]]

The folding support should be included the: EDITABLE_TEXT_PANEL

= ADT =
WhatWhereWhenHowWhy 
[[User:Sanakan|Sanakan]] 16:59, 26 April 2006 (CEST)

discuss what the ADT of the widget should be like: 

--[[User:Unthomas|Unthomas]] 14:05, 1 May 2006 (CEST) 
Here a link to an interesting paper about ADTs and text editors (node 15):
http://www.cs.unm.edu/~crowley/papers/sds/sds.html 
Are you able to see the figures?

: no images over here, either... but here's a download of said paper: [http://citeseer.ist.psu.edu/rd/0%2C162545%2C1%2C0.25%2CDownload/http://citeseer.ist.psu.edu/compress/0/papers/cs/1797/http:zSzzSzwww.bolthole.comzSzjwordzSzwppaper.ps.gz/crowley98data.ps crowley98data.ps] [[User:Sanakan|Sanakan]] 01:06, 2 May 2006 (CEST)

= working title of the project =

A few ideas:
* Folding -> falten -> eiffel-origami
* FEES : Folding editor for Eiffel Studio
* hidden beauty project
* HYCs : Hide your code
* Folding Fields
* Heilige Dreifaltigkeit

any comments from team members?

[[User:Sanakan|Sanakan]] 22:02, 19 April 2006 (CEST)

[[User:Bayt|Bayt]]
I really like origamiE :-)

TODOs

2006-05-03T13:44:37Z

Bayt: moved to RT

[[Category:TODOs]]
Here is the list TODOs for the entire project buildup:

* create SA branch (responsible: [[User:Schoelle| Bernd]])
* Automatic build scripts (responsible: [[User:Schoelle| Bernd]]) and coordinate with [[User:Baumanda| Daniel]] for Debian uploads.

Main Page

2006-04-26T12:49:37Z

Bayt: removed mailinglists link - it is in the sidebar now

Welcome to [http://www.eiffel.com/ Eiffel Software]'s Wiki, the home page for Eiffel Software's Open Source initiative in collaboration with the [http://se.inf.ethz.ch/ Chair of Software Engineering] at [http://www.ethz.ch| ETH Zurich].

{{block|'''Project ideas''' 

If you'd like to contribute to the progress of Eiffel technology but don't know where to start, be sure to
take a look at the [[:Category:Projects| project suggestion pages]]. They contain lots of great ideas for projects large and small!}}

To download or look at the source code of EiffelStudio, please go to the [[Repository| SVN repository]] page.

To compile the source code, you will need a snapshot of the current development release of EiffelStudio. To get it go to the [[Downloads| Downloads]] page.

=== Wiki Contents ===

* [[:Category:EiffelStudio|EiffelStudio]]
* [[:Category:EiffelBuild|EiffelBuild]]
* [[:Category:Compiler| Eiffel Compiler]]
* [[:Category:Runtime| Eiffel Runtime]]
* [[:Category:Library| Eiffel Libraries]]:
** [[:Category:EiffelBase| EiffelBase]]
** [[:Category:EiffelVision2| EiffelVision2]]
** [[:Category:WEL| WEL]]
* [[:Category:Documentation| Documentation]]
* [[Downloads| Downloads]]
* [[Repository| SVN repository]]
* [[Contributing| How To Contribute?]]
* [[:Category:Projects| Projects and project suggestions]]
* [[URLs| Useful URLs]]
* [[TODOs| Project TODOs]]

Compiling EiffelStudio

2006-04-25T08:31:15Z

Bayt: /* Compiling run-time on Windows */ typo

[[Category:Compiler]]
[[Category:EiffelStudio]]

== Installing EiffelStudio ==

To compile EiffelStudio, you need an already working EiffelStudio compiler on your machine. The current source tree '''requires at least version 5.7''' of EiffelStudio. You can download it from http://eiffelsoftware.origo.ethz.ch/downloads/builds/. This version still requires a registration (we missed to remove the registration cluster while compiling). You need to '''activate''' EiffelStudio (see below), because in some cases the compiler won't work correctly if not activated. [[Installing EiffelStudio]] is covered in its own article.

'''Note:''' on Windows you will need the Microsoft C compiler to compile Eiffel Studio. How to install the free version of the Microsoft C compiler: [[Installing Microsoft C compiler]]

===Compilation methods===
Currently there are two compilation methods.
* You can use one of the [[Automatic Build Scripts]]
* Alternatively you can compile EiffelStudio from scratch following the instructions in this document.

If possible, use the [[Automatic Build Scripts]] and report any errors to the [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-devel developer mailing list].

==Extracting source code==

===Checking out from SVN===
#Point an environment variable called '''EIFFEL_SRC''' to the directory where you want to compile EiffelStudio Usually we use the '''XXdev''' convention for this directory name - where XX is the version number from the current developped version of the compiler.
#Make sure that '''ISE_EIFFEL''', '''ISE_PLATFORM''' and '''ISE_C_COMPILER''' (on windows only) are properly defined
#Perform the following checkout procedures:

'''DOS'''
<pre>
set SVNURL=https://eiffelsoftware.origo.ethz.ch/svn/es
svn co %SVNURL%/trunk/Src 57dev
svn co %SVNURL%/trunk/Delivery 57dev/Delivery
svn co %SVNURL%/trunk/free_add_ons 57dev/free_add_ons
</pre>

'''Bash'''
<pre>
export SVNURL=https://eiffelsoftware.origo.ethz.ch/svn/es
svn co $SVNURL/trunk/Src 57dev
svn co $SVNURL/trunk/Delivery 57dev/Delivery
svn co $SVNURL/trunk/free_add_ons 57dev/free_add_ons
</pre>

To update the sourcefiles to the latest revision, perform the following steps:

'''Bash and DOS'''
<pre>
cd 57dev
svn up
svn up free_add_ons
svn up Delivery
</pre>

==Installing gobo==

Please make sure to use the version provided or the very latest version from CVS. All other versions (including the official 3.4 release) will not work because of name clashes in the UC_STRING class between GOBO and EiffelStudio. 
As the anonymous CVS on sourceforge is currently broken, use the following link from the gobo newsgroup to get the [http://www.gobosoft.com/download/gobo-cvs-060418.zip CVS-checkout of 18.April].

===Windows specific===

You have to unzip the gobo distribution from $EIFFEL_SRC/free_add_ons/gobo/gobo_34_win.tgz and extract it into $EIFFEL_SRC/library.

===Unix specific===

You have to unzip the gobo distribution from $EIFFEL_SRC/free_add_ons/gobo/gobo_34_unix.tgz and extract it into $EIFFEL_SRC/library. Here is the list of commands to do this:
<pre>cd $EIFFEL_SRC/library
tar -xvzf $EIFFEL_SRC/free_add_ons/gobo/gobo_34_unix.tgz
</pre>

==Compiling C libraries==

===Compiling run-time on Windows===

Before being able to compile the run-time, you need to ensure that '''bash''' is in your '''PATH'''. You can download it from [http://www.cygwin.com http://www.cygwin.com]. Also make sure, that the path to the binaries of your c compiler is placed before the path to cygwin or else the wrong linker will be used. Once done you can do: 
'''Important:''' if you are using the setup as described in [[Installing Microsoft C compiler]] please read this first: [http://origo.ethz.ch/pipermail/es-devel/2006-April/000082.html mail from manus] you need to replace this file: <code>%EIFFEL_SRC%/C/CONFIGS/windows-msc-x86</code>

'''DOS'''
<pre>cd %EIFFEL_SRC%/C
configure [win32|win64] [b|m]</pre>

'''Bash'''
<pre>cd $EIFFEL_SRC/C
./configure.bat [win32|win64] [b|m]</pre>

The first argument indicated whether you are compiling the run-time for 32 or 64 bits. The second one is to tell which C compiler will be used. For now only `b' (Borland) and `m' (Microsoft) are officially supported. We also informally support `g' (GCC) and `l' (LCC).

On Windows 32 bits to clean up all the generated files you do:

'''DOS'''
<pre>configure clean</pre>
'''Bash'''
<pre>./configure.bat clean</pre>

On Windows 64 bits, you do:
<pre>configure cleand</pre>

===Compiling run-time on Unix===

The command is simply:
<pre>cd $EIFFEL_SRC/C
./quick_configure</pre>
This requires that '''ISE_PLATFORM''' is properly defined. The `quick_configure' script will look for the file CONFIGS/$ISE_PLATFORM and use it to extract the platform specific information to compile the run-time. If not found then an error will be reported.

===Compiling C code from libraries===

Here is the list of commands to compile all required C libraries on Windows:

'''DOS'''
<pre>cd %EIFFEL_SRC%/library/net/Clib
make_msc.bat
cd %EIFFEL_SRC%/library/vision2/Clib
make_msc.bat
cd %EIFFEL_SRC%/library/wel/Clib
make_msc.bat</pre>
'''Bash'''
<pre>cd $EIFFEL_SRC/library/net/Clib
./make_msc.bat
cd $EIFFEL_SRC/library/vision2/Clib
./make_msc.bat
cd $EIFFEL_SRC/library/wel/Clib
./make_msc.bat</pre>

On Unix it is slightly different:
<pre>cd $EIFFEL_SRC/library/event/Clib
finish_freezing -library
cd $EIFFEL_SRC/library/net/Clib
finish_freezing -library
cd $EIFFEL_SRC/library/vision2/Clib
finish_freezing -library
cd $EIFFEL_SRC/library/vision2/implementation/gtk/Clib
finish_freezing -library</pre>

Make sure that '''ISE_EIFFEL''' is set correctly to your current "EiffelStudio" installation!

===Compiling C code from C_library===

This is only required on Windows to read PNG file. On Unix, this is not required because it is included in GTK+2.4. Simply do the following:

'''DOS'''
<pre>cd %EIFFEL_SRC%/C_library/zlib
make_msc.bat
cd %EIFFEL_SRC%/C_library/libpng
make_msc.bat</pre>
'''Bash'''
<pre>cd $EIFFEL_SRC/C_library/zlib
./make_msc.bat
cd $EIFFEL_SRC/C_library/libpng
./make_msc.bat</pre>

===Compiling C code from compiler===

This is only required on Windows as this C code is a tiny wrapper around the Microsoft C++ API to generate and to debug .NET code.

To compile it, you first need to install the Microsoft .NET SDK. You can download it from their website.

After installing it, you need to update your '''LIB''' and '''INCLUDE''' environment variable to include the path the lib and include directory of the .NET Framework SDK.

Once properly installed, you can do:

'''DOS'''
<pre>cd %EIFFEL_SRC%/Eiffel/library/cli_writer/Clib
nmake</pre>
'''Bash'''
<pre>cd $EIFFEL_SRC/Eiffel/library/cli_writer/Clib
nmake</pre>

==Compiling EiffelStudio==

Now that we have taken care of the C code compilation we can compile the compiler. There are four ace files in $EIFFEL_SRC/Eiffel/Ace:
* batch.mswin.ace
* newbench.mswin.ace
* batch.unix.ace
* newbench.linux.ace
The first two are for windows, the last two for unix (even if the last one says `linux').

To compile simply do:
<pre>ec -ace <chosen_ace_file> -c_compile</pre>

Please note: the 'ec' binary produced by the newbench .ace file contains the full Eiffel compiler, including the batch version. 'estudio' is just a wrapper (available in Src/bench/C/ipc/daemon). So, you need either the one or the other.

===Windows specific===

At the end of the compilation for the workbench version, the C compilation will fail reporting an undefined reference to `nbref'. This is because the ace file has been built for the finalized version of EiffelStudio not the workbench version. To fix this problem do the following:
<pre>copy ec.lnk h</pre>
Then edit the file `h' and replace '''mtcompiler.lib''' by '''mtwcompiler.lib'''.
Once this is done you can complete you do:
<pre>link @h</pre>
In order to update to the new version of metadata consumer tool, follow the instructions described [[Compiling Metadata Consumer|here]].

===Unix specific===

Like the windows version the C compilation, it will fail, but this time for two reasons:
* nbref
* linking order causing many errors to be reported

Here is the recommended way, make a copy of the generated Makefile and put it at the same level as your EIFGEN directory. Edit it and replace '''libmtcompiler.a''' by '''libmtwcompiler.a''', then search for "$(EXTERNALS) $(EIFLIB)" and replace it by "$(EIFLIB) $(EXTERNALS)". Once this is done, you can do:
<pre>make -f ../../Makefile</pre>

A little script that does the necessary changes: Place it at the same level as the EIFGEN directory is.

<code>[bash,N]
#!/bin/bash

cp EIFGEN/W_code/Makefile .
sed 's/libmtcompiler\.a/libmtwcompiler\.a/g' Makefile > tmp
sed 's/\$(EXTERNALS) \$(EIFLIB)/\$$EIFLIB$ \$$EXTERNALS$/g' tmp > Makefile
cd EIFGEN/W_code
make -f ../../Makefile
</code>

'''Note:''' These changes are not required if you try to compile a finalized version of EiffelStudio, but only if you want to create a workbench version of EiffelStudio for development and debugging.

Also, if you encounter problems with your self-compiled version of EiffelStudio, you might try to compile it with GCC 3.x. Version 4 of GCC has a slight change in semantics and EiffelStudio has not been updated. You can see the change in behavior in the following code:

<code>[C,N]
#include <stdio.h>

int a;
int b;
int *pointer;

int foo()
{
pointer = &b;
return 4;
}

int main (int argc, char** argv)
{
a = 3;
b = 0;

pointer = &a;

*pointer = foo();

printf ("You are using GCC %d.%d\n",a,b);
return 0;
}
</code>

===Mac OS X specific===

The basic steps are:
* compile it under linux (as described above, but finalize with ec -ace <chosen_ace_file> -finalize -c_compile)
* copy the F_Code directory to the mac (and build the whole source arround it... so that it almost looks like under linux).
* compile it there using make (compile all the dependencies as described above, then try to compile ... & ok change a lot of stuff in the Makefile.SH's or do it otherwise! )
* fix whatever problems appear

for more information : try the experimental release from http://eiffelsoftware.origo.ethz.ch/downloads/porting/ and have a look at the basher.sh - skript

You can get the F_code build under Linux with gcc-3.3 and gtk2.8.17 (same as available under darwin ports) here [24.04.06]: http://n.ethz.ch/student/dfurrer/files/f_code.tar.gz

still todo : script to generate a working environement for EiffelStudio

note : it seems to be neccessary to install gtk-2.6 if you want to build a working environement for EiffelStudio (neccessary for some vision2-libraries)

a first (binary) experimental releas is available from http://eiffelsoftware.origo.ethz.ch/downloads/builds/experimental/

Automatic Build Scripts

2006-04-25T06:56:56Z

Bayt: /* Windows */

[[Category:Compiler]]
[[Category:EiffelStudio]]
This page references different build scripts that automate the process of building EiffelStudio.

== Windows ==

Bernardo Buss created a set of scripts for the automated compilation of EiffelStudio under Windows.
* Script: http://homepage.hispeed.ch/barnski/EiffelStudio_batch_files.zip
* Announcement: http://origo.ethz.ch/pipermail/es-devel/2006-April/000052.html
Updated "2_checkout_dev.bat" according to [[Compiling_EiffelStudio#Checking_out_from_SVN|Checking out from SVN]]. 
'''Note:''' 
* Additionally there is the checkout for two delivery paths, which are necessary for building the Delivery after compilation.
* You may need to keep "2_checkout_dev.bat" up to date by yourself according to [[Compiling_EiffelStudio#Checking_out_from_SVN|Checking out from SVN]].

== Linux ==

Bernd Schoeller has developed a build script available for download at http://se.inf.ethz.ch/people/schoeller/download/build-studio

This script requires a single checkout from the SVN repository (with the EIFFEL_SVN environment variable pointing to it). It will compile the bench or the batch compiler (you need to modify the script for the second).

== Mac OSX ==

None yet.

Compiling EiffelStudio

2006-04-25T06:54:17Z

Bayt: /* Compilation methods */

[[Category:Compiler]]
[[Category:EiffelStudio]]

== Installing EiffelStudio ==

To compile EiffelStudio, you need an already working EiffelStudio compiler on your machine. The current source tree '''requires at least version 5.7''' of EiffelStudio. You can download it from http://eiffelsoftware.origo.ethz.ch/downloads/builds/. This version still requires a registration (we missed to remove the registration cluster while compiling). You need to '''activate''' EiffelStudio (see below), because in some cases the compiler won't work correctly if not activated. [[Installing EiffelStudio]] is covered in its own article.

'''Note:''' on Windows you will need the Microsoft C compiler to compile Eiffel Studio. How to install the free version of the Microsoft C compiler: [[Installing Microsoft C compiler]]

===Compilation methods===
Currently there are two compilation methods.
* You can use one of the [[Automatic Build Scripts]]
* Alternatively you can compile EiffelStudio from scratch following the instructions in this document.

If possible, use the [[Automatic Build Scripts]] and report any errors to the [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-devel developer mailing list].

==Extracting source code==

===Checking out from SVN===
#Point an environment variable called '''EIFFEL_SRC''' to the directory where you want to compile EiffelStudio Usually we use the '''XXdev''' convention for this directory name - where XX is the version number from the current developped version of the compiler.
#Make sure that '''ISE_EIFFEL''', '''ISE_PLATFORM''' and '''ISE_C_COMPILER''' (on windows only) are properly defined
#Perform the following checkout procedures:

'''DOS'''
<pre>
set SVNURL=https://eiffelsoftware.origo.ethz.ch/svn/es
svn co %SVNURL%/trunk/Src 57dev
svn co %SVNURL%/trunk/Delivery 57dev/Delivery
svn co %SVNURL%/trunk/free_add_ons 57dev/free_add_ons
</pre>

'''Bash'''
<pre>
export SVNURL=https://eiffelsoftware.origo.ethz.ch/svn/es
svn co $SVNURL/trunk/Src 57dev
svn co $SVNURL/trunk/Delivery 57dev/Delivery
svn co $SVNURL/trunk/free_add_ons 57dev/free_add_ons
</pre>

To update the sourcefiles to the latest revision, perform the following steps:

'''Bash and DOS'''
<pre>
cd 57dev
svn up
svn up free_add_ons
svn up Delivery
</pre>

==Installing gobo==

Please make sure to use the version provided or the very latest version from CVS. All other versions (including the official 3.4 release) will not work because of name clashes in the UC_STRING class between GOBO and EiffelStudio. 
As the anonymous CVS on sourceforge is currently broken, use the following link from the gobo newsgroup to get the [http://www.gobosoft.com/download/gobo-cvs-060418.zip CVS-checkout of 18.April].

===Windows specific===

You have to unzip the gobo distribution from $EIFFEL_SRC/free_add_ons/gobo/gobo_34_win.tgz and extract it into $EIFFEL_SRC/library.

===Unix specific===

You have to unzip the gobo distribution from $EIFFEL_SRC/free_add_ons/gobo/gobo_34_unix.tgz and extract it into $EIFFEL_SRC/library. Here is the list of commands to do this:
<pre>cd $EIFFEL_SRC/library
tar -xvzf $EIFFEL_SRC/free_add_ons/gobo/gobo_34_unix.tgz
</pre>

==Compiling C libraries==

===Compiling run-time on Windows===

Before being able to compile the run-time, you need to ensure that '''bash''' is in your '''PATH'''. You can download it from [http://www.cygwin.com http://www.cygwin.com]. Also make sure, that the path to the binaries of your c compiler is placed before the path to cygwin or else the wrong linker will be used. Once done you can do:

'''DOS'''
<pre>cd %EIFFEL_SRC%/C
configure [win32|win64] [b|m]</pre>

'''Bash'''
<pre>cd $EIFFEL_SRC/C
./configure.bat [win32|win64] [b|m]</pre>

The first argument indicated whether you are compiling the run-time for 32 or 64 bits. The second one is to tell which C compiler will be used. For now only `b' (Borland) and `m' (Microsoft) are officially supported. We also informally support `g' (GCC) and `l' (LCC).

On Windows 32 bits to clean up all the generated files you do:

'''DOS'''
<pre>configure clean</pre>
'''Bash'''
<pre>./configure.bat clean</pre>

On Windows 64 bits, you do:
<pre>configure cleand</pre>

===Compiling run-time on Unix===

The command is simply:
<pre>cd $EIFFEL_SRC/C
./quick_configure</pre>
This requires that '''ISE_PLATFORM''' is properly defined. The `quick_configure' script will look for the file CONFIGS/$ISE_PLATFORM and use it to extract the platform specific information to compile the run-time. If not found then an error will be reported.

===Compiling C code from libraries===

Here is the list of commands to compile all required C libraries on Windows:

'''DOS'''
<pre>cd %EIFFEL_SRC%/library/net/Clib
make_msc.bat
cd %EIFFEL_SRC%/library/vision2/Clib
make_msc.bat
cd %EIFFEL_SRC%/library/wel/Clib
make_msc.bat</pre>
'''Bash'''
<pre>cd $EIFFEL_SRC/library/net/Clib
./make_msc.bat
cd $EIFFEL_SRC/library/vision2/Clib
./make_msc.bat
cd $EIFFEL_SRC/library/wel/Clib
./make_msc.bat</pre>

On Unix it is slightly different:
<pre>cd $EIFFEL_SRC/library/event/Clib
finish_freezing -library
cd $EIFFEL_SRC/library/net/Clib
finish_freezing -library
cd $EIFFEL_SRC/library/vision2/Clib
finish_freezing -library
cd $EIFFEL_SRC/library/vision2/implementation/gtk/Clib
finish_freezing -library</pre>

Make sure that '''ISE_EIFFEL''' is set correctly to your current "EiffelStudio" installation!

===Compiling C code from C_library===

This is only required on Windows to read PNG file. On Unix, this is not required because it is included in GTK+2.4. Simply do the following:

'''DOS'''
<pre>cd %EIFFEL_SRC%/C_library/zlib
make_msc.bat
cd %EIFFEL_SRC%/C_library/libpng
make_msc.bat</pre>
'''Bash'''
<pre>cd $EIFFEL_SRC/C_library/zlib
./make_msc.bat
cd $EIFFEL_SRC/C_library/libpng
./make_msc.bat</pre>

===Compiling C code from compiler===

This is only required on Windows as this C code is a tiny wrapper around the Microsoft C++ API to generate and to debug .NET code.

To compile it, you first need to install the Microsoft .NET SDK. You can download it from their website.

After installing it, you need to update your '''LIB''' and '''INCLUDE''' environment variable to include the path the lib and include directory of the .NET Framework SDK.

Once properly installed, you can do:

'''DOS'''
<pre>cd %EIFFEL_SRC%/Eiffel/library/cli_writer/Clib
nmake</pre>
'''Bash'''
<pre>cd $EIFFEL_SRC/Eiffel/library/cli_writer/Clib
nmake</pre>

==Compiling EiffelStudio==

Now that we have taken care of the C code compilation we can compile the compiler. There are four ace files in $EIFFEL_SRC/Eiffel/Ace:
* batch.mswin.ace
* newbench.mswin.ace
* batch.unix.ace
* newbench.linux.ace
The first two are for windows, the last two for unix (even if the last one says `linux').

To compile simply do:
<pre>ec -ace <chosen_ace_file> -c_compile</pre>

Please note: the 'ec' binary produced by the newbench .ace file contains the full Eiffel compiler, including the batch version. 'estudio' is just a wrapper (available in Src/bench/C/ipc/daemon). So, you need either the one or the other.

===Windows specific===

At the end of the compilation for the workbench version, the C compilation will fail reporting an undefined reference to `nbref'. This is because the ace file has been built for the finalized version of EiffelStudio not the workbench version. To fix this problem do the following:
<pre>copy ec.lnk h</pre>
Then edit the file `h' and replace '''mtcompiler.lib''' by '''mtwcompiler.lib'''.
Once this is done you can complete you do:
<pre>link @h</pre>
In order to update to the new version of metadata consumer tool, follow the instructions described [[Compiling Metadata Consumer|here]].

===Unix specific===

Like the windows version the C compilation, it will fail, but this time for two reasons:
* nbref
* linking order causing many errors to be reported

Here is the recommended way, make a copy of the generated Makefile and put it at the same level as your EIFGEN directory. Edit it and replace '''libmtcompiler.a''' by '''libmtwcompiler.a''', then search for "$(EXTERNALS) $(EIFLIB)" and replace it by "$(EIFLIB) $(EXTERNALS)". Once this is done, you can do:
<pre>make -f ../../Makefile</pre>

A little script that does the necessary changes: Place it at the same level as the EIFGEN directory is.

<code>[bash,N]
#!/bin/bash

cp EIFGEN/W_code/Makefile .
sed 's/libmtcompiler\.a/libmtwcompiler\.a/g' Makefile > tmp
sed 's/\$(EXTERNALS) \$(EIFLIB)/\$$EIFLIB$ \$$EXTERNALS$/g' tmp > Makefile
cd EIFGEN/W_code
make -f ../../Makefile
</code>

'''Note:''' These changes are not required if you try to compile a finalized version of EiffelStudio, but only if you want to create a workbench version of EiffelStudio for development and debugging.

Also, if you encounter problems with your self-compiled version of EiffelStudio, you might try to compile it with GCC 3.x. Version 4 of GCC has a slight change in semantics and EiffelStudio has not been updated. You can see the change in behavior in the following code:

<code>[C,N]
#include <stdio.h>

int a;
int b;
int *pointer;

int foo()
{
pointer = &b;
return 4;
}

int main (int argc, char** argv)
{
a = 3;
b = 0;

pointer = &a;

*pointer = foo();

printf ("You are using GCC %d.%d\n",a,b);
return 0;
}
</code>

===Mac OS X specific===

The basic steps are:
* compile it under linux (as described above, but finalize with ec -ace <chosen_ace_file> -finalize -c_compile)
* copy the F_Code directory to the mac (and build the whole source arround it... so that it almost looks like under linux).
* compile it there using make (compile all the dependencies as described above, then try to compile ... & ok change a lot of stuff in the Makefile.SH's or do it otherwise! )
* fix whatever problems appear

for more information : try the experimental release from http://eiffelsoftware.origo.ethz.ch/downloads/porting/ and have a look at the basher.sh - skript

You can get the F_code build under Linux with gcc-3.3 and gtk2.8.17 (same as available under darwin ports) here [24.04.06]: http://n.ethz.ch/student/dfurrer/files/f_code.tar.gz

still todo : script to generate a working environement for EiffelStudio

note : it seems to be neccessary to install gtk-2.6 if you want to build a working environement for EiffelStudio (neccessary for some vision2-libraries)

a first (binary) experimental releas is available from http://eiffelsoftware.origo.ethz.ch/downloads/builds/experimental/

Compiling EiffelStudio

2006-04-25T06:51:39Z

Bayt: /* Compilation methods */ typo

[[Category:Compiler]]
[[Category:EiffelStudio]]

== Installing EiffelStudio ==

To compile EiffelStudio, you need an already working EiffelStudio compiler on your machine. The current source tree '''requires at least version 5.7''' of EiffelStudio. You can download it from http://eiffelsoftware.origo.ethz.ch/downloads/builds/. This version still requires a registration (we missed to remove the registration cluster while compiling). You need to '''activate''' EiffelStudio (see below), because in some cases the compiler won't work correctly if not activated. [[Installing EiffelStudio]] is covered in its own article.

'''Note:''' on Windows you will need the Microsoft C compiler to compile Eiffel Studio. How to install the free version of the Microsoft C compiler: [[Installing Microsoft C compiler]]

===Compilation methods===
Currently there are two compilation methods.
* You can either compile EiffelStudio from scratch following the instructions in this document.
* Alternatively you can use one of the [[Automatic Build Scripts]]
If possible, use the compilation script and report any errors to the developer mailing list.

==Extracting source code==

===Checking out from SVN===
#Point an environment variable called '''EIFFEL_SRC''' to the directory where you want to compile EiffelStudio Usually we use the '''XXdev''' convention for this directory name - where XX is the version number from the current developped version of the compiler.
#Make sure that '''ISE_EIFFEL''', '''ISE_PLATFORM''' and '''ISE_C_COMPILER''' (on windows only) are properly defined
#Perform the following checkout procedures:

'''DOS'''
<pre>
set SVNURL=https://eiffelsoftware.origo.ethz.ch/svn/es
svn co %SVNURL%/trunk/Src 57dev
svn co %SVNURL%/trunk/Delivery 57dev/Delivery
svn co %SVNURL%/trunk/free_add_ons 57dev/free_add_ons
</pre>

'''Bash'''
<pre>
export SVNURL=https://eiffelsoftware.origo.ethz.ch/svn/es
svn co $SVNURL/trunk/Src 57dev
svn co $SVNURL/trunk/Delivery 57dev/Delivery
svn co $SVNURL/trunk/free_add_ons 57dev/free_add_ons
</pre>

To update the sourcefiles to the latest revision, perform the following steps:

'''Bash and DOS'''
<pre>
cd 57dev
svn up
svn up free_add_ons
svn up Delivery
</pre>

==Installing gobo==

Please make sure to use the version provided or the very latest version from CVS. All other versions (including the official 3.4 release) will not work because of name clashes in the UC_STRING class between GOBO and EiffelStudio. 
As the anonymous CVS on sourceforge is currently broken, use the following link from the gobo newsgroup to get the [http://www.gobosoft.com/download/gobo-cvs-060418.zip CVS-checkout of 18.April].

===Windows specific===

You have to unzip the gobo distribution from $EIFFEL_SRC/free_add_ons/gobo/gobo_34_win.tgz and extract it into $EIFFEL_SRC/library.

===Unix specific===

You have to unzip the gobo distribution from $EIFFEL_SRC/free_add_ons/gobo/gobo_34_unix.tgz and extract it into $EIFFEL_SRC/library. Here is the list of commands to do this:
<pre>cd $EIFFEL_SRC/library
tar -xvzf $EIFFEL_SRC/free_add_ons/gobo/gobo_34_unix.tgz
</pre>

==Compiling C libraries==

===Compiling run-time on Windows===

Before being able to compile the run-time, you need to ensure that '''bash''' is in your '''PATH'''. You can download it from [http://www.cygwin.com http://www.cygwin.com]. Also make sure, that the path to the binaries of your c compiler is placed before the path to cygwin or else the wrong linker will be used. Once done you can do:

'''DOS'''
<pre>cd %EIFFEL_SRC%/C
configure [win32|win64] [b|m]</pre>

'''Bash'''
<pre>cd $EIFFEL_SRC/C
./configure.bat [win32|win64] [b|m]</pre>

The first argument indicated whether you are compiling the run-time for 32 or 64 bits. The second one is to tell which C compiler will be used. For now only `b' (Borland) and `m' (Microsoft) are officially supported. We also informally support `g' (GCC) and `l' (LCC).

On Windows 32 bits to clean up all the generated files you do:

'''DOS'''
<pre>configure clean</pre>
'''Bash'''
<pre>./configure.bat clean</pre>

On Windows 64 bits, you do:
<pre>configure cleand</pre>

===Compiling run-time on Unix===

The command is simply:
<pre>cd $EIFFEL_SRC/C
./quick_configure</pre>
This requires that '''ISE_PLATFORM''' is properly defined. The `quick_configure' script will look for the file CONFIGS/$ISE_PLATFORM and use it to extract the platform specific information to compile the run-time. If not found then an error will be reported.

===Compiling C code from libraries===

Here is the list of commands to compile all required C libraries on Windows:

'''DOS'''
<pre>cd %EIFFEL_SRC%/library/net/Clib
make_msc.bat
cd %EIFFEL_SRC%/library/vision2/Clib
make_msc.bat
cd %EIFFEL_SRC%/library/wel/Clib
make_msc.bat</pre>
'''Bash'''
<pre>cd $EIFFEL_SRC/library/net/Clib
./make_msc.bat
cd $EIFFEL_SRC/library/vision2/Clib
./make_msc.bat
cd $EIFFEL_SRC/library/wel/Clib
./make_msc.bat</pre>

On Unix it is slightly different:
<pre>cd $EIFFEL_SRC/library/event/Clib
finish_freezing -library
cd $EIFFEL_SRC/library/net/Clib
finish_freezing -library
cd $EIFFEL_SRC/library/vision2/Clib
finish_freezing -library
cd $EIFFEL_SRC/library/vision2/implementation/gtk/Clib
finish_freezing -library</pre>

Make sure that '''ISE_EIFFEL''' is set correctly to your current "EiffelStudio" installation!

===Compiling C code from C_library===

This is only required on Windows to read PNG file. On Unix, this is not required because it is included in GTK+2.4. Simply do the following:

'''DOS'''
<pre>cd %EIFFEL_SRC%/C_library/zlib
make_msc.bat
cd %EIFFEL_SRC%/C_library/libpng
make_msc.bat</pre>
'''Bash'''
<pre>cd $EIFFEL_SRC/C_library/zlib
./make_msc.bat
cd $EIFFEL_SRC/C_library/libpng
./make_msc.bat</pre>

===Compiling C code from compiler===

This is only required on Windows as this C code is a tiny wrapper around the Microsoft C++ API to generate and to debug .NET code.

To compile it, you first need to install the Microsoft .NET SDK. You can download it from their website.

After installing it, you need to update your '''LIB''' and '''INCLUDE''' environment variable to include the path the lib and include directory of the .NET Framework SDK.

Once properly installed, you can do:

'''DOS'''
<pre>cd %EIFFEL_SRC%/Eiffel/library/cli_writer/Clib
nmake</pre>
'''Bash'''
<pre>cd $EIFFEL_SRC/Eiffel/library/cli_writer/Clib
nmake</pre>

==Compiling EiffelStudio==

Now that we have taken care of the C code compilation we can compile the compiler. There are four ace files in $EIFFEL_SRC/Eiffel/Ace:
* batch.mswin.ace
* newbench.mswin.ace
* batch.unix.ace
* newbench.linux.ace
The first two are for windows, the last two for unix (even if the last one says `linux').

To compile simply do:
<pre>ec -ace <chosen_ace_file> -c_compile</pre>

Please note: the 'ec' binary produced by the newbench .ace file contains the full Eiffel compiler, including the batch version. 'estudio' is just a wrapper (available in Src/bench/C/ipc/daemon). So, you need either the one or the other.

===Windows specific===

At the end of the compilation for the workbench version, the C compilation will fail reporting an undefined reference to `nbref'. This is because the ace file has been built for the finalized version of EiffelStudio not the workbench version. To fix this problem do the following:
<pre>copy ec.lnk h</pre>
Then edit the file `h' and replace '''mtcompiler.lib''' by '''mtwcompiler.lib'''.
Once this is done you can complete you do:
<pre>link @h</pre>
In order to update to the new version of metadata consumer tool, follow the instructions described [[Compiling Metadata Consumer|here]].

===Unix specific===

Like the windows version the C compilation, it will fail, but this time for two reasons:
* nbref
* linking order causing many errors to be reported

Here is the recommended way, make a copy of the generated Makefile and put it at the same level as your EIFGEN directory. Edit it and replace '''libmtcompiler.a''' by '''libmtwcompiler.a''', then search for "$(EXTERNALS) $(EIFLIB)" and replace it by "$(EIFLIB) $(EXTERNALS)". Once this is done, you can do:
<pre>make -f ../../Makefile</pre>

A little script that does the necessary changes: Place it at the same level as the EIFGEN directory is.

<code>[bash,N]
#!/bin/bash

cp EIFGEN/W_code/Makefile .
sed 's/libmtcompiler\.a/libmtwcompiler\.a/g' Makefile > tmp
sed 's/\$(EXTERNALS) \$(EIFLIB)/\$$EIFLIB$ \$$EXTERNALS$/g' tmp > Makefile
cd EIFGEN/W_code
make -f ../../Makefile
</code>

'''Note:''' These changes are not required if you try to compile a finalized version of EiffelStudio, but only if you want to create a workbench version of EiffelStudio for development and debugging.

Also, if you encounter problems with your self-compiled version of EiffelStudio, you might try to compile it with GCC 3.x. Version 4 of GCC has a slight change in semantics and EiffelStudio has not been updated. You can see the change in behavior in the following code:

<code>[C,N]
#include <stdio.h>

int a;
int b;
int *pointer;

int foo()
{
pointer = &b;
return 4;
}

int main (int argc, char** argv)
{
a = 3;
b = 0;

pointer = &a;

*pointer = foo();

printf ("You are using GCC %d.%d\n",a,b);
return 0;
}
</code>

===Mac OS X specific===

The basic steps are:
* compile it under linux (as described above, but finalize with ec -ace <chosen_ace_file> -finalize -c_compile)
* copy the F_Code directory to the mac (and build the whole source arround it... so that it almost looks like under linux).
* compile it there using make (compile all the dependencies as described above, then try to compile ... & ok change a lot of stuff in the Makefile.SH's or do it otherwise! )
* fix whatever problems appear

for more information : try the experimental release from http://eiffelsoftware.origo.ethz.ch/downloads/porting/ and have a look at the basher.sh - skript

You can get the F_code build under Linux with gcc-3.3 and gtk2.8.17 (same as available under darwin ports) here [24.04.06]: http://n.ethz.ch/student/dfurrer/files/f_code.tar.gz

still todo : script to generate a working environement for EiffelStudio

note : it seems to be neccessary to install gtk-2.6 if you want to build a working environement for EiffelStudio (neccessary for some vision2-libraries)

a first (binary) experimental releas is available from http://eiffelsoftware.origo.ethz.ch/downloads/builds/experimental/

TODOs

2006-04-24T06:42:49Z

Bayt: updated todo's

[[Category:TODOs]]
Here is the list TODOs for the entire project buildup:

* create SA branch (responsible: [[User:Schoelle| Bernd]])
* Design new EiffelStudio logo (responsible: [[User:Bayt| Bayt]])
** done, waiting for feedback
** Replace favicon of page with logo (responsible: [[User:Bayt| Bayt]])
* Get valid ssl certificate from Switch (responsible: [[User:Bayt| Bayt]])
** assigned to [[User:Luc| Luc]]
* Migration of yahoogroup mailinglist here after EiffelWorld newsletter (responsible: [[User:Luc| Luc]])
** Give list of subscribed people to [[User:Luc| Luc]] (responsible: [[User:Manus| Manus]])
* Automatic build scripts (responsible: [[User:Schoelle| Bernd]]) and coordinate with [[User:Baumanda| Daniel]] for Debian uploads.

Multi screen support

2006-04-21T14:04:17Z

Bayt: typos

[[Category:Projects]]
[[Category:EiffelVision2]]

=Overview=
The aim of this project is to enhance Vision with a support for multiple screens.

=Milestones=

==M1: April 25th==

==M2: May ??? ==
* To be completed by the team

=Team=

Everyone interested in this project is welcome to join our mailinglist [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-ui| es-ui@origo.ethz.ch]

* TODO add project leader (Project leader)
* TODO add project members
* [[User:Serafin| Serafin]]
* [[User:Bayt| Bayt]]

Folding support

2006-04-21T07:56:27Z

Bayt: typo

[[Category:Projects]]
[[Category:EiffelVision2]]

=Overview=
The aim of this project is to enhance Vision with a RichText control that supports folding. The goal is to make this surface in the editor windows of EiffelStudio.

=Milestones=

==M1: April 25th==

==M2: May ??? ==
* implement support for word wrapping
* To be completed by the team

=Team=

Everyone intrested in this project is welcome to join our mailinglist [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-ui es-ui@origo.ethz.ch]

* [[User:Sanakan| Sanakan]] (Project leader)
* TODO add 2nd project leader Mario Deuss (Project leader)
* TODO add project members
* [[User:Exception| Exception]]
* [[User:Panarium| Panarium]]
* [[User:Bayt| Bayt]]

EiffelVision accelerators

2006-04-21T07:54:47Z

Bayt:

[[Category:EiffelVision2]]
[[Category:Projects]]

The EiffelVision2 accelerator addition Wiki page.

== Overview ==
This page discusses the initial design of a new shortcut propagation mechanism that may be built into EiffelVision 2. The initial requirement indicated that a widget should be able to handle a shortcut accelerator and execute an action. If a widget does not handle the shortcut, the shortcut key combination will be propagate to the parent contain. This process continues until either a shortcut has been handled or the top-level windows has been reached, in which case there is no parent widget.

== Proposal ==
During a design meeting a number of designed were proffered as designs that could be used at the EV_WIDGET level. However, through a process of elimination and evolution a design was decided upon that is simple, backwards compatible and whose interface is more akin to EiffelVision 2 action sequences used to date. The design of the interface proved important to provide backwards compatibility.

For this proposal to correctly function it is imperative that the widget who recieved focused last be given initial rights to process an accelerator key combination. The widget will then handle any unhandled accelerator key combinations by propagating it to a parent container.

It is proposed that an action sequence, similar to the action sequence for accelerators on EV_APPLICATION, be added to EV_WIDGET or EV_WIDGET_I (interface). Adding to the interface is preferable to prevent code duplication for each supported platform. EV_WIDGET(_I) would also host a feature that is responsible for receiving an accelerator key combination, for the sake of reference it will be called `process_accelerator'. `process_accelerator' will iterate the accelerator action sequence to determine if any item in the sequence matches the accelerator key combination passed to `process_accelerator'. If there is a match then agents on the action sequence item (presumably EV_ACCELERATOR) will be executed.

For propagation, the initial requirement is that any unhandled shortcut be propagated to a widget's parent container. In this case the simple detection of an item in the accelerator action sequence, on the widget, that matches the accelerator key combination passed to `process_accelerator' would suffice. However, users may want to force propagation.

The proposed solution is to extend EV_ACCELERATOR, either by adding to EV_ACCELERATOR or through sub-classing, with a propagate state flag. Again for the sake of reference it will be called `propagate_accelerator'. Clients would simple set `propagate_accelerator' if they wanted to propagate the accelerator to parent widget container.

With the addition of `propagate_accelerator' on the widget's accelerator action sequence, `process_accelerator' could have to check the state flag of any applicable accelerator action sequence item to determine if the accelerator should be propagate. The state flag should be logically OR-ed so that multiple accelerator action sequence items, matching the passed accelerator key combination to `process_accelerator', will propagate the accelerator if one item requests propagation. Failure to find an item in the accelerator action sequence should remain an cause to propagate the accelerator to the widget's parent container.

== The Proposed Design ==
As stated, the design is simple.

class EV_WIDGET_I

-- class features elided for clarity.

feature -- Agents

accelerator_actions: EV_NOTIFY_ACTION_SEQUENCE
-- Accelerator actions for `Current' widget

feature {EV_WIDGET} -- Propagation

process_accelerator (a_accl: EV_ACCELERATROR) is
-- Process actions for accelerator `a_accl'.
require
a_accl_attached: a_accl /= Void
do
-- Loop through `accelerator_actions'.
-- If an accelerator matches `a_accl' call action sequence on accelerator.
-- Query the accelerator item in the `accelerator_actions' for the `propagate_accelerator' state flag
-- Locigally or `propagate_accelerator' with locally scoped state flag (`should_prop').

-- After loop has completed, examine `should_prop'.
-- If true or no accelerator was found call parent widget's `process_accelerator'
end

end -- class EV_WIDGET_I

The proposed design does require a change in EV_ACCELERATOR. It was discussed if EV_ACCELERATOR should be descended and specialized, but instead EV_APPLICATION will receive a new attribute and assigner - `propagate_accelerator' and `propagate_accelerator'

class EV_ACCELERATOR

-- class features elided for clarity.

feature -- Access

propagate_accelerator: BOOLEAN assign set_propagate_accelerator
-- Should accelerator be propagated to parent widgets?

feature -- Status Setting

enable_propagation is
-- Enable accelerator to be propagated to parent containers.
do
propagate_accelerator := True
ensure
propagate_accelerator_set: propagate_accelerator = True
end

disable_propagation is
-- Prevent accelerator to be propagated to parent containers.
do
propagate_accelerator := False
ensure
propagate_accelerator_set: propagate_accelerator = False
end

end -- class EV_ACCELERATOR

By the proposed design any existing application using EV_ACCELERATORs on an EV_APPLICATION should not be affected. Instead, now, of the top-level window receiving notification the last focused widget will handle the accelerator. If the widget does not handle the accelerator or the accelerator should be propagated, then the parent widget's implementation is executed. Existing developed application do not yet know about shortcut propagation so the accelerator will be propagated back until it reaches the top-level window, which as an end result exhibits the same behavior.

=Milestones=

==M1: April 25th==

==M2: May ??? ==
* To be completed by the team

=Team=

Everyone intrested in this project is welcome to join our mailinglist [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-vision es-vision@origo.ethz.ch]

* TODO add project leader (Project leader)
* TODO add project members
* [[User:Bayt| Bayt]]

Syntax checking

2006-04-21T07:48:10Z

Bayt: Mailinglist created

[[Category:Projects]]
[[Category:Editor]]

=Overview=
The aim of this project is to have a syntax checking done as you type.
Syntax errors should be highlited and eventualy also options for correcting the error should be propossed.

=Milestones=

==M1: April 25th==

==M2: May ??? ==
* To be completed by the team

=Team=
* [[User:jabernet| Janick Bernet]] (big boss and scapegoat)
* [[User:maser| Martin Luder]]
* [[User:clerco| Olivier Clerc]]

Everyone intrested in this project is welcome to join our mailinglist [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-ui| es-ui@origo.ethz.ch]

* TODO add project leader
* TODO add project members
* [[User:FoB| Stephan Classen]]

Multi screen support

2006-04-21T07:47:39Z

Bayt: Mailinglist created

[[Category:Projects]]
[[Category:EiffelVision2]]

=Overview=
The aim of this project is to enhance Vision with a support for multiple screens.

=Milestones=

==M1: April 25th==

==M2: May ??? ==
* To be completed by the team

=Team=

Everyone intrested in this project is welcome to join our mailinglist [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-ui| es-ui@origo.ethz.ch]

* TODO add project leader Mario Deuss (Project leader)
* TODO add project members
* [[User:Serafin| Serafin]]
* [[User:Bayt| Bayt]]

Folding support

2006-04-21T07:47:06Z

Bayt: Mailinglist created

[[Category:Projects]]
[[Category:EiffelVision2]]

=Overview=
The aim of this project is to enhance Vision with a RichText control that supports folding. The goal is to make this surface in the editor windows of EiffelStudio.

=Milestones=

==M1: April 25th==

==M2: May ??? ==
* implement support for word wrapping
* To be completed by the team

=Team=

Everyone intrested in this project is welcome to join our mailinglist [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-ui| es-ui@origo.ethz.ch]

* [[User:Sanakan| Sanakan]] (Project leader)
* TODO add 2nd project leader Mario Deuss (Project leader)
* TODO add project members
* [[User:Exception| Exception]]
* [[User:Panarium| Panarium]]
* [[User:Bayt| Bayt]]

Vision2 and Unicode

2006-04-21T07:46:34Z

Bayt: Mailinglist created

[[Category:EiffelVision2]]
[[Category:Projects]]
[[Category:Unicode]]

=Introduction=
Have a look at the [[WEL_and_Unicode|description made for the WEL library]]. The same applies to EiffelVision2.

=Readings=

==Unicode==
* http://de.wikipedia.org/wiki/Unicode
* http://www.unicode.org/
** http://www.unicode.org/standard/WhatIsUnicode.html
** http://www.unicode.org/standard/standard.html

=Milestones=

==M1: April 25th==

==M2: May ??? ==
* implement multi screen support for Vision: [[Multi screen support]]
* collaborate with the internationalization team (TODO add link to their project page)
* write a decent STRING_32 implementation for
** string comparisons
** lower/upper case conversion
** some of it is already in Gobo but not completely as efficient as it should
* To be completed by the team

=Team=

Everyone intrested in this project is welcome to join our mailinglist [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-vision| es-vision@origo.ethz.ch]

* Project Leader: Raffaele
* [[User:Serafin| Serafin]]
* [[User:Bayt| Bayt]]

=Communication=
We agreed to communicate via [http://de.wikipedia.org/wiki/Irc IRC] (orwell.freenode.net/es-vision).
For Windows user there are different programs available. For example:
* [http://hydrairc.com/index.php?page=downloads HydraIRC]
* [http://www.mirc.com/get.html mirc]

Linux user (for ex.) one of the following
* xchat
* irssi (console-app.)

after downloading and installing, you can connect to a server with the command
<pre>
/server <serveradress>
</pre>
where <serveradress> is (for ex.) orwell.freenode.net ([http://freenode.net/irc_servers.shtml more freenode servers]).

to enter our channel, type:
<pre>
/join #es-vision
</pre>

also you can set/change your nickname with
<pre>
/nick <new_nick>
</pre>
where <new_nick> is you nickname.

EiffelVision accelerators

2006-04-21T07:45:27Z

Bayt: Mailinglist created

[[Category:EiffelVision2]]
[[Category:Projects]]

The EiffelVision2 accelerator addition Wiki page.

== Overview ==
This page discusses the initial design of a new shortcut propagation mechanism that may be built into EiffelVision 2. The initial requirement indicated that a widget should be able to handle a shortcut accelerator and execute an action. If a widget does not handle the shortcut, the shortcut key combination will be propagate to the parent contain. This process continues until either a shortcut has been handled or the top-level windows has been reached, in which case there is no parent widget.

== Proposal ==
During a design meeting a number of designed were proffered as designs that could be used at the EV_WIDGET level. However, through a process of elimination and evolution a design was decided upon that is simple, backwards compatible and whose interface is more akin to EiffelVision 2 action sequences used to date. The design of the interface proved important to provide backwards compatibility.

For this proposal to correctly function it is imperative that the widget who recieved focused last be given initial rights to process an accelerator key combination. The widget will then handle any unhandled accelerator key combinations by propagating it to a parent container.

It is proposed that an action sequence, similar to the action sequence for accelerators on EV_APPLICATION, be added to EV_WIDGET or EV_WIDGET_I (interface). Adding to the interface is preferable to prevent code duplication for each supported platform. EV_WIDGET(_I) would also host a feature that is responsible for receiving an accelerator key combination, for the sake of reference it will be called `process_accelerator'. `process_accelerator' will iterate the accelerator action sequence to determine if any item in the sequence matches the accelerator key combination passed to `process_accelerator'. If there is a match then agents on the action sequence item (presumably EV_ACCELERATOR) will be executed.

For propagation, the initial requirement is that any unhandled shortcut be propagated to a widget's parent container. In this case the simple detection of an item in the accelerator action sequence, on the widget, that matches the accelerator key combination passed to `process_accelerator' would suffice. However, users may want to force propagation.

The proposed solution is to extend EV_ACCELERATOR, either by adding to EV_ACCELERATOR or through sub-classing, with a propagate state flag. Again for the sake of reference it will be called `propagate_accelerator'. Clients would simple set `propagate_accelerator' if they wanted to propagate the accelerator to parent widget container.

With the addition of `propagate_accelerator' on the widget's accelerator action sequence, `process_accelerator' could have to check the state flag of any applicable accelerator action sequence item to determine if the accelerator should be propagate. The state flag should be logically OR-ed so that multiple accelerator action sequence items, matching the passed accelerator key combination to `process_accelerator', will propagate the accelerator if one item requests propagation. Failure to find an item in the accelerator action sequence should remain an cause to propagate the accelerator to the widget's parent container.

== The Proposed Design ==
As stated, the design is simple.

class EV_WIDGET_I

-- class features elided for clarity.

feature -- Agents

accelerator_actions: EV_NOTIFY_ACTION_SEQUENCE
-- Accelerator actions for `Current' widget

feature {EV_WIDGET} -- Propagation

process_accelerator (a_accl: EV_ACCELERATROR) is
-- Process actions for accelerator `a_accl'.
require
a_accl_attached: a_accl /= Void
do
-- Loop through `accelerator_actions'.
-- If an accelerator matches `a_accl' call action sequence on accelerator.
-- Query the accelerator item in the `accelerator_actions' for the `propagate_accelerator' state flag
-- Locigally or `propagate_accelerator' with locally scoped state flag (`should_prop').

-- After loop has completed, examine `should_prop'.
-- If true or no accelerator was found call parent widget's `process_accelerator'
end

end -- class EV_WIDGET_I

The proposed design does require a change in EV_ACCELERATOR. It was discussed if EV_ACCELERATOR should be descended and specialized, but instead EV_APPLICATION will receive a new attribute and assigner - `propagate_accelerator' and `propagate_accelerator'

class EV_ACCELERATOR

-- class features elided for clarity.

feature -- Access

propagate_accelerator: BOOLEAN assign set_propagate_accelerator
-- Should accelerator be propagated to parent widgets?

feature -- Status Setting

enable_propagation is
-- Enable accelerator to be propagated to parent containers.
do
propagate_accelerator := True
ensure
propagate_accelerator_set: propagate_accelerator = True
end

disable_propagation is
-- Prevent accelerator to be propagated to parent containers.
do
propagate_accelerator := False
ensure
propagate_accelerator_set: propagate_accelerator = False
end

end -- class EV_ACCELERATOR

By the proposed design any existing application using EV_ACCELERATORs on an EV_APPLICATION should not be affected. Instead, now, of the top-level window receiving notification the last focused widget will handle the accelerator. If the widget does not handle the accelerator or the accelerator should be propagated, then the parent widget's implementation is executed. Existing developed application do not yet know about shortcut propagation so the accelerator will be propagated back until it reaches the top-level window, which as an end result exhibits the same behavior.

=Milestones=

==M1: April 25th==

==M2: May ??? ==
* To be completed by the team

=Team=

Everyone intrested in this project is welcome to join our mailinglist [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-vision| es-vision@origo.ethz.ch]

* TODO add project leader (Project leader)
* TODO add project members
* [[User:Bayt| Bayt]]

Cocoa for EiffelVision2

2006-04-21T07:44:28Z

Bayt: /* Team */ added link to mailinglist

[[Category:Projects]]
[[Category:EiffelVision2]]

=Overview=
The goal of this project is to provide Vision with a cocoa backend to make it truly native on the mac.
For more information please refer to the [[Talk:Cocoa_for_EiffelVision2|discussion page]]. See also [[OSX_release_infrastructure]].

=Milestones=

==M1: April 25th==
* get EiffelStudio 5.7 compiled under OS X

==M2: May 2nd ==
* Get a Vision window displayed with a Cocoa window (involves eventloop porting)

==M3: May ==
* To be completed by the team

=Team=
Everyone intrested in this project is welcome to join our mailinglist [http://origo.ethz.ch/cgi-bin/mailman/listinfo/es-mac| es-mac@origo.ethz.ch]

* [[User:Upeter| Upeter]] (Project leader)
* [[User:Maeli| Maeli]]
* [[User:Dfurrer| Dfurrer]]
* [[User:Bayt| Bayt]]
* [[User: nih| nih]]
* [[User:Spooky| Jann]]

Cocoa for EiffelVision2

2006-04-21T07:43:01Z

Bayt: /* M1: April 25th */ Mailinglists are set up now

[[Category:Projects]]
[[Category:EiffelVision2]]

=Overview=
The goal of this project is to provide Vision with a cocoa backend to make it truly native on the mac.
For more information please refer to the [[Talk:Cocoa_for_EiffelVision2|discussion page]]. See also [[OSX_release_infrastructure]].

=Milestones=

==M1: April 25th==
* get EiffelStudio 5.7 compiled under OS X

==M2: May 2nd ==
* Get a Vision window displayed with a Cocoa window (involves eventloop porting)

==M3: May ==
* To be completed by the team

=Team=
Everyone intrested in this project is welcome to join our mailinglist es-mac@origo.ethz.ch

* [[User:Upeter| Upeter]] (Project leader)
* [[User:Maeli| Maeli]]
* [[User:Dfurrer| Dfurrer]]
* [[User:Bayt| Bayt]]
* [[User: nih| nih]]
* [[User:Spooky| Jann]]

Talk:Folding support

2006-04-19T21:44:13Z

Bayt:

== working title of the project ==

A few ideas:
* Folding -> falten -> eiffel-origami
* FEES : Folding editor for Eiffel Studio
* hidden beauty project
* HYCs : Hide your code
* Folding Fields

any comments from team members?

[[User:Sanakan|Sanakan]] 22:02, 19 April 2006 (CEST)

[[User:Bayt|Bayt]]
I really like origamiE :-)

Compiling EiffelStudio

2006-04-18T22:12:04Z

Bayt: /* Checking out from SVN */

[[Category:Compiler]]
[[Category:EiffelStudio]]

== Installing EiffelStudio ==

To compile EiffelStudio, you need an already working EiffelStudio compiler on your machine. The current source tree '''requires at least version 5.7''' of EiffelStudio. You can download it from http://eiffelsoftware.origo.ethz.ch/downloads/builds/. This version still requires a registration (we missed to remove the registration cluster while compiling). You need to '''activate''' EiffelStudio (see below), because in some cases the compiler won't work correctly if not activated. [[Installing EiffelStudio]] is covered in its own article.

'''Note:''' on Windows you will need the Microsoft C compiler to compile Eiffel Studio. How to install the free version of the Microsoft C compiler: [[Installing Microsoft C compiler]]

===Compilation methods===
Currently there are two compilation methods.
* You can either compile EiffelStudio from scratch following the instructions in this document. This is the only method on Windows.
* Alternatively (on Linux/UNIX) you can use a compilation script that Bernd Schoeller has kindly posted to the developer mailinglist: [http://origo.ethz.ch/pipermail/es-devel/2006-April/000016.html Linux compilation script]
If possible, use the compilation script and report any errors to the developer mailing list.

==Extracting source code==

===Checking out from SVN===
#Point an environment variable called '''EIFFEL_SRC''' to the directory where you want to compile EiffelStudio Usually we use the '''XXdev''' convention for this directory name - where XX is the version number from the current developped version of the compiler.
#Make sure that '''ISE_EIFFEL''', '''ISE_PLATFORM''' and '''ISE_C_COMPILER''' (on windows only) are properly defined
#Perform the following checkout procedures:

'''Windows'''
<pre>
set SVNURL=https://eiffelsoftware.origo.ethz.ch/svn/es
svn co %SVNURL%/trunk/Src -N 57dev
svn co %SVNURL%/trunk/Src/bench/C 57dev/C
svn co %SVNURL%/trunk/Src/bench/Eiffel 57dev/Eiffel
svn co %SVNURL%/trunk/Delivery -N 57dev/Delivery
svn co %SVNURL%/trunk/free_add_ons 57dev/free_add_ons

cd 57dev
svn up C_library
svn up dotnet
svn up library
svn up library.net
svn up tools
</pre>

'''Bash'''
<pre>
export SVNURL=https://eiffelsoftware.origo.ethz.ch/svn/es
svn co $SVNURL/trunk/Src -N 57dev
svn co $SVNURL/trunk/Src/bench/C 57dev/C
svn co $SVNURL/trunk/Src/bench/Eiffel 57dev/Eiffel
svn co $SVNURL/trunk/Delivery -N 57dev/Delivery
svn co $SVNURL/trunk/free_add_ons 57dev/free_add_ons

cd 57dev
svn up C_library
svn up dotnet
svn up library
svn up library.net
svn up tools
</pre>

To update the sourcefiles to the latest revision, perform the following steps:

'''Bash and Windows'''
<pre>
cd 57dev
svn up C
svn up Eiffel
svn up free_add_ons
svn up C_library
svn up dotnet
svn up library
svn up library.net
svn up tools
</pre>

==Installing gobo==

Please make sure to use the version provided or the very latest version from CVS. All other versions (including the official 3.4 release) will not work because of name clashes in the UC_STRING class between GOBO and EiffelStudio. 
As the anonymous CVS on sourceforge is currently broken, use the following link from the gobo newsgroup to get the [http://www.gobosoft.com/download/gobo-cvs-060418.zip CVS-checkout of 18.April].

===Windows specific===

You have to unzip the gobo distribution from $EIFFEL_SRC/free_add_ons/gobo/gobo_34_win.tgz and extract it into $EIFFEL_SRC/library.

===Unix specific===

You have to unzip the gobo distribution from $EIFFEL_SRC/free_add_ons/gobo/gobo_34_unix.tgz and extract it into $EIFFEL_SRC/library. Here is the list of commands to do this:
<pre>cd $EIFFEL_SRC/library
tar -xvzf $EIFFEL_SRC/free_add_ons/gobo/gobo_34_unix.tgz
</pre>

==Compiling C libraries==

===Compiling run-time on Windows===

Before being able to compile the run-time, you need to ensure that '''bash''' is in your '''PATH'''. You can download it from [http://www.cygwin.com http://www.cygwin.com]. Also make sure, that the path to the binaries of your c compiler is placed before the path to cygwin or else the wrong linker will be used. Once done you can do:

<pre>cd $EIFFEL_SRC/C
configure [win32|win64] [b|m]</pre>

The first argument indicated whether you are compiling the run-time for 32 or 64 bits. The second one is to tell which C compiler will be used. For now only `b' (Borland) and `m' (Microsoft) are officially supported. We also informally support `g' (GCC) and `l' (LCC).

On Windows 32 bits to clean up all the generated files you do:
<pre>configure clean</pre>

On Windows 64 bits, you do:
<pre>configure cleand</pre>

===Compiling run-time on Unix===

The command is simply:
<pre>cd $EIFFEL_SRC/C
./quick_configure</pre>
This requires that '''ISE_PLATFORM''' is properly defined. The `quick_configure' script will look for the file CONFIGS/$ISE_PLATFORM and use it to extract the platform specific information to compile the run-time. If not found then an error will be reported.

===Compiling C code from libraries===

Here is the list of commands to compile all required C libraries on Windows:

<pre>cd $EIFFEL_SRC/library/net/Clib
make_msc.bat
cd $EIFFEL_SRC/library/vision2/Clib
make_msc.bat
cd $EIFFEL_SRC/library/wel/Clib
make_msc.bat</pre>

On Unix it is slightly different:
<pre>cd $EIFFEL_SRC/library/event/Clib
finish_freezing -library
cd $EIFFEL_SRC/library/net/Clib
finish_freezing -library
cd $EIFFEL_SRC/library/vision2/Clib
finish_freezing -library
cd $EIFFEL_SRC/library/vision2/implementation/gtk/Clib
finish_freezing -library</pre>

Make sure that '''ISE_EIFFEL''' is set correctly to your current "EiffelStudio" installation!

===Compiling C code from C_library===

This is only required on Windows to read PNG file. On Unix, this is not required because it is included in GTK+2.4. Simply do the following:
<pre>cd $EIFFEL_SRC/C_library/zlib
make_msc.bat
cd $EIFFEL_SRC/C_library/libpng
make_msc.bat</pre>

===Compiling C code from compiler===

This is only required on Windows as this C code is a tiny wrapper around the Microsoft C++ API to generate and to debug .NET code.

To compile it, you first need to install the Microsoft .NET SDK. You can download it from their website.

After installing it, you need to update your '''LIB''' and '''INCLUDE''' environment variable to include the path the lib and include directory of the .NET Framework SDK.

Once properly installed, you can do:
<pre>cd $EIFFEL_SRC/Eiffel/library/cli_writer/Clib
nmake</pre>

==Compiling EiffelStudio==

Now that we have taken care of the C code compilation we can compile the compiler. There are four ace files in $EIFFEL_SRC/Eiffel/Ace:
* batch.mswin.ace
* newbench.mswin.ace
* batch.unix.ace
* newbench.linux.ace
The first two are for windows, the last two for unix (even if the last one says `linux').

To compile simply do:
<pre>ec -ace <chosen_ace_file> -c_compile</pre>

Please note: the 'ec' binary produced by the newbench .ace file contains the full Eiffel compiler, including the batch version. 'estudio' is just a wrapper (available in Src/bench/C/ipc/daemon). So, you need either the one or the other.

===Windows specific===

At the end of the compilation for the workbench version, the C compilation will fail reporting an undefined reference to `nbref'. This is because the ace file has been built for the finalized version of EiffelStudio not the workbench version. To fix this problem do the following:
<pre>copy ec.lnk h</pre>
Then edit the file `h' and replace '''mtcompiler.lib''' by '''mtwcompiler.lib'''.
Once this is done you can complete you do:
<pre>link @h</pre>
In order to update to the new version of metadata consumer tool, follow the instructions described [[Compiling Metadata Consumer|here]].

===Unix specific===

Like the windows version the C compilation, it will fail, but this time for two reasons:
* nbref
* linking order causing many errors to be reported

Here is the recommended way, make a copy of the generated Makefile and put it at the same level as your EIFGEN directory. Edit it and replace '''libmtcompiler.a''' by '''libmtwcompiler.a''', then search for "$(EXTERNALS) $(EIFLIB)" and replace it by "$(EIFLIB) $(EXTERNALS)". Once this is done, you can do:
<pre>make -f ../../Makefile</pre>

A little script that does the necessary changes: Place it at the same level as the EIFGEN directory is.

<code>[bash,N]
#!/bin/bash

cp EIFGEN/W_code/Makefile .
sed 's/libmtcompiler\.a/libmtwcompiler\.a/g' Makefile > tmp
sed 's/\$(EXTERNALS) \$(EIFLIB)/\$$EIFLIB$ \$$EXTERNALS$/g' tmp > Makefile
cd EIFGEN/W_code
make -f ../../Makefile
</code>

'''Note:''' These changes are not required if you try to compile a finalized version of EiffelStudio, but only if you want to create a workbench version of EiffelStudio for development and debugging.

Also, if you encounter problems with your self-compiled version of EiffelStudio, you might try to compile it with GCC 3.x. Version 4 of GCC has a slight change in semantics and EiffelStudio has not been updated. You can see the change in behavior in the following code:

<code>[C,N]
#include <stdio.h>

int a;
int b;
int *pointer;

int foo()
{
pointer = &b;
return 4;
}

int main (int argc, char** argv)
{
a = 3;
b = 0;

pointer = &a;

*pointer = foo();

printf ("You are using GCC %d.%d\n",a,b);
return 0;
}
</code>

===Mac OS X specific===

The basic steps are:
* compile it under linux
* copy the F_Code directory to the mac
* compile it there using make
* fix whatever problems appear

Multi screen support

2006-04-18T21:17:57Z

Bayt: Added Serafin

[[Category:Projects]]
[[Category:EiffelVision2]]

=Overview=
The aim of this project is to enhance Vision with a support for multiple screens.

=Milestones=

==M1: April 25th==
* set up mailinglist es-ui@origo.ethz.ch ([[User:Schoelle|Bernd]])

==M2: May ??? ==
* To be completed by the team

=Team=
Everyone intrested in this project is welcome to join our mailinglist es-ui@origo.ethz.ch

* TODO add project leader Mario Deuss (Project leader)
* TODO add project members
* [[User:Serafin| Serafin]]
* [[User:Bayt| Bayt]]

Vision2 and Unicode

2006-04-18T21:17:16Z

Bayt: Added Serafin

[[Category:EiffelVision2]]
[[Category:Projects]]
[[Category:Unicode]]

=Introduction=
Have a look at the [[WEL_and_Unicode|description made for the WEL library]]. The same applies to EiffelVision2.

=Milestones=

==M1: April 25th==
* set up mailinglist es-vision@origo.ethz.ch ([[User:Schoelle|Bernd]])

==M2: May ??? ==
* implement multi screen support for Vision: [[Multi screen support]]
* collaborate with the internationalization team (TODO add link to their project page)
* write a decent STRING_32 implementation for
** string comparisons
** lower/upper case conversion
** some of it is already in Gobo but not completely as efficient as it should
* To be completed by the team

=Team=
Everyone intrested in this project is welcome to join our mailinglist es-vision@origo.ethz.ch

* TODO add project leader (Project leader)
* TODO add project members
* [[User:Serafin| Serafin]]
* [[User:Bayt| Bayt]]

Talk:Vision2 and Unicode

2006-04-18T21:13:41Z

Bayt: added howto

=Howto=
The basic ideas are the following:
*Do the Unicode stuff first as an outside library that takes STRING_GENERAL instances as argument
**The implementation should be as compact as possible for the tables, and of course very efficient. This is actually a quite difficult work since it requires some reading of the Unicode standard.
*Implement helper classes using RAW_FILE as argument to read text file in a special unicode encoding
**Looks like there are some kind of standard out there using BOM
*update editor to accepts STRING_GENERAL instances as arguments and thus enabling user to enter unicode characters

Talk:Multi screen support

2006-04-18T21:06:16Z

Bayt: updated howto

=Howto=
The basic approach would be:
*improve the EV_SCREEN class to handle multiple screens and then let Vision and later ES make use of it

Vision2 and Unicode

2006-04-18T21:02:14Z

Bayt: added reference to other part of this groups project: multi screen support for vision

[[Category:EiffelVision2]]
[[Category:Projects]]
[[Category:Unicode]]

=Introduction=
Have a look at the [[WEL_and_Unicode|description made for the WEL library]]. The same applies to EiffelVision2.

=Milestones=

==M1: April 25th==
* set up mailinglist es-vision@origo.ethz.ch ([[User:Schoelle|Bernd]])

==M2: May ??? ==
* implement multi screen support for Vision: [[Multi screen support]]
* collaborate with the internationalization team (TODO add link to their project page)
* write a decent STRING_32 implementation for
** string comparisons
** lower/upper case conversion
** some of it is already in Gobo but not completely as efficient as it should
* To be completed by the team

=Team=
Everyone intrested in this project is welcome to join our mailinglist es-vision@origo.ethz.ch

* TODO add project leader (Project leader)
* TODO add project members
* [[User:Bayt| Bayt]]

Editor

2006-04-18T21:01:04Z

Bayt:

[[Category:Projects]]

Editor enhancements for ES 5.7:

* Tabbed Editor
* [[Folding support]]
* [[Multi screen support]]
* Fully customizable UI layout, UI docking

Future plans:
* Source code formatter
* Editing shortcuts

Multi screen support

2006-04-18T21:00:25Z

Bayt: created page

[[Category:Projects]]
[[Category:EiffelVision2]]

=Overview=
The aim of this project is to enhance Vision with a support for multiple screens.

=Milestones=

==M1: April 25th==
* set up mailinglist es-ui@origo.ethz.ch ([[User:Schoelle|Bernd]])

==M2: May ??? ==
* To be completed by the team

=Team=
Everyone intrested in this project is welcome to join our mailinglist es-ui@origo.ethz.ch

* TODO add project leader Mario Deuss (Project leader)
* TODO add project members
* [[User:Bayt| Bayt]]

Editor

2006-04-18T20:58:50Z

Bayt:

[[Category:Projects]]

Editor enhancements for ES 5.7:

* Tabbed Editor
* [[Folding support]]
* Multi screen support
* Fully customizable UI layout, UI docking

Future plans:
* Source code formatter
* Editing shortcuts

Vision2 and Unicode

2006-04-18T20:58:17Z

Bayt: update milestones

[[Category:EiffelVision2]]
[[Category:Projects]]
[[Category:Unicode]]

=Introduction=
Have a look at the [[WEL_and_Unicode|description made for the WEL library]]. The same applies to EiffelVision2.

=Milestones=

==M1: April 25th==
* set up mailinglist es-vision@origo.ethz.ch ([[User:Schoelle|Bernd]])

==M2: May ??? ==
* implement multi screen support for Vision
* collaborate with the internationalization team (TODO add link to their project page)
* write a decent STRING_32 implementation for
** string comparisons
** lower/upper case conversion
** some of it is already in Gobo but not completely as efficient as it should
* To be completed by the team

=Team=
Everyone intrested in this project is welcome to join our mailinglist es-vision@origo.ethz.ch

* TODO add project leader (Project leader)
* TODO add project members
* [[User:Bayt| Bayt]]

Folding support

2006-04-18T20:53:47Z

Bayt: added input from manus

[[Category:Projects]]
[[Category:EiffelVision2]]

=Overview=
The aim of this project is to enhance Vision with a RichText control that supports folding. The goal is to make this surface in the editor windows of EiffelStudio.

=Milestones=

==M1: April 25th==
* set up mailinglist es-ui@origo.ethz.ch ([[User:Schoelle|Bernd]])

==M2: May ??? ==
* implement support for word wrapping
* To be completed by the team

=Team=
Everyone intrested in this project is welcome to join our mailinglist es-ui@origo.ethz.ch

* [[User:Sanakan| Sanakan]] (Project leader)
* TODO add 2nd project leader Mario Deuss (Project leader)
* TODO add project members
* [[User:Bayt| Bayt]]

Editor

2006-04-18T20:49:32Z

Bayt:

[[Category:Projects]]

Editor enhancements for ES 5.7:

* Tabbed Editor
* [[Folding support]]
* Fully customizable UI layout, UI docking

Future plans:
* Source code formatter
* Editing shortcuts

Editor

2006-04-18T20:48:26Z

Bayt:

[[Category:Projects]]

Editor enhancements.

* Tabbed Editor (Team at Eiffel Software)
* Source code formatter
* Editing shortcuts
* [[Folding support]]
* Fully customizable UI layout, UI docking

Category:Projects

2006-04-18T20:46:51Z

Bayt: added unicode link

Projects and project suggestions.

* Build infrastructure
**[[Build_tool | Build tool]] 
**[[Debian_packages | Debian packages]] 
**[[OSX_release_infrastructure|OSX release infrastructure]]
**[[Component_standards| Standards and tools for Eiffel based components]]

* UI
**[[Vision2_Accelerator|Vision2 Accelerator]] 
**[[Vision2_and_Unicode|Unicode support for Vision2]] 
**[[Editor|Editor]] 
**[[EiffelBuild_Integration|EiffelBuild Integration]] 
**[[Cocoa_for_EiffelVision2|Cocoa for EiffelVision2]]

* Library
**[[Scintilla_component| Multiplatform editor component: Scintilla]] 
**[[Gecko_component| Multiplatform layout engine component: Mozilla/Gecko]]

Cocoa for EiffelVision2

2006-04-18T20:44:47Z

Bayt: Added link to OS X release infrastrucutre page

[[Category:Projects]]
[[Category:EiffelVision2]]

=Overview=
The goal of this project is to provide Vision with a cocoa backend to make it truly native on the mac.
For more information please refer to the [[Talk:Cocoa_for_EiffelVision2|discussion page]]. See also [[OSX_release_infrastructure]].

=Milestones=

==M1: April 25th==
* get EiffelStudio 5.7 compiled under OS X
* set up mailinglist es-mac@origo.ethz.ch ([[User:Schoelle|Bernd]])

==M2: May 2nd ==
* Get a Vision window displayed with a Cocoa window (involves eventloop porting)

==M3: May ==
* To be completed by the team

=Team=
Everyone intrested in this project is welcome to join our mailinglist es-mac@origo.ethz.ch

* [[User:Upeter| Upeter]] (Project leader)
* [[User:Maeli| Maeli]]
* [[User:Dfurrer| Dfurrer]]
* [[User:Bayt| Bayt]]
* TODO add Roland Haeuslers nick
* TODO add Jan Roeders Nick

Folding support

2006-04-18T20:42:00Z

Bayt: Sanakan was faster

[[Category:Projects]]
[[Category:EiffelVision2]]

=Overview=
The aim of this project is to enhance Vision with a RichText control that supports folding. The goal is to make this surface in the editor windows of EiffelStudio.

=Milestones=

==M1: April 25th==
* set up mailinglist es-ui@origo.ethz.ch ([[User:Schoelle|Bernd]])

==M2: May ??? ==
* To be completed by the team

=Team=
Everyone intrested in this project is welcome to join our mailinglist es-ui@origo.ethz.ch

* [[User:Sanakan| Sanakan]] (Project leader)
* TODO add 2nd project leader Mario Deuss (Project leader)
* TODO add project members
* [[User:Bayt| Bayt]]

Editor

2006-04-18T20:25:19Z

Bayt:

[[Category:Projects]]

Editor enhancements.

* Tabbed Editor (Team at Eiffel Software)
* Source code formatter
* Editing shortcuts
* Folding support
* Fully customizable UI layout, UI docking (Team at Eiffel Software)

Vision2 and Unicode

2006-04-18T20:07:56Z

Bayt:

[[Category:EiffelVision2]]
[[Category:Projects]]
[[Category:Unicode]]

=Introduction=
Have a look at the [[WEL_and_Unicode|description made for the WEL library]]. The same applies to EiffelVision2.

=Milestones=

==M1: April 25th==
* set up mailinglist es-vision@origo.ethz.ch ([[User:Schoelle|Bernd]])

==M2: May ??? ==
* collaborate with the internationalization team (TODO add link to their project page)
* write a decent STRING_32 implementation for
** string comparisons
** lower/upper case conversion
** some of it is already in Gobo but not completely as efficient as it should
* To be completed by the team

=Team=
Everyone intrested in this project is welcome to join our mailinglist es-vision@origo.ethz.ch

* TODO add project leader (Project leader)
* TODO add project members
* [[User:Bayt| Bayt]]

EiffelVision accelerators

2006-04-18T20:04:07Z

Bayt:

[[Category:EiffelVision2]]
[[Category:Projects]]

The EiffelVision2 accelerator addition Wiki page.

== Overview ==
This page discusses the initial design of a new shortcut propagation mechanism that may be built into EiffelVision 2. The initial requirement indicated that a widget should be able to handle a shortcut accelerator and execute an action. If a widget does not handle the shortcut, the shortcut key combination will be propagate to the parent contain. This process continues until either a shortcut has been handled or the top-level windows has been reached, in which case there is no parent widget.

== Proposal ==
During a design meeting a number of designed were proffered as designs that could be used at the EV_WIDGET level. However, through a process of elimination and evolution a design was decided upon that is simple, backwards compatible and whose interface is more akin to EiffelVision 2 action sequences used to date. The design of the interface proved important to provide backwards compatibility.

For this proposal to correctly function it is imperative that the widget who recieved focused last be given initial rights to process an accelerator key combination. The widget will then handle any unhandled accelerator key combinations by propagating it to a parent container.

It is proposed that an action sequence, similar to the action sequence for accelerators on EV_APPLICATION, be added to EV_WIDGET or EV_WIDGET_I (interface). Adding to the interface is preferable to prevent code duplication for each supported platform. EV_WIDGET(_I) would also host a feature that is responsible for receiving an accelerator key combination, for the sake of reference it will be called `process_accelerator'. `process_accelerator' will iterate the accelerator action sequence to determine if any item in the sequence matches the accelerator key combination passed to `process_accelerator'. If there is a match then agents on the action sequence item (presumably EV_ACCELERATOR) will be executed.

For propagation, the initial requirement is that any unhandled shortcut be propagated to a widget's parent container. In this case the simple detection of an item in the accelerator action sequence, on the widget, that matches the accelerator key combination passed to `process_accelerator' would suffice. However, users may want to force propagation.

The proposed solution is to extend EV_ACCELERATOR, either by adding to EV_ACCELERATOR or through sub-classing, with a propagate state flag. Again for the sake of reference it will be called `propagate_accelerator'. Clients would simple set `propagate_accelerator' if they wanted to propagate the accelerator to parent widget container.

With the addition of `propagate_accelerator' on the widget's accelerator action sequence, `process_accelerator' could have to check the state flag of any applicable accelerator action sequence item to determine if the accelerator should be propagate. The state flag should be logically OR-ed so that multiple accelerator action sequence items, matching the passed accelerator key combination to `process_accelerator', will propagate the accelerator if one item requests propagation. Failure to find an item in the accelerator action sequence should remain an cause to propagate the accelerator to the widget's parent container.

== The Proposed Design ==
As stated, the design is simple.

class EV_WIDGET_I

-- class features elided for clarity.

feature -- Agents

accelerator_actions: EV_NOTIFY_ACTION_SEQUENCE
-- Accelerator actions for `Current' widget

feature {EV_WIDGET} -- Propagation

process_accelerator (a_accl: EV_ACCELERATROR) is
-- Process actions for accelerator `a_accl'.
require
a_accl_attached: a_accl /= Void
do
-- Loop through `accelerator_actions'.
-- If an accelerator matches `a_accl' call action sequence on accelerator.
-- Query the accelerator item in the `accelerator_actions' for the `propagate_accelerator' state flag
-- Locigally or `propagate_accelerator' with locally scoped state flag (`should_prop').

-- After loop has completed, examine `should_prop'.
-- If true or no accelerator was found call parent widget's `process_accelerator'
end

end -- class EV_WIDGET_I

The proposed design does require a change in EV_ACCELERATOR. It was discussed if EV_ACCELERATOR should be descended and specialized, but instead EV_APPLICATION will receive a new attribute and assigner - `propagate_accelerator' and `propagate_accelerator'

class EV_ACCELERATOR

-- class features elided for clarity.

feature -- Access

propagate_accelerator: BOOLEAN assign set_propagate_accelerator
-- Should accelerator be propagated to parent widgets?

feature -- Status Setting

enable_propagation is
-- Enable accelerator to be propagated to parent containers.
do
propagate_accelerator := True
ensure
propagate_accelerator_set: propagate_accelerator = True
end

disable_propagation is
-- Prevent accelerator to be propagated to parent containers.
do
propagate_accelerator := False
ensure
propagate_accelerator_set: propagate_accelerator = False
end

end -- class EV_ACCELERATOR

By the proposed design any existing application using EV_ACCELERATORs on an EV_APPLICATION should not be affected. Instead, now, of the top-level window receiving notification the last focused widget will handle the accelerator. If the widget does not handle the accelerator or the accelerator should be propagated, then the parent widget's implementation is executed. Existing developed application do not yet know about shortcut propagation so the accelerator will be propagated back until it reaches the top-level window, which as an end result exhibits the same behavior.

=Milestones=

==M1: April 25th==
* set up mailinglist es-vision@origo.ethz.ch ([[User:Schoelle|Bernd]])

==M2: May ??? ==
* To be completed by the team

=Team=
Everyone intrested in this project is welcome to join our mailinglist es-vision@origo.ethz.ch

* TODO add project leader (Project leader)
* TODO add project members
* [[User:Bayt| Bayt]]

Cocoa for EiffelVision2

2006-04-18T20:01:58Z

Bayt: typo

[[Category:Projects]]
[[Category:EiffelVision2]]

=Overview=
The goal of this project is to provide Vision with a cocoa backend to make it truly native on the mac.
For more information please refer to the [[Talk:Cocoa_for_EiffelVision2|discussion page]].

=Milestones=

==M1: April 25th==
* get EiffelStudio 5.7 compiled under OS X
* set up mailinglist es-mac@origo.ethz.ch ([[User:Schoelle|Bernd]])

==M2: May 2nd ==
* Get a Vision window displayed with a Cocoa window (involves eventloop porting)

==M3: May ==
* To be completed by the team

=Team=
Everyone intrested in this project is welcome to join our mailinglist es-mac@origo.ethz.ch

* [[User:Upeter| Upeter]] (Project leader)
* [[User:Maeli| Maeli]]
* [[User:Dfurrer| Dfurrer]]
* [[User:Bayt| Bayt]]
* TODO add Roland Haeuslers nick
* TODO add Jan Roeders Nick

Talk:Cocoa for EiffelVision2

2006-04-18T19:56:41Z

Bayt: Moved Dfurrer's inputs here, reorganized layout and added cocoa link

=Cocoa, Carbon ???=
* Maybe we should not target Cocoa, but carbon, just like SWT: [http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.swt/Eclipse%20SWT/carbon|carbon example in swt] could serve as inspiration for the backend.
* Info for [[http://developer.apple.com/cocoa|Cocoa]]
* Alternatively (and probably much easier) one could also make EiffelVision use the native GTK+ port instead of the X-version. But the state of Gtk+-Cocoa is unclear. ([[User:Dfurrer|Dfurrer]])

=Howto=
The basic approach would be:
* to write a very simple Vision2 application only showing a window.
* then we will have to write all implementation classes for the Vision2 widgets that will use the cocoa or carbon widgets internally
* these will be empty at the beginning and then slowly filled
* then one would start from the Vision2 event loop and try to fill the first implementation class, the one for the window probably
* and from there one would go to the other widgets

This is a very interesting project as it unifies many different widget toolkits, you learn lots about the widget toolkit on OS X. But it is also tricky because the widget toolkit on top of which you are also has bugs that you have to work around. For example in carbon the Bevel button in OS X does not display correctly when it's height is set to be smaller than 20 pixels. So if you provide an interface to that button, you would have to work around that.

Cocoa for EiffelVision2

2006-04-18T19:52:02Z

Bayt: Updated Cocoa for Vision project page

[[Category:Projects]]
[[Category:EiffelVision2]]

=Overview=
The goal of this project is to provide Vision with a cocoa backend to make it trulz native on the mac.
For more information please refer to the [[Talk:Cocoa_for_EiffelVision2|discussion page]].

=Milestones=

==M1: April 25th==
* get EiffelStudio 5.7 compiled under OS X
* set up mailinglist es-mac@origo.ethz.ch ([[User:Schoelle|Bernd]])

==M2: May 2nd ==
* Get a Vision window displayed with a Cocoa window (involves eventloop porting)

==M3: May ==
* To be completed by the team

=Team=
Everyone intrested in this project is welcomt to join our mailinglist es-mac@origo.ethz.ch

* [[User:Upeter| Upeter]] (Project leader)
* [[User:Maeli| Maeli]]
* [[User:Dfurrer| Dfurrer]]
* [[User:Bayt| Bayt]]
* TODO add Roland Haeuslers nick
* TODO add Jan Roeders Nick

EiffelStudio Internals

2006-04-13T09:19:05Z

Bayt:

[[Category:EiffelStudio]]
[[Category:Compiler]]
[[Category:Presentations]]
List of presentations along with the date at which they were made or presented:
* April 12th 2006: [http://eiffelsoftware.origo.ethz.ch/downloads/presentations/EiffelStudio_internals.ppt EiffelStudio Internals] for ETH as part of the Software Architecture class. A Quicktime movie of this the talk is available [http://se.inf.ethz.ch/teaching/ss2006/0050/movies/ss06.meyer060412.mov here].

Compiling EiffelStudio

2006-04-12T11:25:03Z

Bayt: Added OS X compilation instructions

[[Category:Compiler]]
[[Category:EiffelStudio]]

== Installing EiffelStudio ==

To compile EiffelStudio, you need an already working EiffelStudio compiler on your machine. The current source tree '''requires at least version 5.7''' of EiffelStudio. You can download it from http://eiffelsoftware.origo.ethz.ch/builds. This version still requires a registration (we missed to remove the registration cluster while compiling). You need to '''activate''' EiffelStudio (see below), because in some cases the compiler won't work correctly if not activated. [[Installing EiffelStudio]] is covered in its own article.

'''Note:''' on Windows you will need the Microsoft C compiler to compile Eiffel Studio. How to install the free version of the Microsoft C compiler: [[Installing Microsoft C compiler]]

===Compilation methods===
Currently there are two compilation methods.
* You can either compile EiffelStudio from scratch following the instructions in this document. This is the only method on Windows.
* Alternatively (on Linux/UNIX) you can use a compilation script that Bernd Schoeller has kindly posted to the developer mailinglist: [http://origo.ethz.ch/pipermail/es-devel/2006-April/000016.html Linux compilation script]
If possible, use the compilation script and report any errors to the developer mailing list.

==Extracting source code==

===Checking out from SVN===
Define the '''EIFFEL_SRC''' environment variable. Usually we use the '''XXdev''' convention where XX is the version number from the current developped version of the compiler.

Make sure that '''ISE_EIFFEL''', '''ISE_PLATFORM''' and '''ISE_C_COMPILER''' (on windows only) are properly defined

Perform the following checkout procedures:

'''Windows'''
<pre>
set SVNURL=https://eiffelsoftware.origo.ethz.ch/svn/es
svn co %SVNURL%/trunk/Src -N 57dev
svn co %SVNURL%/trunk/Src/bench/C 57dev/C
svn co %SVNURL%/trunk/Src/bench/Eiffel 57dev/Eiffel
svn co %SVNURL%/trunk/Src/common 57dev/Eiffel/common
svn co %SVNURL%/trunk/Delivery -N 57dev/Delivery
svn co %SVNURL%/trunk/free_add_ons 57dev/free_add_ons

cd 57dev
svn up C_library
svn up dotnet
svn up library
svn up library.net
svn up tools
</pre>

'''Bash'''
<pre>
export SVNURL=https://eiffelsoftware.origo.ethz.ch/svn/es
svn co $SVNURL/trunk/Src -N 57dev
svn co $SVNURL/trunk/Src/bench/C 57dev/C
svn co $SVNURL/trunk/Src/bench/Eiffel 57dev/Eiffel
svn co $SVNURL/trunk/Src/common 57dev/Eiffel/common
svn co $SVNURL/trunk/Delivery -N 57dev/Delivery
svn co $SVNURL/trunk/free_add_ons 57dev/free_add_ons

cd 57dev
svn up C_library
svn up dotnet
svn up library
svn up library.net
svn up tools
</pre>

==Installing gobo==

Please make sure to use the version provided or the very latest version from CVS. All other versions (including the official 3.4 release) will not work because of name clashes in the UC_STRING class between GOBO and EiffelStudio.

===Windows specific===

You have to unzip the gobo distribution from $EIFFEL_SRC/free_add_ons/gobo/gobo_34_win.tgz and extract it into $EIFFEL_SRC/library.

===Unix specific===

You have to unzip the gobo distribution from $EIFFEL_SRC/free_add_ons/gobo/gobo_34_unix.tgz and extract it into $EIFFEL_SRC/library. Here is the list of commands to do this:
<pre>cd $EIFFEL_SRC/library
tar -xvzf $EIFFEL_SRC/free_add_ons/gobo/gobo_34_unix.tgz
</pre>
==Compiling C libraries==

===Compiling run-time on Windows===

Before being able to compile the run-time, you need to ensure that '''bash''' is in your '''PATH'''. You can download it from [http://www.cygwin.com http://www.cygwin.com]. Once done you can do:

<pre>cd $EIFFEL_SRC/C
configure [win32|win64] [b|m]</pre>

The first argument indicated whether you are compiling the run-time for 32 or 64 bits. The second one is to tell which C compiler will be used. For now only `b' (Borland) and `m' (Microsoft) are officially supported. We also informally support `g' (GCC) and `l' (LCC).

On Windows 32 bits to clean up all the generated files you do:
<pre>configure clean</pre>

On Windows 64 bits, you do:
<pre>configure cleand</pre>

===Compiling run-time on Unix===

The command is simply:
<pre>cd $EIFFEL_SRC/C
./quick_configure</pre>
This requires that '''ISE_PLATFORM''' is properly defined. The `quick_configure' script will look for the file CONFIGS/$ISE_PLATFORM and use it to extract the platform specific information to compile the run-time. If not found then an error will be reported.

===Compiling C code from libraries===

Here is the list of commands to compile all required C libraries on Windows:

<pre>cd $EIFFEL_SRC/library/net/Clib
make_msc.bat
cd $EIFFEL_SRC/library/vision2/Clib
make_msc.bat
cd $EIFFEL_SRC/library/wel/Clib
make_msc.bat</pre>

On Unix it is slightly different:
<pre>cd $EIFFEL_SRC/library/event/Clib
finish_freezing -library
cd $EIFFEL_SRC/library/net/Clib
finish_freezing -library
cd $EIFFEL_SRC/library/vision2/Clib
finish_freezing -library
cd $EIFFEL_SRC/library/vision2/implementation/gtk/Clib
finish_freezing -library</pre>

Make sure that '''ISE_EIFFEL''' is set correctly to your current "EiffelStudio" installation!

===Compiling C code from C_library===

This is only required on Windows to read PNG file. On Unix, this is not required because it is included in GTK+2.4. Simply do the following:
<pre>cd $EIFFEL_SRC/C_library/zlib
make_msc.bat
cd $EIFFEL_SRC/C_library/libpng
make_msc.bat</pre>

===Compiling C code from compiler===

This is only required on Windows as this C code is a tiny wrapper around the Microsoft C++ API to generate and to debug .NET code.

To compile it, you first need to install the Microsoft .NET SDK. You can download it from their website.

After installing it, you need to update your '''LIB''' and '''INCLUDE''' environment variable to include the path the lib and include directory of the .NET Framework SDK.

Once properly installed, you can do:
<pre>cd $EIFFEL_SRC/Eiffel/library/cli_writer/Clib
nmake</pre>

==Compiling EiffelStudio==

Now that we have taken care of the C code compilation we can compile the compiler. There are four ace files in $EIFFEL_SRC/Eiffel/Ace:
* batch.mswin.ace
* newbench.mswin.ace
* batch.unix.ace
* newbench.linux.ace
The first two are for windows, the last two for unix (even if the last one says `linux').

To compile simply do:
<pre>ec -ace <chosen_ace_file> -c_compile</pre>

Please note: the 'ec' binary produced by the newbench .ace file contains the full Eiffel compiler, including the batch version. 'estudio' is just a wrapper (available in Src/bench/C/ipc/daemon). So, you need either the one or the other.

===Windows specific===

At the end of the compilation for the workbench version, the C compilation will fail reporting an undefined reference to `nbref'. This is because the ace file has been built for the finalized version of EiffelStudio not the workbench version. To fix this problem do the following:
<pre>copy ec.lnk h</pre>
Then edit the file `h' and replace '''mtcompiler.lib''' by '''mtwcompiler.lib'''.
Once this is done you can complete you do:
<pre>link @h</pre>
In order to update to the new version of metadata consumer tool, follow the instructions described [[Compiling Metadata Consumer|here]].

===Unix specific===

Like the windows version the C compilation, it will fail, but this time for two reasons:
* nbref
* linking order causing many errors to be reported

Here is the recommended way, make a copy of the generated Makefile and put it at the same level as your EIFGEN directory. Edit it and replace '''libmtcompiler.a''' by '''libmtwcompiler.a''', then search for "$(EXTERNALS) $(EIFLIB)" and replace it by "$(EIFLIB) $(EXTERNALS)". Once this is done, you can do:
<pre>make -f ../../Makefile</pre>

A little script that does the necessary changes: Place it at the same level as the EIFGEN directory is.

<code>[bash,N]
#!/bin/bash

cp EIFGEN/W_code/Makefile .
sed 's/libmtcompiler\.a/libmtwcompiler\.a/g' Makefile > tmp
sed 's/\$(EXTERNALS) \$(EIFLIB)/\$$EIFLIB$ \$$EXTERNALS$/g' tmp > Makefile
cd EIFGEN/W_code
make -f ../../Makefile
</code>

Also, if you encounter problems with your self-compiled version of EiffelStudio, you might try to compile it with GCC 3.x. Version 4 of GCC has a slight change in semantics and EiffelStudio has not been updated. You can see the change in behavior in the following code:

<code>[C,N]
#include <stdio.h>

int a;
int b;
int *pointer;

int foo()
{
pointer = &b;
return 4;
}

int main (int argc, char** argv)
{
a = 3;
b = 0;

pointer = &a;

*pointer = foo();

printf ("You are using GCC %d.%d\n",a,b);
return 0;
}
</code>

===Mac OS X specific===

The basic steps are:
* compile it under linux
* copy the F_Code directory to the mac
* compile it there using make
* fix whatever problems appear

Compiling EiffelStudio

2006-04-12T09:19:58Z

Bayt:

[[Category:Compiler]]
[[Category:EiffelStudio]]

== Installing EiffelStudio ==

To compile EiffelStudio, you need an already working EiffelStudio compiler on your machine. The current source tree '''requires at least version 5.7''' of EiffelStudio. You can download it from http://eiffelsoftware.origo.ethz.ch/builds. This version still requires a registration (we missed to remove the registration cluster while compiling). You need to '''activate''' EiffelStudio (see below), because in some cases the compiler won't work correctly if not activated. [[Installing EiffelStudio]] is covered in its own article.

'''Note:''' on Windows you will need the Microsoft C compiler to compile Eiffel Studio. How to install the free version of the Microsoft C compiler: [[Installing Microsoft C compiler]]

===Compilation methods===
Currently there are two compilation methods.
* You can either compile EiffelStudio from scratch following the instructions in this document. This is the only method on Windows.
* Alternatively (on Linux/UNIX) you can use a compilation script that Bernd Schoeller has kindly posted to the developer mailinglist: [http://origo.ethz.ch/pipermail/es-devel/2006-April/000016.html Linux compilation script]
If possible, use the compilation script and report any errors to the developer mailing list.

==Extracting source code==

===Checking out from SVN===
Define the '''EIFFEL_SRC''' environment variable. Usually we use the '''XXdev''' convention where XX is the version number from the current developped version of the compiler.

Make sure that '''ISE_EIFFEL''', '''ISE_PLATFORM''' and '''ISE_C_COMPILER''' (on windows only) are properly defined

Perform the following checkout procedures:

'''Windows'''
<pre>
set SVNURL=https://eiffelsoftware.origo.ethz.ch/svn/es
svn co %SVNURL%/trunk/Src -N 57dev
svn co %SVNURL%/trunk/Src/bench/C 57dev/C
svn co %SVNURL%/trunk/Src/bench/Eiffel 57dev/Eiffel
svn co %SVNURL%/trunk/Src/common 57dev/Eiffel/common
svn co %SVNURL%/trunk/Delivery -N 57dev/Delivery
svn co %SVNURL%/trunk/free_add_ons 57dev/free_add_ons

cd 57dev
svn up C_library
svn up dotnet
svn up library
svn up library.net
svn up tools
</pre>

'''Bash'''
<pre>
export SVNURL=https://eiffelsoftware.origo.ethz.ch/svn/es
svn co $SVNURL/trunk/Src -N 57dev
svn co $SVNURL/trunk/Src/bench/C 57dev/C
svn co $SVNURL/trunk/Src/bench/Eiffel 57dev/Eiffel
svn co $SVNURL/trunk/Src/common 57dev/Eiffel/common
svn co $SVNURL/trunk/Delivery -N 57dev/Delivery
svn co $SVNURL/trunk/free_add_ons 57dev/free_add_ons

cd 57dev
svn up C_library
svn up dotnet
svn up library
svn up library.net
svn up tools
</pre>

==Installing gobo==

Please make sure to use the version provided or the very latest version from CVS. All other versions (including the official 3.4 release) will not work because of name clashes in the UC_STRING class between GOBO and EiffelStudio.

===Windows specific===

You have to unzip the gobo distribution from $EIFFEL_SRC/free_add_ons/gobo/gobo_34_win.tgz and extract it into $EIFFEL_SRC/library.

===Unix specific===

You have to unzip the gobo distribution from $EIFFEL_SRC/free_add_ons/gobo/gobo_34_unix.tgz and extract it into $EIFFEL_SRC/library. Here is the list of commands to do this:
<pre>cd $EIFFEL_SRC/library
tar -xvzf $EIFFEL_SRC/free_add_ons/gobo/gobo_34_unix.tgz
</pre>
==Compiling C libraries==

===Compiling run-time on Windows===

Before being able to compile the run-time, you need to ensure that '''bash''' is in your '''PATH'''. You can download it from [http://www.cygwin.com http://www.cygwin.com]. Once done you can do:

<pre>cd $EIFFEL_SRC/C
configure [win32|win64] [b|m]</pre>

The first argument indicated whether you are compiling the run-time for 32 or 64 bits. The second one is to tell which C compiler will be used. For now only `b' (Borland) and `m' (Microsoft) are officially supported. We also informally support `g' (GCC) and `l' (LCC).

On Windows 32 bits to clean up all the generated files you do:
<pre>configure clean</pre>

On Windows 64 bits, you do:
<pre>configure cleand</pre>

===Compiling run-time on Unix===

The command is simply:
<pre>cd $EIFFEL_SRC/C
./quick_configure</pre>
This requires that '''ISE_PLATFORM''' is properly defined. The `quick_configure' script will look for the file CONFIGS/$ISE_PLATFORM and use it to extract the platform specific information to compile the run-time. If not found then an error will be reported.

===Compiling C code from libraries===

Here is the list of commands to compile all required C libraries on Windows:

<pre>cd $EIFFEL_SRC/library/net/Clib
make_msc.bat
cd $EIFFEL_SRC/library/vision2/Clib
make_msc.bat
cd $EIFFEL_SRC/library/wel/Clib
make_msc.bat</pre>

On Unix it is slightly different:
<pre>cd $EIFFEL_SRC/library/event/Clib
finish_freezing -library
cd $EIFFEL_SRC/library/net/Clib
finish_freezing -library
cd $EIFFEL_SRC/library/vision2/Clib
finish_freezing -library
cd $EIFFEL_SRC/library/vision2/implementation/gtk/Clib
finish_freezing -library</pre>

Make sure that '''ISE_EIFFEL''' is set correctly to your current "EiffelStudio" installation!

===Compiling C code from C_library===

This is only required on Windows to read PNG file. On Unix, this is not required because it is included in GTK+2.4. Simply do the following:
<pre>cd $EIFFEL_SRC/C_library/zlib
make_msc.bat
cd $EIFFEL_SRC/C_library/libpng
make_msc.bat</pre>

===Compiling C code from compiler===

This is only required on Windows as this C code is a tiny wrapper around the Microsoft C++ API to generate and to debug .NET code.

To compile it, you first need to install the Microsoft .NET SDK. You can download it from their website.

After installing it, you need to update your '''LIB''' and '''INCLUDE''' environment variable to include the path the lib and include directory of the .NET Framework SDK.

Once properly installed, you can do:
<pre>cd $EIFFEL_SRC/Eiffel/library/cli_writer/Clib
nmake</pre>

==Compiling EiffelStudio==

Now that we have taken care of the C code compilation we can compile the compiler. There are four ace files in $EIFFEL_SRC/Eiffel/Ace:
* batch.mswin.ace
* newbench.mswin.ace
* batch.unix.ace
* newbench.linux.ace
The first two are for windows, the last two for unix (even if the last one says `linux').

To compile simply do:
<pre>ec -ace <chosen_ace_file> -c_compile</pre>

Please note: the 'ec' binary produced by the newbench .ace file contains the full Eiffel compiler, including the batch version. 'estudio' is just a wrapper (available in Src/bench/C/ipc/daemon). So, you need either the one or the other.

===Windows specific===

At the end of the compilation for the workbench version, the C compilation will fail reporting an undefined reference to `nbref'. This is because the ace file has been built for the finalized version of EiffelStudio not the workbench version. To fix this problem do the following:
<pre>copy ec.lnk h</pre>
Then edit the file `h' and replace '''mtcompiler.lib''' by '''mtwcompiler.lib'''.
Once this is done you can complete you do:
<pre>link @h</pre>
In order to update to the new version of metadata consumer tool, follow the instructions described [[Compiling Metadata Consumer|here]].

===Unix specific===

Like the windows version the C compilation, it will fail, but this time for two reasons:
* nbref
* linking order causing many errors to be reported

Here is the recommended way, make a copy of the generated Makefile and put it at the same level as your EIFGEN directory. Edit it and replace '''libmtcompiler.a''' by '''libmtwcompiler.a''', then search for "$(EXTERNALS) $(EIFLIB)" and replace it by "$(EIFLIB) $(EXTERNALS)". Once this is done, you can do:
<pre>make -f ../../Makefile</pre>

A little script that does the necessary changes: Place it at the same level as the EIFGEN directory is.

<code>[bash,N]
#!/bin/bash

cp EIFGEN/W_code/Makefile .
sed 's/libmtcompiler\.a/libmtwcompiler\.a/g' Makefile > tmp
sed 's/\$(EXTERNALS) \$(EIFLIB)/\$$EIFLIB$ \$$EXTERNALS$/g' tmp > Makefile
cd EIFGEN/W_code
make -f ../../Makefile
</code>

Also, if you encounter problems with your self-compiled version of EiffelStudio, you might try to compile it with GCC 3.x. Version 4 of GCC has a slight change in semantics and EiffelStudio has not been updated. You can see the change in behavior in the following code:

<code>[C,N]
#include <stdio.h>

int a;
int b;
int *pointer;

int foo()
{
pointer = &b;
return 4;
}

int main (int argc, char** argv)
{
a = 3;
b = 0;

pointer = &a;

*pointer = foo();

printf ("You are using GCC %d.%d\n",a,b);
return 0;
}
</code>

===Mac OS X specific===

nothing documented yet...

Editor

2006-04-12T09:13:10Z

Bayt:

[[Category:Projects]]

Editor enhancements.

* Tabbed Editor (Team at Eiffel Software)
* Source code formatter
* Editing shortcuts
* Fully customizable UI layout, UI docking (Team at Eiffel Software)

Talk:Cocoa for EiffelVision2

2006-04-12T06:59:21Z

Bayt:

Maybe we should not target Cocoa, but carbon, just like SWT:http://dev.eclipse.org/viewcvs/index.cgi/org.eclipse.swt/Eclipse%20SWT/carbon

could serve as inspiration for the backend.

The basic approach would be:
* to write a very simple Vision2 application only showing a window.
* then we will have to write all implementation classes for the Vision2 widgets that will use the cocoa or carbon widgets internally
* these will be empty at the beginning and then slowly filled
* then one would start from the Vision2 event loop and try to fill the first implementation class, the one for the window probably
* and from there one would go to the other widgets

This is a very interesting project as it unifies many different widget toolkits, you learn lots about the widget toolkit on OS X. But it is also tricky because the widget toolkit on top of which you are also has bugs that you have to work around. For example in carbon the Bevel button in OS X does not display correctly when it's height is set to be smaller than 20 pixels. So if you provide an interface to that button, you would have to work around that.