10 June 2021, 02:43 | #1321 |
Registered User
Join Date: Sep 2018
Location: Canada
Posts: 79
|
@ OS 3.2 devs and team members
Thank You, Thank You, Thank You !!! |
10 June 2021, 06:49 | #1322 |
Registered User
Join Date: Oct 2012
Location: Germany
Posts: 585
|
|
10 June 2021, 14:12 | #1323 |
Registered User
Join Date: Jun 2009
Location: Dublin, then Glasgow
Posts: 6,334
|
|
10 June 2021, 14:24 | #1324 | |
Registered User
Join Date: Aug 2010
Location: Germany
Posts: 532
|
Quote:
Personally, I would like to keep the existing APIs in play as they are. The exec.library architecture and its APIs are powerful and restrained, for lack of a better word. AmigaOS4 needed to extend them, with the library function call mechanism being the interfaces. They are more than a collection of function pointers because calling the functions implicitly passes the interface address itself to the respective function. This reproduces how the Amiga 68k ABI works with its register sets and the role of register A6, only using 'C' syntax. If I remember correctly, the interface approach reuses functionality which already exists in the GNU 'C' compiler. While this could work for the 68k platform, too, there's the problem that the code which GCC generates is not as well-integrated and suited for system programming as the code produced by SAS/C out of the box. This could be changed, but who knows in which time frame. Would be supremely cool if it were possible! There's also the question of how to provide interfaces for 68k assembly language use (could look different, might require macros), and whether or not the interface functions would support parameters in registers. My guess is that all parameters would be passed on the stack. Which has its drawbacks Just look at intuition.library before V45. The Green Hills 'C' compiler producing great, optimized code could not compensate for the multitude of "let's push those registers on the stack... call the function... that function pulls them off the stack and puts them back in the the same registers" dance steps. When we rebuilt intuition.library with SAS/C and registerized parameters enabled in the code generation option intuition.library became much, much shorter, and not just through function inlining. As I mentioned, there is still time to discuss alternative approaches until we settle on one. It might be good if only a small change would be required and the architecture and design of the exec.library API could be preserved. It's so neat Last edited by Olaf Barthel; 10 June 2021 at 14:37. |
|
10 June 2021, 23:55 | #1325 |
Zone Friend
Join Date: May 2006
Location: France
Posts: 1,801
|
@Olsen
See how fast games made by Abyss are using GCC I’d say it’s good enough maybe better than SAS/C for code optimization. That said it brings other problem’s like regression testing effort. |
11 June 2021, 11:02 | #1326 |
Registered User
Join Date: May 2020
Location: Surrey / UK
Posts: 111
|
I'm loving 3.2, so thanks guys. Also enjoying following the weekly streams which shows how much work and love has gone into the new OS.
I'm not a hardcore developer deep in the technical weeds, but I do enjoy tinkering, and I'm a graphic designer by trade, so like a nice looking Workbench. My main request for AmigaOS would be updates to IconEdit and Palette Prefs. The current IconEdit only understands legacy icons and 4 colours. It would be great to have it updated to support editing the various kinds of icons that can now be found on a typical system, as well as acknowledging larger colour palettes. Basically do for IconEdit what you did for TextEdit. I'd also love an update to the Palette Preference app. So it can show more than only 8 colours, and has built-in FullPalette-type palette locking. I use FullPalette as I have a nice 16 colour scheme I have developed and it lets me design my wb as I like. It mostly works, but not always. It would be great if AmigaOS would let users define a larger palette and solidly lock the Workbench colours if they want to. Last edited by Ulysses13; 11 June 2021 at 12:36. |
11 June 2021, 16:11 | #1327 | |
Camilla, AmigaOS Dev.
Join Date: Mar 2020
Location: Frederiksberg
Posts: 327
|
Quote:
Mind you it is still early days |
|
11 June 2021, 16:13 | #1328 |
Registered User
Join Date: May 2020
Location: Surrey / UK
Posts: 111
|
OMG yes. I love you.
Looking forward to that. |
11 June 2021, 16:22 | #1329 |
Registered User
Join Date: Jun 2009
Location: Dublin, then Glasgow
Posts: 6,334
|
|
11 June 2021, 16:33 | #1330 |
Camilla, AmigaOS Dev.
Join Date: Mar 2020
Location: Frederiksberg
Posts: 327
|
My current projects are:
Last edited by boemann; 11 June 2021 at 19:49. |
11 June 2021, 16:41 | #1331 |
Registered User
Join Date: May 2020
Location: Surrey / UK
Posts: 111
|
No problem, we're good at waiting for stuff round here!
|
11 June 2021, 16:44 | #1332 |
Inviyya Dude!
Join Date: Sep 2016
Location: Amiga Island
Posts: 2,770
|
|
11 June 2021, 17:40 | #1333 |
Registered User
Join Date: Apr 2016
Location: .no
Posts: 148
|
|
11 June 2021, 18:17 | #1334 |
Registered User
Join Date: Apr 2005
Location: digital hell, Germany, after 1984, but worse
Posts: 3,365
|
|
11 June 2021, 18:22 | #1335 |
Registered User
Join Date: Apr 2016
Location: .no
Posts: 148
|
|
11 June 2021, 19:02 | #1336 |
Registered User
Join Date: May 2020
Location: Surrey / UK
Posts: 111
|
@boemann How have your team made the current GlowIcons? Do you use an Amiga application or do you make them on the PC/Mac?
If PC/Mac, what's the process of getting them from Photoshop/etc to an Amiga icon? If you make them on the Amiga, what tools do you use? |
11 June 2021, 19:11 | #1337 |
Camilla, AmigaOS Dev.
Join Date: Mar 2020
Location: Frederiksberg
Posts: 327
|
|
11 June 2021, 19:14 | #1338 |
Camilla, AmigaOS Dev.
Join Date: Mar 2020
Location: Frederiksberg
Posts: 327
|
No idea, i'm not involved in glowicons. I personally use the classic icons
|
11 June 2021, 19:22 | #1339 |
Registered User
Join Date: May 2020
Location: Surrey / UK
Posts: 111
|
I prefer the classic ones too, I like the restriction of the limited colours in the design. My ideal would be a locked 16 colour WB palette.
To be honest, I feel like all the other formats that have followed are just like any other colour icons on Windows95/MacOS9 etc. The classic ones have a unique 'Amiganess' to them. I think the limitation is part of that. I'm just curious about it, as clearly a lot of work has gone into them, and also it feels like now they're such a central part of the OS install, that they're the new standard. |
11 June 2021, 19:33 | #1340 |
Camilla, AmigaOS Dev.
Join Date: Mar 2020
Location: Frederiksberg
Posts: 327
|
I wouldn't call them the new standard. Classic or glowicons live side by side. I've contributed a lot of the new classic icons that are included in 3.2, and they are all drawn in the 3.2 IconEdit.
|
Currently Active Users Viewing This Thread: 1 (0 members and 1 guests) | |
Thread Tools | |
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
AmigaOS 3.1.x v 3.9 | steve_mynott | New to Emulation or Amiga scene | 35 | 19 April 2020 06:23 |
AmigaOS 3.9 | PoLoMoTo | support.WinUAE | 8 | 27 August 2011 18:06 |
AmigaOS 3.5 or 3.9 | maddoc666 | support.Apps | 12 | 22 February 2010 08:02 |
AmigaOS | koncool | request.Apps | 6 | 04 June 2003 17:45 |
AmigaOS XL | sturme | New to Emulation or Amiga scene | 4 | 15 January 2002 02:13 |
|
|