The essential news about content management systems and mobile technology. Powered by Perfect Publisher and XT Search for Algolia.
The News Site publishes posts to the following channels: Facebook, Instagram, Twitter, Telegram, Web Push, Tumblr, and Blogger.
We’re going to look at how to throw together a simple navigable app with the ChocolateChip-UI framework. This will require familiarity with HTML. You don’t need to be good with CSS or even know how to write JavaScript. ChocolateChip-UI provides functionality out of the box to provide functionality for Web apps.
ChocolateChip-UI uses a particular combination of simple tags to define the structures that make up a mobile app. These are: nav, article, section, ul, li, div, aside, span, p and h1 through h5.
To follow along, download the framework and grab the folder “chui”. This contains the files that comprise ChocolateChip-UI. We’re going to use three files: chocolatechip-3.0.4.min.js, chui-3.0.4.min.js and chui-ios-3.0.4.min.js.
To make a Web page behave like an app in the browser, we need to first provide some meta tags. Here is the basic skeleton with appropriate meta tags and links to the ChocolateChip-UI resources:
<!doctype html>
<html lang="en">
<head>
<meta name="viewport" content="initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
<meta name="apple-mobile-web-app-capable" content="yes">
<meta name="msapplication-tap-highlight" content="no">
<meta charset="UTF-8">
<title>Document</title>
<link rel="stylesheet" href="chui/chui.ios-3.0.4.min.css">
<script src="chui/chocolatechip-3.0.4.min.js"></script>
<script src="chui/chui-3.0.4.min.js"></script>
</head>
<body>
</body>
</html>
The app will reside inside of the body tag. When you look at the screen of a mobile devices, you notice that most apps use two main parts to present everything on the screen: a nav bar and everything below that. ChocolateChip-UI uses a combination of a nav
tag and an article
tag to create each screen of the app. Since we’re going to make a navigable app, we’ll need to put together a number of screen, each consisting of a nav
and article
.
The first screen will be the current view, and all others with be upcoming. ChocolateChip-UI designates this navigation status using two classes: “current” and “next”.
Every nav
will have at least an h1
, which is the title that appears in the navigation bar. Let’s start building this. We’ll need to create a navigation bar and an article. ChocolateChip-UI forces the article to fill the screen. Every article should have one child – a section
tag. All the content will go in the section
. It will automatically provide inertia scrolling when the user swipes.
Every article
tag must have a unique id. This is used during navigation so that ChocolateChip-UI knows where to go and where to return to. If you find at some time that your app is not going to where you want or not returning properly, check that your articles have the ids they need and that you have all uses of them spelled identically.
Here is the basic app shell.
<!doctype html>
<html lang="en">
<head>
<meta name="viewport" content="initial-scale=1.0, maximum-scale=1.0, user-scalable=no">
<meta name="apple-mobile-web-app-capable" content="yes">
<meta name="msapplication-tap-highlight" content="no">
<meta charset="UTF-8">
<title>Document</title>
<link rel="stylesheet" href="chui/chui.ios-3.0.4.min.css">
<script src="chui/chocolatechip-3.0.4.min.js"></script>
<script src="chui/chui-3.0.4.min.js"></script>
</head>
<body>
<nav class="current">
<h1>Fruits</h1>
</nav>
<article class="current" id="fruits">
<section></section>
</article>
</body>
</html>
You’ll notice that when it loads in the browser, the title appears in a nav bar, but there is nothing below that. ChocolateChip-UI uses unordered lists with the class list
to display tabular data. We can give the list a title by putting an h2
right before the list. To display data in each list item, we use an h3
as the title and an h4
as the subtitle and a paragraph tag as the item detail. If we put the class nav
on a list item, we get the right facing caret that iOS uses to indicate a navigable item.
To make this list able to navigate to other articles, we need to indicate where each list item should go. We do this using an HTML5 data attribute: data-goto
. We give it the id of the article to which it will go. This will result in automatic navigation when the article that it points to exists.
Now we need to add an article with the id for each fruit: apples, oranges, bananas, mangos and avocados. We’ll also want to provide a nav
with an h1
with the title of each fruit. Because these navs and articles are not current in navigation, we need to explicitly give them the class next
. This will put them out of view until the navigation occurs.
This creates a navigable app, except for one problem. After the user selects a fruit and the app navigates to that screen, there is no way to get back. We can provide a way back by adding a back button in each nav bar right before the title.
To complete our simple app we just need to add a list to each of the fruit articles. We can use the same pattern we used on the main article.
To support Android or Windows Phone 8, you just need to switch out the reference in the CSS link: chui/chui.ios-3.0.4.min.css. Change ios
for android
or win
.
Of course, this is just the most basic setup for an app. In real life you would want to get data dynamically through Ajax requests and output it to your app using templates. Sounds like another article.
Read more https://feedproxy.google.com/~r/dailyjs/~3/eD8Xdt8QYvs/chui-tutorial
As promised the latest release of Fabrik 3.1 is out, Fabrik 3.1rc1 is for Joomla 3.1 and 2.5. This is a major update from the last beta release with over 1000 commits from the largest team of contributors we have ever had for a single Fabrik release.
This is also a security release which fixes the same issue fixed in 3.0.9, where data could be visible when using specific views (raw/json) - disregarding the list's access control settings.
Most intro/out labels etc can be translated via Joomla's translation area.
A couple of key improvements that we've put in are:Read more https://feedproxy.google.com/~r/fabrik/~3/ztxYYQSy9uc/83-fabrik-3-1rc1-for-joomla-3-1-out
Read more https://feeds.joomla.org/~r/JoomlaExtensions/~3/Sh8tSn7kGC4/25223
Read more https://feeds.joomla.org/~r/JoomlaExtensions/~3/biQn4ys0zQs/25288
Joomla! 3.2 is set to be released on November 6, the day before the Joomla World Conference
3.2 is going to be one of the most feature-packed releases that Joomla has ever had.
Here is a list of 15 new features worth noting in Joomla 3.2, followed by a description and/or screenshots for each:
End-user Features:
1) Content History
2) JUX Improvements
3) Front-end Administration of Global Configuration Settings
4) TinyMCE Update
Power-user Features:
5) Install from Web
6) Joomla Multilingual-site Automatic Installer
7) Improved Template Manager
8) Post-install Messages
Developer Features:
9) RAD (Rapid Application Development) Layer
10) AJAX Interface
11) Micro-data Semantics Library
12) HTML5 Form Fields and Attributes
Security Features:
13) Two Factor Authentication
14) BCrypt encryption of Passwords
Miscellaneous Feature:
15) MooTools to jQuery Conversion
Content versioning is Joomla's feature for storing, comparing, and reverting content. For example, you can use it to change back to a previous revision of an article if a mistake happens.
For more information on Content History, click here[1] and here[2].
There have been dozens of improvements to the Joomla User eXperience (JUX) to provide a more user-friendly CMS. Two of my favorites are the cleaned up control panel and top menu. I especially love the way the new control panel looks.
To check out the user experience for yourself, download the latest test version[3] and install it as you normally would Joomla, then go exploring.
Joomla now has two new menu item types that allow end-users to change some of the settings from the front-end. The component uses a web-services approach to change the settings.
Joomla is headed toward front-end in-line editing for the future and this is a small step in the right direction, in order to test the waters from a user perspective.
The above screenshot is from the front-end and shows what the front-end administration options would be like from a user perspective.
TinyMCE has been updated to 4.0 and it looks amazing. Just compare the before (above) and after (below) screenshots to decide for yourself.
I love its new design, drop-downs, and easy of use. For more details on the TinyMCE update, click here[4].
While content versioning (see #1) might be the most needed improvement in Joomla 3.2, the Install from Web feature might be the most exciting for most Joomla users. It's basically the Joomla! Extensions Directory (JED) in the backend with one-click installs! Yes, you heard that right, one-click installs. The feature is reminiscent of Apple's AppStore and Google's Google Play.
The Install from Web feature will include free and commercial extensions, with commercial extensions redirecting to the developers' sites for payment, then automatic installation. The process is similar to what you would have encountered when paying for a product via Paypal, then redirecting back to the original site.
For those wanting a multi-lingual site, you'll now be able to set one up automatically during Joomla's initial installation saving you precious setup time.
Note, I'm testing with the latest test version of Joomla 3.2 Beta, so it states "Language pack does not match this Joomla! version. Some strings may be missing." In Joomla 3.2.0, this will have the corresponding data for each language.
Previously, all that could be done in Template Manager was to edit pre-existing CSS files of templates, to edit root template files, and to duplicate templates. Now, you can:
I'm confident that this feature will make many Joomla power-users very happy.
There's now a post-install component that is used to notify admins of important information when Joomla or an extension is installed or updated. There's also an additional message that's displayed in the control panel to notify admins when they first log in or visit the control panel.
Joomla's new RAD layer is a rapid application development framework on top of Joomla with the following key features:
In short, it's a developer's new best friend and makes Joomla developer significantly easier and faster. For documentation on the new RAD layer, click here[5].
10) AJAX Interface:
Joomla 3.2 has also added an interface for AJAX entry points. This will save development time and also provide standardization for 3rd party custom extensions. Developers can click here[6] to find out more about it.
11) Micro-data Semantics Library:
Another Library that has been added for developers is one that implements https://schema.org micro-data semantics and its usage can be found by clicking here[7].
12) HTML5 form Fields and Attributes:
The last, but not least, improvement for developers is the addition new HTML form fields and attributes, which can be demoed by clicking here[8].
13) Two Factor Authentication:
An optional Joomla security feature that has been added to the arsenal is Two Factor Authentication (TFA). TFA produces an extra temporary security code that is then sent privately to the user (e.g. to their smart phone app) and which allows them to login. This prevents unauthorized login attempts.
14) BCrypt Encryption of Passwords:
Joomla now provides an even stronger password encryption method using BCrypt.
Much of the Joomla Core has been converted from MooTools to jQuery, as jQuery has become the default Joomla library in Joomla 3.
If you would like to test Joomla 3.2, you can download it here[9]. Note, please don't use Joomla 3.2 Beta on a live site or a development site, as it is merely available for testing purposes. Joomla 3.2 will be publicly available on November 6th, 2013 at Joomla.org.
There have been many other improvements and new features added to Joomla 3.2, but the above list is my top 15 features worth noting.
I hope you've enjoyed the article and now over to you.
Which new feature are you most exited about?
Read more https://feedproxy.google.com/~r/ostrainingjoomla/~3/Tkj7pvRuikE/
Page 901 of 1312