Now, having said that, the reason why I hate them is that they are manipulative and insult my, and your, intelligence.

Yes I want to read it, that's what they are designed to do. And everytime I click on a link like that they make me feel bad for that very reason.

It's not me making this choice to click on it, it's not me who thinks that might be interesting and it's not me who wants to read the content. It's my brain getting tricked into thinking this is going to be interesing.
So please, please, stop writing headlines like that.

Pando might think traditional headline ("dullsville") style is boring, but they are not. They just require the reader to maybe stop for a split second, think and reflect about what you just read and then decide. Something more and more people are unwilling or uncapable of doing, so it seems.

From this day forward I'm going to assume that there is no useful content in an article that uses deceits like that and/or the author of is uncapable of writing a compelling story and can't get you to read it any other way.

I've pledged to never click on a clickbait link again and you should too.

Further reading

5 ways stores trick you into buying their goods

Editor

I want the editor to be ready to replace the old version of Techne.
Right now T2 supports almost every feature T1 does and has some exclusive ones.
Things I have to get done before I release it as standalone include

• Some UI refinements
• Java exporter
• Make the texture-mapper snap to integers when dragging.

Which isn't all that much, but still enough.
After that's done I already have a list of things I want to do.

• Making controls work by clicking and dragging them
• Plugins
• Smooth camera controls
• Possibly invert the controls

And for the future

• Animation support
• Multiplayer support
• Auto-save

If you have anything you want to see added to that list, head over to Bitbucket and create a new issue.

In a future post I'll talk about things I want to do for the website.
So long.

With the new Techne website there is now the possibility/requirement to select a license when you upload your model.

Creative Commons

Creative commons are a great set of licenses that give you good control what you want you want to allow.
All of them require others to attribute the original creator. Then you can add a copyleft (share-alike), meaning any deritive work must also be licensed under the same license. Non-commercial clause, prohibiting the use of your work in commercial products and lastly, you can prohibit making derivatives of your work.
More about cc: http://creativecommons.org

WTFPL

One of my favorites, the DO WHAT THE FUCK YOU WANT TO license.
It's succing and it's clear in its purpose.
You can read about it here: http://www.wtfpl.net/

None

No license means noone can do anything. Noone is allowed to download, noone is allowed to distribute or use the model as a base and go from there.

Conclusion

Whatever you choose, choose wisely.
On Techne Online I've set the default to CC-BY-NC. Everyone can use your model as long as you are not making money off it.

Disclaimer

I'm not a lawyer and none of the above is legal advice.

• node.js
• iisnode
  • requires URL rewrite module for IIS
• Ghost

installing node.js and iisnode

First you'll want to get iisnode up and running, fortunately that's quite easy to do.
You'll want to grab and run the latest installer for node.js.
Now make sure you have the URL rewrite module for IIS intsalled.
After that it's just a matter of running the iisnode installer.
To make sure you have everything working run %programfiles%\iisnode\setupsamples.bat and use your browser of choice to navigate to http://localhost/node.

installing Ghost

To get ghost running extract the downloaded source to the directory you want ghost to live in. I chose C:\inetpub\iisnode\ghost so I have all applications running under node in one place.

Once extracted make sure you have granted IIS_IUSRS group read & execute, list, and write permissions on your directory. I actually ran into problems when installing ghost because I hadn't setup the permissions properly.

Next you need to open up a cmd-prompt, navigate to your ghost directory and run npm install --production.

configuring iisnode

We need a web.config file in our Ghost root-directory.
I copied mine from http://philipproplesch.de/

<configuration>  
  <system.webServer>
    <handlers>
      <add name="iisnode" path="index.js" verb="*" modules="iisnode" />
    </handlers>
    <defaultDocument enabled="true">
      <files>
        <add value="index.js" />
      </files>
    </defaultDocument>
    <rewrite>
      <rules>
        <rule name="Ghost">
          <match url="/*" />
          <conditions>
            <add input="{PATH_INFO}" pattern=".+\.js\/debug\/?" negate="true" />
          </conditions>          
          <action type="Rewrite" url="index.js" />
        </rule>
      </rules>
    </rewrite>
    <!--
      See https://github.com/tjanczuk/iisnode/blob/master/src/samples/configuration/web.config for information regarding iisnode specific configuration options.
    -->
    <iisnode node_env="%node_env%" loggingEnabled="false" debuggingEnabled="false" devErrorsEnabled="false" />
  </system.webServer>
</configuration>  

configuring Ghost

Since you are using iisnode we need to change the configs of Ghost a little.
Open up config.js and under config.developement.server change port from whatever it is to "process.env.PORT" as shown below.

   config = { 
      developement : {
      ...
         server: {
            // Host to be passed to node's `net.Server#listen()`
            host: '127.0.0.1',
            // Port to be passed to node's `net.Server#listen()`, for iisnode set this to `process.env.PORT`
            port: process.env.PORT
        }

You also want to change the "url" setting so that it points to wherever you are hosting your blog.
Note that Ghost runs in developement mode by default, so far I haven't been able to find out what the difference is besides a different set of configs.
If you want to change the staging you can either change the NODEENV variable directly or open up the web.config we created earlier and change the value of the nodeenv attribute in the <iisnode /> to production.

configuring IIS

Everything that's left to do is to create a new application that points to your ghost install and you are good to go.

why Ghost

I don't know, it seemed like a good choice.
If I hadn't gone with Ghost I'd have used miniblog - I haven't used either before, so I might still switch.

Here’s how I think this should and could work.
When you want to load a new extension you pass a url to a json that holds all necessary data like name of the plugin, version, where to find supporting scripts and what menu entries to add.
Look here for an example.

As soon as everything is loaded and ready Techne will call the onLoad function in the plugin in case that needs to set things up.
Adding the menu entries is just a matter of adding them to the respective observableArray and knockout will do the rest for us.
I understand that exporter need to prompt the user for some info, take a java-exporter. That needs to know what namespace to use, how to name the model class itself.
So, I’m not sure if I should provide a helper function that takes care of setting up a wizard that you pass an object describing the fields you need. Or if I should just let the extensions do all the work.