Vertical tabs without the 'tree' aspect (at least when I last used Vivaldi). Firefox with Tree Style Tab extension is still the best option I've found so far.
I switched from Firefox + Tree Style Tabs to Vivaldi + Tab Stacks and I mostly prefer it. The ability to tile tabs within a group is the killer feature, as well as it being much better supported by being native. Stack by host is great too. The big tradeoff is that you only get one layer of nesting, but I find it's generally worth that tradeoff for me.
I like it. As going through it though I had read so many in the list it provided. I see 6 is the maximum for a search, but it'd be useful to "neutralise" all the ones that have already been read to clear the stage a bit
Ah, Cartography. Works great in a small project. We ended up moving to standard anchors for almost everything, with some helper methods to handle things like pinning to superviews.
I imagine it was to reach Rank 14 in PvP rather than to hit the level cap. Even at the very start of the game, it took only 11-15 days in-game time to reach level 60.
I agree that it's likely the PvP rank. I could definitely see that taking a year or longer. Although plain old level 60 is still plausible - while it only took 11-15 days to level 60 if you knew what you were doing, a lot of us took longer than that because we took a roundabout route, whether out of fun or ignorance -- or leveled multiple characters before picking one, or maximized our tradeskills while leveling as seemed logical initially, etc.
This is simply not true. Vanilla WoW leveling was extremely slow. My nelf hunter took almost a year to get to 60, and I was an avid player. There's other commenters here saying similar things, so it's not just my possibly-faulty memory.
I had lots of issues using Day One with iCloud. I have the Mac app as well as the iPhone app, but they just wouldn't sync up correctly. Fortunately, after moving to Dropbox syncing everything cleaned up and I've not had a problem since.
Unfortunately this year's release has been... well, awful, from both a user's and a developer's perspective.
* APIs that were fine in iOS 7 are now broken on iOS 8 devices (that's the OS I'm talking about, not the SDK). 6 -> 7 contained the biggest UI changes of any release, and on an iOS 7 OS, apps built under iOS 6 still looked like iOS 6 apps. How it should be.
* Developers saying they have to get/renew both iOS and Mac developer programs, and then request a refund for the one they don't want.
* Requiring 5GB for an over-the-air installation, which given how most devices are 16GB, is terrible. There aren't many end-users that would go through iTunes for this.
* Shocking performance on 4S and iPad 2. I disagree with allowing users to upgrade on these devices. My iPad 2 was unusable; even swiping on the springboard was dropping frames everywhere. Apps taking 10 seconds to load. That's not a good user experience, keep them on 7.
* Apple silently changing their approval processes (not allowed to authenticate through Safari now - it has to be through a web view, which doesn't handle SSO, and is a lot less secure).
* HealthKit bugs.
* The whole 8.0.1 disaster. I couldn't believe this one.
I normally have 100+ tabs open. I use Firefox, with TreeStyleTab (vertical and collapsed tabs) and another extension (which I've forgotten the name of) that greys out unloaded tabs.
I pretty much use it as my reading list. I always forget to check Instapaper or whatever else I would otherwise use, so this at least keeps the names visible to me at all times.
That's a shame. I built one for fun and it works perfectly. There were a couple of tweaks I had to make to get dual monitors working, the sound working, etc, but it didn't take longer than a few hours.
I had a quick look, but to play a track, all I can see is a 30 second preview. Am I missing something, or can you not get the track data from this API?
> EDIT: Should've read the first subtitle... "Our Web API lets your applications fetch data from the Spotify music catalog and manage user’s playlists."
Streaming is only available through libspotify or the beta SDK on IOS. Rumors from #spotify on freenode indicate that the SDK for other platforms is still being worked on. But once it ships it will provide a minimal lib for streaming and the web API will do everything else.
The languages won't be in the same file. They can be in the same project, of course, but at least they'll be separated. It means you can write a class in one language and use it in the other language, without having to worry about it breaking.
