via Cross Platform Mobile Testing with the Page Object Model.
Many of our clients take a hybrid approach to app development. By hybrid we mean using technologies such as Phonegap, Cordova, Appcelerator Titanium, and Sencha as part of their technology stack. Hybrid apps can benefit from cross platform mobile testing.
Companies choose the hybrid approach for several reasons. A major factor is the ability to release on multiple platforms at the same time. The decision of whether or not to make a hybrid app comes down to the skill sets of the various team members developing the app. There are also some downsides to going non-native, such as the possibility of limited features, rendering and responsiveness issues, or crashes on certain devices.
Our customers have asked us about the best testing practices for identifying and addressing these challenges. Our response is cross platform mobile testing. Since hybrid apps are developed from a common code base, it makes perfect sense to have functional UI test cases that can be executed on multiple platforms.
La creacion de un proyecto de Sencha ExtJS 6 usando Sencha CMD es bastante simple. Hacemos la generacion de un proyecto de una forma relativamente sencilla como es usar el comando: >> sencha -sd /ruta_a_framework_6.0/ generate app app03 app03 Una vez ejecutado el comando de generacion de proyecto nos genera nuestro proyecto que puede […]
via ExtJS and Sencha Cmd tutorial for beginners.
When I started with ExtJS several years from now, I worked on a project that included the library in standard script src manner.
I can’t recall that in the time Sencha came up with Sencha Cmd so it seemed completely okay to do so. The project worked out, everyone was happy. I later noticed that lots of folks out there still do this, and I wont argue whether this is a good practice or not, but I started to avoid it as soon I’ve learned the better way.
For a long time (as lazy as one developer can be), I refused to use any external or ready made command line tools for front-end development, as they seemed like another step that will just slow down the process and waste my time. So I didn’t use Sencha Cmd. My colleague and co-author on this blog – Goran, started using it and came up with words – Dude this thing does all that work for us.
As soon I learned about Sencha Cmd and benefits of using it, I started hacking it’s possibilities and it delivered complete happiness to my life. It’s really robust tool that makes your work easier and development cycle looked fulfilled for the first time. Before that we used bunch of various handmade scripts for tasks like minification, deployment, etc. And those scripts were so loosely coupled that you had to look everywhere if something goes wrong. Lots of people worked on those, so you had to go after them in order to find out what exactly this thing does. It was boring, time consuming and generally blocking.
All that washed out as soon we migrated from that chaotic point to the enterprise workflow as people at Sencha described it as best practice for their products – Sencha Cmd.
‘Ext JS in Action SE’ will discuss Ext JS 5 Tablet support, and the new features of Sencha Cmd 5.
Jay Garcia has 20 plus years of technology and consulting experience in leading RIA development for companies around the world. He is actively involved in the Sencha community, and the author of ‘Ext JS In Action SE’ and “Sencha Touch In Action.’
Modus Create is a highly motivated, interdisciplinary team that believes in lean development, design strategy, and user experience to develop stunning applications with emerging technology.
via Getting started with Netzke.
Netzke is a set of Ruby gems that helps you build client-server components, represented in the browser with the help of Sencha Ext JS, and on the server are powered by Ruby on Rails. It’s most useful for creating complex data-rich applications that have to provide the UI to a lot of different data – think about banking, logistics, call centers, and other ERP systems.
In this walk-through I’ll show you how little time it takes to set up a simple application with 2 interacting grids that provide the UI to 2 associated (one-to-many) Rails models. As both grids will be powered by the Netzke::Basepack::Gridcomponent, you may be surprised with all the features like sorting, pagination, search, multi-line editing, etc that this app will provide out of the box.
So, let’s get started.