Browser Suite v0.9 coming soon to a website near you!
Published by admin on
Monday, December 21, 2009 - 05:55:48
- Filed under General, News, Announcements, Development
Hi there!
For those of you expecting the end of the story, I’m asking for a little bit of patience…
Right now, I’m hard at work on the Browser Suite (for a change ;-), currently writing an extended documentation with (hopefully useful!) explanations of all the properties and methods, tips and tricks and examples of usage. All this in a nice PDF with table of contents, screen captures, and all the bells and whistles…
And while I’m working on the doc, I made a few changes to method names and signatures, mainly harmonizing the names to better match Servoy’s conventions like calling the event methods with a name starting by “onXXXX”, adding a JSEvent first parameter to all the event callbacks, adding comments to the sample solution and generally fixing everything I can (while I can).
Which means that there will be a few changes here and there, and if you are already using the Browser Suite you will need to adapt your scripts (nothing major, though :).
I thought that since the suite is not yet production-ready, it was now or never to harmonize all this stuff. Once the suite reaches v1.0, I will make sure to keep backward compatibility from then on.
So, with an up to date documentation (that will be included, as an optional install package, in the installer), this will lead to a brand new 0.9 version, where every methods and properties names will be fixed for the future… And only bug fixes for the rest of the cycle until v1.0
You can expect this version between now and next year :)
In the meantime, let me send you my virtual wishes for a happy new decade!
Open list of bugs to vote for in the Eclipse bugzilla system
Published by admin on
Monday, December 7, 2009 - 05:25:43
- Filed under General, News, Development
There has not been too much activity on the Eclipse bugzilla system lately, related to the bugs we (Christopher Deckers and myself) uncovered with our port of the DJ-NativeSwing library in the Browser Suite for Servoy… so I’m putting here a list of direct links to the opened bugs asking you to vote for their resolutions if you intend to use the Browser Suite in the future, because you (or your client) will be affected by them.
These ones are all Mac OS X related (but surely you have Mac clients too?):
- https://bugs.eclipse … ow_bug.cgi?id=291326
[SWT/AWT] Freeze when making a sync SWT call in response to certain Swing events - WAITING
- https://bugs.eclipse … ow_bug.cgi?id=291705
SWT_AWT: new Browser SWT.MOZILLA gives NPE in MozillaDelegate - NOW FIXED!
- https://bugs.eclipse … ow_bug.cgi?id=291328
[SWT_AWT] NPE when accessing a browser custom context menu - WAITING
- https://bugs.eclipse … ow_bug.cgi?id=295795
[SWT_AWT] Popup menu in browser freezes app - WAITING
- https://bugs.eclipse … ow_bug.cgi?id=295794
[SWT_AWT] App freezes when tooltips are called in browser - NOW FIXED!
- https://bugs.eclipse … ow_bug.cgi?id=295792
[SWT] Browser issue: open a window from link or script doesn’t work - FIXED IN SWT- pending in DJNativeSwing
- https://bugs.eclipse … ow_bug.cgi?id=293276
[Browser] SWT_AWT: can’t type in MOZILLA Browser HTML fields - NOW FIXED!
These ones are Windows specific and might or might not affect you or your users:
- https://bugs.eclipse … ow_bug.cgi?id=221235
[Browser-IE] VisibilityWindowListener.show() is not called - WAITING - But in the Browser Suite, a workaround (opening modeless dialogs) is implemented
- https://bugs.eclipse … how_bug.cgi?id=90023
Browser 3D content border not consistent - WAITING - But minor issue (almost unnoticeable)
- https://bugs.eclipse … how_bug.cgi?id=84532
[browser] Browser widget does not send focus events - WAITING - But not used in the Browser Suite
On Linux there is this one that I know of:
- https://bugs.eclipse … ow_bug.cgi?id=225401
[SWT_AWT] Removing the AWT Canvas generates a Gtk-CRITICAL message - FIXED
For all platform, this one fix could also help:
- https://bugs.eclipse … ow_bug.cgi?id=292062
Provide a way to dynamically introspect an SWT port info - WAITING - In the meantime a workaround has been implement in DJNativeSwing
Voting for the resolution of these bugs is as easy as registering on the Eclipse bugzilla system (you won’t get any spam from them!), and clicking on the ‘vote’ link on the pages above, so I say it again: if you intend to use the browser suite in the near future, it is impotant that these bugs are fixed, otherwise you or your clients will suffer from them…
You can also comment if you like, stating that these bugs are actually delaying the need you have of an SWT port on Servoy, this will be true.
Thanks in advance!
Java Web (doesn’t) Start
Published by admin on
Tuesday, December 1, 2009 - 06:10:56
- Filed under General, News, Development
That’s what you could call this wonderful technology that Sun created a while ago, to easily deploy rich clients on any(!) platform, providing that this platform have a proper JRE installed.
And true to its usual motto: ‘write once, debug everywhere!”, Java Web Start actually works great… most of the time. Because then again, you have the usual black sheep (Mac OS X, you’ve recognized it) that never really does thing like any other… One might say that it is a blessing, and sometimes that’s quite true, but when it comes to Java, I’m afraid it is rather a curse.
So, the first step was to make the DJ-NativeSwing demo app work from Java Web Start (JWS for those who love abbreviations) on all the target platform: Windows, Linux and Mac OS X. Armed with the latest SWT nightly build I thought it would be a piece of cake. True for Windows and Linux, although there was the occasionnal tweaking of a few flags, like the infamous -Dsun.awt.disableMixing=true (this one will really be used from Java 6u18 onwards, but I’ve tried it on early release, - to be on the safe side:).
On Mac OS X, I managed to make this work, on Leopard (10.5.8) using Java 5 32/64-bit and Java 6 64-bit only (because in its infinite wisdom, Apple decided not to release any Java 6 32-bit for Leopard, only for the new Snow Leopard - 10.6 - go figure!). So it was working fine on Leopard, and I decided that it would be nice to try it on Tiger (the previous beast: 10.4.x), because there is Java 5 available and I thought that it would be nice to be able to say to users that this stuff was compatible Tiger or more…
[Read More…]
