http://wiki.kyanite-studios.org/ 2011-09-29T19:52:15+02:00 http://wiki.kyanite-studios.org/ http://wiki.kyanite-studios.org/lib/images/favicon.ico text/html 2011-09-28T01:37:49+02:00 http://wiki.kyanite-studios.org/doku.php?id=herethefirst_title&rev=1317166669&do=diff Hi to all on this site its content text/html 2010-05-15T14:44:48+02:00 http://wiki.kyanite-studios.org/doku.php?id=metamodel:definitions&rev=1273927488&do=diff First of all, we must define model and metamodel. A model is a representation designed to show the main object or workings of an object. A metamodel is an explicit description (elements, constructs an rules) of how a model is built. A metamodel is usually a strict rule set. text/html 2010-05-08T00:22:12+02:00 http://wiki.kyanite-studios.org/doku.php?id=ca:dev:windows_support&rev=1273270932&do=diff So you want to help on getting ca to run on windows os? Yay, we are looking for developers who can help with that. As CA is python based, it should be possible to run it on windows, but it means you need to sort out how to install all the python dependencies, plus the non-windows dependencies (like gtk, crystalspace, csexternal). text/html 2010-02-16T17:40:22+02:00 http://wiki.kyanite-studios.org/doku.php?id=ca:discussion:component_system&rev=1266338422&do=diff Discussion about component system, both ideal and pythonic. Note the discussion here is not about how to apply such a component system to CA. Components Also, in a general investigation about actions/components, i identified a data driven component can allow all the following (usually component systems implement some subset): text/html 2010-02-16T17:18:17+02:00 http://wiki.kyanite-studios.org/doku.php?id=ca:discussion:currentproblems&rev=1266337097&do=diff This is a page for links or small discussions for current pressuring issues in development. Plugin System We need a plugin system which can handle dependencies among plugins, as well as a browser that allows to see the plugins more organized, probably in a section tree. text/html 2010-02-16T17:11:37+02:00 http://wiki.kyanite-studios.org/doku.php?id=ca:discussion:random_stuff&rev=1266336697&do=diff This page is for discussions not yet worthy of their own full page, or just throwing in your wild ideas. Feel free to move a discussion from here to a separate discussion listed under Discussions if you think it's the moment. Draft Invariants * Every element has to be referenced through the VFS text/html 2010-02-16T16:53:09+02:00 http://wiki.kyanite-studios.org/doku.php?id=ca:dev:developer_protocol&rev=1266335589&do=diff The idea with this document is to provide some guidelines about how to get your changes into ca or any of our maintained subsystems. * Focus on solutions instead of problems. * Ask around before making architecture decisions. * Ask around when you need info. * Follow the coding style guidelines. * Use pylint to check code quality. * Always set proper comments for your changes, both in code and on the wiki. * Document classes and functions properly for epydoc. * Always document… text/html 2010-02-16T13:08:43+02:00 http://wiki.kyanite-studios.org/doku.php?id=caf:vision&rev=1266322123&do=diff (en Español más abajo en esta página - in Spanish down in this page) Intro Development of CA started with the goal of creating a “perfect editor for CS”, as well as developing a new set of graphical modeling tools. Architecture decisions have led to the development of a plug-in based core that is pretty much independent from the underlying engine. We have also already developed a number of (prototype) tools which are generic enough that they can be plugged into any python data-graph (a… text/html 2010-02-16T13:00:16+02:00 http://wiki.kyanite-studios.org/doku.php?id=caf:manual:plugins&rev=1266321616&do=diff What is a plugin for CAF ? Plugins are basically a class which replies to a set of messages (methods). Each class has to implement the corresponding interface. Also, for each interface, a hook (the moment at which it's invoked) is defined in the code.