Re: [EXT] image double click
sorry never mind, the __writeRegistryServiceInfo method was called now, there was just a typo left in my jobs.xcu. However my job itself isn't triggered yet. Do I have to additionally set an entry to my protocolHandler.xcu as: node oor:name=myaddon.test.InterceptorJob oor:op=replace prop oor:name=Protocols oor:type=oor:string-list value.uno:*/value /prop /node regards, Fabian Feb 8, 2012, at 9:09 AM, fabian wrote: Hi Ariel, You were right that I missed to add the class in the property file. I tried that before but comma separated and forgot to test it again only space separated. Doing this gave me the error that the __getComponent method is missing. I added it and the add-on starts but the __getComponent method isn't called and neither are the __getServiceFactory are the __writeRegistryServiceInfo methods. Do I have to implement any other Interfaces in my Job class so that __getComponent is called? I've tried the component wizard before and faced the same problem as you do under linux. regards, Fabian On Feb 7, 2012, at 8:32 PM, Ariel Constenla-Haile wrote: Hi Fabian, On Tue, Feb 07, 2012 at 06:57:10PM +0100, fabian wrote: This is were I stumble and my Job class wasn't triggered so far. I know that my job shall be registered by __getServiceFactory and __writeRegistryServiceInfo by the set implementatiton name: myaddon.test.InterceptorJob, but I couldn't figure out what is necessary that those methods are called by openoffice. I've seen examples where the XJob implementation is set in the jar manifest as RegistrationClassName and I guess therefor its __getServiceFactory is called. In my generated manifest my addonStarter class is set as RegistrationClass. you might be missing to add the class in nbproject/project-uno.properties : The property registration.classname must list all classes that need to be registered as UNO components, separated by a space: registration.classname=my.impl.Class1 my.impl.Class2 my.impl.Class3 AFAIK if you use the wizard (right click on a package and choose New - Other, in the New File dialog choose OpenOffice.org under Categories and Java UNO Object under File Types, then select the type to implement) the class is added automatically (I can't tell now, it does not work on Linux, the Select Services dialog shows No Types Available). Regards -- Ariel Constenla-Haile La Plata, Argentina
Re: [EXT] image double click
Hi Ariel, sorry for spaming, my Job is finally triggered. It was another stupid mistake in my __getComponentFactory. Thanks a lot for the help! regards, Fabian On Feb 8, 2012, at 9:09 AM, fabian wrote: Hi Ariel, You were right that I missed to add the class in the property file. I tried that before but comma separated and forgot to test it again only space separated. Doing this gave me the error that the __getComponent method is missing. I added it and the add-on starts but the __getComponent method isn't called and neither are the __getServiceFactory are the __writeRegistryServiceInfo methods. Do I have to implement any other Interfaces in my Job class so that __getComponent is called? I've tried the component wizard before and faced the same problem as you do under linux. regards, Fabian On Feb 7, 2012, at 8:32 PM, Ariel Constenla-Haile wrote: Hi Fabian, On Tue, Feb 07, 2012 at 06:57:10PM +0100, fabian wrote: This is were I stumble and my Job class wasn't triggered so far. I know that my job shall be registered by __getServiceFactory and __writeRegistryServiceInfo by the set implementatiton name: myaddon.test.InterceptorJob, but I couldn't figure out what is necessary that those methods are called by openoffice. I've seen examples where the XJob implementation is set in the jar manifest as RegistrationClassName and I guess therefor its __getServiceFactory is called. In my generated manifest my addonStarter class is set as RegistrationClass. you might be missing to add the class in nbproject/project-uno.properties : The property registration.classname must list all classes that need to be registered as UNO components, separated by a space: registration.classname=my.impl.Class1 my.impl.Class2 my.impl.Class3 AFAIK if you use the wizard (right click on a package and choose New - Other, in the New File dialog choose OpenOffice.org under Categories and Java UNO Object under File Types, then select the type to implement) the class is added automatically (I can't tell now, it does not work on Linux, the Select Services dialog shows No Types Available). Regards -- Ariel Constenla-Haile La Plata, Argentina
Re: Default values on Writer
Il 07/02/2012 23.59, RGB ES ha scritto: 2012/1/29 Andrea Pescettipesce...@apache.org: On 22/01/2012 RGB ES wrote: == Context sensitive toolbars == Context sensitive toolbars are a really useful feature but new users tend to not like them because by default they appear on not so useful places... like on top of the table you are trying to edit. IMHO, anchoring by default those toolbars on the bottom of the window will give better user experience. Yes. Even better would be anchoring them on the right hand side, but the page will redraw when they move out of the object... Anyway, I agree that toolbars that get in the way are a common annoyance for users, so they should be anchored by default. == Autocorrect options == There are several autocorrect options that create confusion among new (and not so new) users. On this one I'm less sure: there are probably as many (if not more) users who do rely on these features, and if we disbale them by default we will see a lot of requests on how to enable them. Probably the only one that can be safely considered annoying is Number Recognition in tables. == Word Completion == ... Checking under Tools → AutoCorrect Options → Word Completion tab the option Show as a tip provides a far better user experience and make it more clear that this is a suggestion and not something imposed by Writer. Indeed, this one should really be changed for better usability. == Toolbar buttons == Do we need a Zoom button when we have a nice Zoom toolbar bottom right on the window? Well, not everybody is familiar with the slider, and I don't find it so annoying. What do you think? Better defaults are indeed low-hanging fruits that can make the difference in usability. If we have consensus in changing at least the items listed here, this would already be nice. Regards, Andrea. Another default that needs a change is the page and column break colour (Tools → Options → OpenOffice.org → Appearance). Right now is dark blue and it is difficult to see a page break from the text boundary. A light red will make easier to identify breaks. Cheers Ricardo I'd like adding another change to default options. When the search dialog opens (i.e. pressing CTRL+F on the keybord), the Other options section, by pressing which the dialog window is extended with more available options, is always *closed* by default when the dialog is reopened, even when the user previously selected some extra search options. This behavior can cause a usability issue, because the user can't see and remember at once what Other options are selected, so that the search may fail because, for example, regular expressions are selected, while the user is now looking for a plain text word or symbol. The default behavior should be keeping the search dialog window extended when it opens and the user has previously selected an extra option. Here it is how the current default search window always opens in OOo 3.3: http://www.letturefantastiche.com/romanzi/old_default.jpg Here it is how the default search window should open when the user has previously selected an extra option: http://www.letturefantastiche.com/romanzi/new_default.jpg Regards, -- Gianluca Turconi Lettura gratuita o acquisto di libri e racconti di fantascienza, fantasy, horror, noir, narrativa fantastica e tradizionale: http://www.letturefantastiche.com/
Re: [RELEASE]: source release script
Hi, I forgot yesterday to follow up on this a little bit. I did some further tests and have figured out that ant doesn't do a bad job here. I added targets for creating a zip, tar.gz and tar.bz2 and tested them independently. I did the same test native with zip and tar (on a MacOS system of course) on a directory aoo3.4 containing the relevant files (unzipped the ant created zip file ;-)) Time native: aoo-3.4.zip - 2min 5sec aoo-3.4.tar.gz - 4min 17sec aoo-3.4.tar.bz2 - 9min 20sec Time with ant: aoo-3.4.zip - 2min 46sec aoo-3.4.tar.gz - ~4min aoo-3.4.tar.bz2 - ~10min All 3 output files together with ant takes 14min 28sec The ant script creates one tar and used it for both zip files. Probably the time will be varying on the different platforms but the difference is not huge and I will continue with the ant approach. I have to do a little bit more minor things. File sizes by the way are: aoo-3.4.zip - ~382 MB aoo-3.4.tar.gz - ~330MB aoo-3.4.tar.bz2 - ~260MB I can probably add some signing targets to automate some more things... I have to read the docu for managing releases again. Juergen On 2/7/12 9:34 AM, Jürgen Schmidt wrote: On 2/6/12 7:22 PM, Rob Weir wrote: 2012/2/6 Jürgen Schmidtjogischm...@googlemail.com: Hi, I am currently work on a script to package a source release zip, tar.gz file. The idea is to do it later as part of our build bot builds and without copying files into a tmp directory or so to reflect the final directory structure. At the moment I am playing with an ant script that allows me to zip the necessary directories with an exclude list and to prefix everything with a configurable directory name (e.g aoo-3.4). And it allows me to copy some files like the main/NOTICE file into the new root directory. Is this able to ignore all the hidden .svn folders? yes The structure can look like aoo-3.4/NOTICE aoo-3.4/README aoo-3.4/LICNESE aoo-3.4/... aoo-3.4/main/... aoo-3.4/extras/... aoo-3.4/ext_libraries/... The nice thing with ant is that I can easy convert a generated zip file into a tar.gz file. But ok that takes some time where as creating the zip file was quite fast. Does anybody has a better idea how to do that without copying all the files in a final directory structure or checking out the files into a target directory for example aoo3.4. svn export will bring down the files without the .svn tracking folders. But that is still a separate download. I wonder if ant is jut calling java.io.zip stuff to do the archiving? If so, it might be a lot faster to call a native zip utility. I don't know but creating the zip file only was ok (2 minutes and 46 seconds). The conversion of the zip into tar.gz was incredible slow. It's no option. zipping the unpacked aoo-3.4 directory again takes ~2 minutes. But here we need have to export the sources again in the final directory or copy everything first into the final directory structure. I will do some further test creating tar.gz, tar.bz2 directly. If it's comparable with creating the zip I would say ant is fine for creating the src releases. We can simply add a further target for the build bots. Question: if we do ZIP on Windows, will it preserve the executable bits on files? If not, maybe we want to create the source package only from the Linux buildbot and never on the others. I have to check it, don't know for sure. But I would say that creating the src release on Linux should be enough. Juergen
ANONYMOUS CMS ACCESS (was Re: Bad Link on OOO API Web Page)
I don't know if this level of participation interests you Ric, but I'd like to share with the group the process involved in producing an actual patch suitable for a committer to apply regarding the website documents. The first thing an interested party needs to do is to install the CMS bookmarklet wherever their browser normally keeps bookmarks. The url which describes this process is at https://cms.apache.org/ooo-site/#bookmark You will be prompted for credentials when you visit that url: non-committers should present a username of anonymous and an empty password. Those creds will grant you full access to the CMS. What you do then is go to the actual page in question: http://www.openoffice.org/api/docs/common/ref/com/sun/star/text/module-ix.html and simply click on the bookmarklet. After a few moments to prepare a working copy for you, you will be directed to the source page containing the errant html. Click on the [Edit] link and an editor session will let you modify the file to make the appropriate changes. Submit those changes to the server and click on the [Diff] link which will show you your changes in patch form. On that page is the option to [Mail Diff] whereby you can mail your patch off to this mailing list simply by filling out the form. Yes it's that easy, and committers will know how to incorporate your changes into the live site from there. HTH - Original Message - From: Ric Gaudet ricgau...@hotmail.com To: ooo-dev@incubator.apache.org Cc: Sent: Wednesday, February 8, 2012 1:22 PM Subject: Bad Link on OOO API Web Page Hi, I found a link on this page that is bad: http://www.openoffice.org/api/docs/common/ref/com/sun/star/text/module-ix.html The link is to the tag fieldmaster located in the Nested Modules area The current link: http://www.openoffice.org/api/docs/common/ref/com/sun/star/text/fieldmaster/module-ix.html should instead be: http://www.openoffice.org/api/docs/common/ref/com/sun/star/text/FieldMaster/module-ix.html the difference being FieldMaster vs. fieldmaster. However, since the module's name is actually fieldmaster, perhaps the page url containing that content should instead be lowercase. I am still a beginner to Uno, so I have not yet figured out all the naming conventions (or even how to navigate easily through the API!). Thanks, Ric Gaudet
[PATCH] fieldmaster
Here's the patch for Ric's issue. Index: /trunk/content/api/docs/common/ref/com/sun/star/text/module-ix.html === --- /trunk/content/api/docs/common/ref/com/sun/star/text/module-ix.html (revision 1242052) +++ /trunk/content/api/docs/common/ref/com/sun/star/text/module-ix.html (working copy) @@ -52,7 +52,7 @@ td class=subtitle colspan=2Nested Modules/td /tr tr -td class=imsum_lefta href=fieldmaster/module-ix.htmlfieldmaster/a/td +td class=imsum_lefta href=FieldMaster/module-ix.htmlfieldmaster/a/td td class=imsum_right//tr tr td class=imsum_lefta href=textfield/module-ix.htmltextfield/a/td
Re: [PATCH] fieldmaster
No idea if this is sufficient Ric, but I used the CMS to email this patch as I explained earlier. - Original Message - From: Joe Schaefer j...@apache.org To: ooo-dev@incubator.apache.org Cc: Sent: Wednesday, December 31, 1969 7:00 PM Subject: [PATCH] fieldmaster Here's the patch for Ric's issue. ...
Re: [PATCH] fieldmaster
On Wed, Feb 8, 2012 at 3:22 PM, Joe Schaefer joe_schae...@yahoo.com wrote: No idea if this is sufficient Ric, but I used the CMS to email this patch as I explained earlier. Cool. But unless we have more committers download ooo-site and set up an off-line site build environment, these patches are going to be slow to integrate. I'm guilty as well. I'll find some time to get this set up on my machine. Or is there any easier way to suck these patches into the CMS? For example, it would be really cool if there was an upload/apply patch button in the CMS edit view. That would enable any committer to review and apply site patches, even the ones not comfortable with SVN and command-line tools. -Rob - Original Message - From: Joe Schaefer j...@apache.org To: ooo-dev@incubator.apache.org Cc: Sent: Wednesday, December 31, 1969 7:00 PM Subject: [PATCH] fieldmaster Here's the patch for Ric's issue. ...
Re: [PATCH] fieldmaster
Well no, but the beauty of svn is that you only need to deal with the section of the tree you are interested in. So don't check-out all of ooo-site just to apply this tiny patch- look at the patch to see which directory it applies to and just check-out THAT. Applying the patch is a matter of cd'ing to that directory and running % patch path/to/email/msg.txt % svn commit -m 'apply fieldmaster patch' - Original Message - From: Rob Weir robw...@apache.org To: ooo-dev@incubator.apache.org Cc: Sent: Wednesday, February 8, 2012 9:17 PM Subject: Re: [PATCH] fieldmaster On Wed, Feb 8, 2012 at 3:22 PM, Joe Schaefer joe_schae...@yahoo.com wrote: No idea if this is sufficient Ric, but I used the CMS to email this patch as I explained earlier. Cool. But unless we have more committers download ooo-site and set up an off-line site build environment, these patches are going to be slow to integrate. I'm guilty as well. I'll find some time to get this set up on my machine. Or is there any easier way to suck these patches into the CMS? For example, it would be really cool if there was an upload/apply patch button in the CMS edit view. That would enable any committer to review and apply site patches, even the ones not comfortable with SVN and command-line tools. -Rob - Original Message - From: Joe Schaefer j...@apache.org To: ooo-dev@incubator.apache.org Cc: Sent: Wednesday, December 31, 1969 7:00 PM Subject: [PATCH] fieldmaster Here's the patch for Ric's issue. ...
Re: [PATCH] fieldmaster
In this case there is more than one file to patch in that directory. There are possibly more. I'm committing the following and investigating the rest. Regards, Dave Index: TextFieldMaster-xref.html === --- TextFieldMaster-xref.html (revision 1242205) +++ TextFieldMaster-xref.html (working copy) @@ -41,11 +41,11 @@ td class=subtitleServices which Include this Service/td /tr tr -td::com::sun::star::text::a href=fieldmaster/module-ix.htmlfieldmaster/a::a href=fieldmaster/Bibliography.htmlBibliography/abr -::com::sun::star::text::a href=fieldmaster/module-ix.htmlfieldmaster/a::a href=fieldmaster/Database.htmlDatabase/abr -::com::sun::star::text::a href=fieldmaster/module-ix.htmlfieldmaster/a::a href=fieldmaster/DDE.htmlDDE/abr -::com::sun::star::text::a href=fieldmaster/module-ix.htmlfieldmaster/a::a href=fieldmaster/SetExpression.htmlSetExpression/abr -::com::sun::star::text::a href=fieldmaster/module-ix.htmlfieldmaster/a::a href=fieldmaster/User.htmlUser/abr +td::com::sun::star::text::a href=FieldMaster/module-ix.htmlFieldMaster/a::a href=FieldMaster/Bibliography.htmlBibliography/abr +::com::sun::star::text::a href=FieldMaster/module-ix.htmlFieldMaster/a::a href=FieldMaster/Database.htmlDatabase/abr +::com::sun::star::text::a href=FieldMaster/module-ix.htmlFieldMaster/a::a href=FieldMaster/DDE.htmlDDE/abr +::com::sun::star::text::a href=FieldMaster/module-ix.htmlFieldMaster/a::a href=FieldMaster/SetExpression.htmlSetExpression/abr +::com::sun::star::text::a href=FieldMaster/module-ix.htmlFieldMaster/a::a href=FieldMaster/User.htmlUser/abr /td /tr /table Index: module-ix.html === --- module-ix.html (revision 1242205) +++ module-ix.html (working copy) @@ -52,7 +52,7 @@ td class=subtitle colspan=2Nested Modules/td /tr tr -td class=imsum_lefta href=fieldmaster/module-ix.htmlfieldmaster/a/td +td class=imsum_lefta href=FieldMaster/module-ix.htmlFieldMaster/a/td td class=imsum_right//tr tr td class=imsum_lefta href=textfield/module-ix.htmltextfield/a/td On Feb 8, 2012, at 6:22 PM, Joe Schaefer wrote: Well no, but the beauty of svn is that you only need to deal with the section of the tree you are interested in. So don't check-out all of ooo-site just to apply this tiny patch- look at the patch to see which directory it applies to and just check-out THAT. Applying the patch is a matter of cd'ing to that directory and running % patch path/to/email/msg.txt % svn commit -m 'apply fieldmaster patch' - Original Message - From: Rob Weir robw...@apache.org To: ooo-dev@incubator.apache.org Cc: Sent: Wednesday, February 8, 2012 9:17 PM Subject: Re: [PATCH] fieldmaster On Wed, Feb 8, 2012 at 3:22 PM, Joe Schaefer joe_schae...@yahoo.com wrote: No idea if this is sufficient Ric, but I used the CMS to email this patch as I explained earlier. Cool. But unless we have more committers download ooo-site and set up an off-line site build environment, these patches are going to be slow to integrate. I'm guilty as well. I'll find some time to get this set up on my machine. Or is there any easier way to suck these patches into the CMS? For example, it would be really cool if there was an upload/apply patch button in the CMS edit view. That would enable any committer to review and apply site patches, even the ones not comfortable with SVN and command-line tools. -Rob - Original Message - From: Joe Schaefer j...@apache.org To: ooo-dev@incubator.apache.org Cc: Sent: Wednesday, December 31, 1969 7:00 PM Subject: [PATCH] fieldmaster Here's the patch for Ric's issue. ...
Re: buildbot failure in ASF Buildbot on aoo-win7
On Thu, Feb 09, 2012 at 01:44:31AM +, build...@apache.org wrote: The Buildbot has finished a build on builder aoo-win7 while building ASF Buildbot. Full details are available at: http://ci.apache.org/builders/aoo-win7/builds/38 Buildbot URL: http://ci.apache.org/ Buildslave for this Build: bb-win7 Build Reason: forced: by IRC user arist1 on channel #asftest: with odkseeing if apr-util shakes out or if we have an issue with apu.h dependency The issue is in the patches that generate the gbuild makefiles: They use $(OUTPATH) to point to the build output directory, but looking at the sourced scripts: OUTPATH=wntmsci12 INPATH=wntmsci12.pro On Linux 32 bits: OUTPATH=unxlngi6 INPATH=unxlngi6.pro On Linux 64 bits: OUTPATH=unxlngi6 INPATH=unxlngi6.pro The copy commands fails, the source file to copy does not exist, the directory names misses the .pro part. mkdir -p /cygdrive/y/apache/trunk/main/solver/340/wntmsci12.pro/inc/serf/ /usr/bin/cp --remove-destination --force --preserve=timestamps /cygdrive/y/apache/trunk/ext_libraries/serf/wntmsci12/misc/build/serf-1.0.0/serf.h /cygdrive/y/apache/trunk/main/solver/340/wntmsci12.pro/inc/serf/serf.h /usr/bin/cp: cannot stat `/cygdrive/y/apache/trunk/ext_libraries/serf/wntmsci12/misc/build/serf-1.0.0/serf.h': No such file or directory So it seems $(OUTPUT) should be replaced by $(INPATH). Committed as Revision 1242210 Regards -- Ariel Constenla-Haile La Plata, Argentina pgpYHDUKRbrde.pgp Description: PGP signature
Re: svn commit: r1242207 - in /incubator/ooo/ooo-site/trunk/content/api/docs/common/ref/com/sun/star: beans/XPropertySet-xref.html lang/Locale-xref.html uno/XInterface-xref.html
Sure would be nice to see someone other than Dave be responsive to issues relating to ooo-site pages. It's a MASSIVE site, and there is plenty of work for people to tackle. - Original Message - From: w...@apache.org w...@apache.org To: ooo-comm...@incubator.apache.org Cc: Sent: Wednesday, February 8, 2012 9:55 PM Subject: svn commit: r1242207 - in /incubator/ooo/ooo-site/trunk/content/api/docs/common/ref/com/sun/star: beans/XPropertySet-xref.html lang/Locale-xref.html uno/XInterface-xref.html Author: wave Date: Thu Feb 9 02:55:57 2012 New Revision: 1242207 URL: http://svn.apache.org/viewvc?rev=1242207view=rev Log: Trouble with fieldmaster directories that are actually FieldMaster. Reported by Ric Gaudet on ooo-dev. Additional locations Modified: incubator/ooo/ooo-site/trunk/content/api/docs/common/ref/com/sun/star/beans/XPropertySet-xref.html incubator/ooo/ooo-site/trunk/content/api/docs/common/ref/com/sun/star/lang/Locale-xref.html incubator/ooo/ooo-site/trunk/content/api/docs/common/ref/com/sun/star/uno/XInterface-xref.html Modified: incubator/ooo/ooo-site/trunk/content/api/docs/common/ref/com/sun/star/beans/XPropertySet-xref.html URL: http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/api/docs/common/ref/com/sun/star/beans/XPropertySet-xref.html?rev=1242207r1=1242206r2=1242207view=diff == --- incubator/ooo/ooo-site/trunk/content/api/docs/common/ref/com/sun/star/beans/XPropertySet-xref.html (original) +++ incubator/ooo/ooo-site/trunk/content/api/docs/common/ref/com/sun/star/beans/XPropertySet-xref.html Thu Feb 9 02:55:57 2012 @@ -98,7 +98,7 @@ ::com::sun::star::a href=../chart/module-ix.htmlchart/a::a href=../chart/BarDiagram.htmlBarDiagram/abr ::com::sun::star::a href=../text/module-ix.htmltext/a::a href=../text/BaseFrame.htmlBaseFrame/abr ::com::sun::star::a href=../embed/module-ix.htmlembed/a::a href=../embed/BaseStorage.htmlBaseStorage/abr -::com::sun::star::text::a href=../text/fieldmaster/module-ix.htmlfieldmaster/a::a href=../text/fieldmaster/Bibliography.htmlBibliography/abr +::com::sun::star::text::a href=../text/FieldMaster/module-ix.htmlfieldmaster/a::a href=../text/FieldMaster/Bibliography.htmlBibliography/abr ::com::sun::star::text::a href=../text/textfield/module-ix.htmltextfield/a::a href=../text/textfield/Bibliography.htmlBibliography/abr ::com::sun::star::form::a href=../form/binding/module-ix.htmlbinding/a::a href=../form/binding/BindableControlModel.htmlBindableControlModel/abr ::com::sun::star::form::a href=../form/binding/module-ix.htmlbinding/a::a href=../form/binding/BindableDataAwareControlModel.htmlBindableDataAwareControlModel/abr @@ -173,7 +173,7 @@ ::com::sun::star::text::textfield::a href=../text/textfield/docinfo/module-ix.htmldocinfo/a::a href=../text/textfield/docinfo/Custom.htmlCustom/abr ::com::sun::star::a href=../drawing/module-ix.htmldrawing/a::a href=../drawing/CustomShape.htmlCustomShape/abr ::com::sun::star::a href=../form/module-ix.htmlform/a::a href=../form/DataAwareControlModel.htmlDataAwareControlModel/abr -::com::sun::star::text::a href=../text/fieldmaster/module-ix.htmlfieldmaster/a::a href=../text/fieldmaster/Database.htmlDatabase/abr +::com::sun::star::text::a href=../text/FieldMaster/module-ix.htmlfieldmaster/a::a href=../text/FieldMaster/Database.htmlDatabase/abr ::com::sun::star::text::a href=../text/textfield/module-ix.htmltextfield/a::a href=../text/textfield/Database.htmlDatabase/abr ::com::sun::star::a href=../sdb/module-ix.htmlsdb/a::a href=../sdb/DatabaseAccess.htmlDatabaseAccess/abr ::com::sun::star::a href=../sdb/module-ix.htmlsdb/a::a href=../sdb/DatabaseAccessDataSource.htmlDatabaseAccessDataSource/abr @@ -218,7 +218,7 @@ ::com::sun::star::text::a href=../text/textfield/module-ix.htmltextfield/a::a href=../text/textfield/DateTime.htmlDateTime/abr ::com::sun::star::a href=../presentation/module-ix.htmlpresentation/a::a href=../presentation/DateTimeShape.htmlDateTimeShape/abr ::com::sun::star::a href=../xsd/module-ix.htmlxsd/a::a href=../xsd/Day.htmlDay/abr -::com::sun::star::text::a href=../text/fieldmaster/module-ix.htmlfieldmaster/a::a href=../text/fieldmaster/DDE.htmlDDE/abr +::com::sun::star::text::a href=../text/FieldMaster/module-ix.htmlfieldmaster/a::a href=../text/FieldMaster/DDE.htmlDDE/abr ::com::sun::star::text::a href=../text/textfield/module-ix.htmltextfield/a::a href=../text/textfield/DDE.htmlDDE/abr ::com::sun::star::a href=../xsd/module-ix.htmlxsd/a::a href=../xsd/Decimal.htmlDecimal/abr ::com::sun::star::a href=../text/module-ix.htmltext/a::a href=../text/Defaults.htmlDefaults/abr @@ -405,7 +405,7 @@ ::com::sun::star::a href=../report/module-ix.htmlreport/a::a href=../report/Section.htmlSection/abr ::com::sun::star::a
Re: buildbot failure in ASF Buildbot on aoo-win7
FWIW; --- Mer 8/2/12, Ariel Constenla-Haile arie...@apache.org ha scritto: ... So it seems $(OUTPUT) should be replaced by $(INPATH). Committed as Revision 1242210 The build appears broken here, I updated to the latest SVN but still not joy: http://people.apache.org/~pfg/logs/build-serf.log Entering /usr/ports/editors/openoffice-3-devel/work/ooo/main/sal/rtl/source /usr/bin/ld: cannot find -ldl gmake: *** [libserf-1.la] Error 1 dmake: Error code 2, while making './unxfbsdx.pro/misc/build/so_built_so_serf' Pedro.
Re: buildbot failure in ASF Buildbot on aoo-win7
On 2/8/2012 9:12 PM, Pedro Giffuni wrote: FWIW; --- Mer 8/2/12, Ariel Constenla-Hailearie...@apache.org ha scritto: ... So it seems $(OUTPUT) should be replaced by $(INPATH). Committed as Revision 1242210 The build appears broken here, I updated to the latest SVN but still not joy: http://people.apache.org/~pfg/logs/build-serf.log Entering /usr/ports/editors/openoffice-3-devel/work/ooo/main/sal/rtl/source /usr/bin/ld: cannot find -ldl gmake: *** [libserf-1.la] Error 1 dmake: Error code 2, while making './unxfbsdx.pro/misc/build/so_built_so_serf' Pedro. the patch from Ariel was for the makewin32 patches - looks like a similar change needs to be made for xnix. and btw... Thanks Ariel - the win build has gone through! http://ci.apache.org/builders/aoo-win7/builds/39/steps/shell_4/logs/stdio Andrew
Re: buildbot failure in ASF Buildbot on aoo-win7
Hi Pedro, On Wed, Feb 08, 2012 at 09:12:23PM -0800, Pedro Giffuni wrote: FWIW; --- Mer 8/2/12, Ariel Constenla-Haile arie...@apache.org ha scritto: ... So it seems $(OUTPUT) should be replaced by $(INPATH). Committed as Revision 1242210 The build appears broken here, I updated to the latest SVN but still not joy: http://people.apache.org/~pfg/logs/build-serf.log Entering /usr/ports/editors/openoffice-3-devel/work/ooo/main/sal/rtl/source /usr/bin/ld: cannot find -ldl gmake: *** [libserf-1.la] Error 1 dmake: Error code 2, while making './unxfbsdx.pro/misc/build/so_built_so_serf' Pedro. This error is unrelated. /usr/ports/editors/openoffice-3-devel/work/ooo/main/solver/340/unxfbsdx.pro/lib/apr/libtool --silent --tag=CC --mode=link cc -L/usr/local/lib -rpath /usr/local/serf/lib -o libserf-1.la buckets/aggregate_buckets.lo buckets/request_buckets.lo context.lo buckets/buckets.lo buckets/simple_buckets.lo buckets/file_buckets.lo buckets/mmap_buckets.lo buckets/socket_buckets.lo buckets/response_buckets.lo buckets/headers_buckets.lo buckets/allocator.lo buckets/dechunk_buckets.lo buckets/deflate_buckets.lo buckets/limit_buckets.lo buckets/ssl_buckets.lo buckets/barrier_buckets.lo buckets/chunk_buckets.lo buckets/bwtp_buckets.lo buckets/iovec_buckets.lo incoming.lo outgoing.lo ssltunnel.lo auth/auth.lo auth/auth_basic.lo auth/auth_digest.lo auth/auth_kerb.lo auth/auth_kerb_gss.lo -L/usr/ports/editors/openoffice-3-devel/work/ooo/main/solver/340/unxfbsdx.pro/lib -R/usr/ports/editors/openoffice-3-devel/work/ooo/main/solver/340/unxfbsdx.pro/lib -laprutil-1 -lexpat -lapr-1 -lcrypt -lpthread -lz -lssl -lcrypto -ldl /usr/bin/ld: cannot find -ldl gmake: *** [libserf-1.la] Error 1 dmake: Error code 2, while making './unxfbsdx.pro/misc/build/so_built_so_serf' -ldl will tell ld to look for libdl.so, part of glibc-devel in Fedora. Where is this library installed on your system? Regards -- Ariel Constenla-Haile La Plata, Argentina pgp7e0FnNlp7t.pgp Description: PGP signature
Re: buildbot failure in ASF Buildbot on aoo-win7
--- Gio 9/2/12, Ariel Constenla-Haile arie...@apache.org ha scritto: Da: Ariel Constenla-Haile arie...@apache.org Oggetto: Re: buildbot failure in ASF Buildbot on aoo-win7 A: ooo-dev@incubator.apache.org Data: Giovedì 9 febbraio 2012, 00:55 Hi Pedro, On Wed, Feb 08, 2012 at 09:12:23PM -0800, Pedro Giffuni wrote: FWIW; --- Mer 8/2/12, Ariel Constenla-Haile arie...@apache.org ha scritto: ... So it seems $(OUTPUT) should be replaced by $(INPATH). Committed as Revision 1242210 The build appears broken here, I updated to the latest SVN but still not joy: http://people.apache.org/~pfg/logs/build-serf.log Entering /usr/ports/editors/openoffice-3-devel/work/ooo/main/sal/rtl/source /usr/bin/ld: cannot find -ldl gmake: *** [libserf-1.la] Error 1 dmake: Error code 2, while making './unxfbsdx.pro/misc/build/so_built_so_serf' Pedro. This error is unrelated. /usr/ports/editors/openoffice-3-devel/work/ooo/main/solver/340/unxfbsdx.pro/lib/apr/libtool --silent --tag=CC --mode=link cc -L/usr/local/lib -rpath /usr/local/serf/lib -o libserf-1.la buckets/aggregate_buckets.lo buckets/request_buckets.lo context.lo buckets/buckets.lo buckets/simple_buckets.lo buckets/file_buckets.lo buckets/mmap_buckets.lo buckets/socket_buckets.lo buckets/response_buckets.lo buckets/headers_buckets.lo buckets/allocator.lo buckets/dechunk_buckets.lo buckets/deflate_buckets.lo buckets/limit_buckets.lo buckets/ssl_buckets.lo buckets/barrier_buckets.lo buckets/chunk_buckets.lo buckets/bwtp_buckets.lo buckets/iovec_buckets.lo incoming.lo outgoing.lo ssltunnel.lo auth/auth.lo auth/auth_basic.lo auth/auth_digest.lo auth/auth_kerb.lo auth/auth_kerb_gss.lo -L/usr/ports/editors/openoffice-3-devel/work/ooo/main/solver/340/unxfbsdx.pro/lib -R/usr/ports/editors/openoffice-3-devel/work/ooo/main/solver/340/unxfbsdx.pro/lib -laprutil-1 -lexpat -lapr-1 -lcrypt -lpthread -lz -lssl -lcrypto -ldl /usr/bin/ld: cannot find -ldl gmake: *** [libserf-1.la] Error 1 dmake: Error code 2, while making './unxfbsdx.pro/misc/build/so_built_so_serf' -ldl will tell ld to look for libdl.so, part of glibc-devel in Fedora. Where is this library installed on your system? We dont use glibc, so we dont have it. This is covered by libc so I guess its just a matter f removing -ldl. Will try tomorrow. Thanks, Pedro.
Re: Where is Localization/Translation Now?
Hi imacat, (may I can ask you for your real name) On 2/8/12 6:34 PM, imacat wrote: Dear all, Hi. As the OOo Traditional Chinese translation Lead, I would like to ask whether we have a place for translation now? Or is it still some work in progress? work is ongoing here, we had first problems with restoring the pootle data and second we had to understand how the whole process works. I asked this because I did not see the translation our local Traditional Chinese team made for 3.4 last year. Is there anything I need to do to help it? Once the data is imported in the new pootle server at Apache you can review the available translation. It will be good to know for sure if the data we have now is the latest one. Also, could this page be updated? The latest Traditional Chinese (zh-TW) translation lead is I (imacatima...@mail.imacat.idv.tw), not Horng Victor anymore. At Apache we don't have the same structure as before, means we don't have formal project leads. But we have people who taking ownership for specific tasks and drive these things forward. You can say at Apache you lead by doing ;-) I think the translation work will benefit in the future as well from somebody who will take a coordinating role to manage the translation. The project will benefit from more people taking ownership for specific tasks and it's great to having you on board. Regards Juergen
Re: ANONYMOUS CMS ACCESS (was Re: Bad Link on OOO API Web Page)
Hi, first of all, excuse my top posting here. Thanks Joe for explaining once more the process how we can easy change web-sites using the CMS bookmarklet. I will try it again because I wasn't able to use it until now (on MacOS with Firefox). But anyway the mentioned link problem is part of the generated API reference documentation based on the IDL definitions. I don't think it make sense to edit these automatic generated docu directly. Otherwise the next time we completely replace it (for example with the upcoming 3.4 reference docu) local changes will be overwritten. It's better to submit an bugzilla issue for this kind of problems and assign the issue to me (jsc). Juergen On 2/8/12 8:05 PM, Joe Schaefer wrote: I don't know if this level of participation interests you Ric, but I'd like to share with the group the process involved in producing an actual patch suitable for a committer to apply regarding the website documents. The first thing an interested party needs to do is to install the CMS bookmarklet wherever their browser normally keeps bookmarks. The url which describes this process is at https://cms.apache.org/ooo-site/#bookmark You will be prompted for credentials when you visit that url: non-committers should present a username of anonymous and an empty password. Those creds will grant you full access to the CMS. What you do then is go to the actual page in question: http://www.openoffice.org/api/docs/common/ref/com/sun/star/text/module-ix.html and simply click on the bookmarklet. After a few moments to prepare a working copy for you, you will be directed to the source page containing the errant html. Click on the [Edit] link and an editor session will let you modify the file to make the appropriate changes. Submit those changes to the server and click on the [Diff] link which will show you your changes in patch form. On that page is the option to [Mail Diff] whereby you can mail your patch off to this mailing list simply by filling out the form. Yes it's that easy, and committers will know how to incorporate your changes into the live site from there. HTH - Original Message - From: Ric Gaudetricgau...@hotmail.com To: ooo-dev@incubator.apache.org Cc: Sent: Wednesday, February 8, 2012 1:22 PM Subject: Bad Link on OOO API Web Page Hi, I found a link on this page that is bad: http://www.openoffice.org/api/docs/common/ref/com/sun/star/text/module-ix.html The link is to the tag fieldmaster located in the Nested Modules area The current link: http://www.openoffice.org/api/docs/common/ref/com/sun/star/text/fieldmaster/module-ix.html should instead be: http://www.openoffice.org/api/docs/common/ref/com/sun/star/text/FieldMaster/module-ix.html the difference being FieldMaster vs. fieldmaster. However, since the module's name is actually fieldmaster, perhaps the page url containing that content should instead be lowercase. I am still a beginner to Uno, so I have not yet figured out all the naming conventions (or even how to navigate easily through the API!). Thanks, Ric Gaudet
Re: [PATCH] fieldmaster
On 2/9/12 3:40 AM, Dave Fisher wrote: In this case there is more than one file to patch in that directory. There are possibly more. I'm committing the following and investigating the rest. I mentioned in already in another email, it's a bad example to explain how to make minor changes on our web-sites. The mentioned link problem is on generated page and the source for this comes directly fro our IDL files. And the problem is already fixed in the generated reference docu which is part of the built SDK. I will rpelace the whole IDL refernece when we have the 3.4 available. Juergen Regards, Dave Index: TextFieldMaster-xref.html === --- TextFieldMaster-xref.html (revision 1242205) +++ TextFieldMaster-xref.html (working copy) @@ -41,11 +41,11 @@ td class=subtitleServices which Include this Service/td /tr tr -td::com::sun::star::text::a href=fieldmaster/module-ix.htmlfieldmaster/a::a href=fieldmaster/Bibliography.htmlBibliography/abr -::com::sun::star::text::a href=fieldmaster/module-ix.htmlfieldmaster/a::a href=fieldmaster/Database.htmlDatabase/abr -::com::sun::star::text::a href=fieldmaster/module-ix.htmlfieldmaster/a::a href=fieldmaster/DDE.htmlDDE/abr -::com::sun::star::text::a href=fieldmaster/module-ix.htmlfieldmaster/a::a href=fieldmaster/SetExpression.htmlSetExpression/abr -::com::sun::star::text::a href=fieldmaster/module-ix.htmlfieldmaster/a::a href=fieldmaster/User.htmlUser/abr +td::com::sun::star::text::a href=FieldMaster/module-ix.htmlFieldMaster/a::a href=FieldMaster/Bibliography.htmlBibliography/abr +::com::sun::star::text::a href=FieldMaster/module-ix.htmlFieldMaster/a::a href=FieldMaster/Database.htmlDatabase/abr +::com::sun::star::text::a href=FieldMaster/module-ix.htmlFieldMaster/a::a href=FieldMaster/DDE.htmlDDE/abr +::com::sun::star::text::a href=FieldMaster/module-ix.htmlFieldMaster/a::a href=FieldMaster/SetExpression.htmlSetExpression/abr +::com::sun::star::text::a href=FieldMaster/module-ix.htmlFieldMaster/a::a href=FieldMaster/User.htmlUser/abr /td /tr /table Index: module-ix.html === --- module-ix.html (revision 1242205) +++ module-ix.html (working copy) @@ -52,7 +52,7 @@ td class=subtitle colspan=2Nested Modules/td /tr tr -td class=imsum_lefta href=fieldmaster/module-ix.htmlfieldmaster/a/td +td class=imsum_lefta href=FieldMaster/module-ix.htmlFieldMaster/a/td td class=imsum_right//tr tr td class=imsum_lefta href=textfield/module-ix.htmltextfield/a/td On Feb 8, 2012, at 6:22 PM, Joe Schaefer wrote: Well no, but the beauty of svn is that you only need to deal with the section of the tree you are interested in. So don't check-out all of ooo-site just to apply this tiny patch- look at the patch to see which directory it applies to and just check-out THAT. Applying the patch is a matter of cd'ing to that directory and running % patch path/to/email/msg.txt % svn commit -m 'apply fieldmaster patch' - Original Message - From: Rob Weirrobw...@apache.org To: ooo-dev@incubator.apache.org Cc: Sent: Wednesday, February 8, 2012 9:17 PM Subject: Re: [PATCH] fieldmaster On Wed, Feb 8, 2012 at 3:22 PM, Joe Schaeferjoe_schae...@yahoo.com wrote: No idea if this is sufficient Ric, but I used the CMS to email this patch as I explained earlier. Cool. But unless we have more committers download ooo-site and set up an off-line site build environment, these patches are going to be slow to integrate. I'm guilty as well. I'll find some time to get this set up on my machine. Or is there any easier way to suck these patches into the CMS? For example, it would be really cool if there was an upload/apply patch button in the CMS edit view. That would enable any committer to review and apply site patches, even the ones not comfortable with SVN and command-line tools. -Rob - Original Message - From: Joe Schaeferj...@apache.org To: ooo-dev@incubator.apache.org Cc: Sent: Wednesday, December 31, 1969 7:00 PM Subject: [PATCH] fieldmaster Here's the patch for Ric's issue. ...
Re: [PATCH] fieldmaster
Hi Joe, On 2/9/12 3:22 AM, Joe Schaefer wrote: Well no, but the beauty of svn is that you only need to deal with the section of the tree you are interested in. So don't check-out all of ooo-site just to apply this tiny patch- look at the patch to see which directory it applies to and just check-out THAT. Applying the patch is a matter of cd'ing to that directory and running % patch path/to/email/msg.txt % svn commit -m 'apply fieldmaster patch' I hope you can give me a hint what I am missing... I checked out http://svn.apache.org/viewvc/incubator/ooo/ooo-site/trunk/content/api some time ago and made some changes for example in the index.html (e.g. removed the project lead names) I checked the content locally and check in the index.html. But when I browse the API site my changes are not yet visible there. Which step is missing? Juergen - Original Message - From: Rob Weirrobw...@apache.org To: ooo-dev@incubator.apache.org Cc: Sent: Wednesday, February 8, 2012 9:17 PM Subject: Re: [PATCH] fieldmaster On Wed, Feb 8, 2012 at 3:22 PM, Joe Schaeferjoe_schae...@yahoo.com wrote: No idea if this is sufficient Ric, but I used the CMS to email this patch as I explained earlier. Cool. But unless we have more committers download ooo-site and set up an off-line site build environment, these patches are going to be slow to integrate. I'm guilty as well. I'll find some time to get this set up on my machine. Or is there any easier way to suck these patches into the CMS? For example, it would be really cool if there was an upload/apply patch button in the CMS edit view. That would enable any committer to review and apply site patches, even the ones not comfortable with SVN and command-line tools. -Rob - Original Message - From: Joe Schaeferj...@apache.org To: ooo-dev@incubator.apache.org Cc: Sent: Wednesday, December 31, 1969 7:00 PM Subject: [PATCH] fieldmaster Here's the patch for Ric's issue. ...
