Slashdot Mirror

← Back to Stories (view on slashdot.org)

BBC's iPlayer To Be Crossplatform

Posted by ryuzaki0 on from the coming-around dept.

craig1709 writes "10 Downing Street has responded to the petition to open up iPlayer access for those on other operating systems. While the wording is confusing, near as I can tell, they say they will make the iPlayer available to users of those operating systems. 'The BBC Trust made it a condition of approval for the BBC's on-demand services that the iPlayer is available to users of a range of operating systems, and has given a commitment that it will ensure that the BBC meets this demand as soon as possible. They will measure the BBC's progress on this every six months and publish the findings.'"

2 of 232 comments (clear)

  1. Platforms by Hwatzu · · Score: 5, Funny

    Of course it'll be multiplatform. Why, you can run it on XP *and* Vista!

  2. Re:Every six months? by RuBLed · · Score: 5, Funny

    Here's how it works:

    Month 1

    Week 1: Debate which OS/Distro to develop on.
    Week 2: Submit recommendations/analysis to superiors.
    Week 3: Wait
    Week 4: Submission was going to be revised. Resubmit. Hope that it is okay this time.

    Month 2

    Week 1: Accepted. Determine the priority of the modules to port.
    Week 2: Make new test scenarios with regards to the target environment.
    Week 3: Buy development pc/server, install the target OS/distro. set it up.
    Week 4: Manager decides to do team building at the beach.

    Month 3

    Week 1: Start to port the code to the new environment.
    Week 2: same as Week 1
    Week 3: Employees all got common cold.
    Week 4: Coding Finished.

    Month 4

    Week 1: Run Tests and modify code as necessary.
    Week 2: Continue testing and make initial builds.
    Week 3: Install initail build on test server and demo it.
    Week 4: Continue the iterations until an acceptable build was made.

    Month 5

    Week 1: Had the QA run the build on their tests.
    Week 2: QA tests the build and determines if the video would no longer play after a few weeks.
    Week 3: QA waiting for the two week expiration of video. CEO resigns.
    Week 4: QA test completed, bugs logged, dev goes into cramming.

    Month 6

    Week 1: QA runs tests as necessary.
    Week 2: Management determines product is good even with active bugs.
    Week 3: Marketing announces the launch date of the product.
    Week 4: Dev copies the exe from his bin...

    Month 7 ...