Bug 531879 - Bug 531877 - Add css to Text content-type
Summary: Bug 531877 - Add css to Text content-type
Status: RESOLVED WONTFIX
Alias: None
Product: Platform
Classification: Eclipse Project
Component: UI (show other bugs)
Version: 3.7.1   Edit
Hardware: All All
: P3 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-UI-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords: usability
Depends on:
Blocks:
 
Reported: 2018-03-01 15:19 EST by Lars Vogel CLA
Modified: 2018-03-01 15:34 EST (History)
2 users (show)

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Lars Vogel CLA 2018-03-01 15:19:11 EST 
Would be nice to be able to smaller css changes directly in Eclipse with the text editor.
Comment 1 Lars Vogel CLA 2018-03-01 15:19:31 EST 
Mickael, what do you think?
Comment 2 Mickael Istria CLA 2018-03-01 15:27:52 EST 
(In reply to Lars Vogel from comment #1)
> Mickael, what do you think?


Note that it's the same question for addition of any file format to associated content-types. It must be decided what behavior we prefer for user on each file type: either we ship a default editor, or we don't associate it and let MPC do a recommendation of a plugin.

If we do that, then it means that Text editor would be associated by default with CSS and users of EPP packages wouldn't get the Marketplace Client proposing more complete solutions such as WTP, BlueSky and others.
So there is a risk here of adding CSS content-type actually resulting in user not recommended to install richer solutions.
Given the criticity of CSS in many apps, the very low value of Eclipse Text Editor for it, and the richness of extensions; I think it's preferable to lead users towards installing an extension when doing CSS that shipping a default support for basic text editor.
Comment 3 Lars Vogel CLA 2018-03-01 15:34:12 EST 
Ok, makes sense, thanks.