extension_tutorial.rst 34 KB

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