Posts Tagged ‘chrome’
Full-screen Browsing with Webkit on a Secondary Display
Posted in Web, on April 26th, 2010 by Carlos.
When I was working on my Status Board, I knew I had to find a full-screen browser that would open on my secondary display to make the whole thing work. Surprisingly enough, it was a lot easier said than done. Can you say niche problem? I know it is, but it’s the kind of information I wish I had found when I was researching browsers, so hopefully this comes in handy for some people. And if, you’re looking at building your own status board, this really may come in handy!
For starters, I knew I wanted to base my Status Board app on Webkit, and not Mozilla, or anything else for that matter. My second criteria was that I couldn’t use Safari. For one, it doesn’t support full-screen browsing, but also, I open and close Safari multiple times an hour, so I know I would unintentionally close my status board even when I didn’t intend to.
My first attempt was with Fluid. Being able to run the browser as it’s own process would allow me to prevent the unintentional closing of the browser window. I currently use it for Google Reader, and even my posts to Keys That Click and love having these windows be independent of my Safari browser. I was happy to see Fluid had a full-screen option. I was disappointed, however to see that it didn’t work properly with a secondary display. If you throw your Fluid browser window onto your secondary display, and enable the full screen mode, it throws the browser back to your primary display with the window/toolbars/etc. hidden. It just doesn’t quite work right. I tried various ways of opening and positioning the browser to see if I can make it work, but I eventually had to give up.
I then turned to Chrome which was the next logical choice. I’ll skip details on this one until later in the article, as I’d like to cover off a couple other browsers I tried.
My hunt was on for other webkit-based browsers for the Mac. Next I tried Shiira, an open-source webkit browser. It to has a full-screen mode. Unfortunately, when I opened my status board in full-screen on my secondary display, the screen went completely white. Looks like theirs some bugs there that need to be figured out. In fact, as I’m writing this article, and am trying to replicate the issues I ran into, the full-screen mode isn’t working properly on my primary display either. It tries to open up the window on my secondary display, but it shows up positioned many hundreds of pixels off center. It also didn’t seem to allow launching in full-screen mode, which would be ideal.
My search continued and I stumbled upon Plainview, by the Barbarian Group. On their FAQs, they quite simply claim Plainview to be a full-screen web browser. Thinking I found the holy grail of full-screen webkit browsers, I gave it a shot. Given that it is meant to be run solely as a full-screen browser, it obviously has the ability to launch in full-screen mode. But once again, having dual displays created a problem for the app. After moving the window to my secondary display, and trying to start it up, it goes to full-screen on my primary display. I did bring this point up to the developers, and it is a known bug that they are working to fix. Apparently it is a much trickier issue than it sounds. I’ll be checking back with them to see if they fix this feature in future builds.
After all that, I figured I’d have no other choice but to turn to Chrome. So what’s so bad about Chrome? Well to be honest, it’s not bad. It’s a decent browser and renders things well, and is stable enough (even in Beta). For starters, it’s full-screen browsing mode works on my secondary display. Given that the development team for Chrome must be sizeable-enough, I would have been surprised that this wouldn’t work properly. There is one thing that I wish it had though, and that is the ability to launch the application in full-screen mode. I currently have my status board set to the homepage, and have Chrome launch on system startup. I, however, have to manually enable full-screen mode. Given that I have to do it typically only once a day, it’s not that much of a problem. But still, it would be nice to have it launch in that mode automatically. Another plus, that it has even has over Safari, is that it supports inset CSS3 shadows, where, it seems that Safari currently doesn’t! As I used a couple of inset shadows, this was a welcome feature.
So there you have it, a quick run down on full-screen browsing with webkit browsers on a secondary display.
My Very Own Panic-inspired Status Board
Posted in Design, on April 13th, 2010 by Carlos.
[Update: You can check out a Live Preview of the Status Board by reading my post, Panic-Inspired Status Board Live Preview Using HTML5 and contentEditable.]
I recently picked up a beauty of a monitor (Dell U2711) which left me with my 24″ Samsung looking for a home. Given that the displays are very different, I wasn’t truly digging the two monitor side-by-side idea, but did want to do something with it so I would have it handy in case when having two monitors makes life easier (working with presentation documents seems to make me wish I had the second monitor).
Anywho, I started to think about the Status Board that Panic created and blogged about a while back and thought I could do something similar to replace the white board I have next to my desk. In fact my second monitor is currently blocking the view of my white board, so I only found it appropriate! I basically wanted a glorified to-do list split up by clients, while having some handy information at my fingertips (time, weather and Twitter feeds). I had and still have some delusions of grandeur which would make this thing fully AJAX enabled where I can drag and drop items and lists, but I had to start somewhere, and I’m not quite there yet. The DIV’s that contain the lists do expand as you type more in, and the DIV’s themselves will automatically position them self in the page columns as the lists grow. It is by no means done, as I have several more tweaks I’d like to make to it.
I will likely break out how I created the Status Board over a few blog postings so I don’t glance over too many of the details, but here’s a quick overview of the elements I used to create it:
- The Status Board is really just a HTML page set to full-screen at 1920×1200 resolution . I had to use Chrome for this as other browsers/methods failed with the two displays. I also wanted to keep it based on Webkit, so I didn’t look at any Mozilla alternatives.
- Several helpful jQuery scripts and plugins including:
- The really nifty HTC-esque clock and weather that is displayed in the corner (jDigiClock)
- Real-time Twitter feed using Juitter
- HTML5 properties such as contentEditable to make the lists editable right on the screen, and localStorage to keep a copy of the list stored on the local machine (really only did this as I need some assistance with saving it to a mysql database)
- CSS3 layout properties such as columns, rounded corners, opacity and shadows
I must say, designing a site that you can control the audience, browser, resolution – everything – was fun, but surprisingly challenging. Old habits die hard, I suppose, but I really shouldn’t get use to developing sites for only one platform.
I’m hoping that this will provide a clever use of a secondary display and that I actually do wind up using it! I’ll do my best to share my findings as I enhance the web app further, at the same time asking for help if anyone is willing to provide it!
Browser Wars: Chrome Surpasses Safari
Posted in Web, on December 15th, 2009 by Carlos.
It looks like Chrome has sneaked past Safari as the 3rd most popular browser according to Net Applications. IE currently dominates at 63.6%, followed by Firefox at 24.7%, Chrome at 4.4% and Safari at 4.37%. Although I’m a fan of Safari, I’m glad to see that Webkit browsers as a whole are gaining popularity. [via Tuaw]
Google Chrome Beta for Mac Released
Posted in Web, on December 8th, 2009 by Carlos.
Google has made available a beta version of the webkit based browser, Chrome. I had downloaded an earlier release for some testing and it seemed to run well. I’ll probably stick to Safari though, only firing up Chrome when I accidentally click the wrong icon. My only hope is that Chrome becomes more successful on the Windows side of things so people move away from Internet Explorer. I have downloaded it and it feels pretty snappy and responsive, more so than FireFox even, but then again, I’ve always found FireFox to load up too slowly on the Mac compared to Safari. Go download it now.
Will you be switching?
5 Comments »