[Cuis-dev] Addition of buttons to the Code File Browser class list menu

[Victor Gabriel Fierro]

Hi Juan!
I'm glad to see that you liked it! Thanks!

El vie, 1 nov 2024 17:29, Juan Vuletich <juan at cuis.st> escribió:

> On 10/30/2024 4:20 PM, Victor Gabriel Fierro via Cuis-dev wrote:
>
> Hello again!
>
> I'm sorry to bother you one more time, but I realized some mistakes in the
> changes I sent in the previous email. The problem is in the functionality
> of opening the Change List Window from the Code File Browser. I realized
> three problems in the earlier version:
>
>    1. Responsibilities were assigned incorrectly. I made the Code File
>    have the responsibility of opening the Change List Window, which makes no
>    sense.
>    2. It didn't take into account that the original file could be moved
>    or removed.
>    3. It didn't take into account that the original file could be
>    modified.
>
> When I realized these mistakes I started making a new version of the
> functionality to replace the previous one, but I could only solve the first
> and second problems (At least to some degree, more on that later). Firstly,
> in the new version the Code File Browser Window has the responsibility to
> open the Change List Window, which I think is better. Secondly, now the
> function checks whether the file still exists before doing anything, and if
> it doesn't then just throws a Pop Up that lets the user acknowledge the
> situation.
> The thing I couldn't do is solve the third problem, the new code ignores
> completely whether the file has been modified or not. Also, although
> technically the second problem is "solved", I don't find it satisfactory
> that if you remove the file then you can't browse the changes anymore, even
> though they are all there in the Code File browser! I just couldn't figure
> out a way to convert the information held by the Code File into a Change
> List (Actually I played around with the idea of storing the Change List
> that is created in the initialization of Code File to scan the file. This
> would solve the problems better but I don't really like the idea of storing
> a whole Change List 'just in case' and also that solution comes with a
> bunch of other problems, but I have an implementation of it if you are
> interested).
> Please let me know what you think of this new version, and share with me
> any comments or suggestions.
> Thank you very much!
>
> El lun, 28 oct 2024 a la(s) 4:06 p.m., Victor Gabriel Fierro (
> vigabf at gmail.com) escribió:
>
>> Hello again!
>>
>> I'm Gabriel, and I have a new contribution to make to Cuis. Last week I
>> sent changes to the Code File Browser to show classes hierarchically. After
>> playing with the new version a bit I realized that the Code File Browser
>> lacked the buttons to alternate between alphabetical and hierarchical class
>> organization when you right clicked on them, so I added them. While doing
>> so I noticed that it also lacked a button to open a Change List Window to
>> browse through the changes of the code of the file, so I added too and
>> implemented the functionality.
>> I hope that you find these additions useful!
>> Have a nice day!
>>
>
> Hi Gabriel,
>
> I actually liked more the first version:
> 1. It will have the responsibility in any case, as that's where the user
> opens the menu to do it. It shouldn't have knowledge on how to do it. But
> it is ok to start the action from there IMO.
> 2. These are developers tools. If the user moves or removes the file, it's
> their fault, and they'll get a reasonable debugger!
> 3. Same as before. Don't worry. A programmer working with code files
> should know what they are doing. Crashing the system of deleting the code
> would not be OK. Opening a debugger that explains the problem is totally OK.
>
> So, I integrated the first version.
>
> Thanks!
>
> --
> Juan Vuletichcuis.stgithub.com/jvuletichresearchgate.net/profile/Juan-Vuletichindependent.academia.edu/JuanVuletichpatents.justia.com/inventor/juan-manuel-vuletichlinkedin.com/in/juan-vuletich-75611b3twitter.com/JuanVuletich
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.cuis.st/mailman/archives/cuis-dev/attachments/20241102/1bd2b645/attachment.htm>