0Pricing
Electron Desktop App Development · Aula

Gerenciamento de Eventos do Ciclo de Vida da Aplicação

Lide com diversos eventos do ciclo de vida da aplicação, como `ready`, `window-all-closed`, `activate` e `quit`, para garantir seu funcionamento adequado.

Gerenciamento de Eventos do Ciclo de Vida da Aplicação é uma aula grátis de Electron Desktop App Development no CoddyKit. Esta é a aula 1 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de Electron Desktop App Development, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de Electron Desktop App Development inclui 4 aulas no total.

Partes desta aula ainda não foram traduzidas e aparecem em inglês.

App's Journey: Lifecycle Events

Just like people, software applications have a lifecycle! They start, run, and eventually close. In Electron, these stages are managed through "lifecycle events".

  • These events let your app react to important moments, like when it's ready to show a window or when all its windows are closed.
  • Properly handling them ensures your app behaves predictably and professionally on different operating systems.

Meet the `app` Module

Electron provides a special module called app. This module is the heart of your application's lifecycle management.

  • You use the app module to control your application's events.
  • It allows you to listen for events like when the app is ready, when windows close, or when the app is about to quit.
  • It also provides methods to manage the app, such as quitting or restarting.

App is Ready! The `ready` Event

The ready event is the most fundamental lifecycle event. It fires when Electron has finished initializing and is ready to create browser windows and interact with the system.

You must wait for this event before performing most operations. Try running this simple example:

const { app } = require('electron');

app.on('ready', () => {
  console.log('Electron app is ready!');
  // In a real app, you'd create windows here.
});

// Minimal handler to allow the app to quit when needed
app.on('window-all-closed', () => {
  if (process.platform !== 'darwin') {
    app.quit();
  }
});

Launching Your First Window

The ready event is typically where you create your application's main window. This ensures the Electron environment is fully initialized before the UI appears.

We import BrowserWindow and create an instance, loading simple HTML content directly.

const { app, BrowserWindow } = require('electron');

let mainWindow;

function createWindow () {
  mainWindow = new BrowserWindow({
    width: 400,
    height: 300
  });

  // Load a simple HTML string directly for a self-contained example
  mainWindow.loadURL('data:text/html;charset=utf-8,<h1>Hello Electron!</h1><p>This is your window.</p>');

  mainWindow.on('closed', () => {
    mainWindow = null;
  });
}

app.on('ready', createWindow);

app.on('window-all-closed', () => {
  if (process.platform !== 'darwin') {
    app.quit();
  }
});

Closing All Windows? `window-all-closed`

The window-all-closed event fires when all of your application's windows have been closed. How you respond depends on the operating system.

  • On Windows and Linux, apps usually quit when all windows close.
  • On macOS, apps often stay active in the dock.

This code ensures the app quits on Windows/Linux but stays open on macOS.

const { app, BrowserWindow } = require('electron');

let mainWindow;

function createWindow () {
  mainWindow = new BrowserWindow({
    width: 400,
    height: 300
  });
  mainWindow.loadURL('data:text/html;charset=utf-8,<h1>Close Me!</h1>');
  mainWindow.on('closed', () => {
    mainWindow = null;
  });
}

app.on('ready', createWindow);

app.on('window-all-closed', () => {
  // On macOS, it's common for apps to remain active in the dock
  // until the user quits explicitly with Cmd + Q.
  if (process.platform !== 'darwin') {
    app.quit();
  }
});

Reactivating Your macOS App

The activate event is specific to macOS. It fires when the application is activated, typically when the user clicks on the app's icon in the dock, but no windows are currently open.

This is where you'd re-create a window if mainWindow is null.

const { app, BrowserWindow } = require('electron');

let mainWindow;

function createWindow () {
  mainWindow = new BrowserWindow({
    width: 400,
    height: 300
  });
  mainWindow.loadURL('data:text/html;charset=utf-8,<h1>Activated!</h1><p>A new window was opened.</p>');
  mainWindow.on('closed', () => {
    mainWindow = null;
  });
}

app.on('ready', createWindow);
app.on('window-all-closed', () => {
  if (process.platform !== 'darwin') {
    app.quit();
  }
});

app.on('activate', () => {
  // On macOS, re-create a window when the dock icon is clicked
  // and there are no other windows open.
  if (mainWindow === null) {
    createWindow();
  }
});

Last Chance: `will-quit`

The will-quit event fires just before the application begins to close its windows and quit. This is your last opportunity to perform synchronous cleanup operations.

  • For example, you might save unsaved data or close database connections.
  • This event is emitted before the quit event.
const { app, BrowserWindow } = require('electron');

let mainWindow;

function createWindow () {
  mainWindow = new BrowserWindow({
    width: 400,
    height: 300
  });
  mainWindow.loadURL('data:text/html;charset=utf-8,<h1>Will Quit Demo</h1>');
  mainWindow.on('closed', () => { mainWindow = null; });
}

app.on('ready', createWindow);
app.on('window-all-closed', () => { if (process.platform !== 'darwin') { app.quit(); } });
app.on('activate', () => { if (mainWindow === null) { createWindow(); } });

app.on('will-quit', (event) => {
  console.log('Application is about to quit! Performing final cleanup...');
  // event.preventDefault(); // Uncomment to prevent quitting
  // Perform synchronous cleanup here, e.g., save data.
});

The Final Goodbye: `quit`

The quit event is emitted when the application successfully exits. By this point, all windows have been closed, and the main process is shutting down.

  • This event is primarily for logging or very simple, final notifications.
  • It's generally too late to perform significant cleanup or prevent the app from quitting.
const { app, BrowserWindow } = require('electron');

let mainWindow;

function createWindow () {
  mainWindow = new BrowserWindow({
    width: 400,
    height: 300
  });
  mainWindow.loadURL('data:text/html;charset=utf-8,<h1>Quit Demo</h1>');
  mainWindow.on('closed', () => { mainWindow = null; });
}

app.on('ready', createWindow);
app.on('window-all-closed', () => { if (process.platform !== 'darwin') { app.quit(); } });
app.on('activate', () => { if (mainWindow === null) { createWindow(); } });
app.on('will-quit', () => { console.log('Will quit...'); });

app.on('quit', (event, exitCode) => {
  console.log(`Application has quit with code: ${exitCode}`);
  // This is the very last event.
});

Lifecycle Event Check

You've learned about several key Electron application lifecycle events. Now, let's test your understanding!

Lifecycle Events: Key Takeaways

Great job! You've learned how to manage your Electron application's lifecycle, ensuring it starts, runs, and quits gracefully on different operating systems.

  • The app module is central to event handling.
  • ready is crucial for initialization and window creation.
  • window-all-closed and activate handle window behavior across platforms.
  • will-quit and quit manage the final stages of app termination.

Mastering these events is fundamental for building robust Electron applications. Keep practicing!

Perguntas Frequentes

A aula “Gerenciamento de Eventos do Ciclo de Vida da Aplicação” é grátis?

Sim — o texto completo de “Gerenciamento de Eventos do Ciclo de Vida da Aplicação” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de Electron Desktop App Development, atualize para CoddyKit PRO. O curso de Electron Desktop App Development inclui 4 aulas no total.

O que vou aprender em “Gerenciamento de Eventos do Ciclo de Vida da Aplicação”?

Lide com diversos eventos do ciclo de vida da aplicação, como `ready`, `window-all-closed`, `activate` e `quit`, para garantir seu funcionamento adequado. Você pratica Electron Desktop App Development com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.

Preciso ter experiência prévia para começar Electron Desktop App Development?

Nenhuma experiência prévia é necessária. Electron Desktop App Development no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 1 de 4.

Quanto tempo leva a aula “Gerenciamento de Eventos do Ciclo de Vida da Aplicação”?

A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.

Posso escrever e executar código nesta aula de Electron Desktop App Development?

Sim. Cada aula de Electron Desktop App Development inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.

Todas as aulas deste curso

  1. Gerenciamento de Eventos do Ciclo de Vida da Aplicação
  2. Implementação de Atualizações Automáticas
  3. Relatórios de Falhas
  4. Deep Linking e Manipuladores de Protocolos
← Voltar para Electron Desktop App Development