OS/2, eCS & ArcaOS - Technical > Graphics and Window Design
Dynamic Icons
David Graser:
The second
David Graser:
I am working on "clear glass Portals." What is interesting is that you can use both. Say you like the blue portals for the desktop, but the clear glass portals for the opened portals with the white background or vice versa. I am also adding to the Blue Portals. It is going to be slower going. Work is getting to be more demanding.
David
David Graser:
--- Quote from: Dave Yeo on January 07, 2018, 08:27:12 am ---Looks good.
About performance, I think the problem is actually losing address space in the lower arena causing programs to fail quicker. This could be tested with Theseus by measuring memory with and without the dynamic icons.
--- End quote ---
Hi Dave
Being a non programmer, I may have thought this out to the wrong conclusion. This would would be true for the more portals one opens. Does ArcaOS load all the portals (folders) into memory on boot-up or does it load into memory only those portals that are open? If the latter is true, then one would probably have to open many portals before the lower memory is exhausted. There again, it may depend on how much memory one has installed on their computer. One can see in some of my uploaded pics that I have quite a few portals open without any degradation. Is my non programming analysis wrong?
Dave Yeo:
I'm not sure how the WPS allocates the memory, whether as icons are opened or all at once. Hopefully as icons are opened and it is released when the icons are closed.
About the memory, or at least my imperfect understanding. On OS/2 systems before 4.5 (earlier with Warp Server), processes only get 512 MBs of shared address space, minus whatever DLLs are loaded and memory they use. eg Right now on a freshly booted system with SeaMonkey running, I seem to have 230 MBs of free lower shared memory. Making it even more complex is that the memory can be fragmented, program requests a bunch of 10MB chunks and then frees up every second one leaving a bunch of 10MB holes. Another program wants to allocate a 20MB chunk and fails even though there is lots of free memory.
Latest versions of OS/2 ca also use high memory if compiled to. So things like Mozilla mostly allocate high memory. Unluckily some of the OS/2 API (old 16 bit stuff) can only access low memory so a big memory hog like Firefox mostly uses high memory and even the DLLs themselves can be loaded high but still needs some low memory and when high memory gets full/fragmented falls back on low memory.
And understand we're talking virtual memory, not physical memory.
My description above might not be quite right but that is the general idea, namely that low memory is a scarce resource on OS/2.
David Graser:
This is a preview of the Clear folder portals. I now refer to my desktop as ArcaOS Dimensions. By uploading, I can see what they look like on a different bigger screen computer.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version