| [ide-dev] IDE working group questions |
| Some of the pain points with Eclipse-based (non-Java) IDEs are: 1. Inability to handle unknown file types. General-purpose editors (e.g. Sublime) will open any file type as text file and provide fairly easy means (e.g. not requiring PDE experience) to setup syntax highlight, brackets matching, etc. Eclipse simply pops open a "system editor" (e.g. Xcode, web browser or Visual Studio) which is incredibly irritating and slow. 2. Inability to work with non-workspace files. The only way in Eclipse is by using that menu item - while other editors can "open" a folder and then provide features like Eclipse "Open Resource…". In Eclipse it is not possible to use Git integration, Open Resource and such. So let's imagine some company is really bothered by such issues and joins this working group (note the hefty price tag of $120k/year). 1. Are there any guarantees somebody would actually implement these enhancements? What may prevent these funds from being spent on EMF enhancements if they get more votes? 2. What would be a timeframe before implementation starts? Would there be a committed delivery schedule? 3. How could such a general-purpose text editor avoid sharing the fate of Bug 155323? Best regards, Eugene
This email message is for the sole use of the intended recipient(s) and may
contain confidential information. Any unauthorized review, use, disclosure
or distribution is prohibited. If you are not the intended recipient,
please contact the sender by reply email and destroy all copies of the original
message.
|