I haven't tried it myself, but I have heard mention of [link] Screenhunter Free at work.
Hermanos! The devil has built a robot!
Numero Cinco ,'The Cautionary Tale of Numero Cinco'
Buffistechnology 3: "Press Some Buttons, See What Happens."
Got a question about technology? Ask it here. Discussion of hardware, software, TiVos, multi-region DVDs, Windows, Macs, LINUX, hand-helds, iPods, anything tech related. Better than any helpdesk!
DCJensen - May 21, 2012 5:21:08 pm PDT #20114 of 25501
All is well that ends in pizza.
§ ita § - May 21, 2012 5:23:58 pm PDT #20115 of 25501
Well not canonically, no, but this is transformative fiction.
Thanks, DCJ. I'll give that a shot tomorrow.
tommyrot - May 22, 2012 8:20:32 am PDT #20116 of 25501
Sir, it's not an offence to let your cat eat your bacon. Okay? And we don't arrest cats, I'm very sorry.
So, anyone develop web pages for the iPad?
So I put this in the html head:
<meta name="viewport" content="width=device-width" />
Which is supposed to make the webpage take up the full screen on any iOS device, right? But it doesn't--just 1/4th of the screen, and there's whitespace that fills up the rest of the screen. (ETA: It works correctly on an iPhone.) If I shrink the page down, the whitespace shrinks too, and no longer fills the whole screen.
What am I missing?
Jon B. - May 22, 2012 8:39:48 am PDT #20117 of 25501
A turkey in every toilet -- only in America!
Is this the problem, Tom? [link]
tommyrot - May 22, 2012 8:52:17 am PDT #20118 of 25501
Sir, it's not an offence to let your cat eat your bacon. Okay? And we don't arrest cats, I'm very sorry.
Is this the problem, Tom? [link]
Interesting. But I don't think so.
If I change
<meta name="viewport" content="width=device-width" />
to
<meta name="viewport" content="width=480" />
the page now fills the full screen, as it's about 480 px wide. So it is responding to the setting. But then it's too big to fit on an iPhone.
Hmmm... I still seem to be confused on this "viewport" thing....
tommyrot - May 22, 2012 9:16:02 am PDT #20119 of 25501
Sir, it's not an offence to let your cat eat your bacon. Okay? And we don't arrest cats, I'm very sorry.
Well, I just ran my page in web-app (fullscreen) mode and I do see the issue you linked to.
This is just a demo--not sure if we want web-app mode or not.
amych - May 22, 2012 10:23:35 am PDT #20120 of 25501
Now let us crush something soft and watch it fountain blood. That is a girlish thing to want to do, yes?
Have you tried adding initial-scale=1 to the viewport tag?
tommyrot - May 22, 2012 11:16:46 am PDT #20121 of 25501
Sir, it's not an offence to let your cat eat your bacon. Okay? And we don't arrest cats, I'm very sorry.
Have you tried adding initial-scale=1 to the viewport tag?
Yeah, if I use that, on the iPad it starts out small.
But I do need "initial-scale=1.0; maximum-scale=1.0;" for the iPhone, so we may just have to leave it that way for the demo.
tommyrot - May 22, 2012 11:40:35 am PDT #20122 of 25501
Sir, it's not an offence to let your cat eat your bacon. Okay? And we don't arrest cats, I'm very sorry.
Talked to my boss. We're not gonna worry about how things look on the iPad for now.
§ ita § - May 22, 2012 7:31:31 pm PDT #20123 of 25501
Well not canonically, no, but this is transformative fiction.
I'm having a caching issue somewhere between my Mac and my NAS.
It's slow--I get it, apparently I have way too many files in the folders, but that's my web site folder structure and without a lot of coding it's not changing. But when I navigate to the one in question with finder, it takes *minutes*--not to load the file list, but to actually bring it up to date. I saved four images there 8 minutes ago, but Finder is just showing them now, and Filezilla, the umpteenth FTP application I've tried flat out refuses to show anything in there from May.
This is 2113 files, FTR.
Most of the OS X FTP clients have choked listing the folders, BTW--either system hangup, or list not populating for minutes, or list not updating like mentioned above.
Is my NAS to blame? Is the OS caching? SMB? Is there anything I can tweak *anywhere* to address this?