Slide 1
Slide 1 text
Hack Atom w/ Node
Kenju Wagatsuma
Slide 2
Slide 2 text
/*
* Introduce Myself
*
* @kenjuwagatsuma
*/
Slide 3
Slide 3 text
'me' = {
name : 'Kenju Wagatsuma ( KJ )’,
}
Slide 4
Slide 4 text
'me' = {
name : 'Kenju Wagatsuma ( KJ )’,
company : 'Recruit Technologies Co.,LTD.',
}
Slide 5
Slide 5 text
'me' = {
name : 'Kenju Wagatsuma ( KJ )’,
company : 'Recruit Technologies Co.,LTD.',
profession : 'Android Development',
}
Slide 6
Slide 6 text
'me' = {
name : 'Kenju Wagatsuma ( KJ )’,
company : 'Recruit Technologies Co.,LTD.',
profession : 'Android Development',
career : {
2011 : 'Graphic Designer ( PS, AI, ID )'
2013 : 'Web Designer ( HTML+CSS, jQuery)'
2014 : 'Web Engineer ( JavaScript )'
2015 : 'Programmer ( Java/Android )'
}
}
Slide 7
Slide 7 text
Me * Node
=
Slide 8
Slide 8 text
Me * Node
= Not Professional
(Just for fun)
Slide 9
Slide 9 text
No content
Slide 10
Slide 10 text
No content
Slide 11
Slide 11 text
No content
Slide 12
Slide 12 text
No content
Slide 13
Slide 13 text
No content
Slide 14
Slide 14 text
No content
Slide 15
Slide 15 text
No content
Slide 16
Slide 16 text
No content
Slide 17
Slide 17 text
No content
Slide 18
Slide 18 text
No content
Slide 19
Slide 19 text
/*
* What Atom?
*/
Slide 20
Slide 20 text
Atom is: ->
❖ Project supported by GitHub
Slide 21
Slide 21 text
Atom is: ->
❖ Project supported by GitHub
❖ Specialized variant of Chromium
designed to be a text editor
Slide 22
Slide 22 text
Atom is: ->
❖ Project supported by GitHub
❖ Specialized variant of Chromium
designed to be a text editor
˕ asset pipelines
Slide 23
Slide 23 text
Atom is: ->
❖ Project supported by GitHub
❖ Specialized variant of Chromium
designed to be a text editor
˕ asset pipelines
˕ access to local files
Slide 24
Slide 24 text
Atom is: ->
❖ Project supported by GitHub
❖ Specialized variant of Chromium
designed to be a text editor
˕ asset pipelines
˕ access to local files
˕ asynchronous module definition
Slide 25
Slide 25 text
Atom is: ->
❖ Project supported by GitHub
❖ Specialized variant of Chromium
designed to be a text editor
˕ asset pipelines
˕ access to local files
˕ asynchronous module definition
˕ script concatenation
Slide 26
Slide 26 text
https://speakerdeck.com/zcbenz/practice-on-embedding-node-dot-js-into-atom-editor
Slide 27
Slide 27 text
https://speakerdeck.com/zcbenz/practice-on-embedding-node-dot-js-into-atom-editor
(Before Electron)
Slide 28
Slide 28 text
/*
* Why Atom?
*/
Slide 29
Slide 29 text
Why Atom: ->
❖ Play with Node API
❖ FS, HTTP, Stream, Async methods…
Slide 30
Slide 30 text
Why Atom: ->
❖ Play with Node API
❖ FS, HTTP, Stream, Async methods…
❖ Always running on the newest Chromium
❖ No more polyfill
❖ Can ignore browser compatibility
Slide 31
Slide 31 text
Why Atom: ->
❖ Play with Node API
❖ FS, HTTP, Stream, Async methods…
❖ Always running on the newest Chromium
❖ No more polyfill
❖ Can ignore browser compatibility
❖ Support from GitHub teams
❖ Long-term development
Slide 32
Slide 32 text
/*
* How Atom?
*/
Slide 33
Slide 33 text
❖ 1. Contribute to Atom Editor
❖ 2. Contribute to Atom Packages
❖ 3. Write Your Own Atom Package
You can: ->
Slide 34
Slide 34 text
❖ 1. Contribute to Atom Editor
❖ 2. Contribute to Atom Packages
❖ 3. Write Your Own Atom Package
You can: ->
Slide 35
Slide 35 text
*
* @param x : ?(mental)
* @param y : ?(skill)
* @param z : ?(grammer)
* @return ?
*/
contribute(x, y, z): ->
while x.isExist
doYourBest
Slide 36
Slide 36 text
*
* @param x : Passion
* @param y : Node
* @param z : CoffeScript
* @return ?
*/
contribute(x, y, z): ->
while x.isExist
doYourBest
Slide 37
Slide 37 text
❖ 1. Contribute to Atom Editor
❖ 2. Contribute to Atom Packages
❖ 3. Write Your Own Atom Package
You can: ->
Slide 38
Slide 38 text
No content
Slide 39
Slide 39 text
No content
Slide 40
Slide 40 text
/*
* We Need Your Help!
*/
Slide 41
Slide 41 text
❖ 1. Contribute to Atom Editor
❖ 2. Contribute to Atom Packages
❖ 3. Write Your Own Atom Package
You can: ->
Slide 42
Slide 42 text
Atom API: ->
Clipboard
Color
Cursor
Directory
File
GitRepository
KeymapManager
TextBuffer
ThemeManager
…etc
Slide 43
Slide 43 text
Get Started: ->
‘cmd-shift-p’
then
‘Package Generator’
… That’s it!
Slide 44
Slide 44 text
Package: ->
This is the basic
package layout.
`lib` file is the core
of the packages:
***-view.coffee
***.coffee
Slide 45
Slide 45 text
Debug: ->
It’s based on
Chromium, right?
Slide 46
Slide 46 text
Test: ->
Oh, my princess
Jasmine—
Slide 47
Slide 47 text
Publish: ->
`apm publish`
is
what you’re looking for.
Run
`apm publish -h`
for help
Slide 48
Slide 48 text
/*
* Conclusion
*/
Slide 49
Slide 49 text
❖ 1. Contribute to Atom Editor
→ Please do if you can :)
❖ 2. Contribute to Atom Packages
→ A lot of rooms for improvement
❖ 3. Write Your Own Atom Package
→ Super Easy
You can: ->
Slide 50
Slide 50 text
Read this: ->
https://atom.io/docs/v1.1.0/
Atom
Flight Manual
Slide 51
Slide 51 text
Ask Here: ->
https://discuss.atom.io/
Atom Discuss
Slide 52
Slide 52 text
Join us: ->
https://atomio.slack.com/
Atom Slack
Slide 53
Slide 53 text
Atom is really hackable
Slide 54
Slide 54 text
Atom is really hackable
powered by Node.js
Slide 55
Slide 55 text
Atom is really hackable
powered by Node.js
and you are Node Professional!
Slide 56
Slide 56 text
No content
Slide 57
Slide 57 text
http://bit.ly/nodefest2015kj
Thanks;
Slide 58
Slide 58 text
/*
* Appendix
*/
Slide 59
Slide 59 text
❖ Release Notes
➡ https://atom.io/releases
❖ API References
➡ https://atom.io/docs/api/v1.1.0/Atom
❖ Blog
➡ http://blog.atom.io/
References: ->
Slide 60
Slide 60 text
❖ “node-webkit” by Cheng Zhao
➡ https://speakerdeck.com/zcbenz/
node-webkit-app-runtime-based-on-
chromium-and-node-dot-js
❖ “Atom” by John Nunemaker
➡ https://speakerdeck.com/
jnunemaker/atom
Best Slides: ->