Re: Release Manager for 4.1.2
I agree. +1 and go ahead :) On 06.07.2015 09:35, jan i wrote: On Monday, July 6, 2015, Andrea Pescetti pesce...@apache.org wrote: On 24/06/2015 Andrea Pescetti wrote: I can volunteer as Release Manager for 4.1.2. Of course, if anybody else is available to do it, please speak up! So, judging from the feedback, we have several +1s and no other volunteers available for the task. I obviously can't fulfill the role completely ... a limited Release Manager like I could be is probably better than nothing if we want to make 4.1.2 a reality. This paragraph was written in a confusing way. Let me restate it so that there is no possible confusion: - I volunteer as Release Manager for the 4.1.2 release (a Release Manager is always for a specific release; this says nothing about the future). - By limited I simply meant that I won't do all the work alone; this is an accordance with the Release Manager role, a release is the work of a community and not of an individual. - I plan to fully respect the role of Release Manager as described in http://www.apache.org/dev/release-publishing.html#release_manager Shall we start a [VOTE]? Shall we need further discussion? Shall we simply go forward? Up to you. I dont think we need a vote, we have consensus, nobody said anything against you volunteering. Gratulations on your new role. We need to find out fir which parts you need what type of help. rgds jan i Regards, Andrea. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [DISCUSS] Qt as a replacement for VCL
This approach would mean that you mostly don't use Qt at all. VCL uses SAL to get a top level window from the os, and then renders all widgets on it's own. Using Qt simply as yet an other SAL implementation would mean that you still only get the top level window (via Qt then), but widget rendering wouldn't change. Really using Qt would probably be a quite huge effort. Malte. On 18.01.2015 19:41, Fernando Cassia wrote: On Sun, Jan 18, 2015 at 12:43 PM, Yuri Dario mc6...@mclink.it wrote: having written or updated most of the OS/2 code in VCL project, I have some experience with it. I'm not enterint the debate QT-yes/QT-no, I will only offer a developer point of view. We can simply use QT like an existing operanting system API, like OS/2 PM or windows GDI/windowing. As we create a window using the os native api, we can also create a window using QT API. Same for drawing, printing, etc... So, what you suggest is actually a VCL-to-QT bridge. If that is actually doable, technically speaking, that sounds like a good FOSS project to start on its own. Don´t restrict it to the realm of AOO, make it a separate endeavour then it can be used in AOO. Just saying... don´t restrict the mindshare and reach of the project to AOO, make it as wide and far-reaching as possible. FC - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: StarWriter for DOS needed
Funny to hear that Marco still uses t3killer :) T3 was Microsoft's code name for the 3rd version of Word for Windows. We planned to release StarWriter for Windows 1.0 in the same year, for a much lower price, so that was intended to be the T3-Killer :D We even wore T3-Killer sweatshirts with a picture and the price of the StarWriter box on it, when we all drove to CeBIT that year... On 30.06.2015 22:05, Fernando Cassia wrote: On Tue, Jun 30, 2015 at 8:40 AM, Jan Eric Hogh jan.h...@outrange.de wrote: I recently registered at the OO-forum and asked if someone could send me a download link for this really old piece of software (StarWriter for DOS, may also be called StarWriter compact 2.0 for DOS). One of the moderators told me to email the developer list, because he is sure that someone there has an archive of old versions. The founder of Stardivision Gmbh,Marco Boerries is on Twitter, and very approacheable. @t3killer https://twitter.com/t3killer https://twitter.com/t3killer I suggest you contact him. I´m sure he could donate a copy of that abandoned software to The Internet Archive (Archive.org), for historical reasons... FC - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: 2015 -- Our 30th Anniversary
Hi Louis, On 28.10.2014 21:12, Louis Suárez-Potts wrote: Hi Malte, And you are right wrt many early developers working for Open-Xchange now :) Yes, and perhaps one day we’ll even see something (I joke; there is already something). Actually everyone can look at the demo version of App Suite, including OX Text and OX Spreadsheet: http://www.open-xchange.com/demo Same focus - Office productivity, ODF and OOXML. Hm. You might want to share with us what’s going on over there…. See below :) Just different technology - now written for the browser. Right. Can you edit in the browser? I mean, edit ODF or OOXML docs. using, for instance, Chrome or Firefox or Safari? Exactly. ODF and OOXML are our natively supported formats that we can edit in the browser. Text and Spreadsheet are already available. We work on the documents very different compared to Open Office or MS Office. One of our most important features is the document roundtrip. You can safely switch between editing with OX Documents and editing with your native application. And we have real-time communication to quickly distribute changes to other clients. I just wrote a blog post that explains the technical details how we achieve it. http://techblog.open-xchange.com/2014/11/13/ox-documents-roundtrip-and-operations/ Best regards Malte. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: 2015 -- Our 30th Anniversary
Hi Louis, I am not interested in being interviewed in a podcast, but if you have specific questions, just let me know. Private email to my web.de account, as I don't follow the mails on the AOO/LO lists on a regular base, except for the security lists. And you are right wrt many early developers working for Open-Xchange now :) We are 14(!) former colleagues from Sun's OpenOffice.org.team. 12 of them even already worked for StarDivision. Same focus - Office productivity, ODF and OOXML. Just different technology - now written for the browser. Best regards Malte. On 27.10.2014 19:57, Louis Suárez-Potts wrote: Malte! So, you do realize this is probably one of the very very few witness accounts we have of the origins of StarOffice? (later OpenOffice) ... and if you were to consent to writing more--or being interviewed in a podcast for more--we, or at least I, would be grateful... and better informed of that application that has so formed my adult life. best louis On 27 October 2014 14:53, Malte Timmermann malte_timmerm...@gmx.com wrote: Honestly, I don't agree on 30th Anniversary, but see 2015 as 25th Anniversary. StarWriter for text screens was written in Lueneburg near Hamburg. In Pascal. By people which later didn't work on StarWriter for Windows. In 1990, Marco started the new StarDivision location in Hamburg. StarWriter for GUI systems to be developed from scratch. Written in C++. By completely different people. When I started there in 1991, there was only a Writer prototype, as we also needed to first develop StarView, the class library for abstracting from Windows, OS/2, Mac and Unix Motif. Yes, there was a StarWriter Mac version in the beginning, long before it was canceled, and many years went by before there was one again! The concept of StarView was to create native system widgets for their corresponding components. As this approach lead to different issues, and not all systems had the same set of widgets, we later replaced StarView with VCL, as you know it today. First versions of StarOffice for Windows contained Calc and Draw developed outside from StarDivision, both using their own technology stack. Iirc, StarOffice 3.0 was the first version of the suite with all components based on StarView. The English Wiki referenced page below is misleading wrt versions. There also was a StarWriter 1.0 for Windows, many years after StarWriter 1.0 for DOS (which already was available in version 6 then). The version history is much better documented on the German Wiki page: http://de.wikipedia.org/wiki/StarOffice Just some historical data :) Best regards Malte. On 24.10.2014 17:25, Rob Weir wrote: On Fri, Oct 24, 2014 at 11:15 AM, Roberto Galoppini roberto.galopp...@gmail.com wrote: 2014-10-24 16:41 GMT+02:00 Rob Weir r...@robweir.com: Those who know the history know that Apache OpenOffice is the continuation of the OpenOffice.org project, which itself came from a proprietary suite developed in Germany called StarOffice, which itself started as StarWriter, an application written in 1985 by Marco Börries . So next year, in 2015, will be our 30th anniversary. Any ideas what we might do? For example, does anyone still have a Zilog Z80 (or an emulator) that can run the original StarWriter? I'm still a proud owner of a ZX Spectrum Sinclair 48k, never heard about a StarWriter app, though. Does it exist, ideas about to get it? Cool! This is from Wikipedia: http://en.wikipedia.org/wiki/StarOffice#History It references a page on our wiki that claims StarWriter 1.0 was released in 1985. No idea where to get the code. Maybe Juergen or another old-timer would have a clue for us? -Rob Roberto It looks like some emulators here: http://www.z80.info/z80emu.htm#EMU_CPU_W32 It might be interesting to show the history of Writer, from release to release, via a set of screen shots (or a movie) showing the evolution of the UI. Regards, -Rob - To unsubscribe, e-mail: marketing-unsubscr...@openoffice.apache.org For additional commands, e-mail: marketing-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: marketing-unsubscr...@openoffice.apache.org For additional commands, e-mail: marketing-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Open-Xchange to launch open-source, browser-based office suite
Next fix here :) https://issues.apache.org/ooo/show_bug.cgi?id=121975 Malte. On 28.03.2013 14:49, Malte Timmermann wrote: Hi Andrea, On 27.03.2013 18:27, Andrea Pescetti wrote: Malte Timmermann wrote: for converting different kinds of documents, we make use of OOo in the backend. We found and fixed some issues, and are contributing back the patches... Good news! Whatever way you decide to use to contribute patches (you already have committer access to the OpenOffice repository, after all) please sent a short note here when you do, or tag issues appropriately in Bugzilla, so that we can properly acknowledge work by the Open-Xchange project in the OpenOffice release notes and/or similar documents. In our team, Sven Jacobi is taking care for contributing our patches to AOO and LO. One patch is attached to https://issues.apache.org/ooo/show_bug.cgi?id=121803 Two more to come soon. He also had provided some security fixes (some time ago) - they had been handled by security team, not via public patches, of course. Best regards Malte. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Open-Xchange to launch open-source, browser-based office suite
On 24.03.2013 18:29, Rob Weir wrote: On Sat, Mar 23, 2013 at 3:14 PM, Louis Suárez-Potts lui...@gmail.com wrote: No doubt many here have already noted this: https://www.infoworld.com/d/cloud-computing/open-xchange-launch-open-source-browser-based-office-suite-214882 It's interesting. One could hope for possibilities of collaboration, license permitting. Our code is free for anyone to use, under a permissive license. But it is not clear to me that our code would be particularly useful to them. For OX Text, we actually can't use any code of OOo... But for converting different kinds of documents, we make use of OOo in the backend. We found and fixed some issues, and are contributing back the patches... Malte. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Open-Xchange to launch open-source, browser-based office suite
Hi Louis, On 24.03.2013 00:38, Louis Suárez-Potts wrote: On 13-03-23, at 19:11 , Dennis E. Hamilton dennis.hamil...@acm.org wrote: The server is GPL and the JavaScripts that run in clients, Outlook, etc., are Creative Commons attribution-share-alike-noncommercial. None of that is Apache friendly. Indeed; hence my wistful hope. More information: http://en.wikipedia.org/wiki/Open-Xchange. The licenses apply to different parts of the code base. From this http://www.linkedin.com/company/open-xchange?trk=prof-following-company-logo I notice that Martin Holmichel is Senior Product Manager and that Malte Timmerman is Head of Development in Hamburg. Quite. I am indeed sorry that both Malte and Martin chose this path but it's quite possible they chose wisely—let's see. Assuming that you talk about working for Open-Xchange now (instead of staying full time OOo contributors), and not about the choice of licenses (which OX is using for many years now): I guess most people here know that we didn't chose to stop working on OOo full time, but that it was purely Oracle's decisions to - let's put it this way - not to have an OOo team anymore... And believe me - with working for Open-Xchange now, Malte and Martin did choose wisely :) Like did the many other people from the former Sun/Oracle OpenOffice.org team, who now work in the OX Hamburg team too. Actually, these people make up a 100% of the Hamburg team. OX launched the Hamburg site just for/with us. OX is a nice place to work. Nice people, great product. Open Source for a long time, now also with office productivity. Afterwards, everybody here is happy that Oracle gave us the opportunity to work for Open-Xchange on OX Documents now - nobody is looking back. Malte. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [CODE][PROPOSAL]: AOO 4.0 getting rid of the 3 layer office, part 1
Didn't read all the replies, but anyway: +1. Also good for startup-performance, if I remember correctly... On 22.03.2013 17:15, Jürgen Schmidt wrote: Hi, the so called 3layer office is not really useful anymore (it was never) and makes more problems than it helps. I thought that AOO 4.0 would be the best time to start at least with the necessary rework. The main idea is to use a new simplified directory layout and tweak the necessary config file (*rc, *.ini), rpath or similar linker flags where necessary etc. Eliminate the URE completely because we don't really want support it as a standalone product. I did some initial work so far and I am now able to build an office for Windows, MacOS and Linux with a new simplified directory layout. Windows and MacOS have already one main directory whereas on Linux we have openoffice (basis layer + URE) and openoffice4 (brand layer). I removed all this base-link, ure-link, URE, urelib stuff and reorganized the directories. Example layout on Linux: openoffice4 openoffice4/help openoffice4/presets openoffice4/program - contains basis-link/program + URE/bin + URE/lib openoffice4/program/misc - former URE/share/misc - will be removed openoffice4/README openoffice4/README.html openoffice4/readmes openoffice4/share In general the layout becomes more equal on all platforms. The good news is that the office work on all 3 platforms, I am able to select Java, extensions seems to work as well. Python is not yet tested, language packs are not yet tested and built but in general I am thinking it will be no problem. Advantage of this move would be a simplified structure, long term a simplified configuration when the *rc/*.ini files are consolidated. Easier deployment on Linux, no conflicts with an URE from LO or the distro at all. My idea is to continue this basic work, do further cleanup in the office as well as the build system, do further testing including the SDK... Still some work to do but from my point of view a useful move forward to get rid of this complex and unnecessary 3layer stuff. What do you think? On demand I can provide test builds if there are people interested to help with testing. Juergen - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
