TLCC2016 TNEW Session

I've been spending a lot of time over the past few months reworking some "infrastructural" components of our customizations to make them far more manageable than they were:

I came up with a way to structure LWP_VALIDATE_CART into code "modules" so that I can see all of the code pertaining to a specific piece of functionality in a contiguous block instead of spending all of my time tracing gotos and jumping back and forth to different parts of the procedure.

I also wrote a simple javascript library called TNEWKit to make it easier to do frontend customizations by eliminating double-entry and moving all javascript snippets out of db tables and content fields and into a script kept into source control. I wrote some features I think are pretty cool -- using a selector syntax with aliases to choose which pages to run code on (instead of checking against window.location for everything yourself), and also using content fields to store flags to indicate when to run code, or when to include HTML. With some help from Sam Menard I'm working on getting this ready for use by other organizations.

Both of these things are more developer-focused than they are sexy functionality, but they've already made my life 100x better. Let me know if this sounds like something you'd be interested for your session.

I've been spending a lot of time over the past few months reworking some "infrastructural" components of our customizations to make them far more manageable than they were:

I came up with a way to structure LWP_VALIDATE_CART into code "modules" so that I can see all of the code pertaining to a specific piece of functionality in a contiguous block instead of spending all of my time tracing gotos and jumping back and forth to different parts of the procedure.

I also wrote a simple javascript library called TNEWKit to make it easier to do frontend customizations by eliminating double-entry and moving all javascript snippets out of db tables and content fields and into a script kept into source control. I wrote some features I think are pretty cool -- using a selector syntax with aliases to choose which pages to run code on (instead of checking against window.location for everything yourself), and also using content fields to store flags to indicate when to run code, or when to include HTML. With some help from Sam Menard I'm working on getting this ready for use by other organizations.

Both of these things are more developer-focused than they are sexy functionality, but they've already made my life 100x better. Let me know if this sounds like something you'd be interested for your session.

That sounds really cook, Nick! I've been meaning to check out your code on the bitbucket. 

Rog, I've mentioned this elsewhere but we built a "Restricted Access" plugin taking advantage of the TNEW shared session functionality to allow only certain people to access certain pages on our site, ie teachers for our education department, press for our high res downloads, and sensitive documents for our board members. 

We use Wordpress and TNEW and this is one of a few custom made plugins we've built in house.

I'm happy to share more if you're interested. Feel free to email me directly at josh@pnb.org.

Thanks guys, those both sound really interesting. We're still finalising the content, so I'll let the other planners know and get back to you asap.

Nick - I'll drop you an email about getting involved in this one.

Josh - I think Marley is putting you down to do this in the Web Customisations one.

Cheers both,

Rog