Re: [Discussion] Would we enable volunteers that develop extensions
Hi Jörg Overall I like your suggestion. Steve On 2/6/21 1:50 AM, Jörg Schmidt wrote: Hello, -Original Message- From: Steve Lubbs [mailto:stevelu...@gmail.com] Sent: Friday, February 05, 2021 9:54 PM To: dev@openoffice.apache.org Subject: Re: [Discussion] Would we enable volunteers that develop extensions Just a thought. As part of an effort to enable volunteer extension authors would it make sense to selectively approve extension functionality for inclusion into AOO on a case by case basis? If it provides a level of new functionality that is considered important and compelling, say something that is on the wish list and that no one has the time to pursue? For instance a PDF importer that was mentioned earlier. This is an interesting idea, which I had already mentioned myself (elsewhere). However, there is the experience of the past to consider, so that it is prevented that extensions, objectively as well as from subjective view of users, are regarded as emergency nail. It should not be allowed (technically) that AOO is delivered with an inflationary high number of _individual_ extensions, but there should be (also in view of the named purpose to transfer extension code later into core code) a kind of main extension as a container for the individual extensions, so that especially in the extension manager only the one main extension is visible. Of course, this requires some organization, i.e. that the extension programmers adhere to certain technical conditions, but this effort will pay off in the long run. As an experience value I can refer to the LiMux project (https://de.wikipedia.org/wiki/LiMux), in which I was involved professionally over many years, and was occupied there with the conversion of specialized applications and VBA macros to OOo extensions. At that time, there were very detailed specifications (size around 50 DIN-A4 pages) for the creation of extensions, which made integration into the overall project and maintenance much easier. Of course, we should be open to any programming languages within the extensions (there can also be so-called non-code extensions), but again I would like to mention: turning our gaze more towards Python would be quite beneficial, especially for extensions to be ported into the core code later. A step in this direction might be the development of an integrated Python IDE, parallel to the StarBasic IDE, in AOO. (I would like to emphasize that my personal Python knowledge is limited, so the above is not a personal preference, but a strategic consideration). With the author's permission and effort the extension could be ported to be core code rather than an extension. The author, upon agreeing to these conditions could be given the right of first refusal to be the maintainer of the code. There should also be a proviso that the author will to do the port. This, or some permutation, could be one way to reward extension authors for their efforts, provide incentive, I think it would also be a motivation to award membership in the PMC according to objective performance and not depending on the subjective opinion of individuals. greetings, Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Discussion] Would we enable volunteers that develop extensions
My concern is related to security. Consider a bad actor who creates an extension that, for instance, harvests personal info. It's one thing if they are listed on a web page. It's a completely different thing if they are sanctioned by the AOO project by being more tightly associated with the AOO project, say by being included in the build. Of course this is true of the project as it stands now. But the increased exposure of the AOO project and the potential for a black eye bears discussion. 2 cents. Steve On Mon, Feb 1, 2021, 5:06 PM Carl Marcum wrote: > Hi Peter, > > On 2/1/21 1:46 AM, Peter Kovacs wrote: > > I have a question. How much willing are we to support extensions. > I think for extensions like report builder where the code is donated and > it's a high-profile extension it makes sense. > Much more so if we build and bundle during a release. > > Freedom to do releases is another issue. If they're AOO sub-projects we > need to do the releases the same way as the Office and that can be > cumbersome for something as small as an extension when they are done > independently and frequently and most members may not have the > toolchains setup. > > I ran into this with things like the NetBeans plugin and some other > developer tools. > > I think for the same reason ASF wants a minimum number of developers for > a project, a lot of extensions are probably one or two developers and we > could end up with a lot of abandoned code. > > > > > I mean we have here a voice recognition questions, there is the > > reporting tool or wiki extension. > > > > We already thinking on creating repos for reporting tool or the wiki > > extensions. > > > > But how do we deal with those topics on the organisatorical level? > > > > Do we form I do not know how to name them, task force around them? Do > > the people who whish to be delevop these functions do this in an > > outside project (independant if this is a Apache project or github > > self sufficient hosted) > > > > > > I would opt that we agree on some form to enable volunteer to use the > > project infrastructure and provide them with a stronger feeling that > > they are part of the project even if they are only working on an > > extension of none core features. > > For most extensions I don't think this is necessary when they have > GitHub, Sourceforge, etc. > > > > > This makes it easier to bring the community together. I mean the > > wording 3rd parties bring a lot of discussion and the need to explain > > things, to the table. > > I think there are things we can do as a project to support a community > which we need to grow. > Some of which like forums and mailing lists we already do. > Extension developers are welcome on the dev@ list. > > There is an api@ list for that purpose but I thought it was shut down for > lack of traffic and I didn't subscribe anymore but I see there are a few > recent posts within the last year and almost no replies to them :( > > Jörg had some good points about Extension Manager support and other tools > for extensions and you may know I'm working on new extension creation tools > as well. We can also make sure the Developer Guide is up to date and > things like that. > > > > > > > I am just wondering what everyone else thinks. > > > > All the best > > > > Peter > > > > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
Re: OS2 code
Hi Marcus, How about something along the lines of: <<<<<<<< Begin Verbiage >>>>>>>> The following list of third-party ports and distributions is made available as a service to the community.The Apache OpenOffice project does not officially endorse or maintain these packages. If you have a port or distribution that you want to be listed here please send the details to our public mailing list <mailto:dev@openoffice.apache.org>. In some cases the Apache OpenOffice project may be able to cooperate with the a porting project. If you wish to discuss how the Apache OpenOffice project may be able to help with your port please check here: . <<<<<<<< End Verbiage >>>>>>>> Regards, Steve On 1/23/21 2:51 AM, Marcus wrote: Am 22.01.21 um 20:22 schrieb Steve Lubbs: Thanks Andrea for the additional clarification. I understand better now. As for gitbox link, I don't have visibility yet beyond the HEAD which is completely understandable. But I can see the list is long! Steve, after all this discussion, do you still see a need to improve the text on the webpage [1]? If so, do have maybe a suggestion what should be changed or added? [1] https://www.openoffice.org/porting/index.html Thanks Marcus On 1/20/21 3:49 PM, Andrea Pescetti wrote: On 18/01/2021 Steve Lubbs wrote: So it seems that OS2 is not supported by the AOO project. Correct. I assume that the AOO project is not updating the OS2 code. Wrong (well, kind of...). Yuri Dario is an Apache committer too; and we did incorporate the last changes he did into our source code; and if he contributes further changes, we will probably incorporate them again. Still, OS/2 is "unsupported" because we cannot guarantee official releases and testing coverage. There are other situations where this could happen. For example, we release ~40 languages but we have partial translations for many more, see https://gitbox.apache.org/repos/asf?p=openoffice.git;a=tree;f=extras/l10n/source;hb=HEAD and one might want to build and distribute OpenOffice in an "unsupported" language, which eventually can become "supported" if the person contributes back and helps complete the translation. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: OS2 code
Thanks Andrea for the additional clarification. I understand better now. As for gitbox link, I don't have visibility yet beyond the HEAD which is completely understandable. But I can see the list is long! Steve On 1/20/21 3:49 PM, Andrea Pescetti wrote: On 18/01/2021 Steve Lubbs wrote: So it seems that OS2 is not supported by the AOO project. Correct. I assume that the AOO project is not updating the OS2 code. Wrong (well, kind of...). Yuri Dario is an Apache committer too; and we did incorporate the last changes he did into our source code; and if he contributes further changes, we will probably incorporate them again. Still, OS/2 is "unsupported" because we cannot guarantee official releases and testing coverage. There are other situations where this could happen. For example, we release ~40 languages but we have partial translations for many more, see https://gitbox.apache.org/repos/asf?p=openoffice.git;a=tree;f=extras/l10n/source;hb=HEAD and one might want to build and distribute OpenOffice in an "unsupported" language, which eventually can become "supported" if the person contributes back and helps complete the translation. Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: OS2 code
On 1/18/21 6:03 PM, Peter Kovacs wrote: The Project does accept bug reports. And Code testing and bug fixing is done by bitworks. That's the part I was missing. Maybe it is that there is a Fuzziness on who is the Project? Who releases the Community binary version? Who releases the binary OS/2 Version and Who releases the Source Code? It is all a bit mixed or separated in a strange way. For a newbie, at least this one, that is so. Thanks for the clarification, Steve
Re: OS2 code
Hi Michael, Comments inline in red. On 1/18/21 2:03 AM, Dr. Michael Stehmann wrote: Hi, I think we have to differ between responsibility and merit and support. To my mind responsibility implies support. Support implies ongoing coding, testing, and bug fixing efforts involving not only the code but the build process. On the webpage we IMO have to clarify we are not responsible for the OS/2 port and the merits belong to others. I think that those points are made pretty well at the top of the page. But clarification is always good. But in our code we IMO should do what is in our potentials to support such a port. An argument can be made that to support implies, at a minimum, maintenance effort, as described above, on the part of the AOO project. As I understand it there has been no maintenance effort on the part of the AOO project for some time. Without any maintenance effort the code will inevitably become stale, including the build. Unfortunately the only way to determine this is to build it and test it which brings us back to some level of maintenance. So please keep the OS/2 code as far as it is usefull. Removing the OS2 code from future versions is not the same as making it unavailable. It will continue to be available in earlier versions. This can be elucidated on the porting page. Besides the points I've already made, keeping the OS2 code in the repository is confusing, especially to those new to the project as I am. I'm in the process of reverse engineering and documenting the design of the concurrency and threading in AOO so as to help myself and, in some small way those who follow, to understand the design of AOO. Believing OS2 to be currently supported I wasted time going down that rabbit hole. It was only when I happened to read the porting page that I realized that my efforts WRT OS2 were not warranted. If it happened to me it's bound to happen to others. :-\ The question I'm asking is, given the lack of responsibility and/or support by the AOO project for the OS2 code and the fact that we can easily inform anyone who is or will be involved in porting to OS2 (or any other formerly supported platforms) where the no longer supported code may be found, should we clean up the code base by removing the unsupported code from future versions? I wonder if, after the discussion is concluded there should be a(n) (in)formal policy or guidance for the future. Good discussion. Steve Kind regards Michael
Re: OS2 code
Hi Marcus, To begin with the use of the phrase "third-party port" in this context indicates to me that a coding/testing activity is required to support the target of the port which is not being done by the AOO project. Here are the statements on the page (that may need to be modified) that indicate to me that the AOO project does not currently support OS2. Bolded, underlined, and in red. ** _*Apache OpenOffice (AOO) is a productivity suite which is already *__*officially available for the following platforms <https://www.openoffice.org/download/>*__*: *_ _**_ * _*Windows - XP, Vista, 7, 8, 10 (32-bit)*_ * _*Linux - RPM / DEB-based (32-bit and 64-bit)*_ * _*MacOS X (Intel) - 10.4 (Tiger) up to 10.15 (Catalina)*_ ** This tells me that OS2 is not supported by the AOO project. ** ** Apache OpenOffice - Third-Party ports and distributions The following list of third-party ports and distributions is made available as a service to the community. _*The Apache OpenOffice project does not officially endorse or maintain these packages.*_ If you have a port or distribution that you want to be listed here please send the details to our public mailing list <mailto:dev@openoffice.apache.org>. ** This indicates to me that that ports to unsupported platforms are the responsibility of those engaging in the process of porting and that those third parties presumably outside of the AOO project. ** ** * Apache OpenOffice for OS/2 <https://www.bitwiseworks.com/news/#122020> _*A port to *__*OS/2 <https://www.arcanoae.com/>*__*by *__*Yuri Dario <mailto:ydario(a)apache.org>*__*and *__*bww bitwise works GmbH <https://www.bitwiseworks.com/>*__*. *_ ** This tells who the third party doing the port is. ** So it seems that OS2 is not supported by the AOO project. I assume that the AOO project is not updating the OS2 code. So a porting organization would need to make changes to the OS2 code that existed at the time OS2 was last supported. It would make sense then that they would have their own forked instance of the OS2 code that they were updating as changes to the non-OS2 code occurred. So, OS2 is not supported by the AOO project and the code required to support a port is available in earlier versions of the AOO code. This is my reasoning. I'm just wondering if the AOO team should consider performing a cleanup of code that is unused by the project. Of course it's true that I don't know if any policy covers this. That's why I'm asking. On 1/10/21 7:29 AM, Marcus wrote: Steve, when you think that the text on [1] leads to the impression that AOO for OS/2 is dead maybe something with the wording is wrong. So, please let us rethink to update the webpage to eleminate this impression. [1] https://www.openoffice.org/porting/index.html Thanks Marcus Am 10.01.21 um 01:25 schrieb Steve Lubbs: Thanks for correcting me. :-[ On 1/9/21 3:43 PM, Matthias Seidel wrote: Where did you get the idea from? ;-) AOO 4.1.8 is released for OS/2 and OS/2 based systems: https://www.bitwiseworks.com/products/ports.php#AOO I am running it in a VM on ArcaOS 5. https://www.arcanoae.com/ Am 09.01.21 um 23:40 schrieb Steve Lubbs: According to this page, https://www.openoffice.org/porting/index.html, OS2 is no longer supported. Isn't it time we remove the OS2-specific code from the code base? BTW, OS2 was my favorite OS back in the day. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: OS2 code
Thanks for correcting me. :-[ On 1/9/21 3:43 PM, Matthias Seidel wrote: Hi Steve, Where did you get the idea from? ;-) AOO 4.1.8 is released for OS/2 and OS/2 based systems: https://www.bitwiseworks.com/products/ports.php#AOO I am running it in a VM on ArcaOS 5. https://www.arcanoae.com/ Regards, Matthias Am 09.01.21 um 23:40 schrieb Steve Lubbs: According to this page, https://www.openoffice.org/porting/index.html, OS2 is no longer supported. Isn't it time we remove the OS2-specific code from the code base? BTW, OS2 was my favorite OS back in the day. Steve Lubbs
OS2 code
According to this page, https://www.openoffice.org/porting/index.html, OS2 is no longer supported. Isn't it time we remove the OS2-specific code from the code base? BTW, OS2 was my favorite OS back in the day. Steve Lubbs
Re: Documenting what I'm learning
Thanks Patricia. From my former life I have a pretty good background in threading and concurrency myself. What I'm doing currently is chasing down who's doing what and where they're doing it WRT concurrency and threading, documenting in UML as I go. I won't hesitate to reach out to you if I feel can use some help. Thanks, Steve On 1/3/21 4:20 PM, Patricia Shanahan wrote: Health permitting I may be able to help with this. I used to help develop, test, and debug multiprocessor servers so I have spent a lot of time thinking about concurrency correctness and performance. Patricia On Dec 30, 2020, at 17:02, Steve Lubbs wrote: Hi All, I've been spending quite a bit of time reverse engineering the threading and concurrency implementation and with an eye towards possible errors. I'm documenting what I find as I go with the hope that it'll be useful to others as well as myself. I'm not a UML expert by a long shot but I think I can use it well enough so it'll be useful. So if you don't here from me for a while it's not because I've left. I just have my head down. BTW, I'm going to see if Umbrello is useful for this. Steve Lubbs - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Documenting what I'm learning
Hi All, I've been spending quite a bit of time reverse engineering the threading and concurrency implementation and with an eye towards possible errors. I'm documenting what I find as I go with the hope that it'll be useful to others as well as myself. I'm not a UML expert by a long shot but I think I can use it well enough so it'll be useful. So if you don't here from me for a while it's not because I've left. I just have my head down. BTW, I'm going to see if Umbrello is useful for this. Steve Lubbs
Re: Big Sur 4.1.x core dumps
Hi Jim, There are professional, non-trivial Native OSX apps that don't run on Big Sur. For Instance Quark is one of them and it has no compatible version currently (well, as of about a month ago). We had to create another bootable partition to go back to Catalina so my wife could work. She is a graphic artist doing page layout for a small local news paper. She has had enough and is now moving to InDesign. We also had problems when we moved to Catalina from several versions back. Had to replace most of her professional software. The problem may be incompatibilities in the third party software such as boost, Java, and/or underlying OSX provided interfaces, etc. I don't know if the build rebuilds all the the third party software. The libraries such as boost (or AOO) may be using deprecated APIsand may not be checkingreturn codes/exceptions appropriately in the libraries or in AOO code. Another possibility, from what I've read in the past Apple has let some deprecated APIs fail silently in the past. OSX has apparently changed enough that they have moved the designation from OSX to OS11. The problem may be deeper than just the AOO code. Big Sur XCode 12 is the current version for OS11. Was AOO 4.2.0 built with this? BTW, this version builds universal apps by default which should make porting to OS11 and Apple Silicon much easier in the short term. Another question just occurred to me. Are the versions of the Java JDK the same for both builds and is the same JRE used at runtime? Just my long 2 cents. Enough rambling on, Steve Lubbs On 12/26/20 10:19 AM, Jim Jagielski wrote: I've confirmed that my 4.2.0 builds work fine on BigSur but the 4.1.8 builds, even using Xcode10 and the 10.13SDK still result in core on macOS11. Below you'll find the stack. My initial thoughts are that it is NOT a build issue, but rather a code one, so I'll start some investigation with that mindset and especially look at the diffs between AOO418 and AOO42X that might be key. Time Awake Since Boot: 1000 seconds System Integrity Protection: enabled Crashed Thread:0 Dispatch queue: com.apple.main-thread Exception Type:EXC_BAD_ACCESS (SIGSEGV) Exception Codes: KERN_INVALID_ADDRESS at 0x0009 Exception Note:EXC_CORPSE_NOTIFY Termination Signal:Segmentation fault: 11 Termination Reason:Namespace SIGNAL, Code 0xb Terminating Process: exc handler [1770] VM Regions Near 0x9: --> __TEXT 10d063000-10d064000[4K] r-x/rwx SM=COW /Applications/OpenOffice-4.1.8.app/Contents/MacOS/soffice Application Specific Information: ViewBridge hint(s): ( "bridge key: delegateInvocation" ) Thread 0 Crashed:: Dispatch queue: com.apple.main-thread 0 libs5abi_uno.dylib 0x0001162d7259 s5abi::fillUnoException(s5abi::__cxa_exception*, _uno_Any*, _uno_Mapping*) + 41 1 libs5abi_uno.dylib 0x0001162d98bd 0x1162d5000 + 18621 2 libs5abi_uno.dylib 0x0001162d8e40 bridges::cpp_uno::shared::unoInterfaceProxyDispatch(_uno_Interface*, _typelib_TypeDescription const*, void*, void**, _uno_Any**) + 736 3 libuno_cppuhelpers5abi.dylib.3 0x00010d4cd688 cppu::getCaughtException() + 840 4 libxstor.dylib 0x00013868d104 OStorage::hasByName(rtl::OUString const&) + 964 5 libxo.dylib 0x000111d4b222 XMLVersionListPersistence::load(com::sun::star::uno::Reference const&) + 322 6 libxo.dylib 0x000111d4b9be non-virtual thunk to XMLVersionListPersistence::load(com::sun::star::uno::Reference const&) + 14 7 libsfx.dylib0x00010d807fcf SfxMedium::GetVersionList(com::sun::star::uno::Reference const&) + 271 8 libsfx.dylib0x00010d787753 sfx2::FileDialogHelper_Impl::updateVersions() + 547 9 libsfx.dylib0x00010d795afd sfx2::FileDialogHelper::FileSelectionChanged(com::sun::star::ui::dialogs::FilePickerEvent const&) + 29 10 libsfx.dylib0x00010d78715d sfx2::FileDialogHelper_Impl::fileSelectionChanged(com::sun::star::ui::dialogs::FilePickerEvent const&) + 45 11 fps_aqua.uno.dylib 0x0001429242a0 0x142917000 + 53920 12 com.apple.AppKit0x7fff236752f5 -[NSSavePanel observeValueForKeyPath:ofObject:change:context:] + 562 13 com.apple.Foundation0x7fff2119bab8 NSKeyValueNotifyObserver + 327 14 com.apple.Foundation0x7fff21262e45 NSKeyValueDidChange + 431 15 com.apple.Foundation0x7fff21303539 NSKeyValueDidChangeWithPerThreadPendingNotifications + 146 16 com.apple.ViewBridge0x7fff2703dd9b __41-[NSViewBridge setObject:forKey:withKVO:]_block_invoke + 360 17 com.apple.ViewBridge0x7fff270b8829 withHintInPro
Re: Apple Dumping Intel.
Yes, that will stave off the inevitable for a while but, correct me if I'm wrong, that support wasn't available for all that long in the scheme of things. Either way it does give us some breathing room. On 12/23/20 1:42 PM, Jim Jagielski wrote: Yes, all this is very similar when Apple moved from the PowerPC to Intel, many many moons ago. In fact, there was a time when you could have *3* versions: x86 32bit, PowerPC, and x86-64 64bit, all in 1 single bundle/binary. On Dec 23, 2020, at 2:00 PM, Matthias Seidel wrote: Hi Steve, Am 22.12.20 um 02:33 schrieb Steve Lubbs: Has there been any thought given to moving/creating an OSX port to Apple's up coming Apple Silicon RISC CPU? Disclaimer: I am not a developer nor do I own a mac... ;-) But what I understand is that Apple lets you compile the code into a "Universal Binary". That UB does contain the code for Intel *and* ARM. It will only install the native version depending on the platform. Advantage: We only need to provide one package for both systems. The downside would be the increased size of the downloadable binary. That said, I don't know how difficult that process will be... Regards, Matthias Steve - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Apple Dumping Intel.
Has there been any thought given to moving/creating an OSX port to Apple's up coming Apple Silicon RISC CPU? Steve
Re: Apple Developer Program
On 12/20/20 12:50 AM, Peter Kovacs wrote: On 20.12.20 01:37, Steve Lubbs wrote: Do we have any access to the Apple Developer Program? Sure would be handy. I think we have access. Can anyone provide the particulars of how to use the Apple Developer Program, assuming we have a membership? I have looked into into it and I could join as an individual for $99.00 but I'd rather not have to. Also if I join as an individual member I don't know if I'd allowed to use it to contribute to the project. I noted that one type of license is for non-profits.
Apple Developer Program
Do we have any access to the Apple Developer Program? Sure would be handy. Steve
Where I think I'll be of the most use.
After spending a few hours poking around I have some ideas on where I can make the biggest impact given my background. Multi-threading/Concurrency: This is one of my bailiwicks. Correct me if I'm wrong but it appears that concurrency support was removed when Mac OSX dropped support for standard concurrency APIs. I saw that all the concurrency APIs were gutted in semaphore.h and mutex.h. Unfortunately replacing them with the OSX GCD (Grand Central Dispatcher, how cute) and dispatch queues won't fill the porting bill. I would like to look into ways to implement semaphores, mutexes,etc. so we can fill this gap. Might still be able to use dispatch queues for threading. I have a pretty good background in threading and concurrency. For example, way back I needed to port some threaded unix code to an OS that had no support for threads or concurrency so implemented my own light-weight threads and concurrency primitives. For atomic operations I used a assembly-level compare and increment command. I was so proud of it I started writing an article for Dr. Dobbs, a big programming mag at the time. While I was so engaged, someone else beat me to the punch. Rats. Architecture Documentation: It appears to be in need of major updating. I haven't seen anything updated in the last 10 years. I would like to update it as much as I can, at least WRT the modules I touch. What do you think? Sorry for bloviating. BTW, this is fun. Steve
Re: Design Docs?
Thanks Dick. That does help, even if it's a little outdated. Every little bit helps. On 12/19/20 3:48 AM, Dick Groskamp wrote: On 2020/12/19 01:06:29, Steve Lubbs wrote: Hi All, I asked this question in recruitment but this may be the proper place for it. Is there any design documentation, especially related to structure (what are the modules, what is their function, how do they interact, etc.), however minimal, that you can point me to to help in wading through the code? I'm hoping to avoid reverse engineering the code. If the answer to my query is available somewhere I should have seen it, I apologize. Thanks in advance, Steve Lubbs Would this be of any help ? https://www.openoffice.org/marketing/ooocon2006/presentations/tuesday_d2.pdf - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Design Docs?
Hi All, I asked this question in recruitment but this may be the proper place for it. Is there any design documentation, especially related to structure (what are the modules, what is their function, how do they interact, etc.), however minimal, that you can point me to to help in wading through the code? I'm hoping to avoid reverse engineering the code. If the answer to my query is available somewhere I should have seen it, I apologize. Thanks in advance, Steve Lubbs
