This question is locked. New answers and comments are not allowed.
Hi,
I was just watching the Icenium Quick Start demo and wanted to ask you two things.
1. Can you elaborate how you have created your android and iphone simulators? I noticed you don't use the word "emulators" and prefer "simulators" instead, I'm guessing that's intentional.
2. I noticed when the author was demoing the app in the "simulators", when he clicked on the textboxes, no on-screen keyboard appeared. Why was that? I think an on-screen keyboard would appear on an actual device. Does this mean the "simulators" aren't fully functional yet?
Thanks.
I was just watching the Icenium Quick Start demo and wanted to ask you two things.
1. Can you elaborate how you have created your android and iphone simulators? I noticed you don't use the word "emulators" and prefer "simulators" instead, I'm guessing that's intentional.
2. I noticed when the author was demoing the app in the "simulators", when he clicked on the textboxes, no on-screen keyboard appeared. Why was that? I think an on-screen keyboard would appear on an actual device. Does this mean the "simulators" aren't fully functional yet?
Thanks.
4 Answers, 1 is accepted
0
Hello Dariaus,
Excellent questions. Indeed the name simulator is intentional and it was chosen because it mimics the behavior of an application on a device and doesn't guarantee the same look & feel and experience when you deploy the app on the device. For more information about the differences between simulator and emulator visit this discussion.
The presence of keyboard in the simulator is one of features we consider to be inherent to emulators. For the sake of testing in simulator, the machine keyboard is far more convenient.
Regards,
Zdravko
Telerik
You've missed the Icenium Visual Studio Integration keynote? It has been recorded and posted here.
Looking for tips & tricks directly from the Icenium team? Check out our blog!
Share feedback and vote for features on our Feedback Portal.
Excellent questions. Indeed the name simulator is intentional and it was chosen because it mimics the behavior of an application on a device and doesn't guarantee the same look & feel and experience when you deploy the app on the device. For more information about the differences between simulator and emulator visit this discussion.
The presence of keyboard in the simulator is one of features we consider to be inherent to emulators. For the sake of testing in simulator, the machine keyboard is far more convenient.
Regards,
Zdravko
Telerik
You've missed the Icenium Visual Studio Integration keynote? It has been recorded and posted here.
Looking for tips & tricks directly from the Icenium team? Check out our blog!
Share feedback and vote for features on our Feedback Portal.
0
Dariaus
Top achievements
Rank 1
answered on 10 Dec 2013, 02:29 PM
Thanks for the reply
0
Don
Top achievements
Rank 1
answered on 24 May 2014, 03:43 AM
"The presence of keyboard in the simulator is one of features we consider to be inherent to emulators. For the sake of testing in simulator, the machine keyboard is far more convenient."
Just wanted to chime in here regarding the choice not to show the soft keyboard in the simulator. I soft keyboard that behaves correctly on each device would be tremendously helpful. I have spent the past few days working on soft-keyboard / layout issues in iOS. If you search for "cordova iOS keyboard issues" you'll find that there are many. Before this, I also spent a fair amount of time working with Android keyboard issues (e.g. the soft keyboard doesn't show in Android when an text input has focus). Not being able to test these sort of things in the simulator is a big downside, especially if you do not have access to every device/OS version combination.
Just wanted to chime in here regarding the choice not to show the soft keyboard in the simulator. I soft keyboard that behaves correctly on each device would be tremendously helpful. I have spent the past few days working on soft-keyboard / layout issues in iOS. If you search for "cordova iOS keyboard issues" you'll find that there are many. Before this, I also spent a fair amount of time working with Android keyboard issues (e.g. the soft keyboard doesn't show in Android when an text input has focus). Not being able to test these sort of things in the simulator is a big downside, especially if you do not have access to every device/OS version combination.
0
Hi Don,
Thank you for the valuable feedback. I also think the idea of having soft keyboard in the simulator can help a lot.
Please, visit our Ideas and Feedback portal and add this as an Idea or Feature Request there. This will allow other Platform clients to prioritize it accordingly among the other items.
Thank you in advance.
Regards,
Kaloyan
Telerik
Thank you for the valuable feedback. I also think the idea of having soft keyboard in the simulator can help a lot.
Please, visit our Ideas and Feedback portal and add this as an Idea or Feature Request there. This will allow other Platform clients to prioritize it accordingly among the other items.
Thank you in advance.
Regards,
Kaloyan
Telerik
Share what you think about AppBuilder and Telerik Platform with us in our feedback portal, so we can become even better!
