Global search GUI for antiX

[Member Wallon]

Helpful

Up

0

::

Dear PPC,

It’s OK with me because it doesn’t modify the *.pot file.
Here is the detail of the pot file after your correction for the 3 windows (variable “mv_finder” replaced by “Finder” on line 67, 109 and 295)

Kind regards,
Wallon

# SOME DESCRIPTIVE TITLE.
# Copyright (C) YEAR THE PACKAGE'S COPYRIGHT HOLDER
# This file is distributed under the same license as the PACKAGE package.
# FIRST AUTHOR <EMAIL@ADDRESS>, YEAR.
#
#, fuzzy
msgid ""
msgstr ""
"Project-Id-Version: PACKAGE VERSION\n"
"Report-Msgid-Bugs-To: \n"
"POT-Creation-Date: 2023-11-12 18:53+0100\n"
"PO-Revision-Date: YEAR-MO-DA HO:MI+ZONE\n"
"Last-Translator: FULL NAME <EMAIL@ADDRESS>\n"
"Language-Team: LANGUAGE <LL@li.org>\n"
"Language: \n"
"MIME-Version: 1.0\n"
"Content-Type: text/plain; charset=UTF-8\n"
"Content-Transfer-Encoding: 8bit\n"
#: finder:13
msgid ""
"You need to have yad installed. Please make sure it is installed and re-run "
"this script"
msgstr ""
#: finder:14
msgid "Nothing to do"
msgstr ""
#: finder:15
msgid "Finder"
msgstr ""
#: finder:16
msgid "not empty, continuing"
msgstr ""
#: finder:17
msgid ""
"No results found for files/folders with names containing this expression, in "
msgstr ""
#: finder:18
msgid "Exit"
msgstr ""
#: finder:19
msgid "COMMAND could not be found"
msgstr ""
#: finder:20
msgid "is a command meant to be run from the terminal"
msgstr ""
#: finder:21
msgid ""
"There are instalable packages that match that query, available in the "
"Repository (and their version): "
msgstr ""
#: finder:22
msgid "No results found for this application or setting:"
msgstr ""
#: finder:23
msgid "Internet: ok"
msgstr ""
#: finder:24
msgid "Download ddgr (40kb)?"
msgstr ""
#: finder:25
msgid " OK "
msgstr ""
#: finder:26
msgid "ddgr not installed!"
msgstr ""
#: finder:27
msgid "Search parameter is empty, exiting"
msgstr ""
#: finder:28
msgid "No region (results are shown in English)"
msgstr ""
#: finder:29
msgid "The current Region code for web searches is:"
msgstr ""
#: finder:30
msgid "It will be replaced by:"
msgstr ""
#: finder:31
msgid "starting Finder"
msgstr ""
#: finder:32
msgid "Language"
msgstr ""
#: finder:33
msgid "New search"
msgstr ""
#: finder:34
msgid "Files"
msgstr ""
#: finder:35
msgid "Apps/Settings"
msgstr ""
#: finder:36
msgid "Web"
msgstr ""
#: finder:37
msgid "Run"
msgstr ""
#: finder:38
msgid "(Terminal command)"
msgstr ""
#: finder:39
msgid "No region"
msgstr ""
#: finder:40
#, sh-format
msgid ""
"WARNING: Closing this terminal window will close also the $query instance "
"running inside it!"
msgstr ""
#: finder:41
msgid "Press any key to close this terminal window"
msgstr ""
#: finder:42
msgid "Searching, please wait"
msgstr ""

[Member Wallon]

Helpful

Up

0

::

Thank you very much anticapitalista for updating finder.pot with comments on Git.

[Member marcelocripe]

Helpful

Up

0

::

Hello everybody.

I’m returning after several versions, today I managed to translate the Finder into Transifex and test the “finder-fixed-please_wait-windows.tar” version and everything worked as expected for each of the buttons.
Unfortunately, I was unable to see the translated texts in the “finder-fixed-please_wait-windows.tar” version and in the version that is available on GitLab.
I downloaded the Transifex file to test the “pt_BR” translation, my objective was to make the necessary adjustments to the “pt_BR” texts.
I noticed an important detail, which I had already warned about in this topic, the comments in the “.pot” file must have the “#.” (the hash and the period), look at the files that were created by Robin. Open the antixscreenshot2.pot file with Geny and notice that the text and comments are in blue. You need to correct the “.pot” file by changing “#” to “#.” In the lines containing comments, the color will change from red to blue.

@PPC here is the Gitlab repo

https://gitlab.com/antiX-Linux/antix-finder

It will be included on antiX-23.1-full.

Thank you anticapitalista for this important information.

– – – – –

Olá a todos.

Eu estou retornando após várias versões, hoje eu consegui traduzir o Finder no Transifex e testar a versão “finder-fixed-please_wait-windows.tar” e tudo funcionou conforme era esperado de cada um dos botões.
Infelizmente, eu não consegui ver os textos traduzidos na versão “finder-fixed-please_wait-windows.tar” e na versão que está disponível no GitLab.
Eu baixei o arquivo do Transifex para testar a tradução “pt_BR”, o meu objetivo era fazer os ajustes necessários nos textos “pt_BR”.
Eu observei um detalhe importante, no qual eu já havia alertado neste tópico, os comentários do arquivo “.pot” precisam possuir o “#.” (o cerquilha ou octótropo e o ponto), observem os arquivos que foram criados pelo Robin. Abra o arquivo antixscreenshot2.pot com o Geny e observe que o texto os comentários estão em cor azul. É preciso corrigir o arquivo “.pot”, alterando “#” para “#.” nas linhas que contenham os comentários, a cor irá mudar de vermelho para azul.

@PPC here is the Gitlab repo

https://gitlab.com/antiX-Linux/antix-finder

It will be included on antiX-23.1-full.

Obrigado anticapitalista por esta informação importante.

[Member Wallon]

Helpful

Up

0

::

Dear Marcelocripte,

I don’t agree with you. The Transifex documentation does not require a dot after #. There are two ways of entering comments. You can see/read my comments in Transifex.

Kind regards,
Wallon.

[Member marcelocripe]

Helpful

Up

0

::

I don’t agree with you. The Transifex documentation does not require a dot after #. There are two ways of entering comments. You can see/read my comments in Transifex.

Dear Waalon.

I never got around to reading the documentation you mentioned. However, Robin is the best person to explain this with technical details that I don’t know how to explain.

– – – – –

I don’t agree with you. The Transifex documentation does not require a dot after #. There are two ways of entering comments. You can see/read my comments in Transifex.

Caro Waalon.

Eu nunca pude ler a documentação que você mencionou. Contudo, o Robin é a pessoa melhor indicada para explicar isso com detalhes técnicos que eu não sei explicar.

[Member Wallon]

Helpful

Up

0

::

Dear Marcelocripte,

Please go to Transifex now and open the finder.pot file. You will see my comments in Transifex.
The first finder.pot file uploaded to Transifex and GitLab had no comments.
The second finder.pot file uploaded to Transifex and GitLab had my comments.
I had written to the translators that they should wait for an update from Transifex. You translated too quickly!

I had put the Transifex documentation in this thread;
Transifex documentation – add comments

Kind regards,
Wallon

[Member verdy]

Helpful

Up

0

::

If I place the mouse cursor in the input area and click the right button, the application will terminate.
Does the same thing happen to others?

finder-fixed-please_wait-windows
antiX23 runit[en] Live USB

[Member ile]

Helpful

Up

0

::

Hello
hello verdy, right-click in entrybox terminates; checking older versions agrees with finder-fixed-please_wait-windows/finder
with that behavior. Finder accepts controlV Paste, and Finder accepts middle-click Paste, interacts with clipboard For You?

[Member ile]

Helpful

Up

0

::

Hello PPC
Finder Launch from toolbar.
I Finder myself planning ahead by Placing the mouse pointer at location Where i wish Finder appear, prior to entering command into terminal or Run. A Launcher will bring Finder to its Launcher.
In icewm and in jwm the window of Finder nicely adjacent toolbar hug.
In fluxbox the window of Finder is Below, under the fluxbox toolbar. I did not trial tint2, but i suppose Finder will play nicely with the tint2 Panel.

[Member PPC]

Helpful

Up

0

::

@verdy – Yes. This is the expected behavior. Anything else other than entering text, left clicking the textbox or the buttons or middle mouse click (to paste to the search-box what’s in the clipboard) will close the main window. This is caused by the use of the “–close-on-unfocus” flag on the command that draws the main window. This option was selected by me to make the search-box “feel more like part of the toolbar/menu”, without access to any contextual menu- just type what you want, nothing more… Clicking outside the main window or pressing Esc, closes the searchbox.
I can’t please every single user, so I have to make design choices. Software is always being developed… That said, the right time to say “Hi, I would like this function/feature to work” is when the developer says “Please test, all input is welcomed”…

@ile – thanks for testing- all development and my testing was done in pure IceWM antiX, no other Window Manager was tested, not even FT10 toolbar. I knew that this kind of yad windows, that I use on my scripts, when placed at the exact mouse pointer position “hugged” the toolbar (I like that term). From back when I was developing FT10 I think I remember that in JWM, by default, that happened too. I never even thought about testing Fluxbox, since it does not allow for quick-launch icons (but now allows quick-launch toolbar text entries, that can be used to start this script).
Once again, making the search-box appear at the exact mouse pointer position was a design choice – one easy to revert, I just have to replace one flag “–mouse” with “–center” to always make the search-box pop up in the middle of the screen.
My reasoning to have the search-box appear at the pointer’s position is so the user has to move the pointer just a bit, to select where to search, instead of having to move it from the toolbar/menu to the center of the screen. I’ll try to investigate if there’s an easy way to easily make the searchbox come up above Fluxbox’s toolbar…

Due to my personal/work life, I don’t have that much time to dedicate to this script. It consumed most of my free time for about 2 weeks- I made it almost exactly as feature rich as I wanted it to be, as easy to use as I wanted it to be… But developing software is a never ending battle – bugs are found, better ways to do stuff are discovered, new suggestions are made… So it’s hard, for me, to always try to be on top of all that. I like to finish a script, and, when the testing period is over and no terrible bugs are found, I just consider it finished (until something prompts me to create a new version, when I have the time/will power).

P.

[Member PPC]

Helpful

Up

0

::

@ile – I found not a fix, but a work-around, to displaying the search box, at the mouse pointer, in Fluxbox: adding the flag “–on-top” to the yad command that draws the search-box.
Please test this (on fluxbox and JWM- and please, if possible, in FT10/tint2 toolbar too). If you like this solution, I’ll try to commit that change to the antiX git page, so that setting can be used on the “final product”.

Edit: after a very quick test. Using the “–on-top” flag:
– on IceWM – the search-box still “hugs the toolbar”
– on JWM – the search-box is displayed on top the toolbar, partly covering it
– on Fluxbox – the search-box is displayed on top the toolbar, partly covering it
– on FT10/tint2 toolbar – the search-box is “hugs the toolbar”

I can’t say I deslike seeing the searchbox on top the toolbar, but it does make it look less integrated int the system…
A more complex work around is checking if Fluxbox is running, and, if so, use the “–on-top” flag, on the yad command that renders the search-box (not that complex, but I would really, really not like putting the extra work on the script.

P.

• This reply was modified 2 weeks, 5 days ago by PPC.

Attachments:

1. finder-13-11-2023.tar

[Member marcelocripe]

Helpful

Up

0

::

I had put the Transifex documentation in this thread;
Transifex documentation – add comments

Thank you Wallon.
I hadn’t seen your answer on the other page of this topic.
I think there must be a reason Robin uses the “#.” (with the dot) instead of “#” (without the dot).

– – – – –

I had put the Transifex documentation in this thread;
Transifex documentation – add comments

Obrigado Wallon.
Eu não tinha visto esta resposta sua na outra página deste tópico.
Eu penso que deve haver um motivo para o Robin utilizar o “#.” (com o ponto) ao invés do “#” (sem o ponto).

[Member ile]

Helpful

Up

0

::

Hello PPC
After trialing every possible combination of options for yad main
finding that /finder-fixed-please_wait-windows/finder is The Best.

The border size from 10 to 22 raises well the fluxbox height
and hoping You accept that as the closest thing to Your vision for General.
Keeping Your width adding 24.
With that border increase Most fluxbox toolbars will see buttons. Beautiful.
Everything Your original idea for You to choose how much padding border is allowed(?)
(, because even as it is[10] in finder-fixed-please_wait-windows fluxbox is usable and Special! in a good way.)
[This path /usr/share/icons/Adwaita/48×48/ is somehow not in this antiX23.
This path /usr/share/icons/Adwaita/48×48/legacy is somehow not here on an antiX23base.]

Is a great lesson within unfocus terminates. Thanks.
I also played with horizontal line unnecessarily.
An –image change for demonstration only, this image chosen because of its size for the demonstration,
The dialog size is relative to the –image size (the image will not be resized.)

Hugs. cheers.
yad --title="$mv_finder" --width=424 --image=/usr/share/antiX/FAQ/images/antix-logo-3.png --text="" --borders=22 --mouse --undecorated --close-on-unfocus --escape-ok --skip-taskbar --form --field="" --button="⌕ $mv_Files_2":2 --button="⌕ $mv_Apps_Settings_4":4 --button="⌕ $mv_Web_44":44 > /tmp/yad --field=:LBL --field=:LBL
and i must ask, comment, is## two## together## thinking it is a comment, now a no-no?
## 2 is not #space and is not #dot. do i avoid ### ?

[Member verdy]

Helpful

Up

0

::

@ile, @PPC
thank you very much.

I have used mostly only MS-DOS/Windows exclusively for almost over 40 years.
Therefore i’m embarrassed to say that I didn’t know about middle-click pasting in the X Window System until now.
Also, I didn’t know that right-clicking would close the application window.
It is all right now.

[Member PPC]

Helpful

Up

0

::

@all – one question, about something that’s been always in my mind, related to Finder – does anyone want (or think it’s a good idea) an extra button, to “ask AI”? It would be trivial, since a basic GUI for that already exists, also using a command line program “tgpt”.
Ex: one can type at the search box “What is antiX Linux?”, press the “ask AI” button and, in a few seconds, a yad window with a detailed answer would appear. This now works in several languages, not just in English. That’s nice, since most web pages are in English, and many, many users can’t read that language…

There are several reasons that turn me off adding this feature:
– I assume, not using a browser solves most privacy problems (since it has no log-in, etc), but user’s IP is shared with the AI, right?
– tgpt may cease working at any time, and I don’t want users complaining about that, since it’s not my fault- if the web-search, that uses “ddgr” ceases to work, we have a plan B, the script can be quickly adapted to open results of the web query directly in the default browser. There is no plan B if “tgpt” fails to work or the AI is off-line (that has happened before).
– AI’s are notorious for sometimes just making stuff up, or providing false information. Searching on-line you at least have several sources to check. I like asking a question and getting a near instant reply, almost like asking something to a real person… but we can’t ever forget that: AI’s are not real, are just a piece of very complex software, without any life or life experience. AI’s are not all knowing and may be prone to say something that is not true. AI’s can be manipulated by user prompts to circumvent the original programming (ex: of not giving users dangerous information, of acting like they have feelings, etc)

P.

• This reply was modified 2 weeks, 4 days ago by PPC.

[Author]

Posts