Update plugins and dubuild markdown files

[advice2020]

Not sure if it would be helpful to you guys but I was just wondering, if it would be okay with you if I was to help out and make some info/cosmetic updates to the following files?
plugins.md and dubuild.md

I can also start to help make some GTK3 updates for the items that I am familiar with, if that is okay as well? I can probably get a general structure for GTK3 stuff and maybe you guys can fill in whatever I cannot in the future?
I might be able to at least save you guys some time/effort from having to update these files?

I would rather not get into making actual Git edits at the moment, but I could just paste the md text into a Github post and then you could just compare by content, my files to the originals to approve if you agree with the changes I have made or not.

Let me know if this would be helpful and I can maybe start working on it, or if not interested.

Thank you

[advice2020]

If you are interested, I just had two quick questions
1.)
Would you be alright with me changing
Qt to QT
just to make it stand out more / match the GTK2 and GTK3 text.
QT5:
QT6:

GTK2:
GTK3:

2.)
Would you want me to create an entirely new WLX section for GTK3 or would you want me to combine like QT5/QT6 do?
For example in the dubuild.md file
GTK2:
GTK3:

[j2969719]

#69

nice

if you have the time and inclination, be my guest. consistency is good; its worth making a separate section, as some plugins are gtk2-only and use ancient dependencies

[Skif-off]

@advice2020

Would you be alright with me changing Qt to QT
just to make it stand out more / match the GTK2 and GTK3 text.

I don't think it's a good idea to change the original name to a "more convenient" one :)

Would you want me to create an entirely new WLX section for GTK3 or would you want me to combine like QT5/QT6 do?

Some plugins have separate versions, some plugins are built from the same source code. So, GTK2/GTK3 (like Qt5/Qt6) looks more logical.

---

dubuild.md was created by one plugin at a time. Reading the build file > searching for packages > installing found packages > compilation attempt; if it fails, then read error(s) in terminal output, view source code... For each plugin :)) Sometimes need to check the dependency versions and changelogs of packages and dependencies. Also some packages in Ubuntu 20.04, 22.04 and 24.04 change their names and contents.
Also it was a minimalist environment (sbuild), not an usual system: this allows to create a list of packages without fear that some packages are already installed in the system. Well, three systems - 20.04, 22.04, 24.04.

It seems that the current list will be easier to fix and supplement, but I don't know how to do it beautifully :(

[advice2020]

I was excited to see that I might be able to help.... then I read what Skif-off said and realized that maybe this is more complex then I understood this to be?

I thought these md files were just text files used to describe the plugins use (plugins.md) and the other to show users the dependencies required to compile (dubuild.md) that could just be edited?

As I had mentioned, I probably would not be able to update every single item, but was going to try to provide the overall structure that was already their for the new GTK3 stuff and leave temporary place holders that could be updated as we all are testing these new plugins out and figuring out which dependencies (new names) are required.

Yeah I was planning on just modifying ("fix and supplement") the current lists, I was not going to make completely new ones.

---

FROM MY FIRST QUESTION
1.)
This was regarding the dubuild.md file
For example:
fontview_qt shows
Qt5: apt install build-essential pkg-config qtbase5-dev
Qt6: apt install build-essential pkg-config qt6-base-dev libgl-dev

was going to change this to
QT5: apt install build-essential pkg-config qtbase5-dev
QT6: apt install build-essential pkg-config qt6-base-dev libgl-dev

GTK2: apt install build-essential pkg-config
GTK3: apt install build-essential pkg-config

make the toolkit names standout a little more visually compared to lowercase cmds?
I shouldn't this?

---

FROM MY SECOND QUESTION
2.)
This was regarding the dubuild.md file as well.
Yeah this one was tricky which is why I asked.
With certain items, yes it is would be nicer if could be combined to match how QT versions are combined in one section, yet for items like gtk_socket and some others, could be confusing if all dependencies were together, due to quantity of them. I would have to type things out and see how clean I can get it to look.

---

3.)
Dependency Naming
I had actually thought of this question the right after I made my original post regarding how to actually display the dependency names between Arch and Debian, I was not even thinking of Ubuntu (and its three version) as Skif has mentioned.
How do you guys want to handle this?
Might have to just choose one distributions naming convention so at least all the names would be consistent to one of them.
Not sure who has the best naming convention?
Let me know how you guys would want to handle this?

Luckily most of the most common dependency names appear to use the same naming convention. For example
build-essential pkg-config

---

But again I would mainly provide the same structure and maybe just leave some kind of symbol/string of characters as a placeholder that could be updated as we all test things out?
But if these md files are actually used for something that I am unaware of then I might not be the best person to modfiy them.

So I guess let me know

Thank You

[Skif-off]

maybe this is more complex then I understood this to be?

If anyone can make the lists more user-friendly, then it would be strange to somehow prevent them from doing so ;)

I thought these md files were just text files used to describe the plugins use (plugins.md) and the other to show users the dependencies required to compile (dubuild.md) that could just be edited?

You are absolutely right, this was done for convenience.
I made dependency lists primarily for myself, but I decided that it might be useful (there are many new Linux users among Ubuntu and its derivatives), so I added details to the beginning and slightly adjusted the appearance.

1.) "Little more visually" is not appropriate in this case.

Toolkits have a specific name, let's open the official home sites:
gtk.org - GTK, not Gtk;
www.qt.io - Qt, not QT.

2.) I meant, for example, something like

- [abiword-gtk2](plugins/wlx/abiword-gtk2)<br>
`apt install dependencies`<br>
Requires AbiWord (GTK2 version).

- [abiword-gtk3](plugins/wlx/abiword-gtk3)<br>
`apt install dependencies`<br>
Requires AbiWord (GTK3 version).

- [gstplayer](plugins/wlx/gstplayer)<br>
GTK2: `apt install dependencies`<br>
GTK3: `apt install dependencies`

- [jsonview_gtk3](plugins/wlx/jsonview_gtk2)<br>
`apt install dependencies`

- [jsonview_gtk3](plugins/wlx/jsonview_gtk3)<br>
`apt install dependencies`

3.) For Arch Linux, @j2969719 adds package names, but Arch Linux users are usually slightly more experienced users... Also Packages in Arch Linux are not separated as in Debian and derivatives, for example, evince in Arch, but libevince-dev libgtk-3-dev in Debian/Ubuntu and so on.

Luckily most of the most common dependency names appear to use the same naming convention.

Of course, Ubuntu is a derivative of Debian, but with some rare exceptions.

[advice2020]

No I just wanted to make sure it was okay, it kind of sounded like maybe these files were linked to something more complex.
I am aware of Qt being the correct casing but just thought it could help this stand out a bit more with these files containing so much data/text.
Also, hopefully me mentioning that maybe I could clean some things up in these files was not insulting in any way. I think these two files are very helpful, I would not have been able to compile any plugins myself or even know what most of them are, if these files were not included.
It was more about the newly created GTK3 plugins that were being added that made me think of this.
I just thought while I was becoming familiar with some of these GTK3 plugins that maybe I could help with something like this. I figured maybe I could at least be able to provide similar structure for the GTK3 items in these files. You guys have helped me out so much, my setup would be pretty sad without all the tools/help you guys have provided, so I thought maybe I could save you guys some time with the tedious task of adding the GTK3 structure to these files, while also making any changes I thought might be beneficial?

Just to let you guys know I have created two posts in the Issues section (one for each md file) if you guys want to take a look.

Anyways, hope this helps in some way