Author Archives: m10v

Update on Minow Progress

Update on Minow Progress - A Closeup

Minow (Minow Is Not WordPress) Engine can now read data from data-store. It’s not generic enough though – right now hard-coded to Google App Engine, but nevertheless.

Here’s what I’ve done since last push:

  • Model for localized content is ready
  • Basic logic to retrieve content for a given locale (not parent, no fallback) is ready. For example, if the language is “hi_IN” (Hindi-India), it – as of now – can get you the content for “hi” and/or fallback to “en_US” / “en”.
    As of now, the language is a query-parameter… will enhance to parse “accept-languages” header with priority (q=0.3 etc)
  • Nest theme has been updated to use the “real” data
  • Implementation exists to lazy load data from the store – don’t load the posts until they’re really required. A lot of WordPress templates do not have blog on their landing page
  • And of course, a piece of code generate sample data 😉

Read more …

WordPress on Google App Engine

Minow is not Wordpress - Wordpress on Google App Engine

I think this is a dream for almost every blogger… well, at least my and at least hundreds of thousands of others.

Most of the other results that you’ll find on search engines relating to WordPress and Google App Engine are about running WordPress on GAE/J by using Caucho Quercus – a bridge between PHP and Java. However, if running / simulating PHP on Java was that easy, PHP on GAE would not have been most starred issue.

And that made me think… how about creating, may be, yet another blog engine for GAE. And what better than taking clues from WordPress.

So, that gave birth of Minow, acronym for Minow Is Not WordPress. Yes, it’s a recursive acronym – see http://en.wikipedia.org/wiki/Recursive_acronym for what I mean.

Read more …

Mojito Hello World now live on Nodester

Mojito Hello World now live on Nodester

My earlier “Hello World” case studies are now live at http://m10v-helloworldapp.nodester.com/

References:

btw, in case you are wondering how I got the Mojit up and running using “node server.js” than the regular “mojito start“, read my last post at http://www.m10v.com/2012/06/yahoo-mojito-on-standard-node-servercloud/

And here goes what it looks like:

Yahoo! Mojito on standard Node Server/Cloud

Yahoo! Mojito on Node Server - Nodester

Getting started with Yahoo! Mojito is pretty straightforward. The only catch is, you must issue a mojito start command.

The problem that we get into is that most of the public Node.js clouds have no idea about this new command. All they know to do is node server.js

Recently I tried my hands with Nodester (www.nodester.com). Standard mojito code failed since server.js only instantiated an HTTP server but did not listen.

With inputs from Terry on making the server listen, I was able to run Mojito application on Nodester.

The original discussion between Terry and myself is at http://groups.google.com/group/nodester/browse_thread/thread/e35c7eb3b122ff01

The running application is provisioned at http://gvtestapp.nodester.com/@HelloMojit/index

UPDATE: The application is now available at http://gvtestapp.nodester.com/

Yahoo! Mojito: Part 2 – Enhanced Hello World!

Yahoo! Mojito:: Part 2 - Enhanced Hello World:: Results after Submit

This is Part 2 of the “Hello World” article. In this followup article, we enhance our code to:

  1. Render a form on the landing page which asks user to enter his/her name
  2. Process the data on the submitted form
  3. Say “Hello {user}” rather than “Hello World”

What we will learn through all this is:

  1. One of the various possible options to accept data to the server
  2. Process incoming data
  3. Apply business logic and create the data to be rendered

Let’s get started with customizing the view to create a form…


Read more …

Yahoo! Mojito: Part 1 – Hello World!

Yahoo! Mojito:: Part 1 - Hello World:: Artifacts

Yahoo! Mojito is, now, watched officially by 1027 developers (as of writing this article) on Github (see https://github.com/yahoo/mojito/watchers) and is actively contributed by developers across the board (see https://github.com/yahoo/mojito/network). And I’m pretty sure, there will be several others who would have downloaded, installed and tried.

Before getting into this detailed Hell World tutorial, I assume that you’ve already installed Yahoo! Mojito using the instructions given at https://github.com/yahoo/mojito README. I preferred an npm-install to ensure that I get a stable version.

Defining the “Hello World” application:

  1. The first step will be to create an application with defaults, no customization, and get it running.
  2. Next, we’ll make the application run at port 80 and ensure that the content is available at “/” rather than a strange but intuitive default path.
  3. Subsequently, we’ll change the default contents to reflect “Hello World” in the message
  4. And finally, we’ll make the application interactive by creating a simple form that will accept user’s name and say hello to him/her rather than to the whole world 😉

And here’s some vocabulary before we deep dive:

  1. Yahoo! Mojito: MVC framework for JavaScript based application.
  2. Mojito Application: An application based on Mojito framework.
  3. Mojit: A mojito widget – with its own model, view, controller and binder.

We call this application – “HelloWorldApp” and the mojit as “HelloMojit“.


Read more …

WordPress for Google App Engine?

I love WordPress. A big fan. But then I once-upon-a-time used to be a huge fan of PHP, and then I’ve grown up. I know people will kill me for that statement. 😉

But the fact of the matter is PHP still has serious issues. And most recently, I can’t use it to run WordPress at Google App Engine, something that’s amazingly great for the starters who want to setup quick-and-not-so-dirty app.

I thought… would it be good to have WordPress for GAE? I came across Vosao – Open Source CMS for GAE/J. And I loved it immediately. Has a long way to go, and I do not see any active development on the same… surprised, what happened to the team.

StackOverflow has a question – What CMS runs on Google App Engine, but I personally didn’t like any of them.

And then I thought again… how about writing my own CMS with persistence in a Non-Relational Store with plug-in model so that I can run it on any store, be it GAE’s Data Store, MongoDB or Amazon DynamoDB or whatever.

Let me see if I can hold on my thoughts and really get on with it… At the moment, no promises! :-)

Yahoo! Mojito – Web Developers’ Dream

I’ve started to love HasGeek forum more than others… and there are reasons, mainly the audience and quality – of speakers, planning and execution. I was happily surprised to note that the guys used NFC cards, most probably during breaks. Probably because I had to leave after my session in the morning.

My session at MetaRefresh 2012 was on Yahoo! Mojito, which was recently open sourced at Github.

Below are the slides from the presentation…

Yahoo! Mojito – My Talk at HasGeek

I’ve started to love HasGeek forum more than others… and there are reasons, mainly the audience and quality – of speakers, planning and execution. I was happily surprised to note that the guys used NFC cards, most probably during breaks. Probably because I had to leave after my session in the morning.

My session at MetaRefresh 2012 was on Yahoo! Mojito, which was recently open sourced at Github.

Below are the slides from the presentation&#8230

Yahoo! Mojito – The Ultimate MVC Framework for Web Apps

Probably. Well, I feel it at least as of date.

More often than not, the web application developers end up in doing the following:

  1. Create a server side logic of the application with all code in PHP, Java, Python, Ruby, C# and what not languages
  2. Choose amazing server side frameworks like CodeIgniter, Struts / JSF, Django, RoR, ASP.Net MVC and what not amazing (MVC or otherwise) frameworks
  3. Create a client side view of the application using HTML / JavaScript / CSS for web, Java for Android, Objective C for iOS etc
  4. Create a middleware for client-server transaction, typically using JSON / XML as content format and serializers and deserializers on either sides in corresponding language (server / client sides)

The issues that typically arise are:

  1. Ensure that the server and client sides of the middleware are always in sync in terms of their contracts
  2. Ensure that the end-points are correctly defined and both the sides are kept in sync
  3. Ensure that the end-points are correctly registered in web.xml, web.config, routes.rb, appropriate Python / PHP files etc
  4. Ensure that if multiple requests are fired to the server to retrieve data, you manage the responses appropriately (this is relatively easier because of jQuery / YUI structures)

I am pretty confident, there are a lot more problems pertaining to client <=> server interaction and state maintenance but these are some of the important ones. I’d love to hear about more crucial issues…

Wouldn’t it be great if it would be possible to answer "YES" for the following…

  1. Can I just do a MyModel.getData(myCallbackFunction) and don’t worry if the piece of code is called on the server or the client?
  2. Can I just call a business operation doWork and don’t worry if it needs data which may have to be retrieved from the server or the client?
  3. Can I just call an operation doWork and don’t worry if it actually gets called on the client or the server?

Well, that’s where – and for lot more reasons – Yahoo! Mojito framework comes into picture.

It seems I just can’t wait to write about it… one piece at a time. btw, my enhancements to Mojito are available at Github at https://github.com/gvaish/mojito