timeline bergungsi untuk mencatat aktifitas pengguna di dalam sistem
{
"meta": {
},
"data" : [
| { | |
| "token":"SMKTOKEN", | |
| "asesor":[ | |
| {"status":"Asesor I","nama":""},{"status":"Asesor II","nama":""} | |
| ], | |
| "data":[ | |
| { | |
| "npsn":"20224331", | |
| "nama":"SMK NEGERI 1", | |
| "jenjang_id":"18", |
##Chrome Packaged Apps
Introduced at Google I/O 2012, Chrome packaged apps are a new way to develop apps that are running 'natively' within Chrome on the desktop as well as on Chrome mobile in the near future. I'm currently in the middle of a project where I develop a Chrome packaged app and in this article I would like to share my experience with the development of packaged apps.
Please note: This article should give you a basic insight of topics that I think are helpful to know for developing packaged apps. Furthermore I will give links to each topic, so you can dive deeper into that specific topic if you want to. It's not the goal of this article to act as a complete introduction to Chrome packaged apps, for a much more detailed overview of packaged apps development, please look at the official packaged app documentation.
Chrome packaged apps are applic
| var Browser = require('zombie'), | |
| url = require('url'), | |
| fs = require('fs'), | |
| $q = require('Q'), | |
| saveDir = __dirname + '/_snapshots'; | |
| var scriptTagRegex = /<script\b[^<]*(?:(?!<\/script>)<[^<]*)*<\/script>/gi; | |
| var stripScriptTags = function(html) { |
| # start/stop/restart atmail | |
| /etc/init.d/atmailserver start | |
| /etc/init.d/atmailserver stop | |
| /etc/init.d/atmailserver restart | |
| # count of messages in queue | |
| /usr/local/atmail/mailserver/bin/exim -bpc | |
| # list of messages in queue | |
| /usr/local/atmail/mailserver/bin/exim -bp |
| // http://jsonresume.org/ | |
| { | |
| bio: { | |
| firstName: string, | |
| lastName: string, | |
| email: { | |
| work: string, // e.g. [email protected] | |
| personal: string // [email protected] | |
| }, | |
| phone: { // Phone numbers are stored as strings so use any format you like |
| { | |
| "data": | |
| [ | |
| { | |
| "id": 435240508806295552, | |
| "tweet": "09:30 Situasi lalu lintas Ciledug Indah arah Graha Raya Bintaro (Regency) pinang padat merayap imbas jalan berlubang", | |
| "screen_name": null, | |
| "time": null, | |
| "parsed": 0, | |
| "created_at": "2014-02-17 02:34:03", |
This gist contains the nginx and tor configurations for the [mike.tig.as][mta] servers, mainly to show:
chris-lea/nginx-devel PPA to allow use of SPDY.ssl_ciphers selection to mitigate BEAST attack, enable
[perfect forward secrecy][pfs] if possible and select the strongest
possible ciphers within those bounds. (Exception is made for several
ciphers at the end of list, for compatibility reasons.)| <!DOCTYPE html> | |
| <html ng-app="app"> | |
| <head> | |
| <meta charset=utf-8 /> | |
| <title>JS Bin</title> | |
| </head> | |
| <body> | |
| <button ng-controller="MyController" ng-click="testing()" data-id="someCustomValue" data-name="Ketika merdeka"> | |
| Press this button | |
| </button> |
| <?php | |
| $data = array( | |
| [0] => A | |
| [1] => B | |
| [2] => C | |
| [3] => D | |
| [4] => E | |
| [5] => F | |
| [6] => G |