Firefox/Projects/TabCandy/Work: Difference between revisions

no edit summary
No edit summary
Line 3: Line 3:
= Who =
= Who =


* [http://www.azarask.in/blog/ Aza Raskin], IRC: aza
* [http://www.azarask.in/blog/ Aza Raskin], [http://twitter.com/azaaza/ @azaaza], IRC: aza
* [http://iangilman.com/ Ian Gilman], IRC: iangilman
* [http://iangilman.com/ Ian Gilman], [http://twitter.com/iangilman/ @iangilman], IRC: iangilman
* [http://mitcho.com/ Michael Yoshitaka Erlewine], IRC: mitcho
* [http://mitcho.com/ Michael Yoshitaka Erlewine], [http://twitter.com/themitcho/ @themitcho], IRC: mitcho
* [http://raysquare.com/ Raymond Lee], IRC: raymondlee
* [http://raysquare.com/ Raymond Lee], [http://twitter.com/raymondlee/ @raymondlee], IRC: raymondlee
* [http://seanedunn.com/ Sean Dunn], [http://twitter.com/somenotes/ @somenotes], IRC: seandunn
* [http://kevinhanes.net/ Kevin Hanes], [http://twitter.com/mr_yuk/ @mr_yuk]


= Important Pages =
= Important Pages =
Line 29: Line 31:


* [[Firefox/Projects/TabCandy/TabsAndGroups|Tabs & Groups]]
* [[Firefox/Projects/TabCandy/TabsAndGroups|Tabs & Groups]]
= Getting Started =
* Please "watch" the TabCandy component in Firefox in bugzilla by adding tabcandy@firefox.bugs at the bottom of: https://bugzilla.mozilla.org/userprefs.cgi?tab=email
* Give yourself a nickname in bugzilla by going to https://bugzilla.mozilla.org/userprefs.cgi?tab=account and adding your IRC handle after a colon in square brackets after your name, e.g. '''Ian Gilman [:iangilman]'''. This makes it easier for people to assign bugs to you.


= Development =  
= Development =  
Line 49: Line 56:
  make -s -j8 -C objdir-ff-release/browser/locales && make -s -j8 -C objdir-ff-release/browser/themes && make -s -j8 -C objdir-ff-release/browser/base && make -s -j8 -C objdir-ff-release/browser/app
  make -s -j8 -C objdir-ff-release/browser/locales && make -s -j8 -C objdir-ff-release/browser/themes && make -s -j8 -C objdir-ff-release/browser/base && make -s -j8 -C objdir-ff-release/browser/app
  objdir-ff-release/dist/Minefield.app/Contents/MacOS/firefox-bin -no-remote -P tcc
  objdir-ff-release/dist/Minefield.app/Contents/MacOS/firefox-bin -no-remote -P tcc
You'll need to do a full rebuild every time you pull new code from mozilla-central, though.


The html and javascript files are in '''browser/base/content/tabview'''. The images and CSS file are in '''browser/themes/<platform>/browser/tabview'''. The tests are in '''browser/base/content/test/tabview'''.
The html and javascript files are in '''browser/base/content/tabview'''. The images and CSS file are in '''browser/themes/<platform>/browser/tabview'''. The tests are in '''browser/base/content/test/tabview'''.
Line 74: Line 83:
# Create a bug in bugzilla describing what your patch will do/fix, or use an existing bug if appropriate
# Create a bug in bugzilla describing what your patch will do/fix, or use an existing bug if appropriate
# If the patch fixes a bug or adds a feature (rather than, say, code clean-up, string changes, style changes, etc), it should have a unit test.   
# If the patch fixes a bug or adds a feature (rather than, say, code clean-up, string changes, style changes, etc), it should have a unit test.   
# Try the tests locally: '''TEST_PATH=browser/base/content/test make -C ''<objdir>'' mochitest-browser-chrome'''
# Push your patch to tryserver to make sure it doesn't break anything:  
# Push your patch to tryserver to make sure it doesn't break anything:  
## Update your m-c local repo  
## Update your m-c local repo  
68

edits