Ok, we all love this Mac OSX look, its a fact - we been skinning and emulating it since day one
. We got
a lot of talented artists and developers that has done realizations of the OSX user-interface to the PC platform, and
we got thousands of users that uses their highly appreciated work :own: . It's a perfect world this far - but, there's a big problem:
There is no structure, logic, collaboration in all these hundreds projects out there - its a jungle. And this is a problem
for both artists/developers and users. ![]()
:nuts: PROBLEM 1:
We got 1 guy making a skin for an app, and at the same time another guy on the
same app - in parallell. They release their masterpieces in two different forums (of
the 30 osx forums out on the internet). This is bad because not all the users will get
the opportunity to try the 2 different projects because the are released in two different
places. Ok, some users are lucky to be members/visitors of both those forums so they
will be aware of the 2 releases - but for those who are not...
:smartass: SOLUTION 1:
Wouldnt it be great to have ONE main forum that the other 29 relies on? I mean we could
have 1 forum that references everything on the subforums (where files are hosted). And the
subforums would report to the main forum as soon as a project is released. Well this is something
like were having here right now in this forum - but it needs a better structure and architecture.
The "Release/distribution"-step must be better.
:nuts: PROBLEM 2:
In problem 1 we saw to different projects working on the same "realization" (e.g making a skin for trillian)
and realising it independently. Another problem with that is that 1. how will the user know wich one is the best,
2. what if one the "realization" is better than the other. 3. What if both projects have different "good" features?
:smartass: SOLUTION 2:
The developers/Artists should collaborate och work together on their project and possibly merge the 2 projects
into 1. This will save time and will result in a better product becasuse the best of both projects will be delivered.
This will also eliminate the problem with "development branching" (i.e 2 projects start at the same spot, but walking
theire own way (in parallel), implementing different features). For example. We got this guy "OSX_Lover" that makes
this incredible skin for Trillian. Its awesame because nobody has done it before. But users realize it has some bugs
or lack of features. Now 2 different guys make their own modifications based on the first skin. The new skins
will be called "MagicT's Trillian skin (based on OSX-lovers)" and "AquaBoys skin for trillian (with permission from OSX-lover)".
this is not good, not good at all. We should collaborate and make "OSX_lovers skin v1.3 (modified buy MagicT and AquaBoy)" instead.
:nuts: PROBLEM 3:
In the solution above we talked about modifications and updates of existing stuff (e.g a skin for Trillian). We all know
this happens all the time: One good developer makes the first version, and later maybe makes an update, but then gets bored
of that application and starts making a skin for another application (in another project), but thats okay because theres another
entuthiastic developer that has will and time to continue on the "Trillian skin project". The fact is : During the lifetime of a skin
there're many modifications and updates made. The problem is nobody know wich one is the latest. Only the ones
that visits everyday the 30 forums will know. An example: I go on hollidays for 1 month and when i get back i see
2 new different uppdates of the trillian skin, Great! But i don't know wich one is the lates because i dont see any
version number only the name is the same, but that wont help.
:smartass: SOLUTION 3:
We need to version each release so that the user will know wich one is the latest, but also helps
for a more concrete referencing of projects.
These ways are very common to every artist/developer that has worked on a professional project before
and its a good practice to work like this. We should take this into our "OSX-PC community".
Finally the conclusion is:
Developers: Will save time. and have the possibility the deliver the best result.
Users: Will not get confused and will always have the best.
Aqua-Soft Forums