extension_tutorial.rst 34 KB

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