Aleph development without an aleph...

  • As I wait for the storms and tragedies effect our hardworking hosts, I am wondering... Can I get started before the arrival of my Aleph? Or is it necessary?

  • sure you can. study:
    particularly bees, modules, operators, the parameter scaling network, and then check out the tutorials. in tutorial 4 galapagoose included some visual flow charts. you'll get a sense of the data flow and you could even practice drawing out application ideas on paper if you thought it was necessary.

  • if you're interested in the c coding side of things i recommend checking out the github. utils/beekeep is a linux compilation layer that runs the BEES program and converts .scn files to and from .json for slightly easier manipulation by humans.

    could use some help with both of these. utils/avr32_sim layer is meant to emulate the low-level hardware routines (calling application event handlers in response to timers, UI changes, etc) - it is mostly incomplete, so the bees emulation isn't good for much except holding scene data.

    utils/beekeep/bees_schema.json is a proposal of a better, more compact and hierarchal, text-based data layout for scenes. reading it will give a good idea of how scenes are stored and manipulated.

  • The json thing sounds extra good!

    Do you guys use an IDE for developing in? I've been poking around using sublime text but I get confused navigating around all the source files.

  • Eclipse may be an answer for you. I swap back and forth between Eclipse, Netbeans and vim myself...

  • I find the JetBrains stuff to be pretty awesome. I use PHPStorm at work. AppCode might be sweet for C stuff.

  • i use emacs.

    brian uses sublime text.

    darren uses eclipse ( i think ).

    code::blocks is another popular one.

    all have IDE-ish facilities (building, source tagging, SCM integration) - pick your poison!