Bug 98230 - [EditorMgmt] No obvious way to add a new content type
Summary: [EditorMgmt] No obvious way to add a new content type
Status: RESOLVED FIXED
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.1   Edit
Hardware: All All
: P3 normal (vote)
Target Milestone: 4.7 M4   Edit
Assignee: Mickael Istria CLA
QA Contact:
URL:
Whiteboard:
Keywords: noteworthy
: 500892 (view as bug list)
Depends on: 57908
Blocks: 508930 534338
  Show dependency tree
 
Reported: 2005-06-03 00:38 EDT by Stefan Xenos CLA
Modified: 2018-05-06 03:12 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stefan Xenos CLA 2005-06-03 00:38:19 EDT
The content types preference page shows a tree of file formats.

My first thought was "Cool. Let's try to create a 'C++' content type.", so I
selected "Text", clicked "Add...", and was only able to add a file extension.

It should be possible to create new content types and rearrange the default ones
(for example, I may want to create a global or 'binary' content type, make
'text' and 'Java Class File' both children of it, and register a hex editor on
the 'binary' content type).
Comment 1 Kim Horne CLA 2005-06-03 08:46:09 EDT

*** This bug has been marked as a duplicate of 57908 ***
Comment 2 Stefan Xenos CLA 2007-01-12 18:06:30 EST
Reopening. bug 57908 requests programmatic control, this bug requests end-user control.
Comment 3 Boris Bokowski CLA 2009-11-17 13:04:31 EST
Remy is now responsible for watching the [EditorMgmt] component area.
Comment 4 Stefan Xenos CLA 2016-10-27 21:18:52 EDT
Here's another content types bug that may be relevant for the generic text editor.
Comment 5 Mickael Istria CLA 2016-10-28 01:20:44 EDT
*** Bug 500892 has been marked as a duplicate of this bug. ***
Comment 7 Mickael Istria CLA 2016-11-29 07:36:40 EST
As the Resources part was merged, I did merge the foolowing UI part which introduce no risk of regression at all. There is most likely still room for improvements (better labels or things like that), but it will probably be easier to get feedback if this is part of next milestone.
Comment 8 Mickael Istria CLA 2016-11-29 07:57:48 EST
Added to N&N: https://www.eclipse.org/eclipse/news/4.7/M4/#manually-create-content-types
Comment 9 Markus Keller CLA 2016-12-08 11:01:57 EST
(In reply to Mickael Istria from comment #8)
> Added to N&N:

Please avoid using <em> in the descriptions, see the instructions.
Comment 10 Lars Vogel CLA 2016-12-08 11:18:27 EST
(In reply to Markus Keller from comment #9)
> Please avoid using <em> in the descriptions, see the instructions.

Created Bug 508931 to avoid this more or less automatically.
Comment 11 Mickael Istria CLA 2017-08-07 10:10:04 EDT
(In reply to Markus Keller from comment #9)
> (In reply to Mickael Istria from comment #8)
> > Added to N&N:
> 
> Please avoid using <em> in the descriptions, see the instructions.

With http://git.eclipse.org/c/gerrit/www.eclipse.org/eclipse/news.git/commit/?id=37c81657e33e246615072474bc2d0d26e24c59be , the entry in N&N was removed. It's really a pity because some downstream projects such as TM4E have been waiting for this to be announced before making such change. As a result, those projects have delayed some interesting and valuable development.
Gerrit is also available for N&N. Using it reduces the risk of removing very valuable content and to slow down our community, please use it.
Comment 12 Lars Vogel CLA 2018-05-06 03:12:47 EDT
(In reply to Mickael Istria from comment #11)
> (In reply to Markus Keller from comment #9)
> > (In reply to Mickael Istria from comment #8)
> > > Added to N&N:
> > 
> > Please avoid using <em> in the descriptions, see the instructions.
> 
> With
> http://git.eclipse.org/c/gerrit/www.eclipse.org/eclipse/news.git/commit/
> ?id=37c81657e33e246615072474bc2d0d26e24c59be , the entry in N&N was removed.

Deleting N&N because of small formatting errors without notifying the author is very bad style and should be avoided. Markus already left the project and I have not seen such behaviour since then.