[dev] how to save a state of checkbox after I add a new checkbox into a pane
Hi ,all In my work , I have a problem while want to add some new feature into the ooo. scene : 1) : create a new ooo writer document . 2) : Click menu Format -- Page , the pop up the Page Style : Default dialog .click the header tab . now I want to add a new feature into this tab, in other words , I want to add a new checkbox in this pane so that I can record some configuration . question : how do I store the state of the checkbox which I added in the scene . in other words , where do I add some source code so that the state of the chckbox can be saved . Would anybody give me suggestion about it ? Best Regards Gao Peng E-mail : [EMAIL PROTECTED] Date : 2007-06-22
[dev] question about use XStorage in filter
Hello!nbsp; nbsp; I'm chensuchun.I'm a newbie in devloping filter.I implement a filter for exporting and importing my own format file,whose format is based on odt.But I get some problems about filter. the code of nbsp;function filter( const Sequence PropertyValue rDescriptor ) is following: xDoc = uno::Reference document::XStorageBasedDocument ( mxSrcDoc, uno::UNO_QUERY );nbsp; ///mxSrcDoc is set by setSourceDocument() savenbsp;to a tmp storage use filter writer8 nbsp;nbsp;xSourceStorage = uno::Reference embed::XStorage ( xStorageFactory-createInstance(), nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; uno::UNO_QUERY ); nbsp;nbsp;uno::Sequence beans::PropertyValue afArgs( 1 ); nbsp;nbsp;afArgs[0].Name = ::rtl::OUString::createFromAscii( FilterName ); nbsp;nbsp;afArgs[0].Value = ::rtl::OUString::createFromAscii( writer8 ); nbsp;nbsp;xDoc-storeToStorage( xSourceStorage, afArgs ); add a sub storage to thenbsp;nbsp;xSourceStorage const ::rtl::OUString aSubStorageName ( RTL_CONSTASCII_USTRINGPARAM ( SubStorage ) ); nbsp;nbsp;nbsp;uno::Reference embed::XStorage xSubStorage = nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;xSourceStorage-openStorageElement( aSubStorageName, embed::ElementModes::WRITE ); uno::Reference beans::XPropertySet xSubStoagePro( xSubStorage, uno::UNO_QUERY ); nbsp;nbsp;nbsp;xSubStoagePro-setPropertyValue( OUString::createFromAscii(MediaType), makeAny(OUString::createFromAscii(SubMediaType)) ); .. ///create the target storage uno::Sequence uno::Any aArgs( 2 ); nbsp;aArgs[0] = aURL; get from rDescriptornbsp; nbsp;aArgs[1] = embed::ElementModes::READWRITE; nbsp;uno::Reference embed::XStorage xTargetStorage( nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;xStorageFactory-createInstanceWithArguments( aArgs ), nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; uno::UNO_QUERY ); copy to target storage and commit xSourceStorage-copyToStorage( xTargetStorage ); nbsp;nbsp;nbsp;bRet = sal_True; nbsp;nbsp;nbsp;uno::Reference XTransactedObject xTransaction = nbsp;nbsp;nbsp;nbsp;uno::Reference XTransactedObject ( xTargetStorage, UNO_QUERY ); nbsp;nbsp;nbsp;if( xTransaction.is() ) nbsp;nbsp;nbsp;nbsp;xTransaction-commit(); /dispose them uno::Reference lang::XComponent xComponent1( xSourceStorage, uno::UNO_QUERY ); nbsp;nbsp;nbsp;OSL_ENSURE( !xSourceStorage.is() || xComponent1.is(), Wrong storage implementation! ); nbsp;nbsp;nbsp;if ( xComponent1.is() ) nbsp;nbsp;nbsp;nbsp;xComponent1-dispose(); nbsp;nbsp;nbsp;uno::Reference lang::XComponent xComponent2( xTargetStorage, uno::UNO_QUERY ); nbsp;nbsp;nbsp;OSL_ENSURE( !xTargetStorage.is() || xComponent2.is(), Wrong storage implementation! ); nbsp;nbsp;nbsp;if ( xComponent2.is() ) nbsp;nbsp;nbsp;nbsp;xComponent2-dispose(); End After the execution of filter( const Sequence PropertyValue rDescriptor ), the target file is created and the size of the file is about 7K. But afternbsp; executing the following code in sal_Bool SfxObjectShell::SaveTo_Impl: nbsp;nbsp;// transfer data to its destinated location nbsp;nbsp;// the medium commits the storage or the stream it is based on nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; RegisterTransfer( rMedium ); nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; bOk = rMedium.Commit(); the target file becomes 0K. Why?nbsp; Is some thing wrong in my filter( const Sequence PropertyValue rDescriptor ) function? what should I do with the XStorage ?nbsp; Any help and sugestion in identifying the missing pieces is appreciated. Thanks nbsp;nbsp; --- 特价限量商品限时抢购,8元起!( http://d1.sina.com.cn/sina/limeng3/mail_zhuiyu/2007/mail_zhuiyu_20070620.html ) === 注册新浪2G免费邮箱( http://mail.sina.com.cn/chooseMode.html )
Re: [dev] Variables and Input Fields
On 22 June 2007 06:49, Sigrid Kronenberger wrote: As far as I know, SuSE adds some patches to its version, so it might be, that this is a bug in the SuSE version, that is not in the original OOo. Hi Sigrid, Maybe that is the answer. The Windows version that I tried is the original one, but in Linux I'm using the SuSE/Novell version, both 2.0 and 2.2.1. I also might add that the Input and User Fields work as aspect in the SuSE version. I'll tried the original version in SuSE; just to clear the issue. -- Regards, Lívio Cipriano - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Variables and Input Fields
On 22 June 2007 09:39, Lívio Cipriano wrote: I'll tried the original version in SuSE; just to clear the issue. Done. The bug disappeared. I'll report it to SuSE. -- Regards, Lívio Cipriano - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[dev] Could the line numbering issue be targeted for OOo 2.3?
Hi, is it possible to target the annoying line numbering issue for OOo 2.3? http://www.openoffice.org/issues/show_bug.cgi?id=78254 This issue is primarly annoying for students. Because they often need to write long documents with tables and line numbering. Best regards, Axel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Could the line numbering issue be targeted for OOo 2.3?
Frank Meies schrieb: Hi Axel, Hi Frank, On 22.06.2007 12:33, Axel Reimer wrote: is it possible to target the annoying line numbering issue for OOo 2.3? http://www.openoffice.org/issues/show_bug.cgi?id=78254 This issue is primarly annoying for students. Because they often need to write long documents with tables and line numbering. I'll have a look. Thank you for the instant answer. It would be great. Axel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[dev] filter selection
Hi All, ??? I have small problem on embedded linux(arch=i386), when I open the openoffice-2.2.1 or 2.0.1 ./swriter ??? it ask for filter selection-text(openoffice.org writer/web) instead of ??? displaying the content of the file it display's? content of the file type , I using .doc , But the .xls,.ppt works fine ?? My second problem is I am unable to save the .doc , it give's me ?? general error input/output , but iam able to save .xls,.ppt , ?? Anybody please point me where exactly I went wrong , does i need add any package, ?? or how do I debug it . ??? Note : I have already sent the mail to [EMAIL PROTECTED] but unable to solve it Regards, Hemanth ? Check out the new AOL.in. Get your free email, keep in touch with friends and family using AOL Messenger and stay up to date with the latest in News, Cricket, Bollywood, Music and much more!
[dev] Integrate patch for issue 29646 ( WW8: some foreign date formats converted to June yyyy)
Hi all, could someone integrate the patch of this issue for OOo 2.3: WW8: some foreign date formats converted to June http://www.openoffice.org/issues/show_bug.cgi?id=29646 As it is the most known OOo issue in France, if someone in the writer team could integrate it, this would really be a huge release. Thanks, -- Pierre-André Galmes Free Software consultant StarXpert - www.starxpert.fr 6, rue Eugène Varlin - 75010 Paris
Re: [dev] Integrate patch for issue 29646 ( WW8: some foreign date formats converted to June yyyy)
PA Galmes wrote: Hi all, could someone integrate the patch of this issue for OOo 2.3: WW8: some foreign date formats converted to June http://www.openoffice.org/issues/show_bug.cgi?id=29646 As it is the most known OOo issue in France, if someone in the writer team could integrate it, this would really be a huge release. Thanks, Hi, I will have a look - the owner of this issue is currently on vacation. Regards, Oliver. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] 470 versions in issuezilla, can we drop a couple of hundred ?
On 2007.06.22. 16:45, Caolan McNamara wrote: There are 470, four hundred and seventy! versions listed by issuezilla for e.g. tools. Can we cull these to at least remove all the milestones current - 5, and consider dropping the release candidates and the 1.0.X releases. this would be awesome. i've mentioned this a couple of times here and there, but that lead to nothing :) it's not like anybody would accept a bugreport for 99% of those versions anyway... and it is a pain to find the correct version in a huge dropdown. thanks for bringing this up again :) Who's the contact for the versions, collabnet ? C. -- Rich - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] RE:[dev] question about use XStorage in filter
The bad format is obviously caused by your mail program. I doubt that anyone will read the bad formatted mail, at least I can't stand it. Sorry, it's too time consuming to read it. Please try to repost your mail with a better mail program. My recommendation would be Thunderbird (http://www.mozilla.com/en-US/thunderbird/). Best regards, Mathias [EMAIL PROTECTED] schrieb: Oh sorry!I don't know why the letter become so ugly. nbsp; Hello!nbsp; nbsp; I'm chensuchun.I'm a newbie in devloping filter.I implement a filter for exporting and importing my own format file,whose format is based on odt.But I get some problems about filter. the code of nbsp;function filter( const Sequence PropertyValue rDescriptor ) is following: xDoc = uno::Reference document::XStorageBasedDocument ( mxSrcDoc, uno::UNO_QUERY );nbsp; ///mxSrcDoc is set by setSourceDocument() savenbsp;to a tmp storage use filter writer8 nbsp;nbsp;xSourceStorage = uno::Reference embed::XStorage ( xStorageFactory-createInstance(), nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; uno::UNO_QUERY ); nbsp;nbsp;uno::Sequence beans::PropertyValue afArgs( 1 ); nbsp;nbsp;afArgs[0].Name = ::rtl::OUString::createFromAscii( FilterName ); nbsp;nbsp;afArgs[0].Value = ::rtl::OUString::createFromAscii( writer8 ); nbsp;nbsp;xDoc-storeToStorage( xSourceStorage, afArgs ); add a sub storage to thenbsp;nbsp;xSourceStorage const ::rtl::OUString aSubStorageName ( RTL_CONSTASCII_USTRINGPARAM ( SubStorage ) ); nbsp;nbsp;nbsp;uno::Reference embed::XStorage xSubStorage = nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;xSourceStorage-openStorageElement( aSubStorageName, embed::ElementModes::WRITE ); uno::Reference beans::XPropertySet xSubStoagePro( xSubStorage, uno::UNO_QUERY ); nbsp;nbsp;nbsp;xSubStoagePro-setPropertyValue( OUString::createFromAscii(MediaType), makeAny(OUString::createFromAscii(SubMediaType)) ); .. ///create the target storage uno::Sequence uno::Any aArgs( 2 ); nbsp;aArgs[0] = aURL; get from rDescriptornbsp; nbsp;aArgs[1] = embed::ElementModes::READWRITE; nbsp;uno::Reference embed::XStorage xTargetStorage( nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;xStorageFactory-createInstanceWithArguments( aArgs ), nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; uno::UNO_QUERY ); copy to target storage and commit xSourceStorage-copyToStorage( xTargetStorage ); nbsp;nbsp;nbsp;bRet = sal_True; nbsp;nbsp;nbsp;uno::Reference XTransactedObject xTransaction = nbsp;nbsp;nbsp;nbsp;uno::Reference XTransactedObject ( xTargetStorage, UNO_QUERY ); nbsp;nbsp;nbsp;if( xTransaction.is() ) nbsp;nbsp;nbsp;nbsp;xTransaction-commit(); /dispose them uno::Reference lang::XComponent xComponent1( xSourceStorage, uno::UNO_QUERY ); nbsp;nbsp;nbsp;OSL_ENSURE( !xSourceStorage.is() || xComponent1.is(), Wrong storage implementation! ); nbsp;nbsp;nbsp;if ( xComponent1.is() ) nbsp;nbsp;nbsp;nbsp;xComponent1-dispose(); nbsp;nbsp;nbsp;uno::Reference lang::XComponent xComponent2( xTargetStorage, uno::UNO_QUERY ); nbsp;nbsp;nbsp;OSL_ENSURE( !xTargetStorage.is() || xComponent2.is(), Wrong storage implementation! ); nbsp;nbsp;nbsp;if ( xComponent2.is() ) nbsp;nbsp;nbsp;nbsp;xComponent2-dispose(); End After the execution of filter( const Sequence PropertyValue rDescriptor ), the target file is created and the size of the file is about 7K. But afternbsp; executing the following code in sal_Bool SfxObjectShell::SaveTo_Impl: nbsp;nbsp;// transfer data to its destinated location nbsp;nbsp;// the medium commits the storage or the stream it is based on nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; RegisterTransfer( rMedium ); nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; bOk = rMedium.Commit(); the target file becomes 0K. Why?nbsp; Is some thing wrong in my filter( const Sequence PropertyValue rDescriptor ) function? what should I do with the XStorage ?nbsp; Any help and sugestion in identifying the missing pieces is appreciated. Thanks nbsp;nbsp; --- 特价限量商品限时抢购,8元起!( http://d1.sina.com.cn/sina/limeng3/mail_zhuiyu/2007/mail_zhuiyu_20070620.html ) === 注册新浪2G免费邮箱( http://mail.sina.com.cn/chooseMode.html ) -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to [EMAIL PROTECTED]. I use it for the OOo lists and only rarely read other mails sent to it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] Suggestion
Hi Andrew, Andrew Douglas Pitonyak schrieb: http://www.openoffice.org/issues/show_bug.cgi?id=1761 Do I understand correctly that this will be fixed in 2.3? This is fixed completely for all documents with a unique page width. In case of a document with non-unique page widths the widest page is centered and the other pages are left aligned to it. We did that for two reasons: - the effort to center every single page was a lot higher and we thought it is better to do first what we can implement comparably fast; - it's still unclear whether centering every single page would be a good idea anyway. Some people find this jagged left border irritating and prefer that all pages have a common left border. As mentioned in the issue 1761 the ability to center every single page will be a side effect of implementing issue 1598. So once we will have done that we will restart the discussion whether having a unique left border is more important or less important than having every page centered. Ciao, Mathias -- Mathias Bauer (mba) - Project Lead OpenOffice.org Writer OpenOffice.org Engineering at Sun: http://blogs.sun.com/GullFOSS Please don't reply to [EMAIL PROTECTED]. I use it for the OOo lists and only rarely read other mails sent to it. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] RE:[dev] question about use XStorage in filter
Seeing all the 'nbsp;' : maybe switching from HTML to plain text might help? Regards, Cor Mathias Bauer wrote: The bad format is obviously caused by your mail program. I doubt that anyone will read the bad formatted mail, at least I can't stand it. Sorry, it's too time consuming to read it. Please try to repost your mail with a better mail program. My recommendation would be Thunderbird (http://www.mozilla.com/en-US/thunderbird/). Best regards, Mathias [EMAIL PROTECTED] schrieb: Oh sorry!I don't know why the letter become so ugly. nbsp; Hello!nbsp; nbsp; I'm chensuchun.I'm a newbie in devloping filter.I implement a filter for exporting and importing my own format file,whose format is based on odt.But I get some problems about filter. the code of nbsp;function filter( const Sequence PropertyValue rDescriptor ) is following: xDoc = uno::Reference document::XStorageBasedDocument ( mxSrcDoc, uno::UNO_QUERY );nbsp; ///mxSrcDoc is set by setSourceDocument() savenbsp;to a tmp storage use filter writer8 nbsp;nbsp;xSourceStorage = uno::Reference embed::XStorage ( xStorageFactory-createInstance(), nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; uno::UNO_QUERY ); nbsp;nbsp;uno::Sequence beans::PropertyValue afArgs( 1 ); nbsp;nbsp;afArgs[0].Name = ::rtl::OUString::createFromAscii( FilterName ); nbsp;nbsp;afArgs[0].Value = ::rtl::OUString::createFromAscii( writer8 ); nbsp;nbsp;xDoc-storeToStorage( xSourceStorage, afArgs ); add a sub storage to thenbsp;nbsp;xSourceStorage const ::rtl::OUString aSubStorageName ( RTL_CONSTASCII_USTRINGPARAM ( SubStorage ) ); nbsp;nbsp;nbsp;uno::Reference embed::XStorage xSubStorage = nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;xSourceStorage-openStorageElement( aSubStorageName, embed::ElementModes::WRITE ); uno::Reference beans::XPropertySet xSubStoagePro( xSubStorage, uno::UNO_QUERY ); nbsp;nbsp;nbsp;xSubStoagePro-setPropertyValue( OUString::createFromAscii(MediaType), makeAny(OUString::createFromAscii(SubMediaType)) ); .. ///create the target storage uno::Sequence uno::Any aArgs( 2 ); nbsp;aArgs[0] = aURL; get from rDescriptornbsp; nbsp;aArgs[1] = embed::ElementModes::READWRITE; nbsp;uno::Reference embed::XStorage xTargetStorage( nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;xStorageFactory-createInstanceWithArguments( aArgs ), nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; uno::UNO_QUERY ); copy to target storage and commit xSourceStorage-copyToStorage( xTargetStorage ); nbsp;nbsp;nbsp;bRet = sal_True; nbsp;nbsp;nbsp;uno::Reference XTransactedObject xTransaction = nbsp;nbsp;nbsp;nbsp;uno::Reference XTransactedObject ( xTargetStorage, UNO_QUERY ); nbsp;nbsp;nbsp;if( xTransaction.is() ) nbsp;nbsp;nbsp;nbsp;xTransaction-commit(); /dispose them uno::Reference lang::XComponent xComponent1( xSourceStorage, uno::UNO_QUERY ); nbsp;nbsp;nbsp;OSL_ENSURE( !xSourceStorage.is() || xComponent1.is(), Wrong storage implementation! ); nbsp;nbsp;nbsp;if ( xComponent1.is() ) nbsp;nbsp;nbsp;nbsp;xComponent1-dispose(); nbsp;nbsp;nbsp;uno::Reference lang::XComponent xComponent2( xTargetStorage, uno::UNO_QUERY ); nbsp;nbsp;nbsp;OSL_ENSURE( !xTargetStorage.is() || xComponent2.is(), Wrong storage implementation! ); nbsp;nbsp;nbsp;if ( xComponent2.is() ) nbsp;nbsp;nbsp;nbsp;xComponent2-dispose(); End After the execution of filter( const Sequence PropertyValue rDescriptor ), the target file is created and the size of the file is about 7K. But afternbsp; executing the following code in sal_Bool SfxObjectShell::SaveTo_Impl: nbsp;nbsp;// transfer data to its destinated location nbsp;nbsp;// the medium commits the storage or the stream it is based on nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; RegisterTransfer( rMedium ); nbsp;nbsp;nbsp;nbsp;nbsp;nbsp;nbsp; bOk = rMedium.Commit(); the target file becomes 0K. Why?nbsp; Is some thing wrong in my filter( const Sequence PropertyValue rDescriptor ) function? what should I do with the XStorage ?nbsp; Any help and sugestion in identifying the missing pieces is appreciated. Thanks nbsp;nbsp; --- 特价限量商品限时抢购,8元起!( http://d1.sina.com.cn/sina/limeng3/mail_zhuiyu/2007/mail_zhuiyu_20070620.html ) === 注册新浪2G免费邮箱( http://mail.sina.com.cn/chooseMode.html ) -- Cor Nouws Arnhem - Netherlands nl.OpenOffice.org - marketing contact - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] 470 versions in issuezilla, can we drop a couple of hundred ?
On Fri, 2007-06-22 at 20:01 +0200, Frank Schönheit - Sun Microsystems Germany wrote: Hi Caolan, There are 470, four hundred and seventy! versions listed by issuezilla for e.g. tools. way too much, agreed. The better solution would be if Version was a free-text field, but alas ... Can we cull these to at least remove all the milestones current - 5, and consider dropping the release candidates and the 1.0.X releases. What would we do then with the issues which currently have one of those versions set? We cannot simply remove the versions, this would violate the data integrity. We would have to reset this field for the affected issues. I'd hope that we could just remove the ability to *add* new bugs against those milestones. i.e. that we'd just list the last couple of milestones and the actual releases as options on the bug submission pages. I'm all for leaving the current version that bugs are logged against untouched. C. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [dev] 470 versions in issuezilla, can we drop a couple of hundred ?
Can we cull these to at least remove all the milestones current - 5, and consider dropping the release candidates and the 1.0.X releases. What would we do then with the issues which currently have one of those versions set? We cannot simply remove the versions, this would violate the data integrity. We would have to reset this field for the affected issues. How about just changing the UI on the website? We could make it so that normally only the active versions would be displayed in the scrolling list, but somewhere there would be a checkbox or other option to make it display all versions. In the search screen, we could also add some meta-versions to the list, i.e., Any version, Any v1.x, Any v2.x, etc. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [dev] 470 versions in issuezilla, can we drop a couple of hundred ?
Hi Allen, How about just changing the UI on the website? We could make it so that normally only the active versions would be displayed in the scrolling list, but somewhere there would be a checkbox or other option to make it display all versions. In the search screen, we could also add some meta-versions to the list, i.e., Any version, Any v1.x, Any v2.x, etc. Unfortunately, things like this require changes to the IssueZilla installation. Since IssueZilla effectively is in maintainance mode only at collab.net (future version of CEE, the web hosting package provided by collab.net, on which OOo is running, will contain another bug tracking system), chances are rather low ... Even it it weren't, chances as you describe them are difficult to do in an alive production system, we would probably have to wait for a next verions, anyway. Ciao Frank -- - Frank Schönheit, Software Engineer [EMAIL PROTECTED] - - Sun Microsystems http://www.sun.com/staroffice - - OpenOffice.org Base http://dba.openoffice.org - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]