Sāmoan language support for the Quasar framework

Exciting news for Sāmoan language app development! 

And just in time to celebrate Sāmoa's 60 years of independence!!

The Sāmoan language is now included as a language pack for the Quasar framework as of version 2.7.2 . It means dozens of Vue Components can now support Sāmoan.

To switch it on, follow the instructions in the docs and use the "sm" code.

This is a biggy for me as it's the only Sāmoan language pack I know of for any framework I've worked with. Much appreciation to the Quasar team for the quick turn around.

Here is an example of using the close translation in your own components 

  {{ $q.lang.label.close }}

And some examples of translated components in action:

WYSIWYG Editor (hover over items to see translations)

See the Pen Editor (WYSIWYG): Kitchen sink in Sāmoan - Quasar v2.7.3 by Ainsof So'o (@ainsofs) on CodePen.

Date Picker (try clicking the month names)

See the Pen QDate: Basic in Sāmoan - Quasar v2.7.3 by Ainsof So'o (@ainsofs) on CodePen.

Table (note the text on the bottom right of the table)

See the Pen Table: Basic in Sāmoan - Quasar v2.7.3 by Ainsof So'o (@ainsofs) on CodePen.

Pull request

To view the pull request that made it happen click here.

What is Quasar?

Quasar (pronounced /ˈkweɪ.zɑɹ/) is an MIT licensed open-source Vue.js based framework, which allows you as a web developer to quickly create responsive++ websites/apps in many flavours:

  • SPAs (Single Page App)
  • SSR (Server-side Rendered App) (+ optional PWA client takeover)
  • PWAs (Progressive Web App)
  • BEX (Browser Extension)
  • Mobile Apps (Android, iOS, …) through Cordova or Capacitor
  • Multi-platform Desktop Apps (using Electron)

Comments

Post a Comment

Popular posts from this blog

Insights for Software Development Workflows from the Pacific Islands

Image
Talofa! I came across an interesting video on how enterprise software development workflows might work. I found that I was using a hybrid of techniques mentioned which aligned well given that it was showing how BIG companies with teams of developers would develop software. We have a few software developers at SPREP but mostly work on our own projects . I thought I would reflect on my workflow as it is something that I've built up over time from research and collaboration with other developers. Tests, Continuous Integration/ Continuous Deployment (CI/CD) My workflow involves setting up tests from the get go and putting them into Gitlab CI pipelines . This gives me confidence that the system builds and I'm not breaking stuff I already fixed . Here is an example of how I would set up a Drupal project with style tests and a Github Action for running them. Feature building with Git branches I build features using git branches . If I have an urgent requirement or fix , I can switch ...
Read more

Government of Tonga’s first mobile app nears completion

Image
  Caption: Workshop participants Last week I was in Tonga to facilitate a training workshop for the Tonga Meteorological Services (TMS) and its partners. The workshop is part of finalising the Tonga Joint Early Warning and Response mobile app (app name to be finalised). The TMS lead initiative will help address challenges in communications on the ground and sharing of data with partners in times of natural disasters. Furthermore, the app provides real-time weather warnings using push notifications to mobile devices. Unlike traditional “weather” apps, TMS envisioned a “two-way” app that not only provides weather forecasts but enables the public to report weather and disaster related events to them. It will become the first mobile app for the Government of Tonga and will be available in Tongan and English languages on Android and iOS devices. SPREP provides ICT expertise to assist TMS Caption: Mr. Ainsof So'o reviewing the mobile app One of the Secretariat of the Pacific Regional Env...
Read more

Bot Busters: Defending Your Site Against Bots

Image
TL;DR: A climate change portal faced performance issues due to excessive bot crawling. After trying various solutions, including updating core and modules, scaling up the server, and exploring different security modules, the problem was solved using Drupal's built-in Ban module to block problematic IP addresses. The Autoban module was then implemented to automate the process, effectively improving the site's performance and resilience against bots.      🌐 Introduction In today's digital landscape, websites face numerous challenges, and one of the most persistent is the threat of bots. These automated programs can wreak havoc on your site's performance, especially when they crawl your pages excessively. Recently, we encountered this issue with one of our country climate change portals built on Drupal 7. Here's how we tackled the problem and restored the site's performance. 🔍 The Investigation Begins When we noticed performance issues on our climate change p...
Read more