Book a Demo

Author Topic: Rich Text Tagged Values  (Read 3645 times)

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Rich Text Tagged Values
« on: April 10, 2010, 10:11:22 am »
Could tagged values of type memo be upgraded to handle Rich Text?

If necessary, a new type of tagged value: RTMemo could be created to specifically hold rich text, while the existing memo could behave as is.

Thoughts?
Paolo
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

beginner

  • Guest
Re: Rich Text Tagged Values
« Reply #1 on: April 12, 2010, 06:41:26 pm »
Before having this I would vote for a more clear "rich text" handling. Why not have HTML instead of this RTF scrap? Of course this would reduce the typesetting abilities but EA is not QuarkXPress. Everyone forced to handle RTF (natively!) knows what I'm talking about. I also know that HTML is not HTML (depends on the browser flavor). But there is a kind of standard behind it. And I would love to see the same HTML capabilities for all "memo"-kind fields in EA.

b.

Geert Bellekens

  • EA Guru
  • *****
  • Posts: 13523
  • Karma: +574/-33
  • Make EA work for YOU!
    • View Profile
    • Enterprise Architect Consultant and Value Added Reseller
Re: Rich Text Tagged Values
« Reply #2 on: April 12, 2010, 07:32:57 pm »
Just to be clear, EA doesn't use RTF for its "rich formatting notes".
Internally they use some kind of markup similar to html. (that is probably also the reason why they have chosen not to enable tables)

Geert

Paolo F Cantoni

  • EA Guru
  • *****
  • Posts: 8626
  • Karma: +259/-129
  • Inconsistently correct systems DON'T EXIST!
    • View Profile
Re: Rich Text Tagged Values
« Reply #3 on: April 12, 2010, 07:53:06 pm »
I'm using "Rich Text" consistently with Sparx's incorrect use of the term with respect to "Rich Text Notes" (see Help) - since it's better to be consistently wrong than inconsistently wrong.

I've heard back from Sparx, it's been added as a formal feature request internally.

Paolo
« Last Edit: April 12, 2010, 07:54:21 pm by PaoloFCantoni »
Inconsistently correct systems DON'T EXIST!
... Therefore, aim for consistency; in the expectation of achieving correctness....
-Semantica-
Helsinki Principle Rules!

beginner

  • Guest
Re: Rich Text Tagged Values
« Reply #4 on: April 12, 2010, 08:57:18 pm »
Quote
Just to be clear, EA doesn't use RTF for its "rich formatting notes".
Internally they use some kind of markup similar to html. (that is probably also the reason why they have chosen not to enable tables)

Geert
I know and actually I don't care about the internal representation. The interface however offers three different flavors to access "rich text": the "internal", HTML and RTF. The problem here (like in many other programs) is that the interface has been "enhanced" during the lifetime of the product. First there was just plain text (with the exception of linefeeds in selected rich text fields). Then more and more rich text features have been added. Dealing with these flavors is extremely touchy. You never know what it will look like. Rendering in diagrams is different to that in note windows and tagged values do not accept any "rich text" except for the above mentioned old fashioned linebreak data for the memo field (which is a bastard by itself as it is used as description of the tag as well as its contents where the user decides so).

It's so easy to see
where you go without CCC.

b.