The reason for me not updating my blog for a long while is that I was very busy. I'm still busy now, but yet writing. Something must have changed.
Metapolator is a next generation font creation tool. I started working on it roughly more than one year ago. We can consider the Libre Graphics Meeting 2014 in Leipzig in April 2-5 as my initiation into the project and the start of the current phase. More about the project history can be found at metapolator.com. Our Team gathered later that year again at the Automatic Type Design conference at the ANRT in Nancy in May 6-7 2014. In the meantime I was working on the previous prototype of Metapolator and shaped my mind about what it did then and what I thought it should be. It was in Nancy where we laid the foundation for the current incarnation of Metapolator technology.
Many people contributed to the project, but at Nancy I met Paul Sladen, whose kind help, being a good listener, and giving valuable advice, helped me to form concepts strong enough to get my hands dirty and start working. I left Nancy with a keen excitement in the project.
After more than one year later the Metapolator Project entered an interesting new phase. Some of the old concepts got replaced by better ones but the general direction has proven right. We have a great product vision and a well conceived ux-design through the work of Peter Sikking. Soon we will present a minimal viable product that supports designers with designing font families. To implement all of our plans and to reach version 1.0 will take some more time however.
My role in the project is less about the creation of the “Metapolator” interface; instead I am the inventor of the underlying “Metapolator Technology”. There are a couple of modules that I realized will be useful in a vastly broader range of applications and tools than just Metapolator. This led to my decision to take parts out of the repositories of Metapolator, and also ufoJS, a library I began developing some years ago that is a key component of Metapolator.
I hope I can use parts of Metapolator, especially CPS, to teach people how to make exciting new tools for font and graphic design.
Taking modules out of Metapolator to create stand-alone projects has primarily didactical reasons. It will be easier to show and explain the technology of Metapolator by looking at one part at a the time, instead of everything at once. It will also be easier to write specific documentation for these projects without having to consider the highly specialized nature of Metapolator. Lastly and most exciting for me: we will be able to create cool little projects with our technology to attract, inspire and teach the community. These projects will form an ecosystem around Metapolator: The developer tool for CPS that I'm working on right now will be available for all CPS based projects as an ad-hoc interface.
In the long run we will establish Metapolator technology as a platform to build the next generation of type design tools, or any other domain as well. Metapolator will be positioned as a highly sophisticated application that spawned new core technologies and on the way stimulates and enables new tools.
I want to see more people participating in Metapolator technology in the future; particularly because we offer interesting and genuinely new approaches for parametric design applications, and can enable everything between professional type design/engineering tools to ultra creative graphic design tools that are fun both to make and to use.
For a FLOSS project like ours it is crucial to gain a diverse community. Each part of the project will profit from discussing and solving issues raised by users from any background. We have topics ranging from computer language design to user interaction. The more people use our tools the more ideas and feedback will be available to further advance our mission.
Metapolator’s minimal viable product and the CPS Developer Tool are being developed in parallel at the moment. When I have finished the developer tool I will start to decouple some modules, namely: CPS plus the object model basics, MOM (maybe), our IO modules, the pen APIs and a collection of pens, and the CPS Developer Tool itself. I am also planning a series of blog posts to document the workings of these modules on a fairly high level and finally one about Metapolator that builds upon that knowledge. These articles will become part of the Metapolator documentation as well. I also have ideas for up to three fun projects that will prove the claims I made above and attract new people to this ecosystem; I expect one of these will be created soon after the isolation of CPS.
I have no comments feature on my blog for several reasons. You can discuss this post at the Metapolator g+ community, write me an email or chat to me on twitter.