[Space-app] Changes to Space & SpaceProcess or just modifications?
Brought to you by:
fusion94
|
From: Morgan A. <mo...@ma...> - 2002-07-29 12:07:05
|
Sorry, I've been really busy lately and haven't gotten to even look
at my copy of Space.app in a long time. Now, I had made some fairly
heavy modifications to my copy (the modified palette window, showing
application icons in the space buttons in the palette window, storing
preferred spaces for apps, etc.) but it was such a mess (as I have
explained to Riley) that I'm really hesitant to use it for more than
just a proof-of-concept.
One of the things I ran into that was a major issue with my
modifications was that I had to do strange hacks to get the
functionality I wanted out of the Space and SpaceProcess classes. I
know atleast one of the major bugs to date (switching spaces too quickly
can move apps to different spaces if they weren't finished
showing/hiding in time) is caused by the current implementations.
I think that the first of my features (except for the modified
palette window, which I believe Riley has already implemented) which I
feel should be implemented is remembering applications' spaces. In
order to implement this, future features, and also to fix the
space-switching bug, I propose that we discuss the current architecture
of the Space and SpaceProcess classes, what really needs to be changed,
what should be kept, and devise a plan of action for reworking them
(whether that means only minor modifications or a large overhaul) and
getting the new versions integrated with the current Space.app
implementation. Does that sound like a good starting point to the rest
of you who would be working on the code? If so I can describe my
observations relating to the functionality of the Space and SpaceProcess
classes.
Morgan Aldridge
---
__ __ __ _ _ _ _
/ |/ |__ _ _ ___ __ __ _ / | |_| |_ _'='_| |___ ___
/ |o | '_|o |o \| | |/ ^ | |o | '_| |o |o | o_|
/_/|_/|__|__|_| \_ |_._|_|__|_/|_|_|_._|_| |_|_._|_ |__/
/__/ mo...@ma... /__/
|