Canaux

108413 éléments (108413 non lus) dans 10 canaux

Actualités Actualités
Hoax Hoax
Logiciels Logiciels
Sécurité Sécurité
Referencement Referencement

BetaNews.Com (151 non lus)

  • Lien pour 'BetaNews.Com/2010/03/02/New_CRM_software_from_SAP_lets_iPhone__WinMo__BlackBerry_replace_PC_clients'

    New CRM software from SAP lets iPhone, WinMo, BlackBerry replace PC clients

    Publié: mars 2, 2010, 10:43pm CET par Jacqueline Emigh

    By Jacqueline Emigh, Betanews

    Sybase's new mobile sales application for iPhone, Windows Mobile, and BlackBerry lets users connect to SAP CRM remotely from their phones, much as they would from a desktop or laptop PC. And a new mobile workflow app from Sybase and SAP lets users play roles in multi-part business processes from their phones, an SAP representative tells Betanews.

    With new business apps for iPhone, WM6, and BlackBerry smartphones rolled out on Tuesday, Sybase and SAP have now completed the first phase of a long-term pact around mobile customer relationship management and (enterprise resource planning software. In the week ahead, iPhone and Windows Mobile client software will be available for both Sybase Mobile Sales for CRM and Sybase Mobile Workflow for SAP Business Suite, said Prashant Chatterjee, director of mobility and industry analytics for SAP.

    Chatterjee noted that RIM released a preliminary proof-of-concept client for BlackBerry about a year ago. But, he added, the existing smartphone software for BlackBerry, currently available on the Web as freeware, will be replaced during the second half of this year with a "full-fledged client."

    In an initial deal announced in March 2009, the two vendors agreed to make business processes from SAP Business Suite Mobile 7 available on Sybase's Unwired Platform to all mobile devices, including Symbian and Palm devices as well.

    Chatterjee told Betanews that the two companies will soon finish up a roadmap that will outline additional phases of their pact.

    Copyright Betanews, Inc. 2010

    Add to digg Add to Google Add to Slashdot Add to Twitter Add to del.icio.us Add to Facebook Add to Technorati
  • Lien pour 'BetaNews.Com/2010/03/02/Got_a_Windows_Mobile_phone__There_s_no_Windows_7_Phone_Series_upgrade_for_you'

    Got a Windows Mobile phone? There's no Windows 7 Phone Series upgrade for you

    Publié: mars 2, 2010, 10:21pm CET par Joe Wilcox

    By Joe Wilcox, Betanews

    Could someone please give back Steve Ballmer's brain? He really needs it. The Web is buzzing about a Microsoft executive telling APC Magazine that existing Windows Mobile handsets will not be eligible for Windows Phone 7 Series upgrades. Is Ballmer, Microsoft's CEO, out of his fraking mind for letting this happen? Oh, right, someone took away his brain. Please return it.

    What's all the fuss about? Firstly, the no-upgrade policy gives every possible Windows Mobile buyer every reason not to purchase. Secondly, the hottest WinMo phone, the HTC HD2, is suddenly a Windows Phone 7 Series brick. According to Natasha Kwan, Microsoft's Asia-Pacific region Mobile Communications Business GM, the HD2 "doesn't qualify because it doesn't have the three buttons." The smartphone has too much of a good thing--five buttons.

    OK, sometimes Microsoft executives shoot off at the mouth, so I contacted the company's PR firm for clarification. I got one of those twisty statements that could mean one thing when it probably means another: "For Windows Phone 7 Series we are enforcing a strict set of hardware requirements to ensure a consistently great experience for end-users and developers. While we cannot confirm that WM6.X phones that satisfy those requirements will be upgradeable, every Windows Phone 7 Series device will be upgradeable with improvements and features we deliver with subsequent Windows Phone 7 Series releases."

    That's doggy talk for "no Windows Mobile 6.x handset will qualify for Windows Phone 7 Series upgrades, but we don't dare say so." The unstated strict hardware requirement: That Windows Phone logo button. With the HD2, I'd wager the problem isn't so much too many buttons but not enough of the right kind. Because by all other measures -- processor, screen size and kind and graphics capability, among others -- the HTC HD2 should otherwise be able to run Windows Phone 7 Series.

    For frak's sake, Microsoft, why don't you make your own phone? If the hardware requirements are going to be so strict for an operating system manufacturers must pay for -- rather than get, say, Google Android for free -- Microsoft should just make its own phone. Dissing HD2 owners is simply unthinkable. It's the hot Windows Mobile phone -- the only one really. Please, thief, return Steve Ballmer's brain because, as the Ramones sang it: "My brain is hanging upside down."

    Unlucky T-Mobile USA is ready to launch the HD2. How's that for the mother of lousy timing? The company's offices are in Bellevue, Wash., or about 10 miles drive up the 405 to 1 Microsoft Way in Redmond. T-Mobile should dispatch employees to assist in the search for Steve Ballmer's brain.

    Microsoft's position -- or lack of it -- about Windows Mobile handset upgrades is brain boggling times three. Nilay Patel writes at Engadget:

    Making matters even less clear, we asked Microsoft's Director of Consumer Experiences Aaron Woodman about the HD2 directly on The Engadget Show, and he politely declined to tell us about the device's upgradability, and said that WP7's final required specs would be revealed at MIX '10. We'll be honest: we're taking all this confusion to mean that Microsoft hasn't quite figured out how to say the HD2 is at a dead end just before it launches on T-Mobile US.

    Yeah, Microsoft sure loves its hardware partners. You can ask any of the MP3 player manufacturers that supported PlaysForSure six years ago. Microsoft was all huggy, kissy before dumping them all for Zune. Microsoft's branded music player ended any Microsoft blabber talk about device "choice." Surely, there's a Microsoft phone somewhere in the future. Why drag out hardware partners' misery?

    Unless -- gasp -- they learned something from Microsoft's past behavior. Microsoft's wishy washy statements about WinMo handsets' future fate might just be enough for many partners to cool their Windows Phone 7 Series jets and look elsewhere -- like Android. That's a path still leading to a Microsoft branded phone, assuming few manufacturers really step up to license the new OS.

    There really isn't any confusion here, by the way. Microsoft is keeping Windows Mobile alive for a reason. Company execs can't exactly look existing hardware partners or customers in the face and say, "There's no Windows 7 Phone Series upgrade for you," if there's no Windows Mobile alternative. By continuing the operating system as Windows Phone Classic, Microsoft has placed a back door for quick escape: Windows Phone Classic is the upgrade path for Windows Mobile.

    I tease about Steve Ballmer losing his brain because I like the guy. No offense is intended. I stand by my late-January post defending Ballmer. That said, starting over with a new mobile operating system was smart. Good job, Microsoft. But potentially killing sales of existing Windows Mobile handsets is simply stupid. Potentially alienating existing hardware partners and customers is stupider still.

    Copyright Betanews, Inc. 2010

    Add to digg Add to Google Add to Slashdot Add to Twitter Add to del.icio.us Add to Facebook Add to Technorati
  • Lien pour 'BetaNews.Com/2010/03/02/Apple_aims_to_take_down_Android_by_court_order'

    Apple aims to take down Android by court order

    Publié: mars 2, 2010, 10:07pm CET par Scott M. Fulton, III

    By Scott M. Fulton, III, Betanews

    At the heart of Apple's very serious charges against HTC -- among the most prominent manufacturers of Android-based phones today -- is whether the methodology Android uses to run Java programs using a specialized derivative of the Java Virtual Machine, called Dalvik, actually borrowed (or stole) ideas directly from the NeXT operating system. NeXTSTEP, you may recall, included radical innovations to the system kernel enabling inter-application communication (IAC), on a level far beyond anything Macintosh had used at the time. It was Steve Jobs' revenge against the company that had spurned him, and as history has borne out, Jobs was the victor in that little skirmish.

    One of the ten patents Apple is defending in its lawsuit against HTC, drafted yesterday and filed this morning in US District Court in Delaware, deals specifically with NeXT's methodology. Apple acquired NeXT at the end of 1996, which is how Jobs re-entered the universe of Apple -- many believe, to have saved the company. Earlier that year, NeXT received a patent on a framework for IAC designed to compete with COM/DCOM and CORBA, the two other leading object methodologies of the time.

    Though the complaint Apple filed with the US International Trade Commission this morning was officially under seal, it managed to get posted to Scribd this afternoon.

    Apple's complaint describes the concept behind the first of its ten defended patents briefly: "As a general rule, separate processes execute independently (even when they may be executed simultaneously), and software within one process cannot directly access resources from or make calls on software within another process. Conventional methods for inter-process communication often required the software programmer to understand and utilize low-level operating system functionalities. The '721 patent describes a more efficient method for inter-process communication by way of a proxy object, which exists in a local process and acts as a local representation of objects that are located in a different process."

    The typical problem with objects, or object-oriented components, in an operating system is that they don't really speak each other's language -- or more accurately, that they don't have a common language to speak. In Microsoft's COM, still at the heart of Windows, that problem is resolved through the System Registry. Windows components all share a few common functions, whose sole purpose is to enable them to discover one another. Once they've done that, they can share information from the Registry to connect them with each other's interfaces, and from there, they acquire each other's vernacular of functions they can perform. I've often said it's not so much like two foreign objects learning a common language, as much as deciding what storage room they can meet in that contains enough other objects they can point to, so they can identify what it is they want for now.

    NeXT handled this problem differently, innovating new concepts that would replace COM's mutual interface exchange with what many at the time felt to be a more elegant methodology. The kernel of the NeXT operating system (and successors based on it, including the current MacOS X) is called Mach. Instead of relying upon binary interfaces, Mach let developers write IAC messages using Objective-C -- a language that for many years has been Apple's ace-in-the-hole. Mach handled all the translation, into streams of primitives that are shared with other objects using Internet-like communications protocols. Although objects still communicated with each other by way of proxy, as was the case with COM, the stream they set up with one another was a port. All the objects that have rights to communicate on that port, formed a domain.

    From Apple's/NeXT's US Patent #5,481,721, which is central to the dispute: "The present invention provides a means for implementing an extensible, distributed program in which one task is responsible for creating other tasks to communicate with. This is a master/slave relationship; the master can provide the slave with send rights to the master's port as part of the creation process. When the slave starts executing, it sends a Mach message containing send rights to its port and a token for its first proxy back to the master. The master then replies with an indication of whether the connection is granted, and what token to use for the first proxy. This 'bootstrap-meta-protocol' results in both tasks knowing about each other, allowing communication to ensue."

    What the objects say to one another over this shared port is almost immaterial to the patent; it's the method through which the port is negotiated and managed around which Mach's technology, and its associated patent, are based. The concepts you've just read about up to this point may become the critical points of debate over the next few years, assuming Apple's case against Android goes to trial, and also assuming (quite likely) that it will involve more competitive manufacturers than HTC. It's one thing to be open, but you can't open somebody else's ideas.

    But did Android do that? Even prior to today's case, there's actually been considerable debate among developers over why Android did not appear to take the Objective-C route.

    Android's runtime interpreter is a kind of Java that isn't really Java. That is to say, Android's Dalvik runs Java code, but it compiles it down to a different bytecode than a true Java virtual machine (VM). The Android Developers' forum explains that the system does this for relative efficiency: "Every Android application runs in its own process, with its own instance of the Dalvik virtual machine. Dalvik has been written so that a device can run multiple VMs efficiently. The Dalvik VM executes files in the Dalvik Executable (.dex) format which is optimized for minimal memory footprint. The VM is register-based, and runs classes compiled by a Java language compiler that have been transformed into the .dex format by the included 'dx' tool."

    Certainly it may seem efficient from the point of view of a developer who simply wants to get his app built. But in terms of processing efficiency, there's considerable complaint that Dalvik is actually inefficient, evidence for which appears in Google's own benchmark results for Dalvik apps compared to Sun Java and complied C.

    While NeXT's patented IAC process adopts an elegant communications scheme, Dalvik approaches the problem of sharing via a more direct, if costly, route -- efficient in the sense that it doesn't appear to require a patent to explain it. Seattle-based mobile software engineer Koushik Dutta cast a sharp spotlight on what he considered Android's inefficiencies, in a post for his personal blog in January 2009, comparing Dalvik to what he perceived as the much more efficient scheme adopted by Mono, the open source, cross-platform work-alike to Microsoft's .NET: "The two line summary is that Dalvik is designed to minimize memory usage by maximizing shared memory. The memory that Dalvik is sharing are the common framework dex files and application dex files (dex is the byte code the Dalvik interpreter runs). The first thing that bugged me about this design, is that sharing the code segments of dex files would be completely unnecessary if the applications were purely native. In Linux, the code segments of libraries are shared by all processes anyways. So, realistically, there is no benefit in doing this.

    "If the battery is the primary constraint on the device, why is Dalvik so concerned with minimizing memory usage?" Dutta continued. "I am by no means a VM design guru...but I can say the following with certainty...Battery life is primarily affected by how much you tax the processor and the other hardware components of the device, especially the use of 3G/EDGE and Wi-Fi radios. Interpreting byte code will tax the processor and thus the battery much more than native/JIT [just-in-time] code...Modern (Dream/iPhone comparable) hardware running Windows Mobile is rarely memory constrained, and they don't have a fancy memory sharing runtime...If all applications can suspend and restore at the system's whim, then memory consumption is trivialized."

    Dutta's explanation, in summary, appears to contrast the architecture of operating systems that adopt the principle of minimizing their memory footprints (Android) against those that take the more direct approach of suspending some apps for others to run (iPhone). Here's where it is important to note that Apple does not appear to be defending its iPhone, but rather technologies that are actually more relevant to MacOS.

    Nevertheless, it may be the very inefficiencies that Dutta pointed out, that could be Android's saving grace in its upcoming battle against Apple. If Android is indeed as inefficient as some say it is, it may not be violating anyone's patent at all.

    Copyright Betanews, Inc. 2010

    Add to digg Add to Google Add to Slashdot Add to Twitter Add to del.icio.us Add to Facebook Add to Technorati
  • Lien pour 'BetaNews.Com/2010/03/02/The_new_champion__Opera_s_all_or_nothing_bid_to_build_the_best_browser'

    The new champion: Opera's all-or-nothing bid to build the best browser

    Publié: mars 2, 2010, 7:18pm CET par Scott M. Fulton, III

    By Scott M. Fulton, III, Betanews

    Download Opera 10.5 Release Version for Windows from Fileforum now.

    Usually software companies have the luxury of picking their own deadlines, and typically -- especially in the case of open source or free programs -- those deadlines are allowed to slip or even lapse. But the European Commission gave Opera a solid opportunity to get back in the game, to be discussed once again in the same company as Mozilla Firefox, Google Chrome, and Apple Safari.

    Version 10.2 wasn't going to do it. We saw that back in December, with performance scores that were falling below those from the stable Opera 10.1. Among those browser users who do take advantage of their choice, speed is becoming more and more of a factor, as evidenced by Chrome's rising usage share. So last January, Opera made a strategic gamble: Dump 10.2, and throw everything behind an effort to re-create the Opera desktop browser for speed and efficiency.

    The main JavaScript processor engine, dubbed Carakan, is to the interpreter in Opera 10.1 what the Macintosh II was to the Apple II. They are worlds different. There is no reason for anyone today to use Opera 10.1; not to upgrade is about as sensible as hanging onto a 1975 Toyota Celica rather than accept a free 2010 Camry.

    Yet there was indisputably a rush to the finish, and even then, developers spent an extra day past the March 1 deadline when Microsoft delivered its browser choice screen to European Internet Explorer users. The big question now is, amid the rush, was Opera 10.5 rushed, or like the hero from the movie Tucker: The Man and His Dream, did the company polish the front end and leave the chasses further down the line to be fixed later?

    Some issues do remain. However, in our initial tests of the stable 10.5 this morning, the quirky drag-and-drop issues apparently were addressed. Selecting an item from the Bookmarks tab, then dragging it to the Personal bar, for instance, resulted in a copy (as opposed to a move) of that item -- not some other item, and not nothing at all. Selecting multiple items and moving them from folder to folder, worked. Dragging items to the Trash folder resulted in a move to the Trash (which makes more sense), followed by an opening of the Trash folder itself, enabling the user to empty the Trash in the next step. In all, drag-and-drop behaved consistently and as we expected -- the testing process worked in this instance, with the result being an improved browser.

    A screenshot from the release version of Opera 10.5, better but not yet 100% in the layout department.

    Improved, though not yet perfected, at this point are some of the layout discrepancies with complex CSS pages. We checked back in with the Olympic Hockey results page, which was first noted by an Opera 10.5 tester in a post to the company's blog responses over the weekend. The column from Facebook is perhaps most important, because it's the style of column that gets imported on thousands more pages than just this one. The stable Opera 10.5 now formats this column cleanly, so this fixes a multitude of pages to some extent. There's still some problems with the positioning of the medal count in the block reserved for it in the upper right corner -- it starts adding medalists beneath the bottom of the block rather than at the top of the interior. This is where developers tend to get into an argument over whether pages are actually developed to the Web standard, and whether the browser or the developer got it wrong. While all that arguing is going on, Firefox, IE, Chrome, and Safari users are reading this page just fine.

    One user today noted a similar layout discrepancy on Opera's own multi-language portal page, which laid out two elements in the middle of one another rather than adjacent to one another. Opera appears to have addressed this issue by completely changing the layout of that page to something simpler for now. Most of the messages to Opera's forum today consisted of congratulations, and very well augmented emoticons of support.

    Our discussions with Opera Software representatives over the past few days give us the impression that there is a certain class of non-crash discrepancy that Opera's developers set aside, in an effort to focus on potential "showstoppers" that could delay the final release. By "delay," I don't mean the kind that could throw things off by a month or more (as has historically been the case with Firefox) but by an hour or two. During the Release Candidate stage (there was actually an RC5 prior to this morning's RTM), the company restricted its feedback to a narrower set of testers which, we're told, included those who responded to forums. We did get the impression, however, that commenters who complained of issues they claimed were unaddressed since version 9, were put aside along with the layout glitches, to be handled at a later time.

    Problems were reported with upgrading Opera 10.1 to 10.5. Our advice is that such problems should be avoided by uninstalling Opera 10.1 first, then installing 10.5 fresh.

    So what we're seeing -- if I may be allowed to continue my automotive analogy for a moment -- is a completely renewed chassis and much more horsepower in the engine, but some work remaining to be done with the upholstery. Still, Opera is back in the hunt. The final build of 10.5 did reclaim some of the performance numbers it lost during the heavily accelerated RC period, scoring a 21.66 in our Windows 7 performance index (21-and-two-thirds the relative performance of IE7 in Windows Vista SP2), which is 314% of the performance of its 10.1 predecessor. Google's fastest browser at the moment, its dev build 335.1 of Chrome 5, scores a 19.88 on the same decathlon of tests on the same machine.

    In terms of computational speed, Opera is not yet the fastest, though it is disarmingly close -- as in, Julia Mancuso-to-Lindsey Vonn close. Opera 10.5 does have the fastest stable browser in the SunSpider battery, with a 68.64 relative score in Windows 7 compared to 58.55 for the latest stable Chrome 4 and 50.56 for the stable Safari 4. The Chrome 5 dev build just tops out at 69.83.

    This morning, Opera 10.5 slipped past the stable Chrome 4 in the SlickSpeed CSS selectors test (even though its CSS rendering could use improvement), with an 11.64 score versus 11.54 for Chrome 4. The development builds of both Safari and Chrome, however, are faster.

    Where Opera zips past the rest of the field at warp speed is in graphics performance, with a jaw-dropping 68.51 that is still better than double any other browser's score in the field, including development builds.

    As of this moment, the Opera development team is sprucing up their final releases for Mac and Unix -- even with no sleep. But now, they have managed an incredible feat: They haven't just put Opera back on the map. They successfully diverted the focus of much of our attention during this critical period in history away from where it most likely would have, and perhaps rightly should have, gone -- from Firefox, the most popular alternative to IE -- to the brand that some analysts believe fell below 1% usage share. Just like Bjorn Ferry in the cross-country pursuit a few weeks ago, the Swedish team has come back to claim gold.

    Copyright Betanews, Inc. 2010

    Add to digg Add to Google Add to Slashdot Add to Twitter Add to del.icio.us Add to Facebook Add to Technorati
  • Lien pour 'BetaNews.Com/2010/03/02/Apple_sues_HTC_for_iPhone_patent_infringement'

    Apple sues HTC for iPhone patent infringement

    Publié: mars 2, 2010, 4:24pm CET par Tim Conneally

    By Tim Conneally, Betanews

    Apple has sued smartphone maker HTC for patent infringement, citing 20 patents related to the iPhone's user interface, architecture, and hardware, a statement from the company said this morning.

    A statement from Apple CEO Steve Jobs today said, "We can sit by and watch competitors steal our patented inventions, or we can do something about it. We've decided to do something about it. We think competition is healthy, but competitors should create their own original technology, not steal ours."

    The lawsuit was filed both with the US International Trade Commission and in US District Court in Delaware, where Nokia has been battling Apple on similar grounds.

    Apple Patents included in the suit:

    • "Time-Based, Non-Constant Translation Of User Interface Objects Between States"
    • "Touch Screen Device, Method, And Graphical User Interface For Determining Commands By Applying Heuristics"
    • "Unlocking A Device By Performing Gestures On An Unlock Image," (this is the newest patent involved, granted on February 2, 2010)
    • "List Scrolling And Document Translation, Scaling, And Rotation On A Touch-Screen Display"
    • "System And Method For Managing Power Conditions Within A Digital Camera Device"
    • "Automated Response To And Sensing Of User Activity In Portable Devices"
    • "GMSK Signal Processors For Improved Communications Capacity And Quality"
    • "Conserving Power By Reducing Voltage Supplied To An Instruction-Processing Portion Of A Processor"
    • "Object-Oriented Graphic System"
    • "Object-Oriented Event Notification System With Listener Registration Of Both Interests And Methods."

    Copyright Betanews, Inc. 2010

    Add to digg Add to Google Add to Slashdot Add to Twitter Add to del.icio.us Add to Facebook Add to Technorati
  • Lien pour 'BetaNews.Com/2010/03/02/Google_buys_Flickr_s_editing_tool__Picnik'

    Google buys Flickr's editing tool, Picnik

    Publié: mars 2, 2010, 1:14am CET par Tim Conneally

    By Tim Conneally, Betanews

    Web-based photo editing suite Picnik announced today that it has been acquired by Google for an unspecified amount that Picnik CEO Jonathan Sposato called a "very, very happy number."

    The startup opened in 2005 and was chosen to be Flickr's default photo editor in 2007 when Yahoo was introducing a host of new features to the popular photo sharing site. Long before Adobe released its Web-based version of Photoshop, Picnik was already going strong.

    Google will reportedly leave Picnik as its own brand for now, and allow it to be integrated into third party sites, including Flickr. Brian Axe, Product Management Director for Picasa, today said there will be no announcements about any significant changes to Picnik today, but Google will be "collaborating closely with them to improve the online photo editing experience on the Web."

    It's the second piece of news today that has involved Google and Yahoo in a strange symbiosis.

    The first bit came in a rather unlikely place: a Motorola Backflip unboxing. Adding to the Backflip's reputation as the strangest Android device to date, the default search engine is Yahoo and not Google.

    Naturally, Motorola's MotoBLUR interface is built on the open source Android framework so a "Google Experience" should not necessarily be expected, but it is nonetheless interesting to see a Yahoo home screen widget on Android instead of a Google one.

    For now, it appears that Google's Picasa and Yahoo's Flickr will share a photo editing suite as well.

    Copyright Betanews, Inc. 2010

    Add to digg Add to Google Add to Slashdot Add to Twitter Add to del.icio.us Add to Facebook Add to Technorati
  • Lien pour 'BetaNews.Com/2010/03/02/Early_word_on_EU__choice_screen___May_not_be_random__may_not_be_obvious'

    Early word on EU 'choice screen:' May not be random, may not be obvious

    Publié: mars 2, 2010, 1:09am CET par Scott M. Fulton, III

    By Scott M. Fulton, III, Betanews

    As IE6 and IE7 users throughout Europe turn on their Windows Vista- and XP-based computers to notice, for the first time, the opportunity to switch Web browsers from Microsoft Internet Explorer to something they may have never heard of, their manufacturers are preparing for an influx of new customers.

    But they may also be preparing to lower expectations just in case the market share numbers for Firefox or Chrome or Opera or Safari fail to swing wildly positive overnight. Last week, Mozilla launched its opentochoice.org blog, ostensibly to help spread the word about the impact the choice screen may make on European computing habits. On Friday, however, the blog posted the results of a six-country, 6,000 respondent consumer poll conducted by advertising research firm Ipsos MORI.

    The firm itself has yet to post detailed results, though the question it posed to consumers may as well have been an advertisement: "Were you aware that the European Commission has adopted a decision ensuring the millions of Microsoft users across the European Union who have Internet Explorer installed as their default Internet browser will now have to be offered the chance to choose the browser they want to use via a choice screen which appears on their PC/Laptop screen?"

    Only 30% of respondents in Poland answered yes to the above question, with 19% of Spaniards replying in the affirmative. Results for participants in France, Germany, Italy, and the UK fell in-between.

    Friday evening, a member of Mozilla's new blog with the handle Pony wrote candidly about being suspicious that the choice screen was some kind of malware: "I wasn't aware of this. The browserchoice window popped up on my laptop today and I was pretty suspicious and tried to close it down. There wasn't an explanation of why it was there, and it was so bland that I thought it was some dodgy pop-up trying to trick me into downloading something bad. I even looked up browserchoice.eu on a Whois to see who owned it, but still thought it was dodgy as I didn't see quite why Microsoft would own a domain like this rather than use their well-known "trusted" microsoft.com. Feel a bit stupid now -- I've been meaning to download Firefox for ages."

    The final browser choice screen, available from browserchoice.eu

    The final browser choice screen, available from browserchoice.eu.

    In order to allay concerns from browser makers that Microsoft would give itself top billing on the browser screen, the company promised to the European Commission that it would randomize the order of the top five browsers in the first panel, so that IE8 would not always appear first. Right away today, there were complaints in some circles that Microsoft wasn't really randomizing the order.

    Those complaints were given some credence when the Slovakian tech site DSL.sk ran tests on the underlying JavaScript code for the browserchoice.eu Web page, and determined that the distribution of browser brands among the top five slots was not even. Despite the translated page appearing to say the test was run in Internet Explorer, it's difficult to avoid seeing DSL.sk's screenshots of the test clearly depict Google Chrome as the browser.

    These numbers were probably impossible to resist for IBM software architect Rob Weir. You may recall Weir from his prominent involvement in the ODF/OOXML debate three years ago. Weir was an active opponent of Microsoft's Office XML standard being approved by the ISO, though throughout that episode, he always accepted the facts in front of him. Over the weekend, Weir put his mind to the task of investigating the claims of unfair distribution. As he discovered, Microsoft's code uses the Math.random() function of the standard JavaScript library. But rather than craft a proven shuffling algorithm, architects of the browser screen apparently took the simplest option: filling the array sequentially {0,1,2,3,4}, and then randomly swapping their locations with one another left or right five times. Imagine a poorly-shuffled street corner shell game, and you get the idea.

    "Microsoft...fell for the well-known trap," Weir wrote. "What they did is sort the array, but with a custom-defined comparison function. JavaScript, like many other programming languages, allows a custom comparator function to be specified... This is a very flexible approach, and allows the programmer to handle all sorts of sorting tasks, from making case-insensitive sorts to defining locale-specific collation orders, etc...Since Math.random() should return a random number chosen uniformly between 0 and 1, the RandomSort() function will return a random value between -0.5 and 0.5. If you know anything about sorting, you can see the problem here. Sorting requires a self-consistent definition of ordering...All of these statements are violated by the given Microsoft comparison function. Since the comparison function returns random results, a sort routine that depends on any of these logical implications would receive inconsistent information regarding the progress of the sort. Given that, the fact that the results were non-random is hardly surprising."

    So Microsoft's solution, once again, is somewhat inelegant. But who does it benefit? Not exactly Microsoft, Weir discovered. The distribution of the random pattern should give each browser 20% distribution on every slot, if it were fair. As it turns out, IE, Firefox, and Safari all get about 25% distribution in the #1 (leftmost) slot, with Opera #1 16% of the time and Chrome #1 9% of the time. More often than any other slot, IE is positioned #2 (28%), Firefox is positioned #2 (28%), Opera is positioned #3 (26.4%), Chrome #4 (38%), and Safari #5 (53%).

    Although it's tempting to blame the randomization function in IE's library, Weir blames the developers of the browserchoice.eu Web site: "So given the above, we know two things: 1) The problem is real. 2) The problem is not related to a flaw in Internet Explorer."

    Copyright Betanews, Inc. 2010

    Add to digg Add to Google Add to Slashdot Add to Twitter Add to del.icio.us Add to Facebook Add to Technorati
  • Lien pour 'BetaNews.Com/2010/03/02/Pew_Internet_study_offers_Microsoft_s_mobile_strategy_a_glimmer_of_hope'

    Pew Internet study offers Microsoft's mobile strategy a glimmer of hope

    Publié: mars 2, 2010, 12:05am CET par Joe Wilcox

    By Joe Wilcox, Betanews

    How disastrous is Microsoft's hobbled mobile strategy? Today's Pew Internet report, "Understanding the Participatory News Consumer," offers some glimpse and even some hope. The report reveals that more Americans than ever rely on their cell phones for news and other information. Speaking personally, I find the Google News widget on my Nexus One to be indispensable.

    Fifty-three percent of US adults "access the Internet wirelessly either through a laptop or a cell phone, BlackBerry or other handheld device," according to the report. Adults? What about measuring teen Internet usage -- and not just cell phones but WiFi devices like Apple's iPod touch? (More griping about Pew overlooking teens will come later in the post.)

    "Pew Internet studies have shown that wireless Internet users are different from other online adults in important ways: they are 36 percent more likely than wired Internet users to access the Internet on a given day, and they engage in virtually all online activities (including email, social networking, and blogging) at higher rates than other internet users."

    According to Pew, about 80 percent of US adults have cell phones, with 37 percent connecting to the Internet or email. "Overall, 26 percent of American adults say they get some form of news via cell phone -- that amounts to 33 percent of adult cell phone owners and 88 percent of adults who have mobile internet." For the broader category of cell phone users, those seeking news varies by age: 43 percent for those under 50 and 15 percent for those over the big five-oh.

    What do these mobile information hounds most care about? The weather (72 percent); news and current events (68 percent); sports scores (44 percent); traffic data (35 percent); financial data (32 percent); and news alerts sent by text or email (31 percent).

    Wireless News

    Analysts love to breakout data into demographic subgroups, and the Pew team is no exception, identifying "on-the-go-news consumers."

    Not surprisingly, on-the-go news consumers maximize their cell phone use. They are 67 percent more likely than other cell phone users to text message, more than twice as likely to take pictures with their phones, and four times as likely to use their phones to instant message. They are also especially heavy Internet users -- 80 percent of this on-the-go group are online on a given day, compared with just 67 percent of other internet users -- and they engage in activities such as blogging (20 percent v. 11 percent ), using social networking sites (73 percent v. 48 percent), and using status update sites like Twitter (29 percent v. 14 percent) at significantly higher rates than other internet users.

    Pew surveyed 2,259 US adults, ages 18 or older, between Dec. 28, 2009 and Jan. 19, 2010. However, the number referring to "Internet users" is 1,675. The valuable data is sadly incomplete because PEW ignored teens, which is simply inconceivable to me.

    As for what this all means for Microsoft's mobile strategy:

    1) More than half of US consumers already get news and other real-time information wirelessly -- laptops more than cell phones. Microsoft should seek to improve news gathering on Windows laptops and transfer the behavior to Windows Phone 7 Series. Tactically, Internet Explorer 8 features like Accelerators and Web Slices are a starting point. New Outlook social networking features are another.

    News on Handhelds

    Microsoft can then use established behavior on the desktop and leverage it to Windows Phone 7 Series, by offering similar capabilities. Consumers should be able to sync capabilities and their behavior from mobile Windows desktop to Windows Phone.

    2) Microsoft should retool Bing for better news and information dissemination coordinated across the desktop and mobile device -- something Google already is doing with newer features like GPS location-based search and inclusion of news and weather widgets on Android 2.1 handsets. Based on other sections of the PEW report, Microsoft is right to make social networking such an important and pervasive feature in Windows Phone 7 Series.

    3) "On-the-go-news consumers" are an ideal demographic for Microsoft. According to Pew Internet: "The typical on-the-go news consumer is a white male, age 34, who has graduated from college and is employed full-time." Many gadget companies target younger (ages 25-34), educated males for a reason. The same demographic going after online information may also be likely to buy bleeding-edge gear -- say, a new Windows Phone.

    News on the Go

    Pew's study may also help explain some odd findings from last week's AdMob study -- that the majority of Android users are male (73 percent). By comparison, iPhone: 57 percent. Additionally, 51 percent of Android users are between 25 and 44 compared to 42 percent of iPhone users. By the way, 65 percent of iPod touch users are under 17 -- and Pew ignored that market segment in its study? Shame. Shame.

    Microsoft should focus some -- perhaps much -- of its initial Windows Phone marketing on males 25-44, provided OS and applications capabilities are information and social sharing focused.

    [Editor's Note: All charts are from Pew Internet report "Understanding the Participatory News Consumer."]

    Copyright Betanews, Inc. 2010

    Add to digg Add to Google Add to Slashdot Add to Twitter Add to del.icio.us Add to Facebook Add to Technorati
  • Lien pour 'BetaNews.Com/2010/03/01/US_government_lays_down_the_law_in_messy_online_ticketing_fiascos'

    US government lays down the law in messy online ticketing fiascos

    Publié: mars 1, 2010, 9:53pm CET par Tim Conneally

    By Tim Conneally, Betanews

    Four men from a San Francisco company called Wiseguy Tickets Inc. have been indicted in a $25 million online ticket fraud scheme, the US Department of Justice announced today.

    The four men -- Kenneth Lowson, 40, Kristofer Kirsch, 37, Faisal Nahdi, 36, and Joel Stevenson, 37 -- have been indicted on conspiracy to commit wire fraud and to gain unauthorized access and exceed authorized access to computer systems, and 42 additional counts of wire fraud; gaining unauthorized access and exceeding authorized access to computer systems; or causing damage to computers in interstate commerce.

    Wiseguy Tickets would allegedly bypass online ticketing limitations so they could purchase huge blocks of the best seats for the most sought after concerts, live theater, and sporting events.

    Vendors such as Ticketmaster, Tickets.com, MLB.com, and MusicToday do not let ticket resellers and brokers buy bulk tickets online. Instead, access is restricted to individuals who must register their sessions through authentication software such as CAPTCHA, an method where the user must type in the letters he sees in a scrambled onscreen image to enter a site. Mechanisms like this are meant to deter automated ticket purchases.

    In 2008, Ticketmaster won a suit against Pittsburgh-based RMG Technologies for selling software that let brokers bypass Ticketmaster's authentication systems and online sales limits.

    According to the indictment, Wiseguys Tickets developed a network of so-called "CAPTCHA Bots" with a Bulgarian software developer which gave Wiseguys the ability to buy tons of tickets the moment they went on sale. The company amassed its own database of hundreds of thousands of potential CAPTCHA test answers which the bots could then identify and complete faster than a person could. The group disguised their activities by setting up fake companies, fake domains, and fake email addresses.

    With these methods in place, Wiseguys managed to buy 1.5 million tickets, including some of the most notoriously expensive shows around. Wiseguys reportedly bought nearly half of the general admission floor seats for a Bruce Springsteen concert in 2008.

    Tickets to Bruce Springsteen shows have been so scarce, and sold at such inflated prices, that the Federal Trade Commission has had to get involved.

    In what the FTC called a "bait and switch" maneuver, Ticketmaster was reportedly routing customers to an affiliate site called TicketsNow where it would sell tickets to 2009 Springsteen shows at triple or even quadruple their face value. Still other customers reportedly bought tickets directly from Ticketmaster.com but never got them.

    Live Nation and Ticketmaster recently settled with the FTC and agreed to provide full refunds to consumers who bought tickets to 14 Springsteen concerts at dramatically inflated prices.

    The "Wiseguys," however, won't get off so easily. Each defendant faces up to five years in prison on the conspiracy charges, and up to 20 years in prison for wire fraud; plus a further $250,000 fine per count of hacking (a.k.a., "gaining unauthorized access and exceeding authorized access to computers").

    Copyright Betanews, Inc. 2010

    Add to digg Add to Google Add to Slashdot Add to Twitter Add to del.icio.us Add to Facebook Add to Technorati
  • Lien pour 'BetaNews.Com/2010/03/01/The_porn_free_iPhone__Not_exactly'

    The porn-free iPhone? Not exactly

    Publié: mars 1, 2010, 9:35pm CET par Carmi Levy

    By Carmi Levy, Betanews

    At first blush, Apple's decision to cull a few thousand sexually suggestive titles from its iTunes App Store may seem like a puritanical attempt to cleanse its consumer-friendly image of any taint of smuttiness. But like everything related to Apple, the reality distortion field that surrounds the company makes even this assessment a questionable one.

    Don't think for a second that wannabe-porn (what Apple called "overtly sexual content" in its removal notices to affected developers) won't be returning soon to any platform with an Apple logo on it. And don't think for a second that Apple will be upset about welcoming more skin to its ecosystem.

    But first, let's look at last month's apparent purge of pseudo-porn. Apple's got a lot of good reasons to clean things up. Namely, as it gets ready to ship iPads later this month, it recognizes that the demographic spread of its iPhone/iPod touch universe will shift once the larger-screened devices hit the market. As iPads pop up in the home and at school, the last thing Apple wants or needs is for a less-than-optimally-supervised child to accidentally stumble into the kind of content that was once delivered surreptitiously to one's doorstep in a paper bag (no, not my own doorstep, but gee, thanks for asking).

    It's all about control

    Carmi Levy Wide Angle Zoom (v.2)Don't get me wrong, though: Apple doesn't necessarily need or want a totally skin-free App Store. It simply wants to be able to control the not-suitable-for-prime-time content that does ultimately get approved. There's money to be made from all forms of porn, and publicly traded Apple never met a profit-driving opportunity it didn't like. That it may or may not be wearing a bikini in the process is immaterial to Apple.

    So while slicing 5,000 or so somewhat blue offerings from its App Store could be seen as correcting an earlier mistake to approve them in the first place, it's really little more than Apple's attempt to control how those apps appear and how they're purchased. Those 5,000 apps will be back before long, and they'll be displayed on the online equivalent of fresh new shelving.

    To keep things simple, let's call anything up to and including February 2010 the "pre-porn era." While Apple happily approved titles from well-known publishers like Playboy and Sports Illustrated, as well as lesser lights like On The Go Girls and Iugo Mobile Entertainment, it didn't categorize them as uniquely as, say, the neighborhood video store would typically treat its adult material. We're all familiar with the stereotype of the cordoned off section at the back of the store, the one kids aren't supposed to enter. The App Store wasn't quite as segregated during this era, so apps with "overtly sexual content" were finding their way into other, more mainstream areas of the online resource.

    It was the Web-based equivalent of putting soft-core next to Pixar's latest release. Until it had a way of keeping the iffy stuff permanently under wraps, Apple's only real solution was to remove it entirely while it programs a workable, long-term solution.

    Another wall in the garden

    That solution will likely take the form of an "Explicit" section in the App Store. Developers are already atwitter over reported sightings of this new category, and Apple's non-confirmation notwithstanding, it would result in a virtual kind of back-of-the-store section -- one that would keep the kids from accidentally encountering things they shouldn't...and developers from complaining that their more mainstream, seriously-themed titles were appearing cheek by jowl (I know, ew, but humor me here) with the titillating ones. Walling off the garden solves the conflict neatly just as it sets the stage for ongoing profits from this growing market space.

    In Apple's post-porn era, which essentially begins now, segregation of content is crucial as the iPhone OS universe continues to expand beyond the original phone-based device. The iPod touch has become the de facto choice of today's kids and teens. For parents not ready to go the full-on cell phone route with their kids, the iPod touch is the ideal compromise as it isn't a simple game machine like the Nintendo DS/DSi and Sony PSP, and it doesn't come with the monthly hit from a wireless carrier. The iPad will extend this even further, as schools are actively exploring the tablet device's educational potential. You can't very well have questionable titles creeping into the mix when the principal is doing her research.

    How do you define it?

    If you're a parent, of course, this entire discussion doubtless makes you feel a little dirty. Porn, after all, is the scourge of the Internet. We can debate all day how we choose to define the various grades of porn, but ultimately there will be no agreement. Apple's "overtly sexual content" is someone else's soft-core porn. And to my prudish, spinster aunt who never smiled for as long as I knew her, the swimsuit catalog that appeared in her mailbox like clockwork every spring was the pornographer's equivalent of a ticket to a very hot, eternal place.

    In any form, pornography's pervasiveness defies the imagination just as it opens up business opportunities for those with the cojones to set the morality of it all aside for a bit. As a profit-seeking, publicly traded company, Apple is simply pursuing a market opportunity that presented itself when developers first decided to push the boundaries of skin -- and taste -- and got the first of those now-disputed 5,000 apps approved.

    The fact that Apple has decided it doesn't want porn ruling its platform doesn't mean it doesn't want porn at all. It simply means that Apple wants to rule everything that goes on in its software universe. That some of the titles may be considered by some pornographic, or overtly sexual, or whatever, is irrelevant to the company. In the coming months, Apple will put the proper controls and processes in place to effectively manage the content and the revenue it's expected to generate.

    Anyone who thinks the same thing isn't about to happen on every other mobile platform in existence is at risk of misunderstanding just how critical this skin-flecked revenue stream is to everyone's future business. Android and BlackBerry users? You're next.

    Carmi Levy is a Canadian-based independent technology analyst and journalist still trying to live down his past life leading help desks and managing projects for large financial services organizations. He comments extensively in a wide range of media, and works closely with clients to help them leverage technology and social media tools and processes to drive their business.

    Copyright Betanews, Inc. 2010

    Add to digg Add to Google Add to Slashdot Add to Twitter Add to del.icio.us Add to Facebook Add to Technorati
  • Lien pour 'BetaNews.Com/2010/03/01/Do_not_even_turn_on_your_PS3_today__Sony_warns'

    Do not even turn on your PS3 today, Sony warns

    Publié: mars 1, 2010, 7:50pm CET par Tim Conneally

    By Tim Conneally, Betanews

    Since yesterday evening, PlayStation 3 users have been reporting difficulties in connecting their consoles to the PlayStation Network for online gameplay and system updates. While it was first thought to be a network-related issue, Sony has warned that there is a much more widespread issue currently affecting older PlayStation 3's.

    Sony's offical statement lists the following errors as a part of this internal clock bug:

    • The date of the PS3 system may be re-set to Jan 1, 2000. When the user tries to sign in to the PlayStation Network, the following message appears on the screen; "An error has occurred. You have been signed out of PlayStation Network (8001050F)."
    • When the user tries to launch a game, the following error message appears on the screen and the trophy data may disappear; "Failed to install trophies. Please exit your game."
    • When the user tries to set the time and date of the system via the Internet, the following message appears on the screen; "The current date and time could not be obtained (8001050F)."
    • Users are not able to play back certain rental video downloaded from the PlayStation Store before the expiration date.

    "If you have a model other than the new slim PS3, we advise that you do not use your PS3 system, as doing so may result in errors in some functionality, such as recording obtained trophies, and not being able to restore certain data," Sony warned this afternoon.

    The company hopes to have the issue resolved by tomorrow.

    Copyright Betanews, Inc. 2010

    Add to digg Add to Google Add to Slashdot Add to Twitter Add to del.icio.us Add to Facebook Add to Technorati
  • Lien pour 'BetaNews.Com/2010/03/01/Let_the_Internet_Explorer_6_death_watch_begin'

    Let the Internet Explorer 6 death watch begin

    Publié: mars 1, 2010, 7:36pm CET par Joe Wilcox

    By Joe Wilcox, Betanews

    All praise the great gods of the InterWeb for their divine intervention. March 1, 2010 is Internet Explorer 6's judgment day, when mighty Google and Microsoft looked down from the heavens -- or Mt. Olympus, if you prefer - and cast IE6 into the abyss. Starting today, Google is beginning to phase out support for Internet Explorer 6, while Microsoft presents European Union Windows users with a ballot screen for choosing even the most obscure browser, but not IE6. Microsoft's once mighty browser has fallen -- and not a second soon enough.

    IE6's heart turned evil long ago. Microsoft released the browser in 2001 only to later let development languish. Only after Mozilla released Firefox in late 2004 and, around the same time, Google showed that bundled search could make browsers profitable did Microsoft start seriously working on IE7. But by the then, IE6's cold-hearted proprietary standards had polluted the InterWeb with wicked metatags.

    During IE6's reign of terror -- before there were real alternative browsers other than Opera -- Website designers paid tribute by using a DOCTYPE (or Document Type Declaration) tag to open browser-specific pages or stylesheets. DOCTYPE was created with other page-rendering purposes, but because of IE6's wicked dictatorship -- ah, proprietary standards -- it came to be mainly used for setting the browser's layout mode, mainly "quirks" or "standards."

    Meanwhile, IE6 amassed a great group of worshipers -- malware writers looking to exploit security vulnerabilities for profit. In the early "noughties," IE6 brandished ActiveX as a great sword and shield, unleashing lightning that promised to spread a great horde of plug-ins across the InterWeb. IE6 blinded enterprise IT managers with great ActiveX promises. By adopting ActiveX, IT managers could automate processes, thus saving time and money. Their promised reward: Heavenly respite from their labors -- the chance to leave the office at 5 p.m. and enjoy a real life, rather than be chained to Web servers demanding manual servitude.

    But IE6 betrayed enterprise ActiveX followers by allowing malware worshipers to spread malicious code across the InterWeb and Intranets. The promise of early work days became long hours of work nights trying to repair the damage done by ActiveX and other IE6 security exploits.

    Like Zeus, who often couldn't keep his god children in check, Microsoft did little to reign in Internet Explorer 6 for far too long. After all, IE6 was Microsoft's child, as wicked as it had become. Parents love even the wickedest child. Now, with the birth of Internet Explorer 8 and growing InterWeb population demands to oust IE6, Microsoft has finally taken action. But only after the great god Google acted first. Google pledged to smite IE6 before Microsoft, even though their first strikes come the same day.

    IE6 will be missed by malware worshipers and enterprise IT managers too dependent on ActiveX controls to easily switch browsers. ActiveX remains in IE7 and IE8, but Microsoft caged the plug-in architecture by changing the default settings. ActiveX is "Prometheus Bound," unless freed by IT managers or end users changing the default settings.

    Google and Microsoft may have struck down IE6, but the browser won't easily or suddenly go into the abyss. Too many worshipers remain. According to Net Applications, 19.76 percent of Internet users used IE6 in February -- that's more than IE7 (13.57 percent) but not IE8 (22.52 percent). IE6 usage share was more than Apple Safari, Google Chrome and Opera combined (12.41 percent). Even for the great gods Google and Microsoft -- and the massive powers of monopoly -- IE6 won't easily be vanquished. But at least they're finally trying.

    The IE6 death watch is finally underway. The question: How long before the browser is cast down into oblivion? I ask Betanews readers for predictions. How long do you think it will take before IE6 usage reaches zero? When will you and all the InterWeb population be free from IE6's lordship? Please answer in comments.

    Copyright Betanews, Inc. 2010

    Add to digg Add to Google Add to Slashdot Add to Twitter Add to del.icio.us Add to Facebook Add to Technorati
  • Lien pour 'BetaNews.Com/2010/03/01/The_mad_rush_to_release_Opera_10.5__Two_months__work_in_one_weekend_'

    The mad rush to release Opera 10.5: Two months' work in one weekend?

    Publié: mars 1, 2010, 7:24pm CET par Scott M. Fulton, III

    By Scott M. Fulton, III, Betanews

    Download Opera 10.5 Release Candidate 4 for Windows from Fileforum now.

    Just a handful of weeks ago, the developers of Opera 10.5 were calling their "pre-alpha" build dangerous if used to run a nuclear reactor facility. Over the weekend, in what appears to have been a round-the-clock effort to compress a few months' work into a few days' time, Opera Software ticked through four release candidates of its latest Windows-based Web browser.

    The reason, of course, is Microsoft's rollout of its browser choice screen for European users of older versions of Internet Explorer. Some users reported seeing the screen for the first time over the weekend, though the full-scale rollout began in earnest today.

    Judging from the fury of messages posted to Opera's developers' site over the past 72 hours, the team has been able to address some of the major bugs reported by testers in the field. Some. But others are complaining that problems continue even with the latest RC4 build posted this morning, including drag-and-drop problems discovered by Betanews last week and verified by others in the field. That somewhat "wonky" behavior persisted for us this morning -- for example, with the problematic Bookmarks tab (where bookmarks are managed in 10.5), we tried dragging a bookmark to the Trash can only to find the entire folder in which that bookmark appeared, was sent there instead.

    Betanews isn't alone here; at least one other tester in the field is reporting similar problems as of just this morning. "Is it not a waste of time to post a new build for every two fixed bugs," reported one tester today. "It is getting to be ridiculous."

    One tester with handle mrd disagreed: "Ideally (but in the real world almost never) you want less bug fixes per release, because then it's easier to nut out any regressions caused," he wrote.

    For others, it's getting to be quite exciting. Many are expecting an RTM edition to go live sometime today. Some have suggested that it may be more important for Opera to go ahead and call it finished now, and just post hotfixes over the coming days for remaining issues.

    Writes Idan Adar, "People need to understand that 10.5 is already a huge step forward from 10.10. People need to understand that at some point a software must get released, despite all issues -- new and old. If any of you guys actually follow these snapshots in this blog, then you also know that a short while after 10.5 is out there will be new snapshots of whatever comes next."

    But there appear to be a truckload of those issues, and testers are providing evidence through screenshots.

    The slightly tweaked transparent skin of Opera 10.5 RC4 still has problems.

    In our own continued tests, with RC4, we noted a few tweaks had been made to the new translucent skin since Beta 2. We also discovered that one of the peculiarities we discovered last week in the layout of the Tab bar when wrapping (multi-row) is turned on -- the creation of an excess gap along the right side -- only occurs on accounts where Windows font magnification is set higher than 100%. At 100% magnification, the trash can icon rests nicely along the right side of the window; but with higher magnification, it gets situated more toward the middle, off by its lonesome.

    How Facebook reported the results of the Gold Medal Canada vs. US hockey game, rendered in Firefox 3.6.

    Other testers are reporting the following issues: smooth scrolling that isn't smooth anymore; improper rendering of Chinese characters, with spaces between each one; some HTML5 videos not playing in the browser while others will; the drop-down list from the address bar occasionally showing up with a transparent backdrop (rendering the opaque contents illegible); and CSS objects that don't line up properly, such as in the test you're seeing here. Pictured above is how Facebook reported the results of Sunday afternoon's classic Canada vs. US men's Olympic hockey game, as rendered in Mozilla Firefox 3.6 (stable version).

    The same hockey results rendered by Opera 10.5 RC4.

    And here is how Opera 10.5 RC4 renders the same page. Note the contents of the table in the middle overlap their boundaries, that the Facebook logo in the table at right is completely obscured, and also that the Medal Count box in the upper right corner appears completely empty. If you look very closely, the contents that should be in that box appear below it instead, peeking out from in-between the borders of the sporting event category buttons.

    For some, sites with streaming content fail to load entirely, such as Last.fm. Early Betanews tests this morning revealed that with the recent bug fixes, Opera 10.5's performance took a hit. We also found evidence that Opera wasn't the only company with developers working overtime: Google has turned the burners on high for Chrome 5. As a result, what was a three-point gap on our Windows 7 performance index has now been cut to less than one point: a 20.70 overall score for Opera versus 19.88 for Chrome 5 dev build 335.1. Chrome leads over Opera, either slightly or substantially, in all the computational tests; it's in graphics and rendering where Opera holds a little bit of an edge. It lost its edge in table rendering to Chrome 5 this morning.

    Long-time Opera users are excited to see their favorite product back in the hunt for browser supremacy, and there's no doubt that this hunt has improved the product significantly. But the rough edges will be the first edges that newcomers to Opera see this week -- folks who haven't even heard of Opera Software, will be trying it for the first time. Those hotfixes, if they're in the works, had better come quickly.

    Copyright Betanews, Inc. 2010

    Add to digg Add to Google Add to Slashdot Add to Twitter Add to del.icio.us Add to Facebook Add to Technorati
  • Lien pour 'BetaNews.Com/2010/03/01/Greener_Gadgets_2010__The_race_to_make_things_out_of_better_things'

    Greener Gadgets 2010: The race to make things out of better things

    Publié: mars 1, 2010, 4:59pm CET par Jacqueline Emigh

    By Jacqueline Emigh, Betanews

    When you buy a PC or some other CE gadget, what kinds of substances are actually inside it...and what's being used to ship it to your house? At the Consumer Electronics Association's Greener Gadgets 2010 in New York City last week, ecologically oriented speakers touched on that question, in some cases proposing alternative materials -- such as cork or "Ecocradle" -- that they'd like to see show up in those places instead.

    Yves Behar, founder of the Fuseproject product design agency, held forth on how gadgets can be "desirable" and "in demand" while at the same time friendly to the environment.

    As a few examples of this combination of traits, Behar cited Herman Miller's energy-efficient LED lights, Bluetooth headphones from Jawbone, and PCs that he personally helped to design earlier in his career for the One Laptop Per Child (OLPC) project.

    But what's actually inside the "typical laptop" PC? Leo Bonanni, founder of Sourcemap.org, provided his answer by pointing to a slide of one of the many "sourcemaps" created by the open source group to illustrate the supply chain origins and carbon footprints of various objects.

    Bonanni's sourcemap of the typical laptop includes about 50 ingredients, including steel from the Russian Federation, copper from Chile, nickel from Australia, and glass from Kentucky, along with aluminum, cadmium, and lead. The latter two ingredients often end up being often reused in children's jewelry, he noted. "We only have something for a short time in its life," according to Bonanni, who is also a PhD. candidate at MIT Media Lab. "We're just kind of shepherding it from one point to another."

    Participants in the Greener Gadgets Conference in New York City, February 26, 2010.

    Pictured left to right: Sarah Rich, senior editor, Dwell; Julian Lwin, owner, Lwindesign; and Andrew Wagner, editor-in-chief, ReadyMade, participating in the Greener Gadgets conference in New York City last February 25. [Photo credit: Jacqueline Emigh]

    Through the information in the sourcemaps about carbon footprints, "You can say, 'We are exactly this green.'"

    Aside from the laptop map, other popular sourcemaps on the .org site include maps for a toothbrush, a bottle of Poland Springs water, a Tesla Roadster, a Toyota Prius, and a giant TCR '04 bicycle.

    Bonanni didn't precisely say whether he believes the materials in a "typical laptop" are environmentally sound. But Adele Peters, a participant in this year's Greener Gadgets design contest, clearly thinks she's come up with a better alternative to the computer mouse that ships in the same box as so many desktop PCs.

    Peters' entry in the contest, Corky, is a wireless mouse designed to be powered by the motion of your hand, thereby eliminating the need for batteries. Corky's shell is made of cork recycled from bottlecaps, whereas its other components come from recycled plastic.

    The Corky self-energy-generating mouse, one of the entrants in the 2010 Greener Gadgets contest.

    "Movement back and forth on the desk is captured by elements within the mouse shell. Buttons on the left and right each engage a piezoelectric element which stores the energy generated. The scroll wheel actuates another element as it turns," according to literature posted on the Green Gadgets site.

    Corky made it onto a list of ten finalists culled from visitors' votes on the Web site. But in two subsequent rounds of votes held at the event -- one of them by an "American Idol"-style panel of three judges, and one by the audience itself -- the mouse got outvoted by several other green innovations.

    First Place in the awards contest went to AUG Living Goods, a mobile phone app that scans bar codes to give you information about the foods you're buying. Taking Second Place was the Empower Chair, a glider-style chair which stores and reuses energy from the motion of the glider. The third slot went to Illumi-Charger, a grid-free USB wall charger.

    One of the judges, ReadyMade Editor-in-Chief Andrew Wagner, voiced doubts that motion alone would be enough to power the Corky mouse.

    Eben Bayer, another presenter at Greener Gadgets, showed a green alternative to the Styrofoam packing that turns up in so many shipments of consumer electronics products.

    "Our vision is to rid the earth of Styrofoam," said Bayer, COO of Ecovative Design LLC. In his talk, Bayer repeatedly referred to Styrofoam as "toxic white stuff."

    Beyond its role as a packing material, Styrofoam is also used inside the walls of homes. The EPA estimates that the material consumes 25% of all landfills, according to Bayer.

    "It's still going to be there a year later because this stuff doesn't break down," he added.

    Bayer's alternative, Ecocradle, uses husks from feedstocks such as buckwheat -- "which would otherwise get burned or dumped into the ocean" -- bound together by glue made of mycelium, the regenerative part of the "ecologically sustainable" mushroom.

    Unlike the environmentally friendly corn ethanol peanuts used recently, Ecocradle is moldable to support the shapes of various electronic components, according to Bayer. He said he hopes that if someone ever tosses Ecocradle packing by the roadside, "you'll [soon] see a plant growing there."

    Copyright Betanews, Inc. 2010

    Add to digg Add to Google Add to Slashdot Add to Twitter Add to del.icio.us Add to Facebook Add to Technorati
  • ← février 2010 (134 élém... avril 2010 (124 éléments) →