[I miss you!] Binary Release When ?

[kRHYME7]

Hi @tittu! I miss you! By any chance do you have any plans to do a binary release soon?

[prasanthrangan]

Hey @kRHYME7 , long time no see... hope you are doing well!
I've to thank you first for maintaining the HyDE project :)

I've replaced swww with wallbash in my system and its working, but I'd like to clean up the code as its a bit messy now...
I'd also like to test it properly in different environments!
So lemme try to clean up and test a bit and release the binary in the next few weeks.

[valkyrieAttr]

I've replaced swww with wallbash in my system and its working, but I'd like to clean up the code as its a bit messy now...
I'd also like to test it properly in different environments!
So lemme try to clean up and test a bit and release the binary in the next few weeks.

After looking into the wiki, I fear the worst of editing thousands of QT SVG's that contains <wallbash_> placeholders. It will break the current implementation of my dotfile. Do we have fallback to use the angle-bracket <> or is it must to convert [[::Palette::]] from <wallbash_>? I hope backward compatibility is available.

[kRHYME7]

Hey @kRHYME7 , long time no see... hope you are doing well!
I've to thank you first for maintaining the HyDE project :)

Yeah as long as I am using it, that's the promise. Just want to tell you that I'm an Electronics Engineer now, finally!

Will definitely test it and track.

I hope you're doing well also.

[prasanthrangan]

I fear the worst of editing thousands of QT SVG's that contains <wallbash__> placeholders. It will break the current implementation of my dotfile._

Lets see how to support/convert the old placeholders <wallbash_> with the new ones [[::Palette::]], the main problem would be mapping the old colors to the new ones as the palette generated would be different.

I've created the template files for qt, rofi and waybar. I've not pushed these templates to any repo yet, so maybe we can create a repo to convert and maintain these templates - wallbash.zip

[prasanthrangan]

Yeah as long as I am using it, that's the promise. Just want to tell you that I'm an Electronics Engineer now, finally!

That's great news, I'm sure that you'll do great as an Electronics Engineer with your talent and skills!

Will definitely test it and track.

I hope you're doing well also.

Thank you very much brother, i'm doing great.
Just trying to learn some rust and vulkan, thought it would be simple at first, but never knew how deep it goes :)
What do you think about rebuilding HyDE using wallbash and quickshell?

[kRHYME7]

. Do we have fallback to use the angle-bracket <> or is it must to convert [[::Palette::]] from <wallbash_>? I hope backward compatibility is available.

It is better to make the rust port use a different template.

wallbash as bash won't go away anytime soon. But won't receive any feature.
For The HyDE Project the built in wallbash will act as fallback mechanism.
It is on the The HyDE Project to do the backward compatibility.

[kRHYME7]

What do you think about rebuilding HyDE using wallbash and quickshell?

Been trying to learn quickshell, It won't be a problem integrating to HyDE. I'm always rooting for quickshell on its early stage.

The HyDE Project repo now is kinda modular, I'm sorry it might not be your vision on how it should work, but I'm trying to lean on standards for extensibility.

This way users can add/remove other stuff. In exchange, HyDE can be anyone's and user's own dotfiles.

---

I suggest we build a separate GUI shell from quickshell+ wallbash instead. It would act as a client on top of what is HyDE. This way it might/can run on different compositor or environment. wdyt?

[prasanthrangan]

I suggest we build a separate GUI shell from quickshell+ wallbash instead. It would act as a client on top of what is HyDE. This way it might/can run on different compositor or environment. wdyt?

Yup, I have the exact same idea... a GUI shell from wallbash + quickshell so that users can run it on different compositor or environment.
So to do that we might need to port the basics to quickshell like -

• system bar (waybar)
• launcher (rofi)
• notification (dunst)
• settings (system + wayland + wallbash settings)

So please lemme know your thoughts and suggestions.

[kRHYME7]

Let me know if you will open a repo or want to host it under the Organization.

Suggestions partly on how it can be interfaced.

• Cli to control Quickshell as qs command is not enough.
• Settings app should have a single source of truth file, this way we can export and import them.
• Keep the minimal look, basic extensibility. Qs is powerful so power users can just extend it.
• plugin system

About the UX, I will respect whatever is your inspiration! I always admired your design choices.

[valkyrieAttr]

I fear the worst of editing thousands of QT SVG's that contains <wallbash__> placeholders. It will break the current implementation of my dotfile._

Lets see how to support/convert the old placeholders <wallbash_> with the new ones [[::Palette::]], the main problem would be mapping the old colors to the new ones as the palette generated would be different.

I've created the template files for qt, rofi and waybar. I've not pushed these templates to any repo yet, so maybe we can create a repo to convert and maintain these templates - wallbash.zip

It wouldn't be much of a hassle if we know what particular wallbash_pry$i or wallbash_$ixa$j aligns with the new palette. Although that is uncertain wheter they may match or not. I will have to update my
hyir.sh to accept the new placeholder [[::placeholder::]] sigils since it doesn't really have to do much job other than environment substitution, atomic writes, lock files, deferred execution, PRE/RUN hooks lifecycles, template inheritances, inline templates, buffer rendering and compatibility with bash functions.

At this point, this shell scripts needs to be rewritten in C++ or Rust. Also, thank you for the new wallbash templates.

[valkyrieAttr]

. Do we have fallback to use the angle-bracket <> or is it must to convert [[::Palette::]] from <wallbash_>? I hope backward compatibility is available.

It is better to make the rust port use a different template.

wallbash as bash won't go away anytime soon. But won't receive any feature. For The HyDE Project the built in wallbash will act as fallback mechanism. It is on the The HyDE Project to do the backward compatibility.

On my side, wallbash.sh acts as a color-palette orchestrator that generates dcol for each wallpapers (Although I replaced this engine with a Perl-script that natively uses ImageMagick library to create dcol colors.).

The heavy-duty work is done by hyir.sh, a meta-template script that does everything in one pass. The reason for asking backward compatibility with the angle bracket sigils is because HyDE-Themes are using <> angle brackets to specify that this is a placeholder. While [::placeholder::] is great and very fast to parse, I think we should add the backward compatibility with the angle bracket.

Side Note: SVG's contains angle brackets and my orchestrator finds it unbound variable that is not populated e.g., . Moving to [::placeholder::] is a great idea and adds O(1) speed (not fully) at runtime.

And it would be hassle for me to dig through each files to change the headers unless I built a separate shell-script to clone the specific HyDE themes and sanitize them via regex. (I really like the Themes except for CIA, FBI themes that were pushed into the repo)

I believe hyq or themepatcher.sh (if I recall correctly, this is a deprecated script) will sanitize the headers and initialize them to the paths?

[prasanthrangan]

Let me know if you will open a repo or want to host it under the Organization.

We can open it under HyDE organization.

I've not explored/used Quickshell yet, I'll give it at try and start with something minimal.
lemme know if you have any useful docs/wiki/repos for Quickshell.

[prasanthrangan]

It wouldn't be much of a hassle if we know what particular wallbash_pry$i or wallbash_$ixa$j

Let me try to create a map to replace the old <placeholders> with new [::placeholders::] that would help to create a fallback for a regex replace script.

The heavy-duty work is done by hyir.sh, a meta-template script that does everything in one pass. The reason for asking backward compatibility with the angle bracket sigils is because HyDE-Themes are using <> angle brackets to specify that this is a placeholder. While [::placeholder::] is great and very fast to parse, I think we should add the backward compatibility with the angle bracket.

For the HyDE-Themes , if we include the backward compatibility within wallbash then all templates have to be parsed twice (1st pass for <placeholders> and 2nd pass for [::placeholders::] ) on runtime.

So i think it would be better option to convert the theme template files from <placeholders> to [::placeholders::] using a script or AI (not sure how good the AI will be for this pattern replace). This will be one time conversion so that we don't have to parse it twice during runtime.