Christoph Läubrich

> for one would expect that if Eclipse would support .editorconfig, it would also mean that all the settings one can set via .editorconfig would also be supported in all...

Just assume I have an editor that supports Grahical editing of a binary file format, has "trim_trailing_whitespace" any meaning?

By the way, as far as I know no one prevents others to also looking at the generic editor extension point later on...

> whatever takes precedence should be shown in the properties file of any resource: I don't think that this is mandatory, any editor can ignore these defaults these are just...

> I don't see why "width" and "height" need to be separate types and not roles of the same type). When designing new APIs/frameworks, that should be the way to...

> That looks way too verbose. I can also already see the boilerplate code of when you e.g want to transpose the object and therefore need to convert the width...

> For Javas Temporal API, you have the java.time.temporal.ChronoUnit enum to define the unit of time. And I think something similar would find more acceptance from users. e.g. setSize(50, 25,...

> Not necessarily a widget, but what about an image? The API should at the very least be consistent across the board. Okay lets for now ignore that images are...

> My conclusion on this is as follows: you are welcome to propose a holistic, completely modernized, future-proof solution, but I really hope that until you come up with it...

Thanks for clarification. > The proposal would add these well fields to the message protocol when available. Correctly, that would be good, to the tools consuming the messages don't need...