futureofpac / oecdinfo Goto Github PK

By doing this, users can open a link from the list of item without open the detail page

Sharing via Facebook works fine but email and twitter doesn't open new window and doesn't work. Facebook or twitter might change the way of sharing but email needs to be fixed

using pac email account services are newly created
based on those, new environments(dev, test, and production) are created respectively

There were some strange behavior for the theme and it needed to be recompiled in order to fix it
icon for the menu has been replaced with the new one
color for the menu has been enhanced

home page: /#home
menu open: /#menu
theme open: /#theme
detail open: /#detail

each those status (menu, theme .. ) of the app have their own routing url so history will be managed by browser therefore desktop and android devices can support the backward key.

To have multiple environments
Services (Heroku, MongoHQ, Twitter, Flickr) are created using pacps email

so the configurations such as database connection and service api will be applied to the app based on the environments.

The order of Items of the list is not consistent
as the app is using group feature using the date of the item and there is not more information for the ordering than date for each item.

For the normal error it will be logged in the database so that it is easy to query and for the db errors, it will be saved in a file so that we can track

In case there is no data due to an error in the backend, the app wil be able to handle the situation.

As the sencha touch is designed for the touch based devices, the key control feature will greatly help desktop users as they can navigate and control mainly with arrow, enter and back buttons.

The question was how we can have the path for sencha app after compiling.
We want to keep origin source codes for the development but for the production we definitely want to have the compiled sources without minimizing manual work.

Previously, to deploy to prod after compile, we grabbed the codes and moved to the folder production and add these source codes in the index.html file but to play with test server we have to undo things changed in index.html so it was very cumbersome.

now what only we need to is grab files and moved to the production folder.
Because we set config variables for both test and prod heroku server.
For the test, '/public' folder and for the prod, '/public/production' will be used.

The url for the service will vary based on the environment.
This way of handling configuration for each environment can be improved later on.

Putting things into the place for the db connection using node.js in the Heroku environment. This will be the fundemental infrastructure for the data store in the backend side. For this, MongoJs module and MongoHQ are used

layout and font modification of the detail page were made

in the left hand menu, the Theme section currently spells "Themem" but should be spelled as "Themes" (note the last character).

navigating each media type such as news, article, video and etc has been enhanced by having clone items

initial case: only save button
not initial case: save and cancel button

to do this, theme component needs to be created dynamically