Small Screen Development

2,522 views
2,398 views

Published on

Many developers are forced to develop on small screens: Travelling, Coworking spaces, changing project locations, you name it. But what can you do to improve your workflow if you are bound to a small screen? This presentation tries to give some answers and suggestions.

Published in: Technology
2 Comments
5 Likes
Statistics
Notes
No Downloads
Views
Total views
2,522
On SlideShare
0
From Embeds
0
Number of Embeds
81
Actions
Shares
0
Downloads
3
Comments
2
Likes
5
Embeds 0
No embeds

No notes for slide
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • Small Screen Development

    1. 1. Small Screen DevelopmentHow to make the most out of sparse screen real estate
    2. 2. /me• Ralph von der Heyden• ralph+developer@railslove.com• @ralph• http://rvdh.de/
    3. 3. Screen real estate...
    4. 4. But...
    5. 5. Find the ideal small screen workflow!
    6. 6. Step 1: Show as muchinformation as possible
    7. 7. Full Screen
    8. 8. Don‘t waste precious pixels
    9. 9. Multitasking is a myth
    10. 10. Distraction free
    11. 11. Usability expertsrecommend it...
    12. 12. How much do youwaste going non- fullscreen?
    13. 13. Dock: 94720px Menubar: 26880pxWorking window: 902400px Full Screen: 1024000px
    14. 14. Diagramm
    15. 15. ~10% wasted pixels
    16. 16. another ~10% for the app‘s toolbar
    17. 17. Conclusion• Keep the dock hidden• Switch your apps to full screen if possible➡More information at a glance
    18. 18. Which applications do we need as Rails developers?
    19. 19. Rails equipment• Browser• Terminal• Editor
    20. 20. Browser: Google Chrome• ⇧⌘F opens full screen• ⌘L • puts the cursor in the address bar • shows tabs, bookmarks etc.• ⌥⌘← and ⌥⌘→ switches tabs
    21. 21. Terminal: iterm2• (in early alpha, but „works for me“)• ⌘-enter switches to full screen• hold ⌘ for a second to see the tabs
    22. 22. Editor: MacVim, vim• Choose an editor without a toolbar• MacVim supports full screen• Terminal editors support full screen via iterm2• Textmate isn‘t bad, either, but has annoyances (e.g. drawer)
    23. 23. What are the problems when developing on small screens?
    24. 24. Problems on small screens• Finding the information you need• Interacting with a specific process➡Switching between applications
    25. 25. Switching on big screens...
    26. 26. Switching on small screens... ⌘-tab
    27. 27. (Usually, there is a bit of ⌘-tab on big screens, too.)
    28. 28. What‘s wrong with... ⌘-tab ?
    29. 29. Danger of overshooting
    30. 30. ⌘-tab ⌘-tab-tab ⌘-tab-tab-tab ⌘-tab-tab-tab-tab ⌘-tab-tab-tab-tab-tab ⌘-tab-tab-tab-tab-tab-tab ⌘-tab-tab-tab-tab-tab-tab-tab ⌘-tab-tab-tab-tab-tab-tab-tab-tab⌘-tab-tab-tab-tab-tab-tab-tab-tab-tab ...
    31. 31. ⌘-tab
    32. 32. Alternative: VisorGlobal keyboard shortcut: ⌘-tab
    33. 33. Conclusion• Switch to a command line editor• Make the terminal your comfy place➡Avoid confusion while switching between your main applications (overshooting)
    34. 34. Command line editor* *(This is the hardest part)
    35. 35. Choices• VIM• Emacs• Set it up right
    36. 36. OSX font rendering?
    37. 37. iterm2 haz it
    38. 38. Color schemes?
    39. 39. 256 colors are enough for everybody
    40. 40. You‘ll have to live withlimitations, but maybe that is worth it.
    41. 41. Make the terminal your comfy zone
    42. 42. Make the terminal your comfy zone• Get a decent shell and prompt• Set up easy process switching
    43. 43. Shell• zsh: oh-my-zsh• bash: bash-it• completion, templates, you name it...
    44. 44. Easier process switching
    45. 45. Easier process switching• CTRL-Z suspends processes• CTRL-F alternates between suspended processes (if you set it up)
    46. 46. Easier process switching (zsh)• Alternate between backgrounded processes with CTRL-F • bindkey -s ^f "fg %-n" • export HISTIGNORE="fg*"• fg to bring up the last bg process• YOU WILL HAVEdoesn‘t work with ruby) !!! (the preexec part TO FIX oh-my-zsh
    47. 47. Assumption: Running 3 processes in 1 shell• bash/zsh• rails console• vim
    48. 48. Switch from vim to shell and back CTRL-Z fg
    49. 49. Switch from vim to rails console and back CTRL-Z CTRL-F CTRL-F CTRL-Z
    50. 50. Shell our from your editor• :!command to run something• :! to see shell history
    51. 51. Why is it better than tabs?
    52. 52. It just feels better.(more smooth, natural, efficient, ...) And works everywhere.
    53. 53. More information at a glance
    54. 54. Use panes
    55. 55. tmux• terminal multiplexer• Very powerful• Does not support OSX clipboard• (though there is patch for the 1.3 version)
    56. 56. iterm2• Very easy to use • ⌘D vertical split • ⌘⇧D horizontal split • ⌥⌘←/→/↑/↓ switches between panes • Touchpad scrolling• Not as powerful as tmux (no rearranging of panes etc.)
    57. 57. Take-aways for all small screeners:• Switch to full screen• Lern you some terminal-fu• Try a command line editor• Some stuff is also useful for big screens, server admin etc.
    58. 58. What do you think?
    59. 59. Sources• http://oinopa.com/2010/10/24/laptop-driven-development.html• http://www.apple.com/macosx/lion/• http://code.google.com/p/iterm2/• http://code.google.com/p/macvim/• https://github.com/robbyrussell/oh-my-zsh• https://github.com/revans/bash-it• http://www.google.com/chrome/• http://tmux.sourceforge.net/

    ×