Looking around, the cheapest I found was $2.62, if you buy a reel of 3000 of them [1]. It's definitely a nice price, but saying something costs two bucks implies maybe up to two and a quarter each, not when it's closer to three.
The LPC54100 series will be available... in the first quarter of 2015, with pricing starting at USD $1.99 in 10K quantities.
If you came from the future to inform us that NXP lied about their chips costing $1.99 in 10K quantities in 2015, then your beef is with the NXP marketing department, not minthd.
minthd is just relaying a number he read in a news article, which in turn relayed it from a NXP press release.
I completely missed that in my reading over the article, which was why I ended up searching for and linking to an aggregator that shows retail pricing.
Still no support for multiple pages? Is it possible to vote for such feature?
I'm really glad to see progress on SVG and hope this will finally make Mozilla to support SVG Tiny Fonts. This bug on their Bugzilla is 11 (!) years open:
It's not "image format file" - it is Scalable Vector Graphics format, there was pageSet in SVG Print draft already. It would be useful because a graphics (text layout) may span several pages, like in PDF.
I'm not sure exactly what you had in mind, but there is a CSS proposal to support paging in general on any kind of content.
For example if you had a very tall SVG image, you would constrain the height of the block that it was in, and set the overflow-style to paged-y. The browser would then provide some form of control for you to page vertically through the content in that block.
This stuff is currently documented in the GCPM module, but I suspect it will move somewhere else eventually.
Well Wikipedia disagrees with you since it states that SVG is a "vector image format" (not that wikipedia could not be wrong anyway).
I would consider printing to be another story though. It is possible to have a page size that spans to several pages when printing, but still it represents just one page.
PDF is not the best analogy because it was designed to be a document format from the beginning.
It is arguably that graphics and image are equivalent for this matter, on the basic meaning both terms imply visual presentation and none of them state a requirement for multi page.
Anyway, I will stop here because this thread is reaching the futile point.
What I don't understand is why Google doesn't have an open source PDF viewer? I mean, Chromium renders OpenGL, decodes movies, contains fastest JavaScript VM and it cannot view PDFs? Given what they did to JavaScript speed, can you imagine what viewer they would be capable of producing of? At least they should join Mozilla on improving pdf.js, IMO...
Chrome already has its own PDF viewer, presumably implemented in C or C++ or whatever, so they probably don't care about making it available for Chromium. Perhaps they bought the rights to the source code they based it on, and are unable to open source it.
Can someone explain to me what does it mean to "renew" the license? If I pay for the license now, assuming the world does not end tomorrow, will I have to pay for it again next year? How much?
The renew is for the subscription license for upgrades. With some of the applications you can get all the updates for free for a year and then you would have to buy a new subscription if you want newer versions if you don't want to pay any more you can continue to use the version you have until the end of the world.
The renewal is optional. You would still be able to use the builds released, during your valid subscription period after it ended. But in case you wanted to use builds that will be released after your subscription ended, you would have to go for a renewal.
