23 November 2009
Current Status On JavaFX 1.3
Some people at the conference have also reported that some of the new JavaFX 1.3 controls were demonstrated using the GUI designer for NetBeans. The major question is will JavaFX 1.3 come with NetBeans 6.8? Currently there is no official word on exactly what new controls will be included in JavaFX 1.3. What is an important question though is will the GUI designer handle the visual design of animations? Also how does the GUI designer differ from the JavaFX Authoring tool?
Prism may actually be the new JavaFX runtime starting with JavaFX 1.3? This is certainly confusing as I originally thought that prism was only a rendering system, all will be revealed when JavaFX 1.3 is released. One person who reported on the Prism demonstration at Devoxx mentioned that it is lightning fast performance wise. It will be interesting to see how that performance scales when there are many nodes on the scenegraph and/or a lot of binding is involved.
Unfortunately there is no official word on when the JavaFX mobile emulators will be released for Linux, although there is the old screenshot that shows the JME (Java Mobile Edition) 3 SDK in action on Linux. Hopefully the mobile emulators will be arriving soon. As always there is nothing official being released about the exact release date for JavaFX 1.3 (it will be released as soon as its ready – good things take time :<) ).
Oracle wise (not the actual company) I think that JavaFX 1.3 will most likely be released around the middle of December after the release of NetBeans 6.8. Again I am just repeating what I have mentioned in a previous post. It will be most interesting to see exactly when JavaFX 1.3 is released. Apparently JavaFX 1.3 will be targeted for release around Jan/Feb 2010 (Jonathan Giles mentioned this in a Twitter) which is a long time away. Prism will most likely not appear in JavaFX 1.3, but will be demonstrated at JavaOne 2010. A possible reason for this might be that Prism will be handling full 3D in the next release of JavaFX after SoMa.
16 November 2009
Introducing JFX Blocks
Introduction
Often there will be parts (blocks – see further down for an explanation) that you want to add to an existing or new application. These parts are missing items of functionality which make the application complete. Today's issues often revolve around being able to quickly and easily find parts that adequately satisfy the functionality that is missing without adding bloat.
But when some parts are found you often find yourself in the situation where other parts have to be used, and/or some prior configuration (significant amounts) is required before using it. Frameworks are extremely poor when it comes to supplying what you need since there is additional baggage that has to be handled as mentioned above.
How does one grab what they need without requiring anything else? A key answer to this is with platform libraries since they do not require you to use what you don't need. Instead the libraries underlying design (eg through loose coupling) permits software developers to use only what they need, and not what they don't want.
An inspiration of this is the NetBeans Platform because the designers have taken into consideration that every application is different in terms of its requirements, and have designed the platform as such that if anything else is required it has sufficient design reasons for including it (eg makes it easier to implement a given piece of functionality).
Another issue is being able to easily integrate a part into an existing application. Especially if this application is used by the masses. Difficulties arise when significant changes need to be made in order to incorporate the part. In this situation you would go for a different part (from a different supplier - see further down for an explanation) provided there are some choices out there.
Certainly we are starting to see the emergence of platform libraries as a trend away from frameworks. So you could be mistaken for thinking that libraries are back with a vengeance. Indeed that is exactly what is occurring since software developers are after a balance between flexibility and simplicity when building applications.
JFX Blocks is designed to quickly and easily build new JavaFX applications (mobile and desktop, not mobile web), and add functionality to existing JavaFX applications. Currently JFX Blocks is at the design stage therefore any core functionality that is mentioned may change.
Main Aims
Emphasise a declarative approach to building applications with a focus on what is needed
Use mixins as “building blocks” to easily build against other existing code
Minimise or remove the need for configuration before using a “block”
Provide default behaviour for every “block” so it is usable straight “out of the box” in a new or existing application
Emphasise the use of design to provide “blocks” that produce huge benefits with little effort
Maintain high documentation standards that incorporate an extensive use of examples (samples) for getting started
Minimise the use of tight coupling
Maintain high coding standards
Provide core functionality that will work on both mobile (not mobile web) and desktop applications without any major changes (JFX Blocks common profile)
Terminology
Block – A self contained piece of functionality that is loosely coupled (a mixin)
Container – Contains a set of blocks that handle a specific (unique) area (a JAR)
Blueprint – Like a block except it contains no default behaviour and it only specifies how to structure something (a mixin that is like a interface)
Connector – Enables a block to be “connected” to an application (a class)
Supplier – Designs and creates the blocks/containers/blueprints/connectors
Builder – The user that builds or partly builds an application using what is provided by supplier(s)
Core Functionality
A basic (generic) lookup system that can obtain physical files, JAR resources
IO (Input/Output) utilities
Factory for controlled creation of “blocks”
Handle all aspects of the application's lifecycle (eg startup, shutdown, resource loading, setting up user settings)
A basic (generic) persistence system for general data, program and user settings
09 November 2009
First Impressions Of Ubuntu 9.10
Display Woes
Smooth sailing wasn't to be the case with the live CD failing to display anything at all. In order to get something displayed the resolution was changed through the use of two keyboard shortcuts (Ctrl+Alt++, Ctrl+Alt+-). Normally most people (non technical) would give up at this point so Ubuntu was not making a good impression so far. At that point the installer could then be started.
Luckily the install went very smoothly and after a reboot everything seemed to be going fine until.... more problems occurred. Once EnvyNG (video driver management for ATI and NVidia video cards) was installed I had tried to run it but to no avail. It turns out that one has to install the envyng-qt package since envyng-gtk is broken. After a reboot the display was showing the CLI login prompt which was flickering for some strange reason.
When I tried entering in the username no characters were being displayed at all. This happened to be one of the most irritating parts of installing and setting up Ubuntu since many people (who have an ATI or NVidia video card) were having the exact same issue, and it took a long time to resolve (a matter of hours). Even worse was the fact that the Nvidia driver package is currently broken thus there is no GUI login being displayed.
Once the NVidia drivers were installed using the version supplied on the official NVidia website some progress was finally being made. Not all the display issues had been resolved yet since not all of the resolutions were being picked up properly. This part took the longest amount of time to resolve through trial and error with editing /etc/X11/xorg.conf. In my case I had eventually reached the point where I had to put up with the resolutions that the NVidia driver had picked up. Luckily after commenting out the "HorizSync" and "VertRefresh" lines in the monitor section, and logging in again all of the resolutions were then picked up properly.
What Is New And Different
- Many packages in the Ubuntu repositories have been updated including NetBeans, and the Sun JRE (Java runtime)
- Firefox is now at version 3.5.4
- Open Office is now at version 3.1.1
- Gnome is now at version 2.28.1
- Vastly improved general performance (start up times are so quick that they rival the Hibernate mode)
- The new Palimpsest Disk Utility 2.28.0 has been included, more details to follow
- Introduction of the new Ubuntu One service, more details to follow
- Default option to use the new ext4 file system when partitioning
- Linux kernel is now at version 2.6.31-14
What is most notable about the current Ubuntu release is the introduction of the brand new Ubuntu One service. Ubuntu One allows contacts, notes, and files (2GB free storage) to be synchronised with one or more Ubuntu (9.10 or later) PCs. Initially when I logged into the service (via Firefox) a message was displayed saying there was a version mismatch with the server. An OS update quickly resolved the problem with updating the Ubuntu One desktop client to handle the current server.
I would advise anyone who is using Ubuntu One on Ubuntu to use Nautilus (file browser) when uploading a batch of files, since the web client is slow and produces errors every time a file is uploaded. With the desktop client you can add directories and files to the Ubuntu One directory. For example with the joe user this is located in "/home/joe/Ubuntu One". Every time you add or remove a directory and/or file the client automatically synchronises the changes whenever your computer is connected with the service.
Another notable change in Ubuntu is the new Palimpsest Disk Utility. Palimpest manages disk partitions, and provides very handy diagnostic information on partitions and all storage devices. It is absolutely amazing what you can find out using this handy utility. For example one can find out about the current airflow temperature for a particular storage device, and can see what the normal temperature is supposed to be. Also Palimpest automatically notifies the OS if there are any major problems, and can perform some tests on the user's behalf for a particular storage device.
One other major change is the brand new refreshing Ubuntu look. This look reminds me of the JavaFX look, classy, legible, and visually appealing which doesn't take up too much screen real estate (netbook friendly).
Lastly Ubuntu's Add Software has been replaced with the new Ubuntu Software Center. When using the software center you can no longer install/uninstall a group of software at once, and more details are provided for each piece of software (including a screenshot, package name and version etc). Installation and uninstallation of software is now handled in the same window used to browse software, and one can swap between "Get Free Software" and "Installed Software" tabs with navigation being remembered with "Get Free Software".Current Issues
Sound performance in my case is much worse than in Ubuntu 8.04. There is a very noticeable sound lag (consistent) which wasn't present before. Hopefully this will be resolved in the next batch of OS updates. Wireless networking is now a bit of hit or miss. It used to be in Ubuntu 8.04 that if the IP address was not picked up through DHCP the first time, then the second attempt would always pick up an address. However with Ubuntu 9.10 I usually have to restart the wireless router in order for an IP address to be obtained properly. Again the next batch of OS updates should resolve this.
Conclusion
For people who have an ATI or NVidia video card in their machine, and are currently thinking of installing Ubuntu 9.10 are advised to hold off until Ubuntu 10.04 LTS arrives. The reason for this is because 10.04 is a long term support release which is supposed to be much more robust for hardware support, and OS stability. If your machine contains an Intel video card then 9.10 is for you since many improvements have been made with supporting Intel video cards out of the box.
02 November 2009
Why Oracle Should Dump JDeveloper For NetBeans (Update)
What is not certain is how Oracle are going to support NetBeans. Perhaps Oracle will be releasing plugins for NetBeans just like they are currently doing for Eclipse? This is probably a mere coincidence but NetBeans is moving to a completely new infrastructure (an announcement was made just a few days after the Oracle FAQ was released), I am sure that this has nothing to do with the timing of Oracle's FAQ.
On an unrelated side note the next version of NetBeans (version 6.8), which is going to be released around December will have JavaFX support ready straight away. Also all future NetBeans releases are going to be synchronised with the JavaFX releases (current and future) which should help increase development speed, and improve stability for the JavaFX plugin.
24 October 2009
Why Oracle Should Dump JDeveloper For NetBeans
When considering whether or not to support JDeveloper or NetBeans the following needs to be taken into consideration:
- Quality of support for development of JavaFX applications
- The ability of the IDE to support the big picture (supporting things that will make a difference in the long run for software developers)
- Support of widely used software development techniques (eg Agile development, Test Driven Design (TDD), team collaboration)
- Level of support for Polygot programming
- General IDE platform support
- Support for different types of software development (mobile, web, desktop, TV)
- User uptake of the IDE and IDE platform
JDeveloper Advantages
- Very good support for enterprise software development (for web development)
- Comprehensive support for software diagramming
- Reasonable built in diagnostic tools
- Ready to use out of the box for web development
- Very good support for developing DB based applications
- Good performance
JDeveloper Disadvantages
- No support for mobile and TV development
- Poor support for desktop development
- No support for Polygot programming
- Does not support JavaFX development
- Very limited uptake of IDE and IDE platform
- IDE platform is mainly used in some major Oracle products
NetBeans Advantages
- Reasonable support for enterprise software development (for web development)
- Very good support for desktop, mobile and TV development
- Reasonably good support for JavaFX development (currently #1 IDE) *1
- Very good support for Polygot programming (currently supports JavaFX Script, Java, Ruby, PHP, Groovy, C/C++)
- IDE and IDE platform are very widely used (high uptake among businesses and software developers)
- Very good diagnostic tools (including profiler and debugger)
- Excellent usability and out of the box experience
- Reasonably good performance
NetBeans Disadvantages
- Limited support for developing DB based applications
- Limited support for software diagramming
Some major questions remain on the very existance of JDeveloper.
- Why did Oracle create JDeveloper when they could have used Eclipse or NetBeans instead?
- Why is JDeveloper designed to be similar to NetBeans (eg with the user interface)?
- Why does JDeveloper have such poor adoption rates compared to NetBeans?
- Why is Oracle taking such an interest in the NetBeans IDE platform when it directly competes with JDeveloper's IDE platform?
For the first time the development of the JavaFX NetBeans plugin has been syncronised with the general development of the NetBeans IDE. It is expected that when NetBeans 6.8 is released that a JavaFX bundle will be available at the same time (on the official downloads web page). Such a change will further bolster the commitment NetBeans has to supporting JavaFX development, and will bring about stronger support in the future. Since Oracle is going to support JavaFX (in a big way) they will find themselves in an very difficult situation should they not support NetBeans (*1).
With the current situation of NetBeans not lagging far behind Eclipse (*2), and the fact that JDeveloper is not one of the top three IDEs is there really room for a 4th IDE (apart from NetBeans, Eclipse, IntelliJ Idea)? Is Oracle willing to get offside with software developers by not supporting NetBeans?
There is a potential risk that if Oracle does not support NetBeans then there could be a mass migration of developers from the Java platform to the .NET platform. Some reasons for this are:
a) NetBeans is more similar to Visual Studio than Eclipse. Why would NetBeans users go to Eclipse when Visual Studio is more familiar? Already there are many Java developers that are doing some software development part time on .NET. Many software developers consider having to use Eclipse (for development on the Java platform) a major step backward from a quality perspective.
b) Possible perception by some software developers that Oracle is not acting in the best interests of the Java platform by removing a major choice, that helps move the platform forward. One can see some of this in the NetBeans Users mailing list, it could be the tip of the iceberg.
*1 - As indicated in an informal poll conducted by Jo Conner
*2 - As indicated in an informal poll by Jo Conner and in a recent poll on java.net
15 October 2009
Should There Be A DB API For JavaFX?
So it is time to start the debate on a DB API for JavaFX. Lets say hypothetically a DB API was to be designed for JavaFX. This DB API would have the following design considerations:
- Provide a consistent API that can provide basic features across all hardware platforms (desktop, mobile, TV)
- Allows advanced DB features to be accessed by desktop JavaFX applications only
- Minimises its footprint and provides as many features as possible, without using too many resources on mobile devices
- Allows seamless conversion between JavaFX Script and DB data types
- Provides reasonably good performance (including on mobile devices)
- Can easily allow syncronisation of data between the JavaFX application and the database in very few steps
- Provides the cabability of querying the DB for internal information without requiring the JavaFX developer to describe the DB structure beforehand
Database API Advantages
- Can use a database with a CLDC profile device (mobile JavaFX uses CLDC as the base)
- Can easily use all JavaFX Script and JavaFX features (eg binding, triggers, functional programming)
- Provides an opportunity for JavaFX to gain a major advantage over its RIA rivals
- Can take advantage of Oracle's excellent DB design expertise (when the acquisition of Sun goes through)
- A single DB API that can be used across all hardware platforms (desktop, mobile, TV)
- Able to populate JavaFX controls (both visual and non visual) quickly and easily with very few steps
- Seamless conversion between DB and JavaFX Script data types
- Reasonably good performance with JavaFX having direct access to the DB
Database API Disadvantages
- Will require JavaFX developers to learn a completely new API
- Generics and reflection will not be available to incorporate into the design of the DB API
- DB API will require existing DBs to supply new drivers
- A new DB may need to be created from the ground up to work accross all hardware platforms (incl with CLDC profile devices)
- May require existing DBs to adjust their design/implementation in order to be compatible with the DB API
- Very challenging to design and implement an effective DB API (may take at least a year before it is ready for production use?)
Now the "should there be a DB API for JavaFX" could very well become one of the biggest JavaFX debates of the year. Currently the DB API for JavaFX should not be considered a high priority at the moment, since JavaFX is mainly aimed at creating graphical applications. Therefore stuff like 3D support is a much higher priority for inclusion in JavaFX.
I intend to make it very clear that I am not a member of the Sun JavaFX team. What I have mentioned above is my own opinions and in no way reflects the opinions of the Sun JavaFX team.
07 October 2009
What Next For JavaFX? (Update)
- Grid Layout (+)
- Spacer (+)
- Separator (+)
- Menu (+)
- Menu Button (+)
- Custom List Cell (*)
- Search Box (*)
- Password Box (+)
- Text Area (+)
- Table (+)
- Spinner (+)
- Dialog (^)
- Multi Style Text Area (*)
- Popup (+)
- Tooltip (^)
- Status Bar (*)
- Tree (+)
- Tool Bar (*)
- Split Menu Button (*)
- Choice Button (^)
- Border (^)
- Split Pane (-)
- Combo Box (+)
- Scroll View (+)
As you can see there are quite a range of controls for the next release! However there is no calendar and tab controls, and some of the controls mentioned above may appear in the internal com.sun package instead. Also note that any controls that end up in the com.sun package are to be considered experimental, just like all the other APIs in com.sun. Luckily from the community there is a Calendar Picker control that is good enough for production use, even though it is currently in beta. For the tab control there is nothing present from the community although it is non trivial to create compared to the calendar control. I do wonder if the Grid Layout control is in fact a new layout.
On to the new and enhanced functionality the majority of the functionality is in the graphics area. Here is the list of functionality that will either, be in SoMa (+), not in SoMa (-), highly likely to be in SoMa (*), or may be in SoMa (^). Do note that this list may change as more information is known about what will be included/not included in SoMa.
- Stage level keyboard and mouse event handlers (*)
- Cloning/duplication of nodes (*)
- Built in callback function variables for state change notification on all controls (+)
- Control key functions are supported in TextBox control (+)
- Controls can be autosized (+)
- 3D transformations for 2D graphics nodes (+)
- Support for 3D bounds (+)
- Can use an image as Paint with 9 slice scaling and tiling for controls (+)
- Perspective and Parallel camera classes for 3D perspective transforms (+)
- Support for 3D rotations (-)
- Non visible controls do not recieve mouse clicks (^)
- Performance tracker for Prism (+)
- Camera/video and microphone capture (-)
- Can remove a parent from a node (+)
- Event bubbling/filtering (-)
- Pixel access (-)
- Support for maps as a core language construct (-)
Based on the 3D graphics functionality for the next release JavaFX will start to develop basic support for doing 3D graphics. Currently think of it as 2.5D where JavaFX is going through a transitional phase. Expect the next release after SoMa to have proper support for basic 3D graphics. Just imagine all the interesting possibilities with 3D graphics for JavaFX apps on desktop, mobile and TV :). There will definitely be other functionality that gets included in SoMa where there is no publicly available information about it.
Expect the JavaFX 1.3 release to not be too far away since the JavaFX TV plugin for NB (NetBeans) has been ready since Sept 14, and is going to be available when the JavaFX 1.3 NB plugin is integrated with the IDE. Already the installers are currently being developed for SoMa. It is only a matter of time (in days?) before JavaFX is released.