A better mobile version of HN. Please review my weekend project
21–30 of 53 posts
Re: A better mobile version of HN. Please review my weekend project
#22Re: A better mobile version of HN. Please review my weekend project
#23EDIT: Oh, and thank you! It really seems to be better than iCombinator.
Re: A better mobile version of HN. Please review my weekend project
#24An icon for iPhone users would be nice... EDIT: Oh, and thank you! It really seems to be better than iCombinator.
EDIT: Duh... HN itself has one. I'll use it.
EDIT: Ok, I added it. Thanks for reminding me about this.
Re: A better mobile version of HN. Please review my weekend project
#25Re: A better mobile version of HN. Please review my weekend project
#26For some reason I can not zoom on that page on my Nexus One. Is that intentional, and how is it done? I can zoom on other web sites. I guess links could be bigger - I tend to zoom on web sites to hit the smaller links, and since it is not possible on your page, it might become an issue.
On the iPhone, and I think also on Android devices, you can prevent a page from being zoomed withe the following meta tag : But this tag isn't being used here, as far I can see.
Re: A better mobile version of HN. Please review my weekend project
#27Re: A better mobile version of HN. Please review my weekend project
#28Re: A better mobile version of HN. Please review my weekend project
#29http://www.icombinator.net/ I really wish there was a way to comment and vote from the interface, though.
I really like icombinator but I wanted to address some problems and add new features (View the article text, collapse/expand comments, and return to the previous position when using the browsers back button).
Re: A better mobile version of HN. Please review my weekend project
#30How does this work?
Works just about the same way for the comments , except it adds some additional functionality like collapsing comments. With the nature of comments being nested, a recursive function worked really well on rendering the output.
The article text functionality uses the algorithm from arc 90's readability project, which is in javascript. I used the main idea behind their readability algorithm for this, except mine runs server side (C#) where theirs is all done on the client.