🚀 go-pugleaf

"Art Pollard" <pollarda@lextek.com> writes:

> Are there any other restrictions I ought to know about?

Use of some classes (like java.awt.Robot) are restricted.

> 
> Also, would there be a significant development time difference developing an
> application so that it can be run as an applet and as an application v.s. as
> an application only?

No; an applet is basically a normal container, except with a couple of
differences when running inside a browser. These are related to two
things:

1) The applet lifecycle (init(), start(), stop(), destroy()). Proper
   handling may require the "run as application" main() to call at
   least init() and start().

2) The AppletContext, which may need to be replaced by an AppletStub
   and related AppletContext implementations.

You can differentiate between the "run modes" by setting a flag in
main().

> Do you think there would be much market for this within the Java
> community?

Possibly; but make it easy to write plugins (like JBuilder and Eclipse
do).

I seem to recall that Corel tried to make a Java-based office suite
once, but it failed; possibly it was ahead of its time, Java's AWT and
Swing have improved in efficiency and speed since then.