Blog Posts

Blog Posts: 284
Items per page
Statistics: Blogs: 48 Blog Posts: 284   1 2 3 ... 10 Previous Next

JxBrowser team is happy to announce a long-awaited release of JxBrowser 2.4 with 64-bit platforms support.

 

In this version we have implemented support of JDK 64-bit for IE engine on Windows, Mozilla engine on Linux and Safari engine on Mac OS X. Please note that Mozilla engine still doesn't support JDK 64-bit on Windows and Mac OS X, because Mozilla browser officially doesn't support 64-bit environment on Windows and Mac OS X platforms.

 

In this update we also added Proxy functionality support for Mozilla and IE engines and other features that you can see on the JxBrowser 2.4 Release Notes page.

 

The update is already available for download. You can try the new version online using the WebStart Demo.

 

For any help or feedback related to the use of our product, please use the support forum or e-mail us directly.

0 Comments Permalink

New Features:

  • IE engine supports JDK 64-bit on Windows;
  • Mozilla engine supports JDK 64-bit on Linux;
  • Safari engine supports JDK 64-bit on Mac OS X;
  • Added Proxy functionality for IE and Mozilla engines;
  • Added DOMElement.click support for Mozilla engine;
  • Added support of custom XULRunner directory extraction path for Mozilla engine.

 

Improvements:

  • Added focus support for Mozilla engine;
  • Added the DialogParams.getBrowser method;
  • Added the NewWindowParams.getParent method;
  • Implemented loginRequested hanlder in DefaultPromptService;
  • Added support for Flash Player 10 into IE engine.

 

Resolved Issues:

  • Mozilla Engine:
    • HTTPS web page with invalid certificate are displayed correcntly now;
    • Problem with focus after closing popup window on Linux and Mac OS X platforms is resolved;
    • The Browser.executeScript method does not fail when Browser is closed from JavaScript;
    • The Browser.waitReady method now works correctly after Browser.setContent;
    • Now Navigation method works for local PDF file;
    • Swing popup menu will be closed when user clicks on Mozilla Browser component.

Known Limitations:

  • Proxy functionality doesn't work for IE engine on JDK 64-bit.
0 Comments Permalink

We're pleased to present the second Early Access release for OpenFaces 3.0 with JSF 2.0 support. This release features tighter integration with the JSF 2.0 infrastructure, which has resolved most of the problems that existed in the previous release. Here are the most notable fixes:

  • fixed Ajax functionality for DataTable, TreeTable, CompositeFilter and all other components;
  • fixed compatibility with the standard JSF 2.0 Ajax APIs (the <f:ajax> component, and jsf.ajax.request() JavaScript function);
  • made possible to attach client behavior tags, such as <f:ajax> to all OpenFaces input and command components

 

Besides, it is now easier to add OpenFaces to your application -- you just need to add OpenFaces jar with its dependencies to your application. No web.xml modification and resource filter registration is required anymore!

 

You can download this version and the demo package that runs on Tomcat and GlassFish v3 here (see the OpenFaces 3.0 Early Access 2 section). If you've used the previous release, please also read the migration instructions in the release notes document.

 

This is the last milestone before the final release of OpenFaces 3.0. We'd like to have your feedback on how it behaves in your JSF 2.0 applications in order to polish the library by the actual release. Please post your feedback and share your experience on the product's forum.

2 Comments Permalink

Here are the changes that were made since the previous early access milestone.

Improvements

  • It's now easier to add OpenFaces to your application: you just need to add OpenFaces jar and its dependencies. No web.xml modification and resource filter registration is required anymore. See the "Installation and Configuration" section in developer's guide for details.

Resolved Issues

  • Fixed Ajax functionality for DataTable, TreeTable, CompositeFilter and all other components.
  • Fixed compatibility with the standard JSF 2.0 Ajax APIs (the <f:ajax> component, and jsf.ajax.request() JavaScript function).
  • Made possible to attach client behavior tags, such as <f:ajax> to all OpenFaces input and command components.

Known issues

  • Session expiration notification for Ajax calls doesn't work currently.

 

Migration Instructions

  1. OpenFaces requires the latest version of Mojarra, 2.0.3, since it has some fixes critical for proper functionality of OpenFaces components. You can download Mojarra 2.0.3 here. If you're running your application on Glassfish application server, make sure to update Mojarra in Glassfish (see the instructions).
  2. Remove ResourceFilter declaration and mapping from application's web.xml.
  3. Make sure to use <h:head> and <h:body> tags instead of old-style plain <head> and <body> tags.

 

Note: running OpenFaces demo, which is available for download, on Glassfish application server, requires the latest version of Mojarra (Mojarra 2.0.3) to be installed in the Glassfish server. See the installation instructions.

0 Comments Permalink

JxBrowser has been updated to version 2.3.1.

 

Improvements

  • Added support of focus transfer between Mozilla Browser component and Swing UI components;
  • Added Flash Player 10 support for IE engine.

 

Resolved Issues

  • Mozilla Engine:
    • Browser component can not be initialized in Java Applet;
    • The executeScript method fails in case of "window.close();" JavaScript code;
    • Mac style native menu disappears after creating new browser instance;
    • Crash of JVM after multiple JavaScript executions.
  • IE Engine:
    • Navigation method does not work for local PDF file.

 

The full list of changes is available at JxBrowser 2.3.1 Release Notes page.

 

The update is available for download.

 

For any help related to the use of our product, please use the support forum.

0 Comments Permalink

Improvements:

  • Added support of focus transfer between Mozilla Browser component and Swing UI components;
  • Added Flash Player 10 support for IE engine.

 

Resolved Issues:

  • Mozilla Engine:
    • Browser component cannot get focus;
    • Problem with focus after closing popup window on Mac OS X and Linux platforms;
    • Browser component can not be initialized in Java Applet;
    • The executeScript method fails in case of "window.close();" JavaScript code;
    • Mac style native menu disappears after creating new browser instance;
    • Crash of JVM after multiple JavaScript executions.
  • IE Engine:
    • Navigation method does not work for local PDF file.
5 Comments Permalink

JxBrowser, our cross-platform library that allows integrating web browser into Java AWT/Swing applications is updated to version 2.3.

 

In this update we focused on Mozilla engine stability issues. By digging into the issues reported by our customers we have practically re-implemented Mozilla engine from scratch. The effort paid off by much more stable and reliable Mozilla engine and a handful of other updates. For the full list of resolved issues and improvements, please see the JxBrowser 2.3 Release Notes page.

 

The update is already available for download. You can try the new version online using the WebStart Demo.

 

For any help or feedback related to the use of our product, please use the support forum or e-mail us directly.

0 Comments Permalink

Improvements:

  • Improved Mozilla engine stability for Windows, Mac OS X and Linux platform;
  • Updated Mozilla XULRunner to 1.9.2 (Firefox 3.6) version on Linux and Mac OS X platforms;
  • Added HTML5 support in Mozilla engine;
  • Added Tooltip support for Mozilla engine;
  • Made Mozilla the default browser on Mac OS X PPC platform ;
  • Added build version into JxBrowser JAR Manifest.

 

Resolved Issues:

  • Mozilla Engine:
    • Crash of JVM on navigate to web page with Flash content (Linux and Mac OS X);
    • Browser component cannot be added-removed-added into Swing container multiple times with JDK 1.6 (Linux);
    • Browser component hangs on dispose when at least one tooltip is displayed;
    • Crash  when display a JavaScript confirmation or prompt dialog (Linux);
    • JavaScript dialogs is not modal (Linux);
    • Browsing to a non existing page does not fire NavigationFinished event;
    • Crash on Ubuntu 9.10 32-bit (Linux);
    • Sometimes JavaScript execution hangs up;
    • The Browser.executeScript method should return only after JavaScript code is executed;
    • JavaScript popup boxes don't prevent dom events (Linux);
    • Sometimes popup window is not opened;
    • Two JavaScript alerts are displayed through double click (Linux);
    • JavaScript modal dialogs do not work (Mac OS X);
    • NavigationListener doesn't work properly;
    • Popup windows do not resize correctly;
    • Prompt dialog does not work when it is invoked from browser that can be created by NewWindowManager;
    • Add/remove Mozilla engine Browser component crashes application (Linux);
    • Swing short cuts cause hang up of native message loop (Linux);
    • The Browser.setContent doesn't render html content without meta tag;
    • The target window parameter doesn't work;
  • IE Engine
    • Incorrect work of SilentPromptService;
    • The Browser.toImage method return a corrupted image;
    • Fail on close after displaying PDF document.

 

Known Limitations:

  • Mozilla engine on Linux platform supports JDK 1.6.0_12 or newer;
  • Sometimes Mozilla engine browser component cannot get focus.
0 Comments Permalink

TeamDev is happy to announce official release of JxCapture 2, a cross-platform library that provides a comprehensive screen and video capture API for Java applications on Windows and Mac OS X platforms.

 

With JxCapture 2, you will be able to capture a screen or a screen area activity and save the result to a movie file. The API allows to specify the resulting movie format, size, bitrate, codec, audio source, etc. For the full scope of changes please check out the JxCapture 2 Release Notes.

 

You can try out the new version online using the WebStart Demo. The JxCapture 2, including demo application and samples, is available for download. Samples in distribution package will demonstrate how you can capture full screen, window or a region, configure capturing options and more.

 

For any help or feedback related to the use of our product, please use the support forum or e-mail us directly.

0 Comments Permalink

New Features:

  • Added audio recording features (WMV and AVI formats only);
  • Ability to get the collection of audio recording devices (in this version for Windows platforms only);
  • Ability to select an audio input device to enable video capture with sound;
  • Ability to specify a required audio codec and its settings;
  • Added video player Java component (Windows only) which allows to play a video file in Java application;
  • Added the ability to select audio source and audio codecs for recording (Demo application).

 

Improvements:

  • Added ability to specify video bit rate mode (VBR, CBR) for WMV;
  • Added ability to modify key frame interval for WMV;
  • Added support of new "Windows Media Video 9 Advanced Profile" (WVC1) video encoder.

 

Known limitations:

  • No support of 64-bit JRE on Mac OS X 10.6;
    • Solution in this case is to run JRE in 32-bit mode;
  • No audio recording for Mac OS X (planned to future versions);
  • No ability to select available audio recording devices on Mac OS X (planned to future versions);
  • There is no native video playback component on Mac OS X.
3 Comments Permalink

We're glad to announce the first early access milestone of the new OpenFaces 3.0 version featuring JSF 2.0 compatibility. Now developers creating JSF 2.0 based applications have access to rich possibilities provided by all kinds of OpenFaces components, ranging from DataTable and TreeTable for flexible data display, to BorderLayoutPanel and Window for creating various layouts, and Validation framework for client-side validation and additional validators.

 

OpenFaces 3.0 will be maintained in parallel with OpenFaces 2.0 and both of them will have the same set of features, but they will target different versions of JSF: 2.0 and 1.2 respectively. The final release for the OpenFaces 3.0 version is expected in June.

 

You can download the new version and the demo package that runs on Tomcat and GlassFish v3 here (see the OpenFaces 3.0 Early Access 1 section).

 

As JSF 2.0 support is currently on an intermediate stage, some functionality is limited yet and there are the following known issues in OpenFaces 3.0 EA1:

- State saving during OpenFaces Ajax requests has some issues when using the built-in Ajax capabilities in certain OpenFaces components. Most notable consequences are: a) impossibility to use Ajax node folding in TreeTable, so only client-side node folding works fine yet, and b) DataTable paginator's "next" button which can't be used more than once.

- The CompositeFilter component doesn't work in this Early Access version.

 

Feel free to share your feedback and ask any questions on the product's forum. Stay up to date with the latest OpenFaces news by following us on Twitter.

8 Comments Permalink


We're introducing the new OpenFaces LevelIndicator component which is already available in the latest nightly builds.level-indicator-default-vertical.png

LevelIndicator  - a component that shows a numeric value in graphic style, similar to the LED volume meter and resource meter used in Windows Task Manager.

 

LevelIndicator component can be defined on the page using <o:levelIndicator> tag. LevelIndicator can be provided with the level value that it will represent. The value should be of typejava.lang.Double and be in [0..1] range.

 

On the following examples you can see the LevelIndicator component in it's default horizontal and vertical states.

level-indicator-default-horizontal.png

 

The component has transitionLevels and colors attributes, so using these attributes you can define value ranges and specify appropriate colors for them.

 

<o:levelIndicator value="0.8" colors="blue,orange,violet" transitionLevels="0.35, 0.6" />

 

The upper declaration defines that LevelIndicator component has two transition level points at 0.35 and 0.6,

this means that LevelIndicator has three value ranges([0 - 0.35] , [0.35 - 0.6] , [0.6 - 1]).

 

Each of defined value ranges will use each own color, defined in colors attribute of <o:levelIndicator> tag. The result component's representation can be seen on the example below.

level-indicator-with-custom-colors.png

As it can be seen from the example below, the component's styles and sizes can be easily customized to the desired look.

  <o:levelIndicator value="0.8"
                    style="background-color: #e6e6e6; border: 1px solid #333; width: 350px; height: 40px;"
                    segmentSize="5"
                    colors="blue,orange,violet"
                    transitionLevels="0.35, 0.6"/>

level-indicator-with-custom-css.png

0 Comments Permalink

We're glad to announce a preview of the JSF 2.0 compliant version of OpenFaces. This is not yet the 3.0 EAP1 milestone mentioned in our Roadmap, which will be published soon but you can already check out OpenFaces in a JSF 2.0 environment and give us some valuable feedback before the upcoming EAP1 version.

 

Here are the OpenFaces 3.0 Preview download files:

openfaces-3.0.preview1.zip -- contains the new openfaces.jar file and runtime dependency jar files.

openfaces-3.0.preview1-src.zip -- source code for the new version.

openfaces-3.0.preview1-demo.zip -- contains the demo application war file deployable under GlassFish v3 and Tomcat 6.x.

openfaces-3.0.preview1-demo-src.zip -- demo source code.

 

The installation instructions are the same as for OpenFaces 2.0 for now, see the documentation. Please note also that OpenFaces versions 2.0 and 3.0 are going to have the same features but run under different versions of JSF -- 1.2 and 2.0 respectively.

 

The JSF 2.0 compatibility support is on an intermediate stage yet though most of the components are already functional. Here are the known issues in this version:

- State saving during OpenFaces Ajax requests has some problems, which results in some issues with built-in Ajax capabilities in certain OpenFaces components. For example DataTable paginator's "next" button can't be used twice and there are certain problems when using the Ajax node folding in TreeTable (hwever client-side TreeTable node folding with preloadedNodes="all" works fine now).

- The CompositeFilter component doesn't work in this version.

- There are numerous validation messages at the bottom of each demo page, though these messages don't affect the demo application's functionality.

- The documentation is not updated to reflect the JSF 2.0 related specifics yet.

 

Please share your feedback and any issues that you might have on the forum.

0 Comments Permalink

TeamDev is happy to announce the Early Access* for JxCapture 2, a cross-platform library that provides a comprehensive screen and video capture API for Java applications on Windows and Mac OS X platforms.

 

In this version we have added support of video capturing on Mac OS X  and Windows platforms. With JxCapture 2, you will be able to capture a screen or a specified screen area activity and save the result to a movie file.  The API allows to specify the resulting movie format, size, bitrate, codec, etc. For the full scope of changes please check out the JxCapture 2 EA Release Notes.

 

You can try out the new version online using the WebStart Demo. The JxCapture 2 Early Access build, including demo application and samples, is available for download.  Note: The Early Access build is bundled with an evaluation license that expires May 30, 2010.

 

Please feel free to ask for help or just leave feedback at our support forum.

 

Stay tuned for new versions with more powerful and exciting features!

 

*Early Access gives you a chance to try the product out before it is officially released. Although we cannot guarantee that there will be no public API changes, or that certain features will be available in the final product, we will do our best to make your Early Access experience useful and future transition to the release version as easy as possible. Early Access - is your opportunity to contribute to the development process and  help us shape the product to fit your needs.

0 Comments Permalink

New Features:

  • New API for Video capturing which allows:
    • Capturing different screen areas such as:
      • Desktop;
      • Full screen (effective for multi-monitor desktops);
      • Custom rectangular area (with possibility to change the location of the captured rectangle during video capturing);
      • Specified window (full or a rectangle on the specified window);
    • Capturing with or without mouse cursor (in Early Access for Windows platform only);
  • API for fast resizing of the captured snapshots (in Early Access only for Windows. Mac native resizing coming soon).
  • Various video encoding features allowing to specify programmatically:
    • Output video formats:
      • WMV, AVI for Windows platforms;
      • MP4, MOV for Mac OS X platforms;
      • Custom video formats on Windows platform. *Requires additional third-party codecs.
    • Output dimensions;
    • Framerate (except AVI format);
    • Bitrate (except AVI format).

 

Improvements:

  • Improved the performance of image capturing;
  • Improved the performance of conversion to Java images;
  • Improved API for capturing images.

 

Resolved Issues:

  • Resolved the GDI leak issues.
0 Comments Permalink

We're introducing the new OpenFaces SelectOneMenu component which is already available in the latest nightly builds. This component is API-compatible with the standard <h:selectOneMenu> tag, though it provides such additional features as autocompletion support, displaying the drop-down items with JSF compnents and/or HTML markup, multi-column items display, etc. This component is still in development and some features are still going to be added, as well as its API which can still undergo minor changes before the release, though you can already check it out now.

 

The fact that it's API-compatible with its standard analog means that you can migrate to the OpenFaces version quite easily. Say, you have a standard combo-box, which is declared like this:

<h:selectOneMenu value="#{SelectOneMenuBean.selectedCity}" converter="#{SelectOneMenuBean.cityConverter}">
  <f:selectItems value="#{SelectOneMenuBean.cityItems}"/>
</h:selectOneMenu>

you can just replace the <h:selectOneMenu> tag with <o:selectOneMenu> to switch to the extended OpenFaces version of this component:

 

<o:selectOneMenu value="#{SelectOneMenuBean.selectedCity}" converter="#{SelectOneMenuBean.cityConverter}">
  <f:selectItems value="#{SelectOneMenuBean.cityItems}"/>
</o:selectOneMenu>

 

Doing this will turn on the autocompletion or automatic search functionality, where you can type a part of an item, a city in this case, and have the matching item to be highlighted automatically. This feature makes it possible to use combo-boxes even if you need to select from a very large number of items, say several hundred items, where using the standard SelectOneMenu component would be impractical. Here's how the latter declaration looks in the browser when searching for an item:

SelectOneMenu1.png

This component is not in the online demo yet, though you can download the nightly build demo that includes this example (deployable on Tomcat 6), and its source code.

SelectOneMenu vs DropDownField

Although the SelectOneMenu above looks very much like the DropDownField component, they have one key difference besides the API differences.

 

The DropDownField component (as well as its cousin SuggestionField) is essentially an input component, like other standard input components such as <h:inputText>. In other words, despite it contains the drop-down list to choose items from, the purpose of the DropDownField component is just the entry of text, and the component's drop-down list as well as the autocompletion functionality just assists the text entry. This particularly means that if for example the drop-down list contains two items with the same name (say London, UK and London, OH), it won't be possible to distinguish between them -- the DropDownField will just contain the "London" text when clicking on any of these items and it will be the same as if the user entered this text without even opening the drop-down list.

 

In contrast, the SelectOneMenu component is a select component, which means that although it allows typing item name in its embedded input field, its purpose is to select from a predefined list of items. So typing "London" (or a partial text) will open a drop-down list for selecting the desired option, and the selected item will be saved in the component and will properly reflect the original item object that corresponds to the selected item.

 

Nevertheless, the components have much in common, and the SelectOneMenu component has much of the DropDownField's API and possibilities, like customizing the suggestion options, and multi-column drop-down list display. These are briefly shown below.

Additional Customization Options

By default, typing in the SelectOneMenu's field brings the drop-down where all items are displayed and the one matching the typed string being highlighted. It is also possible to make SelectOneMenu filter the suggestion list and display only the matching items using the suggestionMode attribute, which can take the following values:

  • "stringStart" - Shows suggestions that begin with the entered value.
  • "substring" - Shows suggestions that contain the entered value.
  • "stringEnd" - Shows suggestions that end with the entered value.
  • "all" (the default value) - Shows all items in the list of suggestions.

 

The SelectOneMenu also has much of the API applicable to DropDownField component, and one of the notable ones is the ability to create multi-column drop-down lists using the embedded <o:column> tags.

 

So we'll add these two capabilities to our original example:

 

<o:selectOneMenu value="#{SelectOneMenuBean.selectedCity}"
                 converter="#{SelectOneMenuBean.cityConverter}"
                 var="city"
                 suggestionMode="stringStart">
  <f:selectItems value="#{SelectOneMenuBean.cityItems}"/>
  <o:column style="color: black">#{city.name}</o:column>
  <o:column style="color:gray">#{city.country}</o:column>
</o:selectOneMenu>

 

and the resulting combo-box will look like this as a result:

SelectOneMenu2.png

You can check out the DropDownField documentation for more customization options until ComboBox documentation receives its own documentation.

0 Comments Permalink

JxBrowser, a cross-platform library that allows integrating web browser into Java AWT/Swing applications on Windows, Linux and Mac OS X platforms, has been updated to version 2.2.

 

In this version we have implemented DOM functionality for all engines, added UserAgent property support and navigation status code in NavigationFinishedEvent.

Also this version contains fixes for the important issues reported by our customers:

  • Deadlock when dispose Browser instance from JavaScript in Internet Explorer engine;
  • Flickering issue when add/remove Browser component in Mozilla and Internet Explorer engine;
  • Internet Explorer engine throws the "Requested resource is in use" exception during web page loading;
  • MenuBar/PopupMenu and Context Menu still open when click on Browser component in Internet Explorer engine.

 

For the full list of resolved issues and improvements, please see the JxBrowser 2.2 Release Notes page.

 

The update is already available for download. You can try the new version online using the WebStart Demo.

 

For any help or feedback related to JxBrowser, please use the support forum or e-mail us directly.

0 Comments Permalink

New Features:

  • Implemented DOM functionality in Safari, Mozilla and MS Internet Explorer engines
  • Added NavigationStatusCode support for NavigationFinishedEvent
  • Added UserAgent support in MS Internet Explorer and Safari engines
  • Added extended DOM functionality

 

Improvements:

  • Added the dialog owner parameter in DialogParams

 

Resolved Issues:

  • Popup windows don't work on Linux and Microsoft Windows Vista with Mozilla engine
  • Dead lock when dispose Browser instance from JavaScript in MS Internet Explorer engine
  • Flickering issue when add/remove Browser component in Mozilla and MS Internet Explorer engine
  • MS Internet Explorer engine throws the "Requested resource is in use" exception during web page loading
  • MenuBar/PopupMenu and Context Menu still open when click on Browser component in MS Internet Explorer engine

 

Known Limitations:

  • Mozilla engine doesn't display web pages with Flash on Linux
  • Mozilla engine browser component cannot be added-removed-added into Swing container on Linux platform multiple times with JDK 1.6
0 Comments Permalink

We are glad to announce that OpenFaces 2.0 has "graduated" from the Early Access Program and the final version is released!

 

OpenFaces is an open source JSF library consisting of a set of advanced components, the Ajax framework and the client-side validation framework.

 

6 new components are introduced since the EAP 2 was published:

  • CompositeFilter – allows the user to build complex filter crieteria with multiple filter conditions;
  • LayeredPane – a container that allows switching between different sets of displayed components;
  • SelectOneRadio – an extended version of the standard <h:selectOneRadio> component;
  • SelectManyCheckbox – an extended version of the standard <h:selectManyCheckbox> component;
  • CommandButton – an extended version of the standard <h:commandButton> component;
  • CommandLink – an extended version of the standard <h:commandLink> component.

 

DataTable and TreeTable components have been significantly extended with the following functionality:

  • Content scrolling with frozen header/footer rows. Both vertical and horizontal scrolling with frozen columns is supported;
  • Interactive drag&drop column reordering;
  • Interactive column visibility customization;
  • Numerous filtering extensions -- customizing search condition, case sensitivity, placing filters inside or outside the table;
  • Tighter integration with the Hibernate library;
  • And more...

 

Certainly, there are many more extensions and fixes in other OpenFaces components and you can see the full list in the release notes.

 

Use your chance to see the components in action in the Live Demo!

 

We welcome everyone to contribute and participate in OpenFaces development. Please don't hesitate to post your feedback at the product forum or email us and follow OpenFaces on Twitter.

7 Comments Permalink

Below are the changes that were made since the last early access release, OpenFaces 2.0 EAP2. Please take a look at the What's New in OpenFaces 2.0 document if you'd like to see all changes since the last 1.x release.

New Components

  • CompositeFilter – allows the user to build complex filter crieteria with multiple filter conditions. Works as a standalone component or can be bound to DataTable/TreeTable components to filter their data.
  • LayeredPane – a container that allows switching between different sets of displayed components.
  • SelectOneRadio – an extended version of the standard <h:selectOneRadio> component, which provides additional styling options and makes it possible to customize radio buttons with images.
  • SelectManyCheckbox – an extended version of the standard <h:selectManyCheckbox> component, which provides additional styling options and makes it possible to customize radio buttons with images.
  • CommandButton – an extended version of the standard <h:commandButton> which includes the Ajax features and an ability to customize button's content with sub-components or HTML.
  • CommandLink – an extended version of the standard <h:commandLink> which includes the Ajax features.

Enhancements

  • Ajax settings:
    • It's now possible to customize Ajax progress message position with new horizontalAlignment/verticalAlignment attributes of <o:defaultProgressMessage> tag.
    • Ajax progress message can now be made semitransparent and shown with a smooth transparency transition (see <o:defaultProgressMessage> tag documentation).
    • Added an option to disable mouse interoperation by shading window contents while Ajax request is in progress (see <o:defaultProgressMessage> tag documentation).
    • It's now possible to customize the appearance of session expiration confirmation (see the <o:defaultSessionExpiration> tag documentation).
  • DayTable:
    • Added <o:daySwitcher> subsidiary component for <o:dayTable> that simplifies navigation between days and provides multiple customization options for representation of selected date.
  • DataTable/TreeTable:
    • Added support for content scrolling with header/footer row(s) freezing for DataTable and TreeTable components. Both vertical and horizontal scrolling with fixed columns is supported. See the Content Scrolling section in DataTable and TreeTable documentation for details.
    • Added support for interactive drag & drop column reordering. See the Drag & Drop Column Reordering section in DataTable and TreeTable documentation for details.
    • Added support for interactive column visibility customization. See the Displaying Column Menus section in DataTable and TreeTable documentation for details.
    • Numerous filtering enhancements, see the "DataTable/TreeTable Filtering Enhancements" section below.
    • Added support for specifying a popup menu for table columns, containing either the standard or customized set of actions. See the Displaying Column Menus section in DataTable and TreeTable documentation for details.
    • Added header and footer attributes to all column tags to serve as a convenient replacement for specifying the text in the "header" and "footer" facets.
    • Significantly simplified handling large data sets using Hibernate library. See the Using DataTable with the Hibernate Library section in DataTable documentation for details.
    • There's a new "subHeader" facet in the column tags for DataTable and TreeTable components that allows customizing the contents that appear in the table's header section under the column headers.
    • Added a new DataTable.getPageIndexForRowKey method for scenarios like detecting the page(s) for selected item(s).
    • Improved TreeTable configuration checking and error reporting.
    • DataTable is now automatically focused when the pagination buttons are used.
    • Resolved the known issue where editable and command components couldn't be used in the Ajax-enabled TreeTable.
  • Input components:
    • Added support for floating point numbers in <o:spinner> component along with customizing number format with <f:convertNumber> tag, which allows to set locale and number pattern using syntax rules defined by java.text.DecimalFormat class.
    • Added "auto-growing" feature to the <o:inputTextarea> component, which allows a TextArea to automatically adjust its height based on the amount of typed text. Assign true to theautoGrowing attribute to turn this functionality on.
    • Added autocomplete attribute to <o:inputText> component to match API of the standard <h:inputText> tag.
    • Added stateList attribute to <o:selectBooleanCheckbox> component, which allows to configure set and order of states of SelectBooleanCheckbox in tri-state mode.
  • FoldingPanel:
    • Added a new loading mode "ajaxAlways", which allows loading a fresh content on each expansion of FoldingPanel. Also note the API change: the "ajax" mode has been renamed to"ajaxLazy".
    • FoldingPanel's expansion state is now properly saved when placed inside of iteration components such as <o:dataTable> and <o:forEach>.
  • TabbedPane:
    • Added a new loading mode "ajaxAlways", which allows loading a fresh tab content on each tab switch. Also note the API change: the "ajax" mode has been renamed to "ajaxLazy".
  • PopupMenu:
    • Added built-in Ajax support to PopupMenu items with render and execute attributes.
    • Improved JavaScript performance for PopupMenu components.
    • PopupMenu is now automatically repositioned if necessary to fit visible window's area.
  • Other:
    • Added the caption attribute for <o:foldingPanel>, <o:window>, <o:sidePanel> and <o:subPanel> (former <o:tabbedPaneItem>) tags, which is a short replacement for the"caption" facet if you need to specify the caption as text.
    • Added built-in Ajax support to the <o:captionButton> tag with render and execute attributes.
    • Added built-in Ajax support to <o:singleRowSelection>, <o:multipleRowSelection>, <o:singleNodeSelection>, and <o:multipleNodeSelection> tags with render and execute attributes.
    • Improved JavaScript performance for DataTable/TreeTable components.
    • Added oncontextmenu event for all components.
    • All popups in components like DropDownField, SuggestionField, Calendar, DateChooser, PopupMenu can now be closed by pressing Esc key.
    • Added support for handling mouse events in <o:floatingIconMessage> tag.
    • Extended client-side API for PopupMenu, Window and PopupLayer components with methods isVisible(), getLeft(), and getTop().
    • Improved error checking when processing default validation message presentation parameters in web.xml.

       

      Ajax Framework Changes

      The Ajax Framework API has been significantly modified and extended to make it consistent with the JSF 2.0 API. Tags and attributes have been renamed in accordance with the new specification. Please refer to the "Migrating to the New Ajax API" sub-section in the Migrating from OpenFaces EAP2 document.

      New features have been added to the Ajax (former ReloadComponents) component:

      • It's possible to specify JavaScript code that should be executed on the client when an event defined by event attribute occurred (onevent attribute);
      • New attribute disabled now indicates whether or not the component should render client script on referred component.
      • Ajax component now automatically decides when to disable the default action of the attached component to avoid the conflict between Ajax action and the default action of the attached component (disableDefault attribute removed).

       

      DataTable/TreeTable Filtering Enhancements

      The filtering API for DataTable and TreeTable components has been significantly reviewed and enhanced. The previous filtering API consisted of filtering-related attributes in <o:column> tag. Although this was enough for a simple API, different kinds of filters require different sets of attributes and additional features require much more attributes, so filters are now organized as separate tags – one tag per one type of filter: <o:inputTextFilter>, <o:dropDownFieldFilter>, and <o:comboBoxFilter>. Each tag has a set of attributes applicable for that particular type of filter. It's quite easy to migrate to the new API though, see the "Migrating to the New Filtering API" sub-section in the Migrating from OpenFaces EAP2 document.

      Here are the new features that were implemented as part of the new API:

      • It's possible to customize whether search should be case sensitive or not.
      • It's now possible to customize the condition by which search has to be performed (contains, equals, less, greater, etc.).
      • It's now possible to specify style and all other component-specific attributes of filtering components.
      • There's now an option (turned on by default) that makes filtering to be performed on the fly as the user types in the filter field.
      • DropDownFieldFilter now suggests filter text as the user types it.
      • Filters can now be placed outside of their DataTable/TreeTable components.
      • The filtering expression can now be detected automatically when a filter resides in a table column.

      Please see the Filtering section in the DataTable and TreeTable documentation for the comprehensive details on featurs and usage of the filtering functionality.

       

      Resolved Issues

      • Ajax component (former ReloadComponents component):
        • Fixed the issue where <o:reloadComponents> (now <o:ajax>) inside <h:commandLink> might cause "...no message was rendered" js error.
        • Fixed input focus loss after Ajax requests.
        • Fixed some cases when <o:reloadComponents> (now <o:ajax>) couldn't find components by id.
        • Fixed <o:reloadComponents> inside <o:dataTable> and <o:forEach>
      • DataTable/TreeTable:
        • Fixed DataTable/TreeTable column resizing issues in IE strict mode and Opera.
        • Fixed improper table column resizing behavior under Chrome and Safari in some configurations.
        • Fixed a known issue of non-working column resizing on tables with common header under Safari.
        • Fixed drop-down table filter size under Chrome and Safari.
        • Fixed filter fields width issue in IE strict mode.
        • Fixed contracting tree indents when resizing columns in TreeTable.
        • Supported rgb-syntax when specifying table gridline styles, e.g. "1px solid rgb(192, 217, 239)" instead of "1px solid #C0D9EF".
      • PopupMenu:
        • Fixed minor sub-menus misalignment in PopupMenu component.
        • Fixed excesssive PopupMenu's focus reacquiring after it is hidden.
        • Fixed unwanted page scrolling when the mouse enters a PopupMenu.
        • Fixed an issue of input fields protruding over PopupMenu in IE6.
        • Fixed an issue where PopupMenu was too wide under IE quirks mode.
        • Fixed unwanted sub-menu blinking when clicking an item while the sub-menu showing delay is in progress.
        • Fixed automatic attaching PopupMenu to TabbedPane and FoldingPanel.
      • Other components:
        • Fixed typing "&" and "(" symbols in DropDownField and SuggestionField components.
        • Fixed clipping popups of drop-down components (DropDownField/SuggestionField/DateChooser) with parent elements having a hidden overflow in IE+quirks.
        • Fixed misplaced Calendar days near DST transition in Southern American time zones.
        • Fixed NPE when changing the rendered attribute of a TabbedPane in an action.
        • Fixed showing/hiding of <o:window> and <o:popupLayer> using binding to visibility attribute.
        • DropDownField and DateChooser components now ensure that the drop-down will be opened in the visible window's area.
        • Fixed using <o:ajax> (former <o:reloadComponents>) inside of <o:menuItem> tags.
        • Fixed "cursor transparency" over DropDownField/DateChooser components placed into an absolutely positioned container in IE8.
        • Fixed non-working size attribute for <o:twoListSelection> tag.
        • Fixed TabbedPane stealing focus from some of the embedded focusable components (such as DataTable, Calendar, etc).
        • Fixed Spinner buttons appearance in IE.
        • Fixed rollover styles for the Spinner component.
      • Miscellaneous:
        • Fixed not applying styles for some components in IE with "Invalid Argument" JavaScript error on pages with lots of OpenFaces components.
        • Fixed duplicating server-generated content of <h:messages> when opening DateChooser.
        • Fixed compatibility with RichFaces in Facelets environment
        • Fixed security issue where reading files from server's current directory was possible.
        • Fixed JavaScript error when changing the set of validated components with Ajax.
        • Fixed misplaced/disappearing <o:floatingIconMessage> images when Ajax-reloading validated fields in a multi-form page.
        • Fixed compatibility issues between OpenFaces and RichFaces session expiration handling functionality during ajax requests.
        • Fixed excessive "enclosing form cannot be found" log messages when using <rich:modalPanel> component.
        • Fixed issues with state saving during ajax requests under MyFaces 1.2.
        • Fixed getCount() function in iteration status of ForEach component to return a 1-based value instead of 0-based one.
        • Fixed isLast() function in iteration status of ForEach component.

      Other

      • DataTable/TreeTable filter fields' text is now not marked with selection for convenient typing after filtering.
      • The default values for the Spinner's minValue and maxValue attributes are now unspecified by default making it possible to enter a number without range restrictions by default.
      • Rollover button style for DateChooser and DropDownField is now applied when mouse is over the button itself rather than over the field.
      • Improved the default look for the PopupMenu component.
      • Completed documentation for all components.

       

      Migration Instructions

      Please see the Migrating from OpenFaces EAP2 document for the migration instructions. If you're migrating from version 1.x of the QuipuKit library, see the Migrating from QuipuKit 1.6.2 document.

      0 Comments Permalink

      First, we would like to announce the new OpenFaces_JSF Twitter channel where you can track the development of OpenFaces, receive news, tips, and other notable information about OpenFaces. You're welcome to follow OpenFaces on Twitter!

       

      Also, a couple of words on the upcoming final version of OpenFaces 2.0. The pre-release period of OpenFaces development comes to an end and the date for the final release is now set to Mar, 4, next week. The upcoming version contains 6 new components, significant DataTable and TreeTable improvements, a lot of extensions for other components, the revised and polished API, comprehensive documentation and of course a lot of fixes.

      0 Comments Permalink

      JxBrowser, a cross-platform library that allows integrating web browser into Java AWT/Swing applications on Windows, Linux and Mac OS X platforms, has been updated to version 2.1.

       

      In this version we introduce the following improvements:

      • Ability to programmatically set path to Mozilla profile directory;
      • MIME type handling functionality for Mozilla engine.

       

      Also this version contains fixes for the issues reported by our customers:

      • JavaScript Error Listener operability issue is resolved (Mozilla engine);
      • The work of StatusListener is corrected (WebKit engine);
      • Navigation finished event is fired when navigation made within the same document (Mozilla engine);
      • Pop-up window now can be opened even if its target name is empty (IE engine).

       

      For the full list of resolved issues and improvements, please see the JxBrowser 2.1 Release Notes page.

       

      The update is already available for download. You can try the new version online using the WebStart Demo.

       

      For any help or feedback related to JxBrowser, please use the support forum or e-mail us directly.

      0 Comments Permalink

      Improvements:

      • Added ability programmatically set path to Mozilla profile directory
      • Added MIME type handling functionality into Mozilla engine
      • Added possibility to run samples using the "java -jar samples.jar <sample name>" command or by samples.bat, samples.sh files.

       

      Resolved Issues:

      • Javascript alert causes Java application to hang under JDK 1.6.0_07 with Internet Explorer engine
      • JavaScript Error Listener doesn't work in Mozilla engine
      • StatusListener doesn't work in Safari (WebKit) engine
      • Navigation finished callback is never invoked when navigation goes to a page by local link (anchor) in Mozilla engine
      • Pop-up window cannot be opened in Internet Explorer engine when pop-up window target name is empty
      • Mozilla engine cannot be started on clear Windows platform

       

      Known Limitations:

      • Apple Safari (WebKit) engine does not provide DOM access yet (will be added in JxBrowser 2.2 planned for March 2010)
      • IE engine doesn't support MIME type handling functionality (to be added in JxBrowser 2.2 planned for March 2010)
      • Mozilla engine browser component cannot be added-removed-added into Swing container on Linux platform multiple times
      0 Comments Permalink

      JExplorer, a library that provides a convenient Java API for integrating Microsoft Internet Explorer into Java applications, has been updated to version 2.3.

       

      This release introduces the following features and improvements:

      • interface for receiving notifications when popup menu is required;
      • event handler for receiving information about popup window before it is opened;
      • listener for receiving events when WebBrowser is disposed.

       

      This version also resolves several important issues reported by our customers. For the full list of resolved issues and improvements, please read the JExplorer 2.3 Release Notes page.

       

      The latest version is available for download at JExplorer page. For any help or feedback related to the use of our product, please use the support forum or e-mail us us directly.

      0 Comments Permalink

      New Features:

      • Added support of ContextMenuProviderExt interface that allows receiving notifications when popup menu is required;
      • Added NewWindowEventHandlerExt2 that allows receiving information (url, target name, features) about popup window before it is opened;
      • Added DisposeListener for receiving events when WebBrowser is disposed.

       

      Improvements:

       

      Resolved Issues:

      • 'Call is rejected by Callee' error on print or preview of a page;
      • 'Call is rejected by Callee' error on launching Find (Ctrl+F);
      • WebBrowser.setContent() method fails when PDF document is already loaded;
      • Document returns wrong maximum scroll values after setting "zoom" property;
      • Cannot open Gmail and Google Reader applications in JExplorer;
      • Several HTMLDialog can't be opened in sequence;
      • java.awt.Robot prevents closing WebBrowser instance;
      • Page content isn't resized correctly;
      • The BrowserWindowListener.onWindowResize event doesn't get fired when browser is resized from JavaScript;
      • JVM doesn't exit when the DefaultCloseOperation for JFrame is set to DISPOSE_ON_CLOSE;
      • HttpSecurityHandler doesn't work on Internet Explorer 6;
      • Handling AuthenticationHandler.onAuthenticate() on Vista generates access-violation error;
      • Browser.getScreenShot() returns cropped image;
      • Browser component steals focus when web page is loaded or refreshed;
      • Browser.getCookies and Browser.setCookies methods don't work with session cookies;
      • Java crashes on Browser.close().
      0 Comments Permalink

      JNIWrapper, a library that enables access to native libraries and components from Java code without using JNI, has been updated to version 3.8.1.

       

      In this version we added support of Mac OS X 10.6 and synchronous mode of Hooks for Windows. This release also includes the updated version of WinPack, free add-on enabling access to the Windows native API and libraries from Java code. WinPack 3.8.1 introduces low level keyboard and mouse hooks that allow working with 32-bit applications on 64-bit Windows systems. For the full scope of changes please check out the JNIWrapper 3.8.1 Release Notes.

       

      As always, you can download and try the fully-functional version of JNIWrapper.

       

      We look forward to your feedback on this update. If you need assistance with using our product, please use the support forum.

       

      0 Comments Permalink

      New Features and Improvements:

      • Added support of Mac OS X 10.6 Snow Leopard platform;
      • Added implementations of low level keyboard (Hook.KEYBOARD_LL) and mouse (Hook.MOUSE_LL) hooks. These new hooks can be used on 64-bit Windows systems instead of KEYBOARD and MOUSE hooks in order to solve deadlock issues. (WinPack);
      • Added support of synchronous / asynchronous modes for Hooks in 32-bit and 64-bit JNIWrapper libraries (JNIWrapper and WinPack).
      0 Comments Permalink

      TeamDev is happy to announce official release of JxBrowser 2.0, a cross-platform library that allows integrating web browser into Java AWT/Swing applications on Windows, Linux and Mac OS X platforms.

       

      In this version we have added support of Apple Safari (WebKit) engine on Mac OS X platform and Internet Explorer on Windows. With JxBrowser 2.x, you have a choice - which browser engine your Java application should use on different operating systems. Now you can use the default system browser instead of Mozilla Gecko engine on Mac OS X and Windows platforms.

       

      You can get access to the powerful browser engines functionality through the new JxBrowser 2.x API. Samples in distribution package will demonstrate how you can navigate to a web page and wait until the page is loaded; take a full web page screen shot and save it to image file; get access to browser events, DOM, browser features and more.

       

      Download the JxBrowser 2.0 build and try the included demo application and samples.

       

      For any help or feedback related to the use of our product, please use the support forum or e-mail us directly.

      0 Comments Permalink

      New Features:

      • Unified API for multiple browser engine support
      • Added Internet Explorer engine support for Windows platforms
      • Added Apple Safari (WebKit) engine support for Mac OS X platforms
      • Added the Browser.waitReady() method that allows blocking the current thread execution until web page is loaded completely
      • Added "Cancel navigation" functionality

       

      Improvements:

      • Added Mozilla XULRunner background deployment functionality
      • Added Mac OS X 10.6 support

       

      Known Limitations:

      • Apple Safari (WebKit) engine does not provide DOM access yet (will be added in JxBrowser 2.2 planned for February 2010)
      • Apple Safari (WebKit) engine does not receive JavaScript error notifications (to be added in JxBrowser 2.2)
      • Mozilla engine doesn't support MIME type handling functionality yet (to be added in JxBrowser 2.1 planned for January 2010)
      0 Comments Permalink

      JxBrowser, the cross-platform library for embedding Mozilla browser into your Java application, has been updated to version 1.4.

       

      JxBrowser 1.4 introduces the following features and improvements:

      • API for interaction with native Mozilla XPCOM
      • API for clearing browser cache
      • Pop-up blocker
      • Ability to use custom implementation for displaying alerts, confirmations, prompts and authentication dialogs
      • New function WebBrowser.findNext for searching through the document with defined parameters.

       

      This new version also resolves several important issues reported by our customers. For the full list of resolved issues and improvements, please read the JxBrowser 1.4 Release Notes page.

       

      The update is already available for download. You can try the new version online using the WebStart Demo.

       

      For any help or feedback related to the use of our product, please use the support forum or e-mail us directly.

      0 Comments Permalink
      1 2 3 ... 10 Previous Next