[dev] Regarding participating in Programming of OpenOffice
Hi, My name is Pradip Bhattacharya and I am working as a 3d mobile game engine programmer. I have 3.6 years of experience in C,C++ and Java. I am very happy with OpenOffice software as a replacement for other commercially available word processors. I would like to contribute my inputs towards this revolution. Please do let me know if I can be of any use. regards Pradip.B
Re: [dev] Detailed build deps
Hi, Nguyen Vu Hung wrote: Tora says he has VMware images for those builds. You can ask him for a copy. The following Wiki page might help you understand why I have chosen Fedora Core 4 to build OpenOffice.org 2.x. Build Environment Running on Fedora Core 4 http://wiki.services.openoffice.org/wiki/Build_Environment_Running_on_Fedora_Core_4 Regards, Tora - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] XStorable and copy/pasting text containing Microsoft Equation objects
2009/2/14 Mathias Bauer nospamfor...@gmx.de: You don't need a complete debug build to track this down. You just need some pdb files and the matching source code. This will give you the call stack and line numbers. I can collect some pdb files for you, the source code is available via cvs. I think you need both for the following modules: sw, svx, sfx2, embeddedobj, svtools, comphelper. We were thinking about creating the build environment anyways - it's just a matter of time and resources, but I guess I should be able to work it out soon. You mentioned that you are using OOo 2.4.1. Just to avoid misunderstandings: can you give me the exact milestone number? It should be visible in the about box. If it is not visible, try hitting CTRL-SDT. You should find something like OOHm17 or so (the number behind the m is important). Its OOH680_m17 Build-1, czech language. Regards, Martin - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Detailed build deps
Nguyen Vu Hung wrote: Tora says he has VMware images for those builds. You can ask him for a copy. That sounds nice! Not only source codes but also the build environment live VM should be maintained and shared with us. Is there good website on which we can get the VM image? oohack - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Detailed build deps
Hi, Tora says he has VMware images for those builds. You can ask him for a copy. That sounds nice! there are also Virtualbox Images with everything included for Ubuntu http://wiki.services.openoffice.org/wiki/Prepared_Build_Images Regards Max - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
[dev] DevGuide Wiki / discussion of SDK examples / source code links into a repository
Hi, Clayton Cornell from documentat...@openoffice.org referred me to discuss a point on this list. You can already find some arguments in the thread DevGuide Wiki on docume...@openoffice.org. Ariel Constenla-Haile mentioned in this thread, that Juergen Schmidt already has some plans pertaining to this point. So let me give a summary: The DevGuide contains a lot of code to explain how to do things, but it almost always limits the code shown to some excerpt, hence focussing on one particular (and probably the most important) point. At least as far as I am concerned I almost always wonder about how a particular piece of code is used and I want to look at the class file as a whole. Since it doesn't make sense to copy the whole source code into the Wiki, a link into the source code repository would make sense and be great. It would be cumbersome to always look things up in an IDE -- instead of just clicking on a link. A first idea was to use, e.g., a link of the form http://svn.services.openoffice.org/opengrok/xref/Current%20 (trunk)/odk/examples/DevelopersGuide/FirstSteps/FirstUnoContact.java to refer to the class FirstUnoContact.java. As Ariel mentioned (in the thread quoted above) Juergen seems to have an idea about a more far-reaching structural change of the DevGuide Wiki concerning the discussion of the SDK examples. Since I am currently reading a larger part of the DevGuide and having a closer look at the SDK examples, I could readily apply some changes to the Wiki. But, on the face of it, I should only do it after the desired outcome has been clearly specified by the community. I am looking forward to any suggestion. -Karl - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] DevGuide Wiki / discussion of SDK examples / source code links into a repository
Hi Karl, let me describe what i have in mind ... First of all i would like to reduce the size of the SDK and i would like to remove most of the examples. In case of the Java examples it definitely makes sense to provide NetBeans or Eclipse projects because it simplifies the whole stuff a lot (easy building and debugging through the code). So the idea is to provide in a first step NB projects for the Java examples of SDK (more or less done by Ariel - many thanks again, http://wiki.services.openoffice.org/wiki/API/Samples/Java) and document them in the wiki. Well the wiki should explain the examples in general and on potential subpages the specific details for NB or Eclipse projects are explained. Ideally we will have the examples available not only in Java but alos in C++ and Python. That means MS Visual Studio projects, maybe XCode projects, etc. The DevGuide will still present related code snippets and of course should provide links to the main example wiki page. Java as the preferred example language should remain in the DevGuide. But as mentioned before we would ideally have the examples in different languages available. Users can easy checkout the example sources from the code repository and can use them in there preferred IDE. Currently they can be easy downloaded as zips. The advantage of this approach is that we can reach more potential users. And of course advanced users can easier help to improve the examples, fix problems etc. It's still a lot of work to provide good example that are well documented ... Often the developers don't focus on developer documentation and examples. But we need it and it is a good opportunity for new developers to get started. Working on examples, understanding the concepts and help others to understand what they have learned etc. Later on the next step to work on or with the real office code should become easier... Juergen Karl Weber wrote: Hi, Clayton Cornell from documentat...@openoffice.org referred me to discuss a point on this list. You can already find some arguments in the thread DevGuide Wiki on docume...@openoffice.org. Ariel Constenla-Haile mentioned in this thread, that Juergen Schmidt already has some plans pertaining to this point. So let me give a summary: The DevGuide contains a lot of code to explain how to do things, but it almost always limits the code shown to some excerpt, hence focussing on one particular (and probably the most important) point. At least as far as I am concerned I almost always wonder about how a particular piece of code is used and I want to look at the class file as a whole. Since it doesn't make sense to copy the whole source code into the Wiki, a link into the source code repository would make sense and be great. It would be cumbersome to always look things up in an IDE -- instead of just clicking on a link. A first idea was to use, e.g., a link of the form http://svn.services.openoffice.org/opengrok/xref/Current%20 (trunk)/odk/examples/DevelopersGuide/FirstSteps/FirstUnoContact.java to refer to the class FirstUnoContact.java. As Ariel mentioned (in the thread quoted above) Juergen seems to have an idea about a more far-reaching structural change of the DevGuide Wiki concerning the discussion of the SDK examples. Since I am currently reading a larger part of the DevGuide and having a closer look at the SDK examples, I could readily apply some changes to the Wiki. But, on the face of it, I should only do it after the desired outcome has been clearly specified by the community. I am looking forward to any suggestion. -Karl - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] DevGuide Wiki / discussion of SDK examples / source code links into a repository
Hi Juergen, first of all, thanks for your long answer. Please find my reply below. Am Montag, 16. Februar 2009 22:25 schrieb Juergen Schmidt: Hi Karl, let me describe what i have in mind ... First of all i would like to reduce the size of the SDK and i would like to remove most of the examples. In case of the Java examples it definitely makes sense to provide NetBeans or Eclipse projects because it simplifies the whole stuff a lot (easy building and debugging through the code). So the idea is to provide in a first step NB projects for the Java examples of SDK (more or less done by Ariel - many thanks again, http://wiki.services.openoffice.org/wiki/API/Samples/Java) and document them in the wiki. Well the wiki should explain the examples in general and on potential subpages the specific details for NB or Eclipse projects are explained. Ideally we will have the examples available not only in Java but alos in C++ and Python. That means MS Visual Studio projects, maybe XCode projects, etc. The DevGuide will still present related code snippets and of course should provide links to the main example wiki page. Java as the preferred example language should remain in the DevGuide. But as mentioned before we would ideally have the examples in different languages available. Users can easy checkout the example sources from the code repository and can use them in there preferred IDE. Currently they can be easy downloaded as zips. The advantage of this approach is that we can reach more potential users. And of course advanced users can easier help to improve the examples, fix problems etc. It's still a lot of work to provide good example that are well documented ... Often the developers don't focus on developer documentation and examples. But we need it and it is a good opportunity for new developers to get started. Working on examples, understanding the concepts and help others to understand what they have learned etc. Later on the next step to work on or with the real office code should become easier... Juergen Hmm, may be it is too late already, but I do not quite understand your idea. So let me try to express it in my words: (1) The DevGuide, in particular with respect to presenting only code snippets in Java, should remain as it is. (2) Boxes with code snippets in the DevGuide should have a link to the one(!) main examples page. So, starting from a code snippet in the DevGuide I click one link to get to the main examples page. (3) The main examples page contains a list of all examples available. On this page I can click on another link to get to another page that discusses the particular example in Java (or any other language) which contains the code snippet from (1), where I started. (One page for every example or even one page for every example _and_ every language?) From this page, I can again navigate to other pages, giving me particulars about the project files for NB or Eclipse or, ... On these pages I might also find links to download the project files for the particular example for the respective IDE. If this is what you mean, where do I find the code? My idea was to start from (1) and find a link to a page where I can read the code on-line. A very good example about what I have in mind is [1]. When I learn something like UNO I don't have to build and run every example. Very often it is enough to just read the code. So it would be great if I could read it by just clicking some links -- refer to [1] again. It would be cumbersome, if I had to download the example and install the project in an IDE in order to just read the code. Even worse, what if I don't use NB, and don't want to use it? If the examples are available only as NB projects, chances are high, that I will not only get frustrated, but that I will loose interest. O.K., my idea will not work for BASIC examples with dialogs. These examples I will have to download and open with OOo. To summarise: (a) It is not clear to me, whether your idea will incorporate the possibility to read code on-line or not. (b) How many pages should there be for every example (see question above)? -Karl [1] https://developer.mozilla.org/en/Viewing_and_searching_Mozilla_source_code_online - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Java extension works directly after installation, but not after Office restart - how to debug?
Christian Lohmaier pisze: Hi Marcin, *, On Fri, Feb 13, 2009 at 9:00 PM, Marcin Miłkowski milek...@o2.pl wrote: Hi Christian, did you try using another JRE? Yes. also tried with 1.5.u17 - same result. [snip] I haven't used 1.6u11 yet and there could be some regression in it. Sometimes also removing javasettings.xml in your user directory helps resolve some problems with Java in OOo. This doesn't help unfortunately, removing the user-profile completely doesn't help either. Hm, this could be related to uno process still in memory. What does ps say about it? In Windows, I've seen tens of uno.exe in memory after OOo crash. You could try using a developer version of the Java extensions with a remote debugger as described here: http://cedric.bosdonnat.free.fr/wordpress/?p=57 But I wouldn't bet much on that - probably this is not visible on the level of Java code. BTW, is Java working for you correctly at all? Maybe it's system-wide, not OOo-specific... Regards Marcin - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] DevGuide Wiki / discussion of SDK examples / source code links into a repository
Hello Juergen, On Monday 16 February 2009 19:25, Juergen Schmidt wrote: So the idea is to provide in a first step NB projects for the Java examples of SDK (more or less done by Ariel - many thanks again, http://wiki.services.openoffice.org/wiki/API/Samples/Java) you're wellcome, but the work on the Wiki is from Jirong Zhang (http://wiki.services.openoffice.org/wiki/User:Jirong), from RedFlag; mine is on the CVS repository (api/examples/java) and will be finished in April (currently only the UNO components examples work). Regards -- Ariel Constenla-Haile La Plata, Argentina Aus der Kriegsschule des Lebens - Was mich nicht umbringt, macht mich härter. Nietzsche Götzendämmerung, Sprüche und Pfeile, 8. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] DevGuide Wiki / discussion of SDK examples / source code links into a repository
Hi Kark, Previousely, I was a microsoft visual studio developer. As you might know, the MSDN ( http://msdn.microsoft.com/ ) is the latest and most important information resources . Because there are a lot of snipped codes, I don't feel unconfortable even if the DevGuide provides same things like that. Traditionally, detailed examples have been provided by power users' blogs, magazines and books, you know. Then, if we try to the next challenge, how about having the My examples sections under the snipped codes or around there. This My examples sections are allowed to edit if you are a member of OpenOffice Deveoper community. I mean some identification like ID is mandatory. And hopefully, if we have some ranking systems for each examples, that should be nicer. Just small idea. Takashi. - Original Message - From: Karl Weber karl.webe...@gmx.net To: dev@openoffice.org Sent: Tuesday, February 17, 2009 5:38 AM Subject: [dev] DevGuide Wiki / discussion of SDK examples / source code links into a repository Hi, Clayton Cornell from documentat...@openoffice.org referred me to discuss a point on this list. You can already find some arguments in the thread DevGuide Wiki on docume...@openoffice.org. Ariel Constenla-Haile mentioned in this thread, that Juergen Schmidt already has some plans pertaining to this point. So let me give a summary: The DevGuide contains a lot of code to explain how to do things, but it almost always limits the code shown to some excerpt, hence focussing on one particular (and probably the most important) point. At least as far as I am concerned I almost always wonder about how a particular piece of code is used and I want to look at the class file as a whole. Since it doesn't make sense to copy the whole source code into the Wiki, a link into the source code repository would make sense and be great. It would be cumbersome to always look things up in an IDE -- instead of just clicking on a link. A first idea was to use, e.g., a link of the form http://svn.services.openoffice.org/opengrok/xref/Current%20 (trunk)/odk/examples/DevelopersGuide/FirstSteps/FirstUnoContact.java to refer to the class FirstUnoContact.java. As Ariel mentioned (in the thread quoted above) Juergen seems to have an idea about a more far-reaching structural change of the DevGuide Wiki concerning the discussion of the SDK examples. Since I am currently reading a larger part of the DevGuide and having a closer look at the SDK examples, I could readily apply some changes to the Wiki. But, on the face of it, I should only do it after the desired outcome has been clearly specified by the community. I am looking forward to any suggestion. -Karl - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
