Jeff Griffiths canuckistani

View jp-init.sh
1 2 3 4
#!/bin/bash
_PWD=`pwd`
mkdir -p "$_PWD/$1" && cd "$_PWD/$1" && jetpack init
echo "" > lib/main.js && echo "" > doc/main.md && echo "" > test/test-main.js && echo "" > ./README.md
View getstyles.js
1 2 3 4 5 6 7 8 9 10
const {Cc, Ci} = require('chrome');
 
var Tabs = require("sdk/tabs");
var TabsUtil = require("sdk/tabs/utils");
var Util = require("./util");
var inIDOMUtils = Cc["@mozilla.org/inspector/dom-utils;1"]
.getService(Ci.inIDOMUtils);
 
function getNativeTab(tab) {
var tabId = tab.id;
View erlang.rb
1 2 3 4 5 6 7 8 9 10
require 'formula'
 
class ErlangManuals < Formula
url 'http://erlang.org/download/otp_doc_man_R15B03-1.tar.gz'
sha1 'c8674767cd0c1f98946f6a08c7ae318c3f026988'
end
 
class ErlangHtmls < Formula
url 'http://erlang.org/download/otp_doc_html_R15B03-1.tar.gz'
sha1 '49d761d8554a83be00e18f681b32b94572f9c050'
View tools-menu-hack.js
1 2 3 4 5 6 7 8 9 10
const utils = require('sdk/window/utils');
const recent = utils.getMostRecentBrowserWindow();
 
// Assume NativeWindow is a global
function showToast() {
recent.NativeWindow.toast.show("Showing you a toast", "short");
}
 
var menuID;
View ghost.conf
1 2 3 4 5 6 7 8 9 10
upstream ghost_upstream {
server 127.0.0.1:2368;
keepalive 64;
}
 
# drop www
server {
listen 80;
server_name www.somedomain.org;
rewrite ^/(.*) $scheme://somedomain.org/$1 permanent;
View ghost_upstart.conf
1 2 3 4 5 6 7 8 9 10
#!upstart
2 #
3 # An example upstart script for running a Node.js process as a service
4 # using Forever as the process monitor. For more configuration options
5 # associated with Forever, see: https://github.com/nodejitsu/forever
6 #
7 # You will need to set the environment variables noted below to conform to
8 # your use case, and should change the description.
9 #
10 description "Example upstart script for a Node.js process"
View widget.js
1 2 3 4 5 6 7 8
require('sdk/widget').Widget({
id: 'mine-test',
label: 'Something',
contentURL: 'chrome://global/skin/icons/webapps-16.png',
onClick: function() {
console.log('foo');
}
});
View launch.foo
1 2 3 4 5 6 7 8 9
do shell script "/Applications/FirefoxNightly.app/Contents/MacOS/firefox -P Nightly &> /dev/null &"
 
delay 2
 
tell application "System Events" to keystroke tab using {command down, shift down}
delay 0.5
tell application "System Events" to keystroke "j" using {command down, shift down}
delay 0.5
tell application "System Events" to keystroke "`" using {command down}
View devtools-pm-process.md

What makes most sense to me is the following ( straw-man ):

Planning Phase

  • Products will generate and post for review user stories for a particular feature. The main utility here is that we consider user expectations divorced from the implementation. User stories should not come from PMs only but PMs will manage them and make sure they're in sync with reality.
  • Developers should be able to express (in writing?) how they are going to proceed with implementing a feature, before they start. With the SDK this is a JEP, and we talked about asking Irakli to present at the work week on how JEPs fit in the Jetpack process, what they buy us in exchange for the time spent writing, posting, discussing and revising them.

Implementation

Once we've got the problem statement ( a PRD of user stories ) and an implementation plan that solves the problem, all of the actual work will be tracked in Bugzilla:

View test.md

Guess who's back? No, this isn't the [eighth track][rakim-guess-whos-back] from [hip-hop legend Rakim's first solo album][rakim-18th-letter], it's another episode of New Features in Firefox Developer Tools! Firefox 25 was just uplifted to the [Aurora release channel][aurora]; included were a bunch of developer tools bug fixes and improvements. This is a summary of some of the most exciting new features, you can also take a look at the [complete list of resolved bugzilla tickets][complete-bug-list].

Black box libraries in the Debugger

Something went wrong with that request. Please try again.