Azoft Case Studies - Page 9 of 9 - Blog about Technology, Events & People
Azoft Case Studies

Save Time Using Drupal Panels Module

By Alex Ilchuk on January 7, 2013
Sometimes, Drupal theming system is unable to cope with a large number of blocks and regions in a project. In this article I'd like to show you how to use Panels — a visual page editor that lets you quickly create complicated layouts with ease. drupal blocks panels 01 Save Time Using Drupal Panels Module

Data Processing Optimization in Android Application

By Alex Vasilkov on December 24, 2012
Developers don't always pay enough attention to structuring the logic of data processing in a mobile application. As a result, developers often face challenges when introducing changes and releasing application updates. In this article I'll talk about my own approach to structuring data processing, including data retrieval, storing and caching. This topic is relevant to the development of all mobile applications, particularly those whose primary purpose is to receive and present data, as well as sending data to the server. Essentially, this applies to any application that provides users with any type of frequently updated information, whether its news, weather, travel info, online magazines, etc.

How To Print Labels Through PHP Application

By Konstantin Medvedev on December 12, 2012
In this article, we'd like to share our experience integrating a PHP web application with BarTender Print Server. This information could be useful to anyone planning to automate the process of printing labels, bar codes or RFID tags and to integrate the necessary equipment with existing enterprise systems. The article concerns PHP applications, since they are frequently used as commercial business systems. But keep in mind that the method we describe here can also be employed for applications based on other platforms.

4 Steps for Avoiding Data Corruption in SQLite 3.5.9 on Android 2.1

By Alexander Ak on October 17, 2012
When it comes to Android application development, it’s often desirable to ensure the app is compatible with older versions of the Android OS. A customer has recently asked us to make an application while keeping backward compatibility down to SDK version 2.1 (API level 7). While working on that project, we encountered a problem: the built-in SQLite version 3.5.9 had a known bug that appeared under certain conditions. Incidentally, SQLite caused the application to crash due to a "database disk image is malformed" error and the entire database was rendered unusable. We didn't find a solution for this problem on the web, so we created the following workaround after some experimenting.

So, what should you do if you’ve stumbled upon this bug? Wrap database access into a content provider. The rest of this post gives step-by-step instructions on how to implement it in your own project.

4 Steps for Avoiding Data Corruption in SQLite 3.5.9 on Android 2.1

Mystery Bug in MKReverseGeocoder: Investigation by iOS Developers

By July Nikolay on September 20, 2012
When developing software applications, programmers often rely on ready solutions to handle certain tasks within the project. After all, applying a ready solution instead of developing one from scratch is much faster, cheaper and just makes sense, right? Well, not always. Today I’ll tell you about our hunt to find a hidden bug in Geocoder (iOS 4.3 SDK) that occurred while working with geolocation services. Let this be an example of how sometimes it's best to apply our own custom-built solution.