Getting Started:
———————–
Since the start of the coding period last week, I’ve been playing around with Enyo.js based app development, identifying the similarities and dissimilarities between Enyo 1.0 and 2.2.
Protyping Approach to Development:
—————————————————
For starters, I’ve been working on writing a simple Feed Reader (https://github.com/sayak-sarkar/FeedReader) based upon Enyo 1.0 and then porting the app to work on Firefox OS. It is basically an app on its own which fetches posts from existing WordPress sites and displays them. This is a simple prototype model that I’m working on to identify and isolate WebOS based code and dependencies in the current WordPress for WebOS app. Once complete, I should be able to put placeholders for equivalent manifest as well as configuration files for Firefox OS in the current app’s code, which is precisely my target for this week.
Once, this is complete, which I expect to be within the next 3 days, I would be moving on to the code upgradation phase of the project where I would be upgrading the existing enyo 1.0 code to enyo 2.2.
Code Tracking:
———————
I’m yet to start using the SVNSVN Apache Subversion (often abbreviated SVN, after its command name svn) is a software versioning and revision control system. Software developers use Subversion to maintain current and historical versions of files such as source code, web pages, and documentation. Its goal is to be a mostly compatible successor to the widely used Concurrent Versions System (CVS). WordPress core and the wordpress.org released code are all centrally managed through SVN. https://subversion.apache.org/. based TracTrac Trac is the place where contributors create issues for bugs or feature requests much like GitHub.https://core.trac.wordpress.org/. repository as the current code that I’m working upon is a mere prototype that is most likely to be discarded, once I start building upon the primary code base of the WordPress for WebOS app next week onwards. Once the prototyping is complete, I would start by uploading a stripped down version of the current codebase containing of only the necessary configuration and coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. files, upon which the final application would be built.