Episode 24 of The SitePoint Podcast is now available! This week your hosts are Patrick O’Keefe (@ifroggy), Stephan Segraves (@ssegraves), Brad Williams (@williamsba) and Kevin Yank (@sentience).
SitePoint Podcast的 第24集现已发布！ 本周的主持人是Patrick O'Keefe( @ifroggy )，Stephan Segraves( @ssegraves )，Brad Williams( @williamsba )和Kevin Yank( @sentience )。
You can also download this episode as a standalone MP3 file. Here’s the link:
您也可以将本集下载为独立的MP3文件。 这是链接：
SitePoint Podcast #24: Those Frames are Ironic (MP3, 33.8MB)
SitePoint Podcast＃24：这些框架具有讽刺意味 (MP3，33.8MB)
Here are the topics covered in this episode:
以下是本集中介绍的主题：
tr.im nearly shuts down, short URLs in question
tr.im即将关闭，有问题的短网址
tr.im R.I.P. (tr.im)
tr.im RIP (tr.im)
Tr.im Cuts Off Bit.ly’s 301works Idea, Wants to Sell (TechCrunch)
Tr.im切断Bit.ly的301works创意，想出售 (TechCrunch)
tr.im Resurrected (tr.im)
tr.im已复活 (tr.im)
Tr.im Can’t/Won’t Sell, Goes Open Source, Blames Everyone (TechCrunch)
Tr.im无法/不会出售，开源，责备所有人 (TechCrunch)
Project Retweet: Phase One (Twitter)
转推项目：第一阶段 (Twitter)
Host Your Own Short URLs (SitePoint)
托管您自己的短URL (SitePoint)
Shorten This (Jeffrey Zeldman)
缩短此时间 (Jeffrey Zeldman)
Short URL plug-in
简短的URL插件
la petite url
小网址
Short URL auto-discovery
短网址自动发现
Yourls
尤尔斯
WP.me — shorten your links (WordPress)
WP.me —缩短您的链接 (WordPress)
Lessn (Shaun Inman)
莱森 (肖恩·英曼)
TweetBackup
鸣叫备份
Lifestream Backup
生命周期备份
How the Web Looked Ten Years Ago
十年前的网络面貌
Ten Web Sites, Ten Years Ago (SitePoint)
十个网站，十年前 (SitePoint)
Designer Add-ons for Firefox
Firefox的Designer附加组件
19 Firefox Add-ons for Designers (SitePoint)
19个适用于设计人员的Firefox附加组件 (SitePoint)
Firebug
萤火虫
Window Resizer
窗口大小调整器
Screengrab
屏幕抓图
Web Developer toolbar
Web Developer工具栏
ColorZilla
ColorZilla
HTML 5 Drag & Drop
HTML 5拖放
On HTML 5 Drag and Drop (Alert Debugging)
在HTML 5上拖放 (警报调试)
Cappucino
卡布奇诺
280 Slides
280张幻灯片
Host Spotlights:
主持人聚光灯：
Stephan: CracklE Summer Drive In
斯蒂芬(Stephan)： Crackle Summer Drive in
Brad: KISSmetrics
布拉德： KISSmetrics
Patrick: Blog World Expo
帕特里克： 博客世界博览会
Kevin: punypng
凯文： punypng
Kevin: The SitePoint Podcast episode 24, for Friday, August 21st, 2009: “Those Frames are Ironic”.
凯文： SitePoint播客第24集，2009年8月21日，星期五：“那些框架具有讽刺意味”。
Kevin: Hi, there and welcome back to the SitePoint Podcast – news, opinion, and fresh thinking for web developers and designers. I’m your host, Kevin Yank coming to you from SitePoint headquarters in Melbourne, Australia and I’m joined by my panel of co-hosts.
凯文：您好，欢迎回到SitePoint播客–有关Web开发人员和设计师的新闻，观点和新思路。 我是您的房东，凯文·扬克(Kevin Yank)从澳大利亚墨尔本的SitePoint总部来找您，我的共同主持人小组也加入了我的行列。
Brad: Brad Williams from WebDevStudios.
布拉德： WebDevStudios的布拉德 ·威廉姆斯。
Patrick: Patrick O’Keefe of the iFroggy Network.
帕特里克： iFroggy网络的Patrick O'Keefe。
Stephan: And Stephan Segraves from Houston, Texas.
斯蒂芬：还有来自德克萨斯州休斯顿的斯蒂芬·塞格雷夫斯。
Kevin: On this show today, we’ll be talking about Firefox add-ons for designers. We’ll be talking about 10 websites that are 10 years old, and we’ll be talking about HTML5’s new drag and drop feature… all this and more, including our host spotlights.
凯文：在今天的节目中，我们将为设计师介绍Firefox附加组件。 我们将讨论10年之久的10个网站，并讨论HTML5的新拖放功能……所有这些以及更多内容，包括我们的主机聚焦。
The first story today is to do with short URLs, right Brad?
今天的第一个故事与短网址有关，对吗，布拉德？
Brad: That’s right Kevin. We’re actually going to talk about tr.im which is a—I’m not sure how popular, but it’s a URL shortener that has been quite a bit at controversy surrounding in the past few days.
布拉德：是的，凯文。 实际上，我们将讨论tr.im ，它是一个-我不确定其流行程度，但是它是一个URL缩短器，在过去几天中引起了很多争议。
Basically, tr.im came out with a blog post and essentially shut down their entire URL shortener service and by doing so essentially dead-linked all of the short URLs that were out there currently using tr.im. So imagine if you’re using TinyURL or Bit.ly or whatever it may be and they all of a sudden go offline, all those links and tweets that linked to those URL shorteners are now dead.
基本上，tr.im带有博客文章，并且实际上关闭了它们的整个URL缩短服务，并且通过这样做基本上将当前使用tr.im的所有短URL进行了死链接。 因此，想象一下，如果您使用的是TinyURL或Bit.ly或它们可能是什么，而它们突然都脱机了，那么链接到这些URL缩短器的所有链接和推文现在都将消失。
Kevin: Yeah, that’s what they announced they were going to do, but thankfully they didn’t do it.
凯文：是的，这就是他们宣布要做的事情，但是幸运的是他们没有这样做。
Brad: They did for about a day and then the entire world started talking about it and then they realized, hey we’re missing all this great press.
布拉德：他们做了大约一天，然后全世界开始谈论它，然后他们意识到，嘿，我们错过了所有这些伟大的新闻。
Kevin: Oh wow! I didn’t realize they actually took down links. I thought they just announced they were going to do it.
凯文：哦，哇！ 我没有意识到他们实际上删除了链接。 我以为他们只是宣布要这样做。
Brad: Well, you know what; I think they took down the site and posted a message and said the links will stop working at so and so date. So I don’t think the links actually did end but they were— they had set a date saying they would die.
布拉德：嗯，你知道吗？ 我认为他们删除了该网站并发布了一条消息，并说这些链接将在某某日期停止工作。 因此，我认为这些链接实际上并没有结束，但是它们确实是－它们已经确定了一个日期，说它们将死。
TechCrunch and some other very large blogs wrote about it and featured them. I’m sure they got a rush of traffic and quickly after the announcement—I think like a day or two later—they were really pushing to sell their service, sell to somebody else who could then bring it back online. After that didn’t happen, they decided to actually bring their service up on their own. So they kind of rescinded what they said and decided not to drop their service. Then after about a week of all this back and forth they finally decided to go open source. It’s been quite a roller coaster ride with tr.im.
TechCrunch和其他一些大型博客对此进行了介绍并进行了介绍。 我确信他们在宣布之后很快就会获得大量的流量(我想像一两天后一样)，他们实际上是在推销他们的服务，卖给其他人然后可以将其重新上线。 在那没发生之后，他们决定真正地自己提供服务。 因此，他们有点放弃了他们的言论，并决定不放弃他们的服务。 经过大约一周的反复研究，他们终于决定使用开源软件。 tr.im挺过山车的。
Kevin: Especially in the TechCrunch stories—there’s been a lot of “he said, she said” around this; about Bit.ly, the competing short URL service that Twitter seems to prefer because they will auto-shorten any tweet that’s posted through the Twitter website using Bit.ly. There’s been stories about Bit.ly volunteering to buy out tr.im for a token amount of money and there’s a bit of nastiness going around about how much this service is worth and what a reasonable offer was. I don’t want to get distracted by that because I think there’s a really interesting story here about short URLs themselves and this is something that people have been warning us about for a while; that these short URLs that we rely on, these services are one day going to go away and it’s a bad idea to rely on them.
凯文：尤其是在TechCrunch的故事中，对此有很多“他说，她说”的信息。 关于Bit.ly ，Twitter似乎更喜欢竞争的短URL服务，因为它们会自动缩短使用Bit.ly通过Twitter网站发布的任何推文。 关于Bit.ly自愿以一定数量的钱购买tr.im的故事，关于这项服务的价值和合理的报价有些令人讨厌。 我不想为此而分心，因为我认为这里有一个关于短URL本身的非常有趣的故事，这是人们一段时间以来一直在警告我们的事情。 我们所依赖的这些短网址，这些服务有一天会消失，依靠它们是一个坏主意。
Stephan: Oh yeah, I completely agree. I mean, I used tr.im…
斯蒂芬：哦，是的，我完全同意。 我的意思是，我使用了tr.im…
Patrick: Sucker. Ha ha.
帕特里克：吸盘。 哈哈。
Stephan: …up until the day they said they were not going to work anymore.
史蒂芬：直到他们说他们不再工作的那一天。
Kevin: Ha ha ha! No, I used tr.im too. In fact, SitePoint used tr.im. Everything we posted from our blogs automatically onto our Twitter feed, we shortened with tr.im.
凯文：哈哈哈！ 不，我也使用过tr.im。 实际上，SitePoint使用了tr.im。 我们从博客自动发布到Twitter feed上的所有内容，都用tr.im缩短了。
Patrick: Well, it had great stat stuff, you know. So it’s like, oh, this is cool! It’s an easy-to-use service—whatever—and then they said they’re going to take it off and I’m like, “Well I can’t even go back and change the URLs that were in my tweets or anything like that because you can’t retrieve them, right? You can’t go back and edit them.” So I was like, “Well those are going to be dead.” So from now on, I’m either going to roll my own or figure out a different way to go about it.
帕特里克：嗯，它的统计数据很棒，你知道的。 就像，哦，这很酷！ 不管它是什么，它都是一种易于使用的服务，然后他们说将要删除它，我想，“好吧，我什至不能回去更改推文中的URL或类似的内容那是因为您无法检索它们，对吧？ 您无法返回并对其进行编辑。” 所以我当时想，“好吧，那些将要死了。” 因此，从现在开始，我要么自己动手，要么想出另一种方式来解决这个问题。
Kevin: We’ve switched to Bit.ly; in the midst of this drama we switched our preferred provider for short URLs to Bit.ly but I think you’re absolutely right that the right way to go here long term is that if you want short URLs you’re going to have to host them yourself. Because that way the only way your short URLs go down is if you yourself take them down. So in theory they’re just as stable as the rest of the content you’re publishing.
凯文：我们已经切换到Bit.ly。 在这部戏中，我们将首选的短URL提供商改为了Bit.ly，但我认为长期正确的做法是，如果您想要短URL，则必须托管他们自己。 因为那样一来，短URL唯一出现故障的方法就是您自己删除它们。 因此，从理论上讲，它们与您要发布的其余内容一样稳定。
The problem then becomes how do you keep other people from linking to you with these short URL services? It’s one thing to provide your own short URLs and use them yourself but other people who link to you… What can happen even is people shorten your short URLs with one of these other services, which is what happens when you post through Twitter. You copy and paste even a short URL into Twitter.com and then they apply Bit.ly to it, no matter what. Potentially a shorter URL could be made longer by Bit.ly on Twitter. I don’t know why Twitter is doing this.
问题就变成了如何通过这些简短的URL服务阻止其他人链接到您？ 提供您自己的短URL并自己使用它们，但其他与您链接的人是一回事……即使人们通过其中一种其他服务缩短了您的短URL，也可能发生，这是您通过Twitter发帖时发生的情况。 您甚至将一个简短的URL复制并粘贴到Twitter.com中，然后无论如何，它们都会将Bit.ly应用于该URL。 Bit.ly在Twitter上可能会缩短URL的长度。 我不知道为什么Twitter会这样做。
Brad: Yeah, why don’t they keep it in-house and just build their own shortener?
布拉德：是的，为什么他们不将其保留在内部而只是自己制造起酥油？
Stephan: Exactly.
史蒂芬：是的 。
Brad: When I first got on Twitter a few years ago I remember it was all TinyURL and it was all automatic as well. You would paste in it and it would switch it over to TinyURL. At some point, they switched it to Bit.ly.
布拉德：几年前当我第一次上Twitter时，我记得那全是TinyURL ，也全是自动的。 您将粘贴其中，它将切换到TinyURL。 在某个时候，他们将其切换为Bit.ly。
Patrick: Well, if tr.im is to be believed, maybe it’s not worth it for Twitter to be a URL shortener, business wise. Maybe it’s not as feasible. They have their own stability issues as is. Do we really want them now providing the URL shortening service too? I don’t know. I think there’s a lot of shorteners out there, there’s a lot of options. Obviously they’ve chosen Bit.ly which will help Bit.ly but at the end of the day it’s yet to be seen if it’s a sustainable operation.
帕特里克(Patrick)：好吧，如果可以相信tr.im，那么从商业角度来说，将Twitter用作URL缩短程序可能不值得。 也许不可行。 它们本身具有自身的稳定性问题。 我们真的要他们现在也提供URL缩短服务吗？ 我不知道。 我认为那里有很多起酥油，有很多选择。 显然，他们选择了Bit.ly，它将对Bit.ly有所帮助，但归根结底，这是否可持续发展尚待观察。
Stephan: I almost have an issue with the short URLs in general just because, one, you can’t see where the URL goes without actually going to it or using a website that extracts the URL for you, right?
史蒂芬(Stephan)：一般而言，我对短网址几乎都有问题，只是因为，一个人如果不实际访问网址或使用为您提取网址的网站就看不到网址的去向，对吗？
Patrick: Or some sort of router to ride on.
帕特里克：或者可以骑的某种路由器。
Stephan: Yeah, exactly. So I think that it leads to a lot of confusion, one, and I think that it’s somewhat of a hassle. It would be nice if I could just post a URL into Twitter and Twitter said, “Okay we’ll ignore the URL,” but I know where that goes. That goes to spam, right? If they say, “We’ll allow URLs,” people just put URLs in into the tweet and that’s all it is.
斯蒂芬：是的，确实如此。 因此，我认为这会导致很多混乱，而且我认为这有点麻烦。 如果我可以将一个URL发布到Twitter，然后Twitter说“好吧，我们会忽略该URL”，那将是很好的选择，但是我知道它的去向。 那就是垃圾邮件，对吗？ 如果他们说“我们将允许URL”，人们只需将URL放入推文中，仅此而已。
Kevin: Can you explain that to me because people already put URLs in their tweets?
凯文：您能向我解释一下，因为人们已经在其推文中添加了网址吗？
Stephan: What I’m saying is, is if Twitter just ignored the URL, no matter how many characters it was and didn’t count it as a character, then they would allow the URL not to take up any space so you could have the full URL there and not eat up your 140 characters – which I think I would be okay with if they had some way of combating the spam.
史蒂芬：我的意思是，如果Twitter只是忽略了URL，无论它有多少个字符，也没有将其视为字符，那么它们将允许URL不占用任何空间，因此您可以那里的完整URL，而不会占用您的140个字符-如果他们可以通过某种方式来打击垃圾邮件，我想我可以接受。
Kevin: I would be totally okay with that. In fact, it looks like the recent announcements coming out of Twitter is that they’re going to start making retweets part of the protocol. So when you want to repeat a tweet that you enjoyed or that you support or whatever, no longer will you have to put “RT” and then the person’s @name at the front of your tweet. That will actually become part of the protocol. You can write whatever you want and that tweet will be flagged as a retweet of the original without using any of your 140 characters. They need to do the same thing for links, you need to be able to attach a link to a tweet without using characters.
凯文：我完全可以接受。 实际上，Twitter 最近发布的公告似乎表明它们将开始使转发成为协议的一部分。 因此，当您想重复自己喜欢或支持的推文时，您不再需要在推文的前面放置“ RT”，然后是该人的@name。 这实际上将成为协议的一部分。 您可以编写任何内容，并且该推文将被标记为原始推文，而无需使用任何140个字符。 他们需要对链接做同样的事情，您需要能够在不使用字符的情况下将链接附加到推文上。
Stephan: I think that comes to the spam issue. So I don’t know Patrick if you had anything to say about that.
史蒂芬：我认为这是垃圾邮件问题。 所以我不知道帕特里克是否有话要说。
Patrick: I think that the new retweets is a good and interesting first step to this but I think the solution has to work with how Twitter works now. People copy and paste tweets, people retweet it by pressing in TweetDeck and they have their URL. So in some manner, these URLs have to be truncated whether it’s through a shortener or with some links they add an ellipsis at the end. How does that work with the retweet? How does that work with copy and pasting? Any solution needs to keep that at mind as well.
帕特里克(Patrick)：我认为新的转推是迈出良好而有趣的第一步，但我认为解决方案必须与Twitter现在的工作方式协同工作。 人们复制并粘贴推文，然后通过按TweetDeck推推它，然后获得其URL。 因此，无论是通过缩短器还是带有某些链接的URL，都必须将其截断，并在它们的末尾添加省略号。 转推如何运作？ 复制和粘贴如何工作？ 任何解决方案都需要牢记这一点。
Kevin: Yeah, Twitter has always been about simplicity and the more of these things they add to the service and the protocol, the more complicated it’ll get. If you had to paste a URL attached to your tweet in a separate field, that immediately makes it twice as painful to paste URLs. So I agree with you Patrick, whatever they do, it needs to maintain that simplicity of fire and forget that Twitter has of just pasting stuff into one field.
凯文：是的，Twitter一直是关于简单性的，它们添加到服务和协议中的东西越多，它就会变得越复杂。 如果您必须在附加字段中粘贴附加到推文上的URL，则立即使粘贴URL的痛苦增加一倍。 因此，我同意您的观点，无论Patrick做什么，都需要保持简单性，而忘记了Twitter仅将内容粘贴到一个字段中。
We’ll see where they go but for the time being I think we can all agree that if you can avoid relying on one of these third party URL shortening services it’s a good thing to do. So I wrote a bit about this in the Tech Times this week and what Jeffrey Zeldman has recommended is he uses WordPress for his site to write his blog. So he’s using a plug-in called the Short URL plug-in for WordPress, which looks relatively nice. It integrates straight into WordPress. It even provides statistics along the same lines as you get with these third party services and you just plug it right in and it immediately makes short URL for each one of your posts.
我们将看到它们的去向，但暂时我想我们都同意，如果您可以避免依赖这些第三方URL缩短服务之一，那是一件好事。 因此，我在本周的《技术时报》上写了一些有关此 的内容， 杰弗里·扎德曼(Jeffrey Zeldman)建议的是，他使用WordPress作为其网站来撰写博客。 因此，他正在使用一个名为WordPress的Short URL插件的插件 ，它看起来相对不错。 它直接集成到WordPress中。 它甚至提供与这些第三方服务相同的统计信息，您只需将其插入即可立即为每个帖子撰写简短的URL。
But there are a few other newer WordPress plug-ins and plug-ins for all sources of content management systems and blogging platforms coming out. Another one for WordPress, la petite url, it supports an exciting feature called short URL auto-discovery, which means in addition to creating a short URL for every post, it also puts a <link> tag in the head of your document that Twitter clients, in theory, could sniff this tag. When they need a short URL for a particular URL they’ll download the page and look for that <link> tag and if it’s present, they’ll just use that as the short URL.
但是，还有其他一些较新的WordPress插件以及用于内容管理系统和博客平台的所有来源的插件。 另一个适用于WordPress的网址是la petite url ，它支持一项令人兴奋的功能，称为短URL自动发现 ，这意味着除了为每个帖子创建一个短URL之外，它还在文档的开头添加了一个<link>标记 ，即Twitter从理论上讲，客户可以嗅探此标签。 当他们需要特定URL的短URL时，他们将下载页面并查找该<link>标记，如果存在，则将其用作短URL。
So this would go a long way towards making sure that when other people reference your content, they also use your preferred, self-hosted short URL. It would be great if even Twitter did that instead of using Bit.ly when it was available but this is all kind and still in theory, at the moment. It’s a proposed protocol. There’s a few sites out there that are doing it but there aren’t any Twitter posting tools that I’ve seen yet that handle short URL auto-discovery.
因此，这将有助于确保当其他人引用您的内容时，他们也使用您首选的自托管短网址。 如果甚至Twitter做到这一点也很好，而不是在可用时使用Bit.ly，但目前这还算是理论上的一切。 这是一个建议的协议。 那里有一些网站正在执行此操作，但是我还没有看到任何处理短URL自动发现的Twitter发布工具。
There are couple of other WordPress plug-ins you wanted to mention, right, Brad?
您还想提到其他几个WordPress插件，对吗，布拉德？
Brad: Yeah, there’s a fairly new that just came out called Yourls.org and this is actually a URL shortener that isn’t WordPress specific so it’s a series of PHP scripts—and I’ll work with it; I can handle PHP, MySQL, and mod_rewrite—but it also does have a WordPress hook as well.
布拉德：是的，刚刚发布了一个相当新的名字叫Yourls.org ，这实际上是一个URL缩短器，它不是特定于WordPress的，因此它是一系列PHP脚本，我将使用它。 我可以处理PHP，MySQL和mod_rewrite，但它也确实具有WordPress挂钩。
The reason I kind of like this one it’s two fold. The two developers that created it are pretty well-known in the WordPress community, Lester Chan and Ozh Richard. Also the fact that it has a simple, little API built into it so you can actually send and GET and POSTs to your specific API URL which you can set. You can validate with username and password and you can actually pullout short URLs and stats directly from the scripts, which is really cool. It makes it a little more extendable.
我之所以喜欢这个原因有两个方面。 创建它的两个开发人员在WordPress社区中非常著名，Lester Chan和Ozh Richard。 还有一个事实，即它内置了一个简单的，很少的API，因此您实际上可以将GET和POST发送和发送到您可以设置的特定API URL。 您可以使用用户名和密码进行验证，并且实际上可以直接从脚本中提取简短的URL和统计信息，这确实很棒。 它使它更具扩展性。
Also along the same lines with WordPress, it was announced recently that wordpress.com blogs are going to have a built in WP.me redirector. So every blog post created on wordpress.com will automatically have a WP.me short URL created for it that can be used when posting in Twitter and things like that. It’s also been noted that if you’re running self-hosted WordPress and you used the WordPress stats plug-in you can also get WP.me short URLs as well.
同样与WordPress相同， 最近宣布 wordpress.com博客将内置WP.me重定向器。 因此，在wordpress.com上创建的每个博客帖子都将自动为其创建一个WP.me短URL，该URL可以在Twitter上发布时使用。 还需要注意的是，如果您运行的是自托管WordPress，并且使用了WordPress stats插件，则也可以获取WP.me短URL。
Kevin: Oh! That’s good of them. I like that, that they don’t force you to use wordpress.com.
凯文：哦！ 那对他们很好。 我喜欢他们，因为它们不会强迫您使用wordpress.com。
Brad: Yeah, it’s the only two-letter .me domain in the world is what Matt Mullenweg said, of WordPress.
布拉德：是的，这是世界上唯一的两个字母的.me域，是马特·穆伦维格(Matt Mullenweg)所说的WordPress。
Patrick: Looking at this as a person who uses WordPress, the plug-ins look really cool and it seems like a nice idea, but I don’t know that I would trust myself to use WordPress for 10 years into the future any more than I’d trust a third party URL system because you’ll always be tied to that piece of software. And I love WordPress; I don’t see myself moving off of WordPress but I’d like to leave the opportunity out there.
帕特里克：作为一个使用WordPress的人，这些插件看起来真的很酷，这似乎是个不错的主意，但我不知道我会相信自己可以在未来十年内使用WordPress，而不仅仅是我相信第三方URL系统，因为您将始终与该软件捆绑在一起。 而且我喜欢WordPress； 我看不到自己要脱离WordPress，但我想把机会留在那儿。
So if I’m going to host my own short URLs I’m looking at something like Lessn, which Kevin pointed out in his article at SitePoint, Host Your Own Short URLs—something that is independent of the WordPress software that I can plug in, that can be separate, that I can take with me. Being the average webmaster, not being a programmer, I can’t write my own WordPress plug-in so I think that’s kind of the way to go for me, anyway.
因此，如果我要托管自己的短URL，我会看到类似Lessn的东西，凯文在他在SitePoint上的文章中指出， 托管自己的短URL —独立于我可以插入的WordPress软件的东西。 ，可以分开，我可以随身携带。 作为普通的网站管理员，不是程序员，我无法编写自己的WordPress插件，因此无论如何我认为这是我的理想之选。
Kevin: Yeah, any way you go you’re going to be setting yourself up for this piece of infrastructure, this library of short URLs that you’re going to have to carry forward into the future. Even with a service like Lessn—which is released by Shaun Inman, whose name we mentioned a couple of weeks ago in relation to his new RSS feed reader feedafever.com, but Lessn is his newest release—it’s a nice little URL shortener that you can host on any PHP/MySQL site but, again what’s the guarantee you’re going to be hosting on PHP/MySQL forever? Even then, it’s probably a safer bet you’ll be on PHP longer than WordPress but still you’re setting yourself up to have this ball-and-chain of links that you have to carry with you.
凯文：是的，无论采取哪种方式，您都将需要为这种基础设施，短URL库做好准备，以备将来使用。 即使有类似Lessn的服务(由Shaun Inman发布，我们在几周前就提到他的名字与他的新RSS feed阅读器feedafever.com有关 ，但Lessn是他的最新版本)，它还是一个不错的URL缩短工具可以在任何PHP / MySQL网站上托管，但是，再次保证您将永远在PHP / MySQL上托管？ 即使那样，您使用PHP的时间可能比WordPress更长，这可能是一个更安全的选择，但您仍在设置自己以拥有必须随身携带的这种球形链接。
What’s interesting to me is everyone who’s setting up their own short URLs is having to, in many cases, come up with a new short domain name for their site. Shaun Inman even; he’s got shauninman.com for his blog but he’s hosting his shortened links at shaun.in. If you thought people who are competing for short URLs before now, when everyone wants their own personalized short domain name, everyone is looking at these new two letter extensions that usually have to do with some obscure or not-so-obscure country. shaun.in, I suppose would be related to India—just off the top of my head there—but suddenly, we have no way of knowing what country a domain is actually hosted in because these country specific, top level domains are being abused to make short URLs.
对我而言，有趣的是，每个设置自己的短URL的人在很多情况下都必须为其网站提供一个新的短域名。 肖恩·英曼(Shaun Inman)甚至； 他的博客拥有shauninman.com，但他在shaun.in托管了缩短的链接。 如果您认为人们在此之前正在争夺短URL，那么当每个人都想要自己的个性化短域名时，每个人都在关注这两个新的字母扩展名，这些扩展名通常与某个默默无闻的国家/地区有关。 shaun.in，我想是和印度有关的-就在我脑海中-但是突然之间，我们无法知道某个域名实际位于哪个国家，因为这些特定于国家/地区的顶级域名被滥用了制作简短的网址。
Patrick: “Web developer Yank pays seven figures for kev.in.”
帕特里克(Patrick)： “网络开发人员Yank为kev.in支付了七个数字。”
Kevin: Geez! No! I have to register it before we post this show.
凯文：天哪！ 没有！ 在发布此节目之前，我必须先注册它。
Stephan: I see it though because I think what we’ve done is we’ve taken a pretty simple issue—dealing with Twitter—and we’ve turned it into this complex solution now where we’ve come around and we’ve realized this was dumb.
斯蒂芬：我看到了，因为我认为我们所做的是解决了一个非常简单的问题-与Twitter交易-我们已经将其变成了一个复杂的解决方案，现在我们已经意识到了这一点这太蠢了。
Kevin: Who is we? I blame Twitter.
凯文：我们是谁？ 我怪Twitter。
Stephan: I think we blamed Twitter a few shows ago, didn’t we?
斯蒂芬：我想我们在几个节目前都怪推特，不是吗？
Kevin: Yeah, I still blame Twitter.
凯文：是的，我还是要怪推特。
Stephan: I think we have to correct the problem. I’m guilty of it; using my short URL – that maybe I’ve posted in a tweet – in a post of mine, or something. So now I have to go back and edit that post with a full link to make sure that that doesn’t break in the future. I don’t know. I feel like we’re going to come to a point where Bit.ly dies, tr.im dies, and a bunch of web servers go down and no one can get anything on the internet because no one knows the full URL.
史蒂芬：我认为我们必须纠正这个问题。 我对此感到内;； 使用我的简短网址(可能是我发布在推文中)或我的帖子。 因此，现在我必须返回并编辑具有完整链接的帖子，以确保将来不会中断。 我不知道。 我感觉到我们将要到一个地步：Bit.ly死了，tr.im死了，一堆Web服务器瘫痪了，没有人可以在Internet上获得任何东西，因为没人知道完整的URL。
Patrick: To be honest, I’m going to keep using Bit.ly on Twitter until a service is in place or something is in place to replace it or to do it better. I’ve never used short URL services in my blog posts or in anything that’s long form beyond Twitter. So I’m okay there and I’ll continue to do that but as far as Twitter; I’m going to use Bit.ly. I’m not going to invest in my own service. I’m just going to keep doing what I’m already doing.
帕特里克(Patrick)：老实说，我将继续在Twitter上使用Bit.ly，直到有一项服务或有替代它或做得更好的服务为止。 我从未在自己的博客文章或Twitter以外的任何形式的简短形式中使用过短URL服务。 所以我很好，我会继续这样做，但就Twitter而言。 我将使用Bit.ly。 我不会投资自己的服务。 我将继续做我已经在做的事情。
Kevin: It seems to me that Twitter’s approach is to treat tweets as completely disposable. Does anyone get that sense? I’ve read things about they’ll start deleting your old tweets when you get to 3,000 or something like that, and now these new services and scripts have started popping up to back up your tweets because Twitter is going to throw them away. There’s a service called Tweetbackup.com and you can authorize it to crawl all your old tweets and back them up so that they don’t disappear, but it seems like Twitter doesn’t want you to think of tweets that way. They throw short URLs in that may break one day. They delete old ones without telling you. It seems like Twitter’s all about the moment and keeping tweets for posterity is not part of their grand plan.
凯文：在我看来，Twitter的方法是将推文视为完全可丢弃的。 有人知道吗？ 我读过一些有关它们将在您达到3,000左右时开始删除您的旧推文的信息，现在这些新服务和脚本开始弹出以备份您的推文，因为Twitter会将它们丢弃。 有一个名为Tweetbackup.com的服务，您可以授权它抓取所有旧的tweet并备份它们，以使它们不会消失，但是Twitter似乎不希望您这样想。 他们抛出简短的URL，可能会破坏一天。 他们删除旧的而不通知您。 似乎Twitter只是一时之间，保留后代推文并不是他们的宏伟计划的一部分。
Stephan: I kind of view it that way though. It’s like, “What am I doing now?”
斯蒂芬：我还是这样看的。 就像，“我现在在做什么？”
Brad: It’s too bad because everyone really referenced it as micro-blogging; but if you’re not keeping those posts as individual, short little blog posts then how can you call it micro-blogging?
布拉德：这太糟糕了，因为每个人都将它称为微博客。 但是，如果您不将这些帖子保持为个人的，简短的小博客帖子，那么您如何称其为微博客？
Patrick: Good point. Good point.
帕特里克：好点。 好点子。
Kevin: Yeah. I’m one of those freaks who backs up all my texts messages, Patrick.
凯文：是的。 我是备份我所有短信的怪胎之一，帕特里克。
Patrick: That’s great. That’s great. I’m sorry.
帕特里克：太好了。 那很棒。 对不起。
Stephan: People use text messages?
斯蒂芬：人们使用短信吗？
Kevin: Yes, I still do. I still do get text messages.
凯文：是的，我仍然这样做。 我仍然收到短信。
Patrick: You do have me thinking about backing up my tweets though because I do take value from Twitter. I do value them as mini blog posts and they are a picture of where I am in life at that moment—to be honest with you—and how I travel and what I do. So, it’s kind of a neat thing that I’m going to look into backing up for sure. Another service is Lifestream Backup and they are a pay service but one of those services might be getting my business.
帕特里克(Patrick)：您确实让我考虑备份我的推文，因为我确实从Twitter中获得了价值。 我确实将它们视为微型博客文章，它们是我当时生活中的一幅图片(老实说)，以及我的出行方式和工作方式。 因此，我要肯定要进行备份是一件很整洁的事情。 另一项服务是Lifestream Backup ，它们是一项付费服务，但其中一项服务可能正在帮助我开展业务。
Kevin: Tweets are one of those things that they have a certain amount of value at the moment, and then very quickly, that value goes down but over time that value is going to come back. In 10 years’ time; what you tweeted 10 years ago you’re going to feel so nostalgic about that. You’ll be like, “Oh, I wonder what I was doing 10 years ago. Wow, I was so crazy back then.” You may not care about your tweets in a week but in 10 years’ time you might want to get them, is what I’m saying.
凯文：推文是目前具有一定价值的东西之一，然后很快，价值下降，但随着时间的流逝，价值将恢复。 10年后； 您10年前发的推文会令您感到怀旧。 您会想，“哦，我想知道十年前在做什么。 哇，那时候我真疯了。” 我要说的是，您可能不会在一周之内在乎自己的推文，但在10年后，您可能想获得它们。
Stephan: Then I think you guys should move to Tumblr or something. I’m just one of these guys that I’m just, like, I’m keeping up-to-date … different things … something interesting I see… I don’t know if I’m ever going to reference it in 10 years. Maybe?
史蒂芬：然后我认为你们应该搬到Tumblr之类的地方 。 我只是这些人中的一员，例如，我保持最新状态……不同的东西……看到的有趣的东西……我不知道我是否会在10中引用它年份。 也许？
Patrick: That speaks to Twitter being different for different people. Some people will use it in one way and another in another and it’s all good. Some of us collect magazines, some of us collect tweets, some of us do something else. That’s life.
帕特里克(Patrick)：这说明Twitter对于不同的人而言是不同的。 有些人会以一种方式使用它，而以另一种方式使用它，这一切都很好。 我们有些人收集杂志，有些人收集推文，有些人做其他事情。 那就是生活。
Kevin: Well, speaking of what things will be like in 10 years’ time, we just got the news this week that Blogger.com turned 10 years old and that gave SitePoint blogger Jennifer Farley the inspiration to look back 10 years at some of the biggest sites on the Web at that time and what they looked like. We’ve got a blog post on sitepoint.com with screenshots of sites like Apple.com, Amazon.com, the BBC, Microsoft, and others, and taking a look at what they looked like 10 years ago. Guys I am horrified!
凯文：恩，谈到10年后的情况，本周我们刚得到一个消息， Blogger.com已经10岁了，这给SitePoint博客Jennifer Farley带来了回顾十年的灵感。当时网络上最大的网站及其外观。 我们在sitepoint.com上有一篇博客文章，其中包含Apple.com，Amazon.com，BBC，Microsoft等网站的屏幕截图，并介绍了十年前的情况。 伙计们，我吓坏了！
Patrick: Honestly, it’s not that bad I have to say. It’s not that— I remember this day!
帕特里克：老实说，我必须说的还不错。 不是那样的-我记得这一天！
Kevin: It’s worst than I thought it would be.
凯文：比我想的还要糟。
Patrick: This is when I actually got really started into developing web sites. It was in fall of 1998. So, I remember some of these—creepy.
帕特里克：这是我真正开始开发网站的时候。 那是1998年的秋天。所以，我记得其中一些-令人毛骨悚然。
Brad: I think the weirdest part is Amazon doesn’t look that much different. Amazon hasn’t really involved too much in 10 years.
布拉德：我认为最奇怪的部分是亚马逊看起来并没有太大不同。 十年来，亚马逊并没有投入太多。
Kevin: So, what I want each of us to do is take a look of these and pick the one you’re really glad is not around today, the worst one of the bunch and then the one that actually doesn’t look so bad. It might actually be better than the one that is up today.
凯文：所以，我希望我们每个人都能做的就是看看这些，然后挑选一个您真正感到高兴的不在今天，那是最糟糕的那一个，然后看起来实际上并不那么糟糕。 它实际上可能比今天提出的要好。
Patrick: Looking at these, I think it’s a tie for the worst between the White House and Google. I mean, I think there’s a tie and when you consider…
帕特里克：看这些，我认为白宫和Google之间的关系最糟。 我的意思是，我认为这是一条领带，当您考虑...
Brad: No. It has to be the White House.
布拉德：不。一定是白宫。
Patrick: Well, think about this though: Consider that Google is these tech students, these guys at Stanford, right, and they’re developing it. At the White House, you know, back then, “the Internet … what?” I mean, so consider that, but for me, it’s a tie as far as the worst goes between those two.
帕特里克(Patrick)：嗯，请考虑一下：考虑到Google是这些技术专业的学生，是斯坦福大学的这些人，对，他们正在开发它。 在白宫，那时候你知道“互联网……什么？” 我的意思是，请考虑一下，但对我而言，这两者之间的关系最糟糕。
Brad: I say it’s got to be the White House, and the reason being I see two American flags and you know those were animated GIFs and those flags are just waving away.
布拉德：我说那一定是白宫，原因是我看到了两个美国国旗，而且你知道那是动画GIF，而那些国旗正在挥舞。
Kevin: Everyone has seen those animated flags.
凯文：每个人都看过那些动画的旗帜。
Stephan: It looks like a really bad Geocities page, like really bad.
史蒂芬：看起来像一个非常糟糕的Geocities页面，就像一个非常糟糕的页面。
Patrick: I know. I like how the background to the photo is not meshed to the back, but again, this is at Archive.org, so maybe there was a background? I don’t know.
帕特里克：我知道。 我喜欢照片的背景如何不与背面网格化，但是还是在Archive.org上，所以也许有背景吗？ 我不知道。
Kevin: I don’t know. We could give them that credit it would still be butt ugly. I like the fact that it says ‘Good Morning’ at the top. So someone did a lot of work 10 years ago to make it say the time of day, and was that good morning on the east coast or the west coast? That’s what I want to know.
凯文：我不知道。 我们可以给他们以信贷，但这仍然是丑陋的。 我喜欢在顶部显示“早安”的事实。 因此，有人在10年前做了很多工作，使之成为一天中的某个时间，是在东海岸还是西海岸呢？ 这就是我想知道的。
“The President and Vice-President, their accomplishments, their families, and how to send them electronic mail.”
“总统和副总统，他们的成就，他们的家庭以及如何向他们发送电子邮件。”
Patrick: Before we abbreviated.
帕特里克：在我们缩写之前。
Kevin: This is just too good. The screenshot cuts off but I really want to read this whole page. It’s just so precious.
凯文：这太好了。 屏幕截图被截断，但我真的很想阅读整个页面。 真是太珍贵了。
Stephan: You know which one isn’t that bad is Monster.com. I don’t think it’s that bad. It might be better than it is today.
史蒂芬：您知道Monster.com是哪一个还不错。 我认为那没那么糟。 它可能比今天更好。
Kevin: It looks quite narrow. I guess back then we were coding for 640×480 still. So, it’s narrow by the standards of today’s fixed width designs, but yeah, it doesn’t look too bad.
凯文：看起来很狭窄。 我想那时候我们仍在编码640×480。 因此，按照今天的固定宽度设计的标准，它是狭窄的，但是，看起来还不错。
Stephan: When you look at Monster today, it’s just a mess.
史蒂芬：今天看怪物，真是一团糟。
Patrick: I’ll take Amazon on this one as far as the best. I mean like Brad said, there’s similarities between what they do now and what they did then but that was a nice design for then, now it wouldn’t be, but as far as this group, I would say it would bother me the least of everyone.
帕特里克：我将把亚马逊带到最好的那个位置。 我的意思是像Brad所说的，他们现在所做的与当时所做的工作之间存在相似之处，但这对当时来说是个不错的设计，现在不是，但是就这一组而言，我会说这至少会打扰我每个人。
Kevin: Yeah. If anything, there’s a lot less clutter.
凯文：是的。 如果有的话，混乱会少很多。
Stephan: I don’t know that Times New Roman font… I don’t know, it just kind of irks me.
史蒂芬：我不知道Times New Roman字体……我不知道，这有点让我讨厌。
Kevin: Yeah. Well, there’s sidebar of menus that are sans-serif, but yeah, the content of the page, the description of the product is all in serifed font. They still had a lot of tabs back then: books, music, video, toys and games, electronics, e-cards, auctions, and e-shops.
凯文：是的。 嗯，菜单的侧边栏是sans-serif，但是，是的，页面的内容，产品的描述全都是衬线字体。 那时他们仍然有很多标签：书籍，音乐，视频，玩具和游戏，电子产品，电子贺卡，拍卖和电子商店。
Patrick: Auctions? I like how it says “Z-shops are new.” So, if that’s their merchant program, it’s like that’s brand new! Okay.
帕特里克：拍卖？ 我喜欢它说“ Z店是新的”。 因此，如果这是他们的商人计划，那就像是全新的！ 好的。
Kevin: Apple does not look the best in this screenshot. There’s actually a missing image, so you got to give them credit; I’m sure that image was there back then.
凯文(Kevin)：苹果在该屏幕截图中看起来并不是最好的。 实际上有一个丢失的图像，因此您必须给予他们荣誉； 我敢肯定那个时候在那里。
Brad: This was really when they were kind of evolving their brand image to be more kind of trendy and hip than prior. So you can kind of tell they’re in that phase of making it a little more hip-looking, you know.
布拉德：确实是在他们不断提升品牌形象，使其比以前更加时尚和时髦的时候。 因此，您可以知道，他们正处于使它看起来更时髦的阶段。
Kevin: Yeah. They had the transparent Blueberry iMac there.
凯文：是的。 他们在那里有透明的蓝莓iMac。
Patrick: Yeah, the one thing about their design, though, is I think it’s the only one in the screenshots—they don’t go to the bottom, like you said, in some cases—but I think they’re the only one to have those “best viewed” sort of buttons at the bottom. “QuickTime: get it!” You know, those little buttons at the bottom… I don’t know, maybe not.
帕特里克：是的，但是关于他们设计的一件事是，我认为它是屏幕截图中唯一的一个-在某些情况下，它们不会像您所说的那样走到最底下-但我认为它们是唯一的一个在底部具有“最佳查看”按钮。 “ QuickTime：明白了！” 您知道，底部的那些小按钮……我不知道，也许不是。
Kevin: Maybe that’s what you needed to view that missing image you needed to have QuickTime installed.
凯文：也许这就是查看安装QuickTime所需的丢失图像所需的内容。
Stephan: You know microsoft.com doesn’t look that different and some of the developer pages that are around now.
史蒂芬：您知道microsoft.com看起来并没有什么不同，并且现在有一些开发人员页面。
Kevin: Yeah, you’re absolutely right. It’s very similar, isn’t it?
凯文：是的，你绝对正确。 这非常相似，不是吗？
Stephan: Yeah, I mean, they… I guess they got kind of lazy. That curved GIF—I can remember back when that was a cool technique, you know, the curved GIF.
斯蒂芬：是的，我是说，他们…我想他们有点懒。 那是弯曲的GIF，我记得那是弯曲的GIF这项很酷的技术。
Kevin: I like in the top, “Internet Explorer 5, download it now.”
凯文：我最喜欢顶部的“ Internet Explorer 5，立即下载。”
Patrick: No, I think best color scheme has to go to Wired I mean look at that, look at that left menu, it’s like bright, right in your face.
帕特里克：不，我认为最好的配色方案必须采用Wired，我的意思是看那个，看左边的菜单，就像在你的脸上一样明亮。
Kevin: Yeah, I’ve always loved Wired’s bald-faced bright colors. “We don’t care how it looks, it’s going to burn your retinas out; that’s what we’re here for.” The one I’m glad has changed is The Onion because it’s built with frames. I’m surprised of these top 10, only one of them was built with frames. I’m kind of relieved that we were… we had progressed that far 10 years ago. Or maybe frames had yet to catch on and The Onion is the cutting edge one that had moved into frames, but that’s one trend that I’m glad is gone. Just look at the big green bar across the bottom. The entire reason it’s there is for a teeny ad in the left hand side and yet, they’ve got the whole green bar across the bottom wasting space on what were very small screens at the time.
凯文：是的，我一直很喜欢Wired秃顶的鲜艳色彩。 “我们不在乎它的外观，它会烧掉您的视网膜； 那就是我们在这里的目的。” 我很高兴更改了一个洋葱，因为它是用框架制成的。 我对这些前十名感到惊讶，其中只有十个是用框架制成的。 令我感到宽慰的是……十年前，我们取得了进步。 也许帧尚未流行，但洋葱是进入帧中的最前沿技术，但这是我很高兴消失的一种趋势。 只需看一下底部的绿色大条即可。 造成这种情况的全部原因是左侧出现了一个小广告，但当时，整个绿色条形图的底部都是浪费在很小的屏幕上的底部。
Patrick: That bottom frame was a parody.
帕特里克：那底架是一个模仿。
Kevin: {laughs} Yeah, of course, I forgot to take irony into account when evaluating The Onion’s screenshot. So, yeah, take a look, listeners, at this blog post; there’s a link to it in our show notes and yeah, let us know what you notice in these screenshots, what’s still around today and what you’re glad is not.
凯文： {笑}是的，当然，我在评估《洋葱》的屏幕截图时忘记了讽刺意味。 是的，听众，看一下这篇博客文章； 是的，在我们的展示笔记中有一个链接，是的，让我们知道您在这些屏幕截图中注意到了什么，今天还有什么，但您高兴的不是。
Another blog post that I think is worth looking at on SitePoint this week is 19 Firefox Add-ons For Designers. We so often concentrate on developer add-ons for Firefox. I’ve said several times that it’s my development browser of choice, but this is a nice collection of add-ons that are for the designers in the crowd, so working with images and colors and things like that.
我认为本周在SitePoint上值得关注的另一篇博客文章是19 Firefox设计师专用插件 。 因此，我们经常专注于Firefox的开发人员附加组件。 我已经说过好几次了，这是我选择的开发浏览器，但这是一个不错的附加组件集合，适合人群中的设计师使用，因此可以处理图像，颜色和类似的东西。
Brad, you had a look through here, which one did you like?
布拉德，您在这里浏览了一下，您喜欢哪一个？
Brad: Well the obvious standout is Firebug; I think that’s almost an essential plug-in for anyone that works in any side of web development, whether it’s design or a developer. Firebug essentially lets you kind of view source on a site and you can right-click on a particular item, inspect it and it will drill down right to the CSS, the particular line that sets the style of that whatever it is you inspected, whether it be a graphic or text or a header, whatever it might be. It also lets you edit in real-time. So say you had a 10-pixel font and you want to see what it looks like at 12, you can easily inspect it, increase it to 12, and see exactly what it would like without actually making the change live.
布拉德：很明显，杰出的就是Firebug ； 我认为对于从事Web开发任何方面的人员(无论是设计人员还是开发人员)而言，这几乎都是必不可少的插件。 Firebug本质上使您可以查看网站上的源代码，您可以右键单击特定项目，对其进行检查，然后它将向下钻取到CSS，该特定行设置了所检查对象的样式，无论是否它可以是图形，文本或标题，无论它是什么。 它还使您可以实时编辑。 因此，假设您有一个10像素的字体，并且想查看12时的字体，可以轻松检查它，将其增加到12，然后准确地看到它的外观，而无需实际进行更改。
So Firebug is definitely one that everyone would want to use, and the other one that I absolutely love is the Window Resizer and essentially, this makes it easy to resize your browser window to different resolutions, whether be 800×600, 1024×768, whatever it may be. You can quickly just click a button and your browser will resize so you can see exactly what looks like in that resolution without actually changing the resolution so it saves quite a bit of time when you’re designing.
因此，Firebug绝对是每个人都想使用的一个，而我绝对喜欢的另一个是Window Resizer ，从本质上讲 ，这可以轻松地将浏览器窗口的大小调整为不同的分辨率，例如800×600、1024×768，不管是什么 您可以快速单击一个按钮，浏览器将调整大小，因此您可以准确地看到该分辨率下的外观，而无需实际更改分辨率，因此在设计时可以节省大量时间。
Kevin: Yeah. Patrick, you used one of these, didn’t you?
凯文：是的。 帕特里克(Patrick)，您使用了其中一种，不是吗？
Patrick: Yeah, I mean, actually Window Resizer sounds cool. I have to check that out. I mean I use Firebug too, but the one I have to highlight here is Screengrab. When I use it, it makes me happy—I guess that’s the simplest way to say it—because you can take a one screenshot of a full window, that’s what I use it for most of the time. I use it for like a media kit when I wanted to have a screenshot of the whole page to put in there to show where ads would be placed. It’s just really easy, it works. You can take screenshots just one scroll, the top scroll, or the whole page, just a visible bit, a draggable selection or whatever, it just works and it works well so that’s why I like it.
帕特里克：是的，我的意思是，实际上Window Resizer听起来很酷。 我必须检查一下。 我的意思是我也使用Firebug，但是在这里我要强调的是Screengrab 。 当我使用它时，它让我感到高兴(我想这是最简单的说法)，因为您可以为整个窗口拍摄一张屏幕截图，这就是我大部分时间使用的屏幕截图。 当我想要将整个页面的屏幕快照放在其中以显示广告放置位置时，我将其用作媒体工具包。 这真的很容易，而且有效。 您可以只截取一个滚动，顶部滚动或整个页面，一个可见的位，一个可拖动的选择或其他内容来截取屏幕截图，它可以正常工作并且效果很好，所以这就是我喜欢它的原因。
Kevin: A few of these add-ons are things that you would think… you’d look at them and you go, oh well, that’s a feature of the Web Developer Toolbar, but not every designer is going to want to wade through the menus of the Web Developer Toolbar just to find the window resizing feature, for example, and I think it’s great that some of these things have made their way into their own add-ons that are much simpler and easier to use.
凯文：您可能会想到其中的一些附加组件……您会看它们然后走，哦，那是Web Developer Toolbar的功能 ，但并不是每个设计人员都想涉足其中例如，Web开发人员工具栏的菜单仅用于查找窗口调整大小功能，我认为很高兴其中的一些功能已融入其自己的插件中，这些插件更加简单易用。
The one that I quite like is ColorZilla, which lets you pick color values out of the page by clicking on pixels within the page and I just really like the interface that it puts a thing in your browser’s status bar, a little color well that shows you the color values that you’re hovering over at any given time. It’s much nicer as an interface and something that I think a designer will really want to use.
我非常喜欢的一个是ColorZilla ，它允许您通过单击页面内的像素来从页面中选择颜色值，我真的很喜欢它在您的浏览器的状态栏中添加了一个东西的界面，该颜色可以很好地显示您可以在任何给定时间悬停的颜色值。 作为界面，它要好得多，我认为设计师真的想使用它。
If you’re a designer or you have a designer in your life that would like to enhance their Firefox experience, check out this list of 19 add-ons. Yeah, cheap Christmas indeed.
如果您是设计师，或者您的生活中有想要增强其Firefox体验的设计师，请查看此19个加载项列表。 是的，确实是便宜的圣诞节。
The last story to cover in the show today is HTML 5 Drag & Drop. There’s this great blog post that I spotted by Francisco Ryan Tolmasky (apologies for what I just did to your name there, Francisco), and it’s sort of dissecting the new HTML 5 built-in Drag & Drop support. This guy is one of the developers on a project called Cappuccino, which is all about building desktop-like applications on the Web using the same coding techniques that you get when building desktop Mac applications, and experienced developers will tell you that’s quite a nice API to work for. They’ve built a project called 280 Slides on Cappuccino and it’s a competitor to PowerPoint or Keynote on the Mac that all runs within a browser. In this blog post, it starts off with a demo video that really blew my mind.
今天在节目中要讲的最后一个故事是HTML 5拖放。 我在Francisco Ryan Tolmasky的身上发现了一篇很棒的博客文章 (对我刚才在您的名字所做的事情，Francisco表示歉意)，并且有点像对HTML 5内置的新拖放支持的剖析。 这个家伙是一个名为Cappuccino的项目的开发人员之一，该项目的全部目的是使用与构建桌面Mac应用程序时相同的编码技术在Web上构建类似于桌面的应用程序，而经验丰富的开发人员会告诉您，这是一个非常不错的API工作。 他们已经在Cappuccino上建立了一个名为280 Slides的项目，它是Mac上可在浏览器中运行的PowerPoint或Keynote的竞争对手。 在这篇博客文章中，它从一个演示视频开始，这让我非常震惊。
Brad, did you see that video?
布拉德，你看过那个视频吗？
Brad: Yeah, I did. It’s really awesome. If you haven’t seen this… and this is the first I have heard of the Drag & Drop with HTML 5. If you haven’t seen it, definitely go check out the video. As soon as it started, the video fires up and it’s a short one 20 seconds—and he starts kind of dragging elements around. I’m thinking, okay, this looks like jQuery, and then he drags it from one browser to another and drops it. I’m like, wow, that’s pretty amazing and wild at the same time, so it’s definitely something I want to do more research on, but this could really like really change the way that web apps are built and how they interact with each other.
布拉德：是的，我做到了。 真的很棒 如果您还没有看过……这是我第一次听说HTML 5拖放。如果您还没有看过，请务必观看该视频。 影片一开始播放，一秒钟就短了20秒钟，他开始在周围拖动元素。 我在想，好吧，它看起来像jQuery，然后将其从一个浏览器拖到另一个浏览器上并放下。 我想，哇，这真是太神奇了，同时又很疯狂，所以我绝对想对它做更多的研究，但这真的很可能会真正改变Web应用程序的构建方式以及它们之间的交互方式。 。
Kevin: Yeah, it just goes from kind of cool to kind of amazing to really mind blowing. He drags the image from one window to another. So I’m thinking, okay well, he marked the image tag as draggable and when he dropped it in, it created an image tag in the other document and so he was able to tell what the image was. Yeah, that’s kind of cool. But then he drags an entire slide from one presentation into the other and I’m thinking “How do they that?” Like the slide with all the formatting and all of the objects in it, all dragged from one window to the other.
凯文：是的，它从一种很酷的变化到一种令人惊奇的变化，到真正令人震惊的程度。 他将图像从一个窗口拖到另一个窗口。 所以我在想，好吧，他将图像标签标记为可拖动，当他将其拖放到其他文档中时，它在另一个文档中创建了图像标签，因此他能够分辨出图像是什么。 是的，这很酷。 但是随后他将整个幻灯片从一个演示文稿拖到另一个演示文稿中，我在想“他们怎么做到的？” 像具有所有格式和其中所有对象的幻灯片一样，所有幻灯片都从一个窗口拖到另一个窗口。
Looking further down in the article, he explains how this works, how when something starts dragging in HTML 5, as a JavaScript developer, you have the opportunity to set the data that’s being dragged in multiple formats so you can say this slide that’s being dragged, I can represent it as a PNG file or as a JavaScript slide object or as a URL. You bundle up these multiple formats and then on the receiving end, you decide which on you want.
Looking further down in the article, he explains how this works, how when something starts dragging in HTML 5, as a JavaScript developer, you have the opportunity to set the data that's being dragged in multiple formats so you can say this slide that's being dragged, I can represent it as a PNG file or as a JavaScript slide object or as a URL. You bundle up these multiple formats and then on the receiving end, you decide which on you want.
He goes on to critique some of the design of this API, saying that having to fill in all those different data formats when you start dragging, can be a slow and heavy process, and on the desktop we’ve learned that the best way to do it is advertise the formats available and then only create the one that the receiver ends up requesting. He also complains that as a developer, you have no control over whether a drag actually starts or not. Once you mark something as draggable, when you start dragging, it’s going to start dragging whether you like it in that moment or not. Whereas on the desktop, you can do things like under certain circumstances, the thing will start dragging, and under other circumstances it might do a text selection, maybe depending on the direction you drag the mouse in, and he’d like to see more flexibility there.
He goes on to critique some of the design of this API, saying that having to fill in all those different data formats when you start dragging, can be a slow and heavy process, and on the desktop we've learned that the best way to do it is advertise the formats available and then only create the one that the receiver ends up requesting. He also complains that as a developer, you have no control over whether a drag actually starts or not. Once you mark something as draggable, when you start dragging, it's going to start dragging whether you like it in that moment or not. Whereas on the desktop, you can do things like under certain circumstances, the thing will start dragging, and under other circumstances it might do a text selection, maybe depending on the direction you drag the mouse in, and he'd like to see more flexibility there.
He makes good points but still, it’s mind blowing what’s possible already. He says that this stuff is supported in WebKit browsers, so we’ll be seeing web applications running in Safari and Chrome that take advantage of this kind of stuff pretty soon.
He makes good points but still, it's mind blowing what's possible already. He says that this stuff is supported in WebKit browsers, so we'll be seeing web applications running in Safari and Chrome that take advantage of this kind of stuff pretty soon.
So yeah, if you’re into the techie side of HTML and JavaScript this blogpost is a must read. Go check it out.
So yeah, if you're into the techie side of HTML and JavaScript this blogpost is a must read. Go check it out.
Which brings us to our host spotlight, gentlemen.
Which brings us to our host spotlight, gentlemen.
Stephan: Yeah, so this week, I was browsing and found that Crackle.com is offering 31 movies in 31 days and you can watch full movies on YouTube. This right now, today, I believe it’s Ghostbusters. If you’re a Ghostbusters fan … I’m sure they’re going to have other movies. The list includes Causalities of War, Crossroads, The Karate Kid, Crazy Joe…
Stephan: Yeah, so this week, I was browsing and found that Crackle.com is offering 31 movies in 31 days and you can watch full movies on YouTube. This right now, today, I believe it's Ghostbusters. If you're a Ghostbusters fan … I'm sure they're going to have other movies. The list includes Causalities of War, Crossroads, The Karate Kid, Crazy Joe…
Kevin: Is each movie only up for a day and if you want to watch all of them, you have to watch one movie a day?
Kevin: Is each movie only up for a day and if you want to watch all of them, you have to watch one movie a day?
Stephan: It doesn’t really explain it very well, but it looks like you can actually watch some of the movies, even after the day has gone by… like Stripes.
Stephan: It doesn't really explain it very well, but it looks like you can actually watch some of the movies, even after the day has gone by… like Stripes.
Kevin: Ghostbusters is celebrating its 25th anniversary, it looks like. I’m just looking at an early promo pic and, man, did Bill Murray ever look young? I’m just saying.
Kevin: Ghostbusters is celebrating its 25th anniversary, it looks like. I'm just looking at an early promo pic and, man, did Bill Murray ever look young? I'm just saying.
Patrick: No, I love Bill Murray, man. C’mon.
Patrick: No, I love Bill Murray, man. 拜托
Kevin: I love Bill Murray too, but geez.
Kevin: I love Bill Murray too, but geez.
Kevin: Brad?
凯文：布拉德？
Brad: My spotlight this week is actually a web service that hasn’t launched yet but it is going to launch soon called KISSmetrics. KISS stands as the popular acronym for Keep It Simple Stupid. Essentially, they are working towards releasing a new analytics package for web sites that is supposed to be simple and easy to use for developers and web site managers and marketers.
Brad: My spotlight this week is actually a web service that hasn't launched yet but it is going to launch soon called KISSmetrics . KISS stands as the popular acronym for Keep It Simple Stupid. Essentially, they are working towards releasing a new analytics package for web sites that is supposed to be simple and easy to use for developers and web site managers and marketers.
Visit KISSmetrics.com, type in your email, get on their waiting list, and as soon as they release the open beta or the final product, whatever is coming out first, I’m sure they’ll let you know. So check it out.
Visit KISSmetrics.com, type in your email, get on their waiting list, and as soon as they release the open beta or the final product, whatever is coming out first, I'm sure they'll let you know. So check it out.
Kevin: Great. Patrick?
凯文：太好了。 帕特里克？
Patrick: My spotlight is BlogWorld & New Media Expo in Las Vegas, October 15-17th. It’s, I’d say, one of the best conferences to attend if you work online or write online. I mention it for two reasons.
Patrick: My spotlight is BlogWorld & New Media Expo in Las Vegas, October 15-17th. It's, I'd say, one of the best conferences to attend if you work online or write online. I mention it for two reasons.
First, Stephan and me are both going to be there. So if you’re going to be there, please leave a comment and we’d be glad to meet up, say hello.
First, Stephan and me are both going to be there. So if you're going to be there, please leave a comment and we'd be glad to meet up, say hello.
And the other thing is I’m speaking. I’m going to be speaking on October 16th on a panel called Social Media – What’s Not To Like. It also has Amber Naslund, Radian6, Wayne Sutton of OurHashtag and Robert Scoble of Building43 at Rackspace, and we’re going to be talking about trends in social media that concern us as far as the growth of the medium.
And the other thing is I'm speaking. I'm going to be speaking on October 16th on a panel called Social Media – What's Not To Like. It also has Amber Naslund, Radian6, Wayne Sutton of OurHashtag and Robert Scoble of Building43 at Rackspace, and we're going to be talking about trends in social media that concern us as far as the growth of the medium.
If you haven’t signed up already, you can use a coupon code. There is a few of them floating around, but one is IFROGGYVIP for 20% off. I don’t make any money from that, I don’t get paid from that; it’s just a coupon for 20% off.
If you haven't signed up already, you can use a coupon code. There is a few of them floating around, but one is IFROGGYVIP for 20% off. I don't make any money from that, I don't get paid from that; it's just a coupon for 20% off.
So check it out and let us know if you’re coming.
So check it out and let us know if you're coming.
Kevin: Great, I wish I was going.
Kevin: Great, I wish I was going.
Kevin: My host spotlight is punypng. It’s a new web-based service for shrinking your PNG files without losing any quality. It doesn’t just work on PNGs; it also works on GIFs and JPEGs.
Kevin: My host spotlight is punypng . It's a new web-based service for shrinking your PNG files without losing any quality. It doesn't just work on PNGs; it also works on GIFs and JPEGs.
The idea is you go to this site and you upload one, or even a whole bunch of image files that you use on your site. There is a maximum size of 500 kilobytes for each. It will analyze each of them and it uses some really clever techniques to squeeze extra space out of these image files. This is stuff that even Photoshop’s Save for the Web, doesn’t do. That’s the benchmark that they compare against in all of their analysis. And they’re saying that commonly, you can lose 35% or more of the file size, even after exporting it from Photoshop.
The idea is you go to this site and you upload one, or even a whole bunch of image files that you use on your site. There is a maximum size of 500 kilobytes for each. It will analyze each of them and it uses some really clever techniques to squeeze extra space out of these image files. This is stuff that even Photoshop's Save for the Web, doesn't do. That's the benchmark that they compare against in all of their analysis. And they're saying that commonly, you can lose 35% or more of the file size, even after exporting it from Photoshop.
One of the ways they do this is called Dirty Transparency. For some reason, when you create a PNG file with transparent regions, those regions are just marked transparent, but there’s still image data there that you just don’t see because it’s been marked transparent. That image data still takes up space within the image. So what punypng does is it replaces all that image data with a solid color that compresses a lot better.
One of the ways they do this is called Dirty Transparency. For some reason, when you create a PNG file with transparent regions, those regions are just marked transparent, but there's still image data there that you just don't see because it's been marked transparent. That image data still takes up space within the image. So what punypng does is it replaces all that image data with a solid color that compresses a lot better.
That’s just one example of the techniques they use, but it’s really a fire and forget service and it’s free; you just upload your images and they analyze them and give you a table of the savings. Unlike a lot of compression services, if their compression actually makes the image bigger somehow and that, in rare cases, can happen, they just send you back the original file, rather than sending you the bloated one that they created. They’ll even analyze JPEG images to see if they could be better compressed as PNGs and they’ll advise you one way or the other. It’s a really slick service and far more comprehensive than anything else that I’ve seen along these lines.
That's just one example of the techniques they use, but it's really a fire and forget service and it's free; you just upload your images and they analyze them and give you a table of the savings. Unlike a lot of compression services, if their compression actually makes the image bigger somehow and that, in rare cases, can happen, they just send you back the original file, rather than sending you the bloated one that they created. They'll even analyze JPEG images to see if they could be better compressed as PNGs and they'll advise you one way or the other. It's a really slick service and far more comprehensive than anything else that I've seen along these lines.
Check it out at punypng.com.
Check it out at punypng.com .
And that is our host spotlight section for this week, which brings us, as always, to the end of the show.
And that is our host spotlight section for this week, which brings us, as always, to the end of the show.
Visit us at sitepoint.com/podcast to leave comments on this episode and to subscribe to receive every show automatically. Let’s go around the table, guys.
Visit us at sitepoint.com/podcast to leave comments on this episode and to subscribe to receive every show automatically. Let's go around the table, guys.
Brad: I’m Brad Williams from webdevstudios.com and you can find me on Twitter @williamsba.
Brad: I'm Brad Williams from webdevstudios.com and you can find me on Twitter @williamsba .
Patrick: I am Patrick O’Keefe for the iFroggy network and I’m on Twitter @iFroggy.
Patrick: I am Patrick O'Keefe for the iFroggy network and I'm on Twitter @iFroggy .
Stephan: I’m Stephan Segraves, and you can find me on Twitter @ssegraves.
Stephan: I'm Stephan Segraves, and you can find me on Twitter @ssegraves .
Kevin: And you can find me on Twitter @sentience and follow SitePoint on Twitter @sitepointdotcom.
Kevin: And you can find me on Twitter @sentience and follow SitePoint on Twitter @sitepointdotcom .
The SitePoint podcast is produced by Carl Longnecker, and I’m Kevin Yank. Thanks for listening.
The SitePoint podcast is produced by Carl Longnecker, and I'm Kevin Yank. 谢谢收听。
Thanks for listening! Feel free to let us know how we’re doing, or to continue the discussion, using the comments field below.
谢谢收听！ 欢迎使用下面的评论字段让我们知道我们的状况，或者继续讨论。
翻译自: https://www.sitepoint.com/podcast-24-those-frames-are-ironic/
