[dev] Ideas on mapping UNO IDL to Java 5
I am a beginner of OpenOffice and I am learning the SDK document now. Instead, i found the mapping from IDL to java looks missing something: 1. the mapped Java classes contains less information than the IDL, By using the Java 5 annotations will solve this problem, and we can even write no IDL at all, and simply writing the Java classes, and using a tool to generate the IDL if neccessary. 2. the Out/In Out parameter mapping is something strange. I think using a OutHolder or InOutHolder will be more clear 3. No Service is mapped, this require the queryInterface called frequently. I think a Service can be mapped to an interface which may extends other interface or aggregate optional interface inside. And more, i think there should be a util to generate the POJO mapping from exists IDL(Its better to include the documents in Java).
[dev] new CCR - Laurent Godard
Laurent Godard is the new Community Council Representative winning with 53% of the total votes. Rene, Christian and Hirano received 14%, 17% and 16% of the votes respectively. Twice as many people participated in the voting for the Community Council Representative (CCR) compared to the previous election. The Community Council (http://council.openoffice.org/) pages will be updated shortly to reflect the new members. Congratulations Laurent, and thanks again to all nominees and participants. All the best Jacqueline McNally Lead, OpenOffice.org Marketing Project - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[dev] Dialog controls: relative ImageURLs
Hi, all! I wonder if there is a way to set property ImageURL (e.g. of CommandButtons) to some kind of "relative" URL at _design time_ (i.e. not resorting to com.sun.star.util.PathSettings at runtime). I what I need is (in decreasing order of importance): 1 - an application dialog to retrieve images from its "installation" folder (inside /user/basic or /share/basic); 2 - a document dialog to retrieve images from the directory where its document is located. Unfortuantely, I am bound to version 1.1.4 and no higher. Thanks in advance. Cheers, Jorge. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[dev] Re: [api-dev] instantiating Basic dialogs from UNO componets
Thank you, Thomas! However, the company I work for does not use the beta version yet, just OOo 1.1.4. I've just checked that this service is not available there. Can that be achieved - even if much more hardly - by 1.1.4 UNO primitives? Cheers, Jorge. Quoting Thomas Benisch <[EMAIL PROTECTED]>: > Jorge Marques Pelizzoni wrote: > > > > Hi, all! Once Mathias Bauer wrote: > > > > > >>But why do you want to call Basic macros from C++? I would expect that > >>you instantiate your (IDE-designed) dialog from your C++ code (should > >>be possible by some UNO calls) ... > > > > > > Its is exactly those UNO calls that interest me. How can I (i) load/access > Basic > > libraries from an arbitrary UNO component, (ii) identify my dialog there > and > > finally instantiate it if I do not have e.g. CreateUnoDialog or > DialogLibraries > > outside Basic? > > > > Thanks in advance. Cheers, > > > > Jorge. > > Especially for dialogs designed with the dialog > editor in the Basic IDE there's the > com.sun.star.awt.DialogProvider service available > (OOo 2.0 code line). The dialog can be created > with the createDialog() method and takes a > script URL as parameter. > > If you want to load a dialog called 'MyDialog' in the > dialog library 'MyDialogLibrary' of the user/share > installation, the script URL would be: > > "vnd.sun.star.script:MyDialogLibrary.MyDialog?location=application" > > A dialog of the current document can be loaded by > > "vnd.sun.star.script:MyDocumentLibrary.MyDocumentDialog?location=document" > > Please note, that for dialogs in documents the XModel of > the current document must be passed as parameter when > instantiating the DialogProvider service. > > See also section 18.3.4 of the developers guide, which contains > an example written in Java. > > Thomas > > > - > 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: [dev] New tool for automating Makefile creation (qmake)
Pierre-Andre Galmes wrote: * Jürgen Schmidt <[EMAIL PROTECTED]> [050718 14:07]: Pierre-Andre Galmes wrote: Do you think it would be a good idea try to develop such a "tool" ? I suppose that ooomake could mainly call other tools (idlc...), to get the work done. Would it be useful to add a feature request for such a tool ? I am not sure. For Java i would say that users will probably use an IDE which is most often ANT based and so it should be no problem to create or adapt an ANT script with some OO specific tasks (e.g. IDL compilation, ...). ANT is the de facto standard for Java projects. Yes, I agree that Ant is THE scripting langage for Java ! Actually, developing for OpenOffice and Java is a quite straight forward task, as the doc (Dev's guide), the tools (Netbeans) and most of the resources are Java Oriented. So i wouldn't introduce a new build system, i would integrate in existing tools\IDE's (e.g. MS Dev integration, Eclipse and NetBeans integration and others) That would have the advantage that people who are already familar with the normal IDE can easily use that IDE for OO specific projects without learning a new build system. True ! But it must be loads of work to do it for the different environments and to maintain with the evolution of the environments. Simplifying the creation of the building step for new projects is an idea to simplify the use of the framework to develop new products. Hope this will work in some time also for C++ ! Have you already planned things like that for the future ? There are things going on for Eclipse and NetBeans (Google Summer of Code). Using gnu make was more or less a decision based on the resources we have had, i am not sure if we would that again ;-) ^_^ Thanks for the explanation ! By the way, is there an IDE well integrated for OpenOffice C++ development and docs about it ? no not really, some people have customized their IDE to make things easier but that's all as far as i know Do you know Which IDE is used by Sun's developers ? it depends, a lot of people use their preferred editor (like emacs, ultra edit, MS Dev Studio,...). For debugging we use most often the MS Dev Studio but some of the developers who are working primary on Unix use the Sun Studio on Solaris. Juergen Juergen Cheers, Pierre-Andre - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[dev] How to restrict local database registration
For policy reasons I need to prevent end-users from registering local databases (i.e. databases stored on the local hard disk) in OpenOffice via the GUI. Does someone have an idea how to do this while retaining the ability to register local databases via UNO calls? Matthias - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] New tool for automating Makefile creation (qmake)
* Jürgen Schmidt <[EMAIL PROTECTED]> [050718 14:07]: > Pierre-Andre Galmes wrote: > >Do you think it would be a good idea try to develop such a "tool" ? I > >suppose that ooomake could mainly call other tools (idlc...), to get the > >work done. Would it be useful to add a feature request for such a tool ? > I am not sure. For Java i would say that users will probably use an IDE > which is most often ANT based and so it should be no problem to create > or adapt an ANT script with some OO specific tasks (e.g. IDL > compilation, ...). ANT is the de facto standard for Java projects. Yes, I agree that Ant is THE scripting langage for Java ! Actually, developing for OpenOffice and Java is a quite straight forward task, as the doc (Dev's guide), the tools (Netbeans) and most of the resources are Java Oriented. > So i wouldn't introduce a new build system, i would integrate in > existing tools\IDE's (e.g. MS Dev integration, Eclipse and NetBeans > integration and others) That would have the advantage that people who > are already familar with the normal IDE can easily use that IDE for OO > specific projects without learning a new build system. True ! But it must be loads of work to do it for the different environments and to maintain with the evolution of the environments. Simplifying the creation of the building step for new projects is an idea to simplify the use of the framework to develop new products. Hope this will work in some time also for C++ ! Have you already planned things like that for the future ? > Using gnu make was more or less a decision based on the resources we > have had, i am not sure if we would that again ;-) ^_^ Thanks for the explanation ! By the way, is there an IDE well integrated for OpenOffice C++ development and docs about it ? Do you know Which IDE is used by Sun's developers ? > Juergen Cheers, Pierre-Andre -- "I have always wished for my computer to be as easy to use as my telephone; my wish has come true because I can no longer figure out how to use my telephone" - Bjarne Stroustrup - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] New tool for automating Makefile creation (qmake)
Pierre-Andre Galmes wrote: * Jürgen Schmidt <[EMAIL PROTECTED]> [050715 09:37]: Pierre-Andre Galmes wrote: Hello, Hello Jürgen, I apologize for the delay answering, but as you may know, in France last days were non-working days, so no internet connection for me. ^_^ In this mail, I will just focus on the idea of a new tool like "qmake". I - The context : - How are the Makefile in the exemples of the SDK created ? By hand ? yes[...] - How do you generate the makefiles in general ? Do you use automake/autoconf or any other tool ? no, as i said the makefiles are created by hand. OO itself used a build environment based on dmake. The SDK build env. was mainly introduced to build the examples easily on all platforms. II - A new tool : - Is there a tool like qmake for QT that generates the Makefile for us from the files in the project directory ? no, but it would be nice to have it. I think it would be nice too, in particular, now that the URE will be released as a separate component of OpenOffice.org. That way, new projects could be managed really easily. It could really help newcomers to OpenOffice to start understanding the API, and developers to earn time ! III - Short description for the tool : For example, such a tool by just typing commands like would generate everything to be done (IDL transformation, compilation...) in a transparent way for the developper. $ ooomake -project // (1) $ ooomake // (2) $ make // (3) (1) - Generates a file containing the dependencies the source files. Example : TEMPLATE = my_app DEPENDPATH += . INCLUDEPATH += . OOO += writer // project depends on the writer API. # Input HEADERS += hello.h SOURCES += hello.cpp SOURCES += main.cpp (2) - generates the Makefile (3) - launches the Makefile IV - links - qmake tutorial - http://doc.trolltech.com/4.0/qmake-tutorial.html qmake doc - http://doc.trolltech.com/4.0/qmake-manual.html Do you think it would be a good idea try to develop such a "tool" ? I suppose that ooomake could mainly call other tools (idlc...), to get the work done. Would it be useful to add a feature request for such a tool ? I am not sure. For Java i would say that users will probably use an IDE which is most often ANT based and so it should be no problem to create or adapt an ANT script with some OO specific tasks (e.g. IDL compilation, ...). ANT is the de facto standard for Java projects. In the long term i would like to define dependencies on service level or at least on UNO package level. That means that a dependency as you suggested (OOO += writer) would make sense when writer means a package providing writer functionality (with the necessary API's) with maybe more dependencies on other packages. So i wouldn't introduce a new build system, i would integrate in existing tools\IDE's (e.g. MS Dev integration, Eclipse and NetBeans integration and others) That would have the advantage that people who are already familar with the normal IDE can easily use that IDE for OO specific projects without learning a new build system. Using gnu make was more or less a decision based on the resources we have had, i am not sure if we would that again ;-) Juergen Juergen Regards, Pierre-Andre - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] New tool for automating Makefile creation (qmake)
* Jürgen Schmidt <[EMAIL PROTECTED]> [050715 09:37]: > Pierre-Andre Galmes wrote: > >Hello, Hello Jürgen, I apologize for the delay answering, but as you may know, in France last days were non-working days, so no internet connection for me. ^_^ In this mail, I will just focus on the idea of a new tool like "qmake". I - The context : > >- How are the Makefile in the exemples of the SDK created ? By hand ? > yes[...] > >- How do you generate the makefiles in general ? Do you use > > automake/autoconf or any other tool ? > no, as i said the makefiles are created by hand. OO itself used a build > environment based on dmake. The SDK build env. was mainly introduced to > build the examples easily on all platforms. II - A new tool : > >- Is there a tool like qmake for QT that generates the Makefile for us > > from the files in the project directory ? > no, but it would be nice to have it. I think it would be nice too, in particular, now that the URE will be released as a separate component of OpenOffice.org. That way, new projects could be managed really easily. It could really help newcomers to OpenOffice to start understanding the API, and developers to earn time ! III - Short description for the tool : For example, such a tool by just typing commands like would generate everything to be done (IDL transformation, compilation...) in a transparent way for the developper. $ ooomake -project // (1) $ ooomake // (2) $ make // (3) (1) - Generates a file containing the dependencies the source files. Example : TEMPLATE = my_app DEPENDPATH += . INCLUDEPATH += . OOO += writer // project depends on the writer API. # Input HEADERS += hello.h SOURCES += hello.cpp SOURCES += main.cpp (2) - generates the Makefile (3) - launches the Makefile IV - links - qmake tutorial - http://doc.trolltech.com/4.0/qmake-tutorial.html qmake doc - http://doc.trolltech.com/4.0/qmake-manual.html Do you think it would be a good idea try to develop such a "tool" ? I suppose that ooomake could mainly call other tools (idlc...), to get the work done. Would it be useful to add a feature request for such a tool ? > Juergen Regards, Pierre-Andre -- "I have always wished for my computer to be as easy to use as my telephone; my wish has come true because I can no longer figure out how to use my telephone" - Bjarne Stroustrup - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] SimpleBootstrap_cpp Makefile Issue
* Jürgen Schmidt <[EMAIL PROTECTED]> [050715 09:11]: > Hi, Hi Jürgen, Thanks for taking the time to answer. > do you have used configure to prepare the setsdkenv script? Yes, I did. > Can you build any other example? Yes, other examples do compile. Did you try to compile this example with the m113_SDK and OOo_m113 ? Does it work for you ? Regards, Pierre-Andre -- "I have always wished for my computer to be as easy to use as my telephone; my wish has come true because I can no longer figure out how to use my telephone" - Bjarne Stroustrup - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
