• Packages
  • Themes
  • Documentation
  • Blog
  • Discuss
Subscribe
  • Docks Deep Dive

    May 23, 2017 matthewwithanm matthewwithanm

    Docks graphic

    This is a guest post written by Facebook’s Nuclide team member @matthewwithanm. He tells the story how the new docks got introduced to Atom and how package authors can make great use of them.

    One of the things that the Nuclide team has always really loved about Atom is how it lets us extend and experiment with UI. Tools like Outline View, Console, Diagnostics, and the Debugger all need custom UI and, up until recently, their natural home was Atom’s Panels. Located at the edges of the window, panels are a great place for these kind of graphical tools but they have a couple of issues.

    Read more
  • Git and GitHub Integration comes to Atom

    May 16, 2017 BinaryMuse BinaryMuse

    Introducing the GitHub Package

    A text editor is at the core of the developer’s toolbox, but many other useful pieces of software coexist along with it, such as Git and GitHub. Starting today, Atom adds Git and GitHub integration directly in Atom via the GitHub package. This is a new core package included with Atom and is available right now in today’s 1.18 beta release. Be sure to check out github.atom.io for more information!

    Read more
  • Atom 1.17

    May 16, 2017 iolsen iolsen

    Atom 1.17

    Today’s Atom 1.17 release comes with the introduction of docks, faster startup time with V8 snapshots, farewell to jQuery and other improvements.

    Read more
  • Improving Startup Time

    April 18, 2017 as-cii as-cii

    Over the last months, the Atom team has been working hard on improving one of the aspects of the editor our users care about the most: startup time. We will first provide the reader with some background about why reducing startup time is a non-trivial task, then illustrate the optimizations we have shipped in Atom 1.17 (currently in beta) and, finally, describe what other improvements to expect in the future.

    Startup Time Illustration

    Read more
  • Atom 1.16

    April 12, 2017 andreagriffiths11 andreagriffiths11

    Atom 1.16

    Today’s Atom 1.16 release comes with two more macOS title bar options, a push to remove jQuery and other improvements.

    Read more
  • Atom 1.15

    March 9, 2017 andreagriffiths11 andreagriffiths11

    Atom 1.15

    It was a quiet month because most of the team is toiling away on cool stuff that’s not yet shipping. But we do have a few goodies hitting Atom 1.15.

    Read more
  • Atom 1.14

    February 8, 2017 iolsen iolsen

    Atom 1.14

    Atom 1.14 has shipped today with improved large file performance, a 64-bit Windows installation, improved MRU tab traversal, and more.

    Read more
  • Atom on Windows

    January 18, 2017 damieng damieng

    Last year I joined the Atom team with the goal of making Atom a better experience on Windows and thought it would be worth highlighting some of our work so far as well as a few of the things new in Atom 1.14 (currently in beta).

    If you haven’t tried Atom on Windows in a while or were just plain heads-down on your projects here’s some Windows-specific improvements you may have missed.

    Read more
  • Atom 1.13

    January 10, 2017 iolsen iolsen

    Atom 1.13

    Atom 1.13 has shipped today with benchmarks, reopen project, new Octicons and a keystroke resolver API. It ships without the Shadow DOM editor boundary.

    Read more
  • Removing Shadow DOM boundaries from text editor elements

    November 14, 2016 as-cii as-cii

    We recently released Atom 1.13 Beta and it features a foundational change to the editor rendering internals that we would like to share with you: the removal of the Shadow DOM boundary from <atom-text-editor> elements. In this blog post we are going to shed some light on the reasons that drove its introduction, as well as why we eventually decided to transition away from it and employ a different technique instead.

    Shadow DOM

    Read more
← Previous 1 2 3 4 5 6 7 8 9 10 Next → Archive
  • Terms of Use
  • Releases
  • FAQ
  • Contact
with by