Re: Proposal: OpenOffice screenshots for publicity
Am Freitag, 15. März 2013 um 00:50 schrieb Rob Weir: On Thu, Mar 14, 2013 at 7:02 PM, Kay Schenk kay.sch...@gmail.com wrote: On Thu, Mar 14, 2013 at 1:31 PM, Rob Weir robw...@apache.org wrote: On Wed, Mar 13, 2013 at 7:39 PM, Kay Schenk kay.sch...@gmail.com wrote: On Sun, Mar 10, 2013 at 8:06 AM, Rob Weir robw...@apache.org wrote: The PMC receives requests, every couple of weeks, from book publishers for permission to use OpenOffice screenshots in a book. Most often they are asking to use a specific screenshot from the website that they have identified, such as: http://www.openoffice.org/product/pix/writer-big.png Generally, Apache permits the use of product screenshots in books, per the trademark policy here: http://www.apache.org/foundation/marks/faq/#insidebook However, that only covers the trademark. There is another rights owner to consider, the author of the document included in the screenshot, including any text, graphics, images, etc., displayed. Of course, the book publisher can avoid that issue by making their own screenshots. But that is extra work. Generally they are trying to clear permissions for dozens or hundreds of images. The more difficult we make it, the less likely they are use it. Since this is free publicity for us, we should try to make it easy for them to use. Another issue is that our posted screenshots are quite old. They don't reflect the new Apache branding. Here's how we can do better: 1) Create a set of demo documents that showcase the capabilities of OpenOffice. Use either public-domain text (Charles Dickens, for examples) or Loren Ipsum, or original text contributed to the project under ALv2 by the original authors. We want documents, for all of our applications. that look good, and are clearly under ALv2. Multilingual text would be ideal, or separate documents for different languages. (We do get requests from book publishers in many countries, so having a native-language screenshot is ideal) 2) Create screenshots for each document, on each platform Do it with AOO 3.4.1 for now. But plan on repeating with each major new release. Agree on screen resolutions, color depth, and image formats, so we have uniformity. 3) Host the screenshots online, along with text that explains their purpose and permissions. What do we think? I can help with the webpage and with screen shots on Windows. But I'll need help assembling a set of showcase demo files. Note: aside from book publishers, this will also be useful for journalists who want a screenshot for an article. -Rob I thought I remembered seeing a screenshot area on the web site once upon a time, and here it is: http://www.openoffice.org/screenshots/ OK. That's the idea, certainly. I see variations for different languages there as well. But it is all very old, some of the screenshots from 2003, 10 years old! yes...I just wanted to point this out basically. It took me a while to track this down though -- there's a link in the marketing area which needs to be fixed to get you to this older area. Originating from: http://www.openoffice.org/marketing/marketing_where.html I fixed that link. Anyway, these are not standard by any means, but worth taking a look at I suppose. Also NO mention of specific license which would need to be included, etc. So, there is certainly a precedent for these. yes, we should update this area. Maybe a short blog for this kind of request? That's one approach. Ask for cool looking documents. Another would be to make our own, based on a theme. For example, we could pick some text, something classic, in the public domain, H.G. Wells, or Dickens, but something appropriate to openness, sharing, or other open source themes. Then use that text as a common element of our sample documents. And then make the sample documents look good. The common works are a great idea! A quick prototype: http://www.robweir.com/screenshot.png Nothing fancy -- but it is based on public domain content. Could probably be improved, like with a border around the image, etc. would it make sense to view the plugged navigator and stylist. For 4.0 of course the sidebar. Juergen -Rob This could work in Writer and Impress, where it is easy to put a quote. But not sure what to do about Calc... unless you make a chart of four score and seven years ago ;-) I'm sure with a little effort we could find something for Calc. State budgets? Other publicly available expenditures? These kinds of
Re: PropertyChangeListener
Hi Антон,
On Fri, Mar 15, 2013 at 02:51:26AM +0400, Антон Борисов wrote:
Why this listener don't work for ConnectorShape's properties StartShape
EndShape?
the base class of all shapes has an empty implementation
http://opengrok.adfinis-sygroup.org/source/xref/aoo-trunk/main/svx/source/unodraw/unoshape.cxx#2054
you'll find this in several places, for example
https://issues.apache.org/ooo/show_bug.cgi?id=121263
I'm not sure if this is for performance issues, or simply a bug. I'm not
aware of this being reported, so please open a new bug, this will help
improve the API.
So is there exists workaround?
add an old css::document::XEventListener at the document model, you'll
get notified of ShapeModified event, EventObject.Source is the shape;
something like the attached source.
Regards
--
Ariel Constenla-Haile
La Plata, Argentina
/
*
* Licensed to the Apache Software Foundation (ASF) under one or more
* contributor license agreements. See the NOTICE file distributed with this
* work for additional information regarding copyright ownership. The ASF
* licenses this file to you under the Apache License, Version 2.0 (the
* License); you may not use this file except in compliance with the License.
* You may obtain a copy of the License at
*
* http://www.apache.org/licenses/LICENSE-2.0
*
* Unless required by applicable law or agreed to in writing, software
* distributed under the License is distributed on an AS IS BASIS, WITHOUT
* WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the
* License for the specific language governing permissions and limitations under
* the License.
*
*/
package com.example;
import com.sun.star.beans.PropertyValue;
import com.sun.star.beans.UnknownPropertyException;
import com.sun.star.beans.XPropertySet;
import com.sun.star.comp.helper.Bootstrap;
import com.sun.star.document.DocumentEvent;
import com.sun.star.document.XDocumentEventBroadcaster;
import com.sun.star.document.XDocumentEventListener;
import com.sun.star.document.XEventBroadcaster;
import com.sun.star.document.XEventListener;
import com.sun.star.drawing.XConnectorShape;
import com.sun.star.drawing.XShape;
import com.sun.star.frame.FrameSearchFlag;
import com.sun.star.frame.XComponentLoader;
import com.sun.star.lang.EventObject;
import com.sun.star.lang.WrappedTargetException;
import com.sun.star.lang.XComponent;
import com.sun.star.lang.XServiceInfo;
import com.sun.star.uno.Exception;
import com.sun.star.uno.UnoRuntime;
import com.sun.star.uno.XComponentContext;
import java.io.BufferedReader;
import java.io.InputStreamReader;
import java.util.HashMap;
import java.util.logging.Level;
import java.util.logging.Logger;
/**
*
* @author ariel
*/
public class ConnectorShapeListener {
private final XComponentContext m_xContext;
private DocumentListener maListener;
private XDocumentEventBroadcaster m_xNewBroadcaster;
private XEventBroadcaster m_xOldBroadcaster;
private ConnectorShapeListener(XComponentContext xContext) {
m_xContext = xContext;
}
private void runDemo() throws Exception {
XComponentLoader xLoader = UnoRuntime.queryInterface(
XComponentLoader.class,
m_xContext.getServiceManager().createInstanceWithContext(
com.sun.star.frame.Desktop, m_xContext));
XComponent xDoc = UnoRuntime.queryInterface(
XComponent.class,
xLoader.loadComponentFromURL(
private:factory/sdraw, _default,
FrameSearchFlag.ALL, new PropertyValue[]{}));
m_xNewBroadcaster =
UnoRuntime.queryInterface(XDocumentEventBroadcaster.class, xDoc);
m_xOldBroadcaster = UnoRuntime.queryInterface(XEventBroadcaster.class,
xDoc);
maListener = new DocumentListener();
if (m_xNewBroadcaster != null) {
m_xNewBroadcaster.addDocumentEventListener(maListener);
}
if (m_xOldBroadcaster != null) {
m_xOldBroadcaster.addEventListener(maListener);
}
}
private void finishDemo() {
if (m_xNewBroadcaster != null) {
m_xNewBroadcaster.removeDocumentEventListener(maListener);
}
if (m_xOldBroadcaster != null) {
m_xOldBroadcaster.removeEventListener(maListener);
}
}
private class DocumentListener implements XDocumentEventListener,
XEventListener {
private final HashMap XConnectorShape, ConnectorShapes
maConnectorsMap = new HashMapXConnectorShape, ConnectorShapes();
private class ConnectorShapes {
private XPropertySet mxConnector;
private XShape mxStart;
private XShape mxEnd;
private ConnectorShapes(XConnectorShape xShape) {
try {
mxConnector = UnoRuntime.queryInterface(XPropertySet.class,
xShape);
Re: ping
Am 15.03.2013 03:51, schrieb Alexandro Colorado: ping.. pong signature.asc Description: OpenPGP digital signature
Re: AOO logo for special purposes?
We've done some special logo variation. For example, Drew made the Get it here logo: http://openoffice.apache.org/get-it-here.html yes, I know From a trademark perspective, this can be a good idea to keep the original logo for use only in the product and the website, but then create special, but related logos for other things. Yes. My concern at the moment is a first AOO-pin, because I always had an OpenOffice.org pin. An Apache-pin (eg http://shop.kernelconcepts.de/images/apache-pin.jpg) advertises not accurate enough for AOO. (Also, I think there are more graphics people on the marketing list, so you might want to ask the same question there) OK, I'll do that, I need only register there first. Greetings, Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Call-for-Review] code changes for more powerful smarttag extensions
On Wed, Mar 13, 2013 at 02:30:26PM +0100, Jürgen Schmidt wrote: - a missing include of XInterface in the new IDL XMarkingAccess.idl, IDL compile error on Mac, surprising that it worked for you This is a bug, the one that removed the need for explicitly inheriting from XInterface should have taken care for not needing to include the IDL, what sounds like a non-sense (do not explicitly inherit, but include the header!). The interface name XMarkingAccess and the method name invalidateMarkings sounds somewhat strange but I have to confess that I don't have a much better name in place. Maybe somebody else has a good name in mind? IMHO what it does is more problematic than how it's named; see my comment on the bug. Regards -- Ariel Constenla-Haile La Plata, Argentina pgpwR6j_capNI.pgp Description: PGP signature
Re: AOO logo for special purposes?
There is a logo proposal for an updated logo which actually has an arrow over the orb. Check out the AOO 4.0 logo proposals on the marketing wiki. Kevin. On Mar 15, 2013, at 5:15 PM, Jörg Schmidt joe...@j-m-schmidt.de wrote: We've done some special logo variation. For example, Drew made the Get it here logo: http://openoffice.apache.org/get-it-here.html yes, I know From a trademark perspective, this can be a good idea to keep the original logo for use only in the product and the website, but then create special, but related logos for other things. Yes. My concern at the moment is a first AOO-pin, because I always had an OpenOffice.org pin. An Apache-pin (eg http://shop.kernelconcepts.de/images/apache-pin.jpg) advertises not accurate enough for AOO. (Also, I think there are more graphics people on the marketing list, so you might want to ask the same question there) OK, I'll do that, I need only register there first. Greetings, Jörg - 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: [Call-for-Review] code changes for more powerful smarttag extensions
On 3/15/13 10:20 AM, Ariel Constenla-Haile wrote: On Wed, Mar 13, 2013 at 02:30:26PM +0100, Jürgen Schmidt wrote: - a missing include of XInterface in the new IDL XMarkingAccess.idl, IDL compile error on Mac, surprising that it worked for you This is a bug, the one that removed the need for explicitly inheriting from XInterface should have taken care for not needing to include the IDL, what sounds like a non-sense (do not explicitly inherit, but include the header!). I agree that it's a bug The interface name XMarkingAccess and the method name invalidateMarkings sounds somewhat strange but I have to confess that I don't have a much better name in place. Maybe somebody else has a good name in mind? IMHO what it does is more problematic than how it's named; see my comment on the bug. issue https://issues.apache.org/ooo/show_bug.cgi?id=121733 you are correct with your concerns of using strings where of course other existing types would make more sense. Your sugggestion of using - a LineColor with value css::util::Color instead of Red, Green, Blue - LinjeType of type css::awt::FontUnderline @Kai, can you please take this into account and adapt the changes? Ariel is right that these changes would an improvement. Regarding your concern I don't agree completely. For me it's fine to allow some more tweaking from the extension. Where I agree is that it shouldn't conflict with other global settings or other SmartTags. I will also take a further look into the code... Thanks for your reply Ariel Juergen - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Draft blog post for Document Freedom Day
Dear Rob, Check the following line in the blog Document Freedom Day, this year on February 21st, is a global celebration of the open standards, With Warm Regards V.Kadal Amutham 919444360480 914422396480 On 15 March 2013 04:25, Rob Weir robw...@apache.org wrote: https://blogs.apache.org/preview/OOo/?previewEntry=openoffice_and_odf It still needs a bit of work but I'm sharing the draft in case anyone has some early feedback. -Rob - To unsubscribe, e-mail: marketing-unsubscr...@openoffice.apache.org For additional commands, e-mail: marketing-h...@openoffice.apache.org
Re: Forums down (SQL error: Too many connections [1040])
The forum are back now. Thanks imacat But, this morning 11:00am (UTC+1), the FR forum is slow again. Maybe the MySQL max_connections parameter must be increase. Do you have check this point? - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Forums down (SQL error: Too many connections [1040])
On Fri, 15 Mar 2013 11:04:09 +0100 (CET) FR web forum ooofo...@free.fr wrote: The forum are back now. Thanks imacat But, this morning 11:00am (UTC+1), the FR forum is slow again. Maybe the MySQL max_connections parameter must be increase. Do you have check this point? Reports from other forums using phpBB software suggest that overflowing log files can cause this problem. I offer this merely as a suggestion - I have no phpBB experience. I note that the maximum number of users listed by the Forum reports has remained static at 294 since 25 October 2012; I have never observed a number of users close to that figure at any time, so I doubt the problem is actually an insufficient number of connections, no matter what the reort says. -- Rory O'Farrell ofarr...@iol.ie - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Call-for-Review] code changes for more powerful smarttag extensions
On Fri, Mar 15, 2013 at 10:45:56AM +0100, Jürgen Schmidt wrote: On 3/15/13 10:20 AM, Ariel Constenla-Haile wrote: On Wed, Mar 13, 2013 at 02:30:26PM +0100, Jürgen Schmidt wrote: - a missing include of XInterface in the new IDL XMarkingAccess.idl, IDL compile error on Mac, surprising that it worked for you This is a bug, the one that removed the need for explicitly inheriting from XInterface should have taken care for not needing to include the IDL, what sounds like a non-sense (do not explicitly inherit, but include the header!). I agree that it's a bug The interface name XMarkingAccess and the method name invalidateMarkings sounds somewhat strange but I have to confess that I don't have a much better name in place. Maybe somebody else has a good name in mind? IMHO what it does is more problematic than how it's named; see my comment on the bug. issue https://issues.apache.org/ooo/show_bug.cgi?id=121733 Not this one, but https://issues.apache.org/ooo/show_bug.cgi?id=121732 invalidation should be triggered on a TextMarkupType base, just like in XFlatParagraph::setChecked, otherwise a smart tag extension triggers unnecessary spell and grammar checking. Regards -- Ariel Constenla-Haile La Plata, Argentina pgpodmt_UVOlL.pgp Description: PGP signature
Re: Tutorial: dedicated website
while extensions for example are closer to software releases. Hmm, tutorials too no? ;-) We have specific tutoriel by major version (1.x, 2.x, 3.x and 4.x) I'm trying to, but, again, do you have a few examples? Maybe tutorials that you wrote yourself and that would be difficult to upload to one of the existing resources? Yes, in FR forum, we have sometime proposal but if I said to author: you must publish on Wiki. No response after. :-( Actually, it seems that the Forum currently offers good possibilities for those who want to publish tutorials: pages like We have a dedicated forum too: http://forum.openoffice.org/fr/forum/forum29-tutoriels.html But upload is limited (attached file must be 500ko) and we have many big tutorials. What would the biggest advantage be for you? Ease of use [...] or visibility Both of course :-) 3rd advantage: search engine and tags to reach out specific tutos And how many tutorials could it be reasonable to have? Could we reach hundreds of tutorials, for example? In first time, we could transfer our tutorials from french www: http://www.openoffice.org/fr/Documentation But I do not want to impose. If this is too complicated, you drop. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: [Call-for-Review] code changes for more powerful smarttag extensions
On 3/15/13 11:34 AM, Ariel Constenla-Haile wrote: On Fri, Mar 15, 2013 at 10:45:56AM +0100, Jürgen Schmidt wrote: On 3/15/13 10:20 AM, Ariel Constenla-Haile wrote: On Wed, Mar 13, 2013 at 02:30:26PM +0100, Jürgen Schmidt wrote: - a missing include of XInterface in the new IDL XMarkingAccess.idl, IDL compile error on Mac, surprising that it worked for you This is a bug, the one that removed the need for explicitly inheriting from XInterface should have taken care for not needing to include the IDL, what sounds like a non-sense (do not explicitly inherit, but include the header!). I agree that it's a bug The interface name XMarkingAccess and the method name invalidateMarkings sounds somewhat strange but I have to confess that I don't have a much better name in place. Maybe somebody else has a good name in mind? IMHO what it does is more problematic than how it's named; see my comment on the bug. issue https://issues.apache.org/ooo/show_bug.cgi?id=121733 Not this one, but https://issues.apache.org/ooo/show_bug.cgi?id=121732 invalidation should be triggered on a TextMarkupType base, just like in XFlatParagraph::setChecked, otherwise a smart tag extension triggers unnecessary spell and grammar checking. ok, I see thanks for the pointer. It's probably worth to take a further look on this code. @Kai, Ariel has a better overview than I have already. I looked not deep enough in the code. Please take his feedback into account. We should avoid any unnecessary overhead. Juergen - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Problems with Accessibility in Open Office
Hello: I thoroughly appreciate your quick response to my issues and am glad that you are integrating accessibility features into this application. To answer your questions regarding the platform I am using your software on, I am using Windows 8 presently; however, the accessibility problems persist, no matter which version of Windows is being used. This is an application specific problem, not an operating system issue. If keyboard navigation is a feature that is already part of this application, then the problem may be that the buttons are not properly labeled in order for assistive technologies to properly detect them. if you want, I can write up a detailed report and have it sent to you before the day is out. This report will explain what i mean about the keyboard navigation and provide exact examples for fixes. If you have any further questions, please feel free ot ask me. I will do whatever I can to answer them. Thank you so much again for making accessibility a priority. The disabled community undoubtedly appreciates your efforts. Warm regards, Reina grosvalet On 3/15/13, Jürgen Schmidt jogischm...@gmail.com wrote: Hello Reina, On 3/15/13 1:20 PM, Waldorf PC wrote: Hi developers: My name is Reina Grosvalet, and I am displeased about the fact that Open Office is not accessible for blind computer users, as this program does not work with screen reading and other assistive technologies. Blind people, just like everyone else, want a free word processing option that works just as well as MS Office. Blind freelancers can especially benefit from your program beingaccessible, as well as blind entrepreneurs, students and professionals. Because I am a certified 508 Compliance Analyst, I can provide detailed feedback concerninghow you can make your program one hundred percent accessible, so the millions of blind computer users around the world will be able to benefit from it along with everyone else. If you need proof of my certificates, I will be glad to send them to you. A plus is that I am also totally blind, so I can provide feedback from the point of view of someone who is blind. in order to give you an idea of some of the problems I see, I am going to provide you with a mini report below. this report states: 1. The installer has buttons that are clearly labeled with text that can be clearly accessed using keyboard navigation. this is a plus because a blind computer user is able to successfully install the program on his or her computer without any sighted help. 2. The buttons in the installer all have corresponding access keys, like alt+n for next and alt+f for finish. This is very helpful for screen reader users and for those who use assistive technologies because these access keys allow such users to complete functions quickly. 3. Upon opening the program, however, i notice that a blind computer user is not able to access any of its functions using keyboard navigation. the blind user cannot select the type of template heor she wishes to use, like a spreadssheet or text document. Drop down menus cannot be accessed using any form of keyboard navigation, like using the alt key to access the menus like in the windows operating system. as soon as you contact me, I can construct a detailed report that contains each problem I see as well as provide detailed fixes to these problems. It is my hope that Open Office becomes completely accessible, so people with disabilities can utilize this software and enjoy its benefits. i look forward to hearing from you on this matter. Thank you so much again. welcome at OpenOffice and we very much appreciate your feedback and your interest to help us to improve the overall accessibility. We are currently working on an improved support for accessibility by integrating IAccessibility2 support that is already available in Symphony. This work is ongoing in a separate branch and you can help us to test the application and to provide valuable feedback. We are of course very interested to make OpenOffice better in this area and the integration of IAccessibility2 is a huge and important milestone here. Regarding the keyboard access to certain functions, I am not sure if understand it correct. We normally allow keyboard navigation through menus and between controls etc. On which platform are you working and can you give more information. I am not sure maybe it is to early to start testing today but Steve Yin can provide a much better and more detailed overview where we are today. Regards Juergen Warm regards, Reina Grosvalet - 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:
Exit moderator mailing
Hi I am moderator of mailing doc,api @ o.a.o. Today I am out of time to moderate, I ask to remove moderation. Thanks. Albino - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Problems with Accessibility in Open Office
Hi Reina, My name is Reina Grosvalet, and I am displeased about the fact that Open Office is not accessible for blind computer users, as this program does not work with screen reading and other assistive technologies. Blind people, just like everyone else, want a free word processing option that works just as well as MS Office. Blind freelancers can especially benefit from your program beingaccessible, as well as blind entrepreneurs, students and professionals. Some of the tools you're using with MS Office don't work well with other programs that use it's own UI controls instead of native controls. OpenOffice currently exposes it's information to accessive technology via Java Accessibility API on Windows and via GNOME Accessibility API on Linux/Solaris with GNOME and on Mac via NSAcessibility. Some developers here are currently working on support for IAccessible2. https://en.wikipedia.org/wiki/IAccessible2 http://wiki.openoffice.org/wiki/Accessibility/IAccessible2_support Have a look here: http://www.openoffice.org/ui/accessibility/at-support.html http://wiki.openoffice.org/wiki/Accessibility Because I am a certified 508 Compliance Analyst, I can provide detailed feedback concerninghow you can make your program one hundred percent accessible, so the millions of blind computer users around the world will be able to benefit from it along with everyone else. If you need proof of my certificates, I will be glad to send them to you. A plus is that I am also totally blind, so I can provide feedback from the point of view of someone who is blind. in order to give you an idea of some of the problems I see, I am going to provide you with a mini report below. this report states: 1. The installer has buttons that are clearly labeled with text that can be clearly accessed using keyboard navigation. this is a plus because a blind computer user is able to successfully install the program on his or her computer without any sighted help. 2. The buttons in the installer all have corresponding access keys, like alt+n for next and alt+f for finish. This is very helpful for screen reader users and for those who use assistive technologies because these access keys allow such users to complete functions quickly. 3. Upon opening the program, however, i notice that a blind computer user is not able to access any of its functions using keyboard navigation. the blind user cannot select the type of template heor she wishes to use, like a spreadssheet or text document. Drop down menus cannot be accessed using any form of keyboard navigation, like using the alt key to access the menus like in the windows operating system. Use funktion key F6 to toggle between the menu, menu bar and tool bars as soon as you contact me, I can construct a detailed report that contains each problem I see as well as provide detailed fixes to these problems. It is my hope that Open Office becomes completely accessible, so people with disabilities can utilize this software and enjoy its benefits. Kind regards, Joost - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Tutorial: dedicated website
On Fri, Mar 15, 2013 at 6:39 AM, FR web forum ooofo...@free.fr wrote: while extensions for example are closer to software releases. Hmm, tutorials too no? ;-) We have specific tutoriel by major version (1.x, 2.x, 3.x and 4.x) I'm trying to, but, again, do you have a few examples? Maybe tutorials that you wrote yourself and that would be difficult to upload to one of the existing resources? Yes, in FR forum, we have sometime proposal but if I said to author: you must publish on Wiki. No response after. :-( Actually, it seems that the Forum currently offers good possibilities for those who want to publish tutorials: pages like We have a dedicated forum too: http://forum.openoffice.org/fr/forum/forum29-tutoriels.html But upload is limited (attached file must be 500ko) and we have many big tutorials. What would the biggest advantage be for you? Ease of use [...] or visibility Both of course :-) 3rd advantage: search engine and tags to reach out specific tutos And how many tutorials could it be reasonable to have? Could we reach hundreds of tutorials, for example? In first time, we could transfer our tutorials from french www: http://www.openoffice.org/fr/Documentation But I do not want to impose. If this is too complicated, you drop. - 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: Problems with Accessibility in Open Office
Hi there: So, what you are saying is that I will need to use the JAVA Accessibility API along with that Open Office application? Honestly, native controls work much better for assistive technologies. I am not sure how much your developers are familiar with coding for accessibility; however, there are some specific things that can be done if you want your application to use its own UI rather than native controls. I tried using function f6 upon opening the application, but i had no such luck. I still cannot choose the template I want, like the writing document or spread sheet. i thank you so much for your diligence with this matter. You guys are so great! :) On 3/15/13, Joost Andrae joost.and...@gmx.de wrote: Hi Reina, My name is Reina Grosvalet, and I am displeased about the fact that Open Office is not accessible for blind computer users, as this program does not work with screen reading and other assistive technologies. Blind people, just like everyone else, want a free word processing option that works just as well as MS Office. Blind freelancers can especially benefit from your program beingaccessible, as well as blind entrepreneurs, students and professionals. Some of the tools you're using with MS Office don't work well with other programs that use it's own UI controls instead of native controls. OpenOffice currently exposes it's information to accessive technology via Java Accessibility API on Windows and via GNOME Accessibility API on Linux/Solaris with GNOME and on Mac via NSAcessibility. Some developers here are currently working on support for IAccessible2. https://en.wikipedia.org/wiki/IAccessible2 http://wiki.openoffice.org/wiki/Accessibility/IAccessible2_support Have a look here: http://www.openoffice.org/ui/accessibility/at-support.html http://wiki.openoffice.org/wiki/Accessibility Because I am a certified 508 Compliance Analyst, I can provide detailed feedback concerninghow you can make your program one hundred percent accessible, so the millions of blind computer users around the world will be able to benefit from it along with everyone else. If you need proof of my certificates, I will be glad to send them to you. A plus is that I am also totally blind, so I can provide feedback from the point of view of someone who is blind. in order to give you an idea of some of the problems I see, I am going to provide you with a mini report below. this report states: 1. The installer has buttons that are clearly labeled with text that can be clearly accessed using keyboard navigation. this is a plus because a blind computer user is able to successfully install the program on his or her computer without any sighted help. 2. The buttons in the installer all have corresponding access keys, like alt+n for next and alt+f for finish. This is very helpful for screen reader users and for those who use assistive technologies because these access keys allow such users to complete functions quickly. 3. Upon opening the program, however, i notice that a blind computer user is not able to access any of its functions using keyboard navigation. the blind user cannot select the type of template heor she wishes to use, like a spreadssheet or text document. Drop down menus cannot be accessed using any form of keyboard navigation, like using the alt key to access the menus like in the windows operating system. Use funktion key F6 to toggle between the menu, menu bar and tool bars as soon as you contact me, I can construct a detailed report that contains each problem I see as well as provide detailed fixes to these problems. It is my hope that Open Office becomes completely accessible, so people with disabilities can utilize this software and enjoy its benefits. Kind regards, Joost - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org -- Get More Bang with Your Buck with Waldorf PC whether you need tech support, troubleshooting, or a new computer custom built, we have it all. Call 301-535-3733 for more details. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Problems with Accessibility in Open Office
On 3/15/13 4:38 PM, Waldorf PC wrote: Hi there: So, what you are saying is that I will need to use the JAVA Accessibility API along with that Open Office application? Honestly, native controls work much better for assistive technologies. I am not sure how much your developers are familiar with coding for accessibility; however, there are some specific things that can be done if you want your application to use its own UI rather than native controls. Java Accessibility is what we had today and which has limited functionality. That is the reason why we work on the IAccessibility2 integration. It makes more sense to focus on this and I am sure your knowledge and experience will be of big help for us when we have more to test for you. Juergen I tried using function f6 upon opening the application, but i had no such luck. I still cannot choose the template I want, like the writing document or spread sheet. i thank you so much for your diligence with this matter. You guys are so great! :) On 3/15/13, Joost Andrae joost.and...@gmx.de wrote: Hi Reina, My name is Reina Grosvalet, and I am displeased about the fact that Open Office is not accessible for blind computer users, as this program does not work with screen reading and other assistive technologies. Blind people, just like everyone else, want a free word processing option that works just as well as MS Office. Blind freelancers can especially benefit from your program beingaccessible, as well as blind entrepreneurs, students and professionals. Some of the tools you're using with MS Office don't work well with other programs that use it's own UI controls instead of native controls. OpenOffice currently exposes it's information to accessive technology via Java Accessibility API on Windows and via GNOME Accessibility API on Linux/Solaris with GNOME and on Mac via NSAcessibility. Some developers here are currently working on support for IAccessible2. https://en.wikipedia.org/wiki/IAccessible2 http://wiki.openoffice.org/wiki/Accessibility/IAccessible2_support Have a look here: http://www.openoffice.org/ui/accessibility/at-support.html http://wiki.openoffice.org/wiki/Accessibility Because I am a certified 508 Compliance Analyst, I can provide detailed feedback concerninghow you can make your program one hundred percent accessible, so the millions of blind computer users around the world will be able to benefit from it along with everyone else. If you need proof of my certificates, I will be glad to send them to you. A plus is that I am also totally blind, so I can provide feedback from the point of view of someone who is blind. in order to give you an idea of some of the problems I see, I am going to provide you with a mini report below. this report states: 1. The installer has buttons that are clearly labeled with text that can be clearly accessed using keyboard navigation. this is a plus because a blind computer user is able to successfully install the program on his or her computer without any sighted help. 2. The buttons in the installer all have corresponding access keys, like alt+n for next and alt+f for finish. This is very helpful for screen reader users and for those who use assistive technologies because these access keys allow such users to complete functions quickly. 3. Upon opening the program, however, i notice that a blind computer user is not able to access any of its functions using keyboard navigation. the blind user cannot select the type of template heor she wishes to use, like a spreadssheet or text document. Drop down menus cannot be accessed using any form of keyboard navigation, like using the alt key to access the menus like in the windows operating system. Use funktion key F6 to toggle between the menu, menu bar and tool bars as soon as you contact me, I can construct a detailed report that contains each problem I see as well as provide detailed fixes to these problems. It is my hope that Open Office becomes completely accessible, so people with disabilities can utilize this software and enjoy its benefits. Kind regards, Joost - 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: Problems with Accessibility in Open Office
Hi there: You are correct about the limited functionality of the JAVA Access Bridge, hence the reason it is never recommended to developers by 508 compliance analysts as an accessibility fix. The intensions were good when developing thebridge, but it is not a good fix. When I am done my work for the day, I can write up a detailed explanation concerning what works in terms of accessibility, like how to make a UI that is compatible with assistive technologies. I will be happy to do that for you. Warm regards, Reina Grosvalet On 3/15/13, Jürgen Schmidt jogischm...@gmail.com wrote: On 3/15/13 4:38 PM, Waldorf PC wrote: Hi there: So, what you are saying is that I will need to use the JAVA Accessibility API along with that Open Office application? Honestly, native controls work much better for assistive technologies. I am not sure how much your developers are familiar with coding for accessibility; however, there are some specific things that can be done if you want your application to use its own UI rather than native controls. Java Accessibility is what we had today and which has limited functionality. That is the reason why we work on the IAccessibility2 integration. It makes more sense to focus on this and I am sure your knowledge and experience will be of big help for us when we have more to test for you. Juergen I tried using function f6 upon opening the application, but i had no such luck. I still cannot choose the template I want, like the writing document or spread sheet. i thank you so much for your diligence with this matter. You guys are so great! :) On 3/15/13, Joost Andrae joost.and...@gmx.de wrote: Hi Reina, My name is Reina Grosvalet, and I am displeased about the fact that Open Office is not accessible for blind computer users, as this program does not work with screen reading and other assistive technologies. Blind people, just like everyone else, want a free word processing option that works just as well as MS Office. Blind freelancers can especially benefit from your program beingaccessible, as well as blind entrepreneurs, students and professionals. Some of the tools you're using with MS Office don't work well with other programs that use it's own UI controls instead of native controls. OpenOffice currently exposes it's information to accessive technology via Java Accessibility API on Windows and via GNOME Accessibility API on Linux/Solaris with GNOME and on Mac via NSAcessibility. Some developers here are currently working on support for IAccessible2. https://en.wikipedia.org/wiki/IAccessible2 http://wiki.openoffice.org/wiki/Accessibility/IAccessible2_support Have a look here: http://www.openoffice.org/ui/accessibility/at-support.html http://wiki.openoffice.org/wiki/Accessibility Because I am a certified 508 Compliance Analyst, I can provide detailed feedback concerninghow you can make your program one hundred percent accessible, so the millions of blind computer users around the world will be able to benefit from it along with everyone else. If you need proof of my certificates, I will be glad to send them to you. A plus is that I am also totally blind, so I can provide feedback from the point of view of someone who is blind. in order to give you an idea of some of the problems I see, I am going to provide you with a mini report below. this report states: 1. The installer has buttons that are clearly labeled with text that can be clearly accessed using keyboard navigation. this is a plus because a blind computer user is able to successfully install the program on his or her computer without any sighted help. 2. The buttons in the installer all have corresponding access keys, like alt+n for next and alt+f for finish. This is very helpful for screen reader users and for those who use assistive technologies because these access keys allow such users to complete functions quickly. 3. Upon opening the program, however, i notice that a blind computer user is not able to access any of its functions using keyboard navigation. the blind user cannot select the type of template heor she wishes to use, like a spreadssheet or text document. Drop down menus cannot be accessed using any form of keyboard navigation, like using the alt key to access the menus like in the windows operating system. Use funktion key F6 to toggle between the menu, menu bar and tool bars as soon as you contact me, I can construct a detailed report that contains each problem I see as well as provide detailed fixes to these problems. It is my hope that Open Office becomes completely accessible, so people with disabilities can utilize this software and enjoy its benefits. Kind regards, Joost - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Problems with Accessibility in Open Office
On Fri, Mar 15, 2013 at 12:03 PM, Waldorf PC waldor...@gmail.com wrote: Hi there: You are correct about the limited functionality of the JAVA Access Bridge, hence the reason it is never recommended to developers by 508 compliance analysts as an accessibility fix. The intensions were good when developing thebridge, but it is not a good fix. When I am done my work for the day, I can write up a detailed explanation concerning what works in terms of accessibility, like how to make a UI that is compatible with assistive technologies. I will be happy to do that for you. Hi Reina, Testing or reporting on what OpenOffice 3.4.1 does today is probably not very useful since we're moving over to an entirely different approach. IBM contributed the source code for their Lotus Symphony product, and we're integrating the IAccesible2 support from that. A great deal of analysis was done at IBM before they did that work. So a good preview of the support we should end up with in the end is what Symphony has today: http://www-03.ibm.com/software/lotus/symphony/home.nsf/home Of course, we'll probably introduce some bugs while we are porting that code over to OpenOffice. So testing of the 4.0 and 4.1 version of OpenOffice, before we release it, will be key. -Rob Warm regards, Reina Grosvalet On 3/15/13, Jürgen Schmidt jogischm...@gmail.com wrote: On 3/15/13 4:38 PM, Waldorf PC wrote: Hi there: So, what you are saying is that I will need to use the JAVA Accessibility API along with that Open Office application? Honestly, native controls work much better for assistive technologies. I am not sure how much your developers are familiar with coding for accessibility; however, there are some specific things that can be done if you want your application to use its own UI rather than native controls. Java Accessibility is what we had today and which has limited functionality. That is the reason why we work on the IAccessibility2 integration. It makes more sense to focus on this and I am sure your knowledge and experience will be of big help for us when we have more to test for you. Juergen I tried using function f6 upon opening the application, but i had no such luck. I still cannot choose the template I want, like the writing document or spread sheet. i thank you so much for your diligence with this matter. You guys are so great! :) On 3/15/13, Joost Andrae joost.and...@gmx.de wrote: Hi Reina, My name is Reina Grosvalet, and I am displeased about the fact that Open Office is not accessible for blind computer users, as this program does not work with screen reading and other assistive technologies. Blind people, just like everyone else, want a free word processing option that works just as well as MS Office. Blind freelancers can especially benefit from your program beingaccessible, as well as blind entrepreneurs, students and professionals. Some of the tools you're using with MS Office don't work well with other programs that use it's own UI controls instead of native controls. OpenOffice currently exposes it's information to accessive technology via Java Accessibility API on Windows and via GNOME Accessibility API on Linux/Solaris with GNOME and on Mac via NSAcessibility. Some developers here are currently working on support for IAccessible2. https://en.wikipedia.org/wiki/IAccessible2 http://wiki.openoffice.org/wiki/Accessibility/IAccessible2_support Have a look here: http://www.openoffice.org/ui/accessibility/at-support.html http://wiki.openoffice.org/wiki/Accessibility Because I am a certified 508 Compliance Analyst, I can provide detailed feedback concerninghow you can make your program one hundred percent accessible, so the millions of blind computer users around the world will be able to benefit from it along with everyone else. If you need proof of my certificates, I will be glad to send them to you. A plus is that I am also totally blind, so I can provide feedback from the point of view of someone who is blind. in order to give you an idea of some of the problems I see, I am going to provide you with a mini report below. this report states: 1. The installer has buttons that are clearly labeled with text that can be clearly accessed using keyboard navigation. this is a plus because a blind computer user is able to successfully install the program on his or her computer without any sighted help. 2. The buttons in the installer all have corresponding access keys, like alt+n for next and alt+f for finish. This is very helpful for screen reader users and for those who use assistive technologies because these access keys allow such users to complete functions quickly. 3. Upon opening the program, however, i notice that a blind computer user is not able to access any of its functions using keyboard navigation. the blind user cannot select the type of template heor she wishes to use, like a spreadssheet or text document. Drop down
Re: Completed How the Apache OpenOffice Project Works
Rebecca -- Thanks for letting us know of your progress. We hope to see more of you on this list soon! On Wed, Mar 13, 2013 at 8:32 PM, Rebecca Williams sxyrck...@gmail.comwrote: I have completed this module. -- MzK Achieving happiness requires the right combination of Zen and Zin.
Re: Completed How the Apache OpenOffice Project Works
Martha, Thanks for letting us know of your progress. We hope to see more of you on this list soon! On Thu, Mar 14, 2013 at 2:37 AM, martha baker trinity1...@icloud.comwrote: complete martha baker trinity1...@icloud.com -- MzK Achieving happiness requires the right combination of Zen and Zin.
Re: [Call-for-Review] code changes for more powerful smarttag extensions
On Fri, Mar 15, 2013 at 01:09:45PM +0100, Kai Labusch wrote: As a first step, it would be sufficient for our purposes, if the extension could specify the color of a smart-tag. Would it reduce your concerns that the patches would give to much control to the extension if we remove the possibilty to specify the line type? IMO it's fine if the smart tag extension specifies both underline color and style, but the application code, before applying it, should check that the settings do not overlap with the other settings for spell and grammar checking, and in case the smart tag extensions overlaps with the other settings, apply some default. Here the priority is the user experience: the user should clearly distinguish the different markups. However, I already heared some complaints that the smart-tags are not visible enough. In other editor applications, we change the background color of the text in order to make the problems more visible. You could implement something similar to the fields shading, may be also a more detailed mouse-over hint in the tooltip (see void SwEditWin::RequestHelp(const HelpEvent rEvt) ), etc. etc. There are place for improvement in the current implementation (always taking take that Writer is supposed to be WYSIWYG editor, so all these visual hints should be configurable). Regards -- Ariel Constenla-Haile La Plata, Argentina pgpSsyDXnGWvD.pgp Description: PGP signature
Re: Forums down (SQL error: Too many connections [1040])
It should be much higher on the EN forum. The 294 figure (statistics information at the bottom of the forum index page) is an instantaneous measurement. Hagar De : FR web forum But, in FR forum, we have specific statistics. In 2012: average of 6,892 visits per day In 2013 (for 3 first months): 9,445 /day Une messagerie gratuite, garantie à vie et des services en plus, ça vous tente ? Je crée ma boîte mail www.laposte.net
Re: Forums down (SQL error: Too many connections [1040])
On Fri, Mar 15, 2013 at 1:54 PM, hagar.del...@laposte.net wrote: It should be much higher on the EN forum. The 294 figure (statistics information at the bottom of the forum index page) is an instantaneous measurement. Do we know what the timeout is for a connection? I don't know if it is the same here, but in other systems I've worked on, if you have N simultaneous users you can have more than N connections active, since users who recently left may still have connections allocated, until they time out for inactivity. -Rob Hagar De : FR web forum But, in FR forum, we have specific statistics. In 2012: average of 6,892 visits per day In 2013 (for 3 first months): 9,445 /day Une messagerie gratuite, garantie à vie et des services en plus, ça vous tente ? Je crée ma boîte mail www.laposte.net - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Apache OpenOffice Extensions Website 2.0 (beta)
As announced back at the end of December we have been working on enhancing AOO Extensions website, you might want to have a look at http://aoo-extbeta.sourceforge.net/ Keep in mind that the final layout would depend on AOO 4.0, and counters are set to zero because downloads don't happen over there. So said, all accounts and extensions have been imported, so releases and comments. If you want to make your mind about the new features have a look at the following URLs: http://aoo-extbeta.sourceforge.net/ http://aoo-extbeta.sourceforge.net/search http://aoo-extbeta.sourceforge.net/project/oracle-pdf-import-extension Comments and feedback are welcome as usual. Roberto - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Problems with Accessibility in Open Office
Hi Rob: I wish I had seen your message before I saw Dennis's. I will merely disregard Open Office 3 and check out what you have sent me in this email. Let me know when you wish for me to do my testing and reporting, and I will be happy to perform these tasks. I assume it will be okay for me to send these test cases to the list? Please let me know. Thank you so much for everything. Warm regards, Reina Grosvalet On 3/15/13, Rob Weir robw...@apache.org wrote: On Fri, Mar 15, 2013 at 12:03 PM, Waldorf PC waldor...@gmail.com wrote: Hi there: You are correct about the limited functionality of the JAVA Access Bridge, hence the reason it is never recommended to developers by 508 compliance analysts as an accessibility fix. The intensions were good when developing thebridge, but it is not a good fix. When I am done my work for the day, I can write up a detailed explanation concerning what works in terms of accessibility, like how to make a UI that is compatible with assistive technologies. I will be happy to do that for you. Hi Reina, Testing or reporting on what OpenOffice 3.4.1 does today is probably not very useful since we're moving over to an entirely different approach. IBM contributed the source code for their Lotus Symphony product, and we're integrating the IAccesible2 support from that. A great deal of analysis was done at IBM before they did that work. So a good preview of the support we should end up with in the end is what Symphony has today: http://www-03.ibm.com/software/lotus/symphony/home.nsf/home Of course, we'll probably introduce some bugs while we are porting that code over to OpenOffice. So testing of the 4.0 and 4.1 version of OpenOffice, before we release it, will be key. -Rob Warm regards, Reina Grosvalet On 3/15/13, Jürgen Schmidt jogischm...@gmail.com wrote: On 3/15/13 4:38 PM, Waldorf PC wrote: Hi there: So, what you are saying is that I will need to use the JAVA Accessibility API along with that Open Office application? Honestly, native controls work much better for assistive technologies. I am not sure how much your developers are familiar with coding for accessibility; however, there are some specific things that can be done if you want your application to use its own UI rather than native controls. Java Accessibility is what we had today and which has limited functionality. That is the reason why we work on the IAccessibility2 integration. It makes more sense to focus on this and I am sure your knowledge and experience will be of big help for us when we have more to test for you. Juergen I tried using function f6 upon opening the application, but i had no such luck. I still cannot choose the template I want, like the writing document or spread sheet. i thank you so much for your diligence with this matter. You guys are so great! :) On 3/15/13, Joost Andrae joost.and...@gmx.de wrote: Hi Reina, My name is Reina Grosvalet, and I am displeased about the fact that Open Office is not accessible for blind computer users, as this program does not work with screen reading and other assistive technologies. Blind people, just like everyone else, want a free word processing option that works just as well as MS Office. Blind freelancers can especially benefit from your program beingaccessible, as well as blind entrepreneurs, students and professionals. Some of the tools you're using with MS Office don't work well with other programs that use it's own UI controls instead of native controls. OpenOffice currently exposes it's information to accessive technology via Java Accessibility API on Windows and via GNOME Accessibility API on Linux/Solaris with GNOME and on Mac via NSAcessibility. Some developers here are currently working on support for IAccessible2. https://en.wikipedia.org/wiki/IAccessible2 http://wiki.openoffice.org/wiki/Accessibility/IAccessible2_support Have a look here: http://www.openoffice.org/ui/accessibility/at-support.html http://wiki.openoffice.org/wiki/Accessibility Because I am a certified 508 Compliance Analyst, I can provide detailed feedback concerninghow you can make your program one hundred percent accessible, so the millions of blind computer users around the world will be able to benefit from it along with everyone else. If you need proof of my certificates, I will be glad to send them to you. A plus is that I am also totally blind, so I can provide feedback from the point of view of someone who is blind. in order to give you an idea of some of the problems I see, I am going to provide you with a mini report below. this report states: 1. The installer has buttons that are clearly labeled with text that can be clearly accessed using keyboard navigation. this is a plus because a blind computer user is able to successfully install the program on his or her computer without any sighted help. 2. The buttons in the installer all have corresponding access
Re:Apache OpenOffice Extensions Website 2.0 (beta)
Really AWESOME! A huge step forward regarding the interface. Many thanks for this improved site. Hagar Message du 15/03/13 19:53 De : Roberto Galoppini A : dev@openoffice.apache.org Copie à : Objet : Apache OpenOffice Extensions Website 2.0 (beta) As announced back at the end of December we have been working on enhancing AOO Extensions website, you might want to have a look at http://aoo-extbeta.sourceforge.net/ Keep in mind that the final layout would depend on AOO 4.0, and counters are set to zero because downloads don't happen over there. So said, all accounts and extensions have been imported, so releases and comments. If you want to make your mind about the new features have a look at the following URLs: http://aoo-extbeta.sourceforge.net/ http://aoo-extbeta.sourceforge.net/search http://aoo-extbeta.sourceforge.net/project/oracle-pdf-import-extension Comments and feedback are welcome as usual. Roberto - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org Une messagerie gratuite, garantie à vie et des services en plus, ça vous tente ? Je crée ma boîte mail www.laposte.net
Re: Fail when build testtools module
Hi
On Fri, Mar 15, 2013 at 05:38:15PM -0300, Claudio Filho wrote:
Hi
More one problem and question about Testtools. I haven't idea about
what happens... some idea?
In other hand, i saw a discution about to remove the module
testtools. It will be removed? If yes (and i understood that yes), why
it is compiled yet?
one thing is the old vcl test tool, and this module, that includes stuff
like the UNO bridge test
Entering
/home/filhocf/projetos/aoo/source/main/testtools/com/sun/star/comp/bridge
updating: META-INF/MANIFEST.MF (deflated 12%)
Nothing to update for zip
Entering /home/filhocf/projetos/aoo/source/main/testtools/source/bridgetest
cd ../../unxlngx6/lib :
LD_LIBRARY_PATH=/home/filhocf/projetos/aoo/source/main/solver/400/unxlngx6/lib${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}
/home/filhocf/projetos/aoo/source/main/solver/400/unxlngx6/bin/uno \
-ro uno_services.rdb -ro uno_types.rdb \
-s com.sun.star.test.bridge.BridgeTest -- \
com.sun.star.test.bridge.CppTestObject
terminate called after throwing an instance of
'com::sun::star::uno::RuntimeException'
/bin/bash: line 1: 15762 Aborted
LD_LIBRARY_PATH=/home/filhocf/projetos/aoo/source/main/solver/400/unxlngx6/lib${LD_LIBRARY_PATH:+:${LD_LIBRARY_PATH}}
/home/filhocf/projetos/aoo/source/main/solver/400/unxlngx6/bin/uno -ro
uno_services.rdb -ro uno_types.rdb -s
com.sun.star.test.bridge.BridgeTest --
com.sun.star.test.bridge.CppTestObject
dmake: Error code 134, while making 'runtest'
ERROR: error 65280 occurred while making
/home/filhocf/projetos/aoo/source/main/testtools/source/bridgetest
Your compiler seems to fail the bridge test.
You can simply disable building this, as it was done for MacOS, FreeBSD
and Solaris, see
http://opengrok.adfinis-sygroup.org/source/xref/aoo-trunk/main/testtools/source/bridgetest/makefile.mk#137
@echo Mac OSX PPC GCC ad FreeBDS/i386 fails this test! likely broken
UNO bridge. Fix me.
though a broken UNO bridge looks like a stopper, not something to work
around just to go further with the build (that said, I have no idea about
the UNO bridge internals...). At least it is worth a bug report.
Regards
--
Ariel Constenla-Haile
La Plata, Argentina
pgpK36F6ZZjn9.pgp
Description: PGP signature
glibc version mentioned on README file
From this forum thread http://forum.openoffice.org/en/forum/viewtopic.php?f=16t=60439 I can see that the README file included on the Linux install say that glibc version needed is 2.5 or higher, but AFAIK AOO is being build with 2.11 which cause the problems commented on Issue 119385. Maybe the readme file need a change? Something like (correct me if I'm wrong) at least 2.5 is needed to build the software from source, but the official builds need at least 2.11. Regards Ricardo
Re: glibc version mentioned on README file
Hi On Fri, Mar 15, 2013 at 11:53:57PM +0100, RGB ES wrote: From this forum thread http://forum.openoffice.org/en/forum/viewtopic.php?f=16t=60439 I can see that the README file included on the Linux install say that glibc version needed is 2.5 or higher, but AFAIK AOO is being build with 2.11 which cause the problems commented on Issue 119385. Maybe the readme file need a change? Something like (correct me if I'm wrong) at least 2.5 is needed to build the software from source, but the official builds need at least 2.11. This is bug https://issues.apache.org/ooo/show_bug.cgi?id=119393 The information was updated on the site only http://www.openoffice.org/dev_docs/source/sys_reqs_aoo34.html Linux kernel version 2.6 or higher, glibc2 version 2.11.1 or higher Updating the README at that time would have triggered a new translation update, see comment 10 in that bug. Current developer snapshots (and future 4.0) will be built on a system with glibc-2.5 /CentOS 5), see https://issues.apache.org/ooo/show_bug.cgi?id=119385 And IMO we should simplify the README: system requirements are on the website, on the download page; maintaining more that one place is error prone (bug 119393 is the proof); the user is supposed to read the system requirements of what he is going to download *before* s/he downloads it and installs it, not once installed, in the README. Regards -- Ariel Constenla-Haile La Plata, Argentina pgpJj9uAjkdqg.pgp Description: PGP signature
Re: glibc version mentioned on README file
On 16 March 2013 00:08, Ariel Constenla-Haile arie...@apache.org wrote: Hi On Fri, Mar 15, 2013 at 11:53:57PM +0100, RGB ES wrote: From this forum thread http://forum.openoffice.org/en/forum/viewtopic.php?f=16t=60439 I can see that the README file included on the Linux install say that glibc version needed is 2.5 or higher, but AFAIK AOO is being build with 2.11 which cause the problems commented on Issue 119385. Maybe the readme file need a change? Something like (correct me if I'm wrong) at least 2.5 is needed to build the software from source, but the official builds need at least 2.11. This is bug https://issues.apache.org/ooo/show_bug.cgi?id=119393 The information was updated on the site only http://www.openoffice.org/dev_docs/source/sys_reqs_aoo34.html Linux kernel version 2.6 or higher, glibc2 version 2.11.1 or higher Updating the README at that time would have triggered a new translation update, see comment 10 in that bug. Current developer snapshots (and future 4.0) will be built on a system with glibc-2.5 /CentOS 5), see https://issues.apache.org/ooo/show_bug.cgi?id=119385 And IMO we should simplify the README: system requirements are on the website, on the download page; maintaining more that one place is error prone (bug 119393 is the proof); the user is supposed to read the system requirements of what he is going to download *before* s/he downloads it and installs it, not once installed, in the README. +1, I would prefer our readme file simply contained links to the relevant pages on www or mwiki. I think we should have a couple of pages: - system requirements - release notes - known issues (this should be a live page, where we can keep a list a bugs specific to this version) I agree totally that keeping the info in more than one place is not correct. rgds jan I. Regards -- Ariel Constenla-Haile La Plata, Argentina
Re: glibc version mentioned on README file
2013/3/16 Ariel Constenla-Haile arie...@apache.org Hi On Fri, Mar 15, 2013 at 11:53:57PM +0100, RGB ES wrote: From this forum thread http://forum.openoffice.org/en/forum/viewtopic.php?f=16t=60439 I can see that the README file included on the Linux install say that glibc version needed is 2.5 or higher, but AFAIK AOO is being build with 2.11 which cause the problems commented on Issue 119385. Maybe the readme file need a change? Something like (correct me if I'm wrong) at least 2.5 is needed to build the software from source, but the official builds need at least 2.11. This is bug https://issues.apache.org/ooo/show_bug.cgi?id=119393 The information was updated on the site only http://www.openoffice.org/dev_docs/source/sys_reqs_aoo34.html Linux kernel version 2.6 or higher, glibc2 version 2.11.1 or higher Updating the README at that time would have triggered a new translation update, see comment 10 in that bug. Current developer snapshots (and future 4.0) will be built on a system with glibc-2.5 /CentOS 5), see https://issues.apache.org/ooo/show_bug.cgi?id=119385 And IMO we should simplify the README: system requirements are on the website, on the download page; maintaining more that one place is error prone (bug 119393 is the proof); the user is supposed to read the system requirements of what he is going to download *before* s/he downloads it and installs it, not once installed, in the README. Regards -- Ariel Constenla-Haile La Plata, Argentina Perfectly clear. Thanks! Regards Ricardo
