Re: [api-dev] OpenOffice.org Extensions - was Format for information file about templates and addons
Paolo Mantovani wrote: Alle 09:35, lunedì 7 marzo 2005, Jürgen Schmidt ha scritto: Ian Laurenson wrote: On Fri, 2005-03-04 at 21:58, Jürgen Schmidt wrote: Ian Laurenson wrote: On Thu, 2005-03-03 at 21:49, Jürgen Schmidt wrote: [snip] Sure, the new SDK provides makefiles for creating UNO packages (both component packages and script/library packages). I also have the first running ant scripts and ideally would be an integrated wizard in NetBeans and/or Eclipse. [snip] While it would be good to be able create UNO packages from external IDEs, to me it would be even better if it were possible within OpenOffice.org. I assume you mean that it would be nice to export Basic libraries as UNO packages, right? Not just Basic libraries, my wish list includes: any graphics that are being used, the associated help files, Python components, the xcu file. mmh, i am not sure. I think this would maybe overload the functionality and it is probably used by less than 0,1% of all users. Whereas the function to simply install an extension is definitely helpful for users to extend their office installation. IMHO this used by less than 0,1% it's due to the fact that currently it's very difficult to deploy graphics or other resources whithin uno packages. This operation infact, requires to write a custom configuration schema (xcs file) plus an xcu file in order to extend the OOo registry. Furthermore you must write some not silly code to extract informations from your custom registry entries and finally for loading the graphics on the proper controls. I would say that this is more a problem of missing documentation and examples. Private graphics for example can be accessed within the package as far as i know (i will check it and i will come back with the info). Own configuration schemes are only necessary if you have really configurable data in your component. I'm sure that there are many peoples that would add some graphics to embellish their dialogs, much more than 0.1% of starbasic users. Most probably they would like to deploy their work as uno package, but it's simply too difficult for almost all of them. I agree for the Basic users, because they use the office as IDE for their macros and dialogs. For all other languages (e.g. Java , C++) i would prefer some kind of integration (e.g. wizards) in popular IDE's like Eclipse or Netbeans for Java. - Juergen ciao Paolo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [api-dev] OpenOffice.org Extensions - was Format for information file about templates and addons
Hi Ian, I am not a friend of licenses and I am not good at policies and stuff, but I think that the Programmer's Guide cannot be edited by you, because it is published under the Sun Microsystems flag. That means that you probably need to make an agreement with Sun first. Am I correct with this, Hamburg?? -- Best Regards Christian Junker On Mon, 07 Mar 2005 11:44:43 +1300, Ian Laurenson [EMAIL PROTECTED] wrote: On Fri, 2005-03-04 at 21:58, Jürgen Schmidt wrote: Ian Laurenson wrote: On Thu, 2005-03-03 at 21:49, Jürgen Schmidt wrote: [snip] Sure, the new SDK provides makefiles for creating UNO packages (both component packages and script/library packages). I also have the first running ant scripts and ideally would be an integrated wizard in NetBeans and/or Eclipse. [snip] While it would be good to be able create UNO packages from external IDEs, to me it would be even better if it were possible within OpenOffice.org. I assume you mean that it would be nice to export Basic libraries as UNO packages, right? Not just Basic libraries, my wish list includes: any graphics that are being used, the associated help files, Python components, the xcu file. [remainder snipped] Thanks, Ian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [api-dev] OpenOffice.org Extensions - was Format for information file about templates and addons
Ian Laurenson wrote: On Fri, 2005-03-04 at 21:58, Jürgen Schmidt wrote: Ian Laurenson wrote: On Thu, 2005-03-03 at 21:49, Jürgen Schmidt wrote: [snip] Sure, the new SDK provides makefiles for creating UNO packages (both component packages and script/library packages). I also have the first running ant scripts and ideally would be an integrated wizard in NetBeans and/or Eclipse. [snip] While it would be good to be able create UNO packages from external IDEs, to me it would be even better if it were possible within OpenOffice.org. I assume you mean that it would be nice to export Basic libraries as UNO packages, right? Not just Basic libraries, my wish list includes: any graphics that are being used, the associated help files, Python components, the xcu file. mmh, i am not sure. I think this would maybe overload the functionality and it is probably used by less than 0,1% of all users. Whereas the function to simply install an extension is definitely helpful for users to extend their office installation. - Juergen [remainder snipped] Thanks, Ian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [api-dev] OpenOffice.org Extensions - was Format for information file about templates and addons
Alle 09:35, lunedì 7 marzo 2005, Jürgen Schmidt ha scritto: Ian Laurenson wrote: On Fri, 2005-03-04 at 21:58, Jürgen Schmidt wrote: Ian Laurenson wrote: On Thu, 2005-03-03 at 21:49, Jürgen Schmidt wrote: [snip] Sure, the new SDK provides makefiles for creating UNO packages (both component packages and script/library packages). I also have the first running ant scripts and ideally would be an integrated wizard in NetBeans and/or Eclipse. [snip] While it would be good to be able create UNO packages from external IDEs, to me it would be even better if it were possible within OpenOffice.org. I assume you mean that it would be nice to export Basic libraries as UNO packages, right? Not just Basic libraries, my wish list includes: any graphics that are being used, the associated help files, Python components, the xcu file. mmh, i am not sure. I think this would maybe overload the functionality and it is probably used by less than 0,1% of all users. Whereas the function to simply install an extension is definitely helpful for users to extend their office installation. IMHO this used by less than 0,1% it's due to the fact that currently it's very difficult to deploy graphics or other resources whithin uno packages. This operation infact, requires to write a custom configuration schema (xcs file) plus an xcu file in order to extend the OOo registry. Furthermore you must write some not silly code to extract informations from your custom registry entries and finally for loading the graphics on the proper controls. I'm sure that there are many peoples that would add some graphics to embellish their dialogs, much more than 0.1% of starbasic users. Most probably they would like to deploy their work as uno package, but it's simply too difficult for almost all of them. ciao Paolo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [api-dev] OpenOffice.org Extensions - was Format for information file about templates and addons
On Fri, 2005-03-04 at 21:58, Jürgen Schmidt wrote: Ian Laurenson wrote: On Thu, 2005-03-03 at 21:49, Jürgen Schmidt wrote: [snip] Sure, the new SDK provides makefiles for creating UNO packages (both component packages and script/library packages). I also have the first running ant scripts and ideally would be an integrated wizard in NetBeans and/or Eclipse. [snip] While it would be good to be able create UNO packages from external IDEs, to me it would be even better if it were possible within OpenOffice.org. I assume you mean that it would be nice to export Basic libraries as UNO packages, right? Not just Basic libraries, my wish list includes: any graphics that are being used, the associated help files, Python components, the xcu file. [remainder snipped] Thanks, Ian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [api-dev] OpenOffice.org Extensions - was Format for information file about templates and addons
How about updating the StarOffice 7 Programmer's Guide. I think this is the no.1 tutorial on Starbasic/OpenOffice Basic and could get an update, I think. By update I mean not just possible corrections but also extending the guide with a few more examples. Best Regards Christian Junker Jürgen Schmidt wrote: Hi Ian, Ian Laurenson wrote: On Thu, 2005-03-03 at 21:49, Jürgen Schmidt wrote: [snip] Sure, the new SDK provides makefiles for creating UNO packages (both component packages and script/library packages). I also have the first running ant scripts and ideally would be an integrated wizard in NetBeans and/or Eclipse. So if there are any volunteers who are familiar with one of the IDE'S and who are willing to investigate some time in this please let me know. I have a lot of ideas but didn't find the time until now. While it would be good to be able create UNO packages from external IDEs, to me it would be even better if it were possible within OpenOffice.org. I assume you mean that it would be nice to export Basic libraries as UNO packages, right? [snip] Where can I find the updated Developers Guide for OOo2.0? It can be found in the Beta SDK and will be published soon on api.openoffice.org Just checking that my understanding is correct: At the moment the updated Developers Guide for OOo2.0 is in the Beta SDK, which is not yet publicly available? I think it will be available this week. I am keen to help with the updated Developers Guide for OOo2.0 - is there anything that I can do now? No, not for this version, but you are welcome to review the guide and feedback is always welcome. As we all know the Devguide is probably more for core developers. I would like start the work on some shorter tutorials, for example 5 pager for add-ons in Java and one for C++. I think we need more documentation concentrating on certain aspects. Thanks Juergen [Remainder snipped] Thanks, Ian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [api-dev] OpenOffice.org Extensions - was Format for information file about templates and addons
On Thu, 2005-03-03 at 21:49, Jürgen Schmidt wrote: [snip] Sure, the new SDK provides makefiles for creating UNO packages (both component packages and script/library packages). I also have the first running ant scripts and ideally would be an integrated wizard in NetBeans and/or Eclipse. So if there are any volunteers who are familiar with one of the IDE'S and who are willing to investigate some time in this please let me know. I have a lot of ideas but didn't find the time until now. While it would be good to be able create UNO packages from external IDEs, to me it would be even better if it were possible within OpenOffice.org. [snip] Where can I find the updated Developers Guide for OOo2.0? It can be found in the Beta SDK and will be published soon on api.openoffice.org Just checking that my understanding is correct: At the moment the updated Developers Guide for OOo2.0 is in the Beta SDK, which is not yet publicly available? I am keen to help with the updated Developers Guide for OOo2.0 - is there anything that I can do now? [Remainder snipped] Thanks, Ian - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
