summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* list-view: Hide Star column titleclear-starred-column-headerAntónio Fernandes2021-02-131-1/+7
| | | | | | | | | | | | | | | | While "Star" is 4 chars long in English, it's longer in other languages. This means the column may become much wider than needed for displaying a small star icon, which both looks bad and takes away space from other columns. Since this is a column of star symbols, we don't really need a title. But setting an empty title makes the columns too narrow (16px), which gets covered by the overlay scrollbar. So, in addition to removing the title label, set a 48 fixed width for the column, which provides enough gutter for the overlay scrollbar.
* location-entry: Highlight basenames of completionsJames Westman2021-02-121-0/+37
| | | | Or, rather, dim the dirnames so the basenames stand out.
* location-entry: Use relative completions for relative pathsJames Westman2021-02-121-1/+20
| | | | | | | | If the user enters a relative path, we get absolute paths as in the completion popover, which is quite jarring and makes it less useful. Instead, truncate the prefix, such that the completions dropdown text aligns with the entry text.
* location-entry: Use g_strstrip()James Westman2021-02-121-2/+2
| | | | Replace g_strchomp and g_strchug with g_strstrip, for simplicity.
* location-entry: Use GtkEntryCompletionJames Westman2021-02-121-31/+76
| | | | | | | | | Improves tab completion in the location entry. GtkEntryCompletion shows a popup when there are multiple matches, so you can choose one or continue typing. The completion's tree model is populated dynamically as you type using a GFilenameCompleter. https://gitlab.gnome.org/GNOME/nautilus/-/issues/1171
* location-entry: Play bell when tab-complete failsJames Westman2021-02-121-4/+11
| | | | | | | When you press Tab in the location entry and there's no autocomplete suggestion, play an error bell instead of closing the location entry. Closes https://gitlab.gnome.org/GNOME/nautilus/-/issues/1171
* location-entry: Remove folder iconJames Westman2021-02-121-13/+0
| | | | | It hasn't been useful for quite a while, and messes with the visual alignment of the GtkEntryCompletion.
* Update Galician translationFran Dieguez2021-02-121-34/+44
|
* Update Ukrainian translationYuri Chornoivan2021-02-121-44/+54
|
* Update Portuguese translationHugo Carvalho2021-02-121-24/+42
|
* file-conflict-dialog: Make manual rename more convenientAntónio Fernandes2021-02-121-5/+16
| | | | | | | | The suggested name is in the form "original (1).txt", if the the conflicting name was "original.txt". The user may want to replace the "(1)" bits with something more meaningful, so select this region for convenience.
* file-conflict-dialog: Automatically suggest new nameAntónio Fernandes2021-02-125-11/+37
| | | | | | | | | | | | When "Select new name for the destination" expander is selected, the users must type a new name in order to proceed. This makes them go and look at the destination to see what would even make a unique name. Let's be more helpful and suggest a unique name based on the original. Closes https://gitlab.gnome.org/GNOME/nautilus/issues/1344
* operations-ui-manager: Rename struct fieldAntónio Fernandes2021-02-121-5/+5
| | | | | | | .nautilus_directory holds a reference to a NautilusFile. Rename it to .nautilus_directory_file, so that the existing name can be reused to store a NautilusDirectory reference in the next commit.
* file-conflict-dialog: Tie default action to expanderAntónio Fernandes2021-02-121-24/+24
| | | | | | | | | | | The default action "Replace" is changed to "Rename" if a different name is set in the entry inside the "Select a new name..." expander. This means we have inconsistent UI states: * "Select a new name..." is expanded but the action is "Replace", * or it's collapsed but the default action is "Rename". Instead, let's tie the default action to the expander's state.
* build: Bump gnome-autoar dependencyOndrej Holy2021-02-121-1/+1
| | | | | This is needed to prevent the "signal 'request-passphrase' is invalid for instance '0x1e41340' of type 'AutoarExtractor'" warnings.
* ci: Add gnome-autoar master to DockerfileOndrej Holy2021-02-121-0/+10
| | | | | The CI currently fails because the gnome-autoar 0.3.0 is not yet in rawhide. Let's add gnome-autoar master to our image to fix the pipeline.
* file-operations: Add support for password protected archivesFelipe Borges2021-02-121-0/+91
| | | | | | | | | | | | This implementation launches a GtkDialog for users to enter a password when gnome-autoar reports that a given archive is password protected. We use an additional GMainContext to block the execution until a password string can be passed to AutoarExtractor's "passphrase-request" signal. This solution is an alternative to gtk_dialog_run(), which is not available in GTK4. See https://ondrej.holych.net/how-to-call-asynchronous-function-synchronously/ Fixes https://gitlab.gnome.org/GNOME/nautilus/-/issues/327
* Update Indonesian translationKukuh Syafaat2021-02-121-727/+713
|
* Update Swedish translationAnders Jonsson2021-02-111-263/+258
|
* Update Turkish translationEmin Tufan Çetin2021-02-111-268/+262
|
* Updated Spanish translationDaniel Mustieles2021-02-111-274/+286
|
* Update Portuguese translationHugo Carvalho2021-02-101-719/+705
|
* Update Romanian translationFlorentina Mușat2021-02-101-263/+258
|
* Update Galician translationFran Dieguez2021-02-101-268/+271
|
* Update Ukrainian translationYuri Chornoivan2021-02-101-265/+271
|
* preferences-window: Add description for the performance groupAntónio Fernandes2021-02-101-0/+1
| | | | Providing guidance for what the trade offs are.
* preferences-window: Clarify context menu optionsAntónio Fernandes2021-02-101-3/+4
| | | | | | Add a group descritpion to avoid long labels in the rows, use the exact label of the menu items instead. Also hint that keyboard shorcuts can be used instead of making the menu longer.
* preferences-window: Implement new single-page designAdrien Plazas2021-02-102-1011/+245
| | | | | | | | | | The Preferences have been recently cleaned up, which now enables us to reorganize them in a single page using modern design patterns. Use HdyPreferencesWindow for convenience of implementation, as well as for the rounded bottom corners and adaptivity to small sizes. Closes https://gitlab.gnome.org/GNOME/nautilus/-/issues/1258
* preferences-window: Remove leftovers from the pastAntónio Fernandes2021-02-102-142/+0
| | | | | | We have a few includes, defines and tree models which we no longer use. They used to be need for widgets and options which are long gone.
* ci: Add libhandy to DockerfileOndrej Holy2021-02-091-1/+1
| | | | | | The fedora rawhide CI job fails currently as the image doesn't contain libhandy package, which is new Nautilus dependency. Let's add the package to fix the CI job.
* Updated Spanish translationDaniel Mustieles2021-02-091-554/+541
|
* properties-window: Make bottom corners roundedChristopher Davis2021-02-093-12/+14
| | | | | | As we have already done for the app's main window. In this case, we must use HdyWindow.
* css: Match floating bar radius to window radiusChristopher Davis2021-02-091-1/+1
| | | | | | The bottom corners of the window have an 8px radius now. The floating status bar shares a corner with the window, but the opposite corner has a smaller radius, which doesn't look good. So, make it 8px too.
* window: Make bottom corners roundedChristopher Davis2021-02-096-11/+14
| | | | | CSS alone is not enough to achieve the desired result. The required pieces are provided by HdyApplicationWindow.
* general: Use libhandy 1.0Adrien Plazas2021-02-093-0/+5
| | | | It provides widgets we need for the enhancements in the next commits.
* window: Init toolbar from templateChristopher Davis2021-02-092-4/+4
| | | | | | This will allow us to easily set up HdyWindow, as otherwise we'd need to use GtkContainer APIs that will be removed in GTK4
* css: Don't conflict with drop target visual feedbackAntónio Fernandes2021-02-081-7/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | While dragging items over the list view, the row which accepts drops in the current pointer position has its top border highlighted, but not the bottom border, as indended by the default stylesheet. This had already been fixed.[1] The regression happened because GTK has stopped using .dnd style class, instead using :drop(active).[2] The previous fix ([1]) consisted in not highlighting any border at all, with the rationale that "we already modify the icon to hint about dnd". This is based on the assumptions that: 1. folder icons change to the folder-open icon; 2. folders are the only drop targets. But these assumptions do not hold: 1. the folder-open icon is not used if a folder has a custom image instead of the default icon, or if a thumbnailer is installed; 2. some non-folder items, such as archive files, accept drops too. So let's fix this the other way around: highlighting both borders, above and below, as intended by the default stylesheet. Closes https://gitlab.gnome.org/GNOME/nautilus/-/issues/1525 [1] https://gitlab.gnome.org/GNOME/nautilus/-/commit/4963cd7d564b633299f8e31bb8ac10f67eae6477 [2] https://gitlab.gnome.org/GNOME/gtk/-/commit/12c5ca5c013e035374ad1590b0e64cb7a452aa30
* preferences-window: Drop default columns tabAntónio Fernandes2021-02-082-149/+0
| | | | | | | | | | | | | Unlike most preferences, changing this may have no effect on open windows, which is unexpected. This affects only new folders without any per-folder override, which has diminute value. Remove this from the Preferences window. The gsettings key is preserved. Fixes https://gitlab.gnome.org/GNOME/nautilus/-/issues/1312 First part of https://gitlab.gnome.org/GNOME/nautilus/-/issues/1703
* preferences-window: Drop sidebar visibility checkboxAntónio Fernandes2021-02-082-56/+0
| | | | | | | | | | | | | | | | When preparing to drop the Application Menu, this was added to the Preferences window.[1] Later when actually dropping the Application Menu, the action was added to the primary window menu.[2] So, it ended up in 2 places, which it not necessary. The sidebar is essential for navigation, so hiding is only tempoary, not a long-lasting preference. So, it doesn't make sense to have here. [1] commit f2061e94093a33072e792181433b0618bf68d1b2 [2] commit 99324771868ca7fad75889418ecd08765d8b4629
* preferences-window: Drop image size thumbnail controlAntónio Fernandes2021-02-082-88/+0
| | | | | | | | | | | | It applies only to image files, which is unexpected. The drawbacks of setting a higher value are not explained either. How much is too much? The last commit has raised the default value to a hopefully high enough value making this UI control even less useful. The gsettings key is preserved for now. https://gitlab.gnome.org/GNOME/nautilus/-/issues/1309
* gschema: Raise thumbnail size limit to 50MBAntónio Fernandes2021-02-081-1/+1
| | | | | | | | This was last updated 12 years ago. Assuming 10MB is too low given today's hardware, make that 50MB. Closes https://gitlab.gnome.org/GNOME/nautilus/-/issues/1309
* Update Swedish translationAnders Jonsson2021-02-081-434/+426
|
* Updated Czech translationMarek Černocký2021-02-071-506/+446
|
* Update Romanian translationDaniel Șerbănescu2021-02-071-508/+499
|
* Update Ukrainian translationYuri Chornoivan2021-02-071-237/+226
|
* Update Turkish translationEmin Tufan Çetin2021-02-071-509/+503
|
* Update Galician translationFran Dieguez2021-02-071-509/+502
|
* preferences: Drop executable-text-activation settingAntónio Fernandes2021-02-065-125/+2
| | | | | | | | | | | | | | | | Whe the ASK option gone, the only alternative to the default is RUN. This option is not safe: it's too easy to accidentally run programs. Now we have a "Run as a Program" action in the context menu, which is available by default (no configuration required) and safe (clearly labeled, intentionally chosen). So, remove the RUN option is no longer necessary, and with it we can remove the preference from both the UI and GSettings schemas. Closes https://gitlab.gnome.org/GNOME/nautilus/-/issues/1700 Discussed in https://gitlab.gnome.org/GNOME/nautilus/-/issues/443
* mime-actions: Drop ACTIVATION_ACTION_ASKAntónio Fernandes2021-02-065-126/+4
| | | | | | | | | | | | | | | | | | There is an option in Preferences which enables a dialog asking users what they intend to do when they double-click an executable text file: open as a text file or run as a program? The dialog asking that question has known design problems, but they remain unaddressed, which is not surprising because it's non-default. Now, with the new menu item added in the last commit, the two options ("Open" and "Run as a Program") are both available by default in the context menu, so there is no need to ask the question in a dialog. Remove the option, the dialog, and the related code. Closes https://bugzilla.gnome.org/show_bug.cgi?id=598671 Part of https://gitlab.gnome.org/GNOME/nautilus/-/issues/1700
* files-view: Add action to run files as programsAntónio Fernandes2021-02-062-0/+76
| | | | | | | | | | | | | | | By default, when as executable text file is activated (by double-click, pressing <Return>, etc.), it opens as a regular text file (usually with a text editor). This is a safe and consistent behavior, but it makes runing scripts harder than it needs to be, requiring configuration by the user. Address this by introducing a new context menu action to run files as programs. (The code for this action was adapted from mime-actions.c.) Required for https://gitlab.gnome.org/GNOME/nautilus/-/issues/1700 Discussed in https://gitlab.gnome.org/GNOME/nautilus/-/issues/443
View Lorry Controller Status