• 5 Posts
  • 21 Comments
Joined 1 year ago
cake
Cake day: July 26th, 2023

help-circle


  • Orac@feddit.nlOPtoVS Code@programming.devLooking for a git history plugin
    link
    fedilink
    English
    arrow-up
    1
    ·
    edit-2
    5 months ago

    I am no git- expert; I mostly just branch and commit, that’s the extent of my knowledge. Can you point me into the direction of some information regarding this (specific commands I could use?)

    And ‘Odd’ is an understatement ;P these files are fairly old (I oldest was made in 1999 and the last version was from 2002) and the client was lucky they found the initial set and the last version on separate backups (floppies !). What we initially did was commit the initial version and then overwrite them with the latest version and commit again. So we now have a git history of the difference between the originals and the revisions. My job is to check if the final version is correct e.i either conform the work specification of the time (report), or any of the revisions (as-built) since then. And then create a comment that can be read by both the operator console and the archive-system. My best guess is someone’s nephew created this program because why anyone would use XML for this is beyond me, although I guess in 1999 this was state-of-the-art? And no one wants to touch that codebase with a 5ft pole, lol. Anyway, the comments are parsed in a specific and precise way.

    EDIT: As for your question about #ACCEPTED. The rules are “simple” each comment should start with either %ATTCHANGE, %REM, %ADD or %NOTE then 2 colons, then the old element (complete) or the ols attribute (seperated) or the note, then again 2 colons and last either #ACCEPTED, #DENIED or #REVIEW. Reveiw is followed by any text explaining why it needs reviewed, and denied and accepted are followed by either “see report xxxxx” or “as-built xxxxx” where xxxx is some reference.


  • They are XML files and changes would be things like added or removed elements or changed attribute values. So e.g.: Version 1:

    [...]
    <Dynamo vendor="Siemens" max-rotation=12>
    [...]
    <Light colour="white">
    [...]
    

    Version 2:

    [...]
    <Dynamo vendor="Siemens" max-rotation=16>
    [...]
    

    The comments would look like:

    [...]
    <!-- %ATTCHANGE :: max-rotation=12 :: #ACCEPTED see report 12.24/2 -->
    <Dynamo vendor="Siemens" max-rotation=16>
    [...]
    <!-- %REM :: <Light colour="white"> :: #ACCEPTED see report 12.24/4 -->
    [...]
    

    I make the changes while going through the report (hardcopy only) which is basically an engineering report that outlines changes made to a factory (12.24/4 means chapter 12, section 24 item 4 which would list the old and new device/machine or the changes made etc. in a technical manner). It’s manual work, which is fine (I get paid by the hour). Just want it to be a bit more streamlined.


  • Orac@feddit.nlOPtoVS Code@programming.devLooking for a git history plugin
    link
    fedilink
    English
    arrow-up
    2
    ·
    edit-2
    5 months ago

    I tried that, it has different ways of looking at a diff/history, but none where you can just have it open while still working (unless you do split I suppose, but that is not practical as I need to go through hundreds of files. But perhaps it helps if I describe the problem. Maybe there is another solution I am not thinking of: I have almost 2000 files that all have had 1 change (so there is an initial commit and a recent version). What I need to do is go through each file and add the changes made to the file as a comment. So what I would like is: When I open a file, see immediately which lines were changed., and then be able to see what it was that changed so I can either copy/paste or retype it as a comment. Each change I review and I either add a #ACCEPTED, #DENIED or a #REVIEW to the comment as well.

    So having to switch to different views and opening/closing tabs for each file is something I would like to avoid. Just open the file, see what I need, type and close the file again.










  • I am very happy with it. I did switch from Kubuntu to Manjaro KDE, but that was not because of the GPU. The only thing that bothers me is that the fans can be noisy during some games at high load. But during everyday desktop use the fans are idle since its passive cooling capabilities are good (I have one from Powercolor, so any other brand may be different on this point). For me, the temp stays at <40°C for normal desktop use. I haven’t seen it go over 83 during gaming. You can adjust the fan curve with Corectl and even overclock it (I haven’t) if you want; but everything else just works without additional drivers/software. Now, I don’t play heavy fps games, but the games I do play are lag/stutter free. My most taxing game atm is Cities Skylines 2 and I get a solid 60fps with that and my heavily modded Minecraft runs smooth as butter. All in all, I think the card gives excellent value for money.








  • I debated whether or not I should respond to your reply for a few hours now. I just want to point out that everyone is different and have their own circumstances. I recognise you do not know me and know nothing of my circumstances. Mainly because I didn’t divulge them because I thought they be irrelevant. But I have a disability which makes it difficult for me to go outside and impossible to travel. My life takes place 90% at home. And while I am mobile and can do other things besides sitting behind a computer, it is my main “escape” from my situation (besides tv, books, etc.) And I am also ashamed to admit I do not have a “shitty wage job” but a “shitty disability income”.