RODIN

Hello Michael,

it seems to be a problem at the feedback page (I'm trying this one, I mean, it's this one that is called after I click the feedback buttom: https://spreadsheets.google.com/spreadsheet/viewform?formkey=dEJmXzUydnRzZGdDVE16WFZmZmd1alE6MQ&entry_0=The%20First%20Machine%3A%20A%20Traffic%20Light%20Controller )

when I try to change the feedback type, the page reloads automatically!!! 

cheers

Dinho


Aryldo G Russo Jr
Diretor de Pesquisa, Desenvolvimento e Inovação
Grupo AeS
ASQ/CRE - ASQ/CSSBB





On 03/08/2011, at 06:52, Michael Jastram wrote:

> Dear all,
> 
> we are happy to announce the completion of the first iteration (out of four) on the Rodin Handbook.  We invite you to participate in the iteration review.  The review phase starts today and will end on August 13th.  Of course, you can still provide feedback after this date, it merely marks the end of the first and the beginning of the second iteration.
> 
> You can access our work so far at handbook.event-b.org.  Note that we will continue to work on the handbook during the review phase.  Therefore, you will find two versions on that page: A "frozen" version for the review, and the latest build.  For the review, please make sure that you access the frozen build.
> 
> The first iteration consists of six work packages, which are documented on the Rodin Wiki.  Links to all deliverables can be found on that page.  Please note that we made some changes to the next three iterations, mainly to accommodate the schedule for user testing.
> 
> The most important deliverable of this iteration is the Tutorial.  Please note that our focus so far has been on structure and content.  We will continue to work on the Tutorial in later iterations by having a copy editor improve the language and by performing user tests to identify weaknesses, omissions, etc.
> 
> Please note that all versions of the handbook contain large sections of incomplete and unstructured content (FAQ, References, etc.).  Just ignore these elements, or simply understand them as a pointer on where our work is going.
> 
> We generate three versions of the documentation from the same sources: HTML, PDF and Eclipse Help.  We encourage you to check out all three versions.  To evaluate the Eclipse Help version, you have to install the handbook plugin into any Eclipse installation.
> 
> On the HTML and Eclipse Help versions, we offer a feedback button <bubble_48.png> that conveniently allows you to provide immediate feedback.  If your organizations blocks the button, or if you are off-line, you can also provide feedback by email (there is also a link for this purpose). The feedback button is useful for error reporting, etc.  For discussions, please consider using the handbook mailing list.
> 
> What you see here is the work of Lukas Ladenberger, Daniel Plagge, Ivan Merlin and Joy Clark, who all did a terrific job, and myself.  We hope you are happy with the developments so far.
> 
> Best regards,
> 
> - Michael
> 
> 
> 
> ------------------------------------------------------------------------------
> BlackBerry&reg; DevCon Americas, Oct. 18-20, San Francisco, CA
> The must-attend event for mobile developers. Connect with experts. 
> Get tools for creating Super Apps. See the latest technologies.
> Sessions, hands-on labs, demos & much more. Register early & save!
> http://p.sf.net/sfu/rim-blackberry-1_______________________________________________
> Rodin-b-sharp-handbook mailing list
> Rodin-b-sharp-handbook@...
> https://lists.sourceforge.net/lists/listinfo/rodin-b-sharp-handbook

Hi Dinho,

Strange.  I tried to reproduce it, both with Firefox and Safari, but it
worked fine with me.  Could you please try it with a different browser? 
And what browser were you using?

Regarding the feedback, just submit it with the "wrong" type, for now.

Thanks,

- Michael

On 08/03/2011 10:07 PM, Aryldo G Russo Jr wrote:
> Hello Michael,
>
> it seems to be a problem at the feedback page (I'm trying this one, I
> mean, it's this one that is called after I click the feedback
> buttom: https://spreadsheets.google.com/spreadsheet/viewform?formkey=dEJmXzUydnRzZGdDVE16WFZmZmd1alE6MQ&entry_0=The%20First%20Machine%3A%20A%20Traffic%20Light%20Controller
> <https://spreadsheets.google.com/spreadsheet/viewform?formkey=dEJmXzUydnRzZGdDVE16WFZmZmd1alE6MQ&entry_0=The%20First%20Machine%3A%20A%20Traffic%20Light%20Controller>
> )
>
> when I try to change the feedback type, the page reloads automatically!!! 
>
> cheers
>
> Dinho
>
>
> Aryldo G Russo Jr
> Diretor de Pesquisa, Desenvolvimento e Inovação
> Grupo AeS
> ASQ/CRE - ASQ/CSSBB
>
>
>
>
>
> On 03/08/2011, at 06:52, Michael Jastram wrote:
>
>> Dear all,
>>
>> we are happy to announce the completion of the first iteration (out
>> of four) on the Rodin Handbook.  We invite you to participate in the
>> iteration review.  The review phase starts today and will end on
>> August 13th.  Of course, you can still provide feedback after this
>> date, it merely marks the end of the first and the beginning of the
>> second iteration.
>>
>> You can access our work so far at handbook.event-b.org
>> <http://handbook.event-b.org>.  Note that we will continue to work on
>> the handbook during the review phase.  Therefore, you will find two
>> versions on that page: A "frozen" version for the review, and the
>> latest build.  For the review, please make sure that you access the
>> frozen build.
>>
>> The first iteration consists of six work packages
>> <http://wiki.event-b.org/index.php/Documentation_Overhaul_DoW#First_Iteration>,
>> which are documented on the Rodin Wiki.  Links to all deliverables
>> can be found on that page.  Please note that we made some changes to
>> the next three iterations, mainly to accommodate the schedule for
>> user testing.
>>
>> The most important deliverable of this iteration is the Tutorial
>> <http://handbook.event-b.org/review-1/html/tutorial.html>.  Please
>> note that our focus so far has been on structure and content.  We
>> will continue to work on the Tutorial in later iterations by having a
>> copy editor improve the language and by performing user tests to
>> identify weaknesses, omissions, etc.
>>
>> Please note that all versions of the handbook contain large sections
>> of incomplete and unstructured content (FAQ, References, etc.).  Just
>> ignore these elements, or simply understand them as a pointer on
>> where our work is going.
>>
>> We generate three versions of the documentation from the same
>> sources: HTML <http://handbook.event-b.org/review-1/html/>, PDF
>> <http://handbook.event-b.org/review-1/pdf/rodin-doc.pdf> and Eclipse
>> Help.  We encourage you to check out all three versions.  To evaluate
>> the Eclipse Help version, you have to install the handbook plugin
>> <http://handbook.event-b.org/review-1/plugin/org.rodinp.handbook.zip> into
>> any Eclipse installation.
>>
>> On the HTML and Eclipse Help versions, we offer a feedback
>> button <bubble_48.png>
>> <https://spreadsheets.google.com/spreadsheet/viewform?formkey=dEJmXzUydnRzZGdDVE16WFZmZmd1alE6MQ&entry_0=User%20Manual%20for%20Rodin%20v.2.2> that
>> conveniently allows you to provide immediate feedback.  If your
>> organizations blocks the button, or if you are off-line, you can also
>> provide feedback by email (there is also a link for this purpose).
>> The feedback button is useful for error reporting, etc.  For
>> discussions, please consider using the handbook mailing list
>> <http://lists.sourceforge.net/mailman/listinfo/rodin-b-sharp-handbook>.
>>
>> What you see here is the work of Lukas Ladenberger, Daniel Plagge,
>> Ivan Merlin and Joy Clark, who all did a terrific job, and myself. 
>> We hope you are happy with the developments so far.
>>
>> Best regards,
>>
>> - Michael
>>
>>
>>
>> ------------------------------------------------------------------------------
>> BlackBerry&reg; DevCon Americas, Oct. 18-20, San Francisco, CA
>> The must-attend event for mobile developers. Connect with experts. 
>> Get tools for creating Super Apps. See the latest technologies.
>> Sessions, hands-on labs, demos & much more. Register early & save!
>> http://p.sf.net/sfu/rim-blackberry-1_______________________________________________
>> Rodin-b-sharp-handbook mailing list
>> Rodin-b-sharp-handbook@...
>> <mailto:Rodin-b-sharp-handbook@...>
>> https://lists.sourceforge.net/lists/listinfo/rodin-b-sharp-handbook
>

Hello Michael

I sent the feedback yesterday, did you get it?

Regarding the browser, I'm running Safari under mac os lion

Sent from my iPhone

On 04/08/2011, at 03:56, Michael Jastram <michael@...> wrote:

> Hi Dinho,
> 
> Strange.  I tried to reproduce it, both with Firefox and Safari, but it worked fine with me.  Could you please try it with a different browser?  And what browser were you using?
> 
> Regarding the feedback, just submit it with the "wrong" type, for now.
> 
> Thanks,
> 
> - Michael
> 
> On 08/03/2011 10:07 PM, Aryldo G Russo Jr wrote:
>> 
>> Hello Michael,
>> 
>> it seems to be a problem at the feedback page (I'm trying this one, I mean, it's this one that is called after I click the feedback buttom: https://spreadsheets.google.com/spreadsheet/viewform?formkey=dEJmXzUydnRzZGdDVE16WFZmZmd1alE6MQ&entry_0=The%20First%20Machine%3A%20A%20Traffic%20Light%20Controller )
>> 
>> when I try to change the feedback type, the page reloads automatically!!! 
>> 
>> cheers
>> 
>> Dinho
>> 
>> 
>> Aryldo G Russo Jr
>> Diretor de Pesquisa, Desenvolvimento e Inovação
>> Grupo AeS
>> ASQ/CRE - ASQ/CSSBB
>> 
>> 
>> 
>> 
>> 
>> On 03/08/2011, at 06:52, Michael Jastram wrote:
>> 
>>> Dear all,
>>> 
>>> we are happy to announce the completion of the first iteration (out of four) on the Rodin Handbook.  We invite you to participate in the iteration review.  The review phase starts today and will end on August 13th.  Of course, you can still provide feedback after this date, it merely marks the end of the first and the beginning of the second iteration.
>>> 
>>> You can access our work so far at handbook.event-b.org.  Note that we will continue to work on the handbook during the review phase.  Therefore, you will find two versions on that page: A "frozen" version for the review, and the latest build.  For the review, please make sure that you access the frozen build.
>>> 
>>> The first iteration consists of six work packages, which are documented on the Rodin Wiki.  Links to all deliverables can be found on that page.  Please note that we made some changes to the next three iterations, mainly to accommodate the schedule for user testing.
>>> 
>>> The most important deliverable of this iteration is the Tutorial.  Please note that our focus so far has been on structure and content.  We will continue to work on the Tutorial in later iterations by having a copy editor improve the language and by performing user tests to identify weaknesses, omissions, etc.
>>> 
>>> Please note that all versions of the handbook contain large sections of incomplete and unstructured content (FAQ, References, etc.).  Just ignore these elements, or simply understand them as a pointer on where our work is going.
>>> 
>>> We generate three versions of the documentation from the same sources: HTML, PDF and Eclipse Help.  We encourage you to check out all three versions.  To evaluate the Eclipse Help version, you have to install the handbook plugin into any Eclipse installation.
>>> 
>>> On the HTML and Eclipse Help versions, we offer a feedback button <bubble_48.png> that                 conveniently allows you to provide immediate feedback.  If your organizations blocks the button, or if you are off-line, you can also provide feedback by email (there is also a link for this purpose). The feedback button is useful for error reporting, etc.  For discussions, please consider using the handbook mailing list.
>>> 
>>> What you see here is the work of Lukas Ladenberger, Daniel Plagge, Ivan Merlin and Joy Clark, who all did a terrific job, and myself.  We hope you are happy with the developments so far.
>>> 
>>> Best regards,
>>> 
>>> - Michael
>>> 
>>> 
>>> 
>>> ------------------------------------------------------------------------------
>>> BlackBerry&reg; DevCon Americas, Oct. 18-20, San Francisco, CA
>>> The must-attend event for mobile developers. Connect with experts. 
>>> Get tools for creating Super Apps. See the latest technologies.
>>> Sessions, hands-on labs, demos & much more. Register early & save!
>>> http://p.sf.net/sfu/rim-blackberry-1_______________________________________________
>>> Rodin-b-sharp-handbook mailing list
>>> Rodin-b-sharp-handbook@...
>>> https://lists.sourceforge.net/lists/listinfo/rodin-b-sharp-handbook
>> 
>

Hi Thomas,

> We saw that a part of the handbook (namely 3.46 Structural Editor)
> will be dedicated to the old editor.
> Could you please use the existing contents and do not spend much time
> on it, as the plan is actually
> to replace the Structural Editor with the Rodin Editor in the future.

Thank you for the pointers!  You raise a good point, especially as
multiple editors are available.  We'll take your advice and will not put
too much effort into this part of the documentation.  Do you already
know when the new editor will replace the current one?

I'll cc the handbook list, as the following may be useful for others as
well.  In a number of places, we thought that references to other
plugins would be useful.  At the same time, we don't have the resources
to create and maintain documentation for other plugins.  We will address
this in the second iteration withWP2-3
<http://wiki.event-b.org/index.php/Documentation_Overhaul_DoW#Second_Iteration>:


          WP2-3: Guideline for Plugin Developers (20mh)

    Even though Plugins are officially not covered by the handbook,
    there are many places where covering some aspects would be extremely
    useful. We will produce a guideline for Plugin developers for
    including references to their work in the handbook.

Once the guideline is complete, you can contribute sections to the
Handbook that describe the new editor plugin (or any other plugin you
fancy).  This may be a good way to raise awareness.

Best,

- Michael


On 08/04/2011 02:44 PM, Thomas Muller wrote:
> Hi Michael!
>
> Congratulations for the end of the first iteration on the Rodin
> Handbook! It looks promising !
>
> We saw that a part of the handbook (namely 3.46 Structural Editor)
> will be dedicated to the old editor.
> Could you please use the existing contents and do not spend much time
> on it, as the plan is actually
> to replace the Structural Editor with the Rodin Editor in the future.
>
> Now the Rodin Editor is still appart from the core platform, as there
> is still major development to do on it and
> basically, we wanted an more flexible way to update it than with
> platform upgrades.
>
> The documentation of the Rodin Editor started here :
> http://wiki.event-b.org/index.php/Rodin_Editor and
> http://wiki.event-b.org/index.php/Rodin_Editor_User_Guide
>
> Best regards,
>
>     Thomas.
>
>
> Le 03/08/2011 11:52, Michael Jastram a écrit :
>> Dear all,
>>
>> we are happy to announce the completion of the first iteration (out
>> of four) on the Rodin Handbook.  We invite you to participate in the
>> iteration review.  The review phase starts today and will end on
>> August 13th.  Of course, you can still provide feedback after this
>> date, it merely marks the end of the first and the beginning of the
>> second iteration.
>>
>> You can access our work so far at handbook.event-b.org
>> <http://handbook.event-b.org>.  Note that we will continue to work on
>> the handbook during the review phase.  Therefore, you will find two
>> versions on that page: A "frozen" version for the review, and the
>> latest build.  For the review, please make sure that you access the
>> frozen build.
>>
>> The first iteration consists of six work packages
>> <http://wiki.event-b.org/index.php/Documentation_Overhaul_DoW#First_Iteration>,
>> which are documented on the Rodin Wiki.  Links to all deliverables
>> can be found on that page.  Please note that we made some changes to
>> the next three iterations, mainly to accommodate the schedule for
>> user testing.
>>
>> The most important deliverable of this iteration is the Tutorial
>> <http://handbook.event-b.org/review-1/html/tutorial.html>.  Please
>> note that our focus so far has been on structure and content.  We
>> will continue to work on the Tutorial in later iterations by having a
>> copy editor improve the language and by performing user tests to
>> identify weaknesses, omissions, etc.
>>
>> Please note that all versions of the handbook contain large sections
>> of incomplete and unstructured content (FAQ, References, etc.).  Just
>> ignore these elements, or simply understand them as a pointer on
>> where our work is going.
>>
>> We generate three versions of the documentation from the same
>> sources: HTML <http://handbook.event-b.org/review-1/html/>, PDF
>> <http://handbook.event-b.org/review-1/pdf/rodin-doc.pdf> and Eclipse
>> Help.  We encourage you to check out all three versions.  To evaluate
>> the Eclipse Help version, you have to install the handbook plugin
>> <http://handbook.event-b.org/review-1/plugin/org.rodinp.handbook.zip>
>> into any Eclipse installation.
>>
>> On the HTML and Eclipse Help versions, we offer a feedback button
>> <https://spreadsheets.google.com/spreadsheet/viewform?formkey=dEJmXzUydnRzZGdDVE16WFZmZmd1alE6MQ&entry_0=User%20Manual%20for%20Rodin%20v.2.2>
>> that conveniently allows you to provide immediate feedback.  If your
>> organizations blocks the button, or if you are off-line, you can also
>> provide feedback by email (there is also a link for this purpose).
>> The feedback button is useful for error reporting, etc.  For
>> discussions, please consider using the handbook mailing list
>> <http://lists.sourceforge.net/mailman/listinfo/rodin-b-sharp-handbook>.
>>
>> What you see here is the work of Lukas Ladenberger, Daniel Plagge,
>> Ivan Merlin and Joy Clark, who all did a terrific job, and myself. 
>> We hope you are happy with the developments so far.
>>
>> Best regards,
>>
>> - Michael
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> BlackBerry&reg; DevCon Americas, Oct. 18-20, San Francisco, CA
>> The must-attend event for mobile developers. Connect with experts. 
>> Get tools for creating Super Apps. See the latest technologies.
>> Sessions, hands-on labs, demos & much more. Register early & save!
>> http://p.sf.net/sfu/rim-blackberry-1
>>
>>
>> _______________________________________________
>> Rodin-b-sharp-handbook mailing list
>> Rodin-b-sharp-handbook@...
>> https://lists.sourceforge.net/lists/listinfo/rodin-b-sharp-handbook
>
>
> -- 
> ------------------------------------------------------------------------
> Thomas MULLER                             Tél. : (+33)(0)4 42 90 65 66
> Engineer in Formal Methods
>
> SYSTEREL
> ------------------------------------------------------------------------
> Standard / Fax : (+33)(0)4 42 90 41 20 / 29     site : http://www.systerel.fr
> ------------------------------------------------------------------------
>

Hello Dinho,

> I sent the feedback yesterday, did you get it?

I did, thanks a lot!

> Regarding the browser, I'm running Safari under mac os lion

Do you have the problem with other browsers, too?

Cheers,

- Michael

>
> Sent from my iPhone
>
> On 04/08/2011, at 03:56, Michael Jastram <michael@...
> <mailto:michael@...>> wrote:
>
>> Hi Dinho,
>>
>> Strange.  I tried to reproduce it, both with Firefox and Safari, but
>> it worked fine with me.  Could you please try it with a different
>> browser?  And what browser were you using?
>>
>> Regarding the feedback, just submit it with the "wrong" type, for now.
>>
>> Thanks,
>>
>> - Michael
>>
>> On 08/03/2011 10:07 PM, Aryldo G Russo Jr wrote:
>>> Hello Michael,
>>>
>>> it seems to be a problem at the feedback page (I'm trying this one,
>>> I mean, it's this one that is called after I click the feedback
>>> buttom: https://spreadsheets.google.com/spreadsheet/viewform?formkey=dEJmXzUydnRzZGdDVE16WFZmZmd1alE6MQ&entry_0=The%20First%20Machine%3A%20A%20Traffic%20Light%20Controller
>>> <https://spreadsheets.google.com/spreadsheet/viewform?formkey=dEJmXzUydnRzZGdDVE16WFZmZmd1alE6MQ&entry_0=The%20First%20Machine%3A%20A%20Traffic%20Light%20Controller>
>>> )
>>>
>>> when I try to change the feedback type, the page reloads
>>> automatically!!! 
>>>
>>> cheers
>>>
>>> Dinho
>>>
>>>
>>> Aryldo G Russo Jr
>>> Diretor de Pesquisa, Desenvolvimento e Inovação
>>> Grupo AeS
>>> ASQ/CRE - ASQ/CSSBB
>>>
>>>
>>>

Michael,
>> We saw that a part of the handbook (namely 3.46 Structural Editor) 
>> will be dedicated to the old editor.
>> Could you please use the existing contents and do not spend much time 
>> on it, as the plan is actually
>> to replace the Structural Editor with the Rodin Editor in the future.
>
> Thank you for the pointers!  You raise a good point, especially as 
> multiple editors are available.  We'll take your advice and will not 
> put too much effort into this part of the documentation.  Do you 
> already know when the new editor will replace the current one?
You're welcome. We don't have yet a date on which this will happen. 
However, we expect it to happen before the end of DEPLOY.
> I'll cc the handbook list, as the following may be useful for others 
> as well.  In a number of places, we thought that references to other 
> plugins would be useful.  At the same time, we don't have the 
> resources to create and maintain documentation for other plugins.  We 
> will address this in the second iteration withWP2-3 
> <http://wiki.event-b.org/index.php/Documentation_Overhaul_DoW#Second_Iteration>:
>
>
>           WP2-3: Guideline for Plugin Developers (20mh)
>
>     Even though Plugins are officially not covered by the handbook,
>     there are many places where covering some aspects would be
>     extremely useful. We will produce a guideline for Plugin
>     developers for including references to their work in the handbook.
>
> Once the guideline is complete, you can contribute sections to the 
> Handbook that describe the new editor plugin (or any other plugin you 
> fancy).  This may be a good way to raise awareness.
With my previous mail I wanted to point you out a situation which is to 
me a bit more complex: "what is currently (and temporarily) only a 
plug-in (the Rodin Editor) will go in the "core platform"." Therefore 
should be documented as is...
I would expect my "plug-in related" contribution to be fitted out in the 
part 3.46 when the replacement will occur...

Best regards, and good luck for the rest of the writing!

     Thomas.

-- 
------------------------------------------------------------------------
Thomas MULLER                             Tél. : (+33)(0)4 42 90 65 66
Engineer in Formal Methods

SYSTEREL
------------------------------------------------------------------------
Standard / Fax : (+33)(0)4 42 90 41 20 / 29     site : http://www.systerel.fr
------------------------------------------------------------------------

Hi Thomas,

>> Thank you for the pointers!  You raise a good point, especially as
>> multiple editors are available.  We'll take your advice and will not
>> put too much effort into this part of the documentation.  Do you
>> already know when the new editor will replace the current one?
> You're welcome. We don't have yet a date on which this will happen.
> However, we expect it to happen before the end of DEPLOY.

That's good to know.  What will happen to the current editor?  Will it
be removed from the core?

> With my previous mail I wanted to point you out a situation which is
> to me a bit more complex: "what is currently (and temporarily) only a
> plug-in (the Rodin Editor) will go in the "core platform"." Therefore
> should be documented as is...
> I would expect my "plug-in related" contribution to be fitted out in
> the part 3.46 when the replacement will occur...

Actually, the situation is a little more complicated than that.  There
are quite a few screenshots in the documentation.  We want to make sure
that these reflect the correct appearance of the UI.  If the new editor
becomes the default, then we'll have to redo all the screenshots.  So
the sooner we know the exact plan, the better.  Of course, if the
structural editor stays part of the core, we can leave things as they
are, and simply extend the documentation with the new editor stuff.  In
that case, I expect to have a section 3.46a and 3.46b (or whatever
numbers they may be), one for each editor.

Best,

- Michael

Dear all,

This is a friendly reminder that we will end the first iteration of the
Handbook Project by the end of this week.  Specifically, please make
sure that

  * You are satisfied that the work done so far reflects the
    deliverables from the workpackages from the DoW
  * You feel that the work goes in the right direction
  * You feel that the upcoming iterations have the right priorities

We already received some positive and constructive feedback - thank you
very much.

Best,

- Michael


On 08/03/2011 11:52 AM, Michael Jastram wrote:
> Dear all,
>
> we are happy to announce the completion of the first iteration (out of
> four) on the Rodin Handbook.  We invite you to participate in the
> iteration review.  The review phase starts today and will end on
> August 13th.  Of course, you can still provide feedback after this
> date, it merely marks the end of the first and the beginning of the
> second iteration.
>
> You can access our work so far at handbook.event-b.org
> <http://handbook.event-b.org>.  Note that we will continue to work on
> the handbook during the review phase.  Therefore, you will find two
> versions on that page: A "frozen" version for the review, and the
> latest build.  For the review, please make sure that you access the
> frozen build.
>
> The first iteration consists of six work packages
> <http://wiki.event-b.org/index.php/Documentation_Overhaul_DoW#First_Iteration>,
> which are documented on the Rodin Wiki.  Links to all deliverables can
> be found on that page.  Please note that we made some changes to the
> next three iterations, mainly to accommodate the schedule for user
> testing.
>
> The most important deliverable of this iteration is the Tutorial
> <http://handbook.event-b.org/review-1/html/tutorial.html>.  Please
> note that our focus so far has been on structure and content.  We will
> continue to work on the Tutorial in later iterations by having a copy
> editor improve the language and by performing user tests to identify
> weaknesses, omissions, etc.
>
> Please note that all versions of the handbook contain large sections
> of incomplete and unstructured content (FAQ, References, etc.).  Just
> ignore these elements, or simply understand them as a pointer on where
> our work is going.
>
> We generate three versions of the documentation from the same sources:
> HTML <http://handbook.event-b.org/review-1/html/>, PDF
> <http://handbook.event-b.org/review-1/pdf/rodin-doc.pdf> and Eclipse
> Help.  We encourage you to check out all three versions.  To evaluate
> the Eclipse Help version, you have to install the handbook plugin
> <http://handbook.event-b.org/review-1/plugin/org.rodinp.handbook.zip>
> into any Eclipse installation.
>
> On the HTML and Eclipse Help versions, we offer a feedback button
> <https://spreadsheets.google.com/spreadsheet/viewform?formkey=dEJmXzUydnRzZGdDVE16WFZmZmd1alE6MQ&entry_0=User%20Manual%20for%20Rodin%20v.2.2>
> that conveniently allows you to provide immediate feedback.  If your
> organizations blocks the button, or if you are off-line, you can also
> provide feedback by email (there is also a link for this purpose). The
> feedback button is useful for error reporting, etc.  For discussions,
> please consider using the handbook mailing list
> <http://lists.sourceforge.net/mailman/listinfo/rodin-b-sharp-handbook>.
>
> What you see here is the work of Lukas Ladenberger, Daniel Plagge,
> Ivan Merlin and Joy Clark, who all did a terrific job, and myself.  We
> hope you are happy with the developments so far.
>
> Best regards,
>
> - Michael
>
>
>