From: WongCK <won...@ya...> - 2024-08-18 10:43:01
|
Pretty sad to see you guys tearing it here. Hanging on to some specs that are 40 years old, how can we progress ?Comparing to NAES and TOS AES.... why? You should be comparing to something more modern say... Windoze/Linux GUI.Yeah aim for the sky and see how high we can go.Like MyAES has some stuff similar to Windoze GUI (ala mouse over the task bar shows a small window of the application running... blew my mind off or am I just dreaming). Keep making XaAES work with old programs, that's a priority as we have not many development like work processor, spreadsheet and email clients.May be some users are still using LDW Power or Pheonix instead of Sheets. IDK. New programs... please go on to the new standard of XaAES.What new standard you ask.... chicken and egg...it will not happen if you guys keep on saying 40 year old standard is the standard.New programs should not just implement stuff... like 3 arrows.... but bring to the group for discussion. Hey... the 3 arrows means so and so can we do something in AES ? I know the fun that we all had the last 40 years when we were developing. That was the old cowboy town days where every maverick do whatever he wants as TOS only running 1 application (ok, i am not counting the ACC) and you can have your own nifty GUI doing your own widget and stuff. But now in multitasking where several applications are running, you should try to not show off your 3 arrows or $ or %% or whatever char.As a user, I want it to look similar. And of course wants to have newer looking and cleverer GUI. May be the whole rework job is needed, not just a band-aid. my 2 cents.... On Saturday, 17 August 2024 at 09:55:32 pm SGT, Lon Pursell <not...@gi...> wrote: Here's my take. The original code inserted the indicator into the string exactly like atari's code does with the exception it was off by 1. This could of been fixed with an extremely minimal fix to attach_menu() and detach_menu(). That's what I was expecting. However, an executive decision was made to completely rework it so the indicator was superimposed on top of the menu entry with the "assumption we might need an image in the future". This makes it harder to comply with Atari's rules, plus more overhead, two vdi calls for an assumption that isn't proven. This fundamental change should of been discussed before it was implemented. There would of been pushback from me and possibly others. i'm not mad at anyone, I just wish there was more discussion and communication before big changes are made. — Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you are subscribed to this thread.Message ID: <freemint/freemint/pull/369/c22...@gi...> |