Re: [dev] assertion failure
On 02/23/10 18:45, Terrence Enger wrote: On Thu, 2010-02-11 at 10:16 +0100, Stephan Bergmann wrote: On 02/11/10 03:11, Terrence Enger wrote: Let me pick on the first assertion which failed, and one which is failing quite regularly. It is ... Error: seekEntry(): Bad map From File /home/terry/OOo_hacking/DEV300_m71/svl/source/misc/inettype.cxx at line 818 Now addressed by http://www.openoffice.org/issues/show_bug.cgi?id=109146. How can I--or similarly situated newbies--contribute? Particularly, how should I go about creating test cases? In other words where should I start reading? Test cases: Due to me currently working in that area on CWS sb118, things are somewhat in flux right now. Once that CWS is integrated and things have settled, the situation should be somewhat like this: - You can write tests in plain JUnit or CppUnit (JUnit will become a prerequisite for building OOo, CppUnit is available in module cppunit). For CppUnit there is a slightly modified test runner cppunittester, built at sal/cppunittester (for technical reasons, it is preferable if the tester executable uses SAL_MAIN instead of plain main). - Tests that require an elaborate test environment (e.g., a running OOo instance to test against) are supported by Java and C++ libraries that set up and tear down such environments (i.e., to be called from the tests' setUp/tearDown) and makefile helpers to start the test runners appropriately. For now, the libraries (from module test) support starting/stopping an OOo instance to which the tests can connect via UNO, and there is one helper solenv/inc/installationtest.mk makefile. This will probably expand to cover other common needs of tests. - All directories containing test code are added to the modules' prj/build.lst files. Tests that cannot be built/run in a normal OOo build, because they have build/run-time dependencies on other modules higher up in the hierarchy (e.g., all tests requiring a running OOo instance, which is only made available in topmost module smoketestoo_native) have makefiles enclosed in .IF$(OOO_SUBSEQUENT_TESTS)!=. That way, they are ignored on a first build, and a second build to run all tests can be scheduled as cd smoketestoo_native OOO_SUBSEQUENT_TESTS=x build --all. Reading: For how to write tests, I would suggest the generic testing and xUnit literature. Writing tests for specific parts of OOo probably requires the same knowledge as when developing non-test code there, so documentation pointers would be the same as for general newbie developers. Let me know if you have any trouble going forward. Maybe you can explain a concrete thing you would like to write a test for, and we can see how to get started with that concrete example. -Stephan - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] question about oDatabaseContext.getElementNames()
Hi Oliver, Is it correct, that oDatabaseContext.getElementNames() will return the displayed name (shown in database brwoser) and not the registered Name shown in Tools - Options ? for example the macro below will return My Database, not mydatabase node oor:name=RegisteredNames node oor:name=My Database oor:op=replace prop oor:name=Location oor:type=xs:string valuefile:///X:/MyDatabase.odb/value /prop prop oor:name=Name oor:type=xs:string valuemydatabase/value /prop /node /node The code for this happen[s/ed] to be a little ... inconsistent. When the config data is created by OOo itself, then the node name and the property value are identical. When reading the data, the node name is taken as registration name. Strictly, this is wrong, of course, but it's noticed only when the node name and the prop value are not identical. On the DEV300 code line, this has been fixed - now the property value is taken as registration name, the node name can be an arbitrary logical name (preferably something like org.something to ensure uniqueness). In addition, an interface css.sdb.XDatabaseRegistrations [1] has been introduced, which hides the configuration data from you, so there is no need to tamper with it directly (The exception would be an extension bringing its own configuration data with it, but even here, an on-demand registration using XDatabaseRegistrations and the new XDeploymentHook would be possible). Ciao Frank [1]http://hg.services.openoffice.org/DEV300/file/1467f46f8817/offapi/com/sun/star/sdb/XDatabaseRegistrations.idl -- - Frank Schönheit, Software Engineer frank.schoenh...@sun.com - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
[dev] Tracing OOo's drawing code from core to Java
Greetings, I am attempting to estimate the level of effort it would take to create a Swing lightweight implementation of the Java OpenOffice interface. We have a project that would like to integrate OpenOffice functionality, but it is based on an internally-developed graphics engine. We can embed lightweight Swing but not heavyweight AWT. Searches of the mailing list archives turned up a few inquiries about this but no answers. I am looking for someone who knows something about OOo's graphics internals to help point the way. I've spent some time digging through UNO and the Java interface and have come up with some candidate courses of action and would appreciate some pointers as to where some of the appropriate code might live within the large OOo codebase. Some approaches I can imagine: * Create a Java BufferedImage in RAM and use it as the drawing surface upon which OOo renders its contents, and use it as the back-buffer to a Swing JComponent. * Use JOGL to create a texture on the graphics card and use that as the hardware peer and render it out to a JComponent through a GLJPanel. * Draw the OOo work off-screen then copy it to a lightweight buffer on-screen. I have experience hacking at Swing and was a C++ expert in a past life, but haven't even glanced at CORBA in over a decade so am having trouble tracing the flow of execution through UNO. Is there anyone out there who can point the way to the right code? --Sam Kass - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
Re: [dev] question about oDatabaseContext.getElementNames()
Hi Frank, When the config data is created by OOo itself, then the node name and the property value are identical. yes, you are right, i tried to insert a more readable (localized) display name, but wasn't aware that oo 3.2 will use the node name for database access. so for upward compatibility i will change it back to the registration name ... otherwise our users's will have to use Edit - Echange Database... or even change macro code in oo 3.x ... thanks :-) Oliver Am 24.02.2010 09:56 schrieb Frank Schoenheit, Sun Microsystems Germany: Hi Oliver, Is it correct, that oDatabaseContext.getElementNames() will return the displayed name (shown in database brwoser) and not the registered Name shown in Tools - Options ? for example the macro below will return My Database, not mydatabase node oor:name=RegisteredNames node oor:name=My Database oor:op=replace prop oor:name=Location oor:type=xs:string valuefile:///X:/MyDatabase.odb/value /prop prop oor:name=Name oor:type=xs:string valuemydatabase/value /prop /node /node The code for this happen[s/ed] to be a little ... inconsistent. When the config data is created by OOo itself, then the node name and the property value are identical. When reading the data, the node name is taken as registration name. Strictly, this is wrong, of course, but it's noticed only when the node name and the prop value are not identical. On the DEV300 code line, this has been fixed - now the property value is taken as registration name, the node name can be an arbitrary logical name (preferably something like org.something to ensure uniqueness). In addition, an interface css.sdb.XDatabaseRegistrations [1] has been introduced, which hides the configuration data from you, so there is no need to tamper with it directly (The exception would be an extension bringing its own configuration data with it, but even here, an on-demand registration using XDatabaseRegistrations and the new XDeploymentHook would be possible). Ciao Frank [1]http://hg.services.openoffice.org/DEV300/file/1467f46f8817/offapi/com/sun/star/sdb/XDatabaseRegistrations.idl -- Oliver Brinzing fon +49 7181 481401 fax +49 7181 475635 Ludwigstrasse 14mobil +49 174 3015743 73614 Schorndorfmailto:oliver.brinz...@gmx.de GnuPG key 0xCFD04A45: 8822 057F 4956 46D3 352C 1A06 4E2C AB40 CFD0 4A45 signature.asc Description: OpenPGP digital signature
[dev] Re: Questions on downloading OpenOffice.org for business use
I'm just a user, not admin, but ... go ahead and download the free version and install/use it wherever you wish. There are no special use requirements with the license that comes with the download and none would require payment of licensing. Limitations would only come in to play if someone wanted to modify the OO.o code and try to charge money for it, basically. It's a little more than that, but not a lot. By coming here you have contacted the right organization. You'll even find the authors of OO.o code here sometimes. Nothing to worry about; many companies large and small, even several governments are now using OO.o and they pay no license fees and have the exact same program. Depending on the situation, it might be necessary to pay for support if this newsgroup isn't sufficient for you/their purposes. Except for a business with a large number of people using OO.o though, I don't even see the expense of Support from an external party as a requirement. It depends on the situation, like I said. If you had 50 people say, that had to be experts on it in a week, you might want payign someone to help out with that, but otherwise ... . HTH, Twayne Mabel Lee mabel_...@lsl.com.hk wrote in message news:2b288dc05fc807409d40147eb493921780e15ca...@exchangeserver.lsl.com.hk... Dear Sir, I am Mabel, from Lighthouse Services Ltd, and one of my clients is looking for the openOffice.org 3.2 for business use, and I've got the following question on that product: 1. For this case, do we need to buy any license on OpenOffice.org? Or we just download the free software? If we need to buy the license, since my client is located in Hong Kong, which organization should we contact? 2. Also, do we need to sign any document? Thank you so much for your all help! Best Regards, Mabel Lee Sales Executive Trainee _ Lighthouse Services Limited Unit B, 24/F., China Overseas Building, 139 Hennessy Road, Wan Chai, Hong Kong. Tel: 2591 9178 Fax: 2591 9378 Email: mabel_...@lsl.com.hkmailto:mabel_...@lsl.com.hk Lighthouse Services Limited is Your IT Solutions Services Provider We are one of the Microsoft certified partners who provides various types of professional services including: 1) Project Management and Consulting Services 2) Developing Application Systems such as ERP System 3) Sourcing various kind of solutions to clients such as HR system, DMS, POS system, etc 4) Hardware and Networking Service (Cabling Wiring, PC Server Setup and License Hardware Purchase) - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
[dev] oo320 simple spreadsheet with control element fails odfvalidator test
Hi, yesterday evening i had some time to create the odfvalidator.jar from http://odftoolkit.org/ODFValidator ... i used schemas from: http://docs.oasis-open.org/office/v1.2/part3/cd01/OpenDocument-manifest-schema-v1.2-cd1.rng http://docs.oasis-open.org/office/v1.2/part3/cd01/OpenDocument-dsig-schema-v1.2-cd1.rng http://docs.oasis-open.org/office/v1.2/part1/cd04/OpenDocument-schema-v1.2-cd04.rng *) *) renamed to OpenDocument-schema-v1.2-cd1.rng, see output below i checked 2 to simple documents (spreadsheet with 1 push button) and here is the result: - oo115_converted_oo32.ods - created with oo115 and converted with oo32 - oo320_native.ods - a native oo 320 document oo115_converted_oo32.ods:Info:ODF Version: 1.2 internal:schema/odf12/OpenDocument-schema-v1.2-cd1.rng:Info:parsed. oo115_converted_oo32.ods/meta.xml:Info:attribute 'grddl:transformation' of element office:document-meta ignored. oo115_converted_oo32.ods/meta.xml:Info:Generator: OpenOffice.org/3.2$Win32 OpenOffice.org_project/320m12$Build-9483 oo115_converted_oo32.ods/meta.xml:Info:no errors internal:schema/odf12/OpenDocument-manifest-schema-v1.2-cd1.rng:Info:parsed. oo115_converted_oo32.ods/META-INF/manifest.xml:Info:no errors oo115_converted_oo32.ods:Info:Media Type: application/vnd.oasis.opendocument.spreadsheet oo115_converted_oo32.ods/settings.xml:Info:no errors oo115_converted_oo32.ods/styles.xml:Info:attribute 'grddl:transformation' of element office:document-styles ignored. oo115_converted_oo32.ods/styles.xml:Info:no errors oo115_converted_oo32.ods/content.xml:Info:attribute 'grddl:transformation' of element office:document-content ignored. oo115_converted_oo32.ods/content.xml[2,3614]:Error:element form:form is missing type attribute oo115_converted_oo32.ods/content.xml[2,5428]:Error:control1 is referenced by an IDREF, but not defined. oo115_converted_oo32.ods/content.xml:Info:validation errors found internal:schema/odf12/OpenDocument-dsig-schema-v1.2-cd1.rng:Info:parsed. oo115_converted_oo32.ods:Info:validation errors found oo320_native.ods:Info:ODF Version: 1.2 oo320_native.ods/meta.xml:Info:attribute 'grddl:transformation' of element office:document-meta ignored. oo320_native.ods/meta.xml:Info:Generator: OpenOffice.org/3.2$Win32 OpenOffice.org_project/320m12$Build-9483 oo320_native.ods/meta.xml:Info:no errors oo320_native.ods/META-INF/manifest.xml:Info:no errors oo320_native.ods:Info:Media Type: application/vnd.oasis.opendocument.spreadsheet oo320_native.ods/settings.xml:Info:no errors oo320_native.ods/styles.xml:Info:attribute 'grddl:transformation' of element office:document-styles ignored. oo320_native.ods/styles.xml:Info:no errors oo320_native.ods/content.xml:Info:attribute 'grddl:transformation' of element office:document-content ignored. oo320_native.ods/content.xml[2,3529]:Error:element form:form is missing type attribute oo320_native.ods/content.xml[2,4216]:Error:element script:event-listener is missing type attribute oo320_native.ods/content.xml[2,5385]:Error:control1 is referenced by an IDREF, but not defined. oo320_native.ods/content.xml:Info:validation errors found oo320_native.ods:Info:validation errors found is there anything to worry about ? Oliver -- GMX DSL: Internet, Telefon und Entertainment für nur 19,99 EUR/mtl.! http://portal.gmx.net/de/go/dsl02 - To unsubscribe, e-mail: dev-unsubscr...@openoffice.org For additional commands, e-mail: dev-h...@openoffice.org
