You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As stated elsewhere, the current accumulation of code—in spite of the code being high quality—is a monolithic mess.
The concept is to restructure code into modular elements that can ultimately be separated, turning Adium into a thin API for a universal/shared OS messaging layer.
In order to do this, it would be helpful to have a diagrammatic view of how things are currently organized.
Research tools for analyzing dependency graphs for Objective C
Create one or more diagrams representing current code organization and dependency relations.
Meanwhile, I will work on creating a corresponding future diagram representing what "universal/shared OS messaging layer" means.
The text was updated successfully, but these errors were encountered:
As stated elsewhere, the current accumulation of code—in spite of the code being high quality—is a monolithic mess.
The concept is to restructure code into modular elements that can ultimately be separated, turning Adium into a thin API for a universal/shared OS messaging layer.
In order to do this, it would be helpful to have a diagrammatic view of how things are currently organized.
Meanwhile, I will work on creating a corresponding future diagram representing what "universal/shared OS messaging layer" means.
The text was updated successfully, but these errors were encountered: