Freeter Community

Could you provide an example and a screenshot?

Hey! New user here! Really loving the app. Makes total sense with how I'd like to work. Still trying to wrap my head around all of the uses for the different widgets - there are so many ways to use them! Keep up the good work. Any plans for an ios/android app? Or maybe a web access version?

@sue It woks. The X will be focused after a click. Then clicking the top-right Okay button will remove the project silently‌.

This is a really good option. Thank you for your team's efforts!

Thanks. Issue resolved.

This topic explains where the data is. After making any significant changes in Freeter, I always make a copy of the folder. (It also allow me to transfer workflows to another computer.)

https://community.freeter.io/topic/9/export-and-import-local-settings

Agree about how good Freeter is!

The Link Opener is for stuff on the internet (URLs) while the File Opener is for content on your computer's disk.

Hovering the mouse over the ? of each widget shows a brief description of what the widget does.

b89002b1-c9e4-46af-becb-31574ba66c0c-image.png

I like the way a "new tab" link opens in a new window. To me, that makes sense within the Freeter workflow model. But I find myself dragging those windows around so they are mostly off-screen, so I can continue working on something else in the same workflow while keeping the link open. Needing to do that feels clunky when you are used to "clicking on a window makes it come to the front" way of thinking. I don't have an alternate idea other than, it would be nice having a simpler way to manager the open windows, than actually moving them around with the mouse so they don't hide the current workflow

I think you are right, there is no keyboard shortcut. I agree that it could be useful.

Thanks for the confirmation! Now Freeter sends a spoofed user-agent to look the same as a standard chrome browser, so it shouldn't break anytime soon 🙂

Thanks for the report!
Fixed in the new v2.4.3. Please give it a try 🙂

Fixed in 2.4.3