The skinning model now is based around callbacks. As you look through the skin that I've provided, you'll see various methods such as onOpen, onReady, onLoad, etc. As the Shadowbox code is executing, it calls these methods on the skin class to let it know what to do.
The skin class also has a bunch of private methods that are called by the public interface to accomplish the things it needs to do. Combined with the CSS file (and of course the images it points to) this constitutes a Shadowbox skin.
The way the skin is set up now you can easily modify any public properties or methods, providing they don't use the underlying private API. For example, if you want to modify the default markup used by the skin, you could simply do something like this:
However, you obviously don't have access to the private API. I did this because the private implementation could change from skin to skin as CSS and markup changes, and I didn't think that the API would still be relevant to other skins. However, if you feel this is too restrictive, we could discuss changes and possibly exposing some of the interface to make it easier to tweak.
Inside that file, you would do something like this:
Shadowbox.skin.markup = ''; // your markup goes here
This would then override the default skin. However, this method could be rather inefficient since you first load the original skin and then override it. A much cleaner method would be to just download the source code and modify the Shadowbox.skin class you find at the bottom of shadowbox.js. Then, recompile the code and away you go. Shadowbox uses Ruby for its build tasks, so you just cd into your source directory and do:
This posting may be of use to use that describes how to apply a Shadowbox Theme.
When posting your markup here on the forum follow these simple steps:
0. Login and paste your markup into the Message Box.
1. Mouse select the markup you just pasted.
2. Press the More Button from the Message Box Toolbar.
3. Select Raw text from the drop down menu. DONE!
If I don't respond to your POST, it's your inability to provide your markup correctly.
Check out a few DEMOS I made that are here in this forum.