Am 13.04.2012 17:40, schrieb Jenna Fox:
An A4 piece of paper has a little over 9kb of data storage if storing in
binary at 300dpi
A4 is about 21*30 cm², i.e. 630 cm² or 97.65 sqin. 300 dpi means 90,000
dpsqin or about 8.788 MdpA4. Without accounting for encoding,
redundancy, synchronization
LOL! Good to know, if I ever need to do those things :-)
An A4 piece of paper has a little over 9kb of data storage if
storing in binary at 300dpi
On the other hand, Camping is already far too big to fit entirely in
a QR code. It would take as many as TWO QR codes to store camping in
rack has a minimal file-server [0]
0.
https://github.com/rack/rack/blob/6496241b25daa20fd9dd736119dc39bdac54869d/lib/rack/file.rb#L70
ive been usin it on my phone to do the basics, it kind of chokes on 128M
podcasts as a mediaplayer
An A4 piece of paper has a little over 9kb of data storage if storing in binary
at 300dpi
—
Jenna
On Saturday, 14 April 2012 at 1:09 AM, Dave Everitt wrote:
There's a crucial point here... if 3k (the old 4k) is a 'proof of concept'
and a great exercise in programming skill, it isn't
I agree, I'd like to see the way Camping works to grow in to something much
more usable. Perhaps a fork is a good idea because the legacy would remain and
all. But then in the fork we could deal with things that might be kind of
annoying at times. And grow it with a steady pace.
If we'd fork
On the other hand, Camping is already far too big to fit entirely in a QR code.
It would take as many as TWO QR codes to store camping in it's entirety.
—
Jenna
On Saturday, 14 April 2012 at 1:40 AM, Jenna Fox wrote:
An A4 piece of paper has a little over 9kb of data storage if storing in
For me, this also depends on what Magnus - as the main Camper ninja -
thinks - DaveE
I agree, I'd like to see the way Camping works to grow in to
something much more usable. Perhaps a fork is a good idea because
the legacy would remain and all. But then in the fork we could deal
with
The problem is basically this:
Sometimes you want to reference static files, and other components of your
site. I have a Gallery app mounted at http://creativepony.com/gallery/ and it
causes me all sorts of trouble. Often times to reference static files I end up
needing to use /../ in URLs
On Thu, Apr 12, 2012 at 15:59, Jenna Fox a...@creativepony.com wrote:
The problem is basically this:
Sometimes you want to reference static files, and other components of your
site. I have a Gallery app mounted at http://creativepony.com/gallery/ and
it causes me all sorts of trouble. Often
bin/camping is great but it's not usually a good way to deploy an app on a
server - it tends to be more for development. Putting functionality in to
bin/camping which belongs in camping core is like wearing a backpack filled
with hydrogen while having your weight checked. 3kb is great and all,
10 matches
Mail list logo
