86 karma · joined September 25, 2011
tomspencer.dev meet.hn/city/gb-Bristol
See the following for more information:
https://vercel.com/docs/serverless-functions/introduction#lo...
I tried a few solutions earlier in the year for a side project (vercel, netlify functions, Cloudflare workers, begin) and found vercel to be the outstanding choice for developer experience, features (wildcard DNS for example is fully supported on their free plan) and support.
There are a number of scripts out there which download the ‘picture of the day’ and store it locally. You can then set your computer to scroll through these images every so often. Here’s the one I use: https://github.com/thejandroman/bing-wallpaper
> My prediction is that Xamarin will come up with its own GUI abstraction framework in future, along the lines of SWT. It is a compromise; but one which delivers a lot of value to developers who want to create cross-platform apps with the maximum amount of shared code.
This will almost certainly create the 'uncanny valley' which the author refers to in an earlier paragraph.
I consider the fact that Xamarin has two APIs for the two platform UIs a real advantage. You can still write your business logic once - so the time to create an iOS and Android app reduces from 2 to 1.x, and you still get the benefit of a fully native feeling app.
Quick question - I just tried the demo on IE on a Nokia Lumia 710 running WP 7.5 Mango, and there was no difference between A and B. Do you have any idea why FastClick might not work on Mango?
4. Framework / Library size. I'm turned off by many JS MV* Libraries due to their larger size. Backbone is very small and lightweight - perfect for mobile web apps.
It takes the approach of setting a cookie when the page first loads with the viewport size, determined through media queries. Every request to the server then includes this cookie.
When an img is requested (as an <img> tag or through CSS background-image) the cookie is read to determine the viewport size of the client. The PHP script then serves up the most appropriate image size to the client.
The only thing you really need to do is add the .htaccess rule (to intercept image requests and route them through the PHP script), the php script itself and the highest resolution you need for each image. The script takes care of scaling down the image for smaller screens, caching them for later use.
I like the way this requires nothing on the client side, other than a cookie being set. All the heavy lifting is done on the server.
One suggestion: make it responsive. The design lends itself well to mobilising: shrink the map view, put the columns into tabs, etc. This would be an even better resource for using when you are out and about, especially as it could use the HTML5 geolocation API to work out where you are and what is close by.
Great work!
One idea I had was to take the CSS from Sencha /KendoUI / jQTouch and combine with the components above to create a 'Backbone Mobile' framework. I just haven't had the time yet to figure out if this would work.
I regularly work more than 40 hours a week, not because I have to, but because I want to learn. One day I'd like to go freelance or perhaps start up a business, but I need to skill up first. I'm lucky that I have a job in my chosen sector of mobile web development, something which pays me to learn about the technologies I am passionate about. I am seizing the opportunity to learn as much as possible so I can be in a position to just work when I want to in later life.
IMO the author is looking at this from an experienced point of view. Juniors and those starting out often have no choice but to work a little longer to get where they want to be in 20 years time. There's nothing wrong with that, surely?
On the face of it, CORS supports this by setting withCredentials: true on the XHR object being sent over the wire. But as I was building a PhoneGap app, the files were being loaded using the file:// protocol, which has the side-effect of setting the Origin header to null whenever you make an AJAX call. According to the CORS spec, when using withCredentials, you must set the response header Access-Control-Allow-Origin on the server to something _other_ than the wildcard *. In this case, it would need to be my Origin. But since my Origin was null, I was stuffed, and I don't think that what I was trying to do, could be done.
Do you think EasyXDM might help here?
(The scenario is explained in more detail on Stack Overflow: http://stackoverflow.com/questions/9103876/cors-cookie-crede... )
http://documentcloud.github.com/backbone/examples/todos/inde... http://documentcloud.github.com/backbone/docs/todos.html http://recipeswithbackbone.com/
That being said, I've always found the best way to learn, is to do. Come up with an idea for an app and build it using Backbone, with the help from the resources above. You'll learn a lot.
From the article:
' ... mobile browsers will wait approximately 300ms from the time that you tap the button to fire the click event. The reason for this is that the browser is waiting to see if you are actually performing a double tap. For most buttons we are developing we know that there is no double click behavior that we want to handle, so waiting this long to start acting on the click is time wasted for users. '
The article goes on to discuss how to mitigate against this problem. jQuery Mobile's solution is to use virtual events to listen for touch events rather than mouse clicks. Try listening for vmouseup instead of vclick, this could solve the issue. See http://jquerymobile.com/demos/1.0.1/docs/pages/page-scriptin... for more details.
Just wondering if you considered using RequireJS instead of namespacing? Backbone plays quite nicely with RequireJS if you use James Burke's version which has been forked to be compatible: https://github.com/jrburke/backbone/blob/optamd/backbone.js
More info here: http://jcreamerlive.com/2011/12/09/backbonejs-modular-app-us...
I've often wondered why computers in general still persist with black text on a white background. I'm convinced in 50 years time there will be legions of people with eye problems that could have been avoided by just inverting colours on active displays.
For this reason I only like ePubs too as you can invert the colours easily when reading on a tablet.
Kudos to Eliot for coming on and answering your phony accusations. I feel sorry for him though as he has obviously spent a great deal of time in responding, when he could have been doing other important things, like fixing urgent bugs. As others have pointed out, this is the mark of a company who take very good care of their customers. Customer service is what differentiates chiefs from cowboys.
HN is an important community resource, especially for people with little startup / dev experience. I would urge you to think next time before being so irresponsible.