iconForURL(): Fix root directory (/) icon. #129

Merged
MicheleC merged 1 commits from issue/128 into master 3 years ago
Collaborator

This resolves issues #128 and tdebase#1.

This resolves issues #128 and [tdebase#1](https://mirror.git.trinitydesktop.org/gitea/TDE/tdebase/issues/1).
blu.256 added this to the R14.0.10 release milestone 3 years ago
blu.256 added the PR/rfc label 3 years ago
blu.256 removed this from the R14.0.10 release milestone 3 years ago
Owner

Please, you can use the issue TDE/tdebase#1 format in commit message to refer issue from another repository? Using the word issue will ensure the generation of reference in Changelog on Wiki. Using the prefix TDE/ will ensure the generation of reference on TGW.

Please, you can use the **issue TDE/tdebase#1** format in commit message to refer issue from another repository? Using the word **issue** will ensure the generation of reference in Changelog on Wiki. Using the prefix **TDE/** will ensure the generation of reference on TGW.
Owner

Uhm... I rebuilt tdelibs with this patch, restarted my system and tested, but I don't see the red folder in Konqueror when I select the / folder.
Not sure I am doing something wrong, I don't think I am.
@blu256 Does this work on your system?

Uhm... I rebuilt tdelibs with this patch, restarted my system and tested, but I don't see the red folder in Konqueror when I select the / folder. Not sure I am doing something wrong, I don't think I am. @blu256 Does this work on your system?
blu.256 force-pushed issue/128 from ec9fe3cf56 to b056cf7982 3 years ago
Owner

Great, following the indications from here (thanks @blu256) it works.

My troubles in testing this raise a question: how do we deliver this to the users and make sure the new correct icon is used even if the user dows not clean the cache? It would be great if it just worked, since it is unlikley users will clean their konqueror cache.
Any idea?

Other feedback: open/save dialogs (for example from Kate) use the standard icon, not the red folder for root. We can look into it in a separate PR and in any case a folder icon is used at the moment.

Great, following the indications from [here](https://mirror.git.trinitydesktop.org/gitea/TDE/tdebase/issues/192#issue-1642) (thanks @blu256) it works. My troubles in testing this raise a question: how do we deliver this to the users and make sure the new correct icon is used even if the user dows not clean the cache? It would be great if it just worked, since it is unlikley users will clean their konqueror cache. Any idea? Other feedback: open/save dialogs (for example from Kate) use the standard icon, not the red folder for root. We can look into it in a separate PR and in any case a folder icon is used at the moment.
Poster
Collaborator

@SlavekB Is the new commit message OK?

@SlavekB Is the new commit message OK?
Owner

@SlavekB Is the new commit message OK?

Yes!

> @SlavekB Is the new commit message OK? Yes!
Poster
Collaborator

My troubles in testing this raise a question: how do we deliver this to the users and make sure the new correct icon is used even if the user dows not clean the cache? It would be great if it just worked, since it is unlikley users will clean their konqueror cache.
Any idea?

Could we possibly add a release first-start shell script (like tde_release_notes) to sed out the intimidating cache entry?

> My troubles in testing this raise a question: how do we deliver this to the users and make sure the new correct icon is used even if the user dows not clean the cache? It would be great if it just worked, since it is unlikley users will clean their konqueror cache. > Any idea? Could we possibly add a release first-start shell script (like `tde_release_notes`) to `sed` out the intimidating cache entry?
Owner

Could we possibly add a release first-start shell script (like tde_release_notes) to sed out the intimidating cache entry?

Nice idea. I was thinking about adding a note in the release notes, but your suggestion is much better!
Will you add to this PR?

> Could we possibly add a release first-start shell script (like `tde_release_notes`) to `sed` out the intimidating cache entry? Nice idea. I was thinking about adding a note in the release notes, but your suggestion is much better! Will you add to this PR?
Poster
Collaborator

Will this shell script be a part of this PR? If so, then yes, I need a little time to work on it.

Will this shell script be a part of this PR? If so, then yes, I need a little time to work on it.
Owner

It should probably go into tdebase where we have other start up scripts like starttde, r14-xdg-update and tde_release_notes.

It should probably go into tdebase where we have other start up scripts like starttde, r14-xdg-update and tde_release_notes.
Owner

I suggest we merge this PR together with the one with the script in tdebase, so it will be easier to test the functionality of the script.
PR is good to merge, in any case.

I suggest we merge this PR together with the one with the script in tdebase, so it will be easier to test the functionality of the script. PR is good to merge, in any case.
blu.256 removed the PR/rfc label 3 years ago
MicheleC reviewed 3 years ago
i = mimeTypeIcon;
// special case: root directory (/) -- Gitea issue #128
if ( _url == KURL("file:///") )
Owner

Hi Philippe,
could you change the "tab" to 8 spaces? on systems with tab != 8 spaces, it causes the "if" line to be badly misaligned. Again consistency with the code around the changes.

Hi Philippe, could you change the "tab" to 8 spaces? on systems with tab != 8 spaces, it causes the "if" line to be badly misaligned. Again consistency with the code around the changes.
Poster
Collaborator

Fixed in fafb93170f.

Fixed in fafb93170f.
blu.256 marked this conversation as resolved
Owner

@blu256
good practice is to check the surrounding part of the file and try to follow the same indentation.
You could observe that TDE code is badly formatted and you would be perfectly right. For that we have started work on a code format guideline and a framework for automatically check/enforce the code format will be follow, although we still have a long way to go there.

@blu256 good practice is to check the surrounding part of the file and try to follow the same indentation. You could observe that TDE code is badly formatted and you would be perfectly right. For that we have started work on a code format guideline and a framework for automatically check/enforce the code format will be follow, although we still have a long way to go there.
MicheleC requested changes 3 years ago
MicheleC left a comment
Owner

As per comment below

As per comment below
Owner

As per comment below

well, turns out to be "comment above" 😓

> As per comment below well, turns out to be "comment above" 😓
Owner

Perfect! Can I ask one last think? Squash the two commits into one? I could do it myself but the commit would lose your GPG key :-(

Perfect! Can I ask one last think? Squash the two commits into one? I could do it myself but the commit would lose your GPG key :-(
blu.256 force-pushed issue/128 from fafb93170f to 646661d0be 3 years ago
Poster
Collaborator

Done!

Done!
MicheleC merged commit 646661d0be into master 3 years ago
MicheleC approved these changes 3 years ago
MicheleC deleted branch issue/128 3 years ago
Owner

Great, merged and backported.

Great, merged and backported.
MicheleC added this to the R14.0.10 release milestone 3 years ago

Reviewers

MicheleC approved these changes 3 years ago
The pull request has been merged as 646661d0be.
Sign in to join this conversation.
No reviewers
No Milestone
No Assignees
3 Participants
Notifications
Due Date

No due date set.

Dependencies

No dependencies set.

Reference: TDE/tdelibs#129
Loading…
There is no content yet.