arglebargle

kde, linux, busses, open source and the good old Grateful Dead.

  • 0 Posts
  • 96 Comments
Joined 1 year ago
cake
Cake day: July 16th, 2023

help-circle

  • Ubuntu has never been remotely stable for me. Something stupid breaks or becomes difficult to get what I want out of it.

    Been that way since it came out for me.

    I find Arch much less hassle than Ubuntu ever was.

    Just recently put Ubuntu on a machine for a work project. It was broken from the get go, throwing errors and being it’s usual shitty self.

    I could never recommend it.

    Fedora on the other hand has been on a spare laptop for about 6 months and I gotta say they really have put some polish in. Updates are frequent but reasonable and most everything works well. Some small issues but they are not show stoppers and Fedora is aware of them.










  • arglebargle@lemm.eetoPatient Gamers@sh.itjust.worksFallout 4
    link
    fedilink
    English
    arrow-up
    2
    ·
    5 months ago

    Guns don’t block a good chunk of the screen either.

    But YOU do! That is why I do not like third person, I do not want to see me. All immersion is lost! \

    But I started up my game, moused out to third person, and the gun sight didnt change at all. It is the same cross hairs based on gun accuracy either way.


  • arglebargle@lemm.eetoPatient Gamers@sh.itjust.worksFallout 4
    link
    fedilink
    English
    arrow-up
    1
    ·
    5 months ago

    That was two New Vegas and one VR title. Fallout 4 aiming doesn’t seem bad at all. You can manage with a sniper rifle as good as any other game. There is a slight chance that one of the mods I applied might have improved it, I havent looked through them, but it seems to me that FO4 was not nearly as bad as 3 and NV by default.



  • arglebargle@lemm.eetoPatient Gamers@sh.itjust.worksFallout 4
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    5 months ago

    I think that is a bit overboard. I modded the hell out of F04 and it still is a brain dead, choices mean nothing, game. It is kind of interesting wandering around and fighting things, but nothing really ever matters and the story progresses the same.

    The second more important thing for this game besides modding, is playing in survival. Anything else is like whats the point.



  • I will not change on this: an official wiki (for example the arch wiki) or other documentation is still the best way to convey exact information. If a user absolutely never wants to use a command line, then they can use Android and a touch interface. Even Microsoft gives directions on how to fix things with a command line. This should be infrequent, but is a necessity for brevity and precision.

    In any case we might as well put that to rest and move on.

    When I have a working example that does at least something we can go from there. The bullet points are helpful, thank you.


  • It is not strange or difficult. I am not expecting them to know what to type, I am expecting to have clear instructions as to exactly what they need to type. Which is really hard to convey with a gui. Administration of a computer and sharing functions is so much faster by copy/paste exactly what you expect them to. It is the easiest, most concise method.

    In any case: lets get back to the task at hand. I will make a simple GUI that creates the credentials file, the mount point file, the automount file, and finally restarts the system daemon.

    I guess it needs to show any errors at that time.

    The user will provide some info that I will gather as it goes along (like SMB credentials) and I guess I will include the ability to simply go on without mounting if the network mount point is not available (in case of laptop).

    There are a few elevations of privileges to sort out, and to keep it simple I will use Kdialog (for the gui presentation) which will make the code very obvious as it is simply bash behind it all.

    After that do you want me to share this with you? I am not sure when I will get it done, but it should be fairly easy. Then I can put it on github I guess.

    Realistically, to make this functional, it should be able to ready your current mount points and allow the user to edit, doing error checking etc. That would be a future phase.


  • There is a reason Digikam can’t rely on the SMB connection that dolphin makes. I do the same with my Music library and make it permanent mount at boot.

    The command line fails hugely on usability, learnability and familiarity.

    No. It EXCELS at usability and learnability. Because it works the same every time. It is shareable, teachable, and precise. GUI’s are sloppy, difficult to explain and tell people what to click on. Difficult for them to explain how to get back to where they were if they get lost.

    Repeatable is not what a GUI is good for.

    I will say it might be nice if there was a pattern that could be reused, for example if a distro wanted to plan for it. Then again, you are connecting to SMB (windows) share, so the importance is fairly low.

    I am looking at a mount now, and it is tempting to make a default file, walk through the questions necessary to create everything, and then execute it. It is only a handful of lines to make the mount point, and then a systemd command to mount with out needing to edit fstab.


  • So somehow they have created and managed SMB sharing in their local environment, but can’t figure this out?

    Simply having a SMB share available is just a simple click in dolphin and then you can bookmark it. Easy enough.

    For a permanent share (like with Digikam expects) takes a few extra steps, but they are not terribly hard.

    I am a bit taken aback with the terms you use: “use some command line or other nerdy hack, with magic words…that shouldnt be necessary in the first place” is over the top annoying. Yes use the command line. That is the easiest way to explain and perform things. Dozens of pictures of clicking things, or a simple direct command that is copy able and repeatable. I will take the latter.

    Why would you call telling you computer what to do a “nerdy hack”? This is not “broken usability”, it is efficient. Why do you have such a negative reaction to using a computer in an easy way?

    I will say it is a few steps to mount at boot, as you will need to add to fstab, create a access file, and so on. Part of that is linux security. I am not sure how that could be wrapped into a gui, but I suppose it would not be too hard to do, with a need to elevate privileges. If you think this is a barrier to entry, would you be interested in writing this gui?