[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [handly-dev] Handly 0.4 : Focus on API quality
- From: Vladimir Piskarev <pisv@xxxxx>
- Date: Fri, 30 Oct 2015 12:21:47 +0300
- Delivered-to: email@example.com
I'm pleased to announce the availability of the 0.4 M4 milestone build, an attempt at API freeze towards the 0.4 release on Dec 11 2015.
The 0.4 version, with its main goal of improving core Handly APIs, will necessarily be much more disruptive than previous releases. With this milestone build, we are seeking to provide current adopters with an opportunity to give it a try and leave feedback/raise concerns before it would be too late.
Here's a N&N list.
Several API methods take IProgressMonitor now
IHandleDelta#getFlags() : int -> long
HandleDelta - multiple breaking changes
* public API remained largely the same
* protected API surface area was significantly reduced
(i.e. many previously protected members are now private)
see bug 480945 for details: https://bugs.eclipse.org/bugs/show_bug.cgi?id=480945
ISourceElement#getElementAt may throw CoreException now
-> use SourceElements#getElementAt if you need original semantics
IElementForEditorInputFactory -> IInputElementProvider
superseded by IInputElementProvider for all intents and purposes
please bind IInputElementProvider instead of IEFEIF in your Xtext modules
ISourceFile#openBuffer -> getBuffer
IDocumentBuffer -> IBuffer#getDocument()
IBuffer#dispose() -> release()
StructureHelper can now be used as it stands, i.e. without subclassing
Xtext 2.9 is supported now (along with 2.8)
FULL LIST OF API RELATED ISSUES
FULL LIST OF ISSUES WITH BREAKING CHANGES
API quality is going to be a very important theme for the 0.4 release. The goal is to attempt to finalize the *core* Handly APIs within the 0.5 time frame (Eclipse Neon). To accomplish that, we should try to get the necessary API changes into the 0.4 release, in order to allow sufficient time for community feedback (and further changes, if necessary).
Here is a tentative (most probably incomplete) list of enhacement requests related to API quality:
Necessarily, this work will result in some breaking changes (hopefully for better than for worse). Therefore, I wanted to inform everyone about the scope of ensuing changes sooner rather than later. Please feel free to comment on these bugs or add yourself to CC list to stay up-to-date with ongoing development. It is also a good opportunity to raise concerns if there is something you strongly disagree with, or submit additional requests regarding API. I will try to keep you informed via this list as we're approaching the goal of better API quality.
Thanks and best regards,