extension_tutorial.rst 34 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148149150151152153154155156157158159160161162163164165166167168169170171172173174175176177178179180181182183184185186187188189190191192193194195196197198199200201202203204205206207208209210211212213214215216217218219220221222223224225226227228229230231232233234235236237238239240241242243244245246247248249250251252253254255256257258259260261262263264265266267268269270271272273274275276277278279280281282283284285286287288289290291292293294295296297298299300301302303304305306307308309310311312313314315316317318319320321322323324325326327328329330331332333334335336337338339340341342343344345346347348349350351352353354355356357358359360361362363364365366367368369370371372373374375376377378379380381382383384385386387388389390391392393394395396397398399400401402403404405406407408409410411412413414415416417418419420421422423424425426427428429430431432433434435436437438439440441442443444445446447448449450451452453454455456457458459460461462463464465466467468469470471472473474475476477478479480481482483484485486487488489490491492493494495496497498499500501502503504505506507508509510511512513514515516517518519520521522523524525526527528529530531532533534535536537538539540541542543544545546547548549550551552553554555556557558559560561562563564565566567568569570571572573574575576577578579580581582583584585586587588589590591592593594595596597598599600601602603604605606607608609610611612613614615616617618619620621622623624625626627628629630631632633634635636637638639640641642643644645646647648649650651652653654655656657658659660661662663664665666667668669670671672673674675676677678679680681682683684685686687688689690691692693694695696697698699700701702703704705706707708709710711712713714715716717718719720721722723724725726727728729730731732733734735736737738739740741742743744745746747748749750751752753754755756757758759760761762763764765766767768769770771772773774775776777778779780781782783784785786787788789790791792793794795796797798799800801802803804805806807808809810811812813814815816817818819820821822823824825826827828829830831832833834835836837838839840841842843844845846847848849850851852853854855856857858859860861862863864865866867868869870871872873874875876877878879880881882883884885886887888889890891892893894895896897898899900901902903904905906907908909910911912913914915916917918919920921922923924925926927928929930931932933934935936937938939940941942943944945946947948949950951952
  1. .. _extension_tutorial:
  2. Let's Make an Astronomy Picture of the Day JupyterLab Extension
  3. ----------------------------------------------------------------
  4. JupyterLab extensions add features to the user experience. This page
  5. describes how to create one type of extension, an *application plugin*,
  6. that:
  7. - Adds a "Random `Astronomy Picture <https://apod.nasa.gov/apod/astropix.html>`__" command to the
  8. *command palette* sidebar
  9. - Fetches the image and metadata when activated
  10. - Shows the image and metadata in a tab panel
  11. By working through this tutorial, you'll learn:
  12. - How to set up an extension development environment from scratch on a
  13. Linux or OSX machine. (You'll need to modify the commands slightly if you are on Windows.)
  14. - How to start an extension project from
  15. `jupyterlab/extension-cookiecutter-ts <https://github.com/jupyterlab/extension-cookiecutter-ts>`__
  16. - How to iteratively code, build, and load your extension in JupyterLab
  17. - How to version control your work with git
  18. - How to release your extension for others to enjoy
  19. .. figure:: extension_tutorial_complete.png
  20. :align: center
  21. :class: jp-screenshot
  22. :alt: The completed extension, showing the Astronomy Picture of the Day for 24 Jul 2015.
  23. The completed extension, showing the `Astronomy Picture of the Day for 24 Jul 2015 <https://apod.nasa.gov/apod/ap150724.html>`__.
  24. Sound like fun? Excellent. Here we go!
  25. Set up a development environment
  26. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  27. Install conda using miniconda
  28. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  29. Start by installing miniconda, following
  30. `Conda's installation documentation <https://docs.conda.io/projects/conda/en/latest/user-guide/install/index.html>`__.
  31. .. _install-nodejs-jupyterlab-etc-in-a-conda-environment:
  32. Install NodeJS, JupyterLab, etc. in a conda environment
  33. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  34. Next create a conda environment that includes:
  35. 1. the latest release of JupyterLab
  36. 2. `cookiecutter <https://github.com/audreyr/cookiecutter>`__, the tool
  37. you'll use to bootstrap your extension project structure (this is a Python tool
  38. which we'll install using conda below).
  39. 3. `NodeJS <https://nodejs.org>`__, the JavaScript runtime you'll use to
  40. compile the web assets (e.g., TypeScript, CSS) for your extension
  41. 4. `git <https://git-scm.com>`__, a version control system you'll use to
  42. take snapshots of your work as you progress through this tutorial
  43. It's best practice to leave the root conda environment (i.e., the environment created
  44. by the miniconda installer) untouched and install your project-specific
  45. dependencies in a named conda environment. Run this command to create a
  46. new environment named ``jupyterlab-ext``.
  47. .. code:: bash
  48. conda create -n jupyterlab-ext -c conda-forge --override-channels jupyterlab cookiecutter nodejs git
  49. Now activate the new environment so that all further commands you run
  50. work out of that environment.
  51. .. code:: bash
  52. conda activate jupyterlab-ext
  53. Note: You'll need to run the command above in each new terminal you open
  54. before you can work with the tools you installed in the
  55. ``jupyterlab-ext`` environment.
  56. Create a repository
  57. ~~~~~~~~~~~~~~~~~~~
  58. Create a new repository for your extension (see, for example, the
  59. `GitHub instructions <https://help.github.com/articles/create-a-repo/>`__. This is an
  60. optional step, but highly recommended if you want to share your
  61. extension.
  62. Create an extension project
  63. ~~~~~~~~~~~~~~~~~~~~~~~~~~~
  64. Initialize the project from a cookiecutter
  65. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  66. Next use cookiecutter to create a new project for your extension.
  67. This will create a new folder for your extension in your current directory.
  68. .. code:: bash
  69. cookiecutter https://github.com/jupyterlab/extension-cookiecutter-ts --checkout v1.0
  70. When prompted, enter values like the following for all of the cookiecutter
  71. prompts (``apod`` stands for Astronomy Picture of the Day, the NASA service we
  72. are using to fetch pictures).
  73. ::
  74. author_name []: Your Name
  75. extension_name [myextension]: jupyterlab_apod
  76. project_short_description [A JupyterLab extension.]: Show a random NASA Astronomy Picture of the Day in a JupyterLab panel
  77. repository [https://github.com/my_name/jupyterlab_myextension]: https://github.com/my_name/jupyterlab_apod
  78. Note: if not using a repository, leave the repository field blank. You can come
  79. back and edit the repository field in the ``package.json`` file later.
  80. Change to the directory the cookiecutter created and list the files.
  81. .. code:: bash
  82. cd jupyterlab_apod
  83. ls
  84. You should see a list like the following.
  85. ::
  86. README.md package.json src style tsconfig.json
  87. Build and install the extension for development
  88. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  89. Your new extension project has enough code in it to see it working in
  90. your JupyterLab. Run the following commands to install the initial
  91. project dependencies and install it in the JupyterLab environment. We
  92. defer building since it will be built in the next step.
  93. .. note::
  94. This tutorial uses ``jlpm`` to install Javascript packages and
  95. run build commands, which is JupyterLab's bundled
  96. version of ``yarn``. If you prefer, you can use another Javascript
  97. package manager like ``npm`` or ``yarn`` itself.
  98. .. code:: bash
  99. jlpm install
  100. jupyter labextension install . --no-build
  101. After the install completes, open a second terminal. Run these commands
  102. to activate the ``jupyterlab-ext`` environment and to start a JupyterLab
  103. instance in watch mode so that it will keep up with our changes as we
  104. make them.
  105. .. code:: bash
  106. conda activate jupyterlab-ext
  107. jupyter lab --watch
  108. See the initial extension in action
  109. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  110. After building with your extension, JupyterLab should open in your
  111. default web browser.
  112. In that browser window, open the JavaScript console
  113. by following the instructions for your browser:
  114. - `Accessing the DevTools in Google
  115. Chrome <https://developer.chrome.com/devtools#access>`__
  116. - `Opening the Web Console in
  117. Firefox <https://developer.mozilla.org/en-US/docs/Tools/Web_Console/Opening_the_Web_Console>`__
  118. After you reload the page with the console open, you should see a message that says
  119. ``JupyterLab extension jupyterlab_apod is activated!`` in the console.
  120. If you do, congratulations, you're ready to start modifying the extension!
  121. If not, go back make sure you didn't miss a step, and `reach
  122. out <https://github.com/jupyterlab/jupyterlab/blob/master/README.md#getting-help>`__ if you're stuck.
  123. Note: Leave the terminal running the ``jupyter lab --watch`` command
  124. open.
  125. Commit what you have to git
  126. ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  127. Run the following commands in your ``jupyterlab_apod`` folder to
  128. initialize it as a git repository and commit the current code.
  129. .. code:: bash
  130. git init
  131. git add .
  132. git commit -m 'Seed apod project from cookiecutter'
  133. Note: This step is not technically necessary, but it is good practice to
  134. track changes in version control system in case you need to rollback to
  135. an earlier version or want to collaborate with others. For example, you
  136. can compare your work throughout this tutorial with the commits in a
  137. reference version of ``jupyterlab_apod`` on GitHub at
  138. https://github.com/jupyterlab/jupyterlab_apod.
  139. Add an Astronomy Picture of the Day widget
  140. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  141. Show an empty panel
  142. ^^^^^^^^^^^^^^^^^^^
  143. The *command palette* is the primary view of all commands available to
  144. you in JupyterLab. For your first addition, you're going to add a
  145. *Random Astronomy Picture* command to the palette and get it to show an *Astronomy Picture*
  146. tab panel when invoked.
  147. Fire up your favorite text editor and open the ``src/index.ts`` file in
  148. your extension project. Change the import at the top of the file to get
  149. a reference to the command palette interface and the Jupyter front end.
  150. .. code:: typescript
  151. import {
  152. JupyterFrontEnd, JupyterFrontEndPlugin
  153. } from '@jupyterlab/application';
  154. import {
  155. ICommandPalette
  156. } from '@jupyterlab/apputils';
  157. You will also need to install these dependencies. Run the following commands in the
  158. repository root folder install the dependency and save it to your
  159. `package.json`:
  160. .. code:: bash
  161. jlpm add @jupyterlab/apputils
  162. jlpm add @jupyterlab/application
  163. Locate the ``extension`` object of type ``JupyterFrontEndPlugin``. Change the
  164. definition so that it reads like so:
  165. .. code:: typescript
  166. /**
  167. * Initialization data for the jupyterlab_apod extension.
  168. */
  169. const extension: JupyterFrontEndPlugin<void> = {
  170. id: 'jupyterlab_apod',
  171. autoStart: true,
  172. requires: [ICommandPalette],
  173. activate: (app: JupyterFrontEnd, palette: ICommandPalette) => {
  174. console.log('JupyterLab extension jupyterlab_apod is activated!');
  175. console.log('ICommandPalette:', palette);
  176. }
  177. };
  178. The ``requires`` attribute states that your plugin needs an object that
  179. implements the ``ICommandPalette`` interface when it starts. JupyterLab
  180. will pass an instance of ``ICommandPalette`` as the second parameter of
  181. ``activate`` in order to satisfy this requirement. Defining
  182. ``palette: ICommandPalette`` makes this instance available to your code
  183. in that function. The second ``console.log`` line exists only so that
  184. you can immediately check that your changes work.
  185. Run the following to rebuild your extension.
  186. .. code:: bash
  187. jlpm run build
  188. JupyterLab will rebuild after the extension does. You can
  189. see it's progress in the ``jupyter lab --watch`` window. After that
  190. finishes, return to the browser tab that opened when you
  191. started JupyterLab. Refresh it and look in the console. You should see
  192. the same activation message as before, plus the new message about the
  193. ICommandPalette instance you just added. If you don't, check the output
  194. of the build command for errors and correct your code.
  195. ::
  196. JupyterLab extension jupyterlab_apod is activated!
  197. ICommandPalette: Palette {_palette: CommandPalette}
  198. Note that we had to run ``jlpm run build`` in order for the bundle to
  199. update, because it is using the compiled JavaScript files in ``/lib``.
  200. If you wish to avoid running ``jlpm run build`` after each change, you
  201. can open a third terminal, and run the ``jlpm run watch`` command from
  202. your extension directory, which will automatically compile the
  203. TypeScript files as they change.
  204. Now return to your editor. Modify the imports at the top of the file to add a few more imports:
  205. .. code:: typescript
  206. import {
  207. ICommandPalette, MainAreaWidget
  208. } from '@jupyterlab/apputils';
  209. import {
  210. Widget
  211. } from '@phosphor/widgets';
  212. Install this new dependency as well:
  213. .. code:: bash
  214. jlpm add @phosphor/widgets
  215. Then modify the ``activate`` function again so that it has the following
  216. code:
  217. .. code-block:: typescript
  218. activate: (app: JupyterFrontEnd, palette: ICommandPalette) => {
  219. console.log('JupyterLab extension jupyterlab_apod is activated!');
  220. // Create a blank content widget inside of a MainAreaWidget
  221. const content = new Widget();
  222. const widget = new MainAreaWidget({content});
  223. widget.id = 'apod-jupyterlab';
  224. widget.title.label = 'Astronomy Picture';
  225. widget.title.closable = true;
  226. // Add an application command
  227. const command: string = 'apod:open';
  228. app.commands.addCommand(command, {
  229. label: 'Random Astronomy Picture',
  230. execute: () => {
  231. if (!widget.isAttached) {
  232. // Attach the widget to the main work area if it's not there
  233. app.shell.add(widget, 'main');
  234. }
  235. // Activate the widget
  236. app.shell.activateById(widget.id);
  237. }
  238. });
  239. // Add the command to the palette.
  240. palette.addItem({command, category: 'Tutorial'});
  241. }
  242. The first new block of code creates a ``MainAreaWidget`` instance with an empty
  243. content ``Widget`` as its child. It also assigns the main area widget a unique
  244. ID, gives it a label that will appear as its tab title, and makes the tab
  245. closable by the user.
  246. The second block of code adds a new command with id ``apod:open`` and label *Random Astronomy Picture*
  247. to JupyterLab. When the command executes,
  248. it attaches the widget to the main display area if it is not already
  249. present and then makes it the active tab. The last new line of code uses the command id to add
  250. the command to the command palette in a section called *Tutorial*.
  251. Build your extension again using ``jlpm run build`` (unless you are using
  252. ``jlpm run watch`` already) and refresh the browser tab. Open the command
  253. palette on the left side by clicking on *Commands* and type *Astronomy* in
  254. the search box. Your *Random Astronomy Picture*
  255. command should appear. Click it or select it with the keyboard and press
  256. *Enter*. You should see a new, blank panel appear with the tab title
  257. *Astronomy Picture*. Click the *x* on the tab to close it and activate the
  258. command again. The tab should reappear. Finally, click one of the
  259. launcher tabs so that the *Astronomy Picture* panel is still open but no longer
  260. active. Now run the *Random Astronomy Picture* command one more time. The
  261. single *Astronomy Picture* tab should come to the foreground.
  262. .. figure:: extension_tutorial_empty.png
  263. :align: center
  264. :class: jp-screenshot
  265. :alt: The in-progress extension, showing a blank panel.
  266. The in-progress extension, showing a blank panel.
  267. If your widget is not behaving, compare your code with the reference
  268. project state at the `01-show-a-panel
  269. tag <https://github.com/jupyterlab/jupyterlab_apod/tree/1.0-01-show-a-panel>`__.
  270. Once you've got everything working properly, git commit your changes and
  271. carry on.
  272. .. code-block:: bash
  273. git add .
  274. git commit -m 'Show Astronomy Picture command in palette'
  275. Show a picture in the panel
  276. ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  277. You now have an empty panel. It's time to add a picture to it. Go back to
  278. your code editor. Add the following code below the lines that create a
  279. ``MainAreaWidget`` instance and above the lines that define the command.
  280. .. code-block:: typescript
  281. // Add an image element to the content
  282. let img = document.createElement('img');
  283. content.node.appendChild(img);
  284. // Get a random date string in YYYY-MM-DD format
  285. function randomDate() {
  286. const start = new Date(2010, 1, 1);
  287. const end = new Date();
  288. const randomDate = new Date(start.getTime() + Math.random()*(end.getTime() - start.getTime()));
  289. return randomDate.toISOString().slice(0, 10);
  290. }
  291. // Fetch info about a random picture
  292. const response = await fetch(`https://api.nasa.gov/planetary/apod?api_key=DEMO_KEY&date=${randomDate()}`);
  293. const data = await response.json() as APODResponse;
  294. if (data.media_type === 'image') {
  295. // Populate the image
  296. img.src = data.url;
  297. img.title = data.title;
  298. } else {
  299. console.log('Random APOD was not a picture.');
  300. }
  301. The first two lines create a new HTML ``<img>`` element and add it to
  302. the widget DOM node. The next lines define a function get a random date in the form ``YYYY-MM-DD`` format, and then the function is used to make a request using the HTML
  303. `fetch <https://developer.mozilla.org/en-US/docs/Web/API/Fetch_API/Using_Fetch>`__
  304. API that returns information about the Astronomy Picture of the Day for that date. Finally, we set the
  305. image source and title attributes based on the response.
  306. Now define the ``APODResponse`` type that was introduced in the code above. Put
  307. this definition just under the imports at the top of the file.
  308. .. code-block:: typescript
  309. interface APODResponse {
  310. copyright: string;
  311. date: string;
  312. explanation: string;
  313. media_type: 'video' | 'image';
  314. title: string;
  315. url: string;
  316. };
  317. And update the ``activate`` method to be ``async`` since we are now using
  318. ``await`` in the method body.
  319. .. code-block:: typescript
  320. activate: async (app: JupyterFrontEnd, palette: ICommandPalette) =>
  321. Rebuild your extension if necessary (``jlpm run build``), refresh your browser
  322. tab, and run the *Random Astronomy Picture* command again. You should now see a
  323. picture in the panel when it opens (if that random date had a picture and not a
  324. video).
  325. .. figure:: extension_tutorial_single.png
  326. :align: center
  327. :class: jp-screenshot
  328. The in-progress extension, showing the `Astronomy Picture of the Day for 19 Jan 2014 <https://apod.nasa.gov/apod/ap140119.html>`__.
  329. Note that the image is not centered in the panel nor does the panel
  330. scroll if the image is larger than the panel area. Also note that the
  331. image does not update no matter how many times you close and reopen the
  332. panel. You'll address both of these problems in the upcoming sections.
  333. If you don't see a image at all, compare your code with the
  334. `02-show-an-image
  335. tag <https://github.com/jupyterlab/jupyterlab_apod/tree/1.0-02-show-an-image>`__
  336. in the reference project. When it's working, make another git commit.
  337. .. code:: bash
  338. git add .
  339. git commit -m 'Show a picture in the panel'
  340. Improve the widget behavior
  341. ~~~~~~~~~~~~~~~~~~~~~~~~~~~
  342. Center the image, add attribution, and error messaging
  343. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  344. Open ``style/index.css`` in our extension project directory for editing.
  345. Add the following lines to it.
  346. .. code-block:: css
  347. .my-apodWidget {
  348. display: flex;
  349. flex-direction: column;
  350. align-items: center;
  351. overflow: auto;
  352. }
  353. This CSS stacks content vertically within the widget panel and lets the panel
  354. scroll when the content overflows. This CSS file is included on the page
  355. automatically by JupyterLab because the ``package.json`` file has a ``style``
  356. field pointing to it. In general, you should import all of your styles into a
  357. single CSS file, such as this ``index.css`` file, and put the path to that CSS
  358. file in the ``package.json`` file ``style`` field.
  359. Return to the ``index.ts`` file. Modify the ``activate``
  360. function to apply the CSS classes, the copyright information, and error handling
  361. for the API response.
  362. The beginning of the function should read like the following:
  363. .. code-block:: typescript
  364. :emphasize-lines: 6,16-17,28-50
  365. activate: async (app: JupyterFrontEnd, palette: ICommandPalette) => {
  366. console.log('JupyterLab extension jupyterlab_apod is activated!');
  367. // Create a blank content widget inside of a MainAreaWidget
  368. const content = new Widget();
  369. content.addClass('my-apodWidget'); // new line
  370. const widget = new MainAreaWidget({content});
  371. widget.id = 'apod-jupyterlab';
  372. widget.title.label = 'Astronomy Picture';
  373. widget.title.closable = true;
  374. // Add an image element to the content
  375. let img = document.createElement('img');
  376. content.node.appendChild(img);
  377. let summary = document.createElement('p');
  378. content.node.appendChild(summary);
  379. // Get a random date string in YYYY-MM-DD format
  380. function randomDate() {
  381. const start = new Date(2010, 1, 1);
  382. const end = new Date();
  383. const randomDate = new Date(start.getTime() + Math.random()*(end.getTime() - start.getTime()));
  384. return randomDate.toISOString().slice(0, 10);
  385. }
  386. // Fetch info about a random picture
  387. const response = await fetch(`https://api.nasa.gov/planetary/apod?api_key=DEMO_KEY&date=${randomDate()}`);
  388. if (!response.ok) {
  389. const data = await response.json();
  390. if (data.error) {
  391. summary.innerText = data.error.message;
  392. } else {
  393. summary.innerText = response.statusText;
  394. }
  395. } else {
  396. const data = await response.json() as APODResponse;
  397. if (data.media_type === 'image') {
  398. // Populate the image
  399. img.src = data.url;
  400. img.title = data.title;
  401. summary.innerText = data.title;
  402. if (data.copyright) {
  403. summary.innerText += ` (Copyright ${data.copyright})`;
  404. }
  405. } else {
  406. summary.innerText = 'Random APOD fetched was not an image.';
  407. }
  408. }
  409. // Keep all the remaining fetch and command lines the same
  410. // as before from here down ...
  411. Build your extension if necessary (``jlpm run build``) and refresh your
  412. JupyterLab browser tab. Invoke the *Random Astronomy Picture* command and
  413. confirm the image is centered with the copyright information below it. Resize
  414. the browser window or the panel so that the image is larger than the
  415. available area. Make sure you can scroll the panel over the entire area
  416. of the image.
  417. If anything is not working correctly, compare your code with the reference project
  418. `03-style-and-attribute
  419. tag <https://github.com/jupyterlab/jupyterlab_apod/tree/1.0-03-style-and-attribute>`__.
  420. When everything is working as expected, make another commit.
  421. .. code:: bash
  422. git add .
  423. git commit -m 'Add styling, attribution, error handling'
  424. Show a new image on demand
  425. ^^^^^^^^^^^^^^^^^^^^^^^^^^
  426. The ``activate`` function has grown quite long, and there's still more
  427. functionality to add. Let's refactor the code into two separate
  428. parts:
  429. 1. An ``APODWidget`` that encapsulates the Astronomy Picture panel elements,
  430. configuration, and soon-to-be-added update behavior
  431. 2. An ``activate`` function that adds the widget instance to the UI and
  432. decide when the picture should refresh
  433. Start by refactoring the widget code into the new ``APODWidget`` class.
  434. Add the following additional import to the top of the file.
  435. .. code-block:: typescript
  436. import {
  437. Message
  438. } from '@phosphor/messaging';
  439. Install this dependency:
  440. .. code:: bash
  441. jlpm add @phosphor/messaging
  442. Then add the class just below the import statements in the ``index.ts``
  443. file.
  444. .. code-block:: typescript
  445. class APODWidget extends Widget {
  446. /**
  447. * Construct a new APOD widget.
  448. */
  449. constructor() {
  450. super();
  451. this.addClass('my-apodWidget'); // new line
  452. // Add an image element to the panel
  453. this.img = document.createElement('img');
  454. this.node.appendChild(this.img);
  455. // Add a summary element to the panel
  456. this.summary = document.createElement('p');
  457. this.node.appendChild(this.summary);
  458. }
  459. /**
  460. * The image element associated with the widget.
  461. */
  462. readonly img: HTMLImageElement;
  463. /**
  464. * The summary text element associated with the widget.
  465. */
  466. readonly summary: HTMLParagraphElement;
  467. /**
  468. * Handle update requests for the widget.
  469. */
  470. async onUpdateRequest(msg: Message): Promise<void> {
  471. const response = await fetch(`https://api.nasa.gov/planetary/apod?api_key=DEMO_KEY&date=${this.randomDate()}`);
  472. if (!response.ok) {
  473. const data = await response.json();
  474. if (data.error) {
  475. this.summary.innerText = data.error.message;
  476. } else {
  477. this.summary.innerText = response.statusText;
  478. }
  479. return;
  480. }
  481. const data = await response.json() as APODResponse;
  482. if (data.media_type === 'image') {
  483. // Populate the image
  484. this.img.src = data.url;
  485. this.img.title = data.title;
  486. this.summary.innerText = data.title;
  487. if (data.copyright) {
  488. this.summary.innerText += ` (Copyright ${data.copyright})`;
  489. }
  490. } else {
  491. this.summary.innerText = 'Random APOD fetched was not an image.';
  492. }
  493. }
  494. You've written all of the code before. All you've done is restructure it
  495. to use instance variables and move the image request to its own
  496. function.
  497. Next move the remaining logic in ``activate`` to a new, top-level
  498. function just below the ``APODWidget`` class definition. Modify the code
  499. to create a widget when one does not exist in the main JupyterLab area
  500. or to refresh the image in the exist widget when the command runs again.
  501. The code for the ``activate`` function should read as follows after
  502. these changes:
  503. .. code-block:: typescript
  504. /**
  505. * Activate the APOD widget extension.
  506. */
  507. function activate(app: JupyterFrontEnd, palette: ICommandPalette) {
  508. console.log('JupyterLab extension jupyterlab_apod is activated!');
  509. // Create a single widget
  510. const content = new APODWidget();
  511. const widget = new MainAreaWidget({content});
  512. widget.id = 'apod-jupyterlab';
  513. widget.title.label = 'Astronomy Picture';
  514. widget.title.closable = true;
  515. // Add an application command
  516. const command: string = 'apod:open';
  517. app.commands.addCommand(command, {
  518. label: 'Random Astronomy Picture',
  519. execute: () => {
  520. if (!widget.isAttached) {
  521. // Attach the widget to the main work area if it's not there
  522. app.shell.add(widget, 'main');
  523. }
  524. // Refresh the picture in the widget
  525. content.update();
  526. // Activate the widget
  527. app.shell.activateById(widget.id);
  528. }
  529. });
  530. // Add the command to the palette.
  531. palette.addItem({ command, category: 'Tutorial' });
  532. }
  533. Remove the ``activate`` function definition from the
  534. ``JupyterFrontEndPlugin`` object and refer instead to the top-level function
  535. like this:
  536. .. code-block:: typescript
  537. const extension: JupyterFrontEndPlugin<void> = {
  538. id: 'jupyterlab_apod',
  539. autoStart: true,
  540. requires: [ICommandPalette],
  541. activate: activate
  542. };
  543. Make sure you retain the ``export default extension;`` line in the file.
  544. Now build the extension again and refresh the JupyterLab browser tab.
  545. Run the *Random Astronomy Picture* command more than once without closing the
  546. panel. The picture should update each time you execute the command. Close
  547. the panel, run the command, and it should both reappear and show a new
  548. image.
  549. If anything is not working correctly, compare your code with the
  550. `04-refactor-and-refresh
  551. tag <https://github.com/jupyterlab/jupyterlab_apod/tree/1.0-04-refactor-and-refresh>`__
  552. to debug. Once it is working properly, commit it.
  553. .. code:: bash
  554. git add .
  555. git commit -m 'Refactor, refresh image'
  556. Restore panel state when the browser refreshes
  557. ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  558. You may notice that every time you refresh your browser tab, the Astronomy Picture
  559. panel disappears, even if it was open before you refreshed. Other open
  560. panels, like notebooks, terminals, and text editors, all reappear and
  561. return to where you left them in the panel layout. You can make your
  562. extension behave this way too.
  563. Update the imports at the top of your ``index.ts`` file so that the
  564. entire list of import statements looks like the following:
  565. .. code-block:: typescript
  566. :emphasize-lines: 2,6
  567. import {
  568. ILayoutRestorer, JupyterFrontEnd, JupyterFrontEndPlugin
  569. } from '@jupyterlab/application';
  570. import {
  571. ICommandPalette, MainAreaWidget, WidgetTracker
  572. } from '@jupyterlab/apputils';
  573. import {
  574. Message
  575. } from '@phosphor/messaging';
  576. import {
  577. Widget
  578. } from '@phosphor/widgets';
  579. Install this dependency:
  580. .. code:: bash
  581. jlpm add @phosphor/coreutils
  582. Then add the ``ILayoutRestorer`` interface to the ``JupyterFrontEndPlugin``
  583. definition. This addition passes the global ``LayoutRestorer`` as the
  584. third parameter of the ``activate`` function.
  585. .. code-block:: typescript
  586. :emphasize-lines: 4
  587. const extension: JupyterFrontEndPlugin<void> = {
  588. id: 'jupyterlab_apod',
  589. autoStart: true,
  590. requires: [ICommandPalette, ILayoutRestorer],
  591. activate: activate
  592. };
  593. Finally, rewrite the ``activate`` function so that it:
  594. 1. Declares a widget variable, but does not create an instance
  595. immediately.
  596. 2. Constructs a ``WidgetTracker`` and tells the ``ILayoutRestorer``
  597. to use it to save/restore panel state.
  598. 3. Creates, tracks, shows, and refreshes the widget panel appropriately.
  599. .. code-block:: typescript
  600. function activate(app: JupyterFrontEnd, palette: ICommandPalette, restorer: ILayoutRestorer) {
  601. console.log('JupyterLab extension jupyterlab_apod is activated!');
  602. // Declare a widget variable
  603. let widget: MainAreaWidget<APODWidget>;
  604. // Add an application command
  605. const command: string = 'apod:open';
  606. app.commands.addCommand(command, {
  607. label: 'Random Astronomy Picture',
  608. execute: () => {
  609. if (!widget) {
  610. // Create a new widget if one does not exist
  611. const content = new APODWidget();
  612. widget = new MainAreaWidget({content});
  613. widget.id = 'apod-jupyterlab';
  614. widget.title.label = 'Astronomy Picture';
  615. widget.title.closable = true;
  616. }
  617. if (!tracker.has(widget)) {
  618. // Track the state of the widget for later restoration
  619. tracker.add(widget);
  620. }
  621. if (!widget.isAttached) {
  622. // Attach the widget to the main work area if it's not there
  623. app.shell.add(widget, 'main');
  624. }
  625. widget.content.update();
  626. // Activate the widget
  627. app.shell.activateById(widget.id);
  628. }
  629. });
  630. // Add the command to the palette.
  631. palette.addItem({ command, category: 'Tutorial' });
  632. // Track and restore the widget state
  633. let tracker = new WidgetTracker<MainAreaWidget<APODWidget>>({
  634. namespace: 'apod'
  635. });
  636. restorer.restore(tracker, {
  637. command,
  638. name: () => 'apod'
  639. });
  640. }
  641. Rebuild your extension one last time and refresh your browser tab.
  642. Execute the *Random Astronomy Picture* command and validate that the panel
  643. appears with an image in it. Refresh the browser tab again. You should
  644. see an Astronomy Picture panel reappear immediately without running the command. Close
  645. the panel and refresh the browser tab. You should then not see an Astronomy Picture tab
  646. after the refresh.
  647. .. figure:: extension_tutorial_complete.png
  648. :align: center
  649. :class: jp-screenshot
  650. :alt: The completed extension, showing the Astronomy Picture of the Day for 24 Jul 2015.
  651. The completed extension, showing the `Astronomy Picture of the Day for 24 Jul 2015 <https://apod.nasa.gov/apod/ap150724.html>`__.
  652. Refer to the `05-restore-panel-state
  653. tag <https://github.com/jupyterlab/jupyterlab_apod/tree/1.0-05-restore-panel-state>`__
  654. if your extension is not working correctly. Make a commit when the state of your
  655. extension persists properly.
  656. .. code:: bash
  657. git add .
  658. git commit -m 'Restore panel state'
  659. Congratulations! You've implemented all of the behaviors laid out at the start
  660. of this tutorial. Now how about sharing it with the world?
  661. .. _publish-your-extension-to-npmjsorg:
  662. Publish your extension to npmjs.org
  663. ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  664. npm is both a JavaScript package manager and the de facto registry for
  665. JavaScript software. You can `sign up for an account on the npmjs.com
  666. site <https://www.npmjs.com/signup>`__ or create an account from the
  667. command line by running ``npm adduser`` and entering values when
  668. prompted. Create an account now if you do not already have one. If you
  669. already have an account, login by running ``npm login`` and answering
  670. the prompts.
  671. Next, open the project ``package.json`` file in your text editor. Prefix
  672. the ``name`` field value with ``@your-npm-username>/`` so that the
  673. entire field reads ``"name": "@your-npm-username/jupyterlab_apod"`` where
  674. you've replaced the string ``your-npm-username`` with your real
  675. username. Review the homepage, repository, license, and `other supported
  676. package.json <https://docs.npmjs.com/files/package.json>`__ fields while
  677. you have the file open. Then open the ``README.md`` file and adjust the
  678. command in the *Installation* section so that it includes the full,
  679. username-prefixed package name you just included in the ``package.json``
  680. file. For example:
  681. .. code:: bash
  682. jupyter labextension install @your-npm-username/jupyterlab_apod
  683. Return to your terminal window and make one more git commit:
  684. .. code:: bash
  685. git add .
  686. git commit -m 'Prepare to publish package'
  687. Now run the following command to publish your package:
  688. .. code:: bash
  689. npm publish --access=public
  690. Check that your package appears on the npm website. You can either
  691. search for it from the homepage or visit
  692. ``https://www.npmjs.com/package/@your-username/jupyterlab_apod``
  693. directly. If it doesn't appear, make sure you've updated the package
  694. name properly in the ``package.json`` and run the npm command correctly.
  695. Compare your work with the state of the reference project at the
  696. `06-prepare-to-publish
  697. tag <https://github.com/jupyterlab/jupyterlab_apod/tree/1.0-06-prepare-to-publish>`__
  698. for further debugging.
  699. You can now try installing your extension as a user would. Open a new
  700. terminal and run the following commands, again substituting your npm
  701. username where appropriate
  702. (make sure to stop the existing ``jupyter lab --watch`` command first):
  703. .. code:: bash
  704. conda create -n jupyterlab-apod jupyterlab nodejs
  705. conda activate jupyterlab-apod
  706. jupyter labextension install @your-npm-username/jupyterlab_apod
  707. jupyter lab
  708. You should see a fresh JupyterLab browser tab appear. When it does,
  709. execute the *Random Astronomy Picture* command to prove that your extension
  710. works when installed from npm.
  711. Learn more
  712. ~~~~~~~~~~
  713. You've completed the tutorial. Nicely done! If you want to keep
  714. learning, here are some suggestions about what to try next:
  715. - Add the image description that comes in the API response to the panel.
  716. - Assign a default hotkey to the *Random Astronomy Picture* command.
  717. - Make the image a link to the picture on the NASA website (URLs are of the form ``https://apod.nasa.gov/apod/apYYMMDD.html``).
  718. - Make the image title and description update after the image loads so that the picture and description are always synced.
  719. - Give users the ability to pin pictures in separate, permanent panels.
  720. - Add a setting for the user to put in their `API key <https://api.nasa.gov/api.html#authentication>`__ so they can make many more requests per hour than the demo key allows.
  721. - Push your extension git repository to GitHub.
  722. - Learn how to write :ref:`other kinds of extensions <developer_extensions>`.