Hi, placeholder strings of "args" seems untranslated.

I think it happens due to this line.

https://github.com/liferooter/textpieces/blob/main/src/widgets/Editor.vala#L204

It would be nice to have textpieces do somes jwt decoding/encoding... a bit like one can do on https://jwt.io/

I use default adwaita (in light mode) and the current interface is pretty jarring for people with poor vision like me.
The app should just follow my system theme instead of enforcing a dark theme, or at least offer a setting.
@bertob

You should definitely create macOS version

The padding on the primary menu popover is too small and looks cramped. I'd bring it in line with other popovers (I think there's 12 or 18px of padding there usually).

Nautilus for comparison:

Text Pieces is not adaptive now and can't be used from touchscreen or on Linux-based phones or tablets.

• Adaptiveness
• In-app notification hover analog for touchscreen (can be done in future with AdwToast)
• Test the application with touchscreen

Dark theme setting should be shown when user's system doesn't have color sheme support or color sheme is 'default', not 'prefer-dark' or 'prefer-light'. Currently dark theme setting is shown only on systems which don't support color schemes.

Some tools have no error handling. It's not good and have to be fixed.

Tools without error handling

• Unescape HTML
• Unescape string
• Unescape URL
• Format XML

The app window is not showing for me on either Wayland or Xorg. I get nothing in the logs. If I start it from CLI no errors show up. The process keeps running. System Monitor shows it as sleeping. The flatpak version works fine, but it's not worth the overhead since I don't use any flatpak apps at all.

Tested on archlinux and Fedora 36

Argument entries is in the bottom of the window now. It's very strange and non-intuitive pattern. It will be good to move them to the top right corner and place one under one for more familiar search-like UI.

I understand why #63 was closed. However, how about an optional split window with one half showing a live preview of what a filter application would result in?

Execution of the filter should be async of course and not block any of the rest of the app.

Will it be possible to create a Windows version?

to reproduce:

1. change settings: gsettings set org.gnome.desktop.interface color-scheme prefer-light
2. install text pieces
3. start text pieces

expected:
text pieces is light

actual behavior:
text pieces is dark

It will be good to have ability to search in the editor

Add support for trimming text of all new lines - not just leading and trailing. This feature will be useful in copying text from certain PDF documents where a single paragraph is split into multiple lines using newline characters.

Quick question: where should I place the translation of tools.pot? Normally, po files should be in the po directory, but in this case, the po files in there are already used for the application translation. So where should I put the translation of the tools.pot file?

Please allow translations to be provided via a web browser using a service like Weblate.

What do you think?

Thank you

It's not building for me either, although, I'm getting different errors.

FAILED: src/textpieces.p/Application.c src/textpieces.p/Window.c src/textpieces.p/Preferences.c src/textpieces.p/Tool.c src/textpieces.p/ToolsController.c src/textpieces.p/ToolSettings.c src/textpieces.p/CustomToolPage.c src/textpieces.p/NewToolPage.c src/textpieces.p/Search.c src/textpieces.p/Utils.c 
/usr/bin/valac-0.52 -C --debug --debug --target-glib=2.70 --enable-experimental --vapidir /var/tmp/portage/app-text/text-pieces-3.0.2/work/textpieces-3.0.2/src/vapi /var/tmp/portage/app-text/text-pieces-3.0.2/work/textpieces-3.0.2/src/vapi/config.vapi --pkg libadwaita-1 --pkg gtksourceview-5 --pkg json-glib-1.0 --pkg gtk4 --pkg gio-unix-2.0 --pkg gio-2.0 --color=always --directory src/textpieces.p --basedir ../textpieces-3.0.2/src --gresources=../textpieces-3.0.2/resources/textpieces.gresource.xml ../textpieces-3.0.2/src/Application.vala ../textpieces-3.0.2/src/Window.vala ../textpieces-3.0.2/src/Preferences.vala ../textpieces-3.0.2/src/Tool.vala ../textpieces-3.0.2/src/ToolsController.vala ../textpieces-3.0.2/src/ToolSettings.vala ../textpieces-3.0.2/src/CustomToolPage.vala ../textpieces-3.0.2/src/NewToolPage.vala ../textpieces-3.0.2/src/Search.vala ../textpieces-3.0.2/src/Utils.vala
../textpieces-3.0.2/src/Window.vala:465.39-465.39: error: syntax error, expected identifier
                label = selected_tool?.name
                                      ^
../textpieces-3.0.2/src/Window.vala:481.40-481.40: error: syntax error, expected identifier
            var n_args = selected_tool?.arguments?.length ?? 0;
                                       ^
../textpieces-3.0.2/src/Window.vala:517.14-517.23: error: syntax error, following expression/statement delimiter `;' missing
        void show_toast (string text) {
             ^^^^^^^^^^
../textpieces-3.0.2/src/Window.vala:517.26-517.31: error: syntax error, following expression/statement delimiter `)' missing
        void show_toast (string text) {
                         ^^^^^^
../textpieces-3.0.2/src/Window.vala:517.26-517.31: error: syntax error, following expression/statement delimiter `;' missing
        void show_toast (string text) {
                         ^^^^^^
../textpieces-3.0.2/src/Window.vala:517.37-517.37: error: syntax error, expected identifier
        void show_toast (string text) {
                                    ^
../textpieces-3.0.2/src/Window.vala:518.52-518.52: error: syntax error, `new' modifier not allowed on creation method
            toast_overlay.add_toast (new Adw.Toast (text) {
                                                   ^
../textpieces-3.0.2/src/ToolsController.vala:167.28-167.28: error: syntax error, expected identifier
            var obj = root?.get_object ();
                           ^
Compilation failed: 8 error(s), 0 warning(s)

Hi, I just completed the translation of textpieces, and sent two PR for you.

I couldn't fix a problem: Tool headers do not follow translations.

I know it's related to these lines but adding _() didn't affect the label. You may know better.

Version: Master branch, the latest commit.

The current icon concept is nice, but it could be drawn more geometrically.

Here's an attempt:

Let me know if you like the direction, I'd be happy to open an MR.

It will be cool to have ability to load file content just by dropping the file into the editor

• Don't autohide in-app notification when it's hovered
• Close in-app notification automatically when cursor leaves it

Consider rewriting this undeniably perfect application in a new, modern and safe language named Rust. For more information about rust visit
https://www.rust-lang.org

You need to activate your Sponsor button for FUNDING.yml via Settings 😉

I just built a quick deb package and came across this warning:

textpieces: spelling-error-in-binary occured occurred [usr/bin/textpieces]

Cheers

If you want you can create a textpieces.doap file in the repo root. Builder takes the project name from this file in it's overview and you can add yourself as a maintainer on https://apps.gnome.org/app/com.github.liferooter.textpieces/ via this file.

Example file https://github.com/sonnyp/Commit/blob/main/Commit.doap

I noted that there is some unnecessary free space around the screenshots. The usual screenshot tools (like Alt + Print) should give a fitting screenshot.

It would be nice to have the option for text wrapping.

Thanks.

The About menu entry should include the app name.

So far Text Pieces only supports in-memory editing, even when you load text from a file.

In other words:

• Make the "Save to File" button write directly to the same file (if the text was loaded from a file);
• And add a "Save (copy) as..." button to save to a different file.

It would be nice to have "undo" button e.g. next to "Apply". It could simplify work a lot! Now once I apply some tool to my text and want to use the second tool I have to reopen the original text. Also, some two section window (one for input, one for output) might be a solution or the next interesting feature.

i still have to go to a random website for this, would be nice if this feature was available in this program.
a "sentence case" would be good too.

Hi!

The tool is amazing, the only problem is that if I select a single word and press CTRL-C to copy, the entire contents of the buffer are copied.

If I select a word and use the context menu with the mouse, I can copy only the selection. So it seems to me that the problem is only with CTRL-C.

The behavior is the same with flatpak installation or compiling from source.

Regards,
Marcelo Módolo

Currently, text pieces does not appear in the list of applications, if I try to set it to be used to open json or xml file types. Is there a way to allow it to be used that way?

In the About window of the app, clicking on the website button takes me to https://gitlab.com/liferooter/textpieces instead of https://github.com/liferooter/textpieces.

XML formatter throws raw Python error instead of handled user-readable error.

When i use textpieces i use the same tool in nine times out of ten.

Perhaps one could add a default tool to the preferences and when the application starts up it would have that selected? Not i big issue but it would save the user from always start by selecting a tool.

As an alternative one could just remember the last selected tool and use that when starting up the next time thus eliminating the need for adding UI to preferences.

Hi,

Some tools have a right corner area and they seems untranslated even they have translated strings.

Also when I change between tools, some strings keep adding and adding this area.

It looks like implementing the recoloring feature unfortunately removed the system wide color scheme support. I was wondering whether this was a design decision or a bug?

when doing base64 -d, if there is a part of the content wrong, for debugging we need to see the complete output.

echo "TG9yZW0gSXBzdW0gaXMgc2ltcGx5IGR1bW15IHRleHQgb2YgdGhlIHByaW50aW5nIGFuZ
CB0eXBlc2V0dGluZyBpbmR1c3RyeS4gTG9yZW0gSXBzdW0gaGFzIGJlZW4gdGhlIGluZHVzdHJ5
J3Mgc3RhbmRhcmQgZHVtbXkgdGV4dCBldmVyIHNpbmNlIHRoZSAxNTAwcywgd2hlbiBhbiB1bmtu
b3duIHByaW50ZXIgdG9vayBhIGdhbGxleSBvZiB0eXBlIGFuZCBzY3JhbWJsZWQgaXQgdG8gbWFr
ZSBhIHR5cGUgc3BlY2ltZW4gYm9vay4gSXQgaGFzIHN1cnZpdmVkIG5vdCBvbmx5IGZpdmUgY2V
udHVyaWVzLCBidXQgYWxzbyB0aGUgbGVhcCBpbnRvIGVsZWN0cm9uaWMgdHlwZXNldHRpbmc
sIHJlbWFpbmluZyBlc3NlbnRpYWxseSB1bmNoYW5nZWQuIEl0IHdhcyBwb3B1bGFyaXNlZCBpbiB0
aGUgMTk2MHMgd2l0aCB0aGUgcmVsZWFzZSBvZiBMZXRyYXNldCBzaGVldHMgY29udGFpbmluZ
yBMb3JlbSBJcHN1bSBwYXNzYWdlcywgYW5kIG1vcmUgcmVjZW50bHkgd2l0aCBkZXNrdG9wIHB1Y
mxpc2hpbmcgc29mdHdhcmUgbGlrZSBBbGR1cyBQYWdlTWFrZXIgaW5jbHVkaW5nIHZlcnNpb25zIG
9mIExvcmVtIElwc3VtLg1daf.12agh" | base64 -d
Lorem Ipsum is simply dummy text of the printing and typesetting industry. Lorem Ipsum has been the
 industry's standard dummy text ever since the 1500s, when an unknown printer took a galley of type
 and scrambled it to make a type specimen book. It has survived not only five centuries, but also the 
leap into electronic typesetting, remaining essentially unchanged. It was popularised in the 1960s with
 the release of Letraset sheets containing Lorem Ipsum passages, and more]ibase64: invalid inputpublishing 
software like Aldus PageMaker including versions of Lorem Ipsum.

Hi,

thank you for your work. It makes my life better.

Textpieces does not pick my default monospace font from gsettings. /org/gnome/desktop/interface/monospace-font-name
Is that intentional?

I am running version 2.3.3 from Flathub.

Thanks.

The word 'you' should be 'your'

Add support of application translating via gettext.

Related with #19

I am trying a local build . I have all the relevant dependencies installed.
OS: debian testing GCC: 11
I attached the test log below
meson_log.txt
.