• Updated 2023-07-12: Hello, Guest! Welcome back, and be sure to check out this follow-up post about our outage a week or so ago.

What do you think of developing a scheme to theme converter?

What do you think of developing a scheme to theme converter?

  • It's definitely worth it.

    Votes: 5 45.5%
  • It's probably worth it.

    Votes: 2 18.2%
  • I don't know if it's worth it or not.

    Votes: 3 27.3%
  • It's probably not worth it.

    Votes: 0 0.0%
  • It's definitely not worth it.

    Votes: 1 9.1%

  • Total voters
    11

Dennis Nedry

Well-known member
I have ALWAYS wanted this converter ever since the demo from Apple that converted Kaleidoscope schemes to Mac OS 8.5+ themes. It existed but was never released.

I have extensive knowledge of Mac OS 8.5 themes and I am confident that this converter is a reasonable undertaking. There are some features of schemes that aren't available to themes, such as alpha-transparent menus and custom cursors, but other than that, themes are capable of everything, if not more, than schemes.

This is basically what would need to be done:

  • Convert 'cicn' resources to 'pxm#' resources. These are both raw bitmap data and can be converted DIRECTLY, even retaining color tables (if used). Totally lossless. However, 'cicn' images would have to be trimmed into multiple pxm# resources.
  • Interpret layout data from the scheme and build layo resources for the theme. The 'layo's reference the 'pxm#'s and tell them how to act and where to go. (For example, put 'pxm#' ID 128 at (t,l,b,r) and give it close box functionality.)
  • Icons: copy over directly.
  • Patterns / colors: copy over with minimal modification. (convert colors to different resource type)


I do know how to do these things:

  • Convert the image/layout/color data in C / C++ code


I don't know how to do these things:

  • Build an app that runs on OS 9, using MPW or CodeWarrior or something. (I really don't want to use RealBasic!)
  • Access resource data in an easy way
  • I am used to embedded C programming, very little experience with using GUIs (ironically). I despise object-oriented programming, I apologize.


I wanted to gauge if people are interested in this converter, because if it's only me that would use it, I couldn't really justify the development. Converting the cicns to multiple pxm#s and building layos will not be a 1-day project. This is to see if anyone else would like to run Kaleidoscope schemes without having Kaleidoscope installed and constantly crashing and reminding you about the shareware fee.

 

MacJunky

Well-known member
Well, Schemes would still be useful for computers that do not have appearance manager installed so there would still be /some/ demand for Kaleidoscope.

 

Dennis Nedry

Well-known member
I doubt there are any more schemes being made, one could simply download the entire archive and convert them all. I wouldn't want to do so if it made somebody upset or lost them money though.

Maybe the Kaleidoscope people would be interested in this project, or at least give permission for old-times sake. I'm not sure if we need permission, I guess, but it wouldn't hurt.

I actually can't believe it never happened, it's not an impossible converter to make. It definitely takes some interest and 2-3 knowledgeable determined people working together. If somebody can put together some application code that gives me resource data in and resource data out, I can make all of the conversions in C.

 

Dennis Nedry

Well-known member
Don't get me wrong though, I really like Kaleidoscope, it is probably one of my very favorite Mac add-ons. It is a much more smooth and finished product than Apple's built-in theme system. But Apple's is more stable. I just think it would be interesting to have both options, neither really could replace each other.

 
Top