niczuloo.blogg.se - Pubcoder examples

#PUBCODER EXAMPLES 64 BIT#
#PUBCODER EXAMPLES SOFTWARE#

This is what we have been building inside PubCoder: clever ways to connect to useful services which provide the ability to search, pick and use assets you may not have at your disposal. There are tons of services out there who provide, for our sake and fortune, technical means to connect to their great products. Not at all! Here is where the other magic word of this millennium comes in: APIs. This doesn’t mean we have to waive to the idea of exploiting at best our great 1 GB/s connection flat contract and the immense power of the web.

#PUBCODER EXAMPLES 64 BIT#

Moreover, PubCoder 3, our newly release in beta for mac, is a 64 bit application. So yes, CPU and RAM are still very useful when it comes to treating and manipulating large assets locally, even in this “cloudy” age. And audio and especially video files can be pretty large. You could embed those from the web (Youtube, Vimeo, etc), but you also might want to include the asset directly in your product for a whole lot of good reasons.

In digital publishing there’s not just images: don’t forget audios and videos.

Certainly with assets we see used in InDesign or PubCoder projects.

How about working on your project offline? There are web apps that allow some small caching in the browser through local storage, but this would be rather uncomfortable when it comes to larger files and project.

Just drag your 2GB TIFF images, use it in your 100px per 100px box layout, and when it’s time to modify your image, for example a PSD layer, this is done immediately. In PubCoder all the work is done by the software, automatically. So you better do all the optimisations on this side of the plug.

On a web application there’s a bottleneck between your desktop and the application, called connectivity.

#PUBCODER EXAMPLES SOFTWARE#

Still, the kinds of projects PubCoder allows you to create are precisely those where having your big source files locally, where the software can use all the horsepower of RAM and CPU makes the whole difference than having less. PubCoder is a “digital-first” authoring tool, with this expression meaning it is built to create digital content output, so you’re working with 72 dpi layouts. One may argue: hey, these need to manage high resolution assets, especially when it comes to printed publications.

There must be a reason why most of DTP tools are desktop apps: Adobe InDesign like QuarkXPress, just to mention the most well-known.

This post is not to defend desktop apps per se, but to argue why we chose to develop an authoring tool for interactive content as such, and - secondly, and most important - to show that a desktop tool and the web may well live perfectly together, providing the most of both environments for the scope PubCoder is designed. The arguments in support seemed coherent with the idea that desktop software, generally speaking, is “antique”, vs the web and its infinite possibilities - always up-to-date, no hard-disk space, collaboration, efficiency and the magic word: “cloud”. Here’s a post that explains what it’s all about). Many PubCoder users have asked us why didn’t we develop a software online.