-
Notifications
You must be signed in to change notification settings - Fork 917
Updating HTML/Java API to 1.7.3 version #3357
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Updating HTML/Java API to 1.7.3 version #3357
Conversation
dbalek
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Proposed API looks fine to me.
lkishalmi
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well, skimming through, I've not found anything wrong with this.
neilcsmith-net
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As with @lkishalmi I have only skimmed through. Seems a good idea. I would happily see the back of all HTML dialogs in the IDE though!
HTML/Java API has recently released its 1.7.3 version which (among other) gives proper OSGi bundle names to its modules. Former
genericmodule is noworg.netbeans.html.presenters.spi. Time to upgrade.When at it, I am also splitting the
api.htmluimodule to two parts. The goal is to move the JavaFX WebView based implementation into its own module and allow the API to be used without it. That's all built aroundHTMLViewerSpiinterface. 40f460e adds a fallback implementation of the SPI interface that warns the user gracefully.Also, to satisfy old @dbalek request, I am introducing
OnSubmitcallback that, allows validation of the state of the dialog before it is closed.The commit c182fc3 modifies
nbjunitmodule. I tried to useMockServicesin TestNG without depending on JUnit4 and was getting linkage errors. Replacing the exceptions withjava.lang.AssertionErrorfixes the problems.This PR is the first in a line of others. The ultimate goal is to get Rich HTML UI for (now only for) VSCode Refactorings as outlined in #3349 into NetBeans and its VSCode extension.