Feature #1550

RCP: 0.7.7, enhance Java graphical engine SVG export post-editing capabilities

Added by Serge Heiden over 3 years ago. Updated 4 months ago.

Status:New Start date:10/03/2015
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:Charts Spent time: -
Target version:TXM 0.8.1

Description

Currently the SVG export of Java graphical engine outputs text nodes with the following properties (for example in the export of a factorial plane):
  • text labels are output in groups (which doesn't help direct selection with mouse in post-editing, for example in Inkscape)
  • from the point of view of Inkscape:
    • their properies are (for example, for the "mitterand" text label in the first factorial plane of the VOEUX_text_loc partition):
      • id: g451
      • tag: #g451
      • title:
      • description:
    • the 'Edit / Search' tool provides also search fields that could be used to help selection for editing:
      • Text
      • ID
      • Style
      • Attribute

To help post-editing, SVG export could:

Solution A: simplify SVG structure

For example ungroup text objects to help mouse selection (not sure it is a good idea).

Solution B: embed TXM objects types in SVG elements

SVG export could embed TXM objects types to help selection in post-editing.

For example for factorial planes we could have:
  • title label
  • column points labels
  • column points points
  • line points labels
  • line points points
  • X axis label
  • X axis line
  • Y axis label
  • Y axis line
  • X axis coordinate
  • Y axis coordinate
  • plane X line
  • plane Y line
  • etc.

The labels are probably the more subject to post-editing.

We must check how the SVG standard helps to embed such information and how tools like Inkscape can use them.

From the point of view of Inkscape, the label type embeded information could be seen as:
  • id: the type could be encoded in the id like in 'text-451'
  • tag: the type could be encoded in the tag like in '#text-451'
  • title: the type could be encoded in the title like in 'text-451'
  • description: the type could be encoded in the description like in 'text-451'

The information could also be provided such that the Inkscape search tool can search for it in the ID, Style or Attribute fields.

History

#1 Updated by Serge Heiden over 3 years ago

  • Description updated (diff)

#2 Updated by Sebastien Jacquot about 2 years ago

  • Category changed from Export to Charts

#3 Updated by Sebastien Jacquot 10 months ago

  • Target version changed from TXM 0.8.0a (split/restructuration) to TXM 0.8.0

#4 Updated by Sebastien Jacquot 4 months ago

  • Target version changed from TXM 0.8.0 to TXM 0.8.1

Also available in: Atom PDF