Registration has officially closed since April 16, but we still have some seats available. If you still would like to enroll please contact\u00a0training@rorohiko.com<\/a> as soon as possible to check whether we can still accommodate you.<\/p>\n (Photo courtesy of Mark Niemann-Ross)<\/p><\/div>\n For more info about the Adobe Creative Suite Developer Summit<\/em> click this link:<\/p>\n http:\/\/www.adobe.com\/go\/2010csbuDevSummit\/<\/a><\/p>\n Registration for the Adobe Creative Suite Developer Summit<\/em> is free, but attendance is limited to 200 participants.<\/p>\n Registering for the workshop Getting Started With the InDesign SDK<\/em> costs US$1149.00 per person, and attendance is limited to 12 participants.<\/p>\n Avoid missing out – register early!<\/p>\n Getting up to speed with the InDesign SDK easily takes a newbie between two and six months of non-productive time.<\/p>\n Attending this one-day workshop will slash the time it takes to get up to speed – it will shave at the very least one month from this non-productive lead time.<\/p>\n No doubt you have a good idea what the cost of one developer-month is, so you can easily estimate what value this workshop is to you.<\/p>\n US$1149.00 per person<\/p>\n Check if your profile fits one or more of the following:<\/p>\n If you fit the above description, you really should enroll in our one-day InDesign SDK workshop.<\/p>\n Registration has officially closed, but we still have some seats available. If you still would like to enroll please contact training@rorohiko.com<\/a> as soon as possible to check whether we can still accommodate you.<\/p>\n If you have this nagging feeling the InDesign SDK documentation almost makes sense, but not quite, and some things unexpectedly make no sense at all – rest assured, you’re not alone, and this workshop is for you!<\/p>\n As the InDesign SDK Workshop is only one day long, and the InDesign SDK is massive, it is impossible to cover even the basics of the InDesign SDK.<\/p>\n For maximum effect, we’ve instead compiled a list of what we found to be the most important stumbling blocks for experienced and beginning InDesign Plug-In developers alike. The aim of the workshop is to help a developer blaze a path into the SDK, towards early productivity.<\/p>\n The InDesign SDK hinges on a number of fairly modern, advanced programming techniques.<\/p>\n Without a thorough understanding of these techniques, an InDesign plug-in developer will often be forced to blindly copy boilerplate code without grasping the mechanisms behind it, which often leads to baffling and hard-to-diagnose bugs and strange behavior.<\/p>\n This issue especially affects C programmers who have been thrown in at the deep end and are forced to use C++ without having had the time to find out how C and C++ are different.<\/p>\n Even though C++ originated in C, it should be approached as a totally different language, and using C++ with a C mindset makes the developer miss out on a number of highly efficient programming techniques.<\/p>\n Examples of concepts one needs to master are: smart pointers, abstract classes, string classes, memory management, reference counting, references vs. pointers, avoiding unwanted dependencies, templates, STL, the boost library.<\/p>\n Another key pillar of the InDesign SDK are a number of patterns – generic programming approaches that help breaking up a complex program into smaller, reusable elements.<\/p>\n Example patterns applicable to the InDesign SDK are: factories and factory methods, singleton, adapter, fa\u00e7ade, command, iterator, observer,… Having a good basic understanding of these patterns helps making the InDesign SDK documentation much easier to understand.<\/p>\n How to get started and how to set up a clean development environment. In many cases, development environments are ‘grown’ organically.<\/p>\n That works, but if for some reason you lose your development environment (e.g. you get a new laptop – yey!), setting everything up from scratch can be a pain.<\/p>\n This can be avoided by defining a development system setup standard – i.e. a description of how to set up a development system, what to install, in what order, where to install it, where to get it from,…<\/p>\n If this is done properly, setting up a new development system can be much less time-consuming, and on top of that, your transported projects can compile without a hitch – no need for adjustments.<\/p>\n This section of the workshop explores a real-life, proven development system standard. This standard can then be used as a starting point for your own in-house standard.<\/p>\n Defining such a standard is a little up-front investment with a tremendous payback; and as a bonus, it also works better with source code control systems.<\/p>\n InDesign SDK developers need to be quite familiar with their IDEs. More often than not, a developer will use more than one IDE on a plug-in project – Xcode as well as Visual Studio.<\/p>\n A good understanding of the basic structure of a plug-in project allows you to quickly diagnose issues – all too often, projects are simply copies of SDK samples that have been gradually transmogrified into something that works, but without really understanding the various settings.<\/p>\n This leads to ‘brittle projects’ – where a single preference change causes unexpected problems, or where something that should be an easy, global change does not propagate properly to subprojects.<\/p>\n Things looked at in this section at are how to ‘clean out’ IDE projects in an efficient way to remove needless, possibly lethal dependencies, remove unneeded settings, and rationalize dependencies.<\/p>\n The InDesign SDK is an abstract object-oriented environment, populated by abstract entities called ‘boss classes’, ‘boss objects’, ‘databases’, etc… This environment is layered on top of a few other nested abstract environments.<\/p>\n Right at the bottom layer we find C++, then some layered abstractions in-between, and finally at the top layer we have the InDesign SDK.<\/p>\n Because they are separated by multiple layers of abstraction, C++ has very little to do with the InDesign SDK. In some respects, C++ is not much more than a low-level detail of the InDesign SDK.<\/p>\n The problem is that both C++ and the InDesign SDK are object- oriented, and as a result, they use the same words to describe similar concepts, but at a totally different level of abstraction – e.g. ‘parent’, ‘child’, ‘inherit’, have similar meaning both in the C ++ world and in the InDesign SDK world, but they are really a long way removed from each other by multiple layers of abstraction.<\/p>\n When reading source code for an InDesign plug-in, it is often hard to understand what level of abstraction to ‘think at’. Compare it to electronics, networks and network protocols. The word ‘port’ can mean:<\/p>\n All meanings of the word port share some features (e.g. you can connect to a port – on all levels of abstraction), yet they are totally different things.<\/p>\n The same thing happens in the InDesign SDK – if one person is talking ‘C++’ and the other person is listening ‘InDesign SDK’, things won’t make sense.<\/p>\n This aspect of the workshop is about how to know from the context what level of abstraction to ‘think in’ when reading documentation or source code – and what sounded like gobbledygook at first will suddenly makes sense!<\/p>\n Because InDesign is such a massive system, plug-ins have to run in a fairly complex environment, and making sure your plug-in is as robust as possible in a number of respects is an important aspect of plug-in development.<\/p>\n To make your plug-in as robust as possible, testing (in the debug as well as in the release versions of InDesign) is important, and needs to be inherently designed into your plug-in.<\/p>\n If testing is part of your development process from the get-go, there are much less baffling bugs to diagnose. This section will handle various testing techniques and testing tools available, and how to use them to tackle bugs.<\/p>\n The US$1149.00 price of the training includes lunch on Monday, May 3, 2010.<\/p>\n During the course there will be very little or no time for hands-on; you also need to bring your own laptop if so desired.<\/p>\n You also need to arrange your own lodging and travel – Kris will be staying at the Courtyard Marriott on Union Bay during the summit. There are no hotels within a short distance of the campus – this is one of the closest (on a nice day, the walk from the hotel to the campus takes about half an hour, and is quite pleasant).<\/p>\n Where: Adobe Freemont Campus, Seattle When: May 3, 2010, from\u00a09:00am- 5:00pm This workshop is incorporated into the Adobe Creative Suite Developer Summit (May 3 – May 7, 2010). Registration has officially closed since April 16, but we still have some … Continue reading ![\"\"](\"https:\/\/www.rorohiko.com\/wordpress\/wp-content\/uploads\/2010\/01\/1daeb2595a0b4a229464934f9c3e0ba4-300x225.jpg\" "\\"InDesign")
<\/a>Description Of The Workshop<\/h3>\n
\n
Cost<\/h3>\n
Target audience<\/h3>\n
\n
Registration<\/h3>\n
About the course<\/h3>\n
1. Advanced C++ programming techniques explained<\/h4>\n
2. Patterns explained<\/h4>\n
3. Getting started<\/h4>\n
4. IDE files<\/h4>\n
5. InDesign SDK concepts<\/h4>\n
\n
6. Testing and debugging techiques<\/h4>\n
Logistics<\/h3>\n
![\"\"](\"https:\/\/www.rorohiko.com\/wordpress\/wp-content\/uploads\/2010\/01\/2010CSDevSummitBanner.png\" "\\"2010CSDevSummitBanner\\"")
<\/a><\/p>\n","protected":false},"excerpt":{"rendered":"