Lobo is an open source web browser completely written in Java. It is undergoing active development with the aim to fully support HTML 4, Javascript and CSS2. Lobo has a browser API and a plugin infrastructure.
The general goal of the Lobo browser effort is to produce a browser that is fast, complete, easy to extend, feature-rich and secure.
Here are some key features of "Lobo":
· Security- In principle, a Java program is less suceptible to certain types of vulnerabilities such as a buffer overflow attack. Java's security model can also allow web content to have access to a complex set of APIs, except in a controlled sandbox.
· Expandability- A Java-based application can be implemented to be expandable via powerful cross-platform plugins. Consider the difference this has made for Java applications such as jEdit and Eclipse. (Lobo already has a plugin API).
· New paradigms- With the help of Java we can implement new powerful cross-platform and secure mechanisms to represent web content. We would like to make it easy to integrate arbitrary UI languages into Lobo (e.g. the many XML UI languages that exist). We would also like to support JavaFX by default as a first-class citizen. But we also plan to allow, for example, representation of web content purely as Java source code.
· Portability- This is the obvious advantage of a pure Java application.
· Current Status
Requirements:
· JRE 1.5+
What's New in This Release: [ read full changelog ]
· Renamed NavigatorListener to NavigatorErrorListener.
· Updated JavaFX support so it's 1.0 compliant.
· Added methods getContentObject() and getCurrentMimeType() to FramePanel and BrowserPanel. getContentObject() should return HTMLDocumentImpl instances if HTML is showing.
· Added navigation listener, content listener and response listener capabilities to FramePanel and BrowserPanel. Navigation events have a linkObject property that should be of type HTMLElement for HTML clicks.
· Added navigation listeners to extensions.
· Added connection pre- and post-processors to extensions.
· Added a FramePanelFactory capability.
· The factory that the browser uses to create FramePanel instances (e.g. for IFRAMEs) can be set with FramePanelFactorySource.
· Fixed a security issue that prevented some windows from being opened programmatically.
· Implemented status URLs on link hover.
· Added insertProvider and removeProvider permissions to security policy for local code.
· Fi...
Find us on Google+
