Features discussion

[rubiin]

Make readme more user friendly. May include an optional video tour guide on install.
Also add sections on how to update to latest hyprdots

[kRHYME7]

Soon will change the goal of this project. At first, it only acts as helper and workarounds, but I guess we should consider turning this project as a wrapper for Hyde.

[rubiin]

I think we should make the cli as preferred option for installing dots in the readme . And the git clone as manual

[kRHYME7]

tl;tr

Not yet, for now. As the CLI is dependent on some install scripts from Hyde.
I am now considering an independent one in case we can't follow the breaking changes upstream.

Expect a markdown for these soon in README.

Hyde-install
Done:

• shell selection
• patching themes
• Sddm theme selectiom
• Restoring configs

not yet:

• nvidia handling ( will steal it from upstream or I'm considering forking the endeavorOS nvidia-inst pkg )
  Can you check if it's legal? I already tested it on my local and it works. I'm hesitant because no one ported this packaeg to AUR. (nvidia-inst AUR is ready too, in my local machine 😄)
• GRUB, (will copy upstream lol)

What's on my plate:

• Hyde-TUI templating (for declarative formats for devs - just bash lol )
• Package installation

1. Everything works now my only issue is I really want to store the package array inside a variable not a file so that it will be faster than writing multiple files. (Just my ego and proof of concept)
2. We can write it all in memory, drawbacks are We should execute everything in a single shell , or do some exports.

Will try 2 this week if it's too much then will use the first method.

I made a fast sketch:

NOTE
consider --[flags] to be invoked manually and consciously, this gives freedom without breaking the defaults for unconscious inputs.

[rubiin]

Also, I think we should rename the cli from "Hyde" to "hyde" , most clis have small case naming patterns

[rubiin]

Also another thing, the make version of the install requires you to sudo. Is it okay?

[kRHYME7]

Yes it requires sudo so that it will be available systemwide.

[kRHYME7]

about the Command being Uppercase, It's for clarity and being conscious of what the user types in the Terminal.

is it really necessary to make it lowercases?

[rubiin]

nah not necessary but a typical linux person would definitely type hyde after installing as the aur name is also hyde-cli-git .

[kRHYME7]

Will leave it like that for now.

My convention for this is like

1st: Main Command
2nd: Actual function
3rd: [args/params]

For me this is too long, so I decided to make the first command stand out, indicating that this is the main Shell. Something like that. Will definitely make it lowercase if 2 or more requested it. ( inspired byt the Compositor command Hyprland )

[rubiin]

that makes sense. lets get on with the remaining milestones . I could help out on my free time with some issues

[kRHYME7]

I'm just annoyed with the Hyde.usage haha.
I'm thinking of breaking it down to single file for each funtions. eg upgrade restore etc
then will make a script to merge them later on, plus compile with complgen. It is not a perfect solution,
But will make it easier for me and other contributors to find the function via file, then add its related function.

Another thing can we use endeavorOS nvidia-inst?
https://github.com/endeavouros-team/PKGBUILDS/blob/master/nvidia-inst/nvidia-inst

[kRHYME7]

@rubiin Hello! the Hyde.usage now is auto generated

[rubiin]

@kRHYME7 cool. Will try out. It was a pain to maintain the usage file as we are adding so many things .

[kRHYME7]

This is exclusive for --dev (contributors)

so Hyde --dev select the gen completion then it will output the Hyde.usgae in the terminal (stdou).

or just using ./complgen.sh

[rubiin]

I was thinking of adding jp2a dependency when installing from aur for seamless experience

[kRHYME7]

This is used to render images in ascii right?

[rubiin]

yup. Having it will dependency will make the CLI workable straightforward

[rubiin]

I was thinking of adding jp2a dependency when installing from aur for seamless experience

@kRHYME7 is this there? Or should I make a pr.

[kRHYME7]

This will opt to install when running anything that renders images and not using kitty

[rubiin]

closing this as it looks covered

[rubiin]

@kRHYME7 you can take code plus inspirations for features from here https://github.com/JaKooLit/Hyprland-Dots that will make hyde a lil better

[rubiin]

@kRHYME7 how about a powersaver mode?
Like powersaver on would quicky turn off all these

[-a] [--animations] Default animations
[-ba] [--borderangle] Default border angle animation
[-b] [--blur] Default blur
[-o] [--opacity] Default tranparency

and again on toggle would enable them.

The current toggle option doesnt do anything :(

[kRHYME7]

Yes that would be helpful! But take note this is NOT set using hyprctl keywords so it will be a persistent mode across reboots.

[rubiin]

yeah lets make toggle act as what the name would suggest. I dont know what toggle does now atm

also can you merge the PR so we might release the 0.60

[kRHYME7]

yeah lets make toggle act as what the name would suggest. I dont know what toggle does now atm

Toggle will unset/set everything being declared set.

So when you run Hyde power save --[multiple_params] you could unset it using "toggle". Then you can set it back to set it again. I will be adding Hyde power save --all ` to set into power save all the [params]

[rubiin]

yeah lets make toggle act as what the name would suggest. I dont know what toggle does now atm

Toggle will unset/set everything being declared set.

So when you run Hyde power save --[multiple_params] you could unset it using "toggle". Then you can set it back to set it again. I will be adding Hyde power save --all ` to set into power save all the [params]

what will be the counterpart for save --all . If save --all would allow to restore the chnages prior to the command, then maybe I could add a waybar module with a button to turn on and off powersaver mode for convinience

[kRHYME7]

Is Hyde power save off good?

The toggle command actually just add/remove the sourced file of the Hyde power options so it would still be good Idea to have explicit on/off, in which will be handles by save on and save off

But to maintain the initial convention I will still add

Hyde power save --all is same with Hyde power save on
Hyde power unset --all same as Hyde power save off

This way we can toggle them one by one and in bulk.

[kRHYME7]

[rubiin]

yeah save on and save off sounds good. I will try to implement a waybar module too

[kRHYME7]

How I wish we could come up with a good plugin system for HyDE. It is easy to input files but managing it across updates and removing it is an extra work.

This plugin system should be the backbone of the installer and anything HyDE extra stuff.

[rubiin]

@kRHYME7 how about a command called Hyde theme generate that will generate bare bones themes according to Hyde sepcs. Would allow making themes easier.

Can you setup a sample theme repo? I would work on this

[kRHYME7]

Something Hyde theme export --ouput_dir /path/to/theme_dir/? Which will repack current theme into a target directory.

generate bare bones themes according to Hyde sepcs. Would allow making themes easier.

Or this is a different thing?

[rubiin]

Nah . This is more like a skeleton theme. Hyde theme init would just clone one of the themes branch from
https://github.com/prasanthrangan/hyde-themes and rename cloned folder as new-theme. Then the user can go to this dir and modify the colors, icons etc

[rubiin]

Additionally we can also add instructions after the init from this discussions for further steps

prasanthrangan/hyprdots#653

[kRHYME7]

Aha yes! This is actually a TODO after hyde makes a default theme (using that as base theme), but at this state the repo is stale.

Also, I noticed that different themes can have different approach, would it be nice that the init command will just copy the current theme and will ask for the new theme name afterward and creates it?

Additionally we can also add instructions after the init from this discussions for further steps

And this part should be in a wiki 😬

[rubiin]

Yeah> lets add it to future plans then

[rubiin]

@kRHYME7 https://github.com/kRHYME7/Hyde-cli/blob/42a9b599dab16175f8734faafeac380f47f88562/Scripts/Launch-Calculator#L3C16-L3C20 the qalc package name is incorrect. correct package is https://archlinux.org/packages/extra/x86_64/libqalculate/

[kRHYME7]

did it cause errors?

Can you open a PR please. I'm on bed rn.

[rubiin]

yes i can. Yeah when launching

[rubiin]

@kRHYME7 How does a user get the latest hyprdots changes and apply it to their system ?
Hyde update followed by Hyde upgrade ?

[kRHYME7]

Hyde update then Hyde restore Config Users needs to resolve the files/dirs.

Only use Hyde upgrade if you want to get all changes possible, like new packages etc.

For my use case I only use Hyde update then Hyde restore Config

[rubiin]

Confused on Hyde upgrade. What does it do. We should include on readme how users can remain in sync with the main repo

[rubiin]

Can do a PR shortly for this

[kRHYME7]

Yes please.

upgrade is use to upgrade everything like rerunning the Hyde-install

restore is used to restore the dotfiles that are declared in the ./restore_cfg.lst

[kRHYME7]

@rubiin Hi!, can you Dm me on Discord. hehe I got some proposal. Thank you!

[rubiin]

@rubiin Hi!, can you Dm me on Discord. hehe I got some proposal. Thank you!

sure thing, heres my username rubiin._ @kRHYME7

[rubiin]

@kRHYME7

heres the high quality image
Update the images

[rubiin]

Maybe we can also add an animation style changer on rofi seems, doable. If rofi supports a gif display that is. Will be a cool addition.

[kRHYME7]

Can rofi display gifs?

[rubiin]

maybe. But we do not need to display gif. Simply put on readme the what the gifs look like in actual