EiffelStudio: an EiffelSoftware project - User contributions [en]

Talk:EMU/SRS

2006-05-27T08:40:45Z

Barnski: Emu Logo not showing?

== Emu Logo not showing? ==

My Norton Internet Security Ad-Blocker hid the logos on the SRS and Protocol page, but surprisingly not on the main EMU page...
If you have the problem that the logo is not showing, then you need to disable your ad-blocker for this site (http://eiffelsoftware.origo.ethz.ch).

EMU

2006-05-24T17:29:32Z

Barnski: /* Milestones */

[[Category:Projects]]
[[Image:emu_group.png|right|frame| EMUs: Eiffel Multi Users]]

=Overview=
==Name==
EMU stands for '''Eiffel Multi User'''.
==Goal==
The aim of this project is to integrate a simple repository functionality into EiffelStudio.

=Software Requirements Specification=
You can find our SRS [[EMU/SRS|here]]

=Milestones=

==M1: April 25th==
* set up mailinglist es-emu@origo.ethz.ch ([[User:Schoelle|Bernd]])
* wiki page up to date
* everyone managed to compile Eiffelstudio

==M2: May 2nd==
* define EMU-Protocol as completely as possible

==M3: May 23rd==
* emu-server prototype
* server-administration application

==M4: May 30th==
* new EMU project wizard
* project-management tool: EMU Project Settings

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

* [[User:Barnski| Bernhard Buss]] (project leader)
* [[User:Zandrea| Andrea Zimmermann]]
* [[User:Kamala| Claudia Kuster]]
* [[User:sdomenic| Domenic Schröder]]
* [[User:luc3D| Lucien Hansen]]
* [[User:ramons| Ramon Schwammberger]]
* [[User:Trickli| Tobias Rickli]]
* [[User:classens| Stephan Classen]]

EMU

2006-05-22T09:17:45Z

Barnski:

[[Category:Projects]]
[[Image:emu_group.png|right|frame| EMUs: Eiffel Multi Users]]

=Overview=
==Name==
EMU stands for '''Eiffel Multi User'''.
==Goal==
The aim of this project is to integrate a simple repository functionality into EiffelStudio.

=Software Requirements Specification=
You can find our SRS [[EMU/SRS|here]]

=Milestones=

==M1: April 25th==
* set up mailinglist es-emu@origo.ethz.ch ([[User:Schoelle|Bernd]])
* wiki page up to date
* everyone managed to compile Eiffelstudio

==M2: May 2nd==
* define EMU-Protocol as completely as possible

==M3: May 23rd==
* emu-server prototype
* server-administration application
* project-management client tool

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

* [[User:Barnski| Bernhard Buss]] (project leader)
* [[User:Zandrea| Andrea Zimmermann]]
* [[User:Kamala| Claudia Kuster]]
* [[User:sdomenic| Domenic Schröder]]
* [[User:luc3D| Lucien Hansen]]
* [[User:ramons| Ramon Schwammberger]]
* [[User:Trickli| Tobias Rickli]]
* [[User:classens| Stephan Classen]]

File:Emu group.png

2006-05-22T09:17:00Z

Barnski: A logo of EMU, Eiffel Multi User Project

A logo of EMU, Eiffel Multi User Project

EMU/Protocol

2006-05-22T09:01:50Z

Barnski: /* Project-Administration */

===Messages===
Messages are encapsulated within objects that are being transmitted over the network.
All messages inherit from EMU_MESSAGE.

====Client====
* login
version
projectname
username
password

* update_request
wants to receive new files

* unlock_request
wants to edit a code chunk

* upload_chunk
upload an edited chunk

* relock_request
wants to end locking session

* lock_status_request
get information about all classes

* online_status_request
get information about online users

* logout
informs about a logout of the client

====Server====
* login_accepted

* login_denied

* update
class files

* unlock_request_granted
checks status
sets status

* unlock_request_denied
status information

* lock_status
send status information of all classes

* online_status
send status of users online

* server_down
send information about server down

* send_message
send a message to all clients

====Server-Administration====
The administration tool is meant to maintain and control the server.

* admin_login
admin_name
admin_password

* admin_cmd
command to be executed? or attribute indicating which command should be executed?

====Project-Administration====
There are two ways of administrating an emu-project:

1. using the New EMU Project Wizard (create)

2. using the EMU Project Settings dialog (customize)

All messages inherit from EMU_PROJECT_MESSAGE, which has an attribute "project_name".

'''to server'''

* PROJECT_CREATE
project_password

* PROJECT_DELETE
project_password

* PROJECT_ADD_USER
project_password
user_name
user_password

* PROJECT_REMOVE_USER
project_password
user_name

* PROJECT_CLASS_LIST_REQUEST
project_password

* PROJECT_USER_LIST_REQUEST
project_password

* PROJECT_CLASS_UNLOCK_REQUEST
project_password
class_name

'''from server'''

* PROJECT_ERROR
error_code
error_msg

* PROJECT_OK
ok_code
ok_msg

* PROJECT_CLASS_LIST
class_list

* PROJECT_USER_LIST
user_list

EMU/Protocol

2006-05-22T08:59:59Z

Barnski:

===Messages===
Messages are encapsulated within objects that are being transmitted over the network.
All messages inherit from EMU_MESSAGE.

====Client====
* login
version
projectname
username
password

* update_request
wants to receive new files

* unlock_request
wants to edit a code chunk

* upload_chunk
upload an edited chunk

* relock_request
wants to end locking session

* lock_status_request
get information about all classes

* online_status_request
get information about online users

* logout
informs about a logout of the client

====Server====
* login_accepted

* login_denied

* update
class files

* unlock_request_granted
checks status
sets status

* unlock_request_denied
status information

* lock_status
send status information of all classes

* online_status
send status of users online

* server_down
send information about server down

* send_message
send a message to all clients

====Server-Administration====
The administration tool is meant to maintain and control the server.

* admin_login
admin_name
admin_password

* admin_cmd
command to be executed? or attribute indicating which command should be executed?

====Project-Administration====
There are two ways of administrating an emu-project:
1. using the New EMU Project Wizard (create)
2. using the EMU Project Settings dialog (customize)

All messages inherit from EMU_PROJECT_MESSAGE, which has an attribute "project_name".

'''to server'''

* PROJECT_CREATE
project_password

* PROJECT_DELETE
project_password

* PROJECT_ADD_USER
project_password
user_name
user_password

* PROJECT_REMOVE_USER
project_password
user_name

* PROJECT_CLASS_LIST_REQUEST
project_password

* PROJECT_USER_LIST_REQUEST
project_password

* PROJECT_CLASS_UNLOCK_REQUEST
project_password
class_name

'''from server'''

* PROJECT_ERROR
error_code
error_msg

* PROJECT_OK
ok_code
ok_msg

* PROJECT_CLASS_LIST
class_list

* PROJECT_USER_LIST
user_list

EMU/SRS

2006-05-22T08:44:02Z

Barnski: /* External Wizards */

=The Parts=
* EMU-Protocol
* EMU-Server
* EMU-Client
* ES integration

=Developer Requirements=
==EMU-Protocol==
defines Client/Server communication with
* client/server states
* available messages
* client/server actions

You can find our complete Protocol Specification [[EMU/Protocol|here]]

==EMU-Server==
* stores and manages code-repository
* synchronizes code of clients
* manages Locking-System
* Account-System
* project update
* add/create new code (classes)
* change-logging
* optional: Media-upload
* optional: BackUp-System
* optional: Release-versions
* optional: Server-Admin-Tool

===Locking-System===
* list of locked code
* check if code (class) is locked
* lock / unlock code (class)

===Code-Synchronization===
* broadcast code-changes
* bring user code up to date

===Account-System===
The server uses an account-system to organize its projects and users.
Every project has its own users assigned.

====Project-Accounts====
* project name
* project-admin(s)
* user lists
* project status
* editable / creatable with a project-admin-tool

====User-Accounts====
* usernames
* used for logins
* assign locked code & changes to users
* online status

===Change-Log===
The Log helps the users to know what has changed during their last login.
It is also used as a look-up table for synchronisation with the clients.
Every lock/unlock action is logged with following data:
* user name
* date and time
* type of action
* code element (class name)
Additionally, it provides the possibility for the user to add comments (e.g what he changed, what doesn't work yet...).

==EMU-Client==
* interface for IDE and server
* provides features to login and communicate with server on an abstract base
* upload/download code elements to/from server
* notify IDE of server-messages (code-updates)
* modular / independent of IDE-integration
* optional: upload media files

===IDE-Notifications===
The client needs to notify the IDE of the new changes.

==ES integration==
* minimal change to existing ES-classes and features.
* modular integration: activatable and removable / hideable
* only a few GUI changes

===ES-GUI Enhancement===

===Internal Dialogs===

===External Wizards===
====New EMU Project Wizard====
The following states need to be reflected by the wizard:
* emu-server hostname and port
* project-name and project-password
* add ES-libraries used
* add users and user-passwords

=User Requirements=
* easy to use
* target is a small project group of up to 20 developers.
* code synchronisation process mostly hidden from user
* minimal extra work (less total work)
* better efficiency

User talk:Philipp

2006-05-20T19:33:56Z

Barnski:

I found your improved scripts of mine and linked them in the automatic build script section.
I haven't tested them but I am sure they work nicely :-) Thanks. -- [[User:Barnski|Bernardo]]

Automatic Build Scripts

2006-05-20T19:30:29Z

Barnski: /* Windows */

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

== Windows ==

[[User:Barnski|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
'''Note:''' 
* 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]].
'''Update:''' 
* [[User:Philipp|Philipp Bönhof]] improved the scripts with customizable parameters. Download here: http://n.ethz.ch/student/pboenhof/autotest/Philipp_Eiffel_Compilation_Scripts.zip

== Linux ==

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

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).

=== Gentoo ===
Eiffelstudio, Gobo, edoc, ewg, eiffelmedia and eclipse edt ebuilds for gentoo, can be downloaded [http://n.ethz.ch/~philipkr/eiffel-ebuilds.tar.gz here] or from cvs:
cvs -z3 -d:pserver:anonymous@waldorf.inf.ethz.ch:/public-cvs co -deiffel-ebuilds student/eiffel-ebuilds
Installation instructions can be found [http://n.ethz.ch/~philipkr/eiffel-tools.html here]

== Mac OSX ==

To compile EiffelStudio under MacOS X with a pre-compiled Linux binary, Martin has developed a script. It is included in the EiffelStudio "compile from source" archive at http://eiffelsoftware.origo.ethz.ch/downloads/tools/experimental/.

Automatic Build Scripts

2006-05-20T19:27:23Z

Barnski: /* Windows */

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

== Windows ==

[[User:Barnski|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
'''Note:''' 
* 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]].
'''Update:''' 
* [[User:Philipp|Philipp]] improved the scripts with customizable parameters. Download here: http://n.ethz.ch/student/pboenhof/autotest/Philipp_Eiffel_Compilation_Scripts.zip

== Linux ==

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

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).

=== Gentoo ===
Eiffelstudio, Gobo, edoc, ewg, eiffelmedia and eclipse edt ebuilds for gentoo, can be downloaded [http://n.ethz.ch/~philipkr/eiffel-ebuilds.tar.gz here] or from cvs:
cvs -z3 -d:pserver:anonymous@waldorf.inf.ethz.ch:/public-cvs co -deiffel-ebuilds student/eiffel-ebuilds
Installation instructions can be found [http://n.ethz.ch/~philipkr/eiffel-tools.html here]

== Mac OSX ==

To compile EiffelStudio under MacOS X with a pre-compiled Linux binary, Martin has developed a script. It is included in the EiffelStudio "compile from source" archive at http://eiffelsoftware.origo.ethz.ch/downloads/tools/experimental/.

Automatic Build Scripts

2006-05-20T19:26:06Z

Barnski: /* Windows */

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

== Windows ==

[[User:Barnski|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
'''Note:''' 
* 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]].
'''Update:''' 
* [[User:Philipp|Philipp] improved the scripts with customizable parameters. Download here: http://n.ethz.ch/student/pboenhof/autotest/Philipp_Eiffel_Compilation_Scripts.zip

== Linux ==

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

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).

=== Gentoo ===
Eiffelstudio, Gobo, edoc, ewg, eiffelmedia and eclipse edt ebuilds for gentoo, can be downloaded [http://n.ethz.ch/~philipkr/eiffel-ebuilds.tar.gz here] or from cvs:
cvs -z3 -d:pserver:anonymous@waldorf.inf.ethz.ch:/public-cvs co -deiffel-ebuilds student/eiffel-ebuilds
Installation instructions can be found [http://n.ethz.ch/~philipkr/eiffel-tools.html here]

== Mac OSX ==

To compile EiffelStudio under MacOS X with a pre-compiled Linux binary, Martin has developed a script. It is included in the EiffelStudio "compile from source" archive at http://eiffelsoftware.origo.ethz.ch/downloads/tools/experimental/.

EMU

2006-05-20T18:35:53Z

Barnski: /* Milestones */

[[Category:Projects]]

=Overview=
==Name==
EMU stands for '''Eiffel Multi User'''.
==Goal==
The aim of this project is to integrate a simple repository functionality into EiffelStudio.

=Software Requirements Specification=
You can find our SRS [[EMU/SRS|here]]

=Milestones=

==M1: April 25th==
* set up mailinglist es-emu@origo.ethz.ch ([[User:Schoelle|Bernd]])
* wiki page up to date
* everyone managed to compile Eiffelstudio

==M2: May 2nd==
* define EMU-Protocol as completely as possible

==M3: May 23rd==
* emu-server prototype
* server-administration application
* project-management client tool

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

* [[User:Barnski| Bernhard Buss]] (project leader)
* [[User:Zandrea| Andrea Zimmermann]]
* [[User:Kamala| Claudia Kuster]]
* [[User:sdomenic| Domenic Schröder]]
* [[User:luc3D| Lucien Hansen]]
* [[User:ramons| Ramon Schwammberger]]
* [[User:Trickli| Tobias Rickli]]
* [[User:classens| Stephan Classen]]

EMU/Protocol

2006-05-18T07:12:41Z

Barnski: /* Messages */

===Messages===
Messages are encapsulated within objects that are being transmitted over the network.

====Client====
* login
version
projectname
username
password

* update_request
wants to receive new files

* unlock_request
wants to edit a code chunk

* upload_chunk
upload an edited chunk

* relock_request
wants to end locking session

* lock_status_request
get information about all classes

* online_status_request
get information about online users

* logout
informs about a logout of the client

====Server====
* login_accepted

* login_denied

* update
class files

* unlock_request_granted
checks status
sets status

* unlock_request_denied
status information

* lock_status
send status information of all classes

* online_status
send status of users online

* server_down
send information about server down

* send_message
send a message to all clients

EMU/Protocol

2006-05-17T17:38:14Z

Barnski: /* Server */

EMU/Protocol

2006-05-17T17:37:36Z

Barnski: /* Client */

===Messages===
Messages are encapsulated within objects that are being transmitted over the network.

====Client====
* login
version
projectname
username
password

* update_request
wants to receive new files

* unlock_request
wants to edit a code chunk

* upload_chunk
upload an edited chunk

* relock_request
wants to end locking session

* lock_status_request
get information about all classes

* online_status_request
get information about online users

* logout
informs about a logout of the client

====Server====
login_accepted

login_denied

update
class files

unlock_request_granted
checks status
sets status

unlock_request_denied
status information

lock_status
send status information of all classes

online_status
send status of users online

server_down
send information about server down

send_message
send a message to all clients

EMU/Protocol

2006-05-17T17:33:52Z

Barnski: /* Client */

===Messages===
Messages are encapsulated within objects that are being transmitted over the network.

====Client====
login
version
projectname
username
password

update_request
wants to receive new files

unlock_request
wants to edit a code chunk

upload_chunk
upload an edited chunk

relock_request
wants to end locking session

lock_status_request
get information about all classes

online_status_request
get information about online users

logout
informs about a logout of the client

====Server====
login_accepted

login_denied

update
class files

unlock_request_granted
checks status
sets status

unlock_request_denied
status information

lock_status
send status information of all classes

online_status
send status of users online

server_down
send information about server down

send_message
send a message to all clients

EMU/Protocol

2006-05-17T17:32:52Z

Barnski: /* Messages */

EMU/SRS

2006-05-17T17:29:27Z

Barnski: /* EMU-Protocol */

=The Parts=
* EMU-Protocol
* EMU-Server
* EMU-Client
* ES integration

=Developer Requirements=
==EMU-Protocol==
defines Client/Server communication with
* client/server states
* available messages
* client/server actions

You can find our complete Protocol Specification [[EMU/Protocol|here]]

==EMU-Server==
* stores and manages code-repository
* synchronizes code of clients
* manages Locking-System
* Account-System
* project update
* add/create new code (classes)
* change-logging
* optional: Media-upload
* optional: BackUp-System
* optional: Release-versions
* optional: Server-Admin-Tool

===Locking-System===
* list of locked code
* check if code (class) is locked
* lock / unlock code (class)

===Code-Synchronization===
* broadcast code-changes
* bring user code up to date

===Account-System===
The server uses an account-system to organize its projects and users.
Every project has its own users assigned.

====Project-Accounts====
* project name
* project-admin(s)
* user lists
* project status
* editable / creatable with a project-admin-tool

====User-Accounts====
* usernames
* used for logins
* assign locked code & changes to users
* online status

===Change-Log===
The Log helps the users to know what has changed during their last login.
It is also used as a look-up table for synchronisation with the clients.
Every lock/unlock action is logged with following data:
* user name
* date and time
* type of action
* code element (class name)
Additionally, it provides the possibility for the user to add comments (e.g what he changed, what doesn't work yet...).

==EMU-Client==
* interface for IDE and server
* provides features to login and communicate with server on an abstract base
* upload/download code elements to/from server
* notify IDE of server-messages (code-updates)
* modular / independent of IDE-integration
* optional: upload media files

===IDE-Notifications===
The client needs to notify the IDE of the new changes.

==ES integration==
* minimal change to existing ES-classes and features.
* modular integration: activatable and removable / hideable
* only a few GUI changes

===ES-GUI Enhancement===

===Internal Dialogs===

===External Wizards===

=User Requirements=
* easy to use
* target is a small project group of up to 20 developers.
* code synchronisation process mostly hidden from user
* minimal extra work (less total work)
* better efficiency

EMU/Protocol

2006-05-17T17:28:16Z

Barnski:

===Messages===
====Connection Establishment====

====Synchronization Check====

====Data Transfer====

====Connection Closure====

EMU/SRS

2006-05-17T17:28:02Z

Barnski: /* EMU-Protocol */

=The Parts=
* EMU-Protocol
* EMU-Server
* EMU-Client
* ES integration

=Developer Requirements=
==EMU-Protocol==
defines Client/Server communication with
* client/server states
* available messages
* client/server actions

You can find our Protocol Specification [[EMU/Protocol]]here

==EMU-Server==
* stores and manages code-repository
* synchronizes code of clients
* manages Locking-System
* Account-System
* project update
* add/create new code (classes)
* change-logging
* optional: Media-upload
* optional: BackUp-System
* optional: Release-versions
* optional: Server-Admin-Tool

===Locking-System===
* list of locked code
* check if code (class) is locked
* lock / unlock code (class)

===Code-Synchronization===
* broadcast code-changes
* bring user code up to date

===Account-System===
The server uses an account-system to organize its projects and users.
Every project has its own users assigned.

====Project-Accounts====
* project name
* project-admin(s)
* user lists
* project status
* editable / creatable with a project-admin-tool

====User-Accounts====
* usernames
* used for logins
* assign locked code & changes to users
* online status

===Change-Log===
The Log helps the users to know what has changed during their last login.
It is also used as a look-up table for synchronisation with the clients.
Every lock/unlock action is logged with following data:
* user name
* date and time
* type of action
* code element (class name)
Additionally, it provides the possibility for the user to add comments (e.g what he changed, what doesn't work yet...).

==EMU-Client==
* interface for IDE and server
* provides features to login and communicate with server on an abstract base
* upload/download code elements to/from server
* notify IDE of server-messages (code-updates)
* modular / independent of IDE-integration
* optional: upload media files

===IDE-Notifications===
The client needs to notify the IDE of the new changes.

==ES integration==
* minimal change to existing ES-classes and features.
* modular integration: activatable and removable / hideable
* only a few GUI changes

===ES-GUI Enhancement===

===Internal Dialogs===

===External Wizards===

=User Requirements=
* easy to use
* target is a small project group of up to 20 developers.
* code synchronisation process mostly hidden from user
* minimal extra work (less total work)
* better efficiency

EMU/SRS

2006-05-02T12:08:20Z

Barnski: /* ES integration */

=The Parts=
* EMU-Protocol
* EMU-Server
* EMU-Client
* ES integration

=Developer Requirements=
==EMU-Protocol==
defines Client/Server communication with
* client/server states
* available messages
* client/server actions

===Messages===
====Connection Establishment====

====Synchronization Check====

====Data Transfer====

====Connection Closure====

==EMU-Server==
* stores and manages code-repository
* synchronizes code of clients
* manages Locking-System
* Account-System
* project update
* add/create new code (classes)
* change-logging
* optional: Media-upload
* optional: BackUp-System
* optional: Release-versions
* optional: Server-Admin-Tool

===Locking-System===
* list of locked code
* check if code (class) is locked
* lock / unlock code (class)

===Code-Synchronization===
* broadcast code-changes
* bring user code up to date

===Account-System===
The server uses an account-system to organize its projects and users.
Every project has its own users assigned.

====Project-Accounts====
* project name
* project-admin(s)
* user lists
* project status
* editable / creatable with a project-admin-tool

====User-Accounts====
* usernames
* used for logins
* assign locked code & changes to users
* online status

===Change-Log===
The Log helps the users to know what has changed during their last login.
It is also used as a look-up table for synchronisation with the clients.
Every lock/unlock action is logged with following data:
* user name
* date and time
* type of action
* code element (class name)
Additionally, it provides the possibility for the user to add comments (e.g what he changed, what doesn't work yet...).

==EMU-Client==
* interface for IDE and server
* provides features to login and communicate with server on an abstract base
* upload/download code elements to/from server
* notify IDE of server-messages (code-updates)
* modular / independent of IDE-integration
* optional: upload media files

===IDE-Notifications===
The client needs to notify the IDE of the new changes.

==ES integration==
* minimal change to existing ES-classes and features.
* modular integration: activatable and removable / hideable
* only a few GUI changes

===ES-GUI Enhancement===

===Internal Dialogs===

===External Wizards===

=User Requirements=
* easy to use
* target is a small project group of up to 20 developers.
* code synchronisation process mostly hidden from user
* minimal extra work (less total work)
* better efficiency

EMU/SRS

2006-05-02T12:05:36Z

Barnski: /* EMU-Protocol */

=The Parts=
* EMU-Protocol
* EMU-Server
* EMU-Client
* ES integration

=Developer Requirements=
==EMU-Protocol==
defines Client/Server communication with
* client/server states
* available messages
* client/server actions

===Messages===
====Connection Establishment====

====Synchronization Check====

====Data Transfer====

====Connection Closure====

==EMU-Server==
* stores and manages code-repository
* synchronizes code of clients
* manages Locking-System
* Account-System
* project update
* add/create new code (classes)
* change-logging
* optional: Media-upload
* optional: BackUp-System
* optional: Release-versions
* optional: Server-Admin-Tool

===Locking-System===
* list of locked code
* check if code (class) is locked
* lock / unlock code (class)

===Code-Synchronization===
* broadcast code-changes
* bring user code up to date

===Account-System===
The server uses an account-system to organize its projects and users.
Every project has its own users assigned.

====Project-Accounts====
* project name
* project-admin(s)
* user lists
* project status
* editable / creatable with a project-admin-tool

====User-Accounts====
* usernames
* used for logins
* assign locked code & changes to users
* online status

===Change-Log===
The Log helps the users to know what has changed during their last login.
It is also used as a look-up table for synchronisation with the clients.
Every lock/unlock action is logged with following data:
* user name
* date and time
* type of action
* code element (class name)
Additionally, it provides the possibility for the user to add comments (e.g what he changed, what doesn't work yet...).

==EMU-Client==
* interface for IDE and server
* provides features to login and communicate with server on an abstract base
* upload/download code elements to/from server
* notify IDE of server-messages (code-updates)
* modular / independent of IDE-integration
* optional: upload media files

===IDE-Notifications===
The client needs to notify the IDE of the new changes.

==ES integration==
* minimal change to existing ES-classes and features.
* modular integration: activatable and removable / hideable

=User Requirements=
* easy to use
* target is a small project group of up to 20 developers.
* code synchronisation process mostly hidden from user
* minimal extra work (less total work)
* better efficiency

EMU

2006-04-29T12:10:05Z

Barnski: /* M2: May ??? */ new milestone set

[[Category:Projects]]

=Overview=
==Name==
EMU stands for '''Eiffel Multi User'''.
==Goal==
The aim of this project is to integrate a simple repository functionality into EiffelStudio.

=Software Requirements Specification=
You can find our SRS [[EMU/SRS|here]]

=Milestones=

==M1: April 25th==
* set up mailinglist es-emu@origo.ethz.ch ([[User:Schoelle|Bernd]])
* wiki page up to date
* everyone managed to compile Eiffelstudio

==M2: May 2nd ==
* define EMU-Protocol as completely as possible

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

* [[User:Barnski| Bernhard Buss]] (project leader)
* [[User:Zandrea| Andrea Zimmermann]]
* [[User:Kamala| Claudia Kuster]]
* [[User:sdomenic| Domenic Schröder]]
* [[User:luc3D| Lucien Hansen]]
* [[User:ramons| Ramon Schwammberger]]
* [[User:Trickli| Tobias Rickli]]
* [[User:classens| Stephan Classen]]

EMU/SRS

2006-04-28T22:57:10Z

Barnski: /* Change-Log */

=The Parts=
* EMU-Protocol
* EMU-Server
* EMU-Client
* ES integration

=Developer Requirements=
==EMU-Protocol==
defines Client/Server communication with
* client/server states
* available messages
* client/server actions

==EMU-Server==
* stores and manages code-repository
* synchronizes code of clients
* manages Locking-System
* Account-System
* project update
* add/create new code (classes)
* change-logging
* optional: Media-upload
* optional: BackUp-System
* optional: Release-versions
* optional: Server-Admin-Tool

===Locking-System===
* list of locked code
* check if code (class) is locked
* lock / unlock code (class)

===Code-Synchronization===
* broadcast code-changes
* bring user code up to date

===Account-System===
The server uses an account-system to organize its projects and users.
Every project has its own users assigned.

====Project-Accounts====
* project name
* project-admin(s)
* user lists
* project status
* editable / creatable with a project-admin-tool

====User-Accounts====
* usernames
* used for logins
* assign locked code & changes to users
* online status

===Change-Log===
The Log helps the users to know what has changed during their last login.
It is also used as a look-up table for synchronisation with the clients.
Every lock/unlock action is logged with following data:
* user name
* date and time
* type of action
* code element (class name)
Additionally, it provides the possibility for the user to add comments (e.g what he changed, what doesn't work yet...).

==EMU-Client==
* interface for IDE and server
* provides features to login and communicate with server on an abstract base
* upload/download code elements to/from server
* notify IDE of server-messages (code-updates)
* modular / independent of IDE-integration
* optional: upload media files

===IDE-Notifications===
The client needs to notify the IDE of the new changes.

==ES integration==
* minimal change to existing ES-classes and features.
* modular integration: activatable and removable / hideable

=User Requirements=
* easy to use
* target is a small project group of up to 20 developers.
* code synchronisation process mostly hidden from user
* minimal extra work (less total work)
* better efficiency

EMU/SRS

2006-04-27T18:10:16Z

Barnski: /* The Parts */ -> ES integration

=The Parts=
* EMU-Protocol
* EMU-Server
* EMU-Client
* ES integration

=Developer Requirements=
==EMU-Protocol==
defines Client/Server communication with
* client/server states
* available messages
* client/server actions

==EMU-Server==
* stores and manages code-repository
* synchronizes code of clients
* manages Locking-System
* Account-System
* project update
* add/create new code (classes)
* change-logging
* optional: Media-upload
* optional: BackUp-System
* optional: Release-versions
* optional: Server-Admin-Tool

===Locking-System===
* list of locked code
* check if code (class) is locked
* lock / unlock code (class)

===Code-Synchronization===
* broadcast code-changes
* bring user code up to date

===Account-System===
The server uses an account-system to organize its projects and users.
Every project has its own users assigned.

====Project-Accounts====
* project name
* project-admin(s)
* user lists
* project status
* editable / creatable with a project-admin-tool

====User-Accounts====
* usernames
* used for logins
* assign locked code & changes to users
* online status

==Change-Log==
The Log helps the users to know what has changed during their last login.
It is also used as a look-up table for synchronisation with the clients.
Every lock/unlock action is logged with following data:
* user name
* date and time
* type of action
* code element (class name)
Additionally, it provides the possibility for the user to add comments (e.g what he changed, what doesn't work yet...).

==EMU-Client==
* interface for IDE and server
* provides features to login and communicate with server on an abstract base
* upload/download code elements to/from server
* notify IDE of server-messages (code-updates)
* modular / independent of IDE-integration
* optional: upload media files

===IDE-Notifications===
The client needs to notify the IDE of the new changes.

==ES integration==
* minimal change to existing ES-classes and features.
* modular integration: activatable and removable / hideable

=User Requirements=
* easy to use
* target is a small project group of up to 20 developers.
* code synchronisation process mostly hidden from user
* minimal extra work (less total work)
* better efficiency

EMU/SRS

2006-04-27T18:09:47Z

Barnski: /* EMU-IDE integration */ changed to: ES integration

=The Parts=
* EMU-Protocol
* EMU-Server
* EMU-Client
* EMU-IDE integration

=Developer Requirements=
==EMU-Protocol==
defines Client/Server communication with
* client/server states
* available messages
* client/server actions

==EMU-Server==
* stores and manages code-repository
* synchronizes code of clients
* manages Locking-System
* Account-System
* project update
* add/create new code (classes)
* change-logging
* optional: Media-upload
* optional: BackUp-System
* optional: Release-versions
* optional: Server-Admin-Tool

===Locking-System===
* list of locked code
* check if code (class) is locked
* lock / unlock code (class)

===Code-Synchronization===
* broadcast code-changes
* bring user code up to date

===Account-System===
The server uses an account-system to organize its projects and users.
Every project has its own users assigned.

====Project-Accounts====
* project name
* project-admin(s)
* user lists
* project status
* editable / creatable with a project-admin-tool

====User-Accounts====
* usernames
* used for logins
* assign locked code & changes to users
* online status

==Change-Log==
The Log helps the users to know what has changed during their last login.
It is also used as a look-up table for synchronisation with the clients.
Every lock/unlock action is logged with following data:
* user name
* date and time
* type of action
* code element (class name)
Additionally, it provides the possibility for the user to add comments (e.g what he changed, what doesn't work yet...).

==EMU-Client==
* interface for IDE and server
* provides features to login and communicate with server on an abstract base
* upload/download code elements to/from server
* notify IDE of server-messages (code-updates)
* modular / independent of IDE-integration
* optional: upload media files

===IDE-Notifications===
The client needs to notify the IDE of the new changes.

==ES integration==
* minimal change to existing ES-classes and features.
* modular integration: activatable and removable / hideable

=User Requirements=
* easy to use
* target is a small project group of up to 20 developers.
* code synchronisation process mostly hidden from user
* minimal extra work (less total work)
* better efficiency

EMU/SRS

2006-04-27T18:07:33Z

Barnski: /* Change-Log */

=The Parts=
* EMU-Protocol
* EMU-Server
* EMU-Client
* EMU-IDE integration

=Developer Requirements=
==EMU-Protocol==
defines Client/Server communication with
* client/server states
* available messages
* client/server actions

==EMU-Server==
* stores and manages code-repository
* synchronizes code of clients
* manages Locking-System
* Account-System
* project update
* add/create new code (classes)
* change-logging
* optional: Media-upload
* optional: BackUp-System
* optional: Release-versions
* optional: Server-Admin-Tool

===Locking-System===
* list of locked code
* check if code (class) is locked
* lock / unlock code (class)

===Code-Synchronization===
* broadcast code-changes
* bring user code up to date

===Account-System===
The server uses an account-system to organize its projects and users.
Every project has its own users assigned.

====Project-Accounts====
* project name
* project-admin(s)
* user lists
* project status
* editable / creatable with a project-admin-tool

====User-Accounts====
* usernames
* used for logins
* assign locked code & changes to users
* online status

==Change-Log==
The Log helps the users to know what has changed during their last login.
It is also used as a look-up table for synchronisation with the clients.
Every lock/unlock action is logged with following data:
* user name
* date and time
* type of action
* code element (class name)
Additionally, it provides the possibility for the user to add comments (e.g what he changed, what doesn't work yet...).

==EMU-Client==
* interface for IDE and server
* provides features to login and communicate with server on an abstract base
* upload/download code elements to/from server
* notify IDE of server-messages (code-updates)
* modular / independent of IDE-integration
* optional: upload media files

===IDE-Notifications===
The client needs to notify the IDE of the new changes.

==EMU-IDE integration==
* minimal change to existing ES-classes and features.
* modular integration: activatable and removable / hideable

=User Requirements=
* easy to use
* target is a small project group of up to 20 developers.
* code synchronisation process mostly hidden from user
* minimal extra work (less total work)
* better efficiency

EMU/SRS

2006-04-27T18:05:48Z

Barnski: /* Change-Log */

=The Parts=
* EMU-Protocol
* EMU-Server
* EMU-Client
* EMU-IDE integration

=Developer Requirements=
==EMU-Protocol==
defines Client/Server communication with
* client/server states
* available messages
* client/server actions

==EMU-Server==
* stores and manages code-repository
* synchronizes code of clients
* manages Locking-System
* Account-System
* project update
* add/create new code (classes)
* change-logging
* optional: Media-upload
* optional: BackUp-System
* optional: Release-versions
* optional: Server-Admin-Tool

===Locking-System===
* list of locked code
* check if code (class) is locked
* lock / unlock code (class)

===Code-Synchronization===
* broadcast code-changes
* bring user code up to date

===Account-System===
The server uses an account-system to organize its projects and users.
Every project has its own users assigned.

====Project-Accounts====
* project name
* project-admin(s)
* user lists
* project status
* editable / creatable with a project-admin-tool

====User-Accounts====
* usernames
* used for logins
* assign locked code & changes to users
* online status

==Change-Log==
Every lock/unlock action is logged with following data:
* user name
* date and time
* type of action
* code element (class name)
Additionally, it provides the possibility for the user to add comments (e.g what he changed, what doesn't work yet...)
The Log helps the users to know what has changed during their last login.

==EMU-Client==
* interface for IDE and server
* provides features to login and communicate with server on an abstract base
* upload/download code elements to/from server
* notify IDE of server-messages (code-updates)
* modular / independent of IDE-integration
* optional: upload media files

===IDE-Notifications===
The client needs to notify the IDE of the new changes.

==EMU-IDE integration==
* minimal change to existing ES-classes and features.
* modular integration: activatable and removable / hideable

=User Requirements=
* easy to use
* target is a small project group of up to 20 developers.
* code synchronisation process mostly hidden from user
* minimal extra work (less total work)
* better efficiency

EMU/SRS

2006-04-27T18:02:36Z

Barnski: /* Change-Log */ typo

=The Parts=
* EMU-Protocol
* EMU-Server
* EMU-Client
* EMU-IDE integration

=Developer Requirements=
==EMU-Protocol==
defines Client/Server communication with
* client/server states
* available messages
* client/server actions

==EMU-Server==
* stores and manages code-repository
* synchronizes code of clients
* manages Locking-System
* Account-System
* project update
* add/create new code (classes)
* change-logging
* optional: Media-upload
* optional: BackUp-System
* optional: Release-versions
* optional: Server-Admin-Tool

===Locking-System===
* list of locked code
* check if code (class) is locked
* lock / unlock code (class)

===Code-Synchronization===
* broadcast code-changes
* bring user code up to date

===Account-System===
The server uses an account-system to organize its projects and users.
Every project has its own users assigned.

====Project-Accounts====
* project name
* project-admin(s)
* user lists
* project status
* editable / creatable with a project-admin-tool

====User-Accounts====
* usernames
* used for logins
* assign locked code & changes to users
* online status

==Change-Log==
Every lock/unlock action is logged with following data:
* user name
* date and time
* type of action
* code element (class name)

==EMU-Client==
* interface for IDE and server
* provides features to login and communicate with server on an abstract base
* upload/download code elements to/from server
* notify IDE of server-messages (code-updates)
* modular / independent of IDE-integration
* optional: upload media files

===IDE-Notifications===
The client needs to notify the IDE of the new changes.

==EMU-IDE integration==
* minimal change to existing ES-classes and features.
* modular integration: activatable and removable / hideable

=User Requirements=
* easy to use
* target is a small project group of up to 20 developers.
* code synchronisation process mostly hidden from user
* minimal extra work (less total work)
* better efficiency

EMU

2006-04-27T11:05:56Z

Barnski: /* EMU-Client */

[[Category:Projects]]

=Overview=
==Name==
EMU stands for '''Eiffel Multi User'''.
==Goal==
The aim of this project is to integrate a simple repository functionality into EiffelStudio.

=Software Requirements Specification=
==The Parts==
* EMU-Protocol
* EMU-Server
* EMU-Client
* EMU-IDE integration

==Developer Requirements==
===EMU-Protocol===
defines Client/Server communication with
* client/server states
* available messages
* client/server actions

===EMU-Server===
* stores and manages code-repository
* synchronizes code of clients
* manages Locking-System
* Account-System
* project update
* add/create new code (classes)
* change-logging
* optional: Media-upload
* optional: BackUp-System
* optional: Release-versions
* optional: Server-Admin-Tool

====Locking-System====
* list of locked code
* check if code (class) is locked
* lock / unlock code (class)

====Code-Synchronization====
* broadcast code-changes
* bring user code up to date

====Account-System====
The server uses an account-system to organize its projects and users.
Every project has its own users assigned.

=====Project-Accounts=====
* project name
* project-admin(s)
* user lists
* project status
* editable / creatable with a project-admin-tool

=====User-Accounts=====
* usernames
* used for logins
* assign locked code & changes to users
* online status

===Change-Log===
Every lock/unlock action is locked with following data:
* user name
* date and time
* type of action
* code element (class name)

===EMU-Client===
* interface for IDE and server
* provides features to login and communicate with server on an abstract base
* upload/download code elements to/from server
* notify IDE of server-messages (code-updates)
* modular / independent of IDE-integration
* optional: upload media files

====IDE-Notifications====
The client needs to notify the IDE of the new changes.

===EMU-IDE integration===
* minimal change to existing ES-classes and features.
* modular integration: activatable and removable / hideable

==User Requirements==
* easy to use
* target is a small project group of up to 20 developers.
* code synchronisation process mostly hidden from user
* minimal extra work (less total work)
* better efficiency

=Milestones=

==M1: April 25th==
* set up mailinglist es-emu@origo.ethz.ch ([[User:Schoelle|Bernd]])
* wiki page up to date
* everyone managed to compile Eiffelstudio

==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-emu es-emu@origo.ethz.ch]

* [[User:Barnski| Bernhard Buss]] (project leader)
* [[User:Zandrea| Andrea Zimmermann]]
* [[User:Kamala| Claudia Kuster]]
* [[User:sdomenic| Domenic Schröder]]
* [[User:luc3D| Lucien Hansen]]
* [[User:ramons| Ramon Schwammberger]]
* [[User:Trickli| Tobias Rickli]]
* [[User:classens| Stephan Classen]]

EMU

2006-04-27T10:51:07Z

Barnski: /* =Change-Log */

[[Category:Projects]]

=Overview=
==Name==
EMU stands for '''Eiffel Multi User'''.
==Goal==
The aim of this project is to integrate a simple repository functionality into EiffelStudio.

=Software Requirements Specification=
==The Parts==
* EMU-Protocol
* EMU-Server
* EMU-Client
* EMU-IDE integration

==Developer Requirements==
===EMU-Protocol===
defines Client/Server communication with
* client/server states
* available messages
* client/server actions

===EMU-Server===
* stores and manages code-repository
* synchronizes code of clients
* manages Locking-System
* Account-System
* project update
* add/create new code (classes)
* change-logging
* optional: Media-upload
* optional: BackUp-System
* optional: Release-versions
* optional: Server-Admin-Tool

====Locking-System====
* list of locked code
* check if code (class) is locked
* lock / unlock code (class)

====Code-Synchronization====
* broadcast code-changes
* bring user code up to date

====Account-System====
The server uses an account-system to organize its projects and users.
Every project has its own users assigned.

=====Project-Accounts=====
* project name
* project-admin(s)
* user lists
* project status
* editable / creatable with a project-admin-tool

=====User-Accounts=====
* usernames
* used for logins
* assign locked code & changes to users
* online status

===Change-Log===
Every lock/unlock action is locked with following data:
* user name
* date and time
* type of action
* code element (class name)

===EMU-Client===
* interface for IDE and server
* modular / independent of IDE-integration

===EMU-IDE integration===
* minimal change to existing ES-classes and features.
* modular integration: activatable and removable / hideable

==User Requirements==
* easy to use
* target is a small project group of up to 20 developers.
* code synchronisation process mostly hidden from user
* minimal extra work (less total work)
* better efficiency

=Milestones=

==M1: April 25th==
* set up mailinglist es-emu@origo.ethz.ch ([[User:Schoelle|Bernd]])
* wiki page up to date
* everyone managed to compile Eiffelstudio

==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-emu es-emu@origo.ethz.ch]

* [[User:Barnski| Bernhard Buss]] (project leader)
* [[User:Zandrea| Andrea Zimmermann]]
* [[User:Kamala| Claudia Kuster]]
* [[User:sdomenic| Domenic Schröder]]
* [[User:luc3D| Lucien Hansen]]
* [[User:ramons| Ramon Schwammberger]]
* [[User:Trickli| Tobias Rickli]]
* [[User:classens| Stephan Classen]]

EMU

2006-04-27T10:50:52Z

Barnski: /* EMU-Server */

[[Category:Projects]]

=Overview=
==Name==
EMU stands for '''Eiffel Multi User'''.
==Goal==
The aim of this project is to integrate a simple repository functionality into EiffelStudio.

=Software Requirements Specification=
==The Parts==
* EMU-Protocol
* EMU-Server
* EMU-Client
* EMU-IDE integration

==Developer Requirements==
===EMU-Protocol===
defines Client/Server communication with
* client/server states
* available messages
* client/server actions

===EMU-Server===
* stores and manages code-repository
* synchronizes code of clients
* manages Locking-System
* Account-System
* project update
* add/create new code (classes)
* change-logging
* optional: Media-upload
* optional: BackUp-System
* optional: Release-versions
* optional: Server-Admin-Tool

====Locking-System====
* list of locked code
* check if code (class) is locked
* lock / unlock code (class)

====Code-Synchronization====
* broadcast code-changes
* bring user code up to date

====Account-System====
The server uses an account-system to organize its projects and users.
Every project has its own users assigned.

=====Project-Accounts=====
* project name
* project-admin(s)
* user lists
* project status
* editable / creatable with a project-admin-tool

=====User-Accounts=====
* usernames
* used for logins
* assign locked code & changes to users
* online status

====Change-Log===
Every lock/unlock action is locked with following data:
* user name
* date and time
* type of action
* code element (class name)

===EMU-Client===
* interface for IDE and server
* modular / independent of IDE-integration

===EMU-IDE integration===
* minimal change to existing ES-classes and features.
* modular integration: activatable and removable / hideable

==User Requirements==
* easy to use
* target is a small project group of up to 20 developers.
* code synchronisation process mostly hidden from user
* minimal extra work (less total work)
* better efficiency

=Milestones=

==M1: April 25th==
* set up mailinglist es-emu@origo.ethz.ch ([[User:Schoelle|Bernd]])
* wiki page up to date
* everyone managed to compile Eiffelstudio

==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-emu es-emu@origo.ethz.ch]

* [[User:Barnski| Bernhard Buss]] (project leader)
* [[User:Zandrea| Andrea Zimmermann]]
* [[User:Kamala| Claudia Kuster]]
* [[User:sdomenic| Domenic Schröder]]
* [[User:luc3D| Lucien Hansen]]
* [[User:ramons| Ramon Schwammberger]]
* [[User:Trickli| Tobias Rickli]]
* [[User:classens| Stephan Classen]]

EMU

2006-04-24T21:47:32Z

Barnski: /* Team */ typo

EMU

2006-04-24T21:44:21Z

Barnski:

EMU

2006-04-24T21:43:23Z

Barnski:

EMU

2006-04-24T21:38:46Z

Barnski:

[[Category:Projects]]

=Overview=
Eiffel Multi User: The aim of this project is to integrate a repository functionality into EiffelStudio.

=Software Requirements Specification=
==The Parts==
* EMU-Protocol
* EMU-Server
* EMU-Client
* EMU-IDE integration

==Developer Requirements==
===EMU-Protocol===
defines Client/Server communication with
* client/server states
* available messages
* client/server actions

===EMU-Server===
* stores and manages code-repository
* synchronizes code of clients
* manages Locking-System

===EMU-Client===
* interface for IDE and server
* modular / independent of IDE-integration

===EMU-IDE integration===
* minimal change to existing ES-classes and features.
* modular integration: activatable and removable / hideable

==User Requirements==
* easy to use
* target is a small project group of up to 20 developers.
* code synchronisation process mostly hidden from user
* minimal extra work (less total work)
* better efficiency

=Milestones=

==M1: April 25th==
* set up mailinglist es-emu@origo.ethz.ch ([[User:Schoelle|Bernd]])
* wiki page up to date
* everyone managed to compile Eiffelstudio

==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-emu es-emu@origo.ethz.ch]

* [[User:Barnski| Bernhard Buss]] (project leader)
* [[User:Zandrea| Andrea Zimmermann]]
* [[User:Kamala| Claudia Kuster]]
* [[User:sdomenic| Domenic Schröder]]
* [[User:luc3D| Lucien Hansen]]
* [[User:ramons| Ramon Schwammberger]]
* [[User:Trickli| Tobias Rickli]]
* [[User:classens| Stephan Classen]]

EMU

2006-04-24T21:36:39Z

Barnski:

Talk:EMU

2006-04-21T22:33:46Z

Barnski:

'''[[User:Patrickr|Patrickr]] 18:11, 21 April 2006 (CEST)'''

Do you plan to write your own repository system? I think it would be nicer if you could support already existing repositories like Subversion.

'''[[User:Barnski|Bernhard Buss]] 20:05, 21 April 2006 (GMT+1)'''

We plan to make our own server, that will handle the code repository. If we were to use subversion as server we would fail our project goal: to provide more functionality than the current solutions. Although we do not know the full capacities of svn, I think it would not allow us to handle code synchronisation on a locking-base, where possibly not only whole classes are lockable, but also features.
Nevertheless we will make sure that we design our components in a way to guarantee maximal reusability, such that the emu-client could be replaced by a svn-client for example.

Maybe this quote helps to distinguish emu from svn:
"What is SVN?"
[...]
"Some version control systems are also software configuration management (SCM) systems. These systems are specifically tailored to manage trees of source code, and have many features that are specific to software development—such as natively understanding programming languages, or supplying tools for building software. Subversion, however, is not one of these systems. It is a general system that can be used to manage any collection of files. For you, those files might be source code—for others, anything from grocery shopping lists to digital video mixdowns and beyond."

-from http://svnbook.red-bean.com

Consider EMU as such a SCM system.

Talk:EMU

2006-04-21T18:11:48Z

Barnski:

Talk:EMU

2006-04-21T18:11:35Z

Barnski:

Talk:EMU

2006-04-21T18:10:36Z

Barnski:

'''[[User:Patrickr|Patrickr]] 18:11, 21 April 2006 (CEST)'''

Do you plan to write your own repository system? I think it would be nicer if you could support already existing repositories like Subversion.

We plan to make our own server, that will handle the code repository. If we were to use subversion as server we would fail our project goal: to provide more functionality than the current solutions. Although we do not know the full capacities of svn, I think it would not allow us to handle code synchronisation on a locking-base, where possibly not only whole classes are lockable, but also features.
Nevertheless we will make sure that we design our components in a way to guarantee maximal reusability, such that the emu-client could be replaced by a svn-client for example.

Automatic Build Scripts

2006-04-20T22:22:46Z

Barnski: /* 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 that there is additionally the checkout for two delivery paths, which are necessary for building the Delivery after compilation.
Note2: 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.

EMU

2006-04-20T21:51:12Z

Barnski:

[[Category:Projects]]

=Overview=
Eiffel Multi User: The aim of this project is to integrate a repository functionality into EiffelStudio.

=Software Requirements Specification=
==The Parts==
* EMU-Server (stores and manages code-repository)
* EMU-Client (communicates with EMU-Server)
* EMU-IDE integration

==Developer Requirements==
===EMU-Server===
===EMU-Client===
===EMU-IDE integration===
* minimial change to existing ES-classes and features.
* modular integration: activatable and removable / hideable

==User Requirements==
* easy to use
* target is a small project group of up to 20 developers.

=Milestones=

==M1: April 25th==
* set up mailinglist es-emu@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-emu@origo.ethz.ch

* [[User:Barnski| Bernhard Buss]]
* [[User:Kamala| Claudia Kuster]]
* [[User:FoB| Stephan Classen]]

Automatic Build Scripts

2006-04-20T20:55:49Z

Barnski: /* 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 that I left the checkout for two delivery paths, which are necessary for building the Delivery after compilation.

== 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.

User:Barnski

2006-04-19T18:14:33Z

Barnski:

barnski.a.t.student.ethz.ch

(Bernardo Buss)

EMU

2006-04-19T14:51:42Z

Barnski: /* Overview */

[[Category:Projects]]

=Overview=
Eiffel Multi User: The aim of this project is to integrate a repository functionality into EiffelStudio.

=Milestones=

==M1: April 25th==
* set up mailinglist es-emu@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-emu@origo.ethz.ch

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