http://wiki.kyanite-studios.org/ 2010-02-24T06:33:41+01:00 http://wiki.kyanite-studios.org/ http://wiki.kyanite-studios.org/lib/images/favicon.ico text/html 2010-02-16T17:40:22+01: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+01: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+01: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+01: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+01: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+01: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. text/html 2010-02-16T12:55:53+01:00 http://wiki.kyanite-studios.org/doku.php?id=caf:discussions:startup_review&rev=1266321353&do=diff * Go runner * Initialize the service manager * Load caf file * Look for services folder * Load the services folder on the services view (the service manager) + (Declare the service dependencies on the service class) * Services view instantiates taking care of dependencies, if some dependency is not maintained, then given service cannot be instantiated <-- CORE services text/html 2010-02-16T12:50:48+01:00 http://wiki.kyanite-studios.org/doku.php?id=caf:discussions:services&rev=1266321048&do=diff This wiki page is for proposing changes to caf. Services The goal is : * To have the configuration of a service as a model tree ; * To have a way to store and restore the state of a service using a saved caf file. The Service Manager The service Manager is now a Datasource.