|
InputOutput
and related interfaces used in
driving the Output Window. The normal implementation is core-output.jar.
InputOutputAPI
Question (arch-overall):
Describe the overall architecture.
WARNING: Question with id="arch-overall" has not been answered!
Question (arch-usecases):
Describe the main
use cases of the new API. Who will use it under
what circumstances? What kind of code would typically need to be written
to use the module?
WARNING: Question with id="arch-usecases" has not been answered!
Question (arch-time):
What are the time estimates of the work?
WARNING: Question with id="arch-time" has not been answered!
Question (arch-quality):
How will the quality
of your code be tested and
how are future regressions going to be prevented?
WARNING: Question with id="arch-quality" has not been answered!java.io.File
directly?
Answer:
It is possible to redirect output from the Output Window to a file in the
user directory. Using FileObject
would be inconvenient in
many cases and probably too inefficient for massive output dumps.
Question (resources-layer):
Does your module provide own layer? Does it create any files or
folders in it? What it is trying to communicate by that and with which
components?
Answer:
Nothing special, just menu items etc.
Question (resources-read):
Does your module read any resources from layers? For what purpose?
Answer:
No
Question (resources-mask):
Does your module mask/hide/override any resources provided by other modules in
their layers?
Answer:
No
org.openide.util.Lookup
or any similar technology to find any components to communicate with? Which ones?
Answer:
IOProvider.getDefault()
asks lookup for the first instance
of itself. This is normally provided by core-output.jar
.
Question (lookup-register):
Do you register anything into lookup for other code to find?
Answer:
No
Question (lookup-remove):
Do you remove entries of other modules from lookup?
Answer:
No
System.getProperty
) property?
Answer:
No
Question (exec-component):
Is execution of your code influenced by any (string) property
of any of your components?
Answer:
No
Question (exec-ant-tasks):
Do you define or register any ant tasks that other can use?
WARNING: Question with id="exec-ant-tasks" has not been answered!
Question (exec-classloader):
Does your code create its own class loader(s)?
Answer:
No
Question (exec-reflection):
Does your code use Java Reflection to execute other code?
Answer:
No
Question (exec-privateaccess):
Are you aware of any other parts of the system calling some of
your methods by reflection?
Answer:
No
Question (exec-process):
Do you execute an external process from your module? How do you ensure
that the result is the same on different platforms? Do you parse output?
Do you depend on result code?
Answer:
No.
Question (exec-introspection):
Does your module use any kind of runtime type information (instanceof
,
work with java.lang.Class
, etc.)?
Answer:
No.
Question (exec-threading):
What threading models, if any, does your module adhere to?
WARNING: Question with id="exec-threading" has not been answered!
Question (security-policy):
Does your functionality require modifications to the standard policy file?
WARNING: Question with id="security-policy" has not been answered!
Question (security-grant):
Does your code grant additional rights to some other code?
WARNING: Question with id="security-grant" has not been answered!java.awt.datatransfer.Transferable
?
Answer:
Plain Unicode text only.
Built on May 4 2005. | Portions Copyright 1997-2005 Sun Microsystems, Inc. All rights reserved.