Video Notes: HiDef (1280x720), switch to full screen for best effect. Low bandwidth users should probably switch HD off by clicking the button which appears when you play it. We've been working on improving the cyn.in buildout for the upcoming version. One of the things we've added is the collective.omelette recipe. Leaving the funny name aside, (it's a pun intended on the fact that pretty much whatever you do in a buildout is based upon pre-defined "recipe"s and that this one is really special in that it mashes up all the code in all available products, projects and everything that's there in your buildout together into a single linked folder chain. And if you didn't get the pun, ignore it, it'd not important for the rest of the stuff here.) Let's start with the usual alert:
Warning !Warning! Danger, Will Robinson! Geek Developer alert! This video and blog post is for the software developer audience. And probably only of interest to people who think that building out cyn.in from source is pretty cool, and would appreciate another productivity tip that would greatly enhance their way of working with cyn.in. Everybody else will probably not make much sense of this, but is of course welcome to try, and fit in. ;) Ok. So here's my list of assumptions:
- You got cyn.in working from buildout
- You're surprised at the complexity of the codebase - all of cyn.in stuff exists in the src folder, but when you go into parts, and eggs, there's just too much stuff there to really comprehend and figuring out which code goes where, is really painful. This recipe is for you.
- You're getting a hang of things. You understand that most of the plone codebase is concentrated around the CMFPlone product, and then you look for plone's kss and you can't find it, for example. This recipe is for you!
- You'd actually like to use a GUI IDE tool to work with, rather than just using Notepad++, gedit, vi, or whatever else it is that you do use for that sort of thing. Something that will give you intellisense for autofilling function names, showing you function arguments, and doing reference lookup jumps into outside code files, when the need arises. This recipe is for you, also.