The flow:

• At first run, the app calls all API endpoints requred to download data from the website:
  • Use “Get All” endpoints for each entity, or use paged calls for large datasets
  • Get and parse JSON, save into local DB
  • Use 1 DB table per entity with all its field
• Store [last update date & time] to local app settings
• On App launch and on app resume, check if last update time is older than X days.
• If it is, call API endpoints “Get All” with ?after=[last update date & time]
• Get and parse JSON, update local DB with new/changed records

We need to store a “last update date” for each entity in UserDefailts. So, for example to save and get the last update date for the Post entity I can do:

UserDefaults.standard.set(Date(), forKey: “PostsLastUpdate”)
UserDefaults.standard.object(forKey: “PostsLastUpdate”) as? Date

In an initial version, I checked all records for updates ater a given interval using the get all entities and going through the full DB each time. This works but is not the best solution. With a complete implementation on server side, you only request updates to the database with a parameter that will get you all posts modified “after” a certain date. Out of the box, this won’t return posts that reside in the trash, so I build a secondary endpoint to return deleted posts. Therefore you need to invoke 2 endpoints:
<ul><li>one for modified and new records,</li>
<li>and one for deleted records.</li>

The implementation can probably be optimized to return both in one call. In order to check for updates, the workflow looks like this.

First, you set a negative number: we subtract this number of days to check if the cache is current or should be updated. This can also be a constant in your global constants file or part of a more generic cache controller class.

let intervalInDays: Int = -1

Then we check if last update was within the days interval. If so, we can kill the process and return void.

if let lastUpdate = UserDefaults.standard.object(forKey: “ItinerariesLastUpdate”) as? Date {
// Updated within the last X days? Skip this update
if(lastUpdate.isGreaterThanDate(Date().addDays(intervalInDays))) {
// Cache is up-to-date, nothing to do.
return
}
}

If the process continues, we call “Get All” the endpoint with an “after” parameter to only get updated items, and parse JSON to store in the local database. Then we explicitely save the DB (context).

Then, we call the endpoint to “get Deleted” posts (using the same “after” parameter) to only get deleted items. This will return an array of post IDs, so you need to make a query to remove those records from your local DB. Save the DB again.

Indeed, it looks like we need to explicitly save the database in swift when we do this kind of stuff, and it’s also good to add a call to write the DB to disk in “will app terminate” within app delegate.

At the end of the process, if no errors were returned and the DB saved correctly to disk, you have to update the Last Update Date like this:

UserDefaults.standard.set(Date(), forKey: “PostsLastUpdate”)

The post Swift iOS Mobile App Caching Controller Update Logic, Cache in Swift first appeared on Surgeworks.

Since the dataset was limited and updated once or twice a week, we decided to create a caching workflow that would allow the app to query the local database for searches and only tap into the server to update the local contents.

This requires some of the business logic (i.e. to search) to be built on the client app rather then the server, which in turn means that if you are building a native app you will need a custom cahce controller and a data manager that knows your business logic to be implemented twice (Anroid and iOS). In our experience though, most of that code is easily portable between Swift and Java, as long as it’s kept in its own class and well commented.

Let’s take a look at the Cache Controller Workflow:

• At first run, the app calls all API endpoints requred to download data from the website:
  • Use “Get All” endpoints for each entity, or use paged calls for large datasets
  • Get and parse JSON, save into local DB
  • Use 1 DB table per entity with all its field
• Store [last update date & time] to local app settings
• On App launch and on app resume, check if last update time is older than X days.
• If it is, call API endpoints “Get All” with ?after=[last update date & time]
• Get and parse JSON, update local DB with new/changed records

Note: the taxonomies (secondary entities such as post tags) only provide a unique string as ID in the standard responses. They lack the nice name and the unique integer ID. So you’ll need an endpoint to retrieve the taxonomies table too.

At this point you can use the local database to get data and search for data, by using a database manager controller that will take care of building your queries and get all necessary related data for you. You can build dictionaries or arrays for your lists to be fed to the view controllers.

The post WordPress as Mobile App Back-end: Caching System Architecture first appeared on Surgeworks.

So you are probably scratching your head to move your hosts from MAMP to the MAMP PRO app. MAMP PRO documentation offers a hint on this page. However, there is one tiny detail missing that makes the difference.

Once you copied your database (copied, not moved) from /Applications/MAMP/db/mysql56 to /Library/Application Support/appsolute/MAMP PRO/db/mysql56 you need to open MAMP PRO, start your servers and select Tools > Upgrade Databases.

Also please note, that the path to the new database files is not referring to the Library in your home directory. It’s the main Library that you can find at the root level of your hard disk.

The post Transition Databases from MAMP to MAMP PRO 4 (Mac) first appeared on Surgeworks.

One way around this is to use a 3 letters code for time zones, however those are hard to remember and deal with when entering the data, so we decided to use the Time Zone description instead (i.e. Europe/Rome or America/Los_Angeles).

In order to be sure we could get a common set of timezones across PHP, iOS and Android, we dumped all supported time zones on each framework and intersected the resulting arrays. Here is the result of safe time zone descriptions you can use in iOS 11, Android 5 and above and PHP 5.4 and later.

Africa/Abidjan
Africa/Accra
Africa/Addis_Ababa
Africa/Algiers
Africa/Asmara
Africa/Bamako
Africa/Bangui
Africa/Banjul
Africa/Bissau
Africa/Blantyre
Africa/Brazzaville
Africa/Bujumbura
Africa/Cairo
Africa/Casablanca
Africa/Ceuta
Africa/Conakry
Africa/Dakar
Africa/Dar_es_Salaam
Africa/Djibouti
Africa/Douala
Africa/El_Aaiun
Africa/Freetown
Africa/Gaborone
Africa/Harare
Africa/Johannesburg
Africa/Juba
Africa/Kampala
Africa/Khartoum
Africa/Kigali
Africa/Kinshasa
Africa/Lagos
Africa/Libreville
Africa/Lome
Africa/Luanda
Africa/Lubumbashi
Africa/Lusaka
Africa/Malabo
Africa/Maputo
Africa/Maseru
Africa/Mbabane
Africa/Mogadishu
Africa/Monrovia
Africa/Nairobi
Africa/Ndjamena
Africa/Niamey
Africa/Nouakchott
Africa/Ouagadougou
Africa/Porto-Novo
Africa/Sao_Tome
Africa/Tripoli
Africa/Tunis
Africa/Windhoek
America/Adak
America/Anchorage
America/Anguilla
America/Antigua
America/Araguaina
America/Argentina/Buenos_Aires
America/Argentina/Catamarca
America/Argentina/Cordoba
America/Argentina/Jujuy
America/Argentina/La_Rioja
America/Argentina/Mendoza
America/Argentina/Rio_Gallegos
America/Argentina/Salta
America/Argentina/San_Juan
America/Argentina/San_Luis
America/Argentina/Tucuman
America/Argentina/Ushuaia
America/Aruba
America/Asuncion
America/Atikokan
America/Bahia
America/Bahia_Banderas
America/Barbados
America/Belem
America/Belize
America/Blanc-Sablon
America/Boa_Vista
America/Bogota
America/Boise
America/Cambridge_Bay
America/Campo_Grande
America/Cancun
America/Caracas
America/Cayenne
America/Cayman
America/Chicago
America/Chihuahua
America/Costa_Rica
America/Creston
America/Cuiaba
America/Curacao
America/Danmarkshavn
America/Dawson
America/Dawson_Creek
America/Denver
America/Detroit
America/Dominica
America/Edmonton
America/Eirunepe
America/El_Salvador
America/Fortaleza
America/Glace_Bay
America/Godthab
America/Goose_Bay
America/Grand_Turk
America/Grenada
America/Guadeloupe
America/Guatemala
America/Guayaquil
America/Guyana
America/Halifax
America/Havana
America/Hermosillo
America/Indiana/Indianapolis
America/Indiana/Knox
America/Indiana/Marengo
America/Indiana/Petersburg
America/Indiana/Tell_City
America/Indiana/Vevay
America/Indiana/Vincennes
America/Indiana/Winamac
America/Inuvik
America/Iqaluit
America/Jamaica
America/Juneau
America/Kentucky/Louisville
America/Kentucky/Monticello
America/Kralendijk
America/La_Paz
America/Lima
America/Los_Angeles
America/Lower_Princes
America/Maceio
America/Managua
America/Manaus
America/Marigot
America/Martinique
America/Matamoros
America/Mazatlan
America/Menominee
America/Merida
America/Metlakatla
America/Mexico_City
America/Miquelon
America/Moncton
America/Monterrey
America/Montevideo
America/Montserrat
America/Nassau
America/New_York
America/Nipigon
America/Nome
America/Noronha
America/North_Dakota/Beulah
America/North_Dakota/Center
America/North_Dakota/New_Salem
America/Ojinaga
America/Panama
America/Pangnirtung
America/Paramaribo
America/Phoenix
America/Port-au-Prince
America/Port_of_Spain
America/Porto_Velho
America/Puerto_Rico
America/Rainy_River
America/Rankin_Inlet
America/Recife
America/Regina
America/Resolute
America/Rio_Branco
America/Santarem
America/Santiago
America/Santo_Domingo
America/Sao_Paulo
America/Scoresbysund
America/Sitka
America/St_Barthelemy
America/St_Johns
America/St_Kitts
America/St_Lucia
America/St_Thomas
America/St_Vincent
America/Swift_Current
America/Tegucigalpa
America/Thule
America/Thunder_Bay
America/Tijuana
America/Toronto
America/Tortola
America/Vancouver
America/Whitehorse
America/Winnipeg
America/Yakutat
America/Yellowknife
Antarctica/Casey
Antarctica/Davis
Antarctica/DumontDUrville
Antarctica/Macquarie
Antarctica/Mawson
Antarctica/McMurdo
Antarctica/Palmer
Antarctica/Rothera
Antarctica/Syowa
Antarctica/Troll
Antarctica/Vostok
Arctic/Longyearbyen
Asia/Aden
Asia/Almaty
Asia/Amman
Asia/Anadyr
Asia/Aqtau
Asia/Aqtobe
Asia/Ashgabat
Asia/Baghdad
Asia/Bahrain
Asia/Baku
Asia/Bangkok
Asia/Beirut
Asia/Bishkek
Asia/Brunei
Asia/Chita
Asia/Choibalsan
Asia/Colombo
Asia/Damascus
Asia/Dhaka
Asia/Dili
Asia/Dubai
Asia/Dushanbe
Asia/Gaza
Asia/Hebron
Asia/Ho_Chi_Minh
Asia/Hong_Kong
Asia/Hovd
Asia/Irkutsk
Asia/Jakarta
Asia/Jayapura
Asia/Jerusalem
Asia/Kabul
Asia/Kamchatka
Asia/Karachi
Asia/Kathmandu
Asia/Khandyga
Asia/Krasnoyarsk
Asia/Kuala_Lumpur
Asia/Kuching
Asia/Kuwait
Asia/Macau
Asia/Magadan
Asia/Makassar
Asia/Manila
Asia/Muscat
Asia/Nicosia
Asia/Novokuznetsk
Asia/Novosibirsk
Asia/Omsk
Asia/Oral
Asia/Phnom_Penh
Asia/Pontianak
Asia/Pyongyang
Asia/Qatar
Asia/Qyzylorda
Asia/Riyadh
Asia/Sakhalin
Asia/Samarkand
Asia/Seoul
Asia/Shanghai
Asia/Singapore
Asia/Srednekolymsk
Asia/Taipei
Asia/Tashkent
Asia/Tbilisi
Asia/Tehran
Asia/Thimphu
Asia/Tokyo
Asia/Ulaanbaatar
Asia/Urumqi
Asia/Ust-Nera
Asia/Vientiane
Asia/Vladivostok
Asia/Yakutsk
Asia/Yekaterinburg
Asia/Yerevan
Atlantic/Azores
Atlantic/Bermuda
Atlantic/Canary
Atlantic/Cape_Verde
Atlantic/Faroe
Atlantic/Madeira
Atlantic/Reykjavik
Atlantic/South_Georgia
Atlantic/St_Helena
Atlantic/Stanley
Australia/Adelaide
Australia/Brisbane
Australia/Broken_Hill
Australia/Currie
Australia/Darwin
Australia/Eucla
Australia/Hobart
Australia/Lindeman
Australia/Lord_Howe
Australia/Melbourne
Australia/Perth
Australia/Sydney
Europe/Amsterdam
Europe/Andorra
Europe/Athens
Europe/Belgrade
Europe/Berlin
Europe/Bratislava
Europe/Brussels
Europe/Bucharest
Europe/Budapest
Europe/Busingen
Europe/Chisinau
Europe/Copenhagen
Europe/Dublin
Europe/Gibraltar
Europe/Guernsey
Europe/Helsinki
Europe/Isle_of_Man
Europe/Istanbul
Europe/Jersey
Europe/Kaliningrad
Europe/Kiev
Europe/Lisbon
Europe/Ljubljana
Europe/London
Europe/Luxembourg
Europe/Madrid
Europe/Malta
Europe/Mariehamn
Europe/Minsk
Europe/Monaco
Europe/Moscow
Europe/Oslo
Europe/Paris
Europe/Podgorica
Europe/Prague
Europe/Riga
Europe/Rome
Europe/Samara
Europe/San_Marino
Europe/Sarajevo
Europe/Simferopol
Europe/Skopje
Europe/Sofia
Europe/Stockholm
Europe/Tallinn
Europe/Tirane
Europe/Uzhgorod
Europe/Vaduz
Europe/Vatican
Europe/Vienna
Europe/Vilnius
Europe/Volgograd
Europe/Warsaw
Europe/Zagreb
Europe/Zaporozhye
Europe/Zurich
Indian/Antananarivo
Indian/Chagos
Indian/Christmas
Indian/Cocos
Indian/Comoro
Indian/Kerguelen
Indian/Mahe
Indian/Maldives
Indian/Mauritius
Indian/Mayotte
Indian/Reunion
Pacific/Apia
Pacific/Auckland
Pacific/Bougainville
Pacific/Chatham
Pacific/Chuuk
Pacific/Easter
Pacific/Efate
Pacific/Enderbury
Pacific/Fakaofo
Pacific/Fiji
Pacific/Funafuti
Pacific/Galapagos
Pacific/Gambier
Pacific/Guadalcanal
Pacific/Guam
Pacific/Honolulu
Pacific/Johnston
Pacific/Kiritimati
Pacific/Kosrae
Pacific/Kwajalein
Pacific/Majuro
Pacific/Marquesas
Pacific/Midway
Pacific/Nauru
Pacific/Niue
Pacific/Norfolk
Pacific/Noumea
Pacific/Pago_Pago
Pacific/Palau
Pacific/Pitcairn
Pacific/Pohnpei
Pacific/Port_Moresby
Pacific/Rarotonga
Pacific/Saipan
Pacific/Tahiti
Pacific/Tarawa
Pacific/Tongatapu
Pacific/Wake
Pacific/Wallis

The following lists compare the missing records in each framework.

PHP

America/Fort_Nelson missing in Android
Asia/Atyrau missing in Android
Asia/Barnaul missing in Android
Asia/Famagusta missing in Android
Asia/Kolkata missing in Swift
Asia/Tomsk missing in Android
Asia/Yangon missing in Android
Europe/Astrakhan missing in Android
Europe/Kirov missing in Android
Europe/Saratov missing in Android
Europe/Ulyanovsk missing in Android
UTC missing in Swift

Swift

America/Fort_Nelson missing in Android
America/Montreal missing in PHP
America/Punta_Arenas missing in PHP
America/Punta_Arenas missing in Android
America/Santa_Isabel missing in PHP
America/Shiprock missing in PHP
Antarctica/South_Pole missing in PHP
Asia/Atyrau missing in Android
Asia/Barnaul missing in Android
Asia/Calcutta missing in PHP
Asia/Chongqing missing in PHP
Asia/Famagusta missing in Android
Asia/Harbin missing in PHP
Asia/Kashgar missing in PHP
Asia/Katmandu missing in PHP
Asia/Rangoon missing in PHP
Asia/Tomsk missing in Android
Asia/Yangon missing in Android
Europe/Astrakhan missing in Android
Europe/Kirov missing in Android
Europe/Saratov missing in Android
Europe/Ulyanovsk missing in Android
GMT missing in PHP
Pacific/Ponape missing in PHP
Pacific/Truk missing in PHP

Android

Africa/Asmera missing in PHP
Africa/Asmera missing in Swift
Africa/Timbuktu missing in PHP
Africa/Timbuktu missing in Swift
America/Argentina/ComodRivadavia missing in PHP
America/Argentina/ComodRivadavia missing in Swift
America/Atka missing in PHP
America/Atka missing in Swift
America/Buenos_Aires missing in PHP
America/Buenos_Aires missing in Swift
America/Catamarca missing in PHP
America/Catamarca missing in Swift
America/Coral_Harbour missing in PHP
America/Coral_Harbour missing in Swift
America/Cordoba missing in PHP
America/Cordoba missing in Swift
America/Ensenada missing in PHP
America/Ensenada missing in Swift
America/Fort_Wayne missing in PHP
America/Fort_Wayne missing in Swift
America/Indianapolis missing in PHP
America/Indianapolis missing in Swift
America/Jujuy missing in PHP
America/Jujuy missing in Swift
America/Knox_IN missing in PHP
America/Knox_IN missing in Swift
America/Louisville missing in PHP
America/Louisville missing in Swift
America/Mendoza missing in PHP
America/Mendoza missing in Swift
America/Montreal missing in PHP
America/Porto_Acre missing in PHP
America/Porto_Acre missing in Swift
America/Rosario missing in PHP
America/Rosario missing in Swift
America/Santa_Isabel missing in PHP
America/Shiprock missing in PHP
America/Virgin missing in PHP
America/Virgin missing in Swift
Antarctica/South_Pole missing in PHP
Asia/Ashkhabad missing in PHP
Asia/Ashkhabad missing in Swift
Asia/Calcutta missing in PHP
Asia/Chongqing missing in PHP
Asia/Chungking missing in PHP
Asia/Chungking missing in Swift
Asia/Dacca missing in PHP
Asia/Dacca missing in Swift
Asia/Hanoi missing in PHP
Asia/Hanoi missing in Swift
Asia/Harbin missing in PHP
Asia/Istanbul missing in PHP
Asia/Istanbul missing in Swift
Asia/Kashgar missing in PHP
Asia/Katmandu missing in PHP
Asia/Kolkata missing in Swift
Asia/Macao missing in PHP
Asia/Macao missing in Swift
Asia/Rangoon missing in PHP
Asia/Saigon missing in PHP
Asia/Saigon missing in Swift
Asia/Tel_Aviv missing in PHP
Asia/Tel_Aviv missing in Swift
Asia/Thimbu missing in PHP
Asia/Thimbu missing in Swift
Asia/Ujung_Pandang missing in PHP
Asia/Ujung_Pandang missing in Swift
Asia/Ulan_Bator missing in PHP
Asia/Ulan_Bator missing in Swift
Atlantic/Faeroe missing in PHP
Atlantic/Faeroe missing in Swift
Atlantic/Jan_Mayen missing in PHP
Atlantic/Jan_Mayen missing in Swift
Australia/ACT missing in PHP
Australia/ACT missing in Swift
Australia/Canberra missing in PHP
Australia/Canberra missing in Swift
Australia/LHI missing in PHP
Australia/LHI missing in Swift
Australia/NSW missing in PHP
Australia/NSW missing in Swift
Australia/North missing in PHP
Australia/North missing in Swift
Australia/Queensland missing in PHP
Australia/Queensland missing in Swift
Australia/South missing in PHP
Australia/South missing in Swift
Australia/Tasmania missing in PHP
Australia/Tasmania missing in Swift
Australia/Victoria missing in PHP
Australia/Victoria missing in Swift
Australia/West missing in PHP
Australia/West missing in Swift
Australia/Yancowinna missing in PHP
Australia/Yancowinna missing in Swift
Brazil/Acre missing in PHP
Brazil/Acre missing in Swift
Brazil/DeNoronha missing in PHP
Brazil/DeNoronha missing in Swift
Brazil/East missing in PHP
Brazil/East missing in Swift
Brazil/West missing in PHP
Brazil/West missing in Swift
CET missing in PHP
CET missing in Swift
CST6CDT missing in PHP
CST6CDT missing in Swift
Canada/Atlantic missing in PHP
Canada/Atlantic missing in Swift
Canada/Central missing in PHP
Canada/Central missing in Swift
Canada/East-Saskatchewan missing in PHP
Canada/East-Saskatchewan missing in Swift
Canada/Eastern missing in PHP
Canada/Eastern missing in Swift
Canada/Mountain missing in PHP
Canada/Mountain missing in Swift
Canada/Newfoundland missing in PHP
Canada/Newfoundland missing in Swift
Canada/Pacific missing in PHP
Canada/Pacific missing in Swift
Canada/Saskatchewan missing in PHP
Canada/Saskatchewan missing in Swift
Canada/Yukon missing in PHP
Canada/Yukon missing in Swift
Chile/Continental missing in PHP
Chile/Continental missing in Swift
Chile/EasterIsland missing in PHP
Chile/EasterIsland missing in Swift
Cuba missing in PHP
Cuba missing in Swift
EET missing in PHP
EET missing in Swift
EST missing in PHP
EST missing in Swift
EST5EDT missing in PHP
EST5EDT missing in Swift
Egypt missing in PHP
Egypt missing in Swift
Eire missing in PHP
Eire missing in Swift
Etc/GMT missing in PHP
Etc/GMT missing in Swift
Etc/GMT+0 missing in PHP
Etc/GMT+0 missing in Swift
Etc/GMT+1 missing in PHP
Etc/GMT+1 missing in Swift
Etc/GMT+10 missing in PHP
Etc/GMT+10 missing in Swift
Etc/GMT+11 missing in PHP
Etc/GMT+11 missing in Swift
Etc/GMT+12 missing in PHP
Etc/GMT+12 missing in Swift
Etc/GMT+2 missing in PHP
Etc/GMT+2 missing in Swift
Etc/GMT+3 missing in PHP
Etc/GMT+3 missing in Swift
Etc/GMT+4 missing in PHP
Etc/GMT+4 missing in Swift
Etc/GMT+5 missing in PHP
Etc/GMT+5 missing in Swift
Etc/GMT+6 missing in PHP
Etc/GMT+6 missing in Swift
Etc/GMT+7 missing in PHP
Etc/GMT+7 missing in Swift
Etc/GMT+8 missing in PHP
Etc/GMT+8 missing in Swift
Etc/GMT+9 missing in PHP
Etc/GMT+9 missing in Swift
Etc/GMT-0 missing in PHP
Etc/GMT-0 missing in Swift
Etc/GMT-1 missing in PHP
Etc/GMT-1 missing in Swift
Etc/GMT-10 missing in PHP
Etc/GMT-10 missing in Swift
Etc/GMT-11 missing in PHP
Etc/GMT-11 missing in Swift
Etc/GMT-12 missing in PHP
Etc/GMT-12 missing in Swift
Etc/GMT-13 missing in PHP
Etc/GMT-13 missing in Swift
Etc/GMT-14 missing in PHP
Etc/GMT-14 missing in Swift
Etc/GMT-2 missing in PHP
Etc/GMT-2 missing in Swift
Etc/GMT-3 missing in PHP
Etc/GMT-3 missing in Swift
Etc/GMT-4 missing in PHP
Etc/GMT-4 missing in Swift
Etc/GMT-5 missing in PHP
Etc/GMT-5 missing in Swift
Etc/GMT-6 missing in PHP
Etc/GMT-6 missing in Swift
Etc/GMT-7 missing in PHP
Etc/GMT-7 missing in Swift
Etc/GMT-8 missing in PHP
Etc/GMT-8 missing in Swift
Etc/GMT-9 missing in PHP
Etc/GMT-9 missing in Swift
Etc/GMT0 missing in PHP
Etc/GMT0 missing in Swift
Etc/Greenwich missing in PHP
Etc/Greenwich missing in Swift
Etc/UCT missing in PHP
Etc/UCT missing in Swift
Etc/UTC missing in PHP
Etc/UTC missing in Swift
Etc/Universal missing in PHP
Etc/Universal missing in Swift
Etc/Zulu missing in PHP
Etc/Zulu missing in Swift
Europe/Belfast missing in PHP
Europe/Belfast missing in Swift
Europe/Nicosia missing in PHP
Europe/Nicosia missing in Swift
Europe/Tiraspol missing in PHP
Europe/Tiraspol missing in Swift
GB missing in PHP
GB missing in Swift
GB-Eire missing in PHP
GB-Eire missing in Swift
GMT missing in PHP
GMT+0 missing in PHP
GMT+0 missing in Swift
GMT-0 missing in PHP
GMT-0 missing in Swift
GMT0 missing in PHP
GMT0 missing in Swift
Greenwich missing in PHP
Greenwich missing in Swift
HST missing in PHP
HST missing in Swift
Hongkong missing in PHP
Hongkong missing in Swift
Iceland missing in PHP
Iceland missing in Swift
Iran missing in PHP
Iran missing in Swift
Israel missing in PHP
Israel missing in Swift
Jamaica missing in PHP
Jamaica missing in Swift
Japan missing in PHP
Japan missing in Swift
Kwajalein missing in PHP
Kwajalein missing in Swift
Libya missing in PHP
Libya missing in Swift
MET missing in PHP
MET missing in Swift
MST missing in PHP
MST missing in Swift
MST7MDT missing in PHP
MST7MDT missing in Swift
Mexico/BajaNorte missing in PHP
Mexico/BajaNorte missing in Swift
Mexico/BajaSur missing in PHP
Mexico/BajaSur missing in Swift
Mexico/General missing in PHP
Mexico/General missing in Swift
NZ missing in PHP
NZ missing in Swift
NZ-CHAT missing in PHP
NZ-CHAT missing in Swift
Navajo missing in PHP
Navajo missing in Swift
PRC missing in PHP
PRC missing in Swift
PST8PDT missing in PHP
PST8PDT missing in Swift
Pacific/Ponape missing in PHP
Pacific/Samoa missing in PHP
Pacific/Samoa missing in Swift
Pacific/Truk missing in PHP
Pacific/Yap missing in PHP
Pacific/Yap missing in Swift
Poland missing in PHP
Poland missing in Swift
Portugal missing in PHP
Portugal missing in Swift
ROC missing in PHP
ROC missing in Swift
ROK missing in PHP
ROK missing in Swift
Singapore missing in PHP
Singapore missing in Swift
Turkey missing in PHP
Turkey missing in Swift
UCT missing in PHP
UCT missing in Swift
US/Alaska missing in PHP
US/Alaska missing in Swift
US/Aleutian missing in PHP
US/Aleutian missing in Swift
US/Arizona missing in PHP
US/Arizona missing in Swift
US/Central missing in PHP
US/Central missing in Swift
US/East-Indiana missing in PHP
US/East-Indiana missing in Swift
US/Eastern missing in PHP
US/Eastern missing in Swift
US/Hawaii missing in PHP
US/Hawaii missing in Swift
US/Indiana-Starke missing in PHP
US/Indiana-Starke missing in Swift
US/Michigan missing in PHP
US/Michigan missing in Swift
US/Mountain missing in PHP
US/Mountain missing in Swift
US/Pacific missing in PHP
US/Pacific missing in Swift
US/Samoa missing in PHP
US/Samoa missing in Swift
UTC missing in Swift
Universal missing in PHP
Universal missing in Swift
W-SU missing in PHP
W-SU missing in Swift
WET missing in PHP
WET missing in Swift
Zulu missing in PHP
Zulu missing in Swift

The post Supported Time Zones PHP, Swift, Java (Android) first appeared on Surgeworks.

Let’s review the steps to do it.

First of all, you need to realize that you don’t want to version anything but your custom code. WordPress and the plug-ins you are using are already being versioned by their respective authors. To do this, your workflow needs to start from your local machine.

You need to have a local development environemnt setup to test your features and work swiftly on breaking changes.

Step 1. Setup your git repository on github

You need to create a new repository, and clone the repository on your local machine. I like to do this using GitHub’s desktop app.

Step 2. Setup your repository locally

Now create a directory structure for your repository. Remember we want to leave out all the WordPress core and 3rd parties plug-ins: these are already versioned eslewhere.

My typical WordPress repository consists of the following directories:

• root level → support scripts that reside at the root level of the site (i.e. .htaccess)
• wp-content/plugins/ → site-specific custom developed plugins
• wp-content/themes/ → site-specific custom developed themes

Optional directories include:

• misc/ → other stuff that doesn’t bleong to the above groups
• assets/ → images, css, javascript, etc that do not belong to wordpress but you still need to store on your webserver

Step 3. Setup your local web server

In my local environment, I currently use MAMP as web and PHP server. I create an arbitrary root directory for the server where I unzip a fresh copy of WordPress.

Then, I download a database dump from the live server and import it locally. If the database is very large, there are better ways then doing this with phpMyAdmin. Be sure to Search and Replace your live Domain with Localhost in the WordPress Database.

Setup your wp-config.php to use the database you just populated.

I usually also download a full copy of the wp-content directory from the server, so that I will have locally all the plug-ins, themes and images exactly as they are served from the server.

Once you move these in place, be sure to keep in the wp-content direcrory of your local web root all 3rd party plug-ins and themes.

Setp 4. Move custom code in the repository

The custom plug-ins and themes instead belong to the appropriate directories in your repository. Move them out of the wp-content directory of your local web root and into the wp-content directory you created in the repository.

Step 5. Make the local site use the custom plug-ins and themes from the repository

Now, how do you connect all the stuff in the repository to your local web server root?

You could keep everything mixed together and build a huge ignore file, but I personally prefer to create “links” of the custom plug-ins and themes, so that I keep everything clean and separated.

The fastest way to do this is with the Terminal app. It’s one command for plug-ins, one for themes, and works as follows:

ln -s ~/path/to/your/repository/wp-content/plugins/* ~/path/to/your/local/web-root/wp-content/plugins/

ln -s ~/path/to/your/repository/wp-content/themes/* ~/path/to/your/local/web-root/wp-content/themes/

If, in the future, you will add a custom plug-in or a child theme to your repository, you need to remember to create a new link for it, i.e.:

ln -s ~/path/to/your/repository/wp-content/plugins/new-plug-in-name ~/path/to/your/local/web-root/wp-content/plugins/

The post A Git Setup for WordPress first appeared on Surgeworks.

Are you working locally on the design and development of a WordPress site and are now ready to migrate it to a staging or live server? You’ll need to replace localhost with your domain name in the database.

The bare minimum you need to do to make the site operational on the new host, is to update your wp_options table with the new server value. You can easily do this with phpMyAdmin running a query like this:

UPDATE wp_options SET option_value = replace(option_value, ‘https://domain-to-be-replaced’, ‘http://current-installation-domain’);

Be sure to include the http and https as required in case you are migrating between an SSL enabled server and a non-secure one.

But, what if you need to update all your posts with new references? Good news: there are 3 ways to handle this.

1. The Old Fashioned Way: open your SQL dump with your code editor (i.e. Sublime Text), find and replace all occurrences, save, then import the database. This is the easiest way around. Just be sure to include the full domain names you need to replace, and then also check for http:// and https:// too if you’re migrating between a non-secure and an SSL enabled host.

2. The Nerd Way: open the terminal and use the WordPress Command Line to run a search and replace in the database.

i.e. To turn your production multisite database into a local dev database

$ wp search-replace –url=example.com example.com example.dev ‘wp_*options’ wp_blogs

For non multisite installation, remove wp_blogs. If you do not have the WP CLI installed, you probably don’t want to go all the way to make it work for this operation, so read on because the next solution might be the best route for you.

3. The GUI way: download this script from GitHub, it was built by Interconnect/it to search and replace on the WordPress MySQL database.

The script author recommends to rename the directory to some arbitrary hard-to-guess name for security reasons. Upload the folder in the root of your WordPress install, then open it in your browser (i.e. http://yourdomain.com/12340-your-secret-name/)

In the form that will appear, you will be able to enter the string you’re searching for, and then the replace string. Your MySQL details/login should already be populated. After entering your search and replace terms, scroll down and click “Update Details”, then do the “Dry Run” option first to preview the changes that will be applied to the database. If you are satisfied with the changes, click “Live Run”.

Comprehensive step-by-step instructions are available at the author’s website.

Important: for security reasons be sure to delete this directory from your server after you have finished using it

Source

The post Search and Replace Localhost Domain in WordPress Database after Migration first appeared on Surgeworks.

Also, you want to be able to keep your changes versioned and push them over to a staging and a production environment without having to ever pull changes from the server side.

To do this, your workflow needs to start from your local machine.
You need to have a local development environemnt setup to test your features and work on breaking changes. When you are satisfied with the functionality of your new code, you push the changes to a staging server, which is just a slave copy of your production server.

Here is an overview of what you need to do to setup this workflow. 

Requirements: you will need SSH access to the server and Git installed on it. Most providers offer these services nowadays as part of their hosting plans.

Step 1. Setup your git repository on github

You need to create a new repository, and only store into it your custom plugins and your custom child theme.

Leave out all the WordPress core and 3rd parties plug-ins: these are already versione eslewhere.

Clone the repository on your local machine.
I like to do this using GitHub’s desktop app.

Step 2. Setup a bare repository on your server.

SSH to your server, then create a directory to hold your repository and run:

git init –bare

I like to create one directory to hold the repositories in /home/username/repositories and I create one repo for the production environment and one for the staging environment.

Step 3. Setup your post-receive script.

On the server-side, go to the bare repository you have created in ./hooks/ and create a new post-receive script.

Be sure the script has execution privileges by doing:

chmod +x ./post-receive

My script does this every time it runs:

• a. Destroys any existing checkout copy of the repository
• b. Creates a new directory and does a fresh checkout of the repository
• c. Goes into ./wp-content/themes, list all directories directly within it (not sub-sub-directories) and for each directory it will
• remove the corresponding directory on the web root and copy it over from the freshly checked out copy.
• d. Does the same process for ./wp-content/plugins.

This way, the script will remove any file that was removed from the git repository, while leaving intact all third parties themes and plug-ins installed in your main WordPress directory.

The script only does its magic if you are pushing to master. All other branches are ignored.

You can grab a copy of the script at the end of this post.

I like to do this process using an FTP client like CyberDuck and editing my post-receive script locally with Sublime Text, rather then using one of the Linux shell-based text editors.

Step 4. On your local machine, add a remote for your repository.

I recomment to keep a staging and a production repository that will deploy respecively to the staging environment and the live site.

To add the remote, you need to do:

git remote add {name} {protocol://username@server.address:PORT/path/to/repository}

i.e. git remote add staging ssh://user@server.com:1234/path/to/repository

Now you can deploy your code to the server by doing:

git push {name} master

i.e. git push staging master

Post-Receive Git Hook Script Sample

#!/bin/bash
while read oldrev newrev ref
do
    if [[ $ref =~ .*/master$ ]];
    then
        # Setup your script variables

        # 0 - Staging or 1 - Production (this is for messages only)
        IS_PRODUCTION="0" 

        # Your site domain (this is for messages only)
        DOMAIN="yourdomain.com"

        # Repository Directory (no trailing slash)
        REPOSITORY_DIR="/home/path/repositories/your_git_repository_name"
        
        # Web Root Directory (no trailing slash)
        WEB_ROOT_DIR="/home/path/public_html"

        # No more editing needed below this line

        # A temporary work directory, it gets created and removed
        TEMPORARY_DIR="${REPOSITORY_DIR}_checkout"

        if [ $IS_PRODUCTION == "1" ]; then
            echo "WARNING: DEPLOYING CHANGES TO PRODUCTION SERVER!"
        fi
        echo "${ENVIRONMENT} Environment: deploying master branch to ${DOMAIN}..."

        # Clean up checkout dir
        if [ -d "$TEMPORARY_DIR" ]; then
            # Control will enter here if $TEMPORARY_DIR exists.
            echo "Cleaning up temporary directory..."
            rm -rf "${TEMPORARY_DIR}"
        fi
        
        echo "Creating temporary git checkout..."
        
        # Create temporary directory 
        mkdir ${TEMPORARY_DIR}

        # Checkout a fresh copy of the repo
        git --work-tree="${TEMPORARY_DIR}" --git-dir="${REPOSITORY_DIR}" checkout -f
        
        # Get all sub-directories that exist in repository from themes
        cd "${TEMPORARY_DIR}"/wp-content/themes/
        pwd
        
        for D in `find . -mindepth 1 -maxdepth 1 -type d`
        do
            if [ -d "$D" ]; then
              # Control will enter here if $D exists.
              echo "Removing directory from ${WEB_ROOT_DIR}/wp-content/themes/${D}"
              rm -Rf "${WEB_ROOT_DIR}"/wp-content/themes/"${D}"

              echo "Copying checkout version of ${D} to ${WEB_ROOT_DIR}/wp-content/themes/"
              cp -aRf "${D}" "${WEB_ROOT_DIR}"/wp-content/themes/
            fi
        done

        # Get all sub-directories that exist in repository from plugins
        cd "${TEMPORARY_DIR}"/wp-content/plugins/
        pwd

        for D in `find . -mindepth 1 -maxdepth 1 -type d`
        do
            if [ -d "$D" ]; then
              # Control will enter here if $D exists.
              echo "Removing directory from ${WEB_ROOT_DIR}/wp-content/plugins/${D}"
              rm -Rf "${WEB_ROOT_DIR}"/wp-content/plugins/"${D}"

              echo "Copying checkout version of ${D} to ${WEB_ROOT_DIR}/wp-content/themes/"
              cp -aRf "${D}" "${WEB_ROOT_DIR}"/wp-content/plugins/
            fi
        done

        # Clean up checkout dir
        if [ -d "$TEMPORARY_DIR" ]; then
            # Control will enter here if $TEMPORARY_DIR exists.
            echo "Cleaning up temporary directory..."
            rm -rf "${TEMPORARY_DIR}"
        fi
    else
        echo "Ref $ref successfully received. Doing nothing: only the master branch may be deployed on this server."
    fi
    echo "Done!"
done

The post How to setup WordPress deployment from GitHub Repository to a Web Server first appeared on Surgeworks.

I’ve been there and done that, and it has served me nicely for small websites in the early days, but it gets to hit hard limits when you are using WordPress as a CMS or as a framework for a larger web app, especially if it syncs with mobile apps.

The main issue in this FTP-based workflow is that you risk to introduce bugs on a live server, that is being visited by actual people and on which your users, potentialy paying customers, are actively using and relying on to carry out the activities you offer through your app.

So what happens in this scenario when you need to fix a bug, and what are the risks?

Yeah, you get it, an image is better then 1,000 words. This does not look good, right?

A better development workflow will work like this:

Your workflow needs to start from your local machine.
You need to have a local development environemnt setup to test your features and work on breaking changes.
Nowadays this is a very easy task to acocmplish on both Mac and Windows, thanks to MAMP.

MAMP installs a local server environment in a matter of seconds on your computer. It comes free of charge, and is easily installed. MAMP will not compromise any existing Apache installation already running on your system. You can install Apache, PHP and MySQL without starting a script or having to change any configuration files! Furthermore, if MAMP is no longer needed, just delete the MAMP folder and everything returns to its original state (i.e. MAMP does not modify any of the “normal” system).

So you can work and make breaking changes locally, on a machine that is optimized for development (i.e. showing PHP errors and warnings either on the page or easily in your Console app) — once a beta version is completed, you will just deploy the code changes to the server.

You can either sync changes via FTP or use another deployment tool. I personally like to use GitHub with the sites hosted on WPEngine.

But wait, if your development server is on your local machine, how will the site owner test and approve the new features?

You need an online server for that, but you don’t want to deploy the changes to the live server until these are approved, so you need a “staging environemnt”, which is just a slave copy of your production server.

A staging server is the place where the stakeholders (the customer) will verify the new features and changes and approve them for production.

While my local development server database is usually a bit stale compared to the live site, I personally like to wipe and recreate the staging environment from a live copy of the production server every time I need to test some major new feature, so that the testers work with fresh, recent data, and don’t get confused reporting issues just because they don’t see this or that database record they are used to see every time they log-in.

Once the changes are tested and approved, I deploy the changes on the production server.

Many providers have a staging feature built in their systems. WPEngine makes the process a snap, and the latest CPanel has a “Staging” feature.

The post Why you Should Have a Staging Server for your WordPress Site first appeared on Surgeworks.

If you are using MAMP for local development, you may be a bit frustrated as it won’t report errors on the webpage by default. In order to review errors, you need to open a file named php_error.log

The file, on Mac, is located in Applications > MAMP > logs > php_error.log

When you double click on it, the file will open automatically in the Console app. You can click on “Now” on the toolbar of the app to keep the log scrolling as new messages appear. I also like to click on “Clear” so that I can easily spot new errors and warnings that get generated from the moment I start testing the new features.

If you want errors to also show up on the webpage, you will need to edit php.ini, which is located in Applications > MAMP > bin > php > php[VERSION] > conf > php.ini

To see what version of PHP you currently are using in MAMP, go to MAMP > Preferences and click on PHP. The Standard version is currently 7.0.15. You can also get a full path to your currently active php.ini file by opening your MAMP start page and clicking on phpInfo on the top navigation bar. It will be listed as the “Loaded Configuration File”.

Once you locate php.ini, you can open it with your favorite text editor. I personally like Sublime Text for these quick tasks.

Search for “Error handling and logging” and take a look at the text there. It lists all possible options for the parameter error_reporting.

If you are here to make errors show up on the page in your browser, be sure to change the next parameter: display_errors = On

Here are the three php values involved into this task and how to set them up to report all errors in your browser as you load a PHP page:

error_reporting = E_ALL
display_errors = On
display_startup_errors = On

The post How to show PHP Error and review Error Logs from MAMP on your Mac (or PC) first appeared on Surgeworks.

You could increase the size of maximum uploads in your php.ini file, however if the dump is really big (over 100Mb), the operation can take ages to complete.

It is more covenient to do this using the command line, expecially since it’s just a one liner.
mysql -u {DB_USER_NAME} -p {DB_NAME} < {PATH/TO/MYSQL/DUMP/FILE.SQL}
Keep in mind that the default user for MySQL as set by MAMP is root with a password of root, and that you need the full path to MAMP binaries to run the mysql command on a default installation. The command becomes:
/Applications/MAMP/Library/bin/mysql -u root -p {DB_NAME} < {PATH/TO/MYSQL/DUMP/FILE.SQL}
On Mac OS X you can simply drag and drop your file to the console to get the full path written for you. So you just have to:

• Open the Terminal app;
• Copy and paste this string to it:
  /Applications/MAMP/Library/bin/mysql -u root -p
• Now, before you hit enter, type your MySQL database name followed by “<” and drag your SQL dump file to the Terminal so that the full path to it gets appended to the command.
• Your command is complete! Hit enter and have faith. It will take a while for the dump to get imported.

Once the import is completed, the prompt will return. Please note that no success message is given, so go back to phpMyAdmin to verify if your data is there.

The post How to import a large MySQL database dump into MAMP, Mac OS X first appeared on Surgeworks.

Same goes for the Windows 8 app store. The latest OS from Microsoft still has less then 4% of the overall market share on PCs, according to ExtremeTech

The post Windows Phone, RIM, Windows 8 are still not worth to support first appeared on Surgeworks.

“This bundle is invalid. Apple is not currently accepting applications built with this version of the OS.”

In the SystemVersion.plist, it turns out our build for 10.7.3 is 11D50b (b being beta). Xcode does not allow beta OS to be used to compile and submit to the Mac App Store. This is clearly a bug and will be fixed. However there is a workaround:

Change the SystemVersion.plist in /System/Library/CoreServices with TextMate (it will ask you for a password to save) or with TextEdit (you will need to change the file permissions first).

Locate the line Build Number: 11D50b and remove the last “b”.

Save, restart Xcode (make sure you do this), clean, archive and you are finally able to submit successfully.

Once you’re done, I recommend you quit Xcode and made sure to change everything back to how it was before. If you keep the file open in TextMate you can “undo” your way back to the original file, which states:

Build Number: 11D50b
ProductUserVisibleVersion: 10.7.3
ProductVersion: 10.7.3

I will not trust restarting my mac with a messed up plist like that.
So use at your own risk and happy coding!

Source: Stack Overflow

The post Mac OS X 10.7.3 with Xcode 4.3: This bundle is invalid. Apple is not currently accepting applications built with this version of the OS. first appeared on Surgeworks.

Santa brought us a cool gift this year: a Kindle Fire tablet.

At a first glance we were astonished: “Why?! We’ve been good boys through the whole year. Why are being punished?”. It’s not and iPad, but ok.

Heh, just kidding… I couldn’t lose the opportunity. What can you expect from Apple fanboys?

Ok, seriously. We’ve been using it for a week now and decided write a small review of our first impressions while handling the gadget.

Looking at the tech specs available on CNET website, we noticed that this is a very simple yet good tablet for the everyday use and a good gadget to keep on your bedside table:

• 7 inches screen;
• 1024x600px (169ppi) screen resolution;
• 8GB integrated memory and dual-core processor;
• Wi-fi, but no bluetooth nor 3G;
• Supported audio formats: AAC, WAV, OGG, MP3, MIDI;
• Supported text formats: AZW, PRC (Mobipocket), PDF, DOC, TXT, DOCX;
• Supported video format: MPEG-4;
• Supported image formats: PNG, JPEG, BMP, GIF;
• Recharge time: 4 hours with the included charging cable. However, it charges when you plug in your PC, but the gadget stays in “stand-by” mode and you can’t use it while charnging;
• Battery life (wireless off): 8 hours of continuous reading (this could easily spoil a good night of sleep).

A deeper analysis of the tablet brought us into some good and some not so good conclusions.

So let’s start with the not so good aspects:

• No USB to Micro USB cable included, needed to access the gadget content from your computer. Also, after testing with the cable we found out that the transfer rate is quite slow;
• A bit thick;
• Scrolling smoothness is bad;
• It gets slow when changing screen orientation;
• Amazon store accepts only US credit card for pay. Here, at the Brazilian office we couldn’t buy anything (apps, books, TV shows) because it does not even accept international credit cards;
• Does not recognize the main electronic book formats: .epub and .mobi;
• Internet browsing is a poor experience. Since it’s resolution is 1024x600px and most of the websites are built for 1024x768px resolutions, you either lose a lot of vertical space when in landscape position or it cuts part of the content horizontally when in portrait.

Now the good points:

• Feels very good in hand for its size. One can hold it with only one hand;
• The task of typing something is very pleasant because your thumbs can reach all the virtual keyboard keys without having to take your hands off the tablet body. In addition to it, a large variety of special symbols are available on the special keys keyboard;
• You can copy your MP3 files from your computer, there’s no need to re-buy them from Amazon. If your MP3 carries album data like Album cover, Album Name, etc., it will help to organize your songs in albums. Also, it’s possible to listen to music while you read a book or browse the internet.
• Reading books is quite pleasuring just like on iPad. You can highlight texts and make notes over it. However, since the screen emits light, your eyes may get tired after some hours of reading. I know, this is a problem that comes with iPad too.

Overview:

Kindle Fire is a very good tablet, easy to use and to carry, good to have on your bedside table or your backpack.

Also its price is quite reasonable for what is being offered.

The only thing that made me a bit sad was the difficulty of purchasing apps, books, movies and music.

However I’d recommend it for regular users that don’t need awesome performance and graphic resources and think that having iTunes to manage all their tablet content is too much effort for a small piece of shining plastic.

My only concern is: Amazon, Y U NO PUT USB TO MINI USB CABLE INSIDE THE BOX?!

The post Kindle Fire first impressions first appeared on Surgeworks.

We’ve just arrived from an awesome conference that opened our minds to new ideas and point of views.

Yes, last week we were at Interaction South America (#ixdsa11), a conference with emphasis on Interaction Design, that happened in Belo Horizonte, MG, Brazil.

The event had the presence of some of the most talented designers, engineers and architects of the Americas talking about Design Thinking, Service Design and Interaction Design. Although our company focus on mobile design/development and the event wasn’t specifically about the mobile world, we absorbed a lot of good concepts that we plan to include in our work methodology.

The first day began with a brief introduction about the event and we quickly went to the workshops, where we could have a detailed vision about how Design Thinking and User Experience work and why they are so important on project planning.

The Design Thinking workshop was led by Isabel Fróes, Psychologist and Interactive Telecommunications Program master. After she made a brief presentation of what it means, she gave the class an imaginary project and guided the participants through the phases of the process in order to reach three different results and make an analysis of them.

The User Experience workshop, led by Walter Cybis, PhD in Production Engineering applied to Software Ergonomy, was focused on User Experience Monitoring. He went through the most common processes and techniques of user experience analysis and then taught how to use the most popular online tools to measure the user adaptivity to the interface suggested based on the statistics generated in the tests.

Still on the first day, to finish our quest for relevant knowledge, we attended to Brian Rink’s talk about How to Build Creative Communities. Rink is a designer specialist in organizational transformation in IDEO and made a brilliant talk about how to make good use of interaction design and the importance of the designer on several activities identifying problems and developing creative and efficient solutions for those problems in order to achieve better results.

On the second day of the conference we can highlight two lecturers: Denise Eler and Chloe Gottlieb.

Denise Eler, Innovation and Design Thinking consultant, talked about the importance of investing more money in service improvement and less in merchandising and advertisement when what usually happens is the opposite. She showed several cases in which she worked as a consultant and also talked about the several job opportunities that are available to the designers. It was a very interesting talk focused on Service Design and innovation.

Chloe Gottlieb, Creation Executive Director at RG/A, made a brilliant talk about Data Driven Design and how information is used to motivate people change their lifestyle. She cited examples like Nike+ that tracks people workout activities and how the data generated from these exercises is transformed into useful information for the consumers and how they can share it with their online communities.

Finally, the third day of conference was enlightened with the talks of Bill Scott and Mike Kuniavsky.

Bill Scott, Senior Director of Web Development at PayPal, featured the importance of the responsive design for services that need to be present on many different devices and how the design is influenced by different ways of interaction that are clearly visible between web, mobile and TV.

Mike Kuniavsky, designer and entrepreneur, opened our eyes to an interesting aspect of how we see products and services nowadays. He said we were habituated to buy products that matters to us as products, and now what really matters is the service. For example: people wouldn’t buy a smartphone only by its beauty or quality but mainly for the services that come with it such as internet, twitter, facebook ando so on. Things that go beyond the calling function.

The conference itself was very interesting and we came back home with a lot of new ideas and concepts that we want to put into practice and incorporate in our services.

Oh! Needless to say, our new tee made some buzz within the people who went to the conference. Some asked if we were selling it but we were giving it away to some lucky ones that came to ask.

Cool, huh?

And here are some photos we took while we were there: Interaction South America

Next stop: Campus Party BR @ Sao Paulo =]

The post Interaction South America 2011, we were there! first appeared on Surgeworks.

Introducing Catholicpedia

The Catholicpedia App makes The Catholic Encyclopedia available on iPhone, iPad and iPod Touch through an easy-to-use interface.

From the Divine Office Catholic Ministry, developers of the About.com “2011 Best iPhone, iPod and iPad Catholic Apps,” this beautifully crafted, simple to use Catholicpedia App is designed to present its users with the full body of Catholic teaching: the Catholic Encyclopedia contains not only precise statements of what the Church has defined, but also an impartial record of different views of acknowledged authority on all disputed questions.

Features highlights

Over 11,000 articles have been categorized by letter and related by tags. The App includes:

• a powerful multi-keyword search engine,
• a tags browser to drill down to specific topics and articles,
• sortable favorites,
• sharing via eMail, Facebook,
• AirPrint support,
• read in portrait or landscape,
• change font size and color scheme

The easy of use and these great features make Catholicpedia the most convenient way to access and carry in your pocket the full 15 Volumes of the Original Catholic Encyclopedia (1917).

The Catholic Encyclopedia

The Catholic Encyclopedia, proposes to give its readers full and authoritative information on the entire cycle of Catholic interests, action and doctrine. What the Church teaches and has taught; what she has done and is still doing for the highest welfare of mankind; her methods, past and present; her struggles, her triumphs, and the achievements of her members, not only for her own immediate benefit, but for the broadening and deepening of all true science, literature and art — all come within the scope of the Catholic Encyclopedia.

The Encyclopedia bears the imprimatur of the Most Reverend Archbishop under whose jurisdiction it is published. In constituting the Editors the ecclesiastical censors, he has given them a singular proof of his confidence and of his desire to facilitate the publication of the work which he has promoted most effectively by his influence and kindly co-operation.

The Encyclopedia was designed to serve the Roman Catholic Church, concentrating on information related to the Church and explaining matters from the Catholic point of view. It records the accomplishments of Catholics and others in nearly all intellectual and professional pursuits, including artists, educators, poets and scientists. While more limited in focus than other general encyclopedias, it was far broader in scope than previous efforts at comprehensive Catholic encyclopedias. It offers in-depth portrayals of historical and philosophical ideas, persons and events, from a Catholic perspective, including issues that divide Catholicism from Protestantism and other faith communities.

Citations: The Catholic Encyclopedia Original Preface (1917) and Wikipedia.

About Divine Office

The Divine Office Catholic Ministry, in partnership with Surgeworks, Inc., is the developer of several apps including Divine Office – Liturgy of the Hours, an iPhone, iPod and iPad app for the universal prayer of the Roman Catholic Church. Divine Office was selected as the recipient of The NY Times Company’s About.com Readers’ Choice Award 2011 for “The Best Catholic Website,” “The Best Catholic iPhone App,” “The Best Catholic iPad App” and “The Best Catholic Podcast.” Visit the Divine Office Website at http://divineoffice.org or view our award-winning apps on your favorite App Store:

   

The post Surgeworks launches Catholicpedia, the Original Catholic Encyclopedia for iPhone, iPad and iPod Touch (press release) first appeared on Surgeworks.