mirror/aseprite
1
0
Fork 0
mirror of https://github.com/aseprite/aseprite.git synced 2024-12-26 00:19:13 +00:00
Code Issues Packages Projects Releases Wiki Activity
fd445e01f9
aseprite/src/gen
History
David Capello f6be0c3be6 Replace ISettings with Preferences 
Changes:
* Move FreehandAlgorithm/InkType/RotationAlgorithm/SelectionMode to
  app::tools namespace
* Removed ISettings, IToolSettings, IBrushSettings, ISelectionSettings,
  and IColorSwatchesStore (and implementations from UISettingsImpl)
* Added app::tools::PreferenceGlue to do some adjustments that
  UIToolSettingsImpl was doing
* Remove signals from App related to brush size/angle changes, and current
  tool change (there events can be observed directly from Preferences)
* Remove ColorBar::FgColor/BgColor, these options can be observed from
  Preferences::colorBar.fg/bgColor
2015-05-18 16:53:25 -03:00
..
CMakeLists.txt Replaced app::skin::ThemeColor with app::gen::SkinTheme::Colors 2015-02-15 15:29:16 -03:00
common.h Use std:: when necessary, and std::numeric_limits instead of INT_MAX 2015-03-04 21:35:11 -03:00
gen.cpp Remove implicit SharedPtr conversion to T* 2015-04-02 20:42:43 -03:00
LICENSE.txt
pref_types.cpp Replace ISettings with Preferences 2015-05-18 16:53:25 -03:00
pref_types.h Add setting/preference classes/enums generator 2014-12-14 20:19:31 -03:00
README.md
skin_class.cpp Fix app::gen::SkinFile class generator for gcc compiler 2015-03-04 22:50:32 -03:00
skin_class.h Replaced app::skin::ThemeColor with app::gen::SkinTheme::Colors 2015-02-15 15:29:16 -03:00
ui_class.cpp Move logic to import sprite sheet inside ImportSpriteSheetCommand::onExecute 2015-03-19 16:20:33 -03:00
ui_class.h

README.md

Aseprite Code Generator

Copyright (C) 2014 David Capello

Distributed under MIT license

This utility generates source code from XML files. Its aim is to convert XML files (dynamic data) to C++ files (static structures) that can be checked in compile-time. There are three areas of interest:

  1. To create ui::Widgets subclasses from data/widgets/*.xml files. In this way we can create wrappers that can access to each XML file directly in a easier way (e.g. one member for each widget with an id parameter on it).
  2. To create configuration wrappers from a special config-metadata.xml file (so we can replace get/set_config_int/bool/string() function calls). There is an ongoing cfg module to replace the whole reading/writing operations of user's settings/preferences.
  3. To create a wrapper class for theme data access. From data/skins/default/ we can create a C++ class with a member function to access each theme slice, color, style, etc.