|
|
|
|
|
|
The module can be used to plan a project and monitor it's status or to maintain a checklist.
Question (arch-overall): Describe the overall architecture. Answer:This module provides a table list where you can enter your tasks and their subtasks, sort them, etc.
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? Answer:The module is currently (Jan. 2006) available as beta. If no significant bugs or architecture flaws will be found it will be available in 3 months on the stable AUC.
Question (arch-quality): How will the quality of your code be tested and how are future regressions going to be prevented? Answer:There are (although not so many) unit and functional tests that could be run automatically.
Question (arch-where): Where one can find sources for your module? Answer:
The sources for the module are in NetBeans CVS in tasklist/usertasks directory.
These modules are required in project.xml file:
Should run on any platform with a Java implementation.
Question (dep-jre): Which version of JRE do you need (1.2, 1.3, 1.4, etc.)? Answer:1.4
Question (dep-jrejdk): Do you require the JDK or is the JRE enough? Answer:JRE is enough
yes
Question (deploy-shared): Do you need to be installed in the shared location only, or in the user directory only, or can your module be installed anywhere? Answer:The module can be installed anywhere.
Question (deploy-packages): Are packages of your module made inaccessible by not declaring them public? Answer:Yes. There are no public packages.
Question (deploy-dependencies): What do other modules need to do to declare a dependency on this one? Answer:All texts are properly internationalized. The code cannot deal with calendars other than gregorian.
Question (compat-standards): Does the module implement or define any standards? Is the implementation exact or does it deviate somehow? Answer:RFC-2445 - is used to store calendar files. RFC-2445 uses CR+LF as it's end-of-line marker on any platform including Linux. The code in User Tasks uses platform dependant end-of-line markers instead. It allows adding an .ics file as text to a CVS repository. Exporting as iCal 2.0 uses CR+LF as end-of-line marker on any platform. Default task list (opened through "Window"/"User Tasks") resides in {userdir}{/}tasklist.ics (this can be changed in the options dialog). Opened .ics files will be automatically saved if they are changed.
Question (compat-version): Can your module coexist with earlier and future versions of itself? Can you correctly read all old settings? Will future versions be able to read your current settings? Can you read or politely ignore settings stored by a future version? Answer:The module maintains backward compatibility for serialized top components. Usage of org.openide.options.SystemOption for storing setting means compatibility with earlier and future versions of the module. Unknown or unsupported components and properties from RFC-2445 will not be discarded during saving. It means that the compatibility with other RFC-2445 implementations and earlier and future versions of this module is maintained.
java.io.File
directly?
Answer:
Yes.
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: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:
No.
Question (lookup-remove): Do you remove entries of other modules from lookup? Answer:No.
System.getProperty
) property?
Answer:
No.
Question (exec-ant-tasks): Do you define or register any ant tasks that other can use? Answer:No.
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:Yes. JavaHelpIntegrationAPI - org.netbeans.api.javahelp.Help.showHelp is called through reflection API.
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. HtmlBrowser.URLDisplayer.getDefault().showURL is used to start a web browser.
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? Answer:Nothing special here.
Question (security-policy): Does your functionality require modifications to the standard policy file? Answer:No.
Question (security-grant): Does your code grant additional rights to some other code? Answer:No.
Default behavior for nodes.
Question (format-clipboard): Which data flavors (if any) does your code read from or insert to the clipboard (by access to clipboard on means calling methods onjava.awt.datatransfer.Transferable
?
Answer:
No.
Question (perf-exit): Does your module run any code on exit? Answer:Top component settings and module settings are serialized on exit.
Question (perf-scale): Which external criteria influence the performance of your program (size of file in editor, number of files in menu, in source directory, etc.) and how well your code scales? Answer:Size of .ics files only influence the time to load/save the data.
Question (perf-limit): Are there any hard-coded or practical limits in the number or size of elements your code can handle? Answer:No.
Question (perf-mem): How much memory does your component consume? Estimate with a relation to the number of windows, etc. Answer:XXX no answer for perf-mem
Question (perf-wakeup): Does any piece of your code wake up periodically and do something even when the system is otherwise idle (no user interaction)? Answer:Yes. "Spent Time" property is updated periodically (every 15 seconds).
Question (perf-progress): Does your module execute any long-running tasks? Answer:No.
Question (perf-huge_dialogs): Does your module contain any dialogs or wizards with a large number of GUI controls such as combo boxes, lists, trees, or text areas? Answer:"New Task" dialog.
Question (perf-menus): Does your module use dynamically updated context menus, or context-sensitive actions with complicated and slow enablement logic? Answer:No.
Question (perf-spi): How the performance of the plugged in code will be enforced? Answer:Not related.