25 Jan
The Software-based Input Panel functionality in Windows Embedded CE allows target devices that do not have a keyboard to simulate keyboard input by using an input method (IM). Windows Embedded CE implements a software-based input panel (SIP) architecture that functions through a touch screen. This SIP architecture is an IM that enables an application to accommodate input in multiple forms. If you want to enhance the portability of target devices based on your OS design, you should consider including SIP functionality in your OS design instead of keyboard support.
[see http://msdn.microsoft.com/en-us/library/aa932590.aspx
"Software-based Input Panel"]
An input method editor (IME) is an application that allows computer users to enter complex characters and symbols, such as Japanese Kanji characters, by using a standard keyboard.
[see http://msdn.microsoft.com/en-us/library/ms776145(VS.85).aspx "Input Method Editor"]
Opera supports the SIP architecture and the IME architecture, so Opera works fine with the default Microsoft keyboards. Unfortunately, many new devices have shiny keyboards that look nice, but do not comply to Microsoft’s SIP and/or IME standard. Those keyboards work well on an edit control, but not with other applications that want to use user-input from a keyboard.
When Opera is pre-installed on a mobile phone we know what kind of software keyboard the device has, and we can test and make work-arounds to get the keyboard working properly. It is very difficult to get every software keyboard working properly as we would have to test every possible device to ensure compatibility.
This results in several problems, for example:
We have cleaned up the input method code in this first beta, so right now it does not support many non-standard IMEs. We will try to make Opera work well with as many keyboards as possible, but there are limits for how many workarounds we can make to accomodate every device and software keyboard. But please keep letting us know where you find issues so we can keep improving.
25 Jan
24 Jan
Here at MyOpera we are currently researching on some stress testing
applications. Basically, we want to be able to:
There are many stress testing applications
out there. We are still looking for alternatives, but so far these seems roughly what we need:
There’s also another common tool for database-only Alligator release stress testing, super-smack. Probably we will use this for db queries optimization and benchmarking.
Siege has been the simplest and quickest to set up and use. We already built some custom workload profiles for MyOpera, to test cache contention with production-like load and to warm up our cache/backend servers after application upgrades. It could also be used as a simple functional test tool, for instance to verify that a list of urls are working correctly. But we already have that, and Jmeter is much better for that purpose.
BTW, if there’s anyone with JMeter experience, please speak up! I’d love to hear from you…
22 Jan
22 Jan
For Your Consideration full Rosemary’s Baby hd
20 Jan
19 Jan
19 Jan

18 Jan
17 Jan
Just Business the movie Lost and Delirious ipodStarman release