Skip to main content

Good Boy Jack

We have begun work on "Good Boy Jack" it is a simple story about an old lady telling the story of her good little boy named Jack.  It will be a 3D short which we hope to have finished in about 8-10 months.  The story is pretty much nailed down, we are just flushing out some of the dialogue.  This is a project we are taking on at school for our senior year.
Coming together on the project has been a struggle at times, but I am excited for where the project is headed.  We are hoping to have an Animatic done and ready to show some people when we go down to LA next week for siggraph.

Comments

Popular posts from this blog

Delta Cubes - The Dark Side of The Greendale

I'm a huge fan of Community ( @nbccommunity )  And I am also a huge fan of Pink Floyd.  So I decided to do a little mash-up after watching the last episode Season 04 Episode 07 - "Economics of Marine Biology"  And since I haven't posted in awhile, I thought I would Share.

Turning Saved Search Logic Into Insight: A Lesson in NetSuite Date Math

  Sometimes it's the smallest slice of a project that demands the most ingenuity. What seemed like a simple enhancement to a Saved Search ended up stretching my understanding of NetSuite’s formula logic—and my patience. 🔍 The Objective I needed to compare two types of project actions occurring within a 30-day window. Here’s the twist: Project Actions are a custom child record of a NetSuite Project (Job) , and they’re not stored in a way that makes direct comparison easy. So, I had to retrieve them through a Project Search , pulling in individual Action records via joins—first hurdle cleared. 📅 Date Math, NetSuite Style Next came the math. I needed to calculate whether one action happened within 30 days of another, but NetSuite doesn’t make date arithmetic feel intuitive. My first instinct was to use TO_NUMBER() to convert the dates into values I could compute on. Spoiler: it didn’t work. So I tried a workaround—subtracting a fixed reference date ( TO_DATE('01/01/2000...

NetSuite - Force Single Select on Multi-Select Field

Issue: We had a request from our Stakeholders to change a Multi-Select Field to a Single Select.  The Issue came up with this field being part of a bundle that we use.   We didn't want to deal with this being reverted or causing issues after we updated the bundle in the future, so I cam up with this work around. It is a Client Script that will throw an error to the user if they select more than one, and then it will reduce the selection to one option. /**  * @NApiVersion 2.x  * @NScriptType ClientScript  *  * 2025 Prevents multiple selections in a multi-select field * by showing an error message and removing the last selected value.  *  */ define ([ 'N/ui/message' , 'N/runtime' ], function ( message , runtime ) {     function fieldChanged ( context ) {         var scriptObj = runtime . getCurrentScript ();         var fieldName = scriptObj . getParameter ({       ...