GSoC – Week 5: That moment when everything starts coming together.

DEVELOPING THE NEW POST UIUI UI is an acronym for User Interface - the layout of the page the user interacts with. Think ‘how are they doing that’ and less about what they are doing.

Picking up work from last week, this week I finally managed to get over the initial inertia that had kept in check the pace of development. To start with I developed the new Compose UI based on the layout of the earlier WordPress for WebOS app, including the base components for the composer, i.e. Preview/Save/Draft/Publish/Settings buttons, headerHeader The header of your site is typically the first thing people will experience. The masthead or header art located across the top of your page is part of the look and feel of your website. It can influence a visitor’s opinion about your content and you/ your organization’s brand. It may also look different on different screen sizes. and footer toolbars, and the layout for a Rich text based WYSIWYGWhat You See Is What You Get What You See Is What You Get. Most commonly used in relation to editors, where changes made in edit mode reflect exactly as they will translate to the published page. editor. Even though the underlying code for the base implementation was surprisingly easy and straightforward, it took me a bit of time to get hold of the whole process.

Long things short, it’s as simple as writing structured object oriented JSONJSON JSON, or JavaScript Object Notation, is a minimal, readable format for structuring data. It is used primarily to transmit data between a server and web application, as an alternative to XML. documents once you get comfortable with everything Enyo has to offer.


Once I was done with the basic rework of the Compose UI, the next thing that struck me was the fact that the earlier app was specifically designed with tablets in mind, meaning the earlier sliding layout was good for devices with higher resolution. However the primary target devices for Firefox OS being smaller smartphones, most have a basic 320x480px resolution. Hence, the earlier design layout, would just not fit in the display. Hence, what was needed was a change in the layout.

For this part I’m planning to use the same layout as is used by the current Android app. This would in turn result in two main advantages:-
1. Solve the layout problem for smaller devices, and
2. Maintain a consistent look and feel for the app across varying underlying architectures.


Currently I’ve moved on from the Compose module to other parts of the app. At the moment I’m working on implementing the home screen consisting of a list of the users posts using demo data, as well as reworking the overall design layout for the app. I’m planning on finishing up the base UI structure for the app with open hooksHooks In WordPress theme and development, hooks are functions that can be applied to an action or a Filter in WordPress. Actions are functions performed when a certain event occurs in WordPress. Filters allow you to modify certain functions. Arguments used to hook both filters and actions look the same. for the various backend functions.Once this is done, I will be moving on to the backend functions for retrieving and displaying actual user data.


As per development schedule I started with the Compose module last week and have moved up to the other base modules this week, which means, that I’m almost back to the schedule as per the initial plan, with only one deviation. I’m primarily concentrating on getting the skeleton for the app ready by the end of this month or start of the next month. Once, the base skeleton is ready, implementing the newer functions should be a pretty simple and straightforward job.