Rich text for use case scenario documenting

[sargasso]

Hiccups!

No I had a good long talk to myself about it and all three of us agreed (but one of us refuses to commit himself).




bruce

[«Midnight»]

As a matter of fact, I think that it would be a good eough if we could add sorts of tags to defined the markup to be generated (as in html, latex, or old email systems).
For example:
_underscore_
*bold*
- bulleted list with hyphens
* bulleted list with bullets
TAB for indenting the paragraph
... maybe a few more.

I even think that more than this would be too much. As Geert said, all the text is important and the attention should not be driven away by fancy markups. In addition, the presence of many style buttons would clutter the element window.

Definitively: plain text with markups.

I think there's something to be said for keeping it simple. Perhaps additional tags could be added, with an option to ignore those that are not recognized (as with later RTF versions). We could then tag these fields for use in add-ins etc.

If something really fancy were needed, perhaps we could define these as reference data and transfer them that way. I don't know if the SDK (embedded or otherwise) yet supports custom reference data, but this would be a possible example.

David

[Paolo F Cantoni]

As Geert said, all the text is important and the attention should not be driven away by fancy markups.

Yes, all text is important, but, to paraphrase George Orwell, "some is more important than others".

By this I mean that the ability to apply definitive styles to text, is a way of attaching metadata to the term.  Thus even though the rendering of the text may be identical, the different style imparts information about the nature of the term.

A principal use of this would be to style a term <modelItem/>.  This would allow a dictionary to be composed of all the "items" in the model and automation could be used to cross-check/refactor.

In any event SOMETHING, needs to be done real soon!

Paolo

[jdewitt]

One more vote for adding support for rich text content.

One of EA's biggest strenghts is the ability to publish models in popular presentation formats.

I cannot over-stress the importance of professional looking content. EA has the beef, just needs the sizzle..

[zotric]

I too think it should be kept simple as far as text styles are concerned.  It only needs bold text linked into the glossary.  More than that would be too much in my view.
The idea of visible tags has pros and cons but I think on the whole, for readability, I would like it bold and for the actual tag to be invisible.  I still think an interactive link with the glossary (by double clicking) is necessary as per my previous comment.