this is very, very cool
This topic is locked from further discussion.
Just got the update notification. Great changes, everything works as it should. The only complaint is the GB Bumper sound. It's too quiet compared to the other ones.
Great job, keep it up!
Yup, turns out it's really difficult to get a very good sample from the video and get all the levels right. I doubled the volume from the bumper and it'll be on the next update, hopefully that will be enough.
Posted on NeoGAF.
This is amazing duder, fantastic work. I just installed it so I haven't seen it in action yet, but it sure is handy. I think there's a couple things you could do to make the UI look a little nicer (like removing the border if that's possible and using a slab serif for the video title like the site), but the only things that seemed off to me was that the light theme is possibly a bit too dark, and the volume of the bumper notification, which you already addressed. So basically, you rock!
@beepmachine: Thanks for the feedback duder! Regarding the border, there's nothing I can do there. That is as low as I can go and every chrome popup extension have that border. You are totally right about the light theme, it was kind of an afterthought to begin with and it looks half assed compared to the dark theme. I'll work on it when I have the time. :)
@panpipe: Not really a bug, more like an oversight on my part since I don't have any high DPI monitors around to test. Are you up for some testing? If so, PM me so you can have access to the dev build. I don't really know where I'm supposed to put a higher dpi version of the icon since the extension is pulling that from a simple line in the manifest file but I'm assuming it works like a favicon. Gonna need your help on this one.
I pushed a minor 1.2.1 update that includes the new bumper sound (which still sucks TBH) and a fix for a minor schedule bug. I've been busy lately and really didn't have the time to work on the extension. I've also been working on a second chrome extension for my personal use, some Chrome UX improvement and not gb-related, and that is taking a lot of my spare time for now. That and South Park :P
Still, I'll keep improving the code until the API comes around.
For HiDPI screens, you just need to include a double-sized version of the icon as well, where in this case double is that of a 38px icon, so you want a 76x76px icon. In your manifest, create a dictionary for both "19" and "38" with "38" having the retina icon:
It's pretty straight forward. I'd definitely suggest doing this because as it stands, the current icon is nearly illegible on my Retina Macbook Pro screen.
@andorski: It looks like the recent server move may have broken it. The new servers appear to be redirecting the extension's YQL queries. It may need to be adapted to use a YQL query more like this one or use an alternate scraping method. (cc @andmm)
Sorry guys, as Chaser mentioned recent changes to the site broke the extension.
Good news is, @mrpibb is now handling the API stuff that I need so this should fix pretty much every issue with the extension and give me some room to work on improvements and the Firefox port.
For now I recommend using Chris Harris's Java app and I'll give you guys a heads up once it's working again.
Also, just to let you guys know that the extension is open source:
If anyone wanna contribute or fork it, feel free to do it :)
I might push a quick update to fix some OSX issues but we'll see.
As some of you may or may not know, @mrpibb removed the server's exception for YQL which once again broke this. This extension and YQL were basically doing a DDoS on Giant Bomb and crashing the site. There's a new version where I removed all of the YQL stuff that is currently awaiting @andmm to merge and release.
I published the new version on the chrome store so it should update for you guys shortly.
After the accidental "DDoS" there's no other option other than getting rid of YQL, which is a good thing. Chaser provided an alternate version that seems to be working fine so far although it is still largely untested. Please let us know of any bug you come across.
Version 1.2.6 Release:
- Fixed wrong time zone issue
- New way of displaying the date
- New notification sound "Small Business Man"
- Removed the save button, now changes are saved automatically
- Minor fixes
Schedule is now so you should get the same date you get from the site. But instead of just displaying the raw date I'm doing a bit of filtering to make it easier to read:
I got rid of the save button and did some minor fixes. Users with HDPI monitors should be seeing an improved version of the icon instead of a blurry mess, if you're not then drop me a message. Also improved the popup border for OSX users, should look decent now.
Still no filters and light theme is a wip (pretty much broken on osx) but everything else should work fine.
As always, let me know if you guys find any bugs or weird behavior. I appreciate the feedback :)
Is it just me or is the audio quality on the GB Bumper really low?
Seems like it. Also, it's the only usable sound since the other ones are suuuuuuuuper loooooooooong.
But other than that, the extension works like a dream. Thanks and keep it up, duder! :D
Moderation is a private matter, so we would prefer that the circumstances of any and all moderation actions not be discussed publicly on the forums. If you take issue with some moderator action, feel free to contact the mods via PM or e-mail at email@example.com. If you feel there is an issue with a particular mod, feel free to contact Rorie via PM or e-mail at firstname.lastname@example.org. A reminder on our official policy in the forum rules:
Posting negative threads or comments about moderators or staff members: If you have a problem with a mod decision, send the mods a PM asking for more information. If you have an issue with a specific mod, contact our community manager Rorie. If you create threads encouraging people to complain about mods or members of staff, they will be removed and your account may be subject to moderation.
Also, please understand that we never take actions such as a permanent ban lightly. We try to give users every opportunity to avoid a ban, and we only issue bans after lengthy discussions on the matter.
Seeing as the user in question is now using his Chrome extension to spread shit about us, and this thread has now devolved into speculating as to the circumstances of his ban, I'm going to go ahead and lock it up.
I'd like to reiterate what Chaser said: This ban was the result of a lengthy private conversation that took place over several days. If anyone has any concerns regarding the way the site is moderated they are welcome to contact a member of staff.