มุมมอง แม่แบบ และพื้นฐาน LiveView

Web applications aren't static! You need ways to display changing data, like user profiles or product lists. This is where views and templates come in.

They work together to transform raw data from your application into the beautiful HTML that users see in their browsers.

In Phoenix, a View is an Elixir module responsible for preparing data before it's rendered into a template. Think of it as a middleman between your controller and the final HTML.

Views can:

• Format dates or numbers.
• Create dynamic links or URLs.
• Transform complex data structures into simpler ones for display.

Templates are files (often with a .eex extension or using the ~H sigil) that combine standard HTML with embedded Elixir code. Elixir's templating engine, EEx (Embedded Elixir), allows you to inject dynamic content.

• <%= expression %>: Evaluates an Elixir expression and outputs its result directly into the HTML.
• <% expression %>: Evaluates an Elixir expression but does NOT output its result. Useful for control flow like loops or conditionals.

Here's a simplified look at how Phoenix renders a page:

1. A Controller action receives an HTTP request.
2. The Controller calls render/3 (e.g., render(conn, "index.html", assigns)), passing data as 'assigns'.
3. The corresponding View module (e.g., PageView) receives these assigns and can apply helper functions.
4. The Template file (e.g., index.html.eex) uses the prepared assigns to generate the final HTML.
5. This HTML is then sent back to the user's browser.

Let's see how EEx processes dynamic data. This Elixir script simulates a template rendering a value passed to it.

Imagine building highly interactive web interfaces without writing a single line of JavaScript. That's the magic of Phoenix LiveView!

LiveView allows you to render dynamic, real-time user interfaces entirely on the server, using WebSockets for communication. It brings the power of server-side Elixir directly to your frontend interactions.

Every Phoenix LiveView module typically defines at least two key functions:

• mount/3: This function is called when the LiveView is first initialized. It's used to set up the initial state (known as 'assigns') of your LiveView.
• render/1: Takes the current assigns and returns a special HEEx template (using the ~H sigil) to generate the HTML. This function is called automatically whenever the LiveView's state changes.

LiveView handles user events (like clicks or form submissions) by sending messages over the WebSocket back to the server. You attach special phx- attributes to your HTML elements to trigger these events.

• phx-click="event_name": Triggers a server-side event when the element is clicked.
• handle_event/3: A callback function in your LiveView module that receives and processes these events, updating the LiveView's state (assigns).

Here's a simplified look at a LiveView that implements a basic counter. Notice how handle_event updates the @count assign, which automatically re-renders the template.

In Phoenix, what is the primary purpose of a View module?

You've learned how Phoenix uses Views to prepare data and Templates (EEx/HEEx) to render dynamic HTML. We also introduced Phoenix LiveView, a powerful tool for building interactive UIs with Elixir, minimizing the need for client-side JavaScript.

Understanding these components is key to building dynamic and engaging web applications with Phoenix. Next, you might explore more advanced LiveView features or dive into data persistence with Ecto!