RODIN

Dear Ken,
Ken Robinson wrote:
> It would be very useful to be able to add line breaks to comments.
> 
> Is there any way of achieving this?
> 

  You can enter the line breaks in comments through the Edit view of the 
editor. How to display these line is up to the "pretty printers" (e.g. 
HTML or LaTeX". The HTML page already displayed line breaks. I do not 
know about the status of the LaTeX plugin.

> Also, it would also be useful to be able to add comments at any point  
> in a machine or context; not simply to the ends of some components as  
> is now the case.
> 

  This is much more difficult since there is no structure of the file. 
Rather the file is just a collection of modelling elements. What you see 
in the HTML page or the edit page are elements in an order by what we 
defined. So does not make sense to have a comment between two elements. 
However, one can have comments associated with different types of 
elements (e.g. invariants or variables) and that might be some what an 
improvement and answer some of your need.
  Cheers,
Son

Dear Son,

On 25/01/2009, at 16:46 PM, Thai Son Hoang wrote:

> Ken Robinson wrote:
>> It would be very useful to be able to add line breaks to comments.
>>
>> Is there any way of achieving this?
>>
>
>  You can enter the line breaks in comments through the Edit view of  
> the
> editor. How to display these line is up to the "pretty printers" (e.g.
> HTML or LaTeX". The HTML page already displayed line breaks. I do not
> know about the status of the LaTeX plugin.

Yes sorry, I expressed myself badly.

I am concerned with the display of the newlines.

I'm not sure what you mean by the HTML page?  The pretty printing in  
Rodin does display line breaks in the formal part of a construct:  
predicate etc, but does not display line breaks in comments/ 
documentation, and that's where I would like to see them.  Also in the  
LaTeX markup of course.  Documentation is easier to read if it is  
appropriately formatted.

>> Also, it would also be useful to be able to add comments at any point
>> in a machine or context; not simply to the ends of some components as
>> is now the case.
>>
>
>  This is much more difficult since there is no structure of the file.
> Rather the file is just a collection of modelling elements. What you  
> see
> in the HTML page or the edit page are elements in an order by what we
> defined. So does not make sense to have a comment between two  
> elements.
> However, one can have comments associated with different types of
> elements (e.g. invariants or variables) and that might be some what an
> improvement and answer some of your need.

Actually, it gets back to line breaks again.  If the pretty printing  
displayed line breaks then the desire for separate comments would be  
significantly reduced.

BTW: a more general comment.  What you are saying above is "this is  
the way that Rodin is implemented and you can't have ...".

Doesn't this contradict the whole notion of modelling of requirements?

Cheers,

Ken

Dear Ken,
Ken Robinson wrote:
> Dear Son,
>>
>>  You can enter the line breaks in comments through the Edit view of the
>> editor. How to display these line is up to the "pretty printers" (e.g.
>> HTML or LaTeX". The HTML page already displayed line breaks. I do not
>> know about the status of the LaTeX plugin.
> 
> Yes sorry, I expressed myself badly.
> 
> I am concerned with the display of the newlines.
> 
> I'm not sure what you mean by the HTML page?  The pretty printing in 
> Rodin does display line breaks in the formal part of a construct: 
> predicate etc, but does not display line breaks in 
> comments/documentation, and that's where I would like to see them.  Also 
> in the LaTeX markup of course.  Documentation is easier to read if it is 
> appropriately formatted.
> 

  Oops, I meant the Pretty Print page (it is implemented using HTML). I 
attached the screen-shot of the tool which shows the multi-line in both 
the modelling elements and the comments. I do not know about the LaTeX 
markup tool, but I believe this should be formatted accordingly.

>>> Also, it would also be useful to be able to add comments at any point
>>> in a machine or context; not simply to the ends of some components as
>>> is now the case.
>>>
>>
>>  This is much more difficult since there is no structure of the file.
>> Rather the file is just a collection of modelling elements. What you see
>> in the HTML page or the edit page are elements in an order by what we
>> defined. So does not make sense to have a comment between two elements.
>> However, one can have comments associated with different types of
>> elements (e.g. invariants or variables) and that might be some what an
>> improvement and answer some of your need.
> 
> Actually, it gets back to line breaks again.  If the pretty printing 
> displayed line breaks then the desire for separate comments would be 
> significantly reduced.
> 
> BTW: a more general comment.  What you are saying above is "this is the 
> way that Rodin is implemented and you can't have ...".
> 
> Doesn't this contradict the whole notion of modelling of requirements?
> 

  It is not what I meant about the implementation. What I meant is that 
comments should be associated to some modelling elements rather placing 
them freely inside any model. And I think input from users about the 
relationships between comments and modelling elements are really useful.
  Cheers,
Son

Dear Son,

On 26/01/2009, at 10:03 AM, Thai Son Hoang wrote:

> Ken Robinson wrote:

>>> You can enter the line breaks in comments through the Edit view of  
>>> the
>>> editor. How to display these line is up to the "pretty  
>>> printers" (e.g.
>>> HTML or LaTeX". The HTML page already displayed line breaks. I do  
>>> not
>>> know about the status of the LaTeX plugin.
>>>
>> Yes sorry, I expressed myself badly.
>> I am concerned with the display of the newlines.
>> I'm not sure what you mean by the HTML page?  The pretty printing  
>> in Rodin does display line breaks in the formal part of a  
>> construct: predicate etc, but does not display line breaks in  
>> comments/documentation, and that's where I would like to see them.   
>> Also in the LaTeX markup of course.  Documentation is easier to  
>> read if it is appropriately formatted.
>
> Oops, I meant the Pretty Print page (it is implemented using HTML).

Yes, I thought it might be.

> I attached the screen-shot of the tool which shows the multi-line in  
> both the modelling elements and the comments.

Well now I'm more puzzled.

I do not get the behaviour that you show me.

I get:

MACHINE
Testing	   //   line 1 line 2 . xxxx

How can that be?

Is it something to do with the platform?  I'm using Mac OS X.

> I do not know about the LaTeX markup tool, but I believe this should  
> be formatted accordingly.

Yes, the LaTeX is fine, and incidentally the LaTeX for the above is fine

>> BTW: a more general comment.  What you are saying above is "this is  
>> the way that Rodin is implemented and you can't have ...".
>> Doesn't this contradict the whole notion of modelling of  
>> requirements?
>
> It is not what I meant about the implementation. What I meant is  
> that comments should be associated to some modelling elements rather  
> placing them freely inside any model. And I think input from users  
> about the relationships between comments and modelling elements are  
> really useful.

If it worked for me as it does for you, I would be happy! :-)

Cheers,

Ken

Dear Ken,

Le 24 janv. 09 à 01:21, Ken Robinson a écrit :

> At the moment it seems to be difficult to find information on the
> status of some plugins:
>
> animB: this doesn't seem to work with 0.9.1.  What is the position?

Christophe plans to publish a new version of this plug-in on his  
update site this week-end.  The new version will be compatible with  
the coming Rodin 0.9.2 platform.

> requirements plugin: this also doesn't seem to work

We're also working on repairing this plug-in.  A new version should be  
available in the coming week.

Cheers,
Laurent.

Dear Laurent,

Thank you very much.

Cheers,

Ken

On 24/01/2009, at 20:15 PM, Laurent Voisin wrote:

> Dear Ken,
>
> Le 24 janv. 09 à 01:21, Ken Robinson a écrit :
>
>> At the moment it seems to be difficult to find information on the
>> status of some plugins:
>>
>> animB: this doesn't seem to work with 0.9.1.  What is the position?
>
> Christophe plans to publish a new version of this plug-in on his  
> update site this week-end.  The new version will be compatible with  
> the coming Rodin 0.9.2 platform.
>
>> requirements plugin: this also doesn't seem to work
>
> We're also working on repairing this plug-in.  A new version should  
> be available in the coming week.
>
> Cheers,
> Laurent.
>
>