WebRenderer is one of those SDKs that can appear overwhelming on first look.
For this reason we always shipped a “bare bones” Test Browser
(TestBrowser.java) with the product. The Test Browser has at times baffled
people due to it’s lack of features. The Test Browser was
“featureless” by design as we wanted to keep the starter example code as
compact as possible so that developers could embed WebRenderer in just a few
lines of code. This is important as we never wanted the learning curve and
integration to be an overwhelming process.
With that being said, for some time now our WebRenderer developer team has
been utilizing a “Test Browser” that is rather substantial (130 classes)
when compared to our standard Test Browser (one class). This test browser has
been dubbed “Rich Test Browser” by the developer team. Given the amount
of WebRenderer features demonstrated by... (more)
One of the most popular sets of search terms we see in our website statistics
relate to enabling Flash in WebRenderer. When we designed WebRenderer, we
built it knowing that Flash was still being used and demanded by a lot of
users, so we made sure that you could enable it within WebRenderer.
Importantly, we made it easy for you to activate.
On most platforms Flash should work with WebRenderer Swing Edition if Flash
has been set up to run in Firefox, as WebRenderer Swing Edition uses the
plugin finder from the Mozilla engine to detect the Flash plugin. If Firefox
is not setup wi... (more)
From time to time WebRenderer is deployed within an Applet. Applets provide a
convenient mechanism for launching client applications within the browser.
WebRenderer however requires different libraries based on the target platform
(Windows, Linux, OS X, Solaris) and architecture (32/64 bit). Traditionally
to run an Applet, you needed to specify all of the libraries that are
required, and they will all be downloaded. If you intend for the Applet to
run on multiple platforms, then traditional Applet deployment means that all
the libraries for the supported platforms are required w... (more)
Mouse gestures are one of those great "add-ons" that enhance browser
usability. For those that are not familiar with mouse gestures, they are a
browser navigational aid that works via mouse movements. Mouse gestures have
been around for some time now and we thought it would be good to show how to
implement mouse gestures in WebRenderer.
This demonstration application not only aids in browser navigation, but also
shows how to draw on top of the WebRenderer browser. To enact a mouse gesture
one holds down the right mouse button and moves the mouse in a direction or
pattern and the... (more)
We are often asked how our clients use WebRenderer in their projects. There
are thousands of different use cases our ingenious clients have come up with
that have both delighted and surprised us. WebRenderer is more than just an
embeddable Java Swing browser. WebRenderer also gives you, the developer,
complete access and control of the browser.
We thought we would put together an example that demonstrates some of the
in-browser functionality. In this example we use WebRenderer Swing Edition to
create a special “Zoom” effect when a click action is selected, like so:
The Zoom Brow... (more)