Category Archives: The SketchUp team

Goodbye Aidan. Hello Bitsbox.

Ten years. That’s how long I was a member of the SketchUp team. I spent that time starting this blog, teaching classes, writing the For Dummies book, hosting 3D Basecamps, and a thousand other things. But the thing I’m most proud of is helping to establish the SketchUp for Education program: working with kids, parents and teachers to make 3D modeling a part of their lives.

SketchUp 4 Launch.jpg
The @Last Software team on July 6th, 2004, the day we launched SketchUp 4

When Scott Lininger (the co-inventor of Dynamic Components and lots more) approached me about leaving SketchUp with him to start a company that teaches little kids to code, I knew I’d found my (next) calling. I’ve been trying to learn how to program for years—what if I’d had the chance to learn when I was six? As a creative person, there’s no single skill I’ve spent more time wishing I had. I don’t want to be programmer; I want to be a person who can code. I want my kid to be a person who can code. What parent doesn’t?

So I talked it over with my wife Sandra (you know her as the LayOut Product Manager), and we decided I should go for it. It wasn’t an easy decision: The SketchUp team is my extended family, and this community has been the kindest, most generous and humble mob of people I’ve ever had the pleasure to know. And I love SketchUp. I LOVE it. (I still dream in SketchUp sometimes.) It’s part of my DNA.

t-shirts.jpg
About 10% of the SketchUp shirts I’ve collected over the years.

Scott and I left the team to work together full-time in June. In the time since then, we’ve created Bitsbox: A free website where kids can build apps that work on real devices (like phones and iPads), and a box full of app projects that gets delivered to our subscribers’ kids every month. The video we made for our Kickstarter campaign explains it:

Other good news: Last week was Computer Science Education Week, and over 200,000 kids built apps with Bitsbox online. You can, too. We were featured in very nice articles in TechCrunch and GeekDad, and we were the Kickstarter Project of the Day on the 11th. And we’re just getting started.

Scott_Aidan_2014.jpg
Aidan and Scott at Bitsbox World Headquarters in Boulder

If you’d like to support a couple of ex-SketchUppers in our effort to make coding less scary, or you’d like to pre-order Bitsbox for some kids you know, please do. At the end of the campaign, when we ask you if you know any Super-Secret Codewords, put in “SketchUp” and we’ll include something special in your first box. Maybe a hair from John Bacus‘s magical beard. Maybe something even better.

THANK YOU for ten amazing years. It was a pleasure. Maybe we’ll see each other at the next 3D Basecamp. Reach out if you like: I’m aidan@bitsbox.com. Onwards!

Posted by Aidan Chopra, SketchUp Evangelist (Emeritus)

Who is Steve Oles?

Whenever I teach someone SketchUp, the first thing I like to do is introduce our scale figure. Functionally, these 2D face-me components help orient you to a model’s scale and perspective. More personally, the scale figures we’ve chosen for our default templates have always been members of the SketchUp team. For us, it’s a fun way to recognize someone who’s helped make SketchUp what it is.

In SketchUp 2015, our default scale figure isn’t one of our great colleagues, but one of our great friends: Steve Oles.

SketchUp 2015’s default scale figure “Steve” rendered in the PSO Vignette style that he helped create.

If you’ve come to a 3D Basecamp, you may have met Steve or even sat in on one of his unconference sessions about hybrid drawing for architectural illustration. The name might also be familiar if you’ve ever used one of the PSO styles in SketchUp (Steve is short for Paul Stevenson).

And if the PSO styles are familiar, we’re guessing you may have come across Steve’s book at some point in your architectural studies. Steve has been a source of inspiration for our team for some time now, and as we’ve gotten to know him, we’ve really enjoyed learning about his career too. So, in our 2015 update for SketchUp, we decided it was about time to introduce you all to our friend, Steve Oles…

Posted by Mark Harrison, on behalf of the SketchUp team

Sharpening SketchUp for 2015

We have some news to share today — SketchUp 2015 is available for download now — but first we’d like to share something that’s a few weeks old.

Here at SketchUp HQ in Boulder, we have a team dedicated to answering the phone and email questions that customers send us every day. Recently, we received these two emails on the same day:

Thank you for replying to my mum. I’m Marius and I’m 8 years old. I really like SketchUp and we have it in school. In art school, I made a factory with my best friend. 

— Love, Marius XXX

And then, just a few hours later:

I’m a detective for the Ottawa Police Service. I specialize in Bloodstain Pattern Analysis and was introduced to your software while collaborating with university students. Using online tutorials I was able to quickly create 3D plan drawings for our crime scenes. The quality of the visual evidence produced was above and beyond what our court system was used to.

— Det. Ugo Garneau, Ottawa Police Service

We get emails like these all the time, and we always think it’s incredible that so many different kinds of people can learn and be productive with SketchUp almost right away. On the other side of the spectrum, we regularly hear from seasoned modelers who have mastered SketchUp to make building things more efficient.

We’re incredibly proud that SketchUp helps all of these people be successful — and have some fun while they’re at it. So when we plan updates, our team feels a big responsibility to preserve the reliability and flexibility that makes SketchUp… well, SketchUp.

In this release, we turned our focus to upgrading SketchUp’s performance infrastructure. In particular, we’ve updated SketchUp, LayOut, and our Ruby API to run as 64-bit applications. The least nerdy way to explain this change is that 64-bit architecture allows SketchUp to take advantage of more of your computer’s active memory. We’ve moved to 64-bit both to improve performance, but also to set up SketchUp to work better with the operating systems and extensions that people will be using over the next few years. So while this is a big modification to SketchUp’s technical backbone, we kind of hope you won’t notice it at all.

Similarly, SketchUp 2015 includes new modeling and documentation tools that we designed to feel like you’ve been using them for years. Probably our favorite of these is the Rotated Rectangle tool, a way draw to axis-independent rectangles that’s both incredibly useful and surprisingly intuitive. Give it a try: we think it will remind you of the first time you used SketchUp.

SketchUp 2015’s official Rotated Rectangle Tool draws rectangles that don’t have to be perpendicular or parallel to an axes. It’s a simple idea that saves you about a dozen clicks to draw shapes like the cube on the right.

There’s a lot more to explore in SketchUp 2015: fast styles… LayOut smart labels… a 3 Point Arc tool… simpler Pro licensing… full IFC compatibility to get more and more folks participating in information modeling… we’ve even linked SketchUp to Trimble Connect, a new collaboration platform for sharing, reviewing, and commenting on any kind of project file.

You can download our latest version here, and if you have SketchUp Pro License, go ahead and use our license wizard to upgrade. If you work in SketchUp every day, we think you’ll really love this release — after all, all we’ve done is make SketchUp work more like… well, SketchUp.

Posted by Mark Harrison, on behalf of the SketchUp team

Building a PVC Geodesic Dome with SketchUp

Here on the SketchUp team, we’re DIYers at heart — we like solving design problems and building things. For a while now, we’ve had a big presence at Maker Faire. We go because we truly enjoy nerding out with fellow makers and dreaming up our own design-build projects. At World Maker Faire in New York last month, we decided to cook up a pair of large geodesic domes, because, well, why not?

IMG_3999.JPG
Who wouldn’t want to build a geodesic lair out of PVC pipe?

Actually, the point of our exhibit — besides being a practice run for a future Burning Man trip — was to prove that SketchUp makes planning and building team DIY projects easier and more fun. We enlisted the help of our good pal Eric Schimelpfenig of sketchthis.net and set out to turn a pile of PVC pipe into two huge geodesic domes and some comfortable furniture. Here’s how we pulled it off:

After exploring geodesic designs on 3D Warehouse — and a lot of discovery on Domerama — we jumped into SketchUp for conceptual design. Satellite imagery for our site plan demonstrated that two twenty-foot diameter domes would fit perfectly, and a simple massing model proved that 3V ⅝ domes — with their extra head room — would provide plenty of height and floor space for people and furniture.

Once we knew the defining characteristics of our dome, we churned out the strut lengths using Domerama’s geodesic calculator and then advanced the design using Dynamic Components to create a fabricatable model. From there, we employed generate report and some spreadsheet magic to crank out a cut-list for our PVC stockpile from Home Depot.

DCScreenshot
Using the proportional math from Domerama’s 3V ⅝ dome calculator, we built a dynamic component that uses dome diameter and hub protrusion as inputs for automating a 3V dome. You can download this dynamic geodesic model on 3D Warehouse.

As our fabrication captain, Eric got to turn our SketchUp model into a collection of ready-to-assemble parts. Using some simple jigs to speed up the cutting and drilling, he churned through 1,600 feet of pipe — about a quarter-mile of PVC — from his workshop in Massachusetts. Rounding out the list, he ordered up the awesome purpose-built connector hubs from Sonostar and grabbed a giant bag of nuts and bolts to keep things from sliding apart. With just two days to go before assembly, he loaded 152 connectors, 322 pipes, two ladders, and a dozen hammers into a van we’re pretty sure he had permission to borrow.

2014-09-10 19.54.51.jpg
Two geodesic domes and enough left-over pipe to spit out a few of these bad boys…

On-site at the New York Hall of Science, the pipe-laden van was met by a jet-lagged assembly crew of SketchUppers who’d only ever seen the geodomes in our working model. Over the course of a few hours, we assembled the two domes according to these hilarious yet exceedingly clear build instructions, courtesy of Eric and LayOut.

FullSite4-IMG_3903.JPG
Banging pipes together at World Maker Faire. See more photos of our geodesic dome build here, or watch the sketchthis.net time lapse of our build here.

The next day, our team hammered together several pieces of SketchUp-designed PVC furniture (generously contributed by our friends at FORMUFIT), and fitted vinyl tarps to the roof. We had designed the tarps to be a modular shading system, so that we could leave some sections of the dome exposed or cover everything up in case of crummy weather.

To derive the tarps from our SketchUp model, we drew out some basic gore-like polygons over the dome component and then used the Flattery extension to derive their dimensions for printing. The tarps were manufactured with grommets that allowed us to join and secure them with zip ties.

Screen Shot 2014-10-23 at 9.46.20 AM.png
Our tarping system was one of those simple ideas that was meant to work, but not be perfect. We anticipated (and desired) stretching in the tarp, so we modeled our gore polygons for stretched-out coverage, then laid the geometry flat with Flattery.

Throughout the weekend, thousands of attendees — attracted by the awesome sight of our booth and the promise of shade — wandered through our domes, where they were pumped full of SketchUp knowledge and slapped with these bracelets before being sent, disoriented, but not sunburned, back into the Faire.

We introduced a lot of people to SketchUp and Buckminster Fuller (not bad company, right?) over the weekend, and now we have a pair of geodesic domes to keep us cool at the next team picnic.

DSC_0113.JPG
The SketchUp team on good behavior at Maker Faire. We also did a lot of this.

Posted by Mark Harrison and Andrew Strotheide

Looking to build your own geodesic? Explore the links above, then download this dynamic component model and these build instructions to get started. Be sure to Tweet us the pics if you pull it off!

Modeling a laser-cut Halloween costume for my son

October is the time of year that all of my creative energy is focused into a single, solitary purpose: the design and making of an unreasonably complicated Halloween costume for my son. This year, I was determined to reflect his outsized interest in aviation by building him his very own airplane. Something with an open cockpit. Something with a propeller. Something vintage. I started by touring the 3D Warehouse, collecting models of airplanes that might be good candidates. I settled on a WWII-era F4F-4 U.S. Navy fighter because I liked its shape, and because the model I found (by D.James) was beautifully executed.

 I found this Grumman F4F-4 on the 3D Warehouse. It was modeled by D.James.

Opening it in SketchUp, I began the process of simplifying the plane down to its most basic forms by hiding or deleting stuff I didn’t need. The landing gear and propeller went. So did the wire-looking thing (I’m not much of an engineering buff) that connected the tail to the cockpit canopy. Eventually, I grouped the remaining bits of airplane together and put them on a single layer that I called “Reference.”

The first step was to strip away the details that I didn’t think I’d need.

Next, I set about creating a brand-new model of the fuselage and tail by using the Circle, Push/Pull and Scale tools to create a form that (more or less) matched the existing model. I worked right on top, using the original geometry as a snapping guide for the new. This didn’t take as long as you’d think, and it resulted in a simple form that I could easily manipulate later on. For the wings and stabilizers (the smaller wings on either side of the tail) I traced basic, flat shapes; I knew I wouldn’t end up making them aerodynamically correct, so I didn’t bother giving them a realistic thickness. It is, after all, illegal for a two-year-old to pilot aircraft in the state of Colorado.

D.James’ model is very complex, so I made myself a simpler version (grey) by modeling directly over the original (blue). The wings and the horizontal stabilizers are just flat faces.

Not being able to find a decent model of a small child anywhere online, I used a toddler-sized cylinder as a scale reference as I scaled down the entire vehicle to fit him. “Rough” doesn’t begin to describe the level of accuracy I employed at this stage of the engineering process; I basically held a ruler next to his waist and decided that he could squeeze into a ten inch tube. I did NOT at any time actually squeeze him into a ten inch tube. Mostly because I didn’t have one handy.

At this point, I set about changing the proportions to increase the airplane’s overall level of adorableness. To do this, I grouped together the body, wings and tail bits, made a copy off to the side, and used the Scale tool to stretch and squish the whole thing.

Starting with a squashed cylinder to represent a toddler, I used the Move tool to change the proportions of the airplane until it looked wearable.

At this point, I’d pretty much decided that the airplane would be made out of laser-cut cardboard (more on that later), so I continued modeling with the assumption that the wings and stabilizers would be 2D shapes, and the body would be a more organic, 3D form. This part of the process was the most time-consuming and fiddly—it was just a matter of tweaking the shape of each element until I was happy with the overall proportions of the plane.

The intermediate state of the airplane is actually very basic.

As I settled on a material and construction method, I spent a lot of time on the website of a New Zealand and US-based company called Ponoko. They offer laser-cutting and 3D printing services, and their material selection is terrific. Ponoko has also been a good friend of SketchUp since they launched several years ago. Frankly, I’d been waiting for an excuse to try them out; their offering seemed really slick.

Before I could go any further on the airplane project, I needed to know more about the material I’d be using: its precise thickness, what sheet sizes are available, and its cost. Weight and budget were my major concerns, so I settled on double-layer corrugated cardboard with a thickness of 0.264 inches (6.7mm) and a maximum sheet size of 31.1 x 15.1 inches (790mm x 384mm). Sheets that size cost $3.50 apiece, which is cheap, plus file setup and cutting, which is decidedly less so. When I uploaded a test file to Ponoko to see what this undertaking might cost, the average price per sheet of cut parts was about $25.00. I figured I’d need about ten. This was turning out to be a very expensive cardboard airplane.

The double-layer corrugated cardboard page on Ponoko’s website. Make note of the material thickness for accurate modeling.

Back in SketchUp, I set about figuring out how to build the project out of interconnected, flat pieces. I started with the easy parts: the horizontal section of the body, which included the wings, and the vertical section, which included the tail. These two components were the structural parts of the plane, so I made them out of three layers of cardboard, laminated together for stiffness and durability.

The horizontal fuselage sheets (which include the wings) provide the airplane’s back-to-front structural strength. The vertical pieces are necessary for forming the nose and tail.

To design the rest of the plane’s pieces, I copied the 2D profiles that made up the fuselage, made them into faces, and extruded them to the same thickness as the cardboard. Each piece was an individual group at this point; I didn’t bother making named components until I was further along.

The ellipsoid “fins” that march down the length of the airplane are the key to defining the fuselage’s sleek, rounded shape.

Next, I used the maximum sheet size for the cardboard to figure out which parts would need to be subdivided and re-assembled after they’d been cut. This task was made a bit simpler by the fact that the biggest pieces of the plane—the horizontal and vertical “slabs” I’d started with—were each made up of three thicknesses of material. I just figured out a design that would hide the seams on the outside, visible layers, while allowing the middle layer pieces to overlap enough to form a strong sandwich when I glued everything together.

Parts which would ideally have been cut from a single sheet of cardboard had to be broken up into smaller pieces due to the small maximum sheet size for that material. These were then sandwiched together with glue. The resulting triple-layer laminates ended up being very stiff.

One of the last steps in the design process was to design the slots that would allow all (or at least most) of the pieces to interlock together. Figuring that the kerf (the width of the cut made by the laser) would be very small in this material, I decided to make the slots exactly as wide as the material thickness. This part was actually kind of fun—it’s the closest I’ve ever come to modeling a 3D puzzle.

There are lots of ways to cut slots in the pieces; I used the Line and Push/Pull tools in combination with the Copy and Paste in Place commands.

At this point, I began the delicate process of converting my groups into components; piece by piece, I exploded each group and then immediately made it into a component with a meaningful name. Where I had a pair of identical, flipped parts (this was actually the majority of the airplane), I made sure both were instances of the same component. The airplane is made out of 58 individual parts, but only 32 unique components.

Because the airplane is so symmetrical, most of the parts are flipped and duplicated component instances.

Just for fun, and because I knew it would look really cool, I copied the plane onto a duplicate layer, and used the Move tool to arrange the parts as though they’d been exploded out from the object’s center.

All of the airplane’s parts, exploded outward for visibility.

To have something laser cut by Ponoko, you give them a vector file (EPS or SVG) with all of the parts laid out flat. They provide Adobe Illustrator templates for all three of their standard sheet sizes, which makes things a bit easier. In order to go from a 3D, assembled object in SketchUp to a series of 2D cutting files in Illustrator, I needed to disassemble the plane piece by piece. Figuring that it would be easiest to have the assembled and flat versions adjacent to each other, I made a copy of the airplane off to the side and proceeded to take the copy apart with the Move tool. I used the Move tool’s rotation grips (and occasionally the Rotate tool) to spin pieces around so they lay flat.

I made sure not to forget any pieces by literally taking apart an assembled copy of the airplane, laying the parts flat on the ground as I proceeded.

Almost there. I drew a rectangle that matched the sheet size of the cardboard, turned it into component, and made a dozen copies. Then I went through the laborious process of figuring out how to lay out all of the airplane pieces in an efficient way. Having done some experimentation on Ponoko’s website, I’d discovered that it’s significantly cheaper to produce two copies of the same cutting file than it is to make two different sheets. Good thing, because it turns out that most of my airplane parts are symmetrical; they’re mirrored copies that exist in pairs. To take advantage of this, I arranged all of the symmetrical pieces on five sheets and produced two copies of each; all of the “singles” fit on only two more. In total, I had twelve sheets of parts.

The grey rectangles represent 31” x 15” sheets of cardboard. Notice that there are five pairs of identical parts sheets, plus only two unique sheets (in the upper left corner). This significantly reduced the laser cutting costs.

Digging around on Ponoko’s website a little more, I discovered a mention of something called “nodes” which help to keep slot-assembled parts from wobbling and falling apart. Basically, it involves adding rounded bumps to the slots in your pieces. The size, position, and number of nodes depends on your material and its thickness, and the website didn’t provide any specific tips for my double-layered corrugated cardboard, so I made an informed guess and crossed my fingers: I settled on a node height of 1/16th of an inch, which, multiplied by two, represented about a quarter of the 0.264″ thickness of the sheet. That’s a lot, but I figured that cardboard is a pretty compactible material. I was lucky; the nodes ended up working perfectly.

Nodes help to keep the parts snug when the final object is assembled.

One at a time, I copied each sheet to a new SketchUp file, set my camera to a top, parallel projection view, applied a simple, white Style with no profiles edges or other effects, did a Zoom Extents, and exported a PDF at 1:1 scale. Then I opened each PDF in Illustrator, copied just the parts, and pasted them on a new layer in the template provided by Ponoko. I went through this process a total of seven times—once for each unique sheet I’d be sending them.

The sheets are exported out of SketchUp Pro as 1:1 scale PDF files. These are then opened in a vector illustration program like Adobe Illustrator or Inkscape.

In order for Ponoko to convert an Illustrator EPS (their required upload format) into whatever file they send to their laser cutters, you need to make sure all of the edges in your drawings are colored and sized correctly. Blue lines tell the laser to cut, whereas red lines are used for engraving. Just follow the instructions on the template and you’ll be okay.

After uploading my files, putting in all my credit card details, finalizing the order, corresponding a few times with the friendly staff at Ponoko, and waiting a couple of weeks, a box arrived at my house. I opened it up and was nearly knocked over by the smell of laser-cut cardboard. It’s an odd odor; not terrible, but definitely not pleasant. I quarantined the pieces in the spare bedroom and went to work punching everything out.

The accuracy of the cutting was astounding. I’ve never laser cut anything; I expected the pieces to look good, but the quality of what I got made me alternate between grinning and literally giggling. For a person who spent hundreds of hours in architecture school hacking away at cardboard, foam core, basswood and plexiglass with an X-Acto knife, the extravagant expense of laser cutting instantly justified itself. I was hooked.

I couldn’t believe the quality of the laser-cut parts that arrived on my doorstep.

It took longer to peel the paper backing off of the individual parts than it did to assemble the actual airplane (not counting the time it took for the glue to dry completely). With only a couple of exceptions, the parts slotted together exactly the way I’d designed them to. It was the most gratifying thing I’ve made in years.

It took me only a couple of hours to put the airplane together. The next version will have less glue—that was the most time-consuming part of the process.

As a devout follower of the Church of Making Things Overcomplicated, I decided early on that the airplane should have a custom-designed instrument cluster. And a steering wheel. And a working, motorized propeller. This is already a monster blog post, so I’ll end the description of my process here. To conclude, a few photos of the end result.

The final result weighs somewhere between five and six pounds, but that includes the steering wheel, the propeller motor, and four AA batteries. My son (who’s two-and-a-half) had no trouble wearing it.
 I designed the instrument cluster entirely in LayOut, using layers of translucent details to simulate reflections, highlights and shadows.

Posted by Aidan Chopra, SketchUp Evangelist

Fabbing with friends: a WikiHouse for World Maker Faire

When we first heard about WikiHouse, we knew we wanted to build one. When WikiHouse’s co-founder gave an inspiring Ted talk this past May, we were inspired to build one. And when we read the WikiHouse modeling standards (make groups, use layers!), we knew that we just had to build one.

So as we sat down with the WikiHouse team this summer and talked about how we could collaborate for World Maker Faire, our goal was a no-brainer: design and build our own WikiHouse in just over a month.

The SketchUp WikiHouse for World Maker Faire. View more photos of this project here.

Kicking off the project, it was quickly evident that between the SketchUppers and the WikiHouse’rs, there were more than enough architects to go around. Aside from the reality that no one on the team had a CNC router in his garage, we knew we’d need a project partner with tons of CNC experience — and one who wouldn’t laugh off the idea of hammering together a thousand cut pieces in the middle of Maker Faire.

Enter our friend Bill Young over at ShopBot Tools. We’d been itching to do a project with Bill since he caught us spreading saw dust all over Maker Faire Bay Area earlier this year. Bill’s practical experience with wood selection, tolerances, and project planning are nicely measured by his ability to engrave anything (onto anything) while generally believing that most things are possible. With the right mix of optimism and practicality, we started trading SKP’s back and forth, hashing out the trade-offs in various design concepts.

Concept 1: A custom tarp could be tricky, and would we even hear ourselves over a CNC in one bay?
Concept 2: Using ‘Add location,’ we noticed the lookout would showcase a cozy stretch city highway.
Concept 3: We were charmed by an iconic design with exposed sections, but this required too much wood and time.
The Constructible Model: Just right with all the right hooks, tabs, and S-joints.

With an ‘as-built’ SketchUp model set and 160 sheets of plywood sitting in Bill’s shop, it was time to derive cutting sheets and turn up the ShopBots. (Note: if you’re looking to prep your own model for CNC, the free WikiHouse plugin for SketchUp turns grouped geometry into neatly laid out cutting sheets).

Soon after we began cutting, it became clear that our two central constraints were time and lumber. Thankfully, our design and tools were well-suited to these pressures. The WikiHouse design standards call for modular elements that could easily be added, subtracted or adapted — and because WikiHouse uses SketchUp as a platform, making in-progress changes was painless and quick. With a quick pivot for build phasing (agreeing what to cut next based on how much wood and time remained), the sawdust started blowing and the sheets started piling.

Ply piles in progress: only a small accumulation of the full project. See more photos from our cutting phase.

Some 1,150 cut pieces later, we are on our way to New York City after a fantastic month of collaboration between architects in the U.K., software engineers in Colorado, and woodworkers in Virginia. When we reach World Maker Faire, we’ll be joining forces with friends from the SketchUp community to show what open design tools, open design platforms, and a bit of courage can accomplish in just two days.

The right tools for the job: custom cut and engraved wiki-mallets for World Maker Faire.

Didn’t make it to World Maker Faire? Follow the build progress.
Want to see more photos of our project to date?
Watch a timelapse of the SketchUp WikiHouse build.

Posted by Mark Harrison on behalf of the SketchUp Team

Teaching Dynamic Components to the web: a SketchUp summer research project

Hey there. My name is Brandon, and this summer I interned at SketchUp.

I attend the Colorado School of Mines and, as you might guess, I study computer science. Regardless of your major at Mines, all students are required to take a class on drafting. When I was offered a position on the SketchUp team this past spring, I was hesitant to believe I could accomplish anything in three short months. After all, it took me an entire semester to learn another 3D modeling program (which will remain nameless). Thankfully, SketchUp is as easy to use today as it was when I first opened it in middle school.

One of SketchUp’s most powerful feature sets are dynamic components, groups of geometry that have advanced functionality. To use a dynamic component today, you’d download one from the 3D Warehouse (or create it from scratch) and open it in SketchUp before you can change its parametric options. My summer research project was to investigate the feasibility of configuring those parameters from within a browser, before downloading the component to your computer. Another way of looking at it: can we teach a web browser to customize a dynamic component?

Here I am presenting a prototype of my research project to the SketchUp developer team

Last year, we unveiled the SketchUp Showcase which featured the prototype of a web-based model viewer that lets you to rotate and view models in a browser without having to install any additional software. It’s still a prototype, but this viewer offered me a basic way to display a dynamic component online, and then redraw it as parameters changed.

I spent a great deal of time making sure that when an input parameter changed, the browser displayed component transformed just as it would inside SketchUp. To pull this off, I thoroughly investigated how dynamic components work. This involved hours of playing inside SketchUp on my own and bugging numerous engineers for help. Reading through the source code didn’t hurt, either. This allowed me to properly rewrite the dynamic component functionality in JavaScript so that the behavior in a web browser would be consistent for users.

A screenshot of my research project in action: the configurator changes the material in a NanaWall dynamic component, then the component is re-drawn in a web browser

Proving that a web application could configure a SketchUp model was only one part of my research. I also had to investigate how to teach a web browser what a dynamic component is in the first place. You see, what our viewer prototype reads and displays is the geometry contained within a SketchUp file. But dynamic components are more than just geometry; they contain attributes like variable values and formulas.

To close this gap, I used SketchUp’s Ruby API to create an extension that exports the component along with its dynamic properties wrapped up in a separate JavaScipt object. The browser is then able to reunite the geometry from the exported file to its JavaScript counterpart, so the component can be parametrically manipulated. In a way, the extension acts like a moving truck. All the geometry gets packed and sent in one file, while all the attribute data gets sent in another. Everything ends up in the same place, albeit in pieces, and everything works just the same after being reassembled.

My extension exports a dynamic component to the web, packaging its dynamic properties separately so that they can be read by web browsers

This idea of using technologies that require no additional software fits pretty well with SketchUp’s development philosophy, and my research this summer hints at the potential of a SketchUp configurator for the web. For example, components could be viewed and modified on mobile devices, allowing people to share and collaborate more effectively. 3D Warehouse users might be able to manipulate components online, allowing them to find the right modeling asset even faster. Reporting tools could be built in to model viewers, allowing real-time cost analysis, helping designers keep projects on budget and on track.

There were many other highlights from my summer at SketchUp: helping launch SketchUp 2013, learning a ton about LayOut from architects and designers at the AIA National Convention in Denver, and mastering high-tech hardware configurations via our office espresso machine and 3D printer. All in all, I feel pretty lucky to have joined Trimble, and I’m curious to see what’s next from the minds behind SketchUp.

Posted by Brandon Rodriguez, SketchUp Web Intern

This ain’t our first rodeo

It’s always been a SketchUp tradition to include a member of our team as the default component. Functionally, we include these 2D figures to lend a sense of scale and perspective when you first open SketchUp. Without a scale figure, it would be impossible to tell if you were looking at the origin from 10 feet away or from 10,000.

But our scale figures are also subtle nods to the friendly folks on our team. Bryce, Sang, Susan; these people have all played an important role in the development of SketchUp. They’re also great friends. So, who is the scale figure for SketchUp 2013?

Introducing Derrick, the scale figure for SketchUp 2013

It has been about one year since we were acquired by Trimble. It has also been one year since we lost the person who made it all happen. Derrick Darby was Trimble’s champion for our acquisition, and was very excited to move to Boulder, Colorado and continue his career with us. Sadly, he passed away just as the deal was closing, leaving behind a beautiful wife and three talented sons.

Derrick had the kind of rare, infectious personality that made us feel like we’d known him for a lifetime, even if we’d just met him. He was a true southern gentlemen. And although he wasn’t with us as we unpacked on our first day at Trimble, we wouldn’t be where we are today without his leadership and thoughtfulness. Derrick was a visionary and an innovator who previously sold two of his own companies to Trimble. He had been around the block with technology creation, acquisition, integration and strategy — creating jobs and opportunity for many along the way. Derrick liked to say that the SketchUp acquisition wasn’t Trimble’s first rodeo. We hope it’s one that continues kicking up dust for generations.

A few past and present members of the SketchUp team

So, picking a scale figure for SketchUp 2013 was an easy decision. Derrick remains an integral part of our team and family, and we couldn’t think of a better way to remember him than to share a bit of Derrick’s personality with world of SketchUp users. The next time you open SketchUp, take a moment to interact with Derrick’s component (Tools > Interact) and send some good vibes to guy who was largely responsible for SketchUp’s third act.

Posted by Chris Keating, on behalf of the SketchUp team

A recap of SketchUp 3D Basecamp 2012

Almost two months ago, hundreds of the world’s most dedicated SketchUp aficionados descended upon our hometown for 3D Basecamp 2012. On the first day, we packed into the Boulder Theater for presentations from the SketchUp management team, several plugin developers and a keynote by Bre Pettis of MakerBot.

The first day of Basecamp took place at the historic Boulder Theater.

 
Leaders from SketchUp and Trimble talk about what’s in store for our product. They address such questions as “What’s next for SketchUp?” and “Why did Trimble buy SketchUp?”. (46:14)

 
The SketchUp leadership team takes questions from the 3D Basecamp audience. (17:06)

 
Representatives from seven SketchUp photo-realistic rendering plugins outline their product offerings in rapid succession. (17:07)

 
Four very different companies present their SketchUp-related technologies: BuildEdge, Sunglass, Product Connect and 4D Virtual Builder. (56:57)

 
 MakerBot Industries co-founder Bre Pettis delivers a terrific keynote presentation about 3D printing. (31:35)

That night, we gathered at a local spot for a party, where the highlight was undoubtedly the SketchUp ShootOut: two heroes competing to make the audience guess a mystery word by modeling on side-side computers. Bulldozer! Cabin! Bubble tea! Melancholy! The winning guesser and the winning modeler both won free drinks, but everyone seemed to be having a blast. Note: I beat John in a best-of-five match with “glove”, “foyer” and “cook”. It may be the proudest I’ve been all year.

Hotshot modelers squared off against each other in the first-ever SketchUp ShootOut.

Tuesday’s proceedings moved to yet another venue for a full day of barely-contained mayhem. The morning’s three blocks of unconference sessions coincided with three hours of beginner Ruby training. After lunch, we squeezed together to watch scheduled presentations by the likes of Daniel Tal, Nick Sonder, Mark Carvalho, and teams from 3skeng, ARmedia and SightSpace 3D. Three more hours of unconference sessions and a repeat of the morning’s Ruby 101 class followed, then everyone went straight to bed. I assume.

 
Landscape architect and author Daniel Tal presents a wide-ranging set of tips, tricks and best practices for modeling everything from terrain to site design. (40:31)

 
Architect and video tutorial star Nick Sonder outlines his process for using SketchUp Pro and LayOut to create complete sets of construction documents for his projects. Note: We subsequently made a set of six videos with Nick that describe his process in detail. They’re easier to watch and understand than this recording—just an FYI. (52:06)

We planned a Design Charrette for Day 3; participants split up into teams to tackle a challenge that we created in collaboration with Impact on Education, a local non-profit that acts as a kind of R&D department for the Boulder Valley School District. The design brief involved re-imagining a classroom to take into account the way teaching and learning have evolved with the introduction of mobile technology. At the end of the two-and-a-half hour charrette, a dozen teams presented their designs (in SketchUp and LayOut, of course), after which an illustrious panel of judges from IoE picked their favorite projects. The winning team members then squared off against each other for several rounds of SketchUp trivia. The victorious Michaels (Tadros and Brightman) each won a Replicator 3D printer, generously donated by our friends at MakerBot Industries.

While the designer-types did their thing, about twenty plugin authors spent Day 3 across the street at our first-ever Ruby Developers’ Conference. They huddled and schemed and plotted the future of our API (application programming interface). They even held a competition of their own: Dale Martens, a.k.a. “Whaat” and the creator of the Artisan organic modeling tool set, won the hackathon by coding a working first-person shooter game that runs inside SketchUp—in a couple of hours. Needless to say, Dale got a MakerBot, too.

Participants in Wednesday’s Ruby Developer Conference posing as if they’re a sports team.

All in all, we’re pretty proud of how well our first Basecamp at Trimble went, considering how quickly we planned it and that Dusty (our Event Manager extraordinaire) isn’t on the SketchUp team anymore. The space was at times tight and A/V and internet access are forever thorns in my side, but the vast majority of attendees we surveyed said they enjoyed themselves, learned some things, met cool people and (most tellingly) would happily join us at another 3D Basecamp.

Which brings me to my last point: When’s the next Basecamp? Good question. We don’t know right now, but given that our plan is to move to an annual release cycle starting next year, and that conferences are a great way to celebrate product launches, we’ll do our best to make sure there’s a 3D Basecamp in 2013. If you’d like to be one of the first to know when we announce it, you can add your name to our Next Basecamp Notification List.

Feel like looking at lots of pictures from the event? This album should do the trick.

Posted by Aidan Chopra, SketchUp Evangelist

SketchUp gets a warm welcome in China

In mid-July of this year, intrepid world travelers John, Shara and Steve headed east to join Sophie Feng (one of our newest SketchUp team members) on a mission to learn more about folks in China are using our software. Here’s a travelogue that Sophie put together to describe the trip.

When a journey begins, you generally have no idea how it’s going to end. The small talk that seems insignificant turns into a great inspiration. The strangers from another country you only knew by name become your friends, while the colleagues you just met become your family.

In June, we talked by Skype about a trip to visit SketchUp users in China, planned it, then worked toward making it happen. Despite that, I doubt my dear colleagues knew how long it was going to be until we were sitting in a prestigious architectural firm the first day they arrived in Shanghai.

July 9th: Shanghai EC Architectural Design & Planning Co. Ltd.

Users presented to us how they use SketchUp in their workflow. They showed off their design skills by making a beautiful SketchUp animation for us. A local government official also was invited to join the “SketchUp Dialogue”.

John really enjoys drawing on the wall.

July 10th: Better SketchUp, Better Design at the Shanghai Salon

Many designers, mostly young, came to the event filled with hope. They were enthusiastic, intelligent, idealistic, and joined us from all over China (Beijing, Shanghai, Suzhou, etc.) One interior designer even came all the way from Taiwan to share his SketchUp ideas with us.

Our users tell their stories one by one.

We were curious as to how these young designers use SketchUp for such large projects, which are actually fairly common in China. One thing that was very important to all those at the salon: They really want to make sure that SketchUp would not change too much after the transition from Google to Trimble. One of the most impressive presentations of the day was a local developer’s “BIM for SU”. One of our users developed a series of plugins for SketchUp that completed a specific BIM workflow.

On a yacht in Huangpu River, Shanghai. From left: 王韶宁 wang shaoning, developer (Beijing); Steve Dapkus; 潘毅 Panyi, Landscape Architect; 钟凡 Zhongfan, SketchUp-BIM user (Guangzhou); John Bacus; 陈建良 Chen jianliang, interior designer; 刘新雨 Liu xingyu, Urban Planner (Beijing).

July 10th & 11th: Wuhan

This was our first visit to a famous Chinese university: HUST (Huazhong University of Science & Technology) is the only institution to offer a Masters degree for BIM qualification in China. Professor Luo (the College President) told us that there were 8,000 construction sites in Wuhan last year. There’s no doubt that BIM has a great opportunity in China, as does SketchUp’s role in a BIM workflow. My colleagues John, Steve and Shara found themselves feeling hopeful at this leg of the trip, against all odds due to jet lag, 43 degree Celcius heat and 90% humidity.

As the first national research Lab in China, HUST is glad to get new ideas from SketchUp as a BIM tool. In the afternoon, another interesting salon was waiting for us.

Our new friends shared lots of interesting thoughts with us. Shara looks better after she’s had some coffee.

July 13th: Guangzhou

On our way to Guangzhou University, The U-BIM Company prepared a BIM and SketchUp conference for end users in Guangzhou. John added that “Maybe SketchUp is BIM for everyone” in his slides, and added that “SketchUp can do more than just visual representations.” digitalarch, a SketchUp user in Taiwan, had explained this notion for us at the Shanghai salon.

We look fresh today. We are standing at the entrance of Guangzhou University.

SketchUp users always have a way of expressing their thoughts; a designer who is also a professional rapper told us he would write a Chinese rap for SketchUp. What a brilliant idea! I know it’s been a long trip—10 days, 3 different cities, and my American colleagues were all anxious to get back to their sweet families. Let’s end our long trip with a poem written by Chen ling 陈玲, a young Shanghai landscape designer. When he told us that he believes that SketchUp changed his life and career, I saw his eyes light up.

Chen ling is a very talented designer. Look at the scale of these models!

Poem: Gratitude for SketchUp by Chen ling 陈玲

Translation:

Have been working in designing after leaving school
So lucky I met you—SketchUp in October 2004
You change my career
Because of you, I seize more opportunities.
Because of you, I am one of the youngest writers who can publish the book about you.
You give me so much, so much wonderfulness
You bring me so much, so much glory
Thanks a lot

Posted by Sophie Feng, SketchUp China Team