Difference between revisions of "OpenOffice NetBeans Integration/To-Dos"
(→Redesign of UNO project ANT targets) |
|||
| Line 3: | Line 3: | ||
== Redesign of UNO project ANT targets == | == Redesign of UNO project ANT targets == | ||
The UNO ANT targets use default targets of NetBeans to build and jar all project types. This should change to a process that is more aligned to the NetBeans behaviour that leaves overwriting of these targets to the end user. | The UNO ANT targets use default targets of NetBeans to build and jar all project types. This should change to a process that is more aligned to the NetBeans behaviour that leaves overwriting of these targets to the end user. | ||
| + | == Validation of Project Settings == | ||
| + | When a project is opened, the settings for the office and SDK have to be validated. If the project settings are invalid, the user has to be asked if the global settings have to be copied. | ||
| + | |||
== Debug support for component == | == Debug support for component == | ||
It should be possible to debug UNO components directly from NetBeans. That means local office user directory and locally started office with the appropriate debug environment enabled. Comparable to the plugin development in NetBeans and the option to install a new plugin in the target platform. | It should be possible to debug UNO components directly from NetBeans. That means local office user directory and locally started office with the appropriate debug environment enabled. Comparable to the plugin development in NetBeans and the option to install a new plugin in the target platform. | ||
Revision as of 14:23, 5 January 2007
Overview of task which have to be done to enhance the current plugin
Contents
Redesign of UNO project ANT targets
The UNO ANT targets use default targets of NetBeans to build and jar all project types. This should change to a process that is more aligned to the NetBeans behaviour that leaves overwriting of these targets to the end user.
Validation of Project Settings
When a project is opened, the settings for the office and SDK have to be validated. If the project settings are invalid, the user has to be asked if the global settings have to be copied.
Debug support for component
It should be possible to debug UNO components directly from NetBeans. That means local office user directory and locally started office with the appropriate debug environment enabled. Comparable to the plugin development in NetBeans and the option to install a new plugin in the target platform.
C++ support
With the inclusion of C++ as supported programming language in NetBeans, the plugin should also support the creation of all project types in C++.
Scripting support
General support of scripting (Java, Javascript, ...). It should be possbile to create, deploy and debug scripts from within NetBeans into the office or into open documents.
Minor Tasks
Initialization of counter variables
When the AddOn wizard is used for a second time, the count for new commands is not resetted.
Button caption with bitmaps
To improve the usability it would be nice to have arrow images or something similar on the move buttons (menu position, toolbar position, ...)
Default package
All projects should support the same default package or at least the same beginning org.openoffice....
