Bug 259431

Summary:	[misc] Allow to embed images
Product:	[Eclipse Project] Platform	Reporter:	Bernd Kolb <b.kolb>
Component:	Text	Assignee:	Platform-Text-Inbox <platform-text-inbox>
Status:	ASSIGNED ---	QA Contact:
Severity:	enhancement
Priority:	P5	CC:	daniel_megert
Version:	3.5	Keywords:	helpwanted
Target Milestone:	---
Hardware:	All
OS:	All
Whiteboard:

Description Bernd Kolb

2008-12-20 02:24:19 EST

When creating textual domain specific languages, I build quite a lot of text based editors with eclipse text apis (using the Eclipse Modeling Project / http://www.eclipse.org/modeling/tmf/ ). However one feature is missing for me in many cases. I often have to mix textual and graphical DSLs. The easiest, and for a user most obvious way to achieve this to embed an image of the graphical content. No floating around the image is needed. The text is just above and below the image. It should be possible to add some (double-click) actions onto the image so e.g. another editor could be opened. 
I guess such a feature could be used by any kind of rich-text editor as well.
It would be very cool if an API for such a feature could be provided. 

Once we have such a feature, we (TMF/Xtext) could provide an integration with the GMF / GEF

Cheers,
Bernd

Comment 1 Bernd Kolb

2008-12-20 04:13:12 EST

Just to clarify: I'd need that API in AbstractTextEditor (or a subclass)

Comment 2 Dani Megert

2008-12-20 04:26:54 EST

The StyledText widget allows to do this. For the text editor we have two major issues to solve:
1) where do we store the data or should we add suppport for an existing rich text format?
2) StyledText wants a character in the widget's document model (StyledTextContent) which brings the text editor model (document) and the text viewer into trouble

Comment 3 Eclipse Webmaster

2019-09-06 16:14:21 EDT

This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.