Re: [dev] Consolidating build instructions for the community
Christian Lohmaier skrev: Hi Marcin, *, 2009/7/16 Marcin Miłkowski milek...@o2.pl: Christian Lohmaier pisze: I still disagree. Basically /all/ of the questions asken on IRC about building OOo were because people are unable to read configure or because they don't use vanilla build system. Most of those didn't bother to read any instructions, didn't look for instructions. I could reply that probably using IRC is eating their brains ;) as most questions asked at dev seem to be quite different. Those questions will not be answered by a building OOo for newbies guide. The one I remember fall into the not using vanilla OOo/not taking advice given category. /../ To get this straight: I'm /not/ against consolidating the pages, au contraire, I support getting rid of old pages. But: I am against yet another place (instead of reusing the existing pages) I am against the structure as it appears now I doubt that the new documentation will cause less questions. I'm speaking for myself only, and of course don't tell anybody to stop with the efforts. This documentation will replace the current wiki pages, including the build guides at tools. So you will find a less number of pages than before. Per - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
[dev] Re: [documentation-dev] Consolidating build instructions for the community
Hi Per, IMO this is a great and valuable job. A very big + from my side :-) Cor Per Eriksson wrote (15-7-2009 11:09) Hello, I am cross-posting this to dev and documentation, but think that best would be if discussions run on dev, as many of the details probably will be discussed there. As a part of the Simplifying entry for new developers [1] effort I have the idea of collecting all the wiki pages about building the software into a building guide, as the developer guide [2]. I have discussed with several people about including it into the developer guide, but the answer was always that the developer guide would get too big. I therefore see building as an own process or part. Having a building guide would simplify and make it easier for new developers to find articles and getting to the right pages faster by providing the navigation as in the developer guide. This work would be done by sorting, consolidating and editing the various wiki pages into a guide with a structure. In this work various negative comments about building OpenOffice.org being impossible in the articles will be replaced by constructive tips for the developer. If you think this is a good idea, I will start a new small effort for this in the wiki. [1] http://wiki.services.openoffice.org/wiki/Development/Simplifying_entry_for_new_developers#Building_the_software [2] http://wiki.services.openoffice.org/wiki/Documentation/DevGuide/OpenOffice.org_Developers_Guide Per -- Cor Nouws - nl.OpenOffice.org marketing contact Ontwikkelaar? Join! http://council.openoffice.org/developers.html Gevoel niet vrij te zijn? Zie www.nieuwsteversie.nl - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Consolidating build instructions for the community
Hello Regina, Regina Henschel skrev: Hi Per, Per Eriksson schrieb: I have created the guide here: http://wiki.services.openoffice.org/wiki/Development/OpenOffice.org_Building_Guide And these are the page created so far: OpenOffice.org_Building_Guide OpenOffice.org_Building_Guide/Introduction OpenOffice.org_Building_Guide/Getting the source OpenOffice.org_Building_Guide/Basic Concepts OpenOffice.org_Building_Guide/Build Requirements OpenOffice.org_Building_Guide/Windows Build Requirements OpenOffice.org_Building_Guide/Mac OS X Build Requirements OpenOffice.org_Building_Guide/Linux Build Requirements OpenOffice.org_Building_Guide/Solaris Build Requirements Now to the articles that describe the building for the various platforms. I have read through the existing documentation, and come up with the following headlines. Do anyone feel it should look differently? OpenOffice.org_Building_Guide/Building on Windows with Cygwin OpenOffice.org_Building_Guide/Building on Windows with Visual Studio OpenOffice.org_Building_Guide/Building on Mac OS X OpenOffice.org_Building_Guide/Building on Linux OpenOffice.org_Building_Guide/Building on Solaris I would like it more, to have the Requirements in the same chapter as Building. That means main chapters for the OS and then subchapters as needed. Otherwise I would again have to collect the information that are relevant for my OS. On the other hand, I do not know whether a subchapter Requirements is really needed. During the guide [1] you are told, which things are needed and -more important- what you have to consider when installing it or copying to the right place. You're right that they cause too many pages, we don't want to have the situation we have today. I plan to move the requirements for each specific platform soon. You have the two chapters Windows with Cygwin and Windows with Visual Studio. Is there a way to build OOo with Visual Studio without Cygwin? I don't know. I have looked through the various documents for the Windows platform, and you're right that they use both Visual Studio and Cygwin. It will thus be only one document for Windows. For Windows with Cygwin link to [1] http://wiki.services.openoffice.org/wiki/Building_OOo_with_Cygwin_on_Windows I'll move this page into this guide, to maintain the history if this is alright. When content comes from html pages though I have to copy it though. The guide is very good. With that guide I was able to get my first build :) Then this is the document all new developers should read. ;-) Thank you Regina. Per - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Consolidating build instructions for the community
Hi Christian, i really don't understand what your problem is. Maybe you missed the goal of Per's work, it is simply the consolidation of several different pages into one new place, put some structure on it and extend or improve it where necessary. From my point of view structure is always good and the documentation project did a good job here. So why not using the same technique in other places. Call it guide, book or whatever. In the end you don't have to read it all, you will be guide to the pages you need. And i think you look on it with the wrong glasses. You are very familiar with all this stuff and it's clear for you as well as for others. Great you can read configure but many others not. But they maybe want to build OOo on their own because they can C++. And they are maybe able to fix some issues, are able to create patches (with the right instruction), etc. etc. The work Per is doing is not for the developers we already have it is probably more for new ones. We should support this effort with the knowledge we have and make it a valuable resource for new developers. The only place we have to maintain for future changes, improvements in this area. Juergen Christian Lohmaier wrote: Hi Marcin, *, 2009/7/16 Marcin Miłkowski milek...@o2.pl: Christian Lohmaier pisze: I still disagree. Basically /all/ of the questions asken on IRC about building OOo were because people are unable to read configure or because they don't use vanilla build system. Most of those didn't bother to read any instructions, didn't look for instructions. I could reply that probably using IRC is eating their brains ;) as most questions asked at dev seem to be quite different. Those questions will not be answered by a building OOo for newbies guide. The one I remember fall into the not using vanilla OOo/not taking advice given category. The other ones were build breakers are introduced (already built successfully in the past, newer milestone breaks). System components change in a incompatible way. Nothing that could be covered in a simple guide. (but rather are bugs in the code) [...] Linux build was strangely broken). Those even less. To get this straight: I'm /not/ against consolidating the pages, au contraire, I support getting rid of old pages. But: I am against yet another place (instead of reusing the existing pages) I am against the structure as it appears now I doubt that the new documentation will cause less questions. I'm speaking for myself only, and of course don't tell anybody to stop with the efforts. ciao Christian - 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] Consolidating build instructions for the community
Hi Christian, *, Christian Lohmaier pisze: Hi Marcin, *, 2009/7/16 Marcin Miłkowski milek...@o2.pl: Christian Lohmaier pisze: I still disagree. Basically /all/ of the questions asken on IRC about building OOo were because people are unable to read configure or because they don't use vanilla build system. Most of those didn't bother to read any instructions, didn't look for instructions. I could reply that probably using IRC is eating their brains ;) as most questions asked at dev seem to be quite different. Those questions will not be answered by a building OOo for newbies guide. The one I remember fall into the not using vanilla OOo/not taking advice given category. Actually, people were asking quite frequently about details regarding Windows build because they found one page about it but not another one in the wiki (there were several pages that were not linked to each other and it was really hard to find them). This is exactly what will be fixed by Per. The other ones were build breakers are introduced (already built successfully in the past, newer milestone breaks). System components change in a incompatible way. Nothing that could be covered in a simple guide. (but rather are bugs in the code) This is true but if you're a new developer, you might be unaware of the fact that you can easily query IZ and find the patch already submitted by pjanik or others for such build problems. I doubt that the new documentation will cause less questions. Maybe there will be more questions because less people will be intimidated to build OOo and try their own patches. And one more thing: OOo is mainly C++ but sometimes you might want to fix a small snippet of Java inside it, and for that you don't really have to know how to develop in C++. So there are cases when you don't have to be familiar with the usual C++ configuring stuff to submit a patch of some value. Regards Marcin - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Consolidating build instructions for the community
Hello, Marcin Miłkowski skrev: I doubt that the new documentation will cause less questions. Maybe there will be more questions because less people will be intimidated to build OOo and try their own patches. Yes Marcin, you are right and I really hope so. It would be great. Because it would lead to more fixes, more programmers, more contributors and more new features to the market. And one more thing: OOo is mainly C++ but sometimes you might want to fix a small snippet of Java inside it, and for that you don't really have to know how to develop in C++. So there are cases when you don't have to be familiar with the usual C++ configuring stuff to submit a patch of some value. Per - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Consolidating build instructions for the community
Hello, Here is how far I've come so far. Several pages' content have now been moved to these 7 pages: http://wiki.services.openoffice.org/wiki/Development/OpenOffice.org_Building_Guide They originate from various places (which can be hard to find), including: http://tools.openoffice.org/background.html http://tools.openoffice.org/dev_docs/build_linux.html http://tools.openoffice.org/dev_docs/build_solaris.html http://tools.openoffice.org/dev_docs/build_windows_tcsh.html http://wiki.services.openoffice.org/wiki/Building_OpenOffice.org http://wiki.services.openoffice.org/wiki/Windows http://wiki.services.openoffice.org/wiki/Building_OOo_with_Cygwin_on_Windows http://wiki.services.openoffice.org/wiki/Build_Requirements http://wiki.services.openoffice.org/wiki/Build_Linux_Requirements http://wiki.services.openoffice.org/wiki/Build_Windows_Requirements http://wiki.services.openoffice.org/wiki/Build_Solaris_Requirements We are currently *saving* 4 pages, and it will surely increase to more. Some wiki pages already redirect to this new content. The plan is to redirect all the pages, including the tools html pages, each to the corresponding new documents. It will surely be easier for us to update the pages when they are placed more together. It will also be easier to spot irragularities as the instructions are closer to eachother. I have not moved any content for Mac, and I will not do. What I need help with: ** Go through the Windows pages and do any updating that might be needed to the new document. We want all the correct information to be in the new document. http://wiki.services.openoffice.org/wiki/Building_OOo_with_Cygwin_on_Windows http://wiki.services.openoffice.org/wiki/Building_OpenOffice.org http://wiki.services.openoffice.org/wiki/Windows http://tools.openoffice.org/dev_docs/build_windows_tcsh.html E.g. the section about getting the source is already covered by this topic in the guide. ** Design fixes to the new documents, there are still some structure stuff to improve. Per Juergen Schmidt skrev: Hi Christian, i really don't understand what your problem is. Maybe you missed the goal of Per's work, it is simply the consolidation of several different pages into one new place, put some structure on it and extend or improve it where necessary. From my point of view structure is always good and the documentation project did a good job here. So why not using the same technique in other places. Call it guide, book or whatever. In the end you don't have to read it all, you will be guide to the pages you need. And i think you look on it with the wrong glasses. You are very familiar with all this stuff and it's clear for you as well as for others. Great you can read configure but many others not. But they maybe want to build OOo on their own because they can C++. And they are maybe able to fix some issues, are able to create patches (with the right instruction), etc. etc. The work Per is doing is not for the developers we already have it is probably more for new ones. We should support this effort with the knowledge we have and make it a valuable resource for new developers. The only place we have to maintain for future changes, improvements in this area. Juergen Christian Lohmaier wrote: Hi Marcin, *, 2009/7/16 Marcin Miłkowski milek...@o2.pl: Christian Lohmaier pisze: I still disagree. Basically /all/ of the questions asken on IRC about building OOo were because people are unable to read configure or because they don't use vanilla build system. Most of those didn't bother to read any instructions, didn't look for instructions. I could reply that probably using IRC is eating their brains ;) as most questions asked at dev seem to be quite different. Those questions will not be answered by a building OOo for newbies guide. The one I remember fall into the not using vanilla OOo/not taking advice given category. The other ones were build breakers are introduced (already built successfully in the past, newer milestone breaks). System components change in a incompatible way. Nothing that could be covered in a simple guide. (but rather are bugs in the code) [...] Linux build was strangely broken). Those even less. To get this straight: I'm /not/ against consolidating the pages, au contraire, I support getting rid of old pages. But: I am against yet another place (instead of reusing the existing pages) I am against the structure as it appears now I doubt that the new documentation will cause less questions. I'm speaking for myself only, and of course don't tell anybody to stop with the efforts. ciao Christian - 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,
Re: [dev] Consolidating build instructions for the community
Hi Jürgen, *, On Thu, Jul 16, 2009 at 10:48 AM, Juergen Schmidtjuergen.schm...@sun.com wrote: i really don't understand what your problem is. My problem is that everyone is eager to start new projects, new efforts instead of improviing what is there already. My problem is that if you really feel the need of simplifying the build, then don't do it by adding instructions, but by actually making the build itself simpler. Maybe you missed the goal of Per's work, it is simply the consolidation of several different pages into one new place, Seems like my points didn't come through either. I'm all for removing duplication in the build instructions. I was against duplication in the past already. So full support on that item from my side. [...] And i think you look on it with the wrong glasses. You are very familiar with all this stuff and it's clear for you as well as for others. No. I did compile OOo myself for the first time in the past as well. At that time, I just did read the instructions and off it went. I did look for info. I didn't assume I know already. Great you can read configure but many others not. I didn't speak about reading configure itself, but reading the output of configure, i.e. what configure tells you to do when you run it. That's a big difference. If configure prints get file from URL or use mingw and people still complain about not being able to tell where to get file, that sepaks for itself. [...] The work Per is doing is not for the developers we already have it is probably more for new ones. Probably that's another part of the problem I have. This makes it sound like there wouldn't be any documenation for new builders at all. That's just not the case. ciao Christian - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Consolidating build instructions for the community
Hi Christian, Christian Lohmaier skrev: Hi Jürgen, *, On Thu, Jul 16, 2009 at 10:48 AM, Juergen Schmidtjuergen.schm...@sun.com wrote: i really don't understand what your problem is. My problem is that everyone is eager to start new projects, new efforts instead of improviing what is there already. My problem is that if you really feel the need of simplifying the build, then don't do it by adding instructions, but by actually making the build itself simpler. Maybe there are several meanings of the word consolidation. For me it means to move and merge documents together to create fewer documents. The goal has always been to cut the number of documents in half, and provide better linking. Please take a look at the current draft and say what you think. Per - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
[dev] Adding custom Form Control Elements
Hallo, is it possible to add custom Form Control Elements to OO Write? Background of this question is, that I want to add some new Elements to the already available XForms Designer. At the moment things like repeat and so on are missing. Thats why I wanted to know if it is possible to add a custom button with a custom Icon to OpenOffice Write as a Form Controle Element. I already searched for any tutorial or documentation but I didn't find anything. Maybe anyone here can tell me if this is possible or link me a documentation or somthing like that. Greetings Jakob
Re: [dev] Consolidating build instructions for the community
Hi Christian, *, [...] The work Per is doing is not for the developers we already have it is probably more for new ones. Probably that's another part of the problem I have. This makes it sound like there wouldn't be any documenation for new builders at all. That's just not the case. There's additional value in what Per was doing: removing obsolete instruction concerning CVS etc. Note: I was unable to find a good page about SVN just two months ago in OOo wiki, and I've seen that most of the build instructions were really outdated as they didn't point to real sources. If you think that having instruction which is completely off the mark is OK, then you probably don't understand the point of having documentation. Note: documentation is just what it is, it documents the current processes. It cannot simplify them. Maybe OOo should move to more standard build tools: this comes up in conversation quite a lot, and maybe standard autoconfigure tools would work. But migrating to a complete new set of build tools is a major project for many people, and probably not worth the effort. Idiots will of course stay idiots and will ask stupid questions. But there is one thing you do in such a case: you create a FAQ and put the link to the FAQ instead of answering all that stupid questions. Regards Marcin - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Consolidating build instructions for the community
Hi, Christian skrev: Probably that's another part of the problem I have. This makes it sound like there wouldn't be any documenation for new builders at all. That's just not the case. The problem which this effort is working with [1], has got a lot to do with problems with linking on our website. We know where the new developers arrive, at development and contributing. Yet these pages points you to other pages than the beginner documents. This intends to be fixed. The wiki page is currently identifying several issues and suggesting several solutions to them. An extremely simple and constructive way of working. Several project leads are also informed what we are trying to do and think it's a well needed effort. 1. http://wiki.services.openoffice.org/wiki/Development/Simplifying_entry_for_new_developers Per - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] cws rebase failed
Hi Max, Maximilian Odendahl wrote: Hi, SVN 1.5.4 is OK. so any idea why new files were not added during rebase? Sorry, no. Without a log it's hard to guess what went wrong there. Heiner -Max - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org -- Jens-Heiner Rechtien recht...@sun.com - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
[dev] Re: Consolidating build instructions for the community
Christian Lohmaier cloph at openoffice.org writes: My problem is that everyone is eager to start new projects, new efforts instead of improviing what is there already. Cleaning up the docs _is_ improving what is already there. My problem is that if you really feel the need of simplifying the build, then don't do it by adding instructions, but by actually making the build itself simpler. Is a different scope and there are different skillsets needed for both tasks. And both efforts can produce better results. No. I did compile OOo myself for the first time in the past as well. At that time, I just did read the instructions and off it went. I did look for info. I didn't assume I know already. Well, I you look at the current wikipages, it reads like its written by an ADHS-impaired kid: Lots of You might want to ..., You might need to ... etc. with workarounds for problems that are likely long gone. Quoting the Zen of Python: There should be one-- and preferably only one --obvious way to do it. The docs currently provide too many options without noting the one that is the: - most useful - most robust - best documented, updated and supported If configure prints get file from URL or use mingw and people still complain about not being able to tell where to get file, that sepaks for itself. For example, in that particular case I am still wondering, why the URL that configure barfs out isnt a direct one (that is wget-able), but one to an directory where one finds the link to the real unowinreg.dll. Thats just unneeded hassle. Probably that's another part of the problem I have. This makes it sound like there wouldn't be any documenation for new builders at all. That's just not the case. Actually, outdated documentation is much worse than no documentation. Have Fun, Bjoern - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
[dev] Interested in helping with development
I was laid-off from Sun's C++ compiler team last year and have not yet found a new job. To avoid going crazy with nothing to do I would like to become involved with Open Office. Low level C++ issues such as exception handling is the area I know the most about. I have access to systems running Windows XP and Ubuntu Linux. Terrence Miller - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Interested in helping with development
Hello Terrence, Welcome to our community. Nice to know that you have such fine competences in C++. I would currently recommend you reading the the following documents: http://wiki.services.openoffice.org/wiki/I_want_to_be_an_OpenOffice.org_developer http://contributing.openoffice.org/programming.html All questions you might have is welcome on this list. Once again welcome, Per Terrence Miller skrev: I was laid-off from Sun's C++ compiler team last year and have not yet found a new job. To avoid going crazy with nothing to do I would like to become involved with Open Office. Low level C++ issues such as exception handling is the area I know the most about. I have access to systems running Windows XP and Ubuntu Linux. Terrence Miller - 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] Interested in helping with development
Hi Terence, Le 16 juil. 09 à 18:02, Terrence Miller a écrit : I was laid-off from Sun's C++ compiler team last year and have not yet found a new job. To avoid going crazy with nothing to do I would like to become involved with Open Office. Low level C++ issues such as exception handling is the area I know the most about. I have access to systems running Windows XP and Ubuntu Linux. If you are not affraid with IRC, you can contact us on IRC, on #education.openoffice.org channel (server is irc.freenode.net ). I'm there until tomorrow, and we'll be glad to answer your questions, but waiting I'll be back from hollidays, other will certainly be glad to help you. FYI, we can help you to build OOo on all OS (Windows, Mac OS X and Linux), discover how things work, and start with debugging (using gdb). See you :) Eric Bachard -- qɔᴉɹə
Re: [dev] Interested in helping with development
Hi Terence, I think it is exemplary of you to get involved. OOo is a great way to pass the time productively and have fun, too. Per already pointed you in the right direction, but I also thought I'd also point out: http://wiki.services.openoffice.org/wiki/BugBountyProgram/Issues http://wiki.services.openoffice.org/wiki/Extensions_development#Ideas Glad to have you with us! You are very welcome in the OOo community and doing good stuff here is an impressive addition to any resume. Best regards, Liz On 07/16/09 18:29, Per Eriksson wrote: Hello Terrence, Welcome to our community. Nice to know that you have such fine competences in C++. I would currently recommend you reading the the following documents: http://wiki.services.openoffice.org/wiki/I_want_to_be_an_OpenOffice.org_developer http://contributing.openoffice.org/programming.html All questions you might have is welcome on this list. Once again welcome, Per Terrence Miller skrev: I was laid-off from Sun's C++ compiler team last year and have not yet found a new job. To avoid going crazy with nothing to do I would like to become involved with Open Office. Low level C++ issues such as exception handling is the area I know the most about. I have access to systems running Windows XP and Ubuntu Linux. Terrence Miller - 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 -- Sun Microsystems GmbHElizabeth Matthis Nagelsweg 55 User Experience Engineer 20097 HamburgPhone: (+49 40)23646 500 Germany Fax: (+49 40)23646 550 http://www.sun.com mailto:elizabeth.matt...@sun.com Sitz der Gesellschaft: Sonnenallee 1, D-85551 Kirchheim-Heimstetten Amtsgericht München: HRB 161028 Geschäftsführer: Thomas Schröder, Wolfgang Engels, Wolf Frenkel Vorsitzender des Aufsichtsrates: Martin Häring - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
[dev] Re: Interested in helping with development
Terrence Miller terrencem at sbcglobal.net writes: To avoid going crazy with nothing to do I would like to become involved with Open Office. Low level C++ issues such as exception handling is the area I know the most about. I have access to systems running Windows XP and Ubuntu Linux. Hi Terence, Well, for starters just try to build the product: http://wiki.services.openoffice.org/wiki/Development/OpenOffice.org_Building_Guide Feel free to report any problems you ran into when trying to compile OOo. I would recommend to use Linux as development platform if you are free to choose. When you are done with a build, you might help us by fixing a bug of your choice ;-). For further discussion on what can be done and how to get started I guess its best to join the IRC-channel #dev.openoffice.org on freenode. Have Fun, Bjoern Michaelsen - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
[dev] Re: Consolidating build instructions for the community
Per Eriksson pereriksson at openoffice.org writes: Thanks for all the kind words. I have created the guide here: http://wiki.services.openoffice.org/wiki/Development/OpenOffice.org_Building_Guide And these are the page created so far: OpenOffice.org_Building_Guide OpenOffice.org_Building_Guide/Introduction OpenOffice.org_Building_Guide/Getting the source OpenOffice.org_Building_Guide/Basic Concepts ... Hi Per, great stuff, but can you make the source wiki pages from which the info in the Building Guide is collected #REDIRECT to the development guide? That would help weed out old and rotting duplicate content. I did that already with the Getting the source page (and also updated/fixed a bit in it). We should viciously remove all those distributed tidbit-pages (after their info is in the build guide) as those do, among other things, mess up search results. Have Fun, Bjoern - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Re: Consolidating build instructions for the community
Hi, Bjoern Michaelsen skrev: great stuff, but can you make the source wiki pages from which the info in the Building Guide is collected #REDIRECT to the development guide? That would help weed out old and rotting duplicate content. I did that already with the Getting the source page (and also updated/fixed a bit in it). We should viciously remove all those distributed tidbit-pages (after their info is in the build guide) as those do, among other things, mess up search results. Sure, I still have a lot to do with the pages. The Windows pages will still take a few days I think. Whenever I can I will provide redirects for Building OpenOffice.org and Windows articles, sure thing. :-) We know in which direction we're moving, it'll just take a few more days. In the meanwhile I will make sure to make the TOC available on all pages for navigational reasons ;-) Per - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev]
Per Eriksson wrote: - snip - In the meanwhile I will make sure to make the TOC available on all pages for navigational reasons ;-) Hi, Per I added a link to your Building Guide to the Documentation page on the wiki [1]. We have some nice TOC templates (see the Basic Guide or Writer Guide, for example) which you are certainly welcome to use. Or, if you like, I can take a crack at it, though it probably won't be finished before tomorrow. [1] http://wiki.services.openoffice.org/wiki/Documentation Best wishes on the project! /tj/ -- - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Re: Consolidating build instructions for the community
Hi, I am looking at the instructions for Windows and is having the following thoughts: 1. http://wiki.services.openoffice.org/wiki/Windows#MinGW It says MinGW is not supported, but there are a number of referenced issues which have been integrated. What is the current status of using MinGW? Should it be included? 2. Is OOo completely buildable on Visual Studio 2008 or do we still need this note? Currently OOo isn't completely buildable with Visual Studio 2008 Express and Windows Server 2008 SDK due to missing ATL header / libs (these used to be shipped with the 2003 SDK, but the 2003 SDK cannot be used with VS2008). Setting DISABLE_ATL=TRUE after the configure step helps for building but disables Windows (not internal) OLE completely and some other functionality. Per - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Re: Consolidating build instructions for the community
Per Eriksson pisze: 2. Is OOo completely buildable on Visual Studio 2008 or do we still need this note? Currently OOo isn't completely buildable with Visual Studio 2008 Express and Windows Server 2008 SDK due to missing ATL header / libs (these used to be shipped with the 2003 SDK, but the 2003 SDK cannot be used with VS2008). Setting DISABLE_ATL=TRUE after the configure step helps for building but disables Windows (not internal) OLE completely and some other functionality. I think it's buildable - I built 3.0 with Visual Studio 2008 but I think I needed to patch some files. But I submitted them to IZ and they should be integrated. No idea if it's not broken now with 3.1, I didn't try building it. Regards Marcin - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Re: Consolidating build instructions for the community
Hi, Marcin Miłkowski skrev: Per Eriksson pisze: 2. Is OOo completely buildable on Visual Studio 2008 or do we still need this note? Currently OOo isn't completely buildable with Visual Studio 2008 Express and Windows Server 2008 SDK due to missing ATL header / libs (these used to be shipped with the 2003 SDK, but the 2003 SDK cannot be used with VS2008). Setting DISABLE_ATL=TRUE after the configure step helps for building but disables Windows (not internal) OLE completely and some other functionality. I think it's buildable - I built 3.0 with Visual Studio 2008 but I think I needed to patch some files. But I submitted them to IZ and they should be integrated. This is surely something we need to clearify. The instructions mention OOo 3.x together with MSVS 2008, so it looks to me like our recommended way. Per - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
[dev] Consolidating developer documentation
Hi List, While checking, sorting and refactoring stuff for the new building guide, I also ventured into our CVS/SCM/CWS docs. I merged/renamed some stuff, created redirects and tagged some stuff with categories (mostly development, SVN, SCM, CWS). However, there are quite some stuff that is really mixed up, for example infos about SCM-tooling, EIS-tooling and basic QA-workflow are distributed and mixed all over these pages (and some more): http://wiki.services.openoffice.org/wiki/CWS http://wiki.services.openoffice.org/wiki/ChildWorkSpace http://wiki.services.openoffice.org/wiki/EIS I think it would make sense to clearly separate: * cws, the command line tool * cws workflow for developers (including how to use EIS) ^- this one should be further reading in the Building Guide * cws workflow for QAs (inlcuding how to use EIS) (and getting rid of outdated/wrong stuff by the way) Also we need to clean up category:CWS: http://wiki.services.openoffice.org/wiki/Category:CWS Currently, it contains: * SCM tools usage (ok) * QA Policies (ok) * various QA stuff (Gatekeeper, RedTinderboxStatusInEIS) (meh) * QA Status Pages of some cws's (huh?) Im proposing to get rid of the CWS QA states at least (or move them to a new Category:CWSQAStatus). I think these pages (which _should_ be the first thing a contributor reads after having his build enviroment set) should be worth the effort. Comments? Have Fun, Bjoern - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] Re: Consolidating build instructions for the community
Per Eriksson wrote: 2. Is OOo completely buildable on Visual Studio 2008 or do we still need this note? Currently OOo isn't completely buildable with Visual Studio 2008 Express and Windows Server 2008 SDK due to missing ATL header / libs (these used to be shipped with the 2003 SDK, but the 2003 SDK cannot be used with VS2008). Setting DISABLE_ATL=TRUE after the configure step helps for building but disables Windows (not internal) OLE completely and some other functionality. I built early dev versions of 3.0 with Visual Studio 2008 (paid for version), but it did not build with Visual Studio 2008 Express (free version) for the reasons stated above. I suspect the situation is still the same as the problem is with missing compiler/sdk components that cannot be freely downloaded. William - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
