Bug 125217 - Replace Mozilla themes with a custom tool
Summary: Replace Mozilla themes with a custom tool
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
unspecified
Hardware: All All
: medium enhancement
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
: 125448 137414 147954 (view as bug list)
Depends on:
Blocks: LibreOffice-Themes 131023 146181 154237
  Show dependency treegraph
 
Reported: 2019-05-11 19:24 UTC by Leandro Martín Drudi
Modified: 2024-03-18 19:46 UTC (History)
12 users (show)

See Also:
Crash report or crash signature:


Attachments
Exemplary simulation for the proposal (54.34 KB, image/png)
2019-05-11 19:24 UTC, Leandro Martín Drudi
Details
Illustration of bad persona image rendering (20.90 KB, image/png)
2019-05-16 13:47 UTC, Daveo
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Leandro Martín Drudi 2019-05-11 19:24:02 UTC
Description:
1) Use the current tools to create gradients, patterns, screening and create a file that can be used to replace Mozilla themes with the appropriate dimensions for screen resolution.
2) Include a simulation of how it will look when applying with some buttons with the current icon theme.

Steps to Reproduce:
1. Tools
2. Options
3. Personalize
4. Own theme

Actual Results:
Personas themes don't work

Expected Results:
The freedom of a user to create a theme for the customization of LibreOffice.


Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 Leandro Martín Drudi 2019-05-11 19:24:54 UTC
Created attachment 151312 [details]
Exemplary simulation for the proposal
Comment 2 Adolfo Jayme Barrientos 2019-05-15 04:37:42 UTC
Lovely mockup ❤
Comment 3 Heiko Tietze 2019-05-15 06:57:01 UTC
So the idea here is to switch from a predefined theme to a kind of theme editor. We would provide the area fill dialog with color, gradient, and bitmap and apply the result to the tool-/notebookbar (and ideally also the other UI controls). Sounds interesting.
Comment 4 Muhammet Kara 2019-05-15 07:56:15 UTC
Yep. Definitely interesting.

In fact, I was going to do something 'similar' a few months ago, but gave up because it didn't get support. :) (Search for "Please dont introduce a new dialog" in the Design channel on telegram for the context. I guess my mockup skills wasn't enough to convey the idea.)

Anyway, nice & well-thought mock-up IMO.
Comment 5 Heiko Tietze 2019-05-16 11:26:40 UTC
Muhammet, please provide some code pointers to make this an easyhack.
Comment 6 Daveo 2019-05-16 13:47:29 UTC Comment hidden (off-topic)
Comment 7 Buovjaga 2019-05-16 17:46:22 UTC Comment hidden (off-topic)
Comment 8 Heiko Tietze 2019-05-16 18:19:15 UTC Comment hidden (off-topic)
Comment 9 Daveo 2019-05-18 09:13:34 UTC Comment hidden (off-topic)
Comment 10 Daveo 2019-05-18 09:17:29 UTC Comment hidden (off-topic)
Comment 11 andreas_k 2019-05-23 11:15:53 UTC
*** Bug 125448 has been marked as a duplicate of this bug. ***
Comment 12 Muhammet Kara 2019-05-24 09:31:07 UTC
(In reply to Leandro Martín Drudi from comment #1)
> Created attachment 151312 [details]
> Exemplary simulation for the proposal

Thank you for the mockup. Is there an English version of it?
Comment 13 Heiko Tietze 2019-05-24 09:34:02 UTC
(In reply to Muhammet Kara from comment #12)
> (In reply to Leandro Martín Drudi from comment #1)
> > Created attachment 151312 [details]
> > Exemplary simulation for the proposal
> 
> Thank you for the mockup. Is there an English version of it?

Just take the area fill dialog as example (with a specialized preview ideally but not necessarily). The original idea is discussed here https://design.blog.documentfoundation.org/2015/12/22/area-fill-options-made-consistent/
Comment 14 Heiko Tietze 2020-02-02 11:50:24 UTC
Rania, you might be interested in this topic.
Comment 15 Rania Amina 2021-01-31 11:24:02 UTC
It look like what LOTC did, but i still not sure.
Comment 16 Heiko Tietze 2022-03-15 10:04:48 UTC
*** Bug 147954 has been marked as a duplicate of this bug. ***
Comment 17 V Stuart Foote 2022-10-12 14:27:10 UTC
*** Bug 137414 has been marked as a duplicate of this bug. ***
Comment 18 Eyal Rozenberg 2023-04-03 21:40:26 UTC
I don't understand what this bug is about:

1. LO is a FOSS project; why do we need proprietary tools?
2. What Mozilla themes? We use Mozilla themes? Perhaps you mean Mozilla-like theming?
3. "reuse the existing" - existing what? themes? dialog?
Comment 19 Leandro Martín Drudi 2023-04-04 03:04:37 UTC
(In reply to Eyal Rozenberg from comment #18)
> I don't understand what this bug is about:
> 
> 1. LO is a FOSS project; why do we need proprietary tools?
> 2. What Mozilla themes? We use Mozilla themes? Perhaps you mean Mozilla-like
> theming?
> 3. "reuse the existing" - existing what? themes? dialog?

Do you really think that your comment contributes something to the issue? A constructive opinion can be useful, but a comment where only by technicalities you reject something that has been perfectly clarified does not contribute anything and obstructs an effective communication.
The report has been here for years because it was proposed to use LibO tools to make themes to replace Mozilla Themes as they were used until a few years ago. If you want more information, read the previous posts and comment something constructive.
Comment 20 Jeff Fortin Tam 2024-03-05 15:22:33 UTC
I believe it would be wise to retitle this ticket to replace "proprietary" by "in-house" or "custom"; I can guess this is certainly the meaning that was intended by Leandro. Proprietary can either mean "not common" (especially for latin-based languages) or refer to proprietary _licensing_, but in the FLOSS world most people are not used to interpreting this term with the former meaning, and immediately think of the latter meaning.

Avoid this term if you don't want angry mobs coming at you over a misunderstanding.
Comment 21 Leandro Martín Drudi 2024-03-18 19:46:08 UTC
Honestly, I don't speak English. I just used Google to translate.
I will now take advantage of Artificial Intelligences to make the translated texts clearer.
But I believe that if it leads to misunderstandings, it should be changed. The intention refers to reusing what has already been created and "adapting" it to create themes.