0Pricing
Electron Desktop App Development · Pelajaran

Mengelola Peristiwa Siklus Hidup Aplikasi

Tangani berbagai peristiwa siklus hidup aplikasi seperti `ready`, `window-all-closed`, `activate`, dan `quit` untuk memastikan perilaku aplikasi yang semestinya.

Mengelola Peristiwa Siklus Hidup Aplikasi adalah pelajaran Electron Desktop App Development gratis di CoddyKit. Ini adalah pelajaran 1 dari 4. Kamu bisa membaca pelajaran lengkapnya di bawah secara gratis — lalu praktikkan langsung di browser dengan editor kode bawaan dan tutor AI 24/7. Ini adalah bagian dari jalur belajar Electron Desktop App Development, dan progresmu tersinkronisasi di web dan aplikasi CoddyKit. Kursus Electron Desktop App Development mencakup 4 pelajaran total.

Bagian dari pelajaran ini belum diterjemahkan dan ditampilkan dalam bahasa Inggris.

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!

Pertanyaan yang Sering Diajukan

Apakah pelajaran “Mengelola Peristiwa Siklus Hidup Aplikasi” gratis?

Ya — teks lengkap “Mengelola Peristiwa Siklus Hidup Aplikasi” gratis dibaca di sini di web. Untuk praktiknya secara interaktif (editor kode bawaan dan tutor AI 24/7) dan buka sisa kursus Electron Desktop App Development, upgrade ke CoddyKit PRO. Kursus Electron Desktop App Development mencakup 4 pelajaran total.

Apa yang akan aku pelajari di “Mengelola Peristiwa Siklus Hidup Aplikasi”?

Tangani berbagai peristiwa siklus hidup aplikasi seperti `ready`, `window-all-closed`, `activate`, dan `quit` untuk memastikan perilaku aplikasi yang semestinya. Kamu berlatih Electron Desktop App Development dengan kode praktik yang langsung kamu jalankan di browser, dan tutor AI 24/7 menjawab pertanyaanmu saat kamu mengerjakan pelajaran ini.

Apakah aku perlu pengalaman untuk memulai Electron Desktop App Development?

Tidak diperlukan pengalaman sebelumnya. Electron Desktop App Development di CoddyKit dirancang untuk pemula hingga pelajar tingkat lanjut, jadi kamu bisa memulai di sini atau dari awal dan belajar sesuai kecepatan kamu sendiri. Ini adalah pelajaran 1 dari 4.

Berapa lama pelajaran “Mengelola Peristiwa Siklus Hidup Aplikasi” memakan waktu?

Sebagian besar pelajaran CoddyKit memakan waktu sekitar 5–10 menit. Setiap pelajaran ringkas dan interaktif, jadi kamu membuat kemajuan stabil dan melanjutkan dari tempat kamu tinggalkan di web dan aplikasi.

Bisakah aku menulis dan menjalankan kode dalam pelajaran Electron Desktop App Development ini?

Ya. Setiap pelajaran Electron Desktop App Development menyertakan editor kode bawaan, jadi kamu menulis dan menjalankan kode nyata langsung di browser dan mendapatkan umpan balik AI instan — tidak diperlukan penyiapan lokal.

Semua pelajaran dalam kursus ini

  1. Mengelola Peristiwa Siklus Hidup Aplikasi
  2. Penerapan Pembaruan Otomatis
  3. Pelaporan Kerusakan
  4. Tautan Mendalam dan Penangan Protokol
← Kembali ke Electron Desktop App Development