Re: Issue DRAW has with Microsoft SNIP in Win 11
I suggest you turn off the Suggested Actions in the clipboard manager. Here is a quote from a post on the user forum dealing with a Copy/Paste problem in Calc: > Windows 11 has a new Clipboard Manager - go to Start > Settings, Click > Clipboard on the System tab and turn off *Suggested Actions*; if that > doesn't help, try turning off *Clipboard History* > I hope that helps. Regards, Francis On Mon, Nov 27, 2023 at 9:59 PM Newforce Pty Ltd wrote: > Dear Open Office > Every time I try to take a SNIP using Win 11 Snipping Tool it will not > PASTE into a O'Office DRAW page. > Immediately I click PASTE the Open Office goes in to recovery mode, the > page goes pale and the application wants to do a recovery and send reports > to Microsoft. > This is totally frustrating and infuriating as I lose all my work. > So what I do is paste the snip to PAINT and then copy this and try to paste > to DRAW. That works but as soon as I try to PRINT, the application page > goes pale and enters recovery again. Meaning I lose all my work. > When it does eventually 'recover' the page is totally blank without > recovering my work.. > HOW DO I FIX THIS ? > Yours faithfully, > Mr G Douglas - Newforce Pty Ltd >
Issue DRAW has with Microsoft SNIP in Win 11
Dear Open Office Every time I try to take a SNIP using Win 11 Snipping Tool it will not PASTE into a O'Office DRAW page. Immediately I click PASTE the Open Office goes in to recovery mode, the page goes pale and the application wants to do a recovery and send reports to Microsoft. This is totally frustrating and infuriating as I lose all my work. So what I do is paste the snip to PAINT and then copy this and try to paste to DRAW. That works but as soon as I try to PRINT, the application page goes pale and enters recovery again. Meaning I lose all my work. When it does eventually 'recover' the page is totally blank without recovering my work.. HOW DO I FIX THIS ? Yours faithfully, Mr G Douglas - Newforce Pty Ltd
RE: API doc on web site [Was: Accessing the comment object (annotation) in Draw/Impress via API]
> -Original Message- > From: Peter Kovacs [mailto:pe...@apache.org] > Sent: Sunday, October 24, 2021 9:42 PM > To: dev@openoffice.apache.org > Subject: Re: API doc on web site [Was: Accessing the comment > object (annotation) in Draw/Impress via API] > > The question of what "compatible" actually means is by no > means easy to answer. > > > > Example: Perhaps there is a property, method, etc. in the > API that accidentally has a spelling mistake in its name (I > recently had something like this in LO regarding a parameter > of a Posgresql access) - on the one hand, one can then argue > that a name correction that does not change the actual > function would be compatible, but one can also argue that it > is incompatible because only the old naming (which is > possibly already used a lot in projects) no longer works. > > I define Incompatible on User API level if the API user has to change > his work, as a result of changes in a release. OK, but what helps and your (or my) definition? We need a definition that everyone recognises, especially the PMC because they have the power to decide on releases. But I repeat myself: your statements about major, minor and micro releases, and that API changes should only be made in major releases, make sense and are recognised (I think by everyone). So why should we want to violate them? greetings, Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: API doc on web site [Was: Accessing the comment object (annotation) in Draw/Impress via API]
On 24.10.21 20:57, Jörg Schmidt wrote: -Original Message- From: Peter Kovacs [mailto:pe...@apache.org] Sent: Sunday, October 24, 2021 2:19 PM To: dev@openoffice.apache.org Subject: Re: API doc on web site [Was: Accessing the comment object (annotation) in Draw/Impress via API] Hi Jörg, Check: Version Number Assignment (Apache OpenOffice internal) Structure .. Explanation : huge release with visible changes and new features including incompatible API changes if necessary. Translation updates are most often necessary to address the UI visible changes. : smaller improvements of features that don't need any translation. And of course any kind of bug fixes. : only selected bug fixes and most often only critical ones. This includes any potential security issues. From: https://cwiki.apache.org/confluence/display/OOOUSERS/Releases Yes, agreed. That is the current policy. So well as long as compatible we could Change the API with a minor Release. I see no need and no justification for watering down clear rules/explanations. The question of what "compatible" actually means is by no means easy to answer. Example: Perhaps there is a property, method, etc. in the API that accidentally has a spelling mistake in its name (I recently had something like this in LO regarding a parameter of a Posgresql access) - on the one hand, one can then argue that a name correction that does not change the actual function would be compatible, but one can also argue that it is incompatible because only the old naming (which is possibly already used a lot in projects) no longer works. I define Incompatible on User API level if the API user has to change his work, as a result of changes in a release. -- This is the Way! http://www.apache.org/theapacheway/index.html - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: API doc on web site [Was: Accessing the comment object (annotation) in Draw/Impress via API]
> -Original Message- > From: Peter Kovacs [mailto:pe...@apache.org] > Sent: Sunday, October 24, 2021 2:19 PM > To: dev@openoffice.apache.org > Subject: Re: API doc on web site [Was: Accessing the comment > object (annotation) in Draw/Impress via API] > > Hi Jörg, > > Check: > > > Version Number Assignment (Apache OpenOffice internal) > > > Structure > > .. > > > Explanation > > : huge release with visible changes and new features including > incompatible API changes if necessary. Translation updates are most > often necessary to address the UI visible changes. > > : smaller improvements of features that don't need any > translation. And of course any kind of bug fixes. > > : only selected bug fixes and most often only critical > ones. This > includes any potential security issues. > > From: https://cwiki.apache.org/confluence/display/OOOUSERS/Releases Yes, agreed. > That is the current policy. So well as long as compatible we could > Change the API with a minor Release. I see no need and no justification for watering down clear rules/explanations. The question of what "compatible" actually means is by no means easy to answer. Example: Perhaps there is a property, method, etc. in the API that accidentally has a spelling mistake in its name (I recently had something like this in LO regarding a parameter of a Posgresql access) - on the one hand, one can then argue that a name correction that does not change the actual function would be compatible, but one can also argue that it is incompatible because only the old naming (which is possibly already used a lot in projects) no longer works. greetings, Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: API doc on web site [Was: Accessing the comment object (annotation) in Draw/Impress via API]
Hi Jörg, Check: Version Number Assignment (Apache OpenOffice internal) Structure .. Explanation : huge release with visible changes and new features including incompatible API changes if necessary. Translation updates are most often necessary to address the UI visible changes. : smaller improvements of features that don't need any translation. And of course any kind of bug fixes. : only selected bug fixes and most often only critical ones. This includes any potential security issues. From: https://cwiki.apache.org/confluence/display/OOOUSERS/Releases That is the current policy. So well as long as compatible we could Change the API with a minor Release. It seems I got the detail wrong. All the best Peter On 19.10.21 15:30, Jörg Schmidt wrote: Hello Carl, -Original Message- From: Carl Marcum [mailto:cmar...@apache.org] Sent: Tuesday, October 19, 2021 1:13 PM To:dev@openoffice.apache.org Subject: Re: API doc on web site [Was: Accessing the comment object (annotation) in Draw/Impress via API] Actually we do provide updated documentation included in the SDK with each convenience binary release. It can be found on Linux at /opt/openoffice4/sdk/docs/common/ref/module-ix.html if the SDK is installed. Knowing that we can't make API changes like adding or deprecating methods or things like that in a minor version change, Is this a principle that _all_ those involved in releases will also _reliably_ follow? It's up to us to inform new contributors who may make such a mistake if it were to happen. yes, but ... As far as I know, only the PMC has the right to decide about the release of a release - so will the PMC reliably support the mentioned principle (='API changes not in a minor release')? I would appreciate a clear "yes" or "no" on this. And please allow me to say that the current formal minor release of AOO is "4.1", so, respecting the implied principle, a change to the API is thus not allowed until version 5.0.0. greetings, Jörg - To unsubscribe, e-mail:dev-unsubscr...@openoffice.apache.org For additional commands, e-mail:dev-h...@openoffice.apache.org -- This is the Way! http://www.apache.org/theapacheway/index.html
RE: API doc on web site [Was: Accessing the comment object (annotation) in Draw/Impress via API]
Hello Carl, > -Original Message- > From: Carl Marcum [mailto:cmar...@apache.org] > Sent: Tuesday, October 19, 2021 1:13 PM > To: dev@openoffice.apache.org > Subject: Re: API doc on web site [Was: Accessing the comment > object (annotation) in Draw/Impress via API] > >> Actually we do provide updated documentation included in > the SDK with > >> each convenience binary release. > >> It can be found on Linux at > >> /opt/openoffice4/sdk/docs/common/ref/module-ix.html > >> if the SDK is installed. > >> > >> Knowing that we can't make API changes like adding or deprecating > >> methods or things like that in a minor version change, > > Is this a principle that _all_ those involved in releases > will also _reliably_ follow? > > It's up to us to inform new contributors who may make such a > mistake if > it were to happen. yes, but ... As far as I know, only the PMC has the right to decide about the release of a release - so will the PMC reliably support the mentioned principle (='API changes not in a minor release')? I would appreciate a clear "yes" or "no" on this. And please allow me to say that the current formal minor release of AOO is "4.1", so, respecting the implied principle, a change to the API is thus not allowed until version 5.0.0. greetings, Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: API doc on web site [Was: Accessing the comment object (annotation) in Draw/Impress via API]
Hi Jörg, On 10/19/21 4:26 AM, Jörg Schmidt wrote: -Original Message- From: Carl Marcum [mailto:cmar...@apache.org] Sent: Tuesday, October 19, 2021 3:59 AM To: dev@openoffice.apache.org Subject: Re: API doc on web site [Was: Accessing the comment object (annotation) in Draw/Impress via API] Hi All, On 10/17/21 5:17 PM, Peter Kovacs wrote: Hi Jörg, On 17.10.21 19:48, Jörg Schmidt wrote: Hello Peter, -Original Message- From: Peter Kovacs [mailto:pe...@apache.org] Sent: Sunday, October 17, 2021 11:27 AM To: dev@openoffice.apache.org Subject: Re: API doc on web site [Was: Accessing the comment object (annotation) in Draw/Impress via API] Hi Jörg, I am not sure what you refer to. I refer to the fact that changes in the API documentation are marked in time (the typical entry is "since ..."), so that the API documentation can be used in practice for all program versions. I think we are on the same page if we want to change the API, but I think this is not the topic. The documentation has no influence on backward compatibility. right. What I am referring to is only that we should not make changes if the QA is not 100% guaranteed. And what I currently experience is that there is a tiny(!) problem in the API documentation, but immediately demanded now to regularly renew the documentation routinely. Again this is relevant if we change the API itself. Explain to me bitterly where there are at all changes in the API that would make it necessary to update the documentation inflationary frequently? I follow every release carefully, only from API changes I have not noticed for years. The API Documentation is extracted from the Code. For example the comment in http://opengrok.openoffice.org/xref/aoo41x/main/offapi/com/sun /star/modules.idl?r=d1766043#83 does have an impact on the web page: https://www.openoffice.org/api/docs/common/ref/com/sun/star/of fice/module-ix.html I hope you see both documentations are linked. So when do we update the documentation on the web site? Currently we will never update the web site, and the danger is that if we change a comment in the documentation it will not end up on the website.. So Arrigos Idea is to update with each release. This would keep the documentation on the web in sync with the latest Code released for this API Version (Which should roughly correspond with the major release). It makes sense to publish on the website which Code the extraction has been taken from and what Versions the Documentation relates to. On an API Change, QA and documentation Versions need to be discussed. But we can discuss this when we get near to a API Change. I think until then we have done some steps in respect of QA. Carl is working on improvements, and I would like to try if we can establish a UI check with UI Path or similar tool. All the best Peter Actually we do provide updated documentation included in the SDK with each convenience binary release. It can be found on Linux at /opt/openoffice4/sdk/docs/common/ref/module-ix.html if the SDK is installed. Knowing that we can't make API changes like adding or deprecating methods or things like that in a minor version change, Is this a principle that _all_ those involved in releases will also _reliably_ follow? It's up to us to inform new contributors who may make such a mistake if it were to happen. On the whole question of API and documentation, I would like to make a general appeal to all of us: The fact that OpenOffice could not be displaced by LibreOffice is largely due to the good quality of OO. We must do everything we can to preserve this quality and not compromise in this regard. In this context, we must also be ready to examine, critically discuss and improve our activities again and again. I very much agree. Best regards, Carl 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: API doc on web site [Was: Accessing the comment object (annotation) in Draw/Impress via API]
> -Original Message- > From: Carl Marcum [mailto:cmar...@apache.org] > Sent: Tuesday, October 19, 2021 3:59 AM > To: dev@openoffice.apache.org > Subject: Re: API doc on web site [Was: Accessing the comment > object (annotation) in Draw/Impress via API] > > Hi All, > > On 10/17/21 5:17 PM, Peter Kovacs wrote: > > Hi Jörg, > > > > On 17.10.21 19:48, Jörg Schmidt wrote: > >> Hello Peter, > >> > >>> -Original Message- > >>> From: Peter Kovacs [mailto:pe...@apache.org] > >>> Sent: Sunday, October 17, 2021 11:27 AM > >>> To: dev@openoffice.apache.org > >>> Subject: Re: API doc on web site [Was: Accessing the comment > >>> object (annotation) in Draw/Impress via API] > >>> > >>> Hi Jörg, > >>> > >>> > >>> I am not sure what you refer to. > >> I refer to the fact that changes in the API documentation > are marked > >> in time (the typical entry is "since ..."), so that the API > >> documentation can be used in practice for all program versions. > > I think we are on the same page if we want to change the API, but I > > think this is not the topic. > >>> The documentation has no > >>> influence on > >>> backward compatibility. > >> right. > >> > >> What I am referring to is only that we should not make > changes if the > >> QA is not 100% guaranteed. And what I currently experience is that > >> there is a tiny(!) problem in the API documentation, but > immediately > >> demanded now to regularly renew the documentation routinely. > > Again this is relevant if we change the API itself. > >> Explain to me bitterly where there are at all changes in > the API that > >> would make it necessary to update the documentation inflationary > >> frequently? > >> I follow every release carefully, only from API changes I have not > >> noticed for years. > > > > The API Documentation is extracted from the Code. > > > > For example the comment in > > > > > http://opengrok.openoffice.org/xref/aoo41x/main/offapi/com/sun > /star/modules.idl?r=d1766043#83 > > > > > > does have an impact on the web page: > > > > > https://www.openoffice.org/api/docs/common/ref/com/sun/star/of > fice/module-ix.html > > > > > > I hope you see both documentations are linked. So when do we update > > the documentation on the web site? > > > > Currently we will never update the web site, and the danger > is that if > > we change a comment in the documentation it will not end up on the > > website.. > > > > So Arrigos Idea is to update with each release. This would keep the > > documentation on the web in sync with the latest Code released for > > this API Version (Which should roughly correspond with the major > > release). > > > > It makes sense to publish on the website which Code the > extraction has > > been taken from and what Versions the Documentation relates to. > > > > On an API Change, QA and documentation Versions need to be > discussed. > > But we can discuss this when we get near to a API Change. I think > > until then we have done some steps in respect of QA. > > > > Carl is working on improvements, and I would like to try if we can > > establish a UI check with UI Path or similar tool. > > > > All the best > > > > Peter > > > > > > Actually we do provide updated documentation included in the SDK with > each convenience binary release. > It can be found on Linux at > /opt/openoffice4/sdk/docs/common/ref/module-ix.html > if the SDK is installed. > > Knowing that we can't make API changes like adding or deprecating > methods or things like that in a minor version change, Is this a principle that _all_ those involved in releases will also _reliably_ follow? On the whole question of API and documentation, I would like to make a general appeal to all of us: The fact that OpenOffice could not be displaced by LibreOffice is largely due to the good quality of OO. We must do everything we can to preserve this quality and not compromise in this regard. In this context, we must also be ready to examine, critically discuss and improve our activities again and again. Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: API doc on web site [Was: Accessing the comment object (annotation) in Draw/Impress via API]
Hi All, On 10/17/21 5:17 PM, Peter Kovacs wrote: Hi Jörg, On 17.10.21 19:48, Jörg Schmidt wrote: Hello Peter, -Original Message- From: Peter Kovacs [mailto:pe...@apache.org] Sent: Sunday, October 17, 2021 11:27 AM To: dev@openoffice.apache.org Subject: Re: API doc on web site [Was: Accessing the comment object (annotation) in Draw/Impress via API] Hi Jörg, I am not sure what you refer to. I refer to the fact that changes in the API documentation are marked in time (the typical entry is "since ..."), so that the API documentation can be used in practice for all program versions. I think we are on the same page if we want to change the API, but I think this is not the topic. The documentation has no influence on backward compatibility. right. What I am referring to is only that we should not make changes if the QA is not 100% guaranteed. And what I currently experience is that there is a tiny(!) problem in the API documentation, but immediately demanded now to regularly renew the documentation routinely. Again this is relevant if we change the API itself. Explain to me bitterly where there are at all changes in the API that would make it necessary to update the documentation inflationary frequently? I follow every release carefully, only from API changes I have not noticed for years. The API Documentation is extracted from the Code. For example the comment in http://opengrok.openoffice.org/xref/aoo41x/main/offapi/com/sun/star/modules.idl?r=d1766043#83 does have an impact on the web page: https://www.openoffice.org/api/docs/common/ref/com/sun/star/office/module-ix.html I hope you see both documentations are linked. So when do we update the documentation on the web site? Currently we will never update the web site, and the danger is that if we change a comment in the documentation it will not end up on the website.. So Arrigos Idea is to update with each release. This would keep the documentation on the web in sync with the latest Code released for this API Version (Which should roughly correspond with the major release). It makes sense to publish on the website which Code the extraction has been taken from and what Versions the Documentation relates to. On an API Change, QA and documentation Versions need to be discussed. But we can discuss this when we get near to a API Change. I think until then we have done some steps in respect of QA. Carl is working on improvements, and I would like to try if we can establish a UI check with UI Path or similar tool. All the best Peter Actually we do provide updated documentation included in the SDK with each convenience binary release. It can be found on Linux at /opt/openoffice4/sdk/docs/common/ref/module-ix.html if the SDK is installed. Knowing that we can't make API changes like adding or deprecating methods or things like that in a minor version change, any updates I imagine would be to improve documentation of current API. I don't see a problem with that and I think there is a lot of room for improvement especially around examples and more description. I have more concern around the website and SDK being out of sync if in fact documentation changes have been made which I don't know whether that's the case or not. Maybe that's something we can look at making sure the website has the latest copy. Slightly off-topic is that the Java documentation doesn't include all of the juh, jurt, and ridl classes like it could. I've been able to generate them and packed into and archive during a build but I haven't solved getting them into the packaging part. Best regards, Carl - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: API doc on web site [Was: Accessing the comment object (annotation) in Draw/Impress via API]
Am 18.10.21 um 08:07 schrieb Arrigo Marchiori: replying to myself as a correction. On Thu, Oct 14, 2021 at 07:08:25PM +0200, Arrigo Marchiori wrote: [...] Those pages should be generated by Autodoc, for what I understand. Are there any scripts that do this? Or any policies on how and when to update the API documentation? For example, I would suggest that each new release would be a good time to update the API. I should have written "API documentation" instead of API. I apologize. ah, that is changing the game. ;-) I agree that changing the API is a ``big thing'', that we shall be very careful, and I understand Jörg's and Marcus' concern while reading my paragraph above! I suggest we update the _documentation_ whenever possible because IMHO that can be helpful for developers. The details can and should be discussed when it comes to updates. But in general I agree. I hope I could clarify my proposal now. Yes, thanks Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: API doc on web site [Was: Accessing the comment object (annotation) in Draw/Impress via API]
> -Original Message- > From: Arrigo Marchiori [mailto:ard...@yahoo.it.INVALID] > Sent: Monday, October 18, 2021 8:08 AM > To: dev@openoffice.apache.org > Subject: Re: API doc on web site [Was: Accessing the comment > object (annotation) in Draw/Impress via API] > > Hello All, > > replying to myself as a correction. > > On Thu, Oct 14, 2021 at 07:08:25PM +0200, Arrigo Marchiori wrote: > > [...] > > Those pages should be generated by Autodoc, for what I understand. > > > > Are there any scripts that do this? Or any policies on how > and when to > > update the API documentation? For example, I would suggest > that each > > new release would be a good time to update the API. > > I should have written "API documentation" instead of API. I apologize. I assumed that 'API documentation' was meant, so all is well, no misunderstanding. > I agree that changing the API is a ``big thing'', that we shall be > very careful, and I understand Jörg's and Marcus' concern while > reading my paragraph above! > > I suggest we update the _documentation_ whenever possible because "whenever possible"? -1 'whenever necessary' +1 The difference between both things is a basic principle, e.g. in mechanical engineering (it is always worked as exactly as necessary, not as possible) as well as in programming, because one should not change any code (here documentation) if it is not necessary, because every change contains the risk of errors. > IMHO > that can be helpful for developers. Well, I've been professionally developing macros and extensions for OpenOffice for close to 15 years and I caution against frivolously updating the API documentation via automated processes until we have proper QA. Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: API doc on web site [Was: Accessing the comment object (annotation) in Draw/Impress via API]
Hello Peter, > -Original Message- > From: Peter Kovacs [mailto:pe...@apache.org] > Sent: Sunday, October 17, 2021 11:18 PM > To: dev@openoffice.apache.org > Subject: Re: API doc on web site [Was: Accessing the comment > object (annotation) in Draw/Impress via API] > The API Documentation is extracted from the Code. > > For example the comment in > > http://opengrok.openoffice.org/xref/aoo41x/main/offapi/com/sun > /star/modules.idl?r=d1766043#83 > > does have an impact on the web page: > > https://www.openoffice.org/api/docs/common/ref/com/sun/star/of > fice/module-ix.html > > I hope you see both documentations are linked. So when do we > update the > documentation on the web site? > > Currently we will never update the web site, and the danger > is that if > we change a comment in the documentation it will not end up > on the website.. > > So Arrigos Idea is to update with each release. This would keep the > documentation on the web in sync with the latest Code > released for this > API Version (Which should roughly correspond with the major release). > > It makes sense to publish on the website which Code the > extraction has > been taken from and what Versions the Documentation relates to. > > On an API Change, QA and documentation Versions need to be > discussed. yes, exactly. > But we can discuss this when we get near to a API Change. I > think until > then we have done some steps in respect of QA. How do you come to this hope, so we can all see that there is no regulated QA for years? Basically there is no real QA since Raphael left the project. That's just a description of the situation, because we lack enough volunteers to build up a really sufficient QA. But volunteers have to be motivated and for this we have to recognize performance and not admit people to the PMC according to personal preference (called alleged "merit"), but only according to performance. For example, we should have discussed honestly and factually how it came to the release mikt the (so-called) 'Big Sur Bug', to improve our release procedures, that such gross errors no longer occur. But nothing happened. '9 years as a top level project' ... well, I've been in the OO project for more than 16 years ... Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: API doc on web site [Was: Accessing the comment object (annotation) in Draw/Impress via API]
Hello All, replying to myself as a correction. On Thu, Oct 14, 2021 at 07:08:25PM +0200, Arrigo Marchiori wrote: [...] > Those pages should be generated by Autodoc, for what I understand. > > Are there any scripts that do this? Or any policies on how and when to > update the API documentation? For example, I would suggest that each > new release would be a good time to update the API. I should have written "API documentation" instead of API. I apologize. I agree that changing the API is a ``big thing'', that we shall be very careful, and I understand Jörg's and Marcus' concern while reading my paragraph above! I suggest we update the _documentation_ whenever possible because IMHO that can be helpful for developers. I hope I could clarify my proposal now. Best regards, -- Arrigo - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: API doc on web site [Was: Accessing the comment object (annotation) in Draw/Impress via API]
Hi Jörg, On 17.10.21 19:48, Jörg Schmidt wrote: Hello Peter, -Original Message- From: Peter Kovacs [mailto:pe...@apache.org] Sent: Sunday, October 17, 2021 11:27 AM To: dev@openoffice.apache.org Subject: Re: API doc on web site [Was: Accessing the comment object (annotation) in Draw/Impress via API] Hi Jörg, I am not sure what you refer to. I refer to the fact that changes in the API documentation are marked in time (the typical entry is "since ..."), so that the API documentation can be used in practice for all program versions. I think we are on the same page if we want to change the API, but I think this is not the topic. The documentation has no influence on backward compatibility. right. What I am referring to is only that we should not make changes if the QA is not 100% guaranteed. And what I currently experience is that there is a tiny(!) problem in the API documentation, but immediately demanded now to regularly renew the documentation routinely. Again this is relevant if we change the API itself. Explain to me bitterly where there are at all changes in the API that would make it necessary to update the documentation inflationary frequently? I follow every release carefully, only from API changes I have not noticed for years. The API Documentation is extracted from the Code. For example the comment in http://opengrok.openoffice.org/xref/aoo41x/main/offapi/com/sun/star/modules.idl?r=d1766043#83 does have an impact on the web page: https://www.openoffice.org/api/docs/common/ref/com/sun/star/office/module-ix.html I hope you see both documentations are linked. So when do we update the documentation on the web site? Currently we will never update the web site, and the danger is that if we change a comment in the documentation it will not end up on the website.. So Arrigos Idea is to update with each release. This would keep the documentation on the web in sync with the latest Code released for this API Version (Which should roughly correspond with the major release). It makes sense to publish on the website which Code the extraction has been taken from and what Versions the Documentation relates to. On an API Change, QA and documentation Versions need to be discussed. But we can discuss this when we get near to a API Change. I think until then we have done some steps in respect of QA. Carl is working on improvements, and I would like to try if we can establish a UI check with UI Path or similar tool. All the best Peter -- This is the Way! http://www.apache.org/theapacheway/index.html - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: API doc on web site [Was: Accessing the comment object (annotation) in Draw/Impress via API]
Hello Peter, > -Original Message- > From: Peter Kovacs [mailto:pe...@apache.org] > Sent: Sunday, October 17, 2021 11:27 AM > To: dev@openoffice.apache.org > Subject: Re: API doc on web site [Was: Accessing the comment > object (annotation) in Draw/Impress via API] > > Hi Jörg, > > > I am not sure what you refer to. I refer to the fact that changes in the API documentation are marked in time (the typical entry is "since ..."), so that the API documentation can be used in practice for all program versions. > The documentation has no > influence on > backward compatibility. right. What I am referring to is only that we should not make changes if the QA is not 100% guaranteed. And what I currently experience is that there is a tiny(!) problem in the API documentation, but immediately demanded now to regularly renew the documentation routinely. Explain to me bitterly where there are at all changes in the API that would make it necessary to update the documentation inflationary frequently? I follow every release carefully, only from API changes I have not noticed for years. > It would be beneficial if we update the documentation > with each release, > allowing a process that the documentation improves. And where is this process? What I see is that we don't even have a regulated QA for the program. Why do you want to make more work for which quality assurance never has the time? > I would not see documentation update as a blocker to a release thought. Neither do I in the least, but that's not the point, it's the quality assurance of the API documentation. Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: API doc on web site [Was: Accessing the comment object (annotation) in Draw/Impress via API]
Hi Jörg, I am not sure what you refer to. The documentation has no influence on backward compatibility. According to current rules for Version numbers we must bump the first digit if we do an API change. So for Version 5 we must provide a Documentation a Version 4 Documentation and a Version 5 Documentation. I think even if Version 5 is backward compatible with Version 4, the documentation should be per Main Version. I am fighting that we stick to the rule. (Actually I whish we only change the first Digit if we have an API change. Which is a clear signal to anyone what he has to look out for. Current rules have a loophole to bumb for a majore release for features. Which I do not see the benefit in. But this is maybe a different discussion) It would be beneficial if we update the documentation with each release, allowing a process that the documentation improves. I think that means at current release speed we update API Documentation once / twice a year. Which should not be to much effort? I would not see documentation update as a blocker to a release thought. Maybe even not part on the Release itself. But I think it is smart to have both process in sync. I think Arrigos Idea is a good one. All the best Peter On 15.10.21 10:15, Jörg Schmidt wrote: -Original Message- From: Arrigo Marchiori [mailto:ard...@yahoo.it.INVALID] Sent: Thursday, October 14, 2021 7:08 PM To: dev@openoffice.apache.org Subject: API doc on web site [Was: Accessing the comment object (annotation) in Draw/Impress via API] the API doc is (somehow) part of the website. And what you are looking for is maybe here: https://github.com/apache/openoffice-org/blob/main/part2/conte nt/api/docs/common/ref/com/sun/star/office/module-ix.html Thank you! That is what I meant. Those pages should be generated by Autodoc, for what I understand. Are there any scripts that do this? Or any policies on how and when to update the API documentation? For example, I would suggest that each new release would be a good time to update the API. -1 (for the moment) this is only a good idea if there was a way to make backward compatibility, because information is needed for all OO versions, not only for the current version please understand me correctly: it's not about not changing anything, it's about not changing a whole procedure without careful(!) examination just because there is an incorrect entry Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org -- This is the Way! http://www.apache.org/theapacheway/index.html - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: API doc on web site [Was: Accessing the comment object (annotation) in Draw/Impress via API]
Am 15.10.21 um 10:15 schrieb Jörg Schmidt: -Original Message- From: Arrigo Marchiori [mailto:ard...@yahoo.it.INVALID] Sent: Thursday, October 14, 2021 7:08 PM To: dev@openoffice.apache.org Subject: API doc on web site [Was: Accessing the comment object (annotation) in Draw/Impress via API] the API doc is (somehow) part of the website. And what you are looking for is maybe here: https://github.com/apache/openoffice-org/blob/main/part2/conte nt/api/docs/common/ref/com/sun/star/office/module-ix.html Thank you! That is what I meant. Those pages should be generated by Autodoc, for what I understand. Are there any scripts that do this? Or any policies on how and when to update the API documentation? For example, I would suggest that each new release would be a good time to update the API. please not really for each release. We should provide our users with a stable API at least for the 4.1.x release branch. Maybe also for 4.x.y. Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
RE: API doc on web site [Was: Accessing the comment object (annotation) in Draw/Impress via API]
> -Original Message- > From: Arrigo Marchiori [mailto:ard...@yahoo.it.INVALID] > Sent: Thursday, October 14, 2021 7:08 PM > To: dev@openoffice.apache.org > Subject: API doc on web site [Was: Accessing the comment > object (annotation) in Draw/Impress via API] > > the API doc is (somehow) part of the website. And what you > are looking for > > is maybe here: > > > > > https://github.com/apache/openoffice-org/blob/main/part2/conte > nt/api/docs/common/ref/com/sun/star/office/module-ix.html > > Thank you! That is what I meant. > > Those pages should be generated by Autodoc, for what I understand. > > Are there any scripts that do this? Or any policies on how and when to > update the API documentation? For example, I would suggest that each > new release would be a good time to update the API. -1 (for the moment) this is only a good idea if there was a way to make backward compatibility, because information is needed for all OO versions, not only for the current version please understand me correctly: it's not about not changing anything, it's about not changing a whole procedure without careful(!) examination just because there is an incorrect entry Jörg - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
API doc on web site [Was: Accessing the comment object (annotation) in Draw/Impress via API]
Hello, On Wed, Oct 13, 2021 at 12:10:52AM +0200, Marcus wrote: > Am 12.10.21 um 22:06 schrieb Arrigo Marchiori: > > > > On Mon, Oct 11, 2021 at 04:53:56PM +0200, Czesław Wolański wrote: > > > > > Recently a user on the English forum inquired how one can change the font > > > size in a comment box in Draw [1]. > > > He was given the obvious workaround tip and then the discussion started on > > > how to access the comment object via API. > > > Though the AOO's IDL reference says nothing in this regard, it turned out > > > the annotation can be handled > > > programmatically (at least in OpenOffice Basic). > > > > > > Hence my questions: > > > 1. Is the API in terms of annotations' handling fully operational? > > > 2. Should the relevant AOO's IDL reference be amended? > > > see: > > > https://www.openoffice.org/api/docs/common/ref/com/sun/star/office/module-ix.html > > > > I guess that the "API documentation" is extracted from autodoc or > > something like that... how can we update it on our web site? Are there > > any scripts or procedures? > > > > Thank you in advance for any pointers, > > the API doc is (somehow) part of the website. And what you are looking for > is maybe here: > > https://github.com/apache/openoffice-org/blob/main/part2/content/api/docs/common/ref/com/sun/star/office/module-ix.html Thank you! That is what I meant. Those pages should be generated by Autodoc, for what I understand. Are there any scripts that do this? Or any policies on how and when to update the API documentation? For example, I would suggest that each new release would be a good time to update the API. Best regards, -- Arrigo - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Accessing the comment object (annotation) in Draw/Impress via API
Am 12.10.21 um 22:06 schrieb Arrigo Marchiori: On Mon, Oct 11, 2021 at 04:53:56PM +0200, Czesław Wolański wrote: Recently a user on the English forum inquired how one can change the font size in a comment box in Draw [1]. He was given the obvious workaround tip and then the discussion started on how to access the comment object via API. Though the AOO's IDL reference says nothing in this regard, it turned out the annotation can be handled programmatically (at least in OpenOffice Basic). Hence my questions: 1. Is the API in terms of annotations' handling fully operational? 2. Should the relevant AOO's IDL reference be amended? see: https://www.openoffice.org/api/docs/common/ref/com/sun/star/office/module-ix.html I guess that the "API documentation" is extracted from autodoc or something like that... how can we update it on our web site? Are there any scripts or procedures? Thank you in advance for any pointers, the API doc is (somehow) part of the website. And what you are looking for is maybe here: https://github.com/apache/openoffice-org/blob/main/part2/content/api/docs/common/ref/com/sun/star/office/module-ix.html HTH Marcus - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Accessing the comment object (annotation) in Draw/Impress via API
Dear all, On Mon, Oct 11, 2021 at 04:53:56PM +0200, Czesław Wolański wrote: > Hi, > > Recently a user on the English forum inquired how one can change the font > size in a comment box in Draw [1]. > He was given the obvious workaround tip and then the discussion started on > how to access the comment object via API. > Though the AOO's IDL reference says nothing in this regard, it turned out > the annotation can be handled > programmatically (at least in OpenOffice Basic). > > Hence my questions: > 1. Is the API in terms of annotations' handling fully operational? > 2. Should the relevant AOO's IDL reference be amended? > see: > https://www.openoffice.org/api/docs/common/ref/com/sun/star/office/module-ix.html I guess that the "API documentation" is extracted from autodoc or something like that... how can we update it on our web site? Are there any scripts or procedures? Thank you in advance for any pointers, -- Arrigo - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Accessing the comment object (annotation) in Draw/Impress via API
Hi, Recently a user on the English forum inquired how one can change the font size in a comment box in Draw [1]. He was given the obvious workaround tip and then the discussion started on how to access the comment object via API. Though the AOO's IDL reference says nothing in this regard, it turned out the annotation can be handled programmatically (at least in OpenOffice Basic). Hence my questions: 1. Is the API in terms of annotations' handling fully operational? 2. Should the relevant AOO's IDL reference be amended? see: https://www.openoffice.org/api/docs/common/ref/com/sun/star/office/module-ix.html -- "The OpenOffice.org 3 Draw Guide", section "Adding comments to a drawing" (pp. 201-202) states: "Type or paste your comment into the text box. You can optionally apply some basic formatting to parts of the text by selecting it, right-clicking, and choosing from the pop-up menu." -- My sincere thanks to Arrigo Marchiori for providing valuable hints on the relevant source code and the SDK. Regards, Czesław [1] "Changing the font size in a comment box" https://forum.openoffice.org/en/forum/viewtopic.php?f=11&t=106271
[GitHub] [openoffice-org] jeanmicoste edited a comment on pull request #14: Add a line with "Découvrir Draw"
jeanmicoste edited a comment on pull request #14: URL: https://github.com/apache/openoffice-org/pull/14#issuecomment-833872068 No, this is bad handling. And repository is deleted. I have to remake it ? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[GitHub] [openoffice-org] jeanmicoste commented on pull request #14: Add a line with "Découvrir Draw"
jeanmicoste commented on pull request #14: URL: https://github.com/apache/openoffice-org/pull/14#issuecomment-833872068 No, this is bad handling. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[GitHub] [openoffice-org] dave2wave commented on pull request #14: Add a line with "Découvrir Draw"
dave2wave commented on pull request #14: URL: https://github.com/apache/openoffice-org/pull/14#issuecomment-833763889 Did you close this because you are still working on it? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[GitHub] [openoffice-org] jeanmicoste closed pull request #14: Add a line with "Découvrir Draw"
jeanmicoste closed pull request #14: URL: https://github.com/apache/openoffice-org/pull/14 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[GitHub] [openoffice-org] jeanmicoste commented on pull request #14: Add a line with "Découvrir Draw"
jeanmicoste commented on pull request #14: URL: https://github.com/apache/openoffice-org/pull/14#issuecomment-832707562 Add a missing link to a file. Add a missing file indexht-math.html shown in the left menu -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[GitHub] [openoffice-org] jeanmicoste closed pull request #14: Add a line with "Découvrir Draw"
jeanmicoste closed pull request #14: URL: https://github.com/apache/openoffice-org/pull/14 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
[GitHub] [openoffice-org] jeanmicoste opened a new pull request #14: Add a line with "Découvrir Draw"
jeanmicoste opened a new pull request #14: URL: https://github.com/apache/openoffice-org/pull/14 Add a link to a file -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: "convert' pdf images in Draw
Hi! Thank You! I will test. -marcia - Original Message - From: "Mechtilde" To: dev@openoffice.apache.org Sent: Tuesday, January 5, 2021 10:16:19 PM Subject: "convert' pdf images in Draw Hello Marcia, Am 06.01.21 um 00:20 schrieb marcia wilbur: > Hi. > > Do we have a feature to open PDFs in Draw? > I tried. All I had was characters. Am I doing something wrong or do we not > have "open PDF as images in Draw". Yes we have this feature as an extension. I tried to build it from 4.2.x branch. You can get it from http://home.apache.org/~mechtilde/Tools/ and test it. > > I have gs and imagemagick - was able to convert the same PDF at the shell > with convert... So, is it a config or not a feature yet? > > also, i couldn't login to requests so, I'm asking here. > > > Thanks, > Marcia Kind regards -- Mechtilde Stehmann ## Apache OpenOffice ## Freie Office Suite für Linux, MacOSX, Windows und OS/2 ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
"convert' pdf images in Draw
Hello Marcia, Am 06.01.21 um 00:20 schrieb marcia wilbur: > Hi. > > Do we have a feature to open PDFs in Draw? > I tried. All I had was characters. Am I doing something wrong or do we not > have "open PDF as images in Draw". Yes we have this feature as an extension. I tried to build it from 4.2.x branch. You can get it from http://home.apache.org/~mechtilde/Tools/ and test it. > > I have gs and imagemagick - was able to convert the same PDF at the shell > with convert... So, is it a config or not a feature yet? > > also, i couldn't login to requests so, I'm asking here. > > > Thanks, > Marcia Kind regards -- Mechtilde Stehmann ## Apache OpenOffice ## Freie Office Suite für Linux, MacOSX, Windows und OS/2 ## Debian Developer ## PGP encryption welcome ## F0E3 7F3D C87A 4998 2899 39E7 F287 7BBA 141A AD7F OpenPGP_signature Description: OpenPGP digital signature
"convert' pdf images in Draw
Hi. Do we have a feature to open PDFs in Draw? I tried. All I had was characters. Am I doing something wrong or do we not have "open PDF as images in Draw". I have gs and imagemagick - was able to convert the same PDF at the shell with convert... So, is it a config or not a feature yet? also, i couldn't login to requests so, I'm asking here. Thanks, Marcia - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: AOO Draw - User Profile Corrupted, follow-up
Hi Czeslaw I can confirm the glitch in Windows 7 x64 The window that you see now is actually the Slide Pane taking all the slide area (it is on top). Notice that you can close the Slide Pane by clicking on the Close button (X) to the left of Properties or by unchecking the tick in menu View > Slide Pane. There is however a simple solution: when the Slide Pane is open, click to the right of the word Slides and drag up in the direction of menu File and release when you see the box outline. Then simply drag it into place Hope this helps (if not email me for more details) Pedro > On April 9, 2020 6:13 PM Czesław Wolański wrote: > > > Hi, > > Hi team, > > My sincere apologies for delayed reply and even more sincere thanks to you > all for a warm welcome. > > I am not sure it's good news: same glitch occurs in AOO Impress. > > A video file is available at the following link: > > https://drive.google.com/open?id=1Uukw3xx1qTafuj2znLCnr6OBgE8YmoiE > > I would be glad if someone confirms my findings. That would allow me to > rule out a possibility that glitch can be attributed to my computer(s) or... > to myself (sort of "Pauli effect" - > https://en.wikipedia.org/wiki/Pauli_effect). > > > Regards, > > > Czesław > > Le jeu. 9 avr. 2020 à 16:51, Carl Marcum a écrit : > > > Hi Czesław, > > > > Yes, thank you for your hard work on this and your contributions to > > improve the UI! > > > > I had seen your issues come though on the mailing list and had looked a > > few but had no time for testing. > > Your filed issues and steps to reproduce are thorough. > > > > Apologies for not taking time to respond sooner. > > > > And thanks Matthias for following up. > > > > Best regards, > > Carl > > > > > > On 4/9/20 4:01 AM, Matthias Seidel wrote: > > > Hi Czesław, > > > > > > Sorry for getting no feedback here from others... > > > > > > Am 06.04.20 um 15:43 schrieb Czesław Wolański: > > >> Dear Sir / Madam, > > >> > > >> my name is Czesław Wolański. I devote some of my spare time mainly to > > doing > > >> translation of AOO UI into Polish (L10n), > > >> but you might have noticed increasing activity on my part in terms of > > >> reporting issues/bugs to Bugzilla (recent months). > > > Your work on QA is highly appreciated and together we were already able > > > to fix quite a lot of UI "glitches". > > > This is an important part of our "product" because it enhances the > > > experience for the user (our "customers"). > > > > > > Somehow this aspect of OpenOffice was neglected too long, but for 4.2.0 > > > it will get better. > > > > > > I hope other members here will find the time to welcome you! ;-) > > > > > > Regards, > > > > > > Matthias > > > > > >> This report is sort of follow-up to Issue 128329 "AOO Draw - > > irreparable?" > > >> I filed to Bugzilla. > > >> > > >> https://bz.apache.org/ooo/show_bug.cgi?id=128329 > > >> > > >> In "Comment 1" to it (made by Peter) you may read: > > >> > > >> "*An email to dev@openoffice.apache.org > > would > > >> be the right approach for this particular issue. Have you tried to reset > > >> the profile? If this helps please put more research in this, Corrupted > > >> Profile is one of the issues which are really annoying.[...]*" > > >> > > >> So I have "put more research in this". It seems that undocking Page Pane > > >> and redocking it at the top of document window > > >> may lead to glitches in AOO Draw. Resetting User Profile fixes the > > problem. > > >> > > >> My configuration: > > >> - Windows 7 64-bit Home Premium, PL > > >> - Apache OpenOffice 4.1.7 > > >>AOO417m1(Build:9800) - Rev. 46059c9192 > > >>2019-09-03 12:04 > > >> > > >>Apache_OpenOffice_4.1.7_Win_x86_install_pl (full installation, > > PL) > > >>Apache_OpenOffice_4.1.7_Win_x86_langpack_en-US (language pack, > > >> English(US)) > > >> > > >> > > >> I have run test procedure a dozen or so times. After each test, I > > resetted > > >> User Profile > > >> ( path: %AppData%\Roaming\OpenOffice\4\user ) or changed the name of > > >> folder &q
Re: AOO Draw - User Profile Corrupted, follow-up
Hi, Hi team, My sincere apologies for delayed reply and even more sincere thanks to you all for a warm welcome. I am not sure it's good news: same glitch occurs in AOO Impress. A video file is available at the following link: https://drive.google.com/open?id=1Uukw3xx1qTafuj2znLCnr6OBgE8YmoiE I would be glad if someone confirms my findings. That would allow me to rule out a possibility that glitch can be attributed to my computer(s) or... to myself (sort of "Pauli effect" - https://en.wikipedia.org/wiki/Pauli_effect). Regards, Czesław Le jeu. 9 avr. 2020 à 16:51, Carl Marcum a écrit : > Hi Czesław, > > Yes, thank you for your hard work on this and your contributions to > improve the UI! > > I had seen your issues come though on the mailing list and had looked a > few but had no time for testing. > Your filed issues and steps to reproduce are thorough. > > Apologies for not taking time to respond sooner. > > And thanks Matthias for following up. > > Best regards, > Carl > > > On 4/9/20 4:01 AM, Matthias Seidel wrote: > > Hi Czesław, > > > > Sorry for getting no feedback here from others... > > > > Am 06.04.20 um 15:43 schrieb Czesław Wolański: > >> Dear Sir / Madam, > >> > >> my name is Czesław Wolański. I devote some of my spare time mainly to > doing > >> translation of AOO UI into Polish (L10n), > >> but you might have noticed increasing activity on my part in terms of > >> reporting issues/bugs to Bugzilla (recent months). > > Your work on QA is highly appreciated and together we were already able > > to fix quite a lot of UI "glitches". > > This is an important part of our "product" because it enhances the > > experience for the user (our "customers"). > > > > Somehow this aspect of OpenOffice was neglected too long, but for 4.2.0 > > it will get better. > > > > I hope other members here will find the time to welcome you! ;-) > > > > Regards, > > > > Matthias > > > >> This report is sort of follow-up to Issue 128329 "AOO Draw - > irreparable?" > >> I filed to Bugzilla. > >> > >> https://bz.apache.org/ooo/show_bug.cgi?id=128329 > >> > >> In "Comment 1" to it (made by Peter) you may read: > >> > >> "*An email to dev@openoffice.apache.org > would > >> be the right approach for this particular issue. Have you tried to reset > >> the profile? If this helps please put more research in this, Corrupted > >> Profile is one of the issues which are really annoying.[...]*" > >> > >> So I have "put more research in this". It seems that undocking Page Pane > >> and redocking it at the top of document window > >> may lead to glitches in AOO Draw. Resetting User Profile fixes the > problem. > >> > >> My configuration: > >> - Windows 7 64-bit Home Premium, PL > >> - Apache OpenOffice 4.1.7 > >>AOO417m1(Build:9800) - Rev. 46059c9192 > >>2019-09-03 12:04 > >> > >>Apache_OpenOffice_4.1.7_Win_x86_install_pl (full installation, > PL) > >>Apache_OpenOffice_4.1.7_Win_x86_langpack_en-US (language pack, > >> English(US)) > >> > >> > >> I have run test procedure a dozen or so times. After each test, I > resetted > >> User Profile > >> ( path: %AppData%\Roaming\OpenOffice\4\user ) or changed the name of > >> folder "OpenOffice" in %AppData%\Roaming\ > >> > >> Please take a look at my documentation: > >> > >> - video "HowToWTF", available at the following link: > >>https://drive.google.com/open?id=14xm4x1mehtxvXo1_7ueUq5EE_uwuPSfa > >> > >> - information on configuration, file "Infos", available at the following > >> link: > >>https://drive.google.com/open?id=1QfIbjoKIMELTpQHUJY3_mSUtv_6MrKkg > >> > >> - screenshots of glitches, file "DrawGlitches", available at the > following > >> link: > >>https://drive.google.com/open?id=1eAsv5gvWrR35PGAJrx6fOyD8c3l18JDM > >> > >> > >> And some additional remarks: > >> > >> 1. I my report to Bugzilla I wrote: "Recently I have subjected AOO Draw > to > >> harsh tests (multiple docking/redocking of Page Pane, Navigator, > >> Color Replacer and Color Bar in various combinations). In tests > >> observed many glitches. Finally AOO crashed." > >> I am not a hundred percent sure that the rea
Re: AOO Draw - User Profile Corrupted, follow-up
Hi Czesław, Yes, thank you for your hard work on this and your contributions to improve the UI! I had seen your issues come though on the mailing list and had looked a few but had no time for testing. Your filed issues and steps to reproduce are thorough. Apologies for not taking time to respond sooner. And thanks Matthias for following up. Best regards, Carl On 4/9/20 4:01 AM, Matthias Seidel wrote: Hi Czesław, Sorry for getting no feedback here from others... Am 06.04.20 um 15:43 schrieb Czesław Wolański: Dear Sir / Madam, my name is Czesław Wolański. I devote some of my spare time mainly to doing translation of AOO UI into Polish (L10n), but you might have noticed increasing activity on my part in terms of reporting issues/bugs to Bugzilla (recent months). Your work on QA is highly appreciated and together we were already able to fix quite a lot of UI "glitches". This is an important part of our "product" because it enhances the experience for the user (our "customers"). Somehow this aspect of OpenOffice was neglected too long, but for 4.2.0 it will get better. I hope other members here will find the time to welcome you! ;-) Regards, Matthias This report is sort of follow-up to Issue 128329 "AOO Draw - irreparable?" I filed to Bugzilla. https://bz.apache.org/ooo/show_bug.cgi?id=128329 In "Comment 1" to it (made by Peter) you may read: "*An email to dev@openoffice.apache.org would be the right approach for this particular issue. Have you tried to reset the profile? If this helps please put more research in this, Corrupted Profile is one of the issues which are really annoying.[...]*" So I have "put more research in this". It seems that undocking Page Pane and redocking it at the top of document window may lead to glitches in AOO Draw. Resetting User Profile fixes the problem. My configuration: - Windows 7 64-bit Home Premium, PL - Apache OpenOffice 4.1.7 AOO417m1(Build:9800) - Rev. 46059c9192 2019-09-03 12:04 Apache_OpenOffice_4.1.7_Win_x86_install_pl (full installation, PL) Apache_OpenOffice_4.1.7_Win_x86_langpack_en-US (language pack, English(US)) I have run test procedure a dozen or so times. After each test, I resetted User Profile ( path: %AppData%\Roaming\OpenOffice\4\user ) or changed the name of folder "OpenOffice" in %AppData%\Roaming\ Please take a look at my documentation: - video "HowToWTF", available at the following link: https://drive.google.com/open?id=14xm4x1mehtxvXo1_7ueUq5EE_uwuPSfa - information on configuration, file "Infos", available at the following link: https://drive.google.com/open?id=1QfIbjoKIMELTpQHUJY3_mSUtv_6MrKkg - screenshots of glitches, file "DrawGlitches", available at the following link: https://drive.google.com/open?id=1eAsv5gvWrR35PGAJrx6fOyD8c3l18JDM And some additional remarks: 1. I my report to Bugzilla I wrote: "Recently I have subjected AOO Draw to harsh tests (multiple docking/redocking of Page Pane, Navigator, Color Replacer and Color Bar in various combinations). In tests observed many glitches. Finally AOO crashed." I am not a hundred percent sure that the reason for glitches and crash I mentioned in that report is the same I present here. 2. In above mentioned file "DrawGlitches" you may see two examples of start screen in AOO Draw. A few times I saw nothing worrying, but when I repeated docking/undocking and/or hiding/showing Page Pane and then closed and opened AOO Draw again, the glitch appeared. 3. Every time I reset User Profile, run AOO and finish registration process, AOO shows Start Center window not maximized. Next time I run AOO, Start Center window is maximized. 4. And last but definitely least: while watching attached video you'll surely notice how cluttered my Desktop is. I am fighting that mess on end, but the more I try to declutter Desktop, the more it gets cluttered ("mischievous inanimate nature"). Shall you have any questions, please contact me. With regard, Czesław Wolański - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: AOO Draw - User Profile Corrupted, follow-up
Hi Czesław, also from me a great welcome to the project. :-) Marcus Am 09.04.20 um 10:01 schrieb Matthias Seidel: Sorry for getting no feedback here from others... Am 06.04.20 um 15:43 schrieb Czesław Wolański: Dear Sir / Madam, my name is Czesław Wolański. I devote some of my spare time mainly to doing translation of AOO UI into Polish (L10n), but you might have noticed increasing activity on my part in terms of reporting issues/bugs to Bugzilla (recent months). Your work on QA is highly appreciated and together we were already able to fix quite a lot of UI "glitches". This is an important part of our "product" because it enhances the experience for the user (our "customers"). Somehow this aspect of OpenOffice was neglected too long, but for 4.2.0 it will get better. I hope other members here will find the time to welcome you! ;-) This report is sort of follow-up to Issue 128329 "AOO Draw - irreparable?" I filed to Bugzilla. https://bz.apache.org/ooo/show_bug.cgi?id=128329 In "Comment 1" to it (made by Peter) you may read: "*An email to dev@openoffice.apache.org would be the right approach for this particular issue. Have you tried to reset the profile? If this helps please put more research in this, Corrupted Profile is one of the issues which are really annoying.[...]*" So I have "put more research in this". It seems that undocking Page Pane and redocking it at the top of document window may lead to glitches in AOO Draw. Resetting User Profile fixes the problem. My configuration: - Windows 7 64-bit Home Premium, PL - Apache OpenOffice 4.1.7 AOO417m1(Build:9800) - Rev. 46059c9192 2019-09-03 12:04 Apache_OpenOffice_4.1.7_Win_x86_install_pl (full installation, PL) Apache_OpenOffice_4.1.7_Win_x86_langpack_en-US (language pack, English(US)) I have run test procedure a dozen or so times. After each test, I resetted User Profile ( path: %AppData%\Roaming\OpenOffice\4\user ) or changed the name of folder "OpenOffice" in %AppData%\Roaming\ Please take a look at my documentation: - video "HowToWTF", available at the following link: https://drive.google.com/open?id=14xm4x1mehtxvXo1_7ueUq5EE_uwuPSfa - information on configuration, file "Infos", available at the following link: https://drive.google.com/open?id=1QfIbjoKIMELTpQHUJY3_mSUtv_6MrKkg - screenshots of glitches, file "DrawGlitches", available at the following link: https://drive.google.com/open?id=1eAsv5gvWrR35PGAJrx6fOyD8c3l18JDM And some additional remarks: 1. I my report to Bugzilla I wrote: "Recently I have subjected AOO Draw to harsh tests (multiple docking/redocking of Page Pane, Navigator, Color Replacer and Color Bar in various combinations). In tests observed many glitches. Finally AOO crashed." I am not a hundred percent sure that the reason for glitches and crash I mentioned in that report is the same I present here. 2. In above mentioned file "DrawGlitches" you may see two examples of start screen in AOO Draw. A few times I saw nothing worrying, but when I repeated docking/undocking and/or hiding/showing Page Pane and then closed and opened AOO Draw again, the glitch appeared. 3. Every time I reset User Profile, run AOO and finish registration process, AOO shows Start Center window not maximized. Next time I run AOO, Start Center window is maximized. 4. And last but definitely least: while watching attached video you'll surely notice how cluttered my Desktop is. I am fighting that mess on end, but the more I try to declutter Desktop, the more it gets cluttered ("mischievous inanimate nature"). - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: AOO Draw - User Profile Corrupted, follow-up
Hi Czesław, yea I did not manage to put time in your findings. But I am very grateful. I will pick this topic up. hopefully soon. All the best Peter Am 09.04.20 um 10:01 schrieb Matthias Seidel: Hi Czesław, Sorry for getting no feedback here from others... Am 06.04.20 um 15:43 schrieb Czesław Wolański: Dear Sir / Madam, my name is Czesław Wolański. I devote some of my spare time mainly to doing translation of AOO UI into Polish (L10n), but you might have noticed increasing activity on my part in terms of reporting issues/bugs to Bugzilla (recent months). Your work on QA is highly appreciated and together we were already able to fix quite a lot of UI "glitches". This is an important part of our "product" because it enhances the experience for the user (our "customers"). Somehow this aspect of OpenOffice was neglected too long, but for 4.2.0 it will get better. I hope other members here will find the time to welcome you! ;-) Regards, Matthias This report is sort of follow-up to Issue 128329 "AOO Draw - irreparable?" I filed to Bugzilla. https://bz.apache.org/ooo/show_bug.cgi?id=128329 In "Comment 1" to it (made by Peter) you may read: "*An email to dev@openoffice.apache.org would be the right approach for this particular issue. Have you tried to reset the profile? If this helps please put more research in this, Corrupted Profile is one of the issues which are really annoying.[...]*" So I have "put more research in this". It seems that undocking Page Pane and redocking it at the top of document window may lead to glitches in AOO Draw. Resetting User Profile fixes the problem. My configuration: - Windows 7 64-bit Home Premium, PL - Apache OpenOffice 4.1.7 AOO417m1(Build:9800) - Rev. 46059c9192 2019-09-03 12:04 Apache_OpenOffice_4.1.7_Win_x86_install_pl (full installation, PL) Apache_OpenOffice_4.1.7_Win_x86_langpack_en-US (language pack, English(US)) I have run test procedure a dozen or so times. After each test, I resetted User Profile ( path: %AppData%\Roaming\OpenOffice\4\user ) or changed the name of folder "OpenOffice" in %AppData%\Roaming\ Please take a look at my documentation: - video "HowToWTF", available at the following link: https://drive.google.com/open?id=14xm4x1mehtxvXo1_7ueUq5EE_uwuPSfa - information on configuration, file "Infos", available at the following link: https://drive.google.com/open?id=1QfIbjoKIMELTpQHUJY3_mSUtv_6MrKkg - screenshots of glitches, file "DrawGlitches", available at the following link: https://drive.google.com/open?id=1eAsv5gvWrR35PGAJrx6fOyD8c3l18JDM And some additional remarks: 1. I my report to Bugzilla I wrote: "Recently I have subjected AOO Draw to harsh tests (multiple docking/redocking of Page Pane, Navigator, Color Replacer and Color Bar in various combinations). In tests observed many glitches. Finally AOO crashed." I am not a hundred percent sure that the reason for glitches and crash I mentioned in that report is the same I present here. 2. In above mentioned file "DrawGlitches" you may see two examples of start screen in AOO Draw. A few times I saw nothing worrying, but when I repeated docking/undocking and/or hiding/showing Page Pane and then closed and opened AOO Draw again, the glitch appeared. 3. Every time I reset User Profile, run AOO and finish registration process, AOO shows Start Center window not maximized. Next time I run AOO, Start Center window is maximized. 4. And last but definitely least: while watching attached video you'll surely notice how cluttered my Desktop is. I am fighting that mess on end, but the more I try to declutter Desktop, the more it gets cluttered ("mischievous inanimate nature"). Shall you have any questions, please contact me. With regard, Czesław Wolański - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: AOO Draw - User Profile Corrupted, follow-up
Hi Czesław, Sorry for getting no feedback here from others... Am 06.04.20 um 15:43 schrieb Czesław Wolański: > Dear Sir / Madam, > > my name is Czesław Wolański. I devote some of my spare time mainly to doing > translation of AOO UI into Polish (L10n), > but you might have noticed increasing activity on my part in terms of > reporting issues/bugs to Bugzilla (recent months). Your work on QA is highly appreciated and together we were already able to fix quite a lot of UI "glitches". This is an important part of our "product" because it enhances the experience for the user (our "customers"). Somehow this aspect of OpenOffice was neglected too long, but for 4.2.0 it will get better. I hope other members here will find the time to welcome you! ;-) Regards, Matthias > > This report is sort of follow-up to Issue 128329 "AOO Draw - irreparable?" > I filed to Bugzilla. > > https://bz.apache.org/ooo/show_bug.cgi?id=128329 > > In "Comment 1" to it (made by Peter) you may read: > > "*An email to dev@openoffice.apache.org would > be the right approach for this particular issue. Have you tried to reset > the profile? If this helps please put more research in this, Corrupted > Profile is one of the issues which are really annoying.[...]*" > > So I have "put more research in this". It seems that undocking Page Pane > and redocking it at the top of document window > may lead to glitches in AOO Draw. Resetting User Profile fixes the problem. > > My configuration: > - Windows 7 64-bit Home Premium, PL > - Apache OpenOffice 4.1.7 > AOO417m1(Build:9800) - Rev. 46059c9192 > 2019-09-03 12:04 > > Apache_OpenOffice_4.1.7_Win_x86_install_pl (full installation, PL) > Apache_OpenOffice_4.1.7_Win_x86_langpack_en-US (language pack, > English(US)) > > > I have run test procedure a dozen or so times. After each test, I resetted > User Profile > ( path: %AppData%\Roaming\OpenOffice\4\user ) or changed the name of > folder "OpenOffice" in %AppData%\Roaming\ > > Please take a look at my documentation: > > - video "HowToWTF", available at the following link: > https://drive.google.com/open?id=14xm4x1mehtxvXo1_7ueUq5EE_uwuPSfa > > - information on configuration, file "Infos", available at the following > link: > https://drive.google.com/open?id=1QfIbjoKIMELTpQHUJY3_mSUtv_6MrKkg > > - screenshots of glitches, file "DrawGlitches", available at the following > link: > https://drive.google.com/open?id=1eAsv5gvWrR35PGAJrx6fOyD8c3l18JDM > > > And some additional remarks: > > 1. I my report to Bugzilla I wrote: "Recently I have subjected AOO Draw to > harsh tests (multiple docking/redocking of Page Pane, Navigator, > Color Replacer and Color Bar in various combinations). In tests > observed many glitches. Finally AOO crashed." > I am not a hundred percent sure that the reason for glitches and crash > I mentioned in that report is the same I present here. > > 2. In above mentioned file "DrawGlitches" you may see two examples of start > screen in AOO Draw. A few times I saw nothing worrying, > but when I repeated docking/undocking and/or hiding/showing Page Pane > and then closed and opened AOO Draw again, the glitch appeared. > > 3. Every time I reset User Profile, run AOO and finish registration > process, AOO shows Start Center window not maximized. > Next time I run AOO, Start Center window is maximized. > > 4. And last but definitely least: while watching attached video you'll > surely notice how cluttered my Desktop is. I am fighting that mess > on end, but the more I try to declutter Desktop, the more it gets > cluttered ("mischievous inanimate nature"). > > > Shall you have any questions, please contact me. > > > With regard, > > Czesław Wolański > smime.p7s Description: S/MIME Cryptographic Signature
AOO Draw - User Profile Corrupted, follow-up
Dear Sir / Madam, my name is Czesław Wolański. I devote some of my spare time mainly to doing translation of AOO UI into Polish (L10n), but you might have noticed increasing activity on my part in terms of reporting issues/bugs to Bugzilla (recent months). This report is sort of follow-up to Issue 128329 "AOO Draw - irreparable?" I filed to Bugzilla. https://bz.apache.org/ooo/show_bug.cgi?id=128329 In "Comment 1" to it (made by Peter) you may read: "*An email to dev@openoffice.apache.org would be the right approach for this particular issue. Have you tried to reset the profile? If this helps please put more research in this, Corrupted Profile is one of the issues which are really annoying.[...]*" So I have "put more research in this". It seems that undocking Page Pane and redocking it at the top of document window may lead to glitches in AOO Draw. Resetting User Profile fixes the problem. My configuration: - Windows 7 64-bit Home Premium, PL - Apache OpenOffice 4.1.7 AOO417m1(Build:9800) - Rev. 46059c9192 2019-09-03 12:04 Apache_OpenOffice_4.1.7_Win_x86_install_pl (full installation, PL) Apache_OpenOffice_4.1.7_Win_x86_langpack_en-US (language pack, English(US)) I have run test procedure a dozen or so times. After each test, I resetted User Profile ( path: %AppData%\Roaming\OpenOffice\4\user ) or changed the name of folder "OpenOffice" in %AppData%\Roaming\ Please take a look at my documentation: - video "HowToWTF", available at the following link: https://drive.google.com/open?id=14xm4x1mehtxvXo1_7ueUq5EE_uwuPSfa - information on configuration, file "Infos", available at the following link: https://drive.google.com/open?id=1QfIbjoKIMELTpQHUJY3_mSUtv_6MrKkg - screenshots of glitches, file "DrawGlitches", available at the following link: https://drive.google.com/open?id=1eAsv5gvWrR35PGAJrx6fOyD8c3l18JDM And some additional remarks: 1. I my report to Bugzilla I wrote: "Recently I have subjected AOO Draw to harsh tests (multiple docking/redocking of Page Pane, Navigator, Color Replacer and Color Bar in various combinations). In tests observed many glitches. Finally AOO crashed." I am not a hundred percent sure that the reason for glitches and crash I mentioned in that report is the same I present here. 2. In above mentioned file "DrawGlitches" you may see two examples of start screen in AOO Draw. A few times I saw nothing worrying, but when I repeated docking/undocking and/or hiding/showing Page Pane and then closed and opened AOO Draw again, the glitch appeared. 3. Every time I reset User Profile, run AOO and finish registration process, AOO shows Start Center window not maximized. Next time I run AOO, Start Center window is maximized. 4. And last but definitely least: while watching attached video you'll surely notice how cluttered my Desktop is. I am fighting that mess on end, but the more I try to declutter Desktop, the more it gets cluttered ("mischievous inanimate nature"). Shall you have any questions, please contact me. With regard, Czesław Wolański
Re: OPEN OFFICE DRAW - PLEASE CONTACT \ME ASAP
We save the cost for a toll free technical support number in order to ship the Product for free. May I ask where you got your copy of Open office from? Which version of Open Office do you use? I do not understand the Problem you have. I can open Apache Open Office Draw and set the ruler as I whish. Why the pressure. ASAP sounds very urgend. Why is that. A=I am trying to start a business of my own and using Open Office Draw. I need everything to work properly and effectively Even the AVG technician(s) were having problems with the ruler measurements. Why is it that sometimes you click Open-Open Office-Draw and every once in a while a draw window opens without the side panel, to view the content(s) on each page in the individual Draw windows? How do you correct this? What buttons on the keyboard do you press, to correct this? ASAP as it is important to me and I want to complete all contents within the Open Office Draw window(s), so each looks impressive and I can correct the error(s) being made by using specific keys on the keyboard, instead of becoming flustered, and/or frustrated; without any simplistic steps provided to resolve the problem(s) at hand. To me it is an urgent matter which needs immediate attention. When I couldn't get a hold of you, open office by phone I called AVG techs. The AVG techs were even bewildered as to how to resolve the problem(s) presented. Why is Cross Fading, Fields, Links, Object and Hyperlink grayed out in Edit? Why is crop picture grayed out in Format? Why is Distribution,Group, Ungroup, Enter Group, Exit Group, Combine, Split, Connect and Break grayed out in Modify? Why aren't all option selections made available to be used? Not all computer users are computer technicians or programmers and need to know the simplified steps of what keyboard keys are needing to be pressed, to resolve the issue(s) and, or problem(s) which have occurred at the present time(s); otherwise the unresolved issue(s) may become very frustrating and/or blood pressure elevating.. In the help selections, could all the methods/steps of using the keyboard buttons for each problem which may arise, be simply stated in the Help selection. Such as: Draw-Side Panel window display- press ? key+?key+?key (Shift+ F3, Ctrl+S, CTRL+Shift+S, etc.) instead of all the technical jibberish that is unable to be understood by many. Thank you for replying, I just got impatient of waiting for reply and called the AVG techs. As I said, all problems which I have faced are urgent to correct, as I am trying to do impressive work in starting a business of my own and Open Office Draw was the option which suited my needs beat at the time. Patti C. Patti C. Please note this is going over a puplic free for all readable channel. A copy of every message is released on the Web. all the best Peter On Mon, May 15, 2017 at 4:46 AM, Peter Kovacs wrote: > Hello Patti C., > > We save the cost for a toll free technical support number in order to ship > the Product for free. > May I ask where you got your copy of Open office from? > Which version of Open Office do you use? > > I do not understand the Problem you have. I can open Apache Open Office > Draw and set the ruler as I whish. > > Why the pressure. ASAP sounds very urgend. Why is that. > > Please note this is going over a puplic free for all readable channel. > > A copy of every message is released on the Web. > > all the best > > Peter > > On 15.05.2017 02:13, Patti C. wrote: > >> Why is there not a toll free number to call for technical Support? >> >> Why aren't all the proper tools provided which are needed for rulers? at >> the top of Draw and on the left hand side of Draw? >> >> Where are the normal measure scale(s) for all rulers provided >> which measures 01-25, 01-50, 01-75 0r 01-100 from the left to the right, >> for millimeters, centimeters, inches, etc..?! >> >> Why does it seem the ruler correction(s) are so impossible to make? Do you >> want to discourage user(s) so each no longer uses Open Office? >> >> Why are *6* *options* grayed out and made unusable in *Edit*? >> >> Why is it that in* View*-*Input* *Method* *Status* grayed out and made >> unusable? >> >> Why is *Special* *Character* grayed out and made unusable in *Insert*? >> >> *Tools*- Why aren't all *proper* *tools* *provided* to be used, that are >> *needed* to *correct* any *error*(*s*)? This *needs* to become a >> *priority* >> to be *corrected* *immediately*. >> >> *Format* - Why is *Default Formatting* grayed out and not made available >> to >> be used? >> Why is *Position* and *Size* grayed out and made >> unavailable to be used? >> Why is *Crop* *Picture* grayed
Re: OPEN OFFICE DRAW - PLEASE CONTACT \ME ASAP
Hello Patti C., We save the cost for a toll free technical support number in order to ship the Product for free. May I ask where you got your copy of Open office from? Which version of Open Office do you use? I do not understand the Problem you have. I can open Apache Open Office Draw and set the ruler as I whish. Why the pressure. ASAP sounds very urgend. Why is that. Please note this is going over a puplic free for all readable channel. A copy of every message is released on the Web. all the best Peter On 15.05.2017 02:13, Patti C. wrote: Why is there not a toll free number to call for technical Support? Why aren't all the proper tools provided which are needed for rulers? at the top of Draw and on the left hand side of Draw? Where are the normal measure scale(s) for all rulers provided which measures 01-25, 01-50, 01-75 0r 01-100 from the left to the right, for millimeters, centimeters, inches, etc..?! Why does it seem the ruler correction(s) are so impossible to make? Do you want to discourage user(s) so each no longer uses Open Office? Why are *6* *options* grayed out and made unusable in *Edit*? Why is it that in* View*-*Input* *Method* *Status* grayed out and made unusable? Why is *Special* *Character* grayed out and made unusable in *Insert*? *Tools*- Why aren't all *proper* *tools* *provided* to be used, that are *needed* to *correct* any *error*(*s*)? This *needs* to become a *priority* to be *corrected* *immediately*. *Format* - Why is *Default Formatting* grayed out and not made available to be used? Why is *Position* and *Size* grayed out and made unavailable to be used? Why is *Crop* *Picture* grayed out and made unavailable to be used? *Insert* - Why is Formatting Mark grayed out and made unavailable to be used? *Modify* - Why is *Convert* grayed out and made unavailable to be used? Why is *Arrange* options grayed out and made unavailable to be used? Why is *Distribution* grayed out and made unavailable to be used? Why is *Name* grayed out and made unavailable to be used? Why is *Group* grayed out and made unavailable to be used? Why is *Enter* *Group* grayed out and made unavailable to be used? Why is *Exit* *Group* grayed out and made unavailable to be used? Why is *Combine* grayed out and made unavailable to be used? Why is *Split* grayed out and made unavailable to be used? Why is *Connect* grayed out and made unavailable to be used? These need to be made a priority to be made available to all user(s) to use. Why isn't there a *download* *bar* on every *Open* *Office* *download* to let you know when the download(s) have *started*, *downloading* and when *finished*? This would be greatly *appreciated* by all Open Office users, I'm sure. One feature I am appreciative of is the document recovery. Time to make a lot of improvements to Open Office so it is much more effective and simple to use, as well as meeting professional standards. Do you have a remote screen capability? Patti C. 902-989-5582 Call Me Please. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
OPEN OFFICE DRAW - PLEASE CONTACT \ME ASAP
Why is there not a toll free number to call for technical Support? Why aren't all the proper tools provided which are needed for rulers? at the top of Draw and on the left hand side of Draw? Where are the normal measure scale(s) for all rulers provided which measures 01-25, 01-50, 01-75 0r 01-100 from the left to the right, for millimeters, centimeters, inches, etc..?! Why does it seem the ruler correction(s) are so impossible to make? Do you want to discourage user(s) so each no longer uses Open Office? Why are *6* *options* grayed out and made unusable in *Edit*? Why is it that in* View*-*Input* *Method* *Status* grayed out and made unusable? Why is *Special* *Character* grayed out and made unusable in *Insert*? *Tools*- Why aren't all *proper* *tools* *provided* to be used, that are *needed* to *correct* any *error*(*s*)? This *needs* to become a *priority* to be *corrected* *immediately*. *Format* - Why is *Default Formatting* grayed out and not made available to be used? Why is *Position* and *Size* grayed out and made unavailable to be used? Why is *Crop* *Picture* grayed out and made unavailable to be used? *Insert* - Why is Formatting Mark grayed out and made unavailable to be used? *Modify* - Why is *Convert* grayed out and made unavailable to be used? Why is *Arrange* options grayed out and made unavailable to be used? Why is *Distribution* grayed out and made unavailable to be used? Why is *Name* grayed out and made unavailable to be used? Why is *Group* grayed out and made unavailable to be used? Why is *Enter* *Group* grayed out and made unavailable to be used? Why is *Exit* *Group* grayed out and made unavailable to be used? Why is *Combine* grayed out and made unavailable to be used? Why is *Split* grayed out and made unavailable to be used? Why is *Connect* grayed out and made unavailable to be used? These need to be made a priority to be made available to all user(s) to use. Why isn't there a *download* *bar* on every *Open* *Office* *download* to let you know when the download(s) have *started*, *downloading* and when *finished*? This would be greatly *appreciated* by all Open Office users, I'm sure. One feature I am appreciative of is the document recovery. Time to make a lot of improvements to Open Office so it is much more effective and simple to use, as well as meeting professional standards. Do you have a remote screen capability? Patti C. 902-989-5582 Call Me Please.
Draw - crop marks and bleed
Hello, I have tested different "free" layout software on the market. Open Office Draw is the best by far. Good job. I decided to use Draw to design a very simple book cover. The background is one color, and it needs to out over the edges. I extend the rectangle element outside the edges of the workspace. And I put some crop marks to align with the corners of the workspace. My problem is that when I export as PDF, these things do not show up. Only the workspace (page format) is visible.The print place demand that I put the crop marks and the bleed included in the pdf. You can do these things in inDesign and some other software. Can I do it somehow? Can you build it? Other people on the forums seem to have the same need. PS. I have asked the print place if I can make the document size larger format, so crop marks and bleed can be included. But not possible, this screws up their systems. DS. Best regards Martin Lexelius
4.1.0_release_blocker canceled: [Issue 87182] Crash on formatting OLE Draw object
Armin Le Grand has canceled Armin Le Grand 's request for 4.1.0_release_blocker: Issue 87182: Crash on formatting OLE Draw object https://issues.apache.org/ooo/show_bug.cgi?id=87182 --- Additional Comments from Armin Le Grand Not needed for release - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Draw?
On 2/28/14 10:43 AM, Yakov Reztsov wrote: > > > > Пятница, 28 февраля 2014, 3:33 -05:00 от Dawn Lauryn <>: >> Hi, I used to have MS Visio, but that was with a biz. It's far too >> expensive for me to purchase now, but I have a vsd file I need to work >> with. Will Draw work at importing a vsd file and if so, where can I get a >> copy that I know will be malware-free? >> >> Thanks in advance:) > LibreOffice Draw can open MS Visio vsd via libvisio, > Is it possible to use this library together with the Apache OpenOffice Draw? > yes and no, it should be possible to develop a Visio filter extension using this library. But we can't integrate it by default in AOO due to an incompatible license if libvisio. It's similar to the PDF import extension that uses a license incompatible library as well. Juergen - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Draw?
Пятница, 28 февраля 2014, 3:33 -05:00 от Dawn Lauryn <>: >Hi, I used to have MS Visio, but that was with a biz. It's far too >expensive for me to purchase now, but I have a vsd file I need to work >with. Will Draw work at importing a vsd file and if so, where can I get a >copy that I know will be malware-free? > >Thanks in advance:) LibreOffice Draw can open MS Visio vsd via libvisio, Is it possible to use this library together with the Apache OpenOffice Draw?
Draw?
Hi, I used to have MS Visio, but that was with a biz. It's far too expensive for me to purchase now, but I have a vsd file I need to work with. Will Draw work at importing a vsd file and if so, where can I get a copy that I know will be malware-free? Thanks in advance:) -- Dawn dawnlau...@gmail.com
4.1.0_release_blocker requested: [Bug 87182] Crash on formatting OLE Draw object
Armin Le Grand has asked for 4.1.0_release_blocker: Bug 87182: Crash on formatting OLE Draw object https://issues.apache.org/ooo/show_bug.cgi?id=87182 --- Additional Comments from Armin Le Grand Comitted, done. Since it is a crash less, not unsafe to fix and may also crash when Draw is used as OLE from other apps I request 4.1.0 release blocker flag. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
review denied: [Bug 124188] CRASH when pasting grouped contents from Draw over a selected image : [Attachment 82591] Avoid NULL pointer access
Oliver-Rainer Wittmann has denied Andre 's request for review: Bug 124188: CRASH when pasting grouped contents from Draw over a selected image https://issues.apache.org/ooo/show_bug.cgi?id=124188 Attachment 82591: Avoid NULL pointer access https://issues.apache.org/ooo/attachment.cgi?id=82591&action=edit --- Additional Comments from Oliver-Rainer Wittmann The patch avoids the crash, but the document is afterwards in an inconsistent state as the anchor attribute for the as-character anchored object inside the corresponding text node is missing. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
review requested: [Bug 124188] CRASH when pasting grouped contents from Draw over a selected image : [Attachment 82591] Avoid NULL pointer access
Andre has asked Oliver-Rainer Wittmann for review: Bug 124188: CRASH when pasting grouped contents from Draw over a selected image https://issues.apache.org/ooo/show_bug.cgi?id=124188 Attachment 82591: Avoid NULL pointer access https://issues.apache.org/ooo/attachment.cgi?id=82591&action=edit - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Suggested modifications to Open Office Draw
Thanks Andrea, looking through the useful suggestions... On 19.01.2014 02:26, Andrea Pescetti wrote: Forwarding to the list. Ian, I don't have any merit for the answers, I was forwarding a message from Armin. Please always include dev@openoffice.apache.org in your responses. If you need more details on how our mailing lists work, see http://openoffice.apache.org/mailing-lists.html ; if you don't receive an answer, make sure you check the archives: http://markmail.org/message/jvt6q5vslflz6u35 or subscribe to the list as explained above. Ian's comments below. Regards, Andrea. Ian Symons wrote: Hello Andrea Thank you for the response. RE 1. Left side ruler. Depending upon the zoom level, numbers from 100 up often form a continuous numeric stream. They can be interpreted, but it is so much easier if you can read it at a glance. Okay, so - as a first step - defining the jumps to new numberings to avoid that would be a good first step? If yes, a enhancement task with a case where this happens in bugzilla would be nice. RE: 2a. Snap Lines, Snap Points and Grid I am talking about objects that help positioning. For example you might set a guide line at Y=100. Then when positioning / modifying shapes, the guide may be clicked on instead of the shape. This is particularly troublesome when a line or point lies on or close to the guideline. When this happens the tiniest movement of the mouse will shift the guide line. This problem would be solved if the guides (or snap point) can be locked preferably via their existing UI dialog box. This would then operate in the same manner as shapes that can be locked in position via their Position & Size UI dialog box. A good suggestion, esp since guides have no undo actions. Maybe a pinpoint close to the edge of the page (helplines are always connected to the outer bounds of the eit window) would be nice, additionally to the possibility to lock them in the dialog. Also worth an enhancement task in bugzilla. RE: 2b. My apologies, I phrased my question badly. Yes, you do have X-Y co-ordinates displayed. Perhaps it is just on my computer (a fairly new 64 bit 2.4GHz Toshiba Qosmio X870 laptop, Windows 8), but the X-Y co-ordinates do not update when slowly and continuously dragging a shape. Also when the movement of the shapes stops for a moment, the X-Y co-ordinates take about one quarter to one third of a second to update. A good update speed would be about a tenth of a second. I think this is due to their nature as being implemented based on execution slots, these have those uppdate times (e.g. when selecting an object and until the sidebar updates). This is generally by purpose and fixed (to avoid too much flicker when rapidly changing selection, e.g. using TAB), but maybe could be improved for the feedback in the footer, Also good for an enhancement task in bugzilla. RE: 2c and 2d. I am referring to the ability to select shapes AND to also select guides THEN group the guides with the shapes. This facility has always existed in Visio. It has several important advantages: (i) When the shapes and selected guidelines are grouped, then the guides are visually removed as unnecessary clutter from other object shapes on the screen. (ii) The grouping can be copied and then placed elsewhere upon the screen. This is a common function. Note that the guidelines will have different co-ordinates when the grouping of shapes and guidelines is ungrouped. (iii) I have often done this just to copy a group of guidelines, so that after positioning my copied group, I would then ungroup it and then delete the shape object. (iv) A very common action is to copy a shape with its guides and then paste it onto a different page. Also a good suggestion, the advantages are true. I have currently no idea how that could be done, but also a candidate for an enhancement task in bugzilla. RE: 2e and 2f. Ah, thank you. I had in fact set this up when I first started using Draw. Now I do not know if it is the default setting, but Snap to Grid is best selected rather than Visible grid. My error was that I had it set to Visible grid. I use Snap to Grid with a 1 mm resolution with 10 subdivisions. The reason for this is that whatever resolution that you select as default, most of your drawing will use that setting. In the case where you do want an off-grid point, you either use a UI dialog box, set guidelines via a UI dialog box, or zoom into the view you want. When zooming, the visible grid is very handy as a reference, but not if objects snap to it as changing the zoom level is a constant process during drawing. Having said all this it would be great if direct access to this UI was made possible via an additional icon it the View-Toolbars-Options bar. You can configure that to every toolbar you like, just use the rightmost small button of the toolbar you want and add it in the dialog. Again, thanks for the great response. Best
Re: Suggested modifications to Open Office Draw
Forwarding to the list. Ian, I don't have any merit for the answers, I was forwarding a message from Armin. Please always include dev@openoffice.apache.org in your responses. If you need more details on how our mailing lists work, see http://openoffice.apache.org/mailing-lists.html ; if you don't receive an answer, make sure you check the archives: http://markmail.org/message/jvt6q5vslflz6u35 or subscribe to the list as explained above. Ian's comments below. Regards, Andrea. Ian Symons wrote: Hello Andrea Thank you for the response. RE 1. Left side ruler. Depending upon the zoom level, numbers from 100 up often form a continuous numeric stream. They can be interpreted, but it is so much easier if you can read it at a glance. RE: 2a. Snap Lines, Snap Points and Grid I am talking about objects that help positioning. For example you might set a guide line at Y=100. Then when positioning / modifying shapes, the guide may be clicked on instead of the shape. This is particularly troublesome when a line or point lies on or close to the guideline. When this happens the tiniest movement of the mouse will shift the guide line. This problem would be solved if the guides (or snap point) can be locked preferably via their existing UI dialog box. This would then operate in the same manner as shapes that can be locked in position via their Position & Size UI dialog box. RE: 2b. My apologies, I phrased my question badly. Yes, you do have X-Y co-ordinates displayed. Perhaps it is just on my computer (a fairly new 64 bit 2.4GHz Toshiba Qosmio X870 laptop, Windows 8), but the X-Y co-ordinates do not update when slowly and continuously dragging a shape. Also when the movement of the shapes stops for a moment, the X-Y co-ordinates take about one quarter to one third of a second to update. A good update speed would be about a tenth of a second. RE: 2c and 2d. I am referring to the ability to select shapes AND to also select guides THEN group the guides with the shapes. This facility has always existed in Visio. It has several important advantages: (i) When the shapes and selected guidelines are grouped, then the guides are visually removed as unnecessary clutter from other object shapes on the screen. (ii) The grouping can be copied and then placed elsewhere upon the screen. This is a common function. Note that the guidelines will have different co-ordinates when the grouping of shapes and guidelines is ungrouped. (iii) I have often done this just to copy a group of guidelines, so that after positioning my copied group, I would then ungroup it and then delete the shape object. (iv) A very common action is to copy a shape with its guides and then paste it onto a different page. RE: 2e and 2f. Ah, thank you. I had in fact set this up when I first started using Draw. Now I do not know if it is the default setting, but Snap to Grid is best selected rather than Visible grid. My error was that I had it set to Visible grid. I use Snap to Grid with a 1 mm resolution with 10 subdivisions. The reason for this is that whatever resolution that you select as default, most of your drawing will use that setting. In the case where you do want an off-grid point, you either use a UI dialog box, set guidelines via a UI dialog box, or zoom into the view you want. When zooming, the visible grid is very handy as a reference, but not if objects snap to it as changing the zoom level is a constant process during drawing. Having said all this it would be great if direct access to this UI was made possible via an additional icon it the View-Toolbars-Options bar. Again, thanks for the great response. Best regards, Ian On Saturday, 18 January 2014 3:10 AM, Andrea Pescetti wrote: Forwarding Armin's answer (below) to Ian who is not subscribed. Andrea On 16/01/2014 Armin Le Grand wrote: > Hi Ian, > > thanks for your suggestions, much appreciated. Some are pretty > interesting. Comments inline... > > On 15.01.2014 20:27, Ian Symons wrote: >> Ian >> Symons >> ian.sym...@yahoo.com.au <mailto:ian.sym...@yahoo.com.au> >> >> 15 >> Jan 2014 >> >> dev@openoffice.apache.org <mailto:dev@openoffice.apache.org> >> >> RE: >> Suggested modifications to Open Office Draw >> >> Hello, >> >> The >> following suggestions generally have work around solutions, however >> performing such is a real pain when these are common actions. >> >> 1. >> Re >> the ruler on the left side, please orientate the numbers >> horizontally. >> The >> vertical numbering blends together and is unreadable. > > I have not seen it blend togethter, but I agree that these would be less > irritating when done horizontally. > >> >> 2. >> Re >> Snap Lines, Snap Points and Grid >> a. >> I
Re: Suggested modifications to Open Office Draw
Forwarding Armin's answer (below) to Ian who is not subscribed. Andrea On 16/01/2014 Armin Le Grand wrote: Hi Ian, thanks for your suggestions, much appreciated. Some are pretty interesting. Comments inline... On 15.01.2014 20:27, Ian Symons wrote: Ian Symons ian.sym...@yahoo.com.au 15 Jan 2014 dev@openoffice.apache.org RE: Suggested modifications to Open Office Draw Hello, The following suggestions generally have work around solutions, however performing such is a real pain when these are common actions. 1. Re the ruler on the left side, please orientate the numbers horizontally. The vertical numbering blends together and is unreadable. I have not seen it blend togethter, but I agree that these would be less irritating when done horizontally. 2. Re Snap Lines, Snap Points and Grid a. It is a common error that when positioning lines and shapes that the Snap Line or Snap Point is accidentally moved slightly. This is often not noticed immediately. Please provide an option to lock these Snaps into their set position. Doy you talk about - objects that get placed or - objects which help positioning (HelpLines, Grid, edges of existing objects, ...) here? If you have cases where there is a misplacement in snapping, please provide a reproducable example, this would be an error. Please note that snapping can be influenced while in action by pressing qualifiers (shift, ctrl, tab) and by changing snap features (see view/toolbars/options in draw). Note that you can create helplines with start to drag on the rulers, they even have an UI for setting them to precise positions. b. It would also be nice when dragging such Snaps that the X-Y co-ordinates are displayed during the dragging, This is in the last line of the app at the left; a text and measurements dependent of the type of action is displayed. The idea to keep this after MouseUp for a defined time is nice, especially since the reason is very good. and displayed for say 1 second after the mouse button is released. It provides confirmation to the user that the setting was not altered upon releasing the mouse button. c. It would be very good if the Snaps could be grouped with an object and: I do not understand if "Snaps" are the graphic objects or snap helper pobjects; of course graphic objects can be grouped. d. that upon copying and pasting onto another page that those Snaps are also retained (the position would be relative to where you placed the group on the page). Also not clear. The grid on the destinatopnmay be defined dofferent, do you want that to be changed when pasting? e. I do not know if there is already a way to do this, but it would be a big help if when dragging Snaps that they would snap to the selected grid. They do depending on the settings f. And I do not see any way to specify the grid divisions. Again, this would be a help. See tools/options/draw/grid 3. Please provide a line circular arc tool that lets you: a. Specify the origin (point of rotation) b. Specify the radius c. Specify the arc begin angle d. Specify the arc end angle e. Allows an option to close the curve at the origin to create a segment In the drawing toolbar, use the rightmost dropdown from the toolbar itself, choose customize. Use "add", Seelct "drawing" left, add what you need. Best is to add "Ellipse", there are two, use the general one which adds another drop-down toolbox to the menu. 4. Please provide a line arc tool that lets you click on a line and convert it to a circular arc – the point would appear at the centre of the line and be dragged at a normal to the line So instead of Modify – To Curve you would also have Modify – To Circular Curve You should be able to do that using the Points mode (see icon or press F8 in draw/impress) and using the bezier stuff. 5. Please provide an option to allow a line to be specified in two ways, shown on the one dialog box a. Origin, length and angle b. Begin point and end point This is missing, only pos/size is available for the object, so if it's a line you can define the start/end point exactly. 6. It is a real major pain that intersecting lines cannot be selected and fragmented at their intersecting point(s). Please fix this. Not possible with lines; would need to constuct filled objects including the lines, using substract and extract the results. Good suggestion to offer that with lines directly. 7. Please make it easy to add onto a line by clicking onto a line, selecting an end point, then selecting a line tool (line, arc, polygon) and then just use that line tool to extend the original line. You can add/remove/edit points using the edit points toolbar 8. Lastly, I know this is not intended to be a 3D Cad program. But a few features would help. a. Have the ability to group several shapes before rotation. This is possible, group or just multi-select what you need b. When the 3D view comes up, have butto
Re: Suggested modifications to Open Office Draw
Hi Ian, thanks for your suggestions, much appreciated. Some are pretty interesting. Comments inline... On 15.01.2014 20:27, Ian Symons wrote: Ian Symons ian.sym...@yahoo.com.au 15 Jan 2014 dev@openoffice.apache.org RE: Suggested modifications to Open Office Draw Hello, The following suggestions generally have work around solutions, however performing such is a real pain when these are common actions. 1. Re the ruler on the left side, please orientate the numbers horizontally. The vertical numbering blends together and is unreadable. I have not seen it blend togethter, but I agree that these would be less irritating when done horizontally. 2. Re Snap Lines, Snap Points and Grid a. It is a common error that when positioning lines and shapes that the Snap Line or Snap Point is accidentally moved slightly. This is often not noticed immediately. Please provide an option to lock these Snaps into their set position. Doy you talk about - objects that get placed or - objects which help positioning (HelpLines, Grid, edges of existing objects, ...) here? If you have cases where there is a misplacement in snapping, please provide a reproducable example, this would be an error. Please note that snapping can be influenced while in action by pressing qualifiers (shift, ctrl, tab) and by changing snap features (see view/toolbars/options in draw). Note that you can create helplines with start to drag on the rulers, they even have an UI for setting them to precise positions. b. It would also be nice when dragging such Snaps that the X-Y co-ordinates are displayed during the dragging, This is in the last line of the app at the left; a text and measurements dependent of the type of action is displayed. The idea to keep this after MouseUp for a defined time is nice, especially since the reason is very good. and displayed for say 1 second after the mouse button is released. It provides confirmation to the user that the setting was not altered upon releasing the mouse button. c. It would be very good if the Snaps could be grouped with an object and: I do not understand if "Snaps" are the graphic objects or snap helper pobjects; of course graphic objects can be grouped. d. that upon copying and pasting onto another page that those Snaps are also retained (the position would be relative to where you placed the group on the page). Also not clear. The grid on the destinatopnmay be defined dofferent, do you want that to be changed when pasting? e. I do not know if there is already a way to do this, but it would be a big help if when dragging Snaps that they would snap to the selected grid. They do depending on the settings f. And I do not see any way to specify the grid divisions. Again, this would be a help. See tools/options/draw/grid 3. Please provide a line circular arc tool that lets you: a. Specify the origin (point of rotation) b. Specify the radius c. Specify the arc begin angle d. Specify the arc end angle e. Allows an option to close the curve at the origin to create a segment In the drawing toolbar, use the rightmost dropdown from the toolbar itself, choose customize. Use "add", Seelct "drawing" left, add what you need. Best is to add "Ellipse", there are two, use the general one which adds another drop-down toolbox to the menu. 4. Please provide a line arc tool that lets you click on a line and convert it to a circular arc – the point would appear at the centre of the line and be dragged at a normal to the line So instead of Modify – To Curve you would also have Modify – To Circular Curve You should be able to do that using the Points mode (see icon or press F8 in draw/impress) and using the bezier stuff. 5. Please provide an option to allow a line to be specified in two ways, shown on the one dialog box a. Origin, length and angle b. Begin point and end point This is missing, only pos/size is available for the object, so if it's a line you can define the start/end point exactly. 6. It is a real major pain that intersecting lines cannot be selected and fragmented at their intersecting point(s). Please fix this. Not possible with lines; would need to constuct filled objects including the lines, using substract and extract the results. Good suggestion to offer that with lines directly. 7. Please make it easy to add onto a line by clicking onto a line, selecting an end point, then selecting a line tool (line, arc, polygon) and then just use that line tool to extend the original line. You can add/remove/edit points using the edit points toolbar 8. Lastly, I know this is not intended to be a 3D Cad program. But a few features would help. a. Have the ability to group several shapes before rotation. This is possible, group or just multi-select what you need b. When the 3D view comes up, have buttons to select the front, top, bottom and side views (a total of 6 views). c. This is a big
Suggested modifications to Open Office Draw
Ian Symons ian.sym...@yahoo.com.au 15 Jan 2014 dev@openoffice.apache.org RE: Suggested modifications to Open Office Draw Hello, The following suggestions generally have work around solutions, however performing such is a real pain when these are common actions. 1. Re the ruler on the left side, please orientate the numbers horizontally. The vertical numbering blends together and is unreadable. 2. Re Snap Lines, Snap Points and Grid a. It is a common error that when positioning lines and shapes that the Snap Line or Snap Point is accidentally moved slightly. This is often not noticed immediately. Please provide an option to lock these Snaps into their set position. b. It would also be nice when dragging such Snaps that the X-Y co-ordinates are displayed during the dragging, and displayed for say 1 second after the mouse button is released. It provides confirmation to the user that the setting was not altered upon releasing the mouse button. c. It would be very good if the Snaps could be grouped with an object and: d. that upon copying and pasting onto another page that those Snaps are also retained (the position would be relative to where you placed the group on the page). e. I do not know if there is already a way to do this, but it would be a big help if when dragging Snaps that they would snap to the selected grid. f. And I do not see any way to specify the grid divisions. Again, this would be a help. 3. Please provide a line circular arc tool that lets you: a. Specify the origin (point of rotation) b. Specify the radius c. Specify the arc begin angle d. Specify the arc end angle e. Allows an option to close the curve at the origin to create a segment 4. Please provide a line arc tool that lets you click on a line and convert it to a circular arc – the point would appear at the centre of the line and be dragged at a normal to the line So instead of Modify – To Curve you would also have Modify – To Circular Curve 5. Please provide an option to allow a line to be specified in two ways, shown on the one dialog box a. Origin, length and angle b. Begin point and end point 6. It is a real major pain that intersecting lines cannot be selected and fragmented at their intersecting point(s). Please fix this. 7. Please make it easy to add onto a line by clicking onto a line, selecting an end point, then selecting a line tool (line, arc, polygon) and then just use that line tool to extend the original line. 8. Lastly, I know this is not intended to be a 3D Cad program. But a few features would help. a. Have the ability to group several shapes before rotation. b. When the 3D view comes up, have buttons to select the front, top, bottom and side views (a total of 6 views). c. This is a big one – some ability to edit 3D shapes Thanks everyone. Best regards, Ian
Re: Impossible to get the button "Vertical Text" activ in the draw bar
Hi Guy, Guy Waterval schrieb: Hi all, Could somebody confirm that ? AOO 4.01 OS : Windows 7 and Linux Mint 15 XFCE I can't say if it was already the case before. You have to check the "Enhanced language support" in Tools > Options >Language Settings > Languages Kind regards Regina - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Impossible to get the button "Vertical Text" activ in the draw bar
Hi all, Could somebody confirm that ? AOO 4.01 OS : Windows 7 and Linux Mint 15 XFCE I can't say if it was already the case before. Many thanks -- gw
4.0.1_release_blocker granted: [Bug 123048] line skew parameter is not read from file for connectors in OO draw
j...@apache.org has granted Armin Le Grand 's request for 4.0.1_release_blocker: Bug 123048: line skew parameter is not read from file for connectors in OO draw https://issues.apache.org/ooo/show_bug.cgi?id=123048 --- Additional Comments from j...@apache.org approve showstopper request again - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
4.0.1_release_blocker requested: [Bug 123048] line skew parameter is not read from file for connectors in OO draw
Armin Le Grand has asked for 4.0.1_release_blocker: Bug 123048: line skew parameter is not read from file for connectors in OO draw https://issues.apache.org/ooo/show_bug.cgi?id=123048 --- Additional Comments from Armin Le Grand @Joe: As long as the flag is not on '+' I see the fix targeted to AOO410. *If* the flag is given, I change it when comitting to AOO401 usually. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
4.0.1_release_blocker granted: [Bug 123048] line skew parameter is not read from file for connectors in OO draw
j...@apache.org has granted Regina Henschel 's request for 4.0.1_release_blocker: Bug 123048: line skew parameter is not read from file for connectors in OO draw https://issues.apache.org/ooo/show_bug.cgi?id=123048 --- Additional Comments from j...@apache.org approve showstopper request - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
4.0.1_release_blocker requested: [Bug 123048] line skew parameter is not read from file for connectors in OO draw
Regina Henschel has asked for 4.0.1_release_blocker: Bug 123048: line skew parameter is not read from file for connectors in OO draw https://issues.apache.org/ooo/show_bug.cgi?id=123048 --- Additional Comments from Regina Henschel It is severe, that existing drawings are destroyed on opening. Therefore I request release blocker. - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Graphical glitches on Draw 4.0
On Mon, 17 Jun 2013 22:10:03 +0200 Juergen Schmidt wrote: > Am Freitag, 14. Juni 2013 um 15:43 schrieb Rory O'Farrell: > > On Fri, 14 Jun 2013 15:24:43 +0200 > > Armin Le Grand wrote: > > > > > Hi Ricardo, > > > > > > as I already wrote in #122456# I am very surprised how something like > > > that can happen. I would be happy to be able to reproduce this. Could > > > you give a step-by-step description and infos about machine/system > > > running on? Maybe put it directly in the task and write that you canks > > > in advance! > > > > > > Sincerely, > > > Armin > > > > > > On 14.06.2013 15:08, RGB ES wrote: > > > > Just draw a thick line and see if you can reproduce this > > > > > > > > http://people.apache.org/~rgb-es/Draw-341vs400.png > > > > > > > > On the left, 3.4.1, on the right, 4.0. As you can see, handlers are > > > > misplaced on 4.0. There is also a lot of "noise" when you move an object > > > > around con 4.0 > > > > > > > > http://people.apache.org/~rgb-es/Draw-400noise.png > > > > > > > > This problem is absent on 3.4.1. > > > > > > > > I'm testing the 64 bits Linux build. From the Help → About > > > > > > > > AOO400m2(Build:9701) - Rev. 1491860 > > > > 2013-06-11 15:16:25 (Tue, 11 Jun 2013) - Linux x86_64 > > > > > > > > Refreshing the screen with Ctrl-Shift-R fix the second problem, but not > > > > the > > > > first one. I cannot find any related issue in bugzilla. > > > > > > > > One user on ES forums reported that boxes like font name/size are not > > > > repainting for him, but I cannot reproduce that. > > > > > > > > Regards > > > > Ricardo > > > > > > > > > > -- > > > ALG > > > > > > > > > I have just tested this and I'm getting the same effect using AOO 4.0.2 > > (buld 1489073) on Xubuntu 12.10. > please don't use such a version number 4.0.2, we don't have released a 4.0.0 > yet and it can be very confusing for external readers. I may have been mistaken; I remembered that as the version number and didn't check. Installing AOO 4 on another machine it said it was 4.0.0-2 during the install and perhaps that is what I misremembered. In any case the build number is the significant item. > > Juergen > > Also, with a wide line (24pt) the corners of the line away from the green > > handles are clipped (bevelled) perhaps by the bounding box of the > > selection. Also, draw a rectangle or square using the thick line. The four > > lines are offset from the desired position: that is the wide line is being > > drawn to one side of the target position, instead of being centred on it, > > and the top and left lines are the correct width, but the bottom and right > > lines are narrower. > > > > Using the sidepanel, I am only able to alter the line width using the spin > > buttons (up/down arrows beside the width selector. I cannot highlight ad > > enter a value direct into the line width selector. > > > > > > -- > > Rory O'Farrell > > > > - > > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > > For additional commands, e-mail: dev-h...@openoffice.apache.org > > > > > > -- Rory O'Farrell - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Graphical glitches on Draw 4.0
Am Freitag, 14. Juni 2013 um 15:43 schrieb Rory O'Farrell: > On Fri, 14 Jun 2013 15:24:43 +0200 > Armin Le Grand wrote: > > > Hi Ricardo, > > > > as I already wrote in #122456# I am very surprised how something like > > that can happen. I would be happy to be able to reproduce this. Could > > you give a step-by-step description and infos about machine/system > > running on? Maybe put it directly in the task and write that you canks > > in advance! > > > > Sincerely, > > Armin > > > > On 14.06.2013 15:08, RGB ES wrote: > > > Just draw a thick line and see if you can reproduce this > > > > > > http://people.apache.org/~rgb-es/Draw-341vs400.png > > > > > > On the left, 3.4.1, on the right, 4.0. As you can see, handlers are > > > misplaced on 4.0. There is also a lot of "noise" when you move an object > > > around con 4.0 > > > > > > http://people.apache.org/~rgb-es/Draw-400noise.png > > > > > > This problem is absent on 3.4.1. > > > > > > I'm testing the 64 bits Linux build. From the Help → About > > > > > > AOO400m2(Build:9701) - Rev. 1491860 > > > 2013-06-11 15:16:25 (Tue, 11 Jun 2013) - Linux x86_64 > > > > > > Refreshing the screen with Ctrl-Shift-R fix the second problem, but not > > > the > > > first one. I cannot find any related issue in bugzilla. > > > > > > One user on ES forums reported that boxes like font name/size are not > > > repainting for him, but I cannot reproduce that. > > > > > > Regards > > > Ricardo > > > > > > > -- > > ALG > > > > > I have just tested this and I'm getting the same effect using AOO 4.0.2 (buld > 1489073) on Xubuntu 12.10. please don't use such a version number 4.0.2, we don't have released a 4.0.0 yet and it can be very confusing for external readers. Juergen > Also, with a wide line (24pt) the corners of the line away from the green > handles are clipped (bevelled) perhaps by the bounding box of the selection. > Also, draw a rectangle or square using the thick line. The four lines are > offset from the desired position: that is the wide line is being drawn to one > side of the target position, instead of being centred on it, and the top and > left lines are the correct width, but the bottom and right lines are narrower. > > Using the sidepanel, I am only able to alter the line width using the spin > buttons (up/down arrows beside the width selector. I cannot highlight ad > enter a value direct into the line width selector. > > > -- > Rory O'Farrell > > - > To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
Re: Graphical glitches on Draw 4.0
On Fri, 14 Jun 2013 17:06:18 +0200 Armin Le Grand wrote: > On 14.06.2013 16:59, Rory O'Farrell wrote: > > On Fri, 14 Jun 2013 15:41:24 +0100 > > The problem still exists in AOO build 1491860 on Ubuntu, although not on > > the Windows version of that build. > Yes, the commit is r1493078, you will need some patience ;-) > > > > Also, on Windows version (same build) the line widths are predetermined, on > > the side panel I could find no selection box into which one can enter a > > desired line width, or adjust the line width using the up/down arrows. To > > test in Windows, I had to use the line width selector on the Toolbar. > In the Line panel (which you should see) is the Width dropdown. Drop it > down to see predefined widths and a input box for custom value. > HTH! > > Got it now, Armin! I was getting the custom line widths, but was working in too small a window, so that the input box fell under the window edge. -- Rory O'Farrell - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Graphical glitches on Draw 4.0
2013/6/14 Armin Le Grand > Hi Ricrado, > > how do I open webm format...? > Interested because I still look for a good format/tooling to do some > screencasts for the AOO4.0 feature page ;-) > VLC. But be sure to install all codecs first. I did a clumsy screencast of the sidebar some days ago: http://youtu.be/L4T1uTn7p0U I still need to learn how to do those things better... I used a strange tandem: RecordItNow on top of RecordMyDesktop, setting the bitrate of it (through RecordItNow UI) to 200. But that only provides ogv videos that are not accepted by youtube, so I converted the ogv to webm with VLC, to obtain a video of same quality but something like one third of its size :) Regards Ricardo > > Sincerely, > Armin > > On 14.06.2013 16:20, RGB ES wrote: > >> 2013/6/14 Armin Le Grand >> >> Hi Rory, >>> >>> Thanks a lot! I can now reproduce, recativated the task and I am on it >>> ;-) >>> >>> You are fast! While I was submitting a short screencast to the report, >> you >> fixed it! Many thanks!! >> >> Regards >> Ricardo >> >> >> >> >> Sincerely, >>> Armin >>> >>> >>> On 14.06.2013 15:47, Rory O'Farrell wrote: >>> >>> On Fri, 14 Jun 2013 14:43:22 +0100 >>>> Rory O'Farrell wrote: >>>> >>>> On Fri, 14 Jun 2013 15:24:43 +0200 >>>> >>>>> Armin Le Grand wrote: >>>>> >>>>> Hi Ricardo, >>>>> >>>>>> as I already wrote in #122456# I am very surprised how something like >>>>>> that can happen. I would be happy to be able to reproduce this. Could >>>>>> you give a step-by-step description and infos about machine/system >>>>>> running on? Maybe put it directly in the task and write that you canks >>>>>> in advance! >>>>>> >>>>>> Sincerely, >>>>>>Armin >>>>>> >>>>>> On 14.06.2013 15:08, RGB ES wrote: >>>>>> >>>>>> Just draw a thick line and see if you can reproduce this >>>>>>> >>>>>>> http://people.apache.org/~rgb-es/Draw-341vs400.png<http://people.apache.org/~rgb-**es/Draw-341vs400.png> >>>>>>> <http://**people.apache.org/~rgb-es/**Draw-341vs400.png<http://people.apache.org/~rgb-es/Draw-341vs400.png> >>>>>>> > >>>>>>> >>>>>>> >>>>>>> On the left, 3.4.1, on the right, 4.0. As you can see, handlers are >>>>>>> misplaced on 4.0. There is also a lot of "noise" when you move an >>>>>>> object >>>>>>> around con 4.0 >>>>>>> >>>>>>> http://people.apache.org/~rgb-es/Draw-400noise.png<http://people.apache.org/~rgb-**es/Draw-400noise.png> >>>>>>> <http://**people.apache.org/~rgb-es/**Draw-400noise.png<http://people.apache.org/~rgb-es/Draw-400noise.png> >>>>>>> > >>>>>>> >>>>>>> >>>>>>> This problem is absent on 3.4.1. >>>>>>> >>>>>>> I'm testing the 64 bits Linux build. From the Help → About >>>>>>> >>>>>>> AOO400m2(Build:9701) - Rev. 1491860 >>>>>>> 2013-06-11 15:16:25 (Tue, 11 Jun 2013) - Linux x86_64 >>>>>>> >>>>>>> Refreshing the screen with Ctrl-Shift-R fix the second problem, but >>>>>>> not the >>>>>>> first one. I cannot find any related issue in bugzilla. >>>>>>> >>>>>>> One user on ES forums reported that boxes like font name/size are not >>>>>>> repainting for him, but I cannot reproduce that. >>>>>>> >>>>>>> Regards >>>>>>> Ricardo >>>>>>> >>>>>>> -- >>>>>>> >>>>>> ALG >>>>>> >>>>>> I have just tested this and I'm getting the same effect using AOO >>>>> 4.0.2 >>>>> (buld 1489073) on Xubuntu 12.10. Also, with a wide line (24pt) the >>>>> corners >>>>> of the line away from the green handles are clipped (bevelled) perhaps >>>>> by >>>>> the bounding box of the selection. Also, draw a rectangle or square >>>>> using >>>>> the thick line. The four lines are offset from the desired position: >>>>> that >>>>> is the wide line is being drawn to one side of the target position, >>>>> instead >>>>> of being centred on it, and the top and left lines are the correct >>>>> width, >>>>> but the bottom and right lines are narrower. >>>>> >>>>> Using the sidepanel, I am only able to alter the line width using the >>>>> spin buttons (up/down arrows beside the width selector. I cannot >>>>> highlight >>>>> ad enter a value direct into the line width selector. >>>>> >>>>> >>>>> -- >>>>> Rory O'Farrell >>>>> >>>>> I follow up immediately to say that Draw prints and Exports as PDF >>>>> >>>> correctly, so the problem is probably localisable to the display module. >>>> >>>> -- >>>> >>> ALG >>> >>> >>> --** >>> --**- >>> To unsubscribe, e-mail: >>> dev-unsubscribe@openoffice.**a**pache.org<http://apache.org> >>> >>> > >>> >>> For additional commands, e-mail: dev-h...@openoffice.apache.org >>> >>> >>> > > --**--**- > To unsubscribe, e-mail: > dev-unsubscribe@openoffice.**apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
Re: Graphical glitches on Draw 4.0
On 14.06.2013 16:59, Rory O'Farrell wrote: On Fri, 14 Jun 2013 15:41:24 +0100 The problem still exists in AOO build 1491860 on Ubuntu, although not on the Windows version of that build. Yes, the commit is r1493078, you will need some patience ;-) Also, on Windows version (same build) the line widths are predetermined, on the side panel I could find no selection box into which one can enter a desired line width, or adjust the line width using the up/down arrows. To test in Windows, I had to use the line width selector on the Toolbar. In the Line panel (which you should see) is the Width dropdown. Drop it down to see predefined widths and a input box for custom value. HTH! - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Graphical glitches on Draw 4.0
On Fri, 14 Jun 2013 15:41:24 +0100 The problem still exists in AOO build 1491860 on Ubuntu, although not on the Windows version of that build. Also, on Windows version (same build) the line widths are predetermined, on the side panel I could find no selection box into which one can enter a desired line width, or adjust the line width using the up/down arrows. To test in Windows, I had to use the line width selector on the Toolbar. -- Rory O'Farrell - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Graphical glitches on Draw 4.0
On Fri, 14 Jun 2013 16:20:25 +0200 RGB ES wrote: > 2013/6/14 Armin Le Grand > > > Hi Rory, > > > > Thanks a lot! I can now reproduce, recativated the task and I am on it ;-) > > > > You are fast! While I was submitting a short screencast to the report, you > fixed it! Many thanks!! > > Regards > Ricardo > > > > > > > > Sincerely, > > Armin > > > > > > On 14.06.2013 15:47, Rory O'Farrell wrote: > > > >> On Fri, 14 Jun 2013 14:43:22 +0100 > >> Rory O'Farrell wrote: > >> > >> On Fri, 14 Jun 2013 15:24:43 +0200 > >>> Armin Le Grand wrote: > >>> > >>>Hi Ricardo, > >>>> > >>>> as I already wrote in #122456# I am very surprised how something like > >>>> that can happen. I would be happy to be able to reproduce this. Could > >>>> you give a step-by-step description and infos about machine/system > >>>> running on? Maybe put it directly in the task and write that you canks > >>>> in advance! > >>>> > >>>> Sincerely, > >>>> Armin > >>>> > >>>> On 14.06.2013 15:08, RGB ES wrote: > >>>> > >>>>> Just draw a thick line and see if you can reproduce this > >>>>> > >>>>> http://people.apache.org/~rgb-**es/Draw-341vs400.png<http://people.apache.org/~rgb-es/Draw-341vs400.png> > >>>>> > >>>>> On the left, 3.4.1, on the right, 4.0. As you can see, handlers are > >>>>> misplaced on 4.0. There is also a lot of "noise" when you move an > >>>>> object > >>>>> around con 4.0 > >>>>> > >>>>> http://people.apache.org/~rgb-**es/Draw-400noise.png<http://people.apache.org/~rgb-es/Draw-400noise.png> > >>>>> > >>>>> This problem is absent on 3.4.1. > >>>>> > >>>>> I'm testing the 64 bits Linux build. From the Help → About > >>>>> > >>>>> AOO400m2(Build:9701) - Rev. 1491860 > >>>>> 2013-06-11 15:16:25 (Tue, 11 Jun 2013) - Linux x86_64 > >>>>> > >>>>> Refreshing the screen with Ctrl-Shift-R fix the second problem, but > >>>>> not the > >>>>> first one. I cannot find any related issue in bugzilla. > >>>>> > >>>>> One user on ES forums reported that boxes like font name/size are not > >>>>> repainting for him, but I cannot reproduce that. > >>>>> > >>>>> Regards > >>>>> Ricardo > >>>>> > >>>>> -- > >>>> ALG > >>>> > >>> I have just tested this and I'm getting the same effect using AOO 4.0.2 > >>> (buld 1489073) on Xubuntu 12.10. Also, with a wide line (24pt) the > >>> corners > >>> of the line away from the green handles are clipped (bevelled) perhaps by > >>> the bounding box of the selection. Also, draw a rectangle or square using > >>> the thick line. The four lines are offset from the desired position: that > >>> is the wide line is being drawn to one side of the target position, > >>> instead > >>> of being centred on it, and the top and left lines are the correct width, > >>> but the bottom and right lines are narrower. > >>> > >>> Using the sidepanel, I am only able to alter the line width using the > >>> spin buttons (up/down arrows beside the width selector. I cannot > >>> highlight > >>> ad enter a value direct into the line width selector. > >>> > >>> > >>> -- > >>> Rory O'Farrell > >>> > >>> I follow up immediately to say that Draw prints and Exports as PDF > >> correctly, so the problem is probably localisable to the display module. > >> > >> -- > > ALG > > > > > > --**--**- Earlier, where I said AO0 4.0.2 I was wrong: it is AOO 4.0.0, but the build number I gave was correct. I have now tried using AOO 4.0.0 (build 1491860) on Windows XP SP2 and the display is good, without the problem. I am using the prebuilt snapshots, not building myself (no time!) -- Rory O'Farrell - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Graphical glitches on Draw 4.0
Hi Ricrado, how do I open webm format...? Interested because I still look for a good format/tooling to do some screencasts for the AOO4.0 feature page ;-) Sincerely, Armin On 14.06.2013 16:20, RGB ES wrote: 2013/6/14 Armin Le Grand Hi Rory, Thanks a lot! I can now reproduce, recativated the task and I am on it ;-) You are fast! While I was submitting a short screencast to the report, you fixed it! Many thanks!! Regards Ricardo Sincerely, Armin On 14.06.2013 15:47, Rory O'Farrell wrote: On Fri, 14 Jun 2013 14:43:22 +0100 Rory O'Farrell wrote: On Fri, 14 Jun 2013 15:24:43 +0200 Armin Le Grand wrote: Hi Ricardo, as I already wrote in #122456# I am very surprised how something like that can happen. I would be happy to be able to reproduce this. Could you give a step-by-step description and infos about machine/system running on? Maybe put it directly in the task and write that you canks in advance! Sincerely, Armin On 14.06.2013 15:08, RGB ES wrote: Just draw a thick line and see if you can reproduce this http://people.apache.org/~rgb-**es/Draw-341vs400.png<http://people.apache.org/~rgb-es/Draw-341vs400.png> On the left, 3.4.1, on the right, 4.0. As you can see, handlers are misplaced on 4.0. There is also a lot of "noise" when you move an object around con 4.0 http://people.apache.org/~rgb-**es/Draw-400noise.png<http://people.apache.org/~rgb-es/Draw-400noise.png> This problem is absent on 3.4.1. I'm testing the 64 bits Linux build. From the Help → About AOO400m2(Build:9701) - Rev. 1491860 2013-06-11 15:16:25 (Tue, 11 Jun 2013) - Linux x86_64 Refreshing the screen with Ctrl-Shift-R fix the second problem, but not the first one. I cannot find any related issue in bugzilla. One user on ES forums reported that boxes like font name/size are not repainting for him, but I cannot reproduce that. Regards Ricardo -- ALG I have just tested this and I'm getting the same effect using AOO 4.0.2 (buld 1489073) on Xubuntu 12.10. Also, with a wide line (24pt) the corners of the line away from the green handles are clipped (bevelled) perhaps by the bounding box of the selection. Also, draw a rectangle or square using the thick line. The four lines are offset from the desired position: that is the wide line is being drawn to one side of the target position, instead of being centred on it, and the top and left lines are the correct width, but the bottom and right lines are narrower. Using the sidepanel, I am only able to alter the line width using the spin buttons (up/down arrows beside the width selector. I cannot highlight ad enter a value direct into the line width selector. -- Rory O'Farrell I follow up immediately to say that Draw prints and Exports as PDF correctly, so the problem is probably localisable to the display module. -- ALG --**--**- To unsubscribe, e-mail: dev-unsubscribe@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: Graphical glitches on Draw 4.0
Hi Ricardo, On 14.06.2013 16:20, RGB ES wrote: 2013/6/14 Armin Le Grand Hi Rory, Thanks a lot! I can now reproduce, recativated the task and I am on it ;-) You are fast! While I was submitting a short screencast to the report, you fixed it! Many thanks!! Well, thank you to bring this up again. I had this somewhere in the backhead and hoped to be able to reproduce it. Also I was lucky having a linux build ready for debugging ;-) Regards Ricardo Sincerely, Armin On 14.06.2013 15:47, Rory O'Farrell wrote: On Fri, 14 Jun 2013 14:43:22 +0100 Rory O'Farrell wrote: On Fri, 14 Jun 2013 15:24:43 +0200 Armin Le Grand wrote: Hi Ricardo, as I already wrote in #122456# I am very surprised how something like that can happen. I would be happy to be able to reproduce this. Could you give a step-by-step description and infos about machine/system running on? Maybe put it directly in the task and write that you canks in advance! Sincerely, Armin On 14.06.2013 15:08, RGB ES wrote: Just draw a thick line and see if you can reproduce this http://people.apache.org/~rgb-**es/Draw-341vs400.png<http://people.apache.org/~rgb-es/Draw-341vs400.png> On the left, 3.4.1, on the right, 4.0. As you can see, handlers are misplaced on 4.0. There is also a lot of "noise" when you move an object around con 4.0 http://people.apache.org/~rgb-**es/Draw-400noise.png<http://people.apache.org/~rgb-es/Draw-400noise.png> This problem is absent on 3.4.1. I'm testing the 64 bits Linux build. From the Help → About AOO400m2(Build:9701) - Rev. 1491860 2013-06-11 15:16:25 (Tue, 11 Jun 2013) - Linux x86_64 Refreshing the screen with Ctrl-Shift-R fix the second problem, but not the first one. I cannot find any related issue in bugzilla. One user on ES forums reported that boxes like font name/size are not repainting for him, but I cannot reproduce that. Regards Ricardo -- ALG I have just tested this and I'm getting the same effect using AOO 4.0.2 (buld 1489073) on Xubuntu 12.10. Also, with a wide line (24pt) the corners of the line away from the green handles are clipped (bevelled) perhaps by the bounding box of the selection. Also, draw a rectangle or square using the thick line. The four lines are offset from the desired position: that is the wide line is being drawn to one side of the target position, instead of being centred on it, and the top and left lines are the correct width, but the bottom and right lines are narrower. Using the sidepanel, I am only able to alter the line width using the spin buttons (up/down arrows beside the width selector. I cannot highlight ad enter a value direct into the line width selector. -- Rory O'Farrell I follow up immediately to say that Draw prints and Exports as PDF correctly, so the problem is probably localisable to the display module. -- ALG --**--**- To unsubscribe, e-mail: dev-unsubscribe@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: Graphical glitches on Draw 4.0
2013/6/14 Armin Le Grand > Hi Rory, > > Thanks a lot! I can now reproduce, recativated the task and I am on it ;-) > You are fast! While I was submitting a short screencast to the report, you fixed it! Many thanks!! Regards Ricardo > > Sincerely, > Armin > > > On 14.06.2013 15:47, Rory O'Farrell wrote: > >> On Fri, 14 Jun 2013 14:43:22 +0100 >> Rory O'Farrell wrote: >> >> On Fri, 14 Jun 2013 15:24:43 +0200 >>> Armin Le Grand wrote: >>> >>>Hi Ricardo, >>>> >>>> as I already wrote in #122456# I am very surprised how something like >>>> that can happen. I would be happy to be able to reproduce this. Could >>>> you give a step-by-step description and infos about machine/system >>>> running on? Maybe put it directly in the task and write that you canks >>>> in advance! >>>> >>>> Sincerely, >>>> Armin >>>> >>>> On 14.06.2013 15:08, RGB ES wrote: >>>> >>>>> Just draw a thick line and see if you can reproduce this >>>>> >>>>> http://people.apache.org/~rgb-**es/Draw-341vs400.png<http://people.apache.org/~rgb-es/Draw-341vs400.png> >>>>> >>>>> On the left, 3.4.1, on the right, 4.0. As you can see, handlers are >>>>> misplaced on 4.0. There is also a lot of "noise" when you move an >>>>> object >>>>> around con 4.0 >>>>> >>>>> http://people.apache.org/~rgb-**es/Draw-400noise.png<http://people.apache.org/~rgb-es/Draw-400noise.png> >>>>> >>>>> This problem is absent on 3.4.1. >>>>> >>>>> I'm testing the 64 bits Linux build. From the Help → About >>>>> >>>>> AOO400m2(Build:9701) - Rev. 1491860 >>>>> 2013-06-11 15:16:25 (Tue, 11 Jun 2013) - Linux x86_64 >>>>> >>>>> Refreshing the screen with Ctrl-Shift-R fix the second problem, but >>>>> not the >>>>> first one. I cannot find any related issue in bugzilla. >>>>> >>>>> One user on ES forums reported that boxes like font name/size are not >>>>> repainting for him, but I cannot reproduce that. >>>>> >>>>> Regards >>>>> Ricardo >>>>> >>>>> -- >>>> ALG >>>> >>> I have just tested this and I'm getting the same effect using AOO 4.0.2 >>> (buld 1489073) on Xubuntu 12.10. Also, with a wide line (24pt) the corners >>> of the line away from the green handles are clipped (bevelled) perhaps by >>> the bounding box of the selection. Also, draw a rectangle or square using >>> the thick line. The four lines are offset from the desired position: that >>> is the wide line is being drawn to one side of the target position, instead >>> of being centred on it, and the top and left lines are the correct width, >>> but the bottom and right lines are narrower. >>> >>> Using the sidepanel, I am only able to alter the line width using the >>> spin buttons (up/down arrows beside the width selector. I cannot highlight >>> ad enter a value direct into the line width selector. >>> >>> >>> -- >>> Rory O'Farrell >>> >>> I follow up immediately to say that Draw prints and Exports as PDF >> correctly, so the problem is probably localisable to the display module. >> >> -- > ALG > > > --**--**- > To unsubscribe, e-mail: > dev-unsubscribe@openoffice.**apache.org > For additional commands, e-mail: dev-h...@openoffice.apache.org > >
Re: Graphical glitches on Draw 4.0
Hi Rory, Thanks a lot! I can now reproduce, recativated the task and I am on it ;-) Sincerely, Armin On 14.06.2013 15:47, Rory O'Farrell wrote: On Fri, 14 Jun 2013 14:43:22 +0100 Rory O'Farrell wrote: On Fri, 14 Jun 2013 15:24:43 +0200 Armin Le Grand wrote: Hi Ricardo, as I already wrote in #122456# I am very surprised how something like that can happen. I would be happy to be able to reproduce this. Could you give a step-by-step description and infos about machine/system running on? Maybe put it directly in the task and write that you canks in advance! Sincerely, Armin On 14.06.2013 15:08, RGB ES wrote: Just draw a thick line and see if you can reproduce this http://people.apache.org/~rgb-es/Draw-341vs400.png On the left, 3.4.1, on the right, 4.0. As you can see, handlers are misplaced on 4.0. There is also a lot of "noise" when you move an object around con 4.0 http://people.apache.org/~rgb-es/Draw-400noise.png This problem is absent on 3.4.1. I'm testing the 64 bits Linux build. From the Help → About AOO400m2(Build:9701) - Rev. 1491860 2013-06-11 15:16:25 (Tue, 11 Jun 2013) - Linux x86_64 Refreshing the screen with Ctrl-Shift-R fix the second problem, but not the first one. I cannot find any related issue in bugzilla. One user on ES forums reported that boxes like font name/size are not repainting for him, but I cannot reproduce that. Regards Ricardo -- ALG I have just tested this and I'm getting the same effect using AOO 4.0.2 (buld 1489073) on Xubuntu 12.10. Also, with a wide line (24pt) the corners of the line away from the green handles are clipped (bevelled) perhaps by the bounding box of the selection. Also, draw a rectangle or square using the thick line. The four lines are offset from the desired position: that is the wide line is being drawn to one side of the target position, instead of being centred on it, and the top and left lines are the correct width, but the bottom and right lines are narrower. Using the sidepanel, I am only able to alter the line width using the spin buttons (up/down arrows beside the width selector. I cannot highlight ad enter a value direct into the line width selector. -- Rory O'Farrell I follow up immediately to say that Draw prints and Exports as PDF correctly, so the problem is probably localisable to the display module. -- ALG - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Graphical glitches on Draw 4.0
On Fri, 14 Jun 2013 14:43:22 +0100 Rory O'Farrell wrote: > On Fri, 14 Jun 2013 15:24:43 +0200 > Armin Le Grand wrote: > > > Hi Ricardo, > > > > as I already wrote in #122456# I am very surprised how something like > > that can happen. I would be happy to be able to reproduce this. Could > > you give a step-by-step description and infos about machine/system > > running on? Maybe put it directly in the task and write that you canks > > in advance! > > > > Sincerely, > > Armin > > > > On 14.06.2013 15:08, RGB ES wrote: > > > Just draw a thick line and see if you can reproduce this > > > > > > http://people.apache.org/~rgb-es/Draw-341vs400.png > > > > > > On the left, 3.4.1, on the right, 4.0. As you can see, handlers are > > > misplaced on 4.0. There is also a lot of "noise" when you move an object > > > around con 4.0 > > > > > > http://people.apache.org/~rgb-es/Draw-400noise.png > > > > > > This problem is absent on 3.4.1. > > > > > > I'm testing the 64 bits Linux build. From the Help → About > > > > > > AOO400m2(Build:9701) - Rev. 1491860 > > > 2013-06-11 15:16:25 (Tue, 11 Jun 2013) - Linux x86_64 > > > > > > Refreshing the screen with Ctrl-Shift-R fix the second problem, but not > > > the > > > first one. I cannot find any related issue in bugzilla. > > > > > > One user on ES forums reported that boxes like font name/size are not > > > repainting for him, but I cannot reproduce that. > > > > > > Regards > > > Ricardo > > > > > -- > > ALG > > I have just tested this and I'm getting the same effect using AOO 4.0.2 (buld > 1489073) on Xubuntu 12.10. Also, with a wide line (24pt) the corners of the > line away from the green handles are clipped (bevelled) perhaps by the > bounding box of the selection. Also, draw a rectangle or square using the > thick line. The four lines are offset from the desired position: that is the > wide line is being drawn to one side of the target position, instead of being > centred on it, and the top and left lines are the correct width, but the > bottom and right lines are narrower. > > Using the sidepanel, I am only able to alter the line width using the spin > buttons (up/down arrows beside the width selector. I cannot highlight ad > enter a value direct into the line width selector. > > > -- > Rory O'Farrell > I follow up immediately to say that Draw prints and Exports as PDF correctly, so the problem is probably localisable to the display module. -- Rory O'Farrell - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Graphical glitches on Draw 4.0
On Fri, 14 Jun 2013 15:24:43 +0200 Armin Le Grand wrote: > Hi Ricardo, > > as I already wrote in #122456# I am very surprised how something like > that can happen. I would be happy to be able to reproduce this. Could > you give a step-by-step description and infos about machine/system > running on? Maybe put it directly in the task and write that you canks > in advance! > > Sincerely, > Armin > > On 14.06.2013 15:08, RGB ES wrote: > > Just draw a thick line and see if you can reproduce this > > > > http://people.apache.org/~rgb-es/Draw-341vs400.png > > > > On the left, 3.4.1, on the right, 4.0. As you can see, handlers are > > misplaced on 4.0. There is also a lot of "noise" when you move an object > > around con 4.0 > > > > http://people.apache.org/~rgb-es/Draw-400noise.png > > > > This problem is absent on 3.4.1. > > > > I'm testing the 64 bits Linux build. From the Help → About > > > > AOO400m2(Build:9701) - Rev. 1491860 > > 2013-06-11 15:16:25 (Tue, 11 Jun 2013) - Linux x86_64 > > > > Refreshing the screen with Ctrl-Shift-R fix the second problem, but not the > > first one. I cannot find any related issue in bugzilla. > > > > One user on ES forums reported that boxes like font name/size are not > > repainting for him, but I cannot reproduce that. > > > > Regards > > Ricardo > > > -- > ALG I have just tested this and I'm getting the same effect using AOO 4.0.2 (buld 1489073) on Xubuntu 12.10. Also, with a wide line (24pt) the corners of the line away from the green handles are clipped (bevelled) perhaps by the bounding box of the selection. Also, draw a rectangle or square using the thick line. The four lines are offset from the desired position: that is the wide line is being drawn to one side of the target position, instead of being centred on it, and the top and left lines are the correct width, but the bottom and right lines are narrower. Using the sidepanel, I am only able to alter the line width using the spin buttons (up/down arrows beside the width selector. I cannot highlight ad enter a value direct into the line width selector. -- Rory O'Farrell - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Graphical glitches on Draw 4.0
Hi Ricardo, as I already wrote in #122456# I am very surprised how something like that can happen. I would be happy to be able to reproduce this. Could you give a step-by-step description and infos about machine/system running on? Maybe put it directly in the task and write that you canks in advance! Sincerely, Armin On 14.06.2013 15:08, RGB ES wrote: Just draw a thick line and see if you can reproduce this http://people.apache.org/~rgb-es/Draw-341vs400.png On the left, 3.4.1, on the right, 4.0. As you can see, handlers are misplaced on 4.0. There is also a lot of "noise" when you move an object around con 4.0 http://people.apache.org/~rgb-es/Draw-400noise.png This problem is absent on 3.4.1. I'm testing the 64 bits Linux build. From the Help → About AOO400m2(Build:9701) - Rev. 1491860 2013-06-11 15:16:25 (Tue, 11 Jun 2013) - Linux x86_64 Refreshing the screen with Ctrl-Shift-R fix the second problem, but not the first one. I cannot find any related issue in bugzilla. One user on ES forums reported that boxes like font name/size are not repainting for him, but I cannot reproduce that. Regards Ricardo -- ALG - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Graphical glitches on Draw 4.0
2013/6/14, RGB ES : > Just draw a thick line and see if you can reproduce this > > http://people.apache.org/~rgb-es/Draw-341vs400.png > > On the left, 3.4.1, on the right, 4.0. As you can see, handlers are > misplaced on 4.0. There is also a lot of "noise" when you move an object > around con 4.0 > > http://people.apache.org/~rgb-es/Draw-400noise.png > > This problem is absent on 3.4.1. > > I'm testing the 64 bits Linux build. From the Help → About > > AOO400m2(Build:9701) - Rev. 1491860 > 2013-06-11 15:16:25 (Tue, 11 Jun 2013) - Linux x86_64 > > Refreshing the screen with Ctrl-Shift-R fix the second problem, but not the > first one. I cannot find any related issue in bugzilla. > Here you are: https://issues.apache.org/ooo/show_bug.cgi?id=122456 Regards - Tsutomu > One user on ES forums reported that boxes like font name/size are not > repainting for him, but I cannot reproduce that. > > Regards > Ricardo > - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Graphical glitches on Draw 4.0
Just draw a thick line and see if you can reproduce this http://people.apache.org/~rgb-es/Draw-341vs400.png On the left, 3.4.1, on the right, 4.0. As you can see, handlers are misplaced on 4.0. There is also a lot of "noise" when you move an object around con 4.0 http://people.apache.org/~rgb-es/Draw-400noise.png This problem is absent on 3.4.1. I'm testing the 64 bits Linux build. From the Help → About AOO400m2(Build:9701) - Rev. 1491860 2013-06-11 15:16:25 (Tue, 11 Jun 2013) - Linux x86_64 Refreshing the screen with Ctrl-Shift-R fix the second problem, but not the first one. I cannot find any related issue in bugzilla. One user on ES forums reported that boxes like font name/size are not repainting for him, but I cannot reproduce that. Regards Ricardo
Re: Draw, make some changes to gradients
Hi bugreporter99, On 13.06.2013 18:48, bugreporte...@hushmail.com wrote: hey, In Ellipsoid and Rectangular (play with it) the center of the gradient gets to a line. There is no linear transformation to map this to SVG gradients. Anyways there is no mapping to Rectangluar at all. Was trying to cheat but seems not to work the way I want it to look like. For the rectangular gradient I tried to use three instead of two colors, so to imitate a black to white gradient(the old school way) I just used a black to white to black gradient (SVGgradient). Just kind of "mirror" the colors at the middle line/color. http://i39.tinypic.com/302ctw9.png the ellepsoid es even harder to imitate Yes, but that's the 'Axial' type, not too hard and doable as you describe. To make it clear, here is how to find all six types: - start impress - press 'Area' button in the 'Line and Filling' Toolbar (the can in the upper toolbar) - You get the area dialog - There, select the tab 'Gradients' - Play with Type, you have six kinds of gradients - Also play with the other values, lots of things to do here... The types 'Linear' and 'Axial' are simple. The type 'Radial' is simple. The type 'Ellipsoid is *not* simple, put 50% in CenterY and CenterY to see that is has no single *center*. The types 'Square' and 'Rectangular' have similar problems, plus that they are based on rectangles, not available in SVG - close the dialog - create a rectangle, keep it selected - open the dialog again - in the 'Area' tab, select 'Gradient' in the Fill DropDown - Choose any gradient - At 'Increments' at the right, switch off 'Automatic' and choose a small value (e.g. three) ->No way to do that with SVG. Hope this gets clearer now. If you find ways to map these to SVG stuff, tell me, I will be happy. BTW: Didi you commit some tasks in bugzilla for SVG import recently? If yes, thanks for that, I will look asap ;-) Sincerely, Armin On 12.06.2013 at 11:10 AM, "Armin Le Grand" wrote:Hi bugreporter99, On 11.06.2013 17:50, bugreporte...@hushmail.com wrote: Hi, Ah, I see. Just curious; how did you find out, it's not really advertized that they use our code...? ... Did you read (https://blogs.apache.org/OOo/entry/good_news_libreoffice_is_integrating), btw...? I think that's the same page the person posted to the forum I got the information from (actually did not read the article). IIRC I heard it from here: http://en.libreofficeforum.org/node/293#comment-22501 (comment #26) Ah okay. They should at least tell people that it's not useful to write tasks for LO for an AOO-feature. I will not even see them there, I am not working at/for/on LO. >...(problem is the non-linear (irregular) form of the Ellipsoid and Rectangular ones, another problem is that you can select the number of steps in AOO, say just eight and get useful nice effects.) What do you mean by "non-linear (irregular) form of the Ellipsoid and Rectangular" ? is "on-linear (irregular) form of the Ellipsoid " an ellipse with some bumps??? In Ellipsoid and Rectangular (play with it) the center of the gradient gets to a line. There is no linear transformation to map this to SVG gradients. Anyways there is no mapping to Rectangluar at all. ...you can select the number of steps in AOO Which steps do you mean? gradient steps?? Yes. In the fill attributes you can set the step cout to e.g. user-defined 3 steps. This is useful in arious cases, but will also not map to SVG where this is not possible. regards. On 10.06.2013 at 10:36 AM, "Armin Le Grand" wrote:Hi bugreporter99, [deletd some older stuff here] -- ALG - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org -- ALG - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Draw, make some changes to gradients
Hi, bugreporte...@hushmail.com schrieb: hey, In Ellipsoid and Rectangular (play with it) the center of the gradient gets to a line. There is no linear transformation to map this to SVG gradients. Anyways there is no mapping to Rectangluar at all. Was trying to cheat but seems not to work the way I want it to look like. For the rectangular gradient I tried to use three instead of two colors, so to imitate a black to white gradient(the old school way) I just used a black to white to black gradient (SVGgradient). Just kind of "mirror" the colors at the middle line/color. http://i39.tinypic.com/302ctw9.png the ellepsoid es even harder to imitate This simple kind of gradient you made with Inkscape in that picture is called "Axial" in AOO. Kind regards Regina - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Draw, make some changes to gradients
hey, >In Ellipsoid and Rectangular (play with it) the center of the gradient >gets to a line. There is no linear transformation to map this to SVG >gradients. Anyways there is no mapping to Rectangluar at all. Was trying to cheat but seems not to work the way I want it to look like. For the rectangular gradient I tried to use three instead of two colors, so to imitate a black to white gradient(the old school way) I just used a black to white to black gradient (SVGgradient). Just kind of "mirror" the colors at the middle line/color. http://i39.tinypic.com/302ctw9.png the ellepsoid es even harder to imitate On 12.06.2013 at 11:10 AM, "Armin Le Grand" wrote:Hi bugreporter99, On 11.06.2013 17:50, bugreporte...@hushmail.com wrote: > Hi, > >> Ah, I see. Just curious; how did you find out, it's not really >> advertized that they use our code...? > ... >> Did you read >> (https://blogs.apache.org/OOo/entry/good_news_libreoffice_is_integrating), >> btw...? > I think that's the same page the person posted to the forum I got the > information from (actually did not read the article). > IIRC I heard it from here: > http://en.libreofficeforum.org/node/293#comment-22501 > (comment #26) Ah okay. They should at least tell people that it's not useful to write tasks for LO for an AOO-feature. I will not even see them there, I am not working at/for/on LO. > > >...(problem is the non-linear (irregular) form of the Ellipsoid and >> Rectangular ones, another problem is that you can select the number > of >> steps in AOO, say just eight and get useful nice effects.) > What do you mean by "non-linear (irregular) form of the Ellipsoid and > Rectangular" ? > is "on-linear (irregular) form of the Ellipsoid " an ellipse with some > bumps??? In Ellipsoid and Rectangular (play with it) the center of the gradient gets to a line. There is no linear transformation to map this to SVG gradients. Anyways there is no mapping to Rectangluar at all. > >> ...you can select the number of steps in AOO > Which steps do you mean? > gradient steps?? Yes. In the fill attributes you can set the step cout to e.g. user-defined 3 steps. This is useful in arious cases, but will also not map to SVG where this is not possible. > > regards. > > On 10.06.2013 at 10:36 AM, "Armin Le Grand" wrote:Hi bugreporter99, > [deletd some older stuff here] -- ALG - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Draw, make some changes to gradients
Hi bugreporter99, On 11.06.2013 17:50, bugreporte...@hushmail.com wrote: Hi, Ah, I see. Just curious; how did you find out, it's not really advertized that they use our code...? ... Did you read (https://blogs.apache.org/OOo/entry/good_news_libreoffice_is_integrating), btw...? I think that's the same page the person posted to the forum I got the information from (actually did not read the article). IIRC I heard it from here: http://en.libreofficeforum.org/node/293#comment-22501 (comment #26) Ah okay. They should at least tell people that it's not useful to write tasks for LO for an AOO-feature. I will not even see them there, I am not working at/for/on LO. >...(problem is the non-linear (irregular) form of the Ellipsoid and Rectangular ones, another problem is that you can select the number of steps in AOO, say just eight and get useful nice effects.) What do you mean by "non-linear (irregular) form of the Ellipsoid and Rectangular" ? is "on-linear (irregular) form of the Ellipsoid " an ellipse with some bumps??? In Ellipsoid and Rectangular (play with it) the center of the gradient gets to a line. There is no linear transformation to map this to SVG gradients. Anyways there is no mapping to Rectangluar at all. ...you can select the number of steps in AOO Which steps do you mean? gradient steps?? Yes. In the fill attributes you can set the step cout to e.g. user-defined 3 steps. This is useful in arious cases, but will also not map to SVG where this is not possible. regards. On 10.06.2013 at 10:36 AM, "Armin Le Grand" wrote:Hi bugreporter99, [deletd some older stuff here] -- ALG - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Draw, make some changes to gradients
Hi, >Ah, I see. Just curious; how did you find out, it's not really >advertized that they use our code...? ... >Did you read >(https://blogs.apache.org/OOo/entry/good_news_libreoffice_is_integrating), >btw...? I think that's the same page the person posted to the forum I got the information from (actually did not read the article). IIRC I heard it from here: http://en.libreofficeforum.org/node/293#comment-22501 (comment #26) >...(problem is the non-linear (irregular) form of the Ellipsoid and >Rectangular ones, another problem is that you can select the number of >steps in AOO, say just eight and get useful nice effects.) What do you mean by "non-linear (irregular) form of the Ellipsoid and Rectangular" ? is "on-linear (irregular) form of the Ellipsoid " an ellipse with some bumps??? >...you can select the number of steps in AOO Which steps do you mean? gradient steps?? regards. On 10.06.2013 at 10:36 AM, "Armin Le Grand" wrote:Hi bugreporter99, On 07.06.2013 18:24, bugreporte...@hushmail.com wrote: > Hi Armin, > > I reported the bugs to the LO bugzilla. After finding out that AOO > sarted the svg import stuff and LO adopted/is adopting it I started to > look at AOO. Ah, I see. Just curious; how did you find out, it's not really advertized that they use our code...? > So the current bugs I found are somewhere here: > https://www.libreoffice.org/bugzilla/buglist.cgi?component=Drawing&product=LibreOffice&query_format=advanced&resolution=---&order=bug_id%20DESC&query_based_on= > starting at 64457 and ending at about 64550 (so somewhere in between > this to bug IDs I think) I cannot work on LO tasks, please consider to commit these in AOO, too. Of course after having a look which still exist, I aloready fixed some, working together with another guy who also found out who really is behind SVG import and did it... Did you read (https://blogs.apache.org/OOo/entry/good_news_libreoffice_is_integrating), btw...? >> There is an interactive gradient edit mode, have you seen it? It's >> a little bit hidden... > Thanks for the hint will look at this one. > Because I thought that the old gradient stuff can be also done in the > svg way I thought of replacing the old gradient with > the new one. For example the Border value could be also done with the > hight and width of the gradient in the svg way (at least that's what I > thought). But if that's not possible I guess we would have to have > Gradient and SVGGradient (was thinking like Gradient + SVGGradient == > newawesomeAOOgradient). Something like that. OTOH you made me start again thinking about if it's possible somehoy, baybe together with the possible UserTransformation (problem is the non-linear (irregular) form of the Ellipsoid and Rectangular ones, another problem is that you can select the number of steps in AOO, say just eight and get useful nice effects.) Sincerely, Armin > > regards. > > On 07.06.2013 at 10:16 AM, "Armin Le Grand" wrote:Hi bugreporter99, > > I see no changes to the old gradient sizes; that's because these are > historically grown and should not be touched at all. They do not have > own pos/size or whatever attributes, they are just using the area they > > are set at. Historically (a lot has changed since then, but to make > clear why it is as it is): > > - The area wich is maximally covered (and needs to be painted) is > calculated in pixels (no double precision) > - This leads to a boundrect > - The to be filled geometry is set as mask > - Number of steps (as Integer) is calculated > - For left/R/T/B an integer add is calculyted to shrink that rect > (radial: same, ellipse: different) > - In a loop for n steps the rectangle is shrunk by these values, but > there were 'if's to not let it overlap itself > - The rectangle is filled with a calculated color with rect or ellipse > > This cannot even be direclty mapped to a transformation (mix of > local/discrete coordinate system) and depends on object rotation (!). > It > was a lot of work to get this mapped to transformations to 'emulate' > it > in primitive rendering at all (argh), but it works now. Today a > primitive is used, all is in double precision. Still, the basic > principle from the older days has to be used (the boundrect in world > coordinates) to make it look the same, you do not want older loaded > files to look diffeent, do you? > > BTW: There is an interactive gradient edit mode, have you seen it? > It's > a little bit hidden. Open draw, create a shape with gradient, in the > drawing toolber (normally at the bottom) there is a 'effects' DropDown > > (normally on rotation). Drop it down (or undock
Re: Draw, make some changes to gradients
Hi bugreporter99, On 07.06.2013 18:24, bugreporte...@hushmail.com wrote: Hi Armin, I reported the bugs to the LO bugzilla. After finding out that AOO sarted the svg import stuff and LO adopted/is adopting it I started to look at AOO. Ah, I see. Just curious; how did you find out, it's not really advertized that they use our code...? So the current bugs I found are somewhere here: https://www.libreoffice.org/bugzilla/buglist.cgi?component=Drawing&product=LibreOffice&query_format=advanced&resolution=---&order=bug_id%20DESC&query_based_on= starting at 64457 and ending at about 64550 (so somewhere in between this to bug IDs I think) I cannot work on LO tasks, please consider to commit these in AOO, too. Of course after having a look which still exist, I aloready fixed some, working together with another guy who also found out who really is behind SVG import and did it... Did you read (https://blogs.apache.org/OOo/entry/good_news_libreoffice_is_integrating), btw...? There is an interactive gradient edit mode, have you seen it? It's a little bit hidden... Thanks for the hint will look at this one. Because I thought that the old gradient stuff can be also done in the svg way I thought of replacing the old gradient with the new one. For example the Border value could be also done with the hight and width of the gradient in the svg way (at least that's what I thought). But if that's not possible I guess we would have to have Gradient and SVGGradient (was thinking like Gradient + SVGGradient == newawesomeAOOgradient). Something like that. OTOH you made me start again thinking about if it's possible somehoy, baybe together with the possible UserTransformation (problem is the non-linear (irregular) form of the Ellipsoid and Rectangular ones, another problem is that you can select the number of steps in AOO, say just eight and get useful nice effects.) Sincerely, Armin regards. On 07.06.2013 at 10:16 AM, "Armin Le Grand" wrote:Hi bugreporter99, I see no changes to the old gradient sizes; that's because these are historically grown and should not be touched at all. They do not have own pos/size or whatever attributes, they are just using the area they are set at. Historically (a lot has changed since then, but to make clear why it is as it is): - The area wich is maximally covered (and needs to be painted) is calculated in pixels (no double precision) - This leads to a boundrect - The to be filled geometry is set as mask - Number of steps (as Integer) is calculated - For left/R/T/B an integer add is calculyted to shrink that rect (radial: same, ellipse: different) - In a loop for n steps the rectangle is shrunk by these values, but there were 'if's to not let it overlap itself - The rectangle is filled with a calculated color with rect or ellipse This cannot even be direclty mapped to a transformation (mix of local/discrete coordinate system) and depends on object rotation (!). It was a lot of work to get this mapped to transformations to 'emulate' it in primitive rendering at all (argh), but it works now. Today a primitive is used, all is in double precision. Still, the basic principle from the older days has to be used (the boundrect in world coordinates) to make it look the same, you do not want older loaded files to look diffeent, do you? BTW: There is an interactive gradient edit mode, have you seen it? It's a little bit hidden. Open draw, create a shape with gradient, in the drawing toolber (normally at the bottom) there is a 'effects' DropDown (normally on rotation). Drop it down (or undock it), there are more interesting functions there... For the SVG gradients we will have better/changed UI; I am thinking about a dialog form and also interactive support if possible. Suggestions welcome ;-) E.G.: Have it as a new fill mode (then two: Gradient and SVGGradient) or as one? One means to change the UI i nthe dialog on gradient selection change, also need a method to determine what kind of gradient to create newly (old ones still need to be creatable). And and and... HTH! On 06.06.2013 22:23, bugreporte...@hushmail.com wrote: Hi, what do you think about the way the size of the gradient should be set (in the future)? I came up with 4 ways: 1. Edit-Box for width and height width/height is set in percentage 2. Edit-Box for width and height width/height is set absolute (mm,cm,inch,...) 3. Edit-Box for width and height width/height is set as a dot seperated value -> 1.0 would be the same width/height as parent width/height 4. NO Edit-Box for width and hight handles on the gradient(on canvas) are used to change the size (the Edit Boxes can be seen in my mockup I sent in the first mail) http://temp-share.com/show/f3Ygit6Xn My opinion 1. cause the size of the gradient can be bigger then the parent's the value would beco
Re: Draw, make some changes to gradients
Hi Armin, I reported the bugs to the LO bugzilla. After finding out that AOO sarted the svg import stuff and LO adopted/is adopting it I started to look at AOO. So the current bugs I found are somewhere here: https://www.libreoffice.org/bugzilla/buglist.cgi?component=Drawing&product=LibreOffice&query_format=advanced&resolution=---&order=bug_id%20DESC&query_based_on= starting at 64457 and ending at about 64550 (so somewhere in between this to bug IDs I think) >There is an interactive gradient edit mode, have you seen it? It's >a little bit hidden... Thanks for the hint will look at this one. Because I thought that the old gradient stuff can be also done in the svg way I thought of replacing the old gradient with the new one. For example the Border value could be also done with the hight and width of the gradient in the svg way (at least that's what I thought). But if that's not possible I guess we would have to have Gradient and SVGGradient (was thinking like Gradient + SVGGradient == newawesomeAOOgradient). regards. On 07.06.2013 at 10:16 AM, "Armin Le Grand" wrote:Hi bugreporter99, I see no changes to the old gradient sizes; that's because these are historically grown and should not be touched at all. They do not have own pos/size or whatever attributes, they are just using the area they are set at. Historically (a lot has changed since then, but to make clear why it is as it is): - The area wich is maximally covered (and needs to be painted) is calculated in pixels (no double precision) - This leads to a boundrect - The to be filled geometry is set as mask - Number of steps (as Integer) is calculated - For left/R/T/B an integer add is calculyted to shrink that rect (radial: same, ellipse: different) - In a loop for n steps the rectangle is shrunk by these values, but there were 'if's to not let it overlap itself - The rectangle is filled with a calculated color with rect or ellipse This cannot even be direclty mapped to a transformation (mix of local/discrete coordinate system) and depends on object rotation (!). It was a lot of work to get this mapped to transformations to 'emulate' it in primitive rendering at all (argh), but it works now. Today a primitive is used, all is in double precision. Still, the basic principle from the older days has to be used (the boundrect in world coordinates) to make it look the same, you do not want older loaded files to look diffeent, do you? BTW: There is an interactive gradient edit mode, have you seen it? It's a little bit hidden. Open draw, create a shape with gradient, in the drawing toolber (normally at the bottom) there is a 'effects' DropDown (normally on rotation). Drop it down (or undock it), there are more interesting functions there... For the SVG gradients we will have better/changed UI; I am thinking about a dialog form and also interactive support if possible. Suggestions welcome ;-) E.G.: Have it as a new fill mode (then two: Gradient and SVGGradient) or as one? One means to change the UI i nthe dialog on gradient selection change, also need a method to determine what kind of gradient to create newly (old ones still need to be creatable). And and and... HTH! On 06.06.2013 22:23, bugreporte...@hushmail.com wrote: > Hi, > > what do you think about the way the size of the gradient should be set > (in the future)? > I came up with 4 ways: > 1. Edit-Box for width and height > width/height is set in percentage > 2. Edit-Box for width and height > width/height is set absolute (mm,cm,inch,...) > 3. Edit-Box for width and height > width/height is set as a dot seperated value > -> 1.0 would be the same width/height as parent width/height > 4. NO Edit-Box for width and hight > handles on the gradient(on canvas) are used to change the size > > (the Edit Boxes can be seen in my mockup I sent in the first mail) > http://temp-share.com/show/f3Ygit6Xn > > My opinion > 1. > cause the size of the gradient can be bigger then the parent's > the value would become bigger than 100% ->weird > 2. > if the size is changed and one want to set it to the parent's size > it's not that simple (unless there is a reset button) > 3. > ok, 1,0 would be the same size as the parent's > 4. > cause in my opinion Draw is mostly used to draw simple stuff > the handles may confuse some people and it may be harder to > implement > (although I would like this option as well, cause that's the way > Inkscape does it) > btw. should the Border Edit Box(in the gradient tab) be replaced with > a width/height Edit Box? > I think if one can set the height and widht the border Edit Box > becomes obsolete??? > where can I get the latest snapshot of AOO > is this one ok?:
Re: Draw, make some changes to gradients
Hi bugreporter99, Ah, forgot one: What about the SVG error reports, I am interested in these ;-) Sincerely, Armin On 06.06.2013 22:23, bugreporte...@hushmail.com wrote: Hi, [stuff deleted] -- ALG - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Draw, make some changes to gradients
Hi bugreporter99, I see no changes to the old gradient sizes; that's because these are historically grown and should not be touched at all. They do not have own pos/size or whatever attributes, they are just using the area they are set at. Historically (a lot has changed since then, but to make clear why it is as it is): - The area wich is maximally covered (and needs to be painted) is calculated in pixels (no double precision) - This leads to a boundrect - The to be filled geometry is set as mask - Number of steps (as Integer) is calculated - For left/R/T/B an integer add is calculyted to shrink that rect (radial: same, ellipse: different) - In a loop for n steps the rectangle is shrunk by these values, but there were 'if's to not let it overlap itself - The rectangle is filled with a calculated color with rect or ellipse This cannot even be direclty mapped to a transformation (mix of local/discrete coordinate system) and depends on object rotation (!). It was a lot of work to get this mapped to transformations to 'emulate' it in primitive rendering at all (argh), but it works now. Today a primitive is used, all is in double precision. Still, the basic principle from the older days has to be used (the boundrect in world coordinates) to make it look the same, you do not want older loaded files to look diffeent, do you? BTW: There is an interactive gradient edit mode, have you seen it? It's a little bit hidden. Open draw, create a shape with gradient, in the drawing toolber (normally at the bottom) there is a 'effects' DropDown (normally on rotation). Drop it down (or undock it), there are more interesting functions there... For the SVG gradients we will have better/changed UI; I am thinking about a dialog form and also interactive support if possible. Suggestions welcome ;-) E.G.: Have it as a new fill mode (then two: Gradient and SVGGradient) or as one? One means to change the UI i nthe dialog on gradient selection change, also need a method to determine what kind of gradient to create newly (old ones still need to be creatable). And and and... HTH! On 06.06.2013 22:23, bugreporte...@hushmail.com wrote: Hi, what do you think about the way the size of the gradient should be set (in the future)? I came up with 4 ways: 1. Edit-Box for width and height width/height is set in percentage 2. Edit-Box for width and height width/height is set absolute (mm,cm,inch,...) 3. Edit-Box for width and height width/height is set as a dot seperated value -> 1.0 would be the same width/height as parent width/height 4. NO Edit-Box for width and hight handles on the gradient(on canvas) are used to change the size (the Edit Boxes can be seen in my mockup I sent in the first mail) http://temp-share.com/show/f3Ygit6Xn My opinion 1. cause the size of the gradient can be bigger then the parent's the value would become bigger than 100% ->weird 2. if the size is changed and one want to set it to the parent's size it's not that simple (unless there is a reset button) 3. ok, 1,0 would be the same size as the parent's 4. cause in my opinion Draw is mostly used to draw simple stuff the handles may confuse some people and it may be harder to implement (although I would like this option as well, cause that's the way Inkscape does it) btw. should the Border Edit Box(in the gradient tab) be replaced with a width/height Edit Box? I think if one can set the height and widht the border Edit Box becomes obsolete??? where can I get the latest snapshot of AOO is this one ok?: https://cwiki.apache.org/OOOUSERS/development-snapshot-builds.html#DevelopmentSnapshotBuilds-AOOSnapshotfullsets I use the LO version from here: http://dev-builds.libreoffice.org/daily/ On 04.06.2013 at 11:31 PM, "Andrea Pescetti" wrote:Forwarding Armin's and Regina's answers, below, to the original poster. bugreporter99: please follow http://mail-archives.apache.org/mod_mbox/openoffice-dev/ to read answers (or subscribe to this list, same link). Andrea Regina Henschel wrote: Hi Armin, Armin Le Grand schrieb: Hi Regina and bugreporter99, a very interesting topic... @bugreporter99: Which tasks did you commit for SVG? I did the SVG import, so these should got to AOO probably, did they...? Using multiple color steps in old gradients: A good idea, I already thought about it. Problem is (as often) that we would need a ODF change for it. Regina, could you think about something like that, please? AOO has not yet implemented the and (ODF 1.2 section 16.40.2 and 16.40.3). They allow multiple stop-colors. The schema has So in this gradient variant, it is already possible to use multiple color steps (and some other nice stuff). Therefore I think, that in a first step this should be implemented. We have start and end colors, in-between colors would have to be so
Re: Draw, make some changes to gradients
On 6/6/13, bugreporte...@hushmail.com wrote: > Hi, > > what do you think about the way the size of the gradient should be set > (in the future)? > I came up with 4 ways: > 1. Edit-Box for width and height >width/height is set in percentage > 2. Edit-Box for width and height >width/height is set absolute (mm,cm,inch,...) > 3. Edit-Box for width and height >width/height is set as a dot seperated value > -> 1.0 would be the same width/height as parent width/height > 4. NO Edit-Box for width and hight >handles on the gradient(on canvas) are used to change the size > > (the Edit Boxes can be seen in my mockup I sent in the first mail) >http://temp-share.com/show/f3Ygit6Xn > > My opinion > 1. >cause the size of the gradient can be bigger then the parent's >the value would become bigger than 100% ->weird I think the dialog should be more graphical and less numerical, most program have both but people end up using the graphical more than the numerical, except when you are cloning something and have pre-defined values. > 2. >if the size is changed and one want to set it to the parent's size >it's not that simple (unless there is a reset button) > 3. > ok, 1,0 would be the same size as the parent's > 4. >cause in my opinion Draw is mostly used to draw simple stuff >the handles may confuse some people and it may be harder to > implement >(although I would like this option as well, cause that's the way > Inkscape does it) > btw. should the Border Edit Box(in the gradient tab) be replaced with > a width/height Edit Box? > I think if one can set the height and widht the border Edit Box > becomes obsolete??? > where can I get the latest snapshot of AOO > is this one ok?: > https://cwiki.apache.org/OOOUSERS/development-snapshot-builds.html#DevelopmentSnapshotBuilds-AOOSnapshotfullsets > > I use the LO version from here: > http://dev-builds.libreoffice.org/daily/ > On 04.06.2013 at 11:31 PM, "Andrea Pescetti" wrote:Forwarding Armin's > and Regina's answers, below, to the original poster. > bugreporter99: please follow > http://mail-archives.apache.org/mod_mbox/openoffice-dev/ to read > answers > (or subscribe to this list, same link). Andrea > > Regina Henschel wrote: >> Hi Armin, >> >> Armin Le Grand schrieb: >>> Hi Regina and bugreporter99, >>> >>> a very interesting topic... >>> @bugreporter99: Which tasks did you commit for SVG? I did the SVG >>> import, so these should got to AOO probably, did they...? >>> >>> Using multiple color steps in old gradients: A good idea, I already >>> thought about it. Problem is (as often) that we would need a ODF > change >>> for it. Regina, could you think about something like that, please? >> >> AOO has not yet implemented the and >> (ODF 1.2 section 16.40.2 and 16.40.3). They allow >> multiple stop-colors. The schema has >> >> So in this gradient variant, it is already possible to use multiple >> color steps (and some other nice stuff). >> >> Therefore I think, that in a first step this should be implemented. I think this would have made a great Google of Summer project. >> >> We >>> have start and end colors, in-between colors would have to be some > value >>> pair of float [0..1] and color value... >> >> The element svg:stop has the attributes >> svg:offset, svg:stop-color, and svg:stop-opacity. >> The offset is double (actual from 0..1) or percent, stop-color is >> #rrggbb, and opacity is double (from 0..1). All is already in the > standard. >> >>> >>> Transparency: I thought myself about this; the current 100-0% > setting to >>> blent the start/end color against black is really not very useful; > it's >>> just handy to not change the color yourself. If adding an alpha > value to >>> each color definition, these value entries in the UI could be > reused. I >>> would guess users who know more modern apps think these values are >>> exactly that, sigh. Also needs a ODF change, though. >> >> It is possible already using stop-opacity. I don't think, that we > should >> go the way to try to get additional attributes/subelements into >> draw:gradient, but implement the two svg-gradients. >> >>> >>> BoundRects of old gradients: This is old stuff some people thought > about >>> 16-20 years ago and of course not state of the art; it was a handy > way >>> to draw these gradients at all (think 640kb systems) and got into > ODF >&g
Re: Draw, make some changes to gradients
Hi, what do you think about the way the size of the gradient should be set (in the future)? I came up with 4 ways: 1. Edit-Box for width and height width/height is set in percentage 2. Edit-Box for width and height width/height is set absolute (mm,cm,inch,...) 3. Edit-Box for width and height width/height is set as a dot seperated value -> 1.0 would be the same width/height as parent width/height 4. NO Edit-Box for width and hight handles on the gradient(on canvas) are used to change the size (the Edit Boxes can be seen in my mockup I sent in the first mail) http://temp-share.com/show/f3Ygit6Xn My opinion 1. cause the size of the gradient can be bigger then the parent's the value would become bigger than 100% ->weird 2. if the size is changed and one want to set it to the parent's size it's not that simple (unless there is a reset button) 3. ok, 1,0 would be the same size as the parent's 4. cause in my opinion Draw is mostly used to draw simple stuff the handles may confuse some people and it may be harder to implement (although I would like this option as well, cause that's the way Inkscape does it) btw. should the Border Edit Box(in the gradient tab) be replaced with a width/height Edit Box? I think if one can set the height and widht the border Edit Box becomes obsolete??? where can I get the latest snapshot of AOO is this one ok?: https://cwiki.apache.org/OOOUSERS/development-snapshot-builds.html#DevelopmentSnapshotBuilds-AOOSnapshotfullsets I use the LO version from here: http://dev-builds.libreoffice.org/daily/ On 04.06.2013 at 11:31 PM, "Andrea Pescetti" wrote:Forwarding Armin's and Regina's answers, below, to the original poster. bugreporter99: please follow http://mail-archives.apache.org/mod_mbox/openoffice-dev/ to read answers (or subscribe to this list, same link). Andrea Regina Henschel wrote: > Hi Armin, > > Armin Le Grand schrieb: >> Hi Regina and bugreporter99, >> >> a very interesting topic... >> @bugreporter99: Which tasks did you commit for SVG? I did the SVG >> import, so these should got to AOO probably, did they...? >> >> Using multiple color steps in old gradients: A good idea, I already >> thought about it. Problem is (as often) that we would need a ODF change >> for it. Regina, could you think about something like that, please? > > AOO has not yet implemented the and > (ODF 1.2 section 16.40.2 and 16.40.3). They allow > multiple stop-colors. The schema has > > So in this gradient variant, it is already possible to use multiple > color steps (and some other nice stuff). > > Therefore I think, that in a first step this should be implemented. > > We >> have start and end colors, in-between colors would have to be some value >> pair of float [0..1] and color value... > > The element svg:stop has the attributes > svg:offset, svg:stop-color, and svg:stop-opacity. > The offset is double (actual from 0..1) or percent, stop-color is > #rrggbb, and opacity is double (from 0..1). All is already in the standard. > >> >> Transparency: I thought myself about this; the current 100-0% setting to >> blent the start/end color against black is really not very useful; it's >> just handy to not change the color yourself. If adding an alpha value to >> each color definition, these value entries in the UI could be reused. I >> would guess users who know more modern apps think these values are >> exactly that, sigh. Also needs a ODF change, though. > > It is possible already using stop-opacity. I don't think, that we should > go the way to try to get additional attributes/subelements into > draw:gradient, but implement the two svg-gradients. > >> >> BoundRects of old gradients: This is old stuff some people thought about >> 16-20 years ago and of course not state of the art; it was a handy way >> to draw these gradients at all (think 640kb systems) and got into ODF >> later, sigh, but cannot be changed >> >> SVG gradients: We already have these in the ODF spec, thus it will be >> better to go forward and offer these for the current draw objects >> directly., I think. Regina, what about ODF here and that it only allows >> one of the SVG mapping modes, I think both should be possible. > > Currently only objectBoundingBox is allowed. I think, that AOO should > have it implemented in a way, that both svg:gradientUnits methods are > possible. If an application supports a feature, it is easier to get it > into ODF. It can be done by using a gradientUnits in an own namespace > and later on, when it is in the ODF, map it to the official one on > reading. For such a namespace, discussion with Thorsten would be useful. > >> &
Re: Draw, make some changes to gradients
Hi Regina, On 04.06.2013 20:07, Regina Henschel wrote: Hi Armin, Armin Le Grand schrieb: Hi Regina and bugreporter99, a very interesting topic... @bugreporter99: Which tasks did you commit for SVG? I did the SVG import, so these should got to AOO probably, did they...? Using multiple color steps in old gradients: A good idea, I already thought about it. Problem is (as often) that we would need a ODF change for it. Regina, could you think about something like that, please? AOO has not yet implemented the and (ODF 1.2 section 16.40.2 and 16.40.3). They allow multiple stop-colors. The schema has So in this gradient variant, it is already possible to use multiple color steps (and some other nice stuff). Therefore I think, that in a first step this should be implemented. Yes, that would be good. We have start and end colors, in-between colors would have to be some value pair of float [0..1] and color value... The element svg:stop has the attributes svg:offset, svg:stop-color, and svg:stop-opacity. The offset is double (actual from 0..1) or percent, stop-color is #rrggbb, and opacity is double (from 0..1). All is already in the standard. Yes, I know SVG ;-) Transparency: I thought myself about this; the current 100-0% setting to blent the start/end color against black is really not very useful; it's just handy to not change the color yourself. If adding an alpha value to each color definition, these value entries in the UI could be reused. I would guess users who know more modern apps think these values are exactly that, sigh. Also needs a ODF change, though. It is possible already using stop-opacity. I don't think, that we should go the way to try to get additional attributes/subelements into draw:gradient, but implement the two svg-gradients. Is it possible to use stop-opacity (and similar stuff) inside the old gradient definitions? I do not think so, maybe I got you wrong here. BoundRects of old gradients: This is old stuff some people thought about 16-20 years ago and of course not state of the art; it was a handy way to draw these gradients at all (think 640kb systems) and got into ODF later, sigh, but cannot be changed SVG gradients: We already have these in the ODF spec, thus it will be better to go forward and offer these for the current draw objects directly., I think. Regina, what about ODF here and that it only allows one of the SVG mapping modes, I think both should be possible. Currently only objectBoundingBox is allowed. I think, that AOO should have it implemented in a way, that both svg:gradientUnits methods are possible. Yes, +1 If an application supports a feature, it is easier to get it into ODF. It can be done by using a gradientUnits in an own namespace and later on, when it is in the ODF, map it to the official one on reading. For such a namespace, discussion with Thorsten would be useful. Yes, changes happened without them discussing outside their ecosystem at all, we should not do the same. With all this, do not forget: More transparency makes all stuff more fancy, BUT also makes printing more expensive (preparation, handling) and also PDF export, especially PDF1/A stuff that does not allow transparencies at all... But that is needed already for proper rendering of svg graphics. So hopefully many parts can be reused. It works, it was just a remark that adding even more transparency is not fancy in all areas. There are areas where transparecy is not so welcome (ask people who need PDF1/A and maybe printer driver developers ;-) I'm not the right person to do it, but shouldn't be the way to use modern graphic cards for the calculations? In a multiplattform environment this is always difficult; you do not even have the same API to the graphic HW on the same system when using another OS. But sure this is the direction for the future. Kind regards Regina - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org Sincerely, Armin -- ALG - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Draw, make some changes to gradients
Hello, >>But I'd like also to set the >>transparency of each gradient color. >Transparency it a forth channel besides RGB. There exist nothing like a >"transparency of a color". Each value of a pixel consists of four parts: >Red, Green, Blue and transparency, each in the range of 0 to 255. >I do not really understand, which result you want to get tried to make an image in Inkscape ;) to make it a little bit clearer. http://i40.tinypic.com/358dtly.png On 04.06.2013 at 5:14 PM, "Regina Henschel" wrote:Hi, bugreporte...@hushmail.com schrieb: > Many thanks for the answer Regina, > > (thought I would be dopped to the spam folder ;) ) > >>Coding is not the only way to make AOO better. For example there are >>always people needed to test the product, whether the new features work >>as intended and whether no regressions slipped in. Also usability is a >>topic for non coder, and usability is not about a single design opinion, >>but making tests like the icon test in LO. > > actually I do report bugs, when I find some (in most cases svg stuff atm) > >>Currently the gradient is relative to the shape. Adjustments are done >>with the Border property. With svg it is possible to define the gradient >>relative to the parent of the shape and that is rendered correctly in AOO. > > Looking at LO4.0.4 and AOO3.4.1 the gradients are not rendered correctly. > for example: > on AOO3.4.1 (can't tell about newer versions) Please do not test with AOO 3.4.1. Rendering svg and rendering gradients have been reworked. Please use a current snapshot of AOO4.0 [..] >>Transparency is an additional feature. You can already combine >>transparency with solid color (I guess from the pdf-file, that you want >>that), but you can also combine transparency with gradients. You need >>not even use the same kind of gradient. It seems you have not yet >>discovered the property 'Gradient' in the Transparency tab of the Area >>dialog. > > Yes, but if you look at the attachement > (https://www.libreoffice.org/bugzilla/attachment.cgi?id=79272) of the > bugreport I mentioned, it does not makde that much sense (imo) to use > the percentage for the blackness. The transparency tab would just change > the WHOLE gradient transparency. The transparency itself can be defined as gradient. But I'd like also to set the > transparency of each gradient color. Transparency it a forth channel besides RGB. There exist nothing like a "transparency of a color". Each value of a pixel consists of four parts: Red, Green, Blue and transparency, each in the range of 0 to 255. I do not really understand, which result you want to get. Your attachment shows some changes in UI, but do not explain, what the resulting gradient should look like. Kind regards Regina
Re: Draw, make some changes to gradients
Forwarding Armin's and Regina's answers, below, to the original poster. bugreporter99: please follow http://mail-archives.apache.org/mod_mbox/openoffice-dev/ to read answers (or subscribe to this list, same link). Andrea Regina Henschel wrote: Hi Armin, Armin Le Grand schrieb: Hi Regina and bugreporter99, a very interesting topic... @bugreporter99: Which tasks did you commit for SVG? I did the SVG import, so these should got to AOO probably, did they...? Using multiple color steps in old gradients: A good idea, I already thought about it. Problem is (as often) that we would need a ODF change for it. Regina, could you think about something like that, please? AOO has not yet implemented the and (ODF 1.2 section 16.40.2 and 16.40.3). They allow multiple stop-colors. The schema has So in this gradient variant, it is already possible to use multiple color steps (and some other nice stuff). Therefore I think, that in a first step this should be implemented. We have start and end colors, in-between colors would have to be some value pair of float [0..1] and color value... The element svg:stop has the attributes svg:offset, svg:stop-color, and svg:stop-opacity. The offset is double (actual from 0..1) or percent, stop-color is #rrggbb, and opacity is double (from 0..1). All is already in the standard. Transparency: I thought myself about this; the current 100-0% setting to blent the start/end color against black is really not very useful; it's just handy to not change the color yourself. If adding an alpha value to each color definition, these value entries in the UI could be reused. I would guess users who know more modern apps think these values are exactly that, sigh. Also needs a ODF change, though. It is possible already using stop-opacity. I don't think, that we should go the way to try to get additional attributes/subelements into draw:gradient, but implement the two svg-gradients. BoundRects of old gradients: This is old stuff some people thought about 16-20 years ago and of course not state of the art; it was a handy way to draw these gradients at all (think 640kb systems) and got into ODF later, sigh, but cannot be changed SVG gradients: We already have these in the ODF spec, thus it will be better to go forward and offer these for the current draw objects directly., I think. Regina, what about ODF here and that it only allows one of the SVG mapping modes, I think both should be possible. Currently only objectBoundingBox is allowed. I think, that AOO should have it implemented in a way, that both svg:gradientUnits methods are possible. If an application supports a feature, it is easier to get it into ODF. It can be done by using a gradientUnits in an own namespace and later on, when it is in the ODF, map it to the official one on reading. For such a namespace, discussion with Thorsten would be useful. With all this, do not forget: More transparency makes all stuff more fancy, BUT also makes printing more expensive (preparation, handling) and also PDF export, especially PDF1/A stuff that does not allow transparencies at all... But that is needed already for proper rendering of svg graphics. So hopefully many parts can be reused. I'm not the right person to do it, but shouldn't be the way to use modern graphic cards for the calculations? Kind regards Regina - 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: Draw, make some changes to gradients
Hi Armin, Armin Le Grand schrieb: Hi Regina and bugreporter99, a very interesting topic... @bugreporter99: Which tasks did you commit for SVG? I did the SVG import, so these should got to AOO probably, did they...? Using multiple color steps in old gradients: A good idea, I already thought about it. Problem is (as often) that we would need a ODF change for it. Regina, could you think about something like that, please? AOO has not yet implemented the and (ODF 1.2 section 16.40.2 and 16.40.3). They allow multiple stop-colors. The schema has So in this gradient variant, it is already possible to use multiple color steps (and some other nice stuff). Therefore I think, that in a first step this should be implemented. We have start and end colors, in-between colors would have to be some value pair of float [0..1] and color value... The element svg:stop has the attributes svg:offset, svg:stop-color, and svg:stop-opacity. The offset is double (actual from 0..1) or percent, stop-color is #rrggbb, and opacity is double (from 0..1). All is already in the standard. Transparency: I thought myself about this; the current 100-0% setting to blent the start/end color against black is really not very useful; it's just handy to not change the color yourself. If adding an alpha value to each color definition, these value entries in the UI could be reused. I would guess users who know more modern apps think these values are exactly that, sigh. Also needs a ODF change, though. It is possible already using stop-opacity. I don't think, that we should go the way to try to get additional attributes/subelements into draw:gradient, but implement the two svg-gradients. BoundRects of old gradients: This is old stuff some people thought about 16-20 years ago and of course not state of the art; it was a handy way to draw these gradients at all (think 640kb systems) and got into ODF later, sigh, but cannot be changed SVG gradients: We already have these in the ODF spec, thus it will be better to go forward and offer these for the current draw objects directly., I think. Regina, what about ODF here and that it only allows one of the SVG mapping modes, I think both should be possible. Currently only objectBoundingBox is allowed. I think, that AOO should have it implemented in a way, that both svg:gradientUnits methods are possible. If an application supports a feature, it is easier to get it into ODF. It can be done by using a gradientUnits in an own namespace and later on, when it is in the ODF, map it to the official one on reading. For such a namespace, discussion with Thorsten would be useful. With all this, do not forget: More transparency makes all stuff more fancy, BUT also makes printing more expensive (preparation, handling) and also PDF export, especially PDF1/A stuff that does not allow transparencies at all... But that is needed already for proper rendering of svg graphics. So hopefully many parts can be reused. I'm not the right person to do it, but shouldn't be the way to use modern graphic cards for the calculations? Kind regards Regina - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Draw, make some changes to gradients
Hi Regina and bugreporter99, a very interesting topic... @bugreporter99: Which tasks did you commit for SVG? I did the SVG import, so these should got to AOO probably, did they...? Using multiple color steps in old gradients: A good idea, I already thought about it. Problem is (as often) that we would need a ODF change for it. Regina, could you think about something like that, please? We have start and end colors, in-between colors would have to be some value pair of float [0..1] and color value... Transparency: I thought myself about this; the current 100-0% setting to blent the start/end color against black is really not very useful; it's just handy to not change the color yourself. If adding an alpha value to each color definition, these value entries in the UI could be reused. I would guess users who know more modern apps think these values are exactly that, sigh. Also needs a ODF change, though. BoundRects of old gradients: This is old stuff some people thought about 16-20 years ago and of course not state of the art; it was a handy way to draw these gradients at all (think 640kb systems) and got into ODF later, sigh, but cannot be changed SVG gradients: We already have these in the ODF spec, thus it will be better to go forward and offer these for the current draw objects directly., I think. Regina, what about ODF here and that it only allows one of the SVG mapping modes, I think both should be possible. With all this, do not forget: More transparency makes all stuff more fancy, BUT also makes printing more expensive (preparation, handling) and also PDF export, especially PDF1/A stuff that does not allow transparencies at all... Just my 2 cents... On 04.06.2013 17:14, Regina Henschel wrote: Hi, bugreporte...@hushmail.com schrieb: Many thanks for the answer Regina, (thought I would be dopped to the spam folder ;) ) Coding is not the only way to make AOO better. For example there are always people needed to test the product, whether the new features work as intended and whether no regressions slipped in. Also usability is a topic for non coder, and usability is not about a single design opinion, but making tests like the icon test in LO. actually I do report bugs, when I find some (in most cases svg stuff atm) Currently the gradient is relative to the shape. Adjustments are done with the Border property. With svg it is possible to define the gradient relative to the parent of the shape and that is rendered correctly in AOO. Looking at LO4.0.4 and AOO3.4.1 the gradients are not rendered correctly. for example: on AOO3.4.1 (can't tell about newer versions) Please do not test with AOO 3.4.1. Rendering svg and rendering gradients have been reworked. Please use a current snapshot of AOO4.0 [..] Transparency is an additional feature. You can already combine transparency with solid color (I guess from the pdf-file, that you want that), but you can also combine transparency with gradients. You need not even use the same kind of gradient. It seems you have not yet discovered the property 'Gradient' in the Transparency tab of the Area dialog. Yes, but if you look at the attachement (https://www.libreoffice.org/bugzilla/attachment.cgi?id=79272) of the bugreport I mentioned, it does not makde that much sense (imo) to use the percentage for the blackness. The transparency tab would just change the WHOLE gradient transparency. The transparency itself can be defined as gradient. But I'd like also to set the transparency of each gradient color. Transparency it a forth channel besides RGB. There exist nothing like a "transparency of a color". Each value of a pixel consists of four parts: Red, Green, Blue and transparency, each in the range of 0 to 255. I do not really understand, which result you want to get. Your attachment shows some changes in UI, but do not explain, what the resulting gradient should look like. Kind regards Regina - 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: Draw, make some changes to gradients
Hi, bugreporte...@hushmail.com schrieb: Many thanks for the answer Regina, (thought I would be dopped to the spam folder ;) ) Coding is not the only way to make AOO better. For example there are always people needed to test the product, whether the new features work as intended and whether no regressions slipped in. Also usability is a topic for non coder, and usability is not about a single design opinion, but making tests like the icon test in LO. actually I do report bugs, when I find some (in most cases svg stuff atm) Currently the gradient is relative to the shape. Adjustments are done with the Border property. With svg it is possible to define the gradient relative to the parent of the shape and that is rendered correctly in AOO. Looking at LO4.0.4 and AOO3.4.1 the gradients are not rendered correctly. for example: on AOO3.4.1 (can't tell about newer versions) Please do not test with AOO 3.4.1. Rendering svg and rendering gradients have been reworked. Please use a current snapshot of AOO4.0 [..] Transparency is an additional feature. You can already combine transparency with solid color (I guess from the pdf-file, that you want that), but you can also combine transparency with gradients. You need not even use the same kind of gradient. It seems you have not yet discovered the property 'Gradient' in the Transparency tab of the Area dialog. Yes, but if you look at the attachement (https://www.libreoffice.org/bugzilla/attachment.cgi?id=79272) of the bugreport I mentioned, it does not makde that much sense (imo) to use the percentage for the blackness. The transparency tab would just change the WHOLE gradient transparency. The transparency itself can be defined as gradient. But I'd like also to set the transparency of each gradient color. Transparency it a forth channel besides RGB. There exist nothing like a "transparency of a color". Each value of a pixel consists of four parts: Red, Green, Blue and transparency, each in the range of 0 to 255. I do not really understand, which result you want to get. Your attachment shows some changes in UI, but do not explain, what the resulting gradient should look like. Kind regards Regina - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Re: Draw, make some changes to gradients
Many thanks for the answer Regina, (thought I would be dopped to the spam folder ;) ) >Coding is not the only way to make AOO better. For example there are >always people needed to test the product, whether the new features work >as intended and whether no regressions slipped in. Also usability is a >topic for non coder, and usability is not about a single design opinion, >but making tests like the icon test in LO. actually I do report bugs, when I find some (in most cases svg stuff atm) >Currently the gradient is relative to the shape. Adjustments are done >with the Border property. With svg it is possible to define the gradient >relative to the parent of the shape and that is rendered correctly in AOO. Looking at LO4.0.4 and AOO3.4.1 the gradients are not rendered correctly. for example: on AOO3.4.1 (can't tell about newer versions) # the ellipsoid gradient (having more than 2 colors) is rendered wrongly #also the hight of the ellipsoid gradient is rendered wrongly (cause there is not option atm to set the hight/width of the gradient) on LO4.0.4 #the same but seems like the issue with ellipsoid gradients with more than 2 colors is maybe fixed in 4.1beta >Transparency is an additional feature. You can already combine >transparency with solid color (I guess from the pdf-file, that you want >that), but you can also combine transparency with gradients. You need >not even use the same kind of gradient. It seems you have not yet >discovered the property 'Gradient' in the Transparency tab of the Area >dialog. Yes, but if you look at the attachement (https://www.libreoffice.org/bugzilla/attachment.cgi?id=79272) of the bugreport I mentioned, it does not makde that much sense (imo) to use the percentage for the blackness. The transparency tab would just change the WHOLE gradient transparency. But I'd like also to set the transparency of each gradient color. >We tend to make the draw stuff more like svg. Already now it is possible >to use a svg-graphic; and its gradients are rendered nicely. +2 >Area > Gradient is already the dialog page to edit gradients. What >editing feature do you miss on that page? But keep in mind, that color >gradient and transparency are independent properties. as described above that maybe should be changed a little (allowoing also to change the transparency of each gradient color) >Besides that, changes have to be compatible with ODF or find its way in >the next version of ODF. ODF needs to update faster so it can support the important/widely used things of svg ;) As you may noticed I'm a spoiled Inkscape user who just wants to import some svg drawing into AOO/LO (at least some basic svg drawings no animation or such things) :) Kind regards bugreporter99. On 03.06.2013 at 6:35 PM, "Regina Henschel" wrote:Hi ???, bugreporte...@hushmail.com schrieb: > Dear Apache Open Office/Libre Office devs, > the reason why I'm writing is, cause I can't code and want to make OO > better. Coding is not the only way to make AOO better. For example there are always people needed to test the product, whether the new features work as intended and whether no regressions slipped in. Also usability is a topic for non coder, and usability is not about a single design opinion, but making tests like the icon test in LO. > Specially the way gradients in Draw works. At the moment the gradients > stuff is rudimentary. > Well I guess little kids may have fun with this but you can't do real > work with that. > So this HAS to be changed. > At least the following things should be added: > - possibility to use more than two colors for the gradient +1 > - set the hight and width of the gradient Currently the gradient is relative to the shape. Adjustments are done with the Border property. With svg it is possible to define the gradient relative to the parent of the shape and that is rendered correctly in AOO. > - the percentage of the color should change the transparency and not > the "blackness" of the color >https://www.libreoffice.org/bugzilla/show_bug.cgi?id=64469 -1 Transparency is an additional feature. You can already combine transparency with solid color (I guess from the pdf-file, that you want that), but you can also combine transparency with gradients. You need not even use the same kind of gradient. It seems you have not yet discovered the property 'Gradient' in the Transparency tab of the Area dialog. > Because this will break compatibillity with older Versions of OO I > think there should be as much changes as > possible to prevent having to do big changes in the future to the > gradients stuff. > So here is my suggestion to the GUI part (pdf file: > http://temp-share.com/show/f3Ygit6Xn). > The coding part is up to you cause that's out of my
Re: Draw, make some changes to gradients
Hi ???, bugreporte...@hushmail.com schrieb: Dear Apache Open Office/Libre Office devs, the reason why I'm writing is, cause I can't code and want to make OO better. Coding is not the only way to make AOO better. For example there are always people needed to test the product, whether the new features work as intended and whether no regressions slipped in. Also usability is a topic for non coder, and usability is not about a single design opinion, but making tests like the icon test in LO. Specially the way gradients in Draw works. At the moment the gradients stuff is rudimentary. Well I guess little kids may have fun with this but you can't do real work with that. So this HAS to be changed. At least the following things should be added: - possibility to use more than two colors for the gradient +1 - set the hight and width of the gradient Currently the gradient is relative to the shape. Adjustments are done with the Border property. With svg it is possible to define the gradient relative to the parent of the shape and that is rendered correctly in AOO. - the percentage of the color should change the transparency and not the "blackness" of the color https://www.libreoffice.org/bugzilla/show_bug.cgi?id=64469 -1 Transparency is an additional feature. You can already combine transparency with solid color (I guess from the pdf-file, that you want that), but you can also combine transparency with gradients. You need not even use the same kind of gradient. It seems you have not yet discovered the property 'Gradient' in the Transparency tab of the Area dialog. Because this will break compatibillity with older Versions of OO I think there should be as much changes as possible to prevent having to do big changes in the future to the gradients stuff. So here is my suggestion to the GUI part (pdf file: http://temp-share.com/show/f3Ygit6Xn). The coding part is up to you cause that's out of my scope. We tend to make the draw stuff more like svg. Already now it is possible to use a svg-graphic; and its gradients are rendered nicely. Besides that, changes have to be compatible with ODF or find its way in the next version of ODF. I would like you guys to think about how this could be implemented and if there is a better way to do it on the GUI side (maybe an extra button which will pop-up an extra window for the editing of the gradient???). Area > Gradient is already the dialog page to edit gradients. What editing feature do you miss on that page? But keep in mind, that color gradient and transparency are independent properties. Please fuck the licensing issues so the code can be used in both projects. If a developer provides his work under AL2, it can be used in both projects. So its up to the individual developer. Changes done in AOO can always be used in LO. Kind regards Regina - To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org For additional commands, e-mail: dev-h...@openoffice.apache.org
Draw, make some changes to gradients
Dear Apache Open Office/Libre Office devs, the reason why I'm writing is, cause I can't code and want to make OO better. Specially the way gradients in Draw works. At the moment the gradients stuff is rudimentary. Well I guess little kids may have fun with this but you can't do real work with that. So this HAS to be changed. At least the following things should be added: - possibility to use more than two colors for the gradient - set the hight and width of the gradient - the percentage of the color should change the transparency and not the "blackness" of the color https://www.libreoffice.org/bugzilla/show_bug.cgi?id=64469 Because this will break compatibillity with older Versions of OO I think there should be as much changes as possible to prevent having to do big changes in the future to the gradients stuff. So here is my suggestion to the GUI part (pdf file: http://temp-share.com/show/f3Ygit6Xn). The coding part is up to you cause that's out of my scope. I would like you guys to think about how this could be implemented and if there is a better way to do it on the GUI side (maybe an extra button which will pop-up an extra window for the editing of the gradient???). Please fuck the licensing issues so the code can be used in both projects.
Re: FormatArea Draw
Hello, http://opengrok.adfinis-sygroup.org/source/xref/aoo-trunk/main/sd/uiconfig/sdraw/toolbar/drawingobjectbar.xml where is the code that converts these xml into toolbars? - --- http://opengrok.adfinis-sygroup.org/source/xref/aoo-trunk/main/officecfg/registry/data/org/openoffice/Office/UI/GenericCommands.xcu#2504 Area... 1 where is the code that bound these 1 into toolbars with an icon? Or what files work on this xml file and xcu file? Regards. 2013/4/14 Ariel Constenla-Haile > On Sat, Apr 13, 2013 at 01:35:55PM -0500, jorge ivan poot diaz wrote: > > Hello Ariel, > > > may be you can simply > > > append a number when the name is already used, given "Blue 9": "Blue > > > 10", then if "Blue 11" is already used, increase it and try with "Blue > > > 12" and so on. > > > > Ok. I like this idea. How I can generate this number? > > I leave this for you, as homework; it is simply an algorithm, nothing > specific to OO API nor C++, you could even find the algorithm using > python. > > What I'm not sure is how generic this can be: will a RTL > language use the "Color N" pattern, or "N Color"? And some locales may > not use the Western-Arabic numerals used with the Latin script, > wikipedia shows http://en.wikipedia.org/wiki/Eastern_Arabic_numerals and > http://en.wikipedia.org/wiki/Indian_numerals > > > Regards > -- > Ariel Constenla-Haile > La Plata, Argentina >
Re: FormatArea Draw
On Sat, Apr 13, 2013 at 01:35:55PM -0500, jorge ivan poot diaz wrote: > Hello Ariel, > > may be you can simply > > append a number when the name is already used, given "Blue 9": "Blue > > 10", then if "Blue 11" is already used, increase it and try with "Blue > > 12" and so on. > > Ok. I like this idea. How I can generate this number? I leave this for you, as homework; it is simply an algorithm, nothing specific to OO API nor C++, you could even find the algorithm using python. What I'm not sure is how generic this can be: will a RTL language use the "Color N" pattern, or "N Color"? And some locales may not use the Western-Arabic numerals used with the Latin script, wikipedia shows http://en.wikipedia.org/wiki/Eastern_Arabic_numerals and http://en.wikipedia.org/wiki/Indian_numerals Regards -- Ariel Constenla-Haile La Plata, Argentina pgp0j2qFANVW0.pgp Description: PGP signature