My current hang-up seems simple. I want to allow for people to use different skinning styles or methodologies when using Clash. The three main ones are:
- Single file, where all of the widget images are on a single bitmap, and the user specifies the clipRect for each widget (currently supported);
- Directory-based, where each widget (and each slice within a widget) are on separate bitmaps, and their association is determined by their relative path from a parent directory;
- Mixed, where each widget's associated bitmaps are located via relative paths, but the slices of the widget are within the same file.
The issue I am having is that I would like to have the latter two skinning styles be able to conform to the current .clash file hierarchy, but it is highly unlikely that I will be able to do so. This would lead to a decent amount of refactoring within the Clash data structures so that I can hide the inconsistencies between the types.
My current hang-up seems simple. I want to allow for people to use different skinning styles or methodologies when using Clash. The three main ones are:
The issue I am having is that I would like to have the latter two skinning styles be able to conform to the current .clash file hierarchy, but it is highly unlikely that I will be able to do so. This would lead to a decent amount of refactoring within the Clash data structures so that I can hide the inconsistencies between the types.