On Jan 8, 2008 3:16 PM, neil [EMAIL PROTECTED] wrote:
Questions include: Is this intuitive? Does the data shift as you might
expect? Are two sliders too complex? Is a slider appropriate here, or should
something else be used? Is the sorting algorithm right? What should we do
about duplicate
As this is the developer list I¹d like to keep it quite technical here
before we open it out to the main list for general feedback... However...
In this instance I was really interested in this work (which came out of the
last labs) because it solves a specific problem for NR that being if you
http://www.bbc.co.uk/technology/ is showing 403 Forbidden.
-
Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please
visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html.
Unofficial list archive: http://www.mail-archive.com/backstage@lists.bbc.co.uk/
On 06/01/2008, James Cridland [EMAIL PROTECTED] wrote:
this list (and this thread in
particular) is precisely because we -do- want people knowing how as much of
this works as possible:
Them tell me how it works!
The HTML looks like it was designed to be hard to read, was this the case?
On
Production client-side code really shouldn't have documentation in. It is
usually taken out by a build script to save bandwidth - the same reason as
why the javascript is badly formatted and obfuscate, it'll probably be
packed or minified.
J
On Jan 9, 2008 9:42 AM, Andy [EMAIL PROTECTED] wrote:
On 09/01/2008, Andy [EMAIL PROTECTED] wrote:
On many other sites all you have to do is view source, Ctrl-F,
.flv and you find the URL needed for the stream.
...
I think the biggest thing people want is you NOT TO USE RTMP.
The BBC is using the latest Flash technology - Flash Media Server -
http://semanticcamp.tommorris.org/
Get your BarCamp fix.
Sign-up is open now.
-Frances
-
Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please
visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html.
Unofficial list archive:
Sean DALY wrote:
http://www.bbc.co.uk/technology/ is showing 403 Forbidden.
Mmmm, sweet forbidden technology. (Not to be confused with
http://www.forbidden.co.uk/).
S
-
Sent via the backstage.bbc.co.uk discussion group. To unsubscribe, please
visit
Jason Cartwright wrote:
the same reason as why the javascript is badly formatted and
obfuscate, it'll probably be packed or minified.
I wish BBC news did that for their HTML; simply stripping the whitespace and
nothing else shrinks the BBC news front page by *a third*! Quite a bandwidth
404 for me here inside the firewall.
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Sean DALY
Sent: 09 January 2008 09:13
To: backstage@lists.bbc.co.uk
Subject: [backstage] 403 Forbidden on http://www.bbc.co.uk/technology/
It appears to be a slightly iffy redirect - bbc.co.uk/technology points to
http://news.bbc.co.uk/1/hi/technology/default.stm - the 404 you're getting
is at http://news.bbc.co.uk/1/hi/technology/default.stm/
On 1/9/08, Melissa Packer [EMAIL PROTECTED] wrote:
404 for me here inside the firewall.
On 09/01/2008, Jason Cartwright [EMAIL PROTECTED] wrote:
Production client-side code really shouldn't have documentation in.
If the BBC is serious about supporting innovation around the iPlayer,
it ought to leave it in here.
--
Regards,
Dave
(Personal opinion only)
-
Sent via the
Dave Crossland wrote:
On 09/01/2008, Jason Cartwright [EMAIL PROTECTED] wrote:
Production client-side code really shouldn't have documentation in.
If the BBC is serious about supporting innovation around the iPlayer,
it ought to leave it in here.
I believe Ian said that there's a proper API
It simply because http://www.bbc.co.uk/technology/ tries to redirect to
http://news.bbc.co.uk/1/hi/technology/default.stm/ - note the trailing slash
in both which makes it not work.
Doing http://www.bbc.co.uk/technology works in Opera and IE as it redirects
to
On Wednesday 09 January 2008 10:46, Tom Morris wrote:
It's like a conference with all the boring
bits taken out.
That _was_ the design goal of the approach - Open Space Technology - when it
was invented by Harrison Owen over 20 years ago... :-)
I'd recommend his book[1] on it to those
On 09/01/2008, Steve Jolly [EMAIL PROTECTED] wrote:
Dave Crossland wrote:
On 09/01/2008, Jason Cartwright [EMAIL PROTECTED] wrote:
Production client-side code really shouldn't have documentation in.
If the BBC is serious about supporting innovation around the iPlayer,
it ought to leave
This sounds really good, I am very interested in semantic web and hope to go
to hear what everyone has to say about it. Be good to get together and throw
some Q/A around. Is anyone else on the list interested in going?
./Matt
On Jan 9, 2008 10:46 AM, Tom Morris [EMAIL PROTECTED] wrote:
Hey
An API would be good, one could request a stream ID based on program, or
perhaps just a category, similar to an RSS feed based on program genre or
series. So my webapp could automatically list the latest 5 top gear episodes
for my fan site, with little programming or knowledge of program IDs. An
Dave Crossland wrote:
(From http://www.zedshaw.com/rants/rails_is_a_ghetto.html which I
found hilarious and may be of interest to Ruby on Rail developers :-)
Listen to the guy himself:
If I remember right I had clicked this morning on the trailing-slash
link on the sidebar of this page:
http://www.bbc.co.uk/blogs/technology/2008/01/networking_with_negroponte.html
But it seems fine now.
On Jan 9, 2008 1:45 PM, Michael Walsh
[EMAIL PROTECTED] wrote:
It simply because
Now http://www.bbc.co.uk/technology redirects directly to:
http://news.bbc.co.uk/1/hi/technology/default.stm
See:
Connected to www.bbc.co.uk (212.58.251.202).
GET /technology HTTP/1.1
HOST: www.bbc.co.uk
HTTP/1.1 302 Found
[snip]
Location: http://news.bbc.co.uk/1/hi/technology/default.stm
I disagree. Using gigs and gigs of bandwidth needlessly and making an app
run slower for millions of people, just so a few developers can hack around
with it?
Much better to release an API and sample source code separately. Example...
Built for users: http://maps.google.com
Built for developers:
On 09/01/2008, Michael Walsh [EMAIL PROTECTED] wrote:
It simply because http://www.bbc.co.uk/technology/ tries to
redirect to
http://news.bbc.co.uk/1/hi/technology/default.stm/ - note
the trailing slash in both which makes it not work.
Using Telnet to view the exact return by the server shows
With or without slash, the redirect is OK for me on Firefox v2.0.0.11,
Safari v1.32, Opera v9.25 on Mac, and Firefox v2.0.0.11, IE v6 on PC
XP.
On Jan 9, 2008 2:57 PM, Andy [EMAIL PROTECTED] wrote:
On 09/01/2008, Michael Walsh [EMAIL PROTECTED] wrote:
It simply because
-- Forwarded Message --
Subject: [GeekUp] BarCamp Manchester needs you
Date: Wednesday 09 January 2008 14:23
From: Paul Robinson [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
This has been in planning for what seems like an eternity. :-)
By scaling things down to a one-day event
here's what curl (v7.14 on Darwin) has to say, with and without the
trailing slash:
$ curl http://www.bbc.co.uk/technology --dump-header bbc-co-uk.technology.txt
!DOCTYPE HTML PUBLIC -//IETF//DTD HTML 2.0//EN
htmlhead
title301 Moved Permanently/title
/headbody
h1Moved Permanently/h1
pThe
(From http://www.zedshaw.com/rants/rails_is_a_ghetto.html which I
found hilarious and may be of interest to Ruby on Rail developers :-)
I *loved* that, but I wasn't convinced I'd ever hire him and expect
him to respect an NDA after the event - which maybe doesn't show he is
a good a business
On 09/01/2008, Jason Cartwright [EMAIL PROTECTED] wrote:
I disagree.
...
Much better to release an API and sample source code separately.
I look forward to the BBC releasing an API and sample source code separately :-)
--
Regards,
Dave
(Personal opinion only!)
-
Sent via the
On 09/01/2008, Frank Wales [EMAIL PROTECTED] wrote:
He sounds like he'd be a hoot to have around, as long as you're not
one of those cheeseburger-eating, IDE-loving, PHP douchebags, as he
might call them.
(Which I'm not, by the way, if you're reading this, Zed. I'm more
your
Good idea, streamline and optimise for the end user, be abundant with
information for the developer. That way it would increase reliability for
the end user too, as the live production code is less likely to change/have
errors introduced, whereas if the developer code goes a little wrong, it's
not
On 09/01/2008, Martin Belam [EMAIL PROTECTED] wrote:
(From http://www.zedshaw.com/rants/rails_is_a_ghetto.html which I
found hilarious and may be of interest to Ruby on Rail developers :-)
I *loved* that, but I wasn't convinced I'd ever hire him and expect
him to respect an NDA after the
http://www.youtube.com/watch?v=CJmCQa9hRl4
Enjoy, thanks George...
Ian Forrester
This e-mail is: [x] private; [] ask first; [] bloggable
Senior Producer, BBC Backstage
BC5 C3, Media Village, 201 Wood Lane, London W12 7TP
email: [EMAIL PROTECTED]
work: +44 (0)2080083965
mob: +44 (0)7711913293
On Jan 9, 2008 4:11 PM, Dave Crossland [EMAIL PROTECTED] wrote:
On 09/01/2008, Frank Wales [EMAIL PROTECTED] wrote:
He sounds like he'd be a hoot to have around, as long as you're not
one of those cheeseburger-eating, IDE-loving, PHP douchebags, as he
might call them.
(Which I'm not,
On Jan 9, 2008 9:42 AM, Andy [EMAIL PROTECTED] wrote:
On 06/01/2008, James Cridland [EMAIL PROTECTED] wrote:
this list (and this thread in
particular) is precisely because we -do- want people knowing how as much of
this works as possible:
Them tell me how it works!
The HTML looks like
Hello Backstage faithful,
Its a rarity on this list ;-) but heres a kinda product (or at least and
idea) announcement
We're working on a new 10% time project over here at FMT Audio and Music -
and we thought we'd give you guys a super sneak preview. Theres a few of us
involved here, including
35 matches
Mail list logo
