Proposals for the Reborn Pharo Developer

  • 423 views
Uploaded on

Proposals for the Reborn Pharo Developer by Simon Denier, Damien Pollet and stephane ducasse. ESUG09, Brest, France

Proposals for the Reborn Pharo Developer by Simon Denier, Damien Pollet and stephane ducasse. ESUG09, Brest, France

  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
423
On Slideshare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
3
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. Proposals for the Reborn Pharo Developer Simon Denier, Damien Pollet, Stéphane Ducasse 1
  • 2. My name is Simon Denier 2
  • 3. and I have nothing to show 3
  • 4. What do I have? 4
  • 5. Some backstory 5
  • 6. I’m a newcomer to Smalltalk 6
  • 7. less than a year 7
  • 8. Did my time in Java 8
  • 9. 5 years with eclipse... 9
  • 10. So it’s quite a shock 10
  • 11. And sometimes I wonder 11
  • 12. “what the f...?” 12
  • 13. Good stuff 13
  • 14. 14
  • 15. Not so good stuff 15
  • 16. 16
  • 17. So I have some ideas and I want yours 17
  • 18. Focus 18
  • 19. When I code 19
  • 20. I do one thing at a time 20
  • 21. Coding is task-oriented 21
  • 22. I may browse the system 22
  • 23. But I always come back to a few classes 23
  • 24. Unfortunately 24
  • 25. 25
  • 26. Working set 26
  • 27. Set of interesting items 27
  • 28. Selected items Unsaved items History items 28
  • 29. Tools built around the working set 29
  • 30. Working set = the new workhorse 30
  • 31. Ubiquity 31
  • 32. Select text then... 32
  • 33. do it, print it, inspect it, debug it... 33
  • 34. browse class, senders, implementors 34
  • 35. It’s a marvellous thing 35
  • 36. Unfortunately 36
  • 37. Not every interaction is so seamless 37
  • 38. Menus are less accessible than toolbars 38
  • 39. Menus are cumbersome for most-used actions 39
  • 40. Menus become cluttered with many items 40
  • 41. What is better? 41
  • 42. Pie menus 42
  • 43. Good for most used items 43
  • 44. Good with mouse gestures 44
  • 45. Hyperlink 45
  • 46. Semi-modal hyperlinks in text pane 46
  • 47. control+click browse definition/implementors 47
  • 48. control+alt+click browse references/senders 48
  • 49. Ubiquity means seamless interaction everywhere 49
  • 50. Navigation 50
  • 51. So ubiquity is cool for browsing code 51
  • 52. but what about focus? 52
  • 53. Did you try browsing senders of #=? 53
  • 54. Do you want implementors of #new in package? 54
  • 55. We need focus for navigation and search 55
  • 56. Look for senders of #= in this class 56
  • 57. Look for implementors of #new in package 57
  • 58. Look for class definition of String in the system 58
  • 59. Look for methods of Collection in its hierarchy 59
  • 60. Do you see the pattern? 60
  • 61. Look for aspect of target in scope 61
  • 62. Look for senders of #= in this class 62
  • 63. Look for implementors of #new in package 63
  • 64. Look for class definition of String in the system 64
  • 65. Look for methods of Collection in its hierarchy 65
  • 66. (all?) search can be expressed in this wannabe API 66
  • 67. Remember 67
  • 68. focus+ubiquity+navigation = new Pharo experience! 68