If you’ve found an error, spotted something missing, or feel a section could be clearer or better explained, we’d love to hear from you. Your feedback helps keep the documentation accurate and useful for everyone.
Please report issues or suggest improvements on GitHub. Community input is invaluable in making the docs stronger.
Not comfortable with GitHub? No problem — you can also get in touch with us directly via our contact form. We welcome all feedback.
Regarding View File Syntax
In Trongate MX, there are two main ways to create form elements and other HTML content. This section will guide you through both approaches:
- Using Trongate's Form Helper Functions
- Writing Plain HTML
Let's explore both approaches.
1) Using Trongate's Form Helper Functions
Trongate's form helper functions provide a clean and consistent way to generate HTML elements. These functions are designed to streamline your code and ensure it follows best practices.
For example, here's how to create a form button using Trongate's form_button() form helper:
This generates the following HTML:
Now, let's look at how to add attributes to create more complex elements. This can be achieved by passing in an array of key-value pairs. For example, a button that triggers an API call (with Trongate MX) could be rendered using the following syntax:
This generates the following HTML:
When using form helpers like form_button(), certain attributes, such as the 'name' attribute, are rendered by default. However, not all of these attributes are essential for Trongate MX to function properly.
2) Writing Pure HTML
While Trongate's form helpers are recommended, you can still write pure HTML for form elements, if you prefer. Here's an alternative syntax the produces the same result as the example shown above:
Both approaches are fully supported and will function correctly with Trongate MX.
The Pros And Cons Of These Approaches
The choice between using form helpers or writing plain HTML is entirely up to you. Both methods will work seamlessly with Trongate MX.
Pros
- Consistent code structure across your application.
- Built-in security features and sanitization.
- Shorter, more readable code in complex scenarios.
Cons
- Requires learning the helper function syntax.
- Slightly more typing required for very simple elements.
- May generate additional attributes you don't need.
Pros
- Complete control over the output HTML.
- No learning curve for developers familiar with HTML.
- Familiar syntax for developers experienced with libraries like HTMX.
Cons
- No built-in security features.
- May require excessive code for complex forms.
Regardless of the method you choose, Trongate MX's attributes (such as mx-get, mx-target, etc.) will function the same way in both scenarios. The underlying functionality remains consistent.