crosspost: https://lemmy.world/post/45022275

Hi

Hello, I created this project with the goal of quickly setting up a template using Nuxt and the “On-demand revalidation” configuration, integrated with a backend (currently only Pocketbase).

While researching, I discovered that “On-demand revalidation” is a very valid option for saving server resources in exchange for having more data in the cache, but this option requires integration with the backend you use in your project.

Workflow

1. The user visits a page

2. The server checks if that page exists in the cache

3. If it exists in the cache, Nitro returns the cached page, and Nitro checks in the background whether the backend data has changed by reviewing “the data block”; since the backend did not send any signal, Nitro returns “the data block” from the cache

4. If the page does not exist in the cache, it generates a new page, and Nitro checks if there is a “data block” in the cache; if there isn’t, it fetches the data from the backend

5. Nitro’s configuration ensures that when a fetch is performed, that data is stored in the cache; that “data block” will expire in one week unless the backend sends an event to reset it.

6. If the data changes on the backend, it sends an event to reset the cache in Nitro

You can run the script with bun, npm or pnpm

Example

npx nurev  

More info

https://codeberg.org/Serroda/nurev#how-it-works

Take a look and let me know what you think
Have a good day!

Hi

Hello, I created this project with the goal of quickly setting up a template using Nuxt and the “On-demand revalidation” configuration, integrated with a backend (currently only Pocketbase).

While researching, I discovered that “On-demand revalidation” is a very valid option for saving server resources in exchange for having more data in the cache, but this option requires integration with the backend you use in your project.

Workflow

1. The user visits a page

2. The server checks if that page exists in the cache

3. If it exists in the cache, Nitro returns the cached page, and Nitro checks in the background whether the backend data has changed by reviewing “the data block”; since the backend did not send any signal, Nitro returns “the data block” from the cache

4. If the page does not exist in the cache, it generates a new page, and Nitro checks if there is a “data block” in the cache; if there isn’t, it fetches the data from the backend

5. Nitro’s configuration ensures that when a fetch is performed, that data is stored in the cache; that “data block” will expire in one week unless the backend sends an event to reset it.

6. If the data changes on the backend, it sends an event to reset the cache in Nitro

You can run the script with bun, npm or pnpm

Example

npx nurev  

More info

https://codeberg.org/Serroda/nurev#how-it-works

Take a look and let me know what you think
Have a good day!

Hi

Hello, I created this project with the goal of quickly setting up a template using Nuxt and the “On-demand revalidation” configuration, integrated with a backend (currently only Pocketbase).

While researching, I discovered that “On-demand revalidation” is a very valid option for saving server resources in exchange for having more data in the cache, but this option requires integration with the backend you use in your project.

Workflow

1. The user visits a page

2. The server checks if that page exists in the cache

3. If it exists in the cache, Nitro returns the cached page, and Nitro checks in the background whether the backend data has changed by reviewing “the data block”; since the backend did not send any signal, Nitro returns “the data block” from the cache

4. If the page does not exist in the cache, it generates a new page, and Nitro checks if there is a “data block” in the cache; if there isn’t, it fetches the data from the backend

5. Nitro’s configuration ensures that when a fetch is performed, that data is stored in the cache; that “data block” will expire in one week unless the backend sends an event to reset it.

6. If the data changes on the backend, it sends an event to reset the cache in Nitro

You can run the script with bun, npm or pnpm

Example

npx nurev  

More info

https://codeberg.org/Serroda/nurev#how-it-works

Take a look and let me know what you think
Have a good day!

Hello everyone, this version is special not only because of the new features, but also because for the first time someone has contributed to the code. This may seem trivial, but it is important to me and to the project, as it means that people like it and it will continue to grow over time

Djmenig, I don't know if you will read this, but thank you for your time and for your interest in making Fluid Tile better

Features

• Auto-switch layout based on tile count made by djmenig This new feature allows you to choose whether you want to add new desktops or switch to the next available layout with the default layouts, avoiding the creation of new desktops
• Add "Trigger overflow per screen", only works when "Switch to next tile layout" is enabled

Improvements

• The trigger that displayed the UI is now more accurate
• The QML object Timer is created dynamically and works independently
• Simplified the tile assignment process
• Preventing signals from other windows from being disabled in certain processes
• Maximize trigger simplified

That's all, remember that you can support the project by adding your ideas, reporting errors, or making pull requests, as well as inviting me to a “ko-fi”

Have a nice K-day!!!

Hello everyone, this version is special not only because of the new features, but also because for the first time someone has contributed to the code. This may seem trivial, but it is important to me and to the project, as it means that people like it and it will continue to grow over time

Djmenig, I don't know if you will read this, but thank you for your time and for your interest in making Fluid Tile better

Features

• Auto-switch layout based on tile count made by djmenig This new feature allows you to choose whether you want to add new desktops or switch to the next available layout with the default layouts, avoiding the creation of new desktops
• Add "Trigger overflow per screen", only works when "Switch to next tile layout" is enabled

Improvements

• The trigger that displayed the UI is now more accurate
• The QML object Timer is created dynamically and works independently
• Simplified the tile assignment process
• Preventing signals from other windows from being disabled in certain processes
• Maximize trigger simplified

That's all, remember that you can support the project by adding your ideas, reporting errors, or making pull requests, as well as inviting me to a “ko-fi”

Have a nice K-day!!!

Hello again, new version = new features

This version is designed to improve the mouse experience for those who don't like the overlay taking up the entire screen. The Compact mode, similar to KZones or MouseTiler, allows you to move your windows around the tiles in KWin tile manager (Meta + T shortcut) with a small window and now the UI adapts to your KDE theme.

Features

• New compact mode for the UI

• Fluid tile adapts to the KDE theme

• New extra empty desktop appears when the last desktop contains windows, allowing you to always have a free desktop, similar to the behavior in GNOME

• New popup appears when executing the “Change tile layout” shortcut

• Improvements for Plasma 6.6

https://codeberg.org/Serroda/fluid-tile/releases/tag/v6.0

https://codeberg.org/Serroda/fluid-tile/wiki/Installation

https://codeberg.org/Serroda/fluid-tile/wiki/User-interface

Demos

https://codeberg.org/Serroda/fluid-tile/raw/commit/066003066815a2a26ec3f17b9fb43a765e636355/.meta/compact_mode_cursor.webp

https://codeberg.org/Serroda/fluid-tile/raw/commit/4247fad9b689fef042c05fe16e4cfddcaf5c5fb2/.meta/popup_shortcut.webp

Just a quick note to say that these small projects depend on you, the users. My laptop keyboard is currently broken, so I have to program the script using a Bluetooth keyboard from Aliexpress. I need a little help from you so I can continue developing the script

So far, there has only been one donation in five months of development to help repair the laptop, but it's still not enough

If you like the project and want to continue seeing updates, or if you think it has a future, you can help me through these links

https://ko-fi.com/M4M81LR295

https://liberapay.com/Serroda/donate

Hello again, new version = new features

This version is designed to improve the mouse experience for those who don't like the overlay taking up the entire screen. The Compact mode, similar to KZones or MouseTiler, allows you to move your windows around the tiles in KWin tile manager (Meta + T shortcut) with a small window and now the UI adapts to your KDE theme.

Features

• New compact mode for the UI

• Fluid tile adapts to the KDE theme

• New extra empty desktop appears when the last desktop contains windows, allowing you to always have a free desktop, similar to the behavior in GNOME

• New popup appears when executing the “Change tile layout” shortcut

• Improvements for Plasma 6.6

https://codeberg.org/Serroda/fluid-tile/releases/tag/v6.0

https://codeberg.org/Serroda/fluid-tile/wiki/Installation

https://codeberg.org/Serroda/fluid-tile/wiki/User-interface

Demos

https://codeberg.org/Serroda/fluid-tile/raw/commit/066003066815a2a26ec3f17b9fb43a765e636355/.meta/compact_mode_cursor.webp

https://codeberg.org/Serroda/fluid-tile/raw/commit/4247fad9b689fef042c05fe16e4cfddcaf5c5fb2/.meta/popup_shortcut.webp

Just a quick note to say that these small projects depend on you, the users. My laptop keyboard is currently broken, so I have to program the script using a Bluetooth keyboard from Aliexpress. I need a little help from you so I can continue developing the script

So far, there has only been one donation in five months of development to help repair the laptop, but it's still not enough

If you like the project and want to continue seeing updates, or if you think it has a future, you can help me through these links

https://ko-fi.com/M4M81LR295

https://liberapay.com/Serroda/donate

Hi, I have good news for those who use a tilling system. I have been working these month on a new system for Fluid tile with the aim of making it easier to maintain and more reliable when moving your windows

During the rewrite, I had to discard some user options that increased the possibility of a error. These options did not add any real value, and I preferred to prioritize reliability of the script

Features

Shortcuts

• Fluid tile | Toggle window to blocklist: Disables the window that is active or has focus so that it does not interact with Fluid tile. If the application name was already included in the block list in the user configuration, the list will take precedence over this shortcut.

  • Sequence: Meta+F

• Fluid tile | Change tile layout: Change the layout of the tiles and rearrange the windows

  • Sequence: Meta+Alt+F

You can change them in the system settings https://codeberg.org/Serroda/fluid-tile/wiki/Shortcuts

Breaking changes

• WindowExtendTileChangedDelay now by default is 300, change in your user settings with this value
  • More info: https://codeberg.org/Serroda/fluid-tile/wiki/Animations

Now, windows will always expand when possible, the UI cannot be disabled, and whenever you move a window to a tile that already has windows, they will always be swapped

These variables will stop working:

• WindowsOrderMove
• WindowsExtendOpen
• WindowsExtendClose
• WindowsExtendMove
• WindowsExtendMinimize
• WindowsExtendResize
• UIEnable

I recommend you take a look at the wiki where it will clarify your doubts https://codeberg.org/Serroda/fluid-tile/wiki

One more thing, this time the news isn't so good

Since my laptop keyboard broke (for whatever reason, neovim doesn't work well without a keyboard /s), I don't have the money to repair it right now, and I have to study for my firefighter exams, there will be fewer updates to the script in the coming months

I encourage you to try it out and let me know what you think. If you find any errors, you can report them in the repository

https://codeberg.org/Serroda/fluid-tile/issues

Have a nice day!

Hi, I have good news for those who use a tilling system. I have been working these month on a new system for Fluid tile with the aim of making it easier to maintain and more reliable when moving your windows

During the rewrite, I had to discard some user options that increased the possibility of a error. These options did not add any real value, and I preferred to prioritize reliability of the script

Features

Shortcuts

• Fluid tile | Toggle window to blocklist: Disables the window that is active or has focus so that it does not interact with Fluid tile. If the application name was already included in the block list in the user configuration, the list will take precedence over this shortcut.

  • Sequence: Meta+F

• Fluid tile | Change tile layout: Change the layout of the tiles and rearrange the windows

  • Sequence: Meta+Alt+F

You can change them in the system settings https://codeberg.org/Serroda/fluid-tile/wiki/Shortcuts

Breaking changes

• WindowExtendTileChangedDelay now by default is 300, change in your user settings with this value
  • More info: https://codeberg.org/Serroda/fluid-tile/wiki/Animations

Now, windows will always expand when possible, the UI cannot be disabled, and whenever you move a window to a tile that already has windows, they will always be swapped

These variables will stop working:

• WindowsOrderMove
• WindowsExtendOpen
• WindowsExtendClose
• WindowsExtendMove
• WindowsExtendMinimize
• WindowsExtendResize
• UIEnable

I recommend you take a look at the wiki where it will clarify your doubts https://codeberg.org/Serroda/fluid-tile/wiki

One more thing, this time the news isn't so good

Since my laptop keyboard broke (for whatever reason, neovim doesn't work well without a keyboard /s), I don't have the money to repair it right now, and I have to study for my firefighter exams, there will be fewer updates to the script in the coming months

I encourage you to try it out and let me know what you think. If you find any errors, you can report them in the repository

https://codeberg.org/Serroda/fluid-tile/issues

Have a nice day!

Edit: Demo video https://youtu.be/SKre99-ud-U

Hello again, this new version 4.0 has taken quite a bit of work since KWin doesn't make it easy for me

Features

• Your windows now extend across empty spaces (This has been like a pain in the ass)

• Windows open on the desktop and screen where you have focus

• Fluid tile has been rewritten with EMACScript modules, improving code efficiency and maintainability More information

Update your script and let me know your feedback

Thank you and have a nice day!!

Hello again, I just released a great new version that lets you organize your windows quickly and efficiently on your desktop

TLDR

Features:

• Move windows between tiles with the new user interface by simply dragging the windows.

• You can now customize the layout that will be set on the newly created virtual desktop.

• New wiki

I know not everyone uses keyboard shortcuts, so to help you use the script more effectively by moving windows around tiles without shortcuts, I've created a new user interface that activates when you move windows

You can also create your own layouts when creating a new virtual desktop, allowing people with multiple monitors to use the script without misalignments in the tiles

New wiki that allows you to learn how Fluid tile works

Preview

Thanks for reading. Have a nice day!!!

Hi, it's me again, the guy trying to make KDE with KWin a smooth experience with this script. In these latest versions, I've managed to add several features to customize your tiling experience.

New Features

• You can now configure window priority based on the width, height, and position of the tiles.

• You can also select a default layout that is set when creating a new virtual desktop.

Some of you may wonder why this script exists when there are plugins like Krohnkite. The main difference is that Fluid tile uses the native KWin API, which ensures compatibility and integration of the script with KDE, simplifying development and adapting to future changes in KDE.

It is gradually growing, and I would like you to take a look at it to hear your opinion and if you have any more ideas to implement. I'm listening!