Skip to main content

Documentation Index

Fetch the complete documentation index at: https://mintlify.com/Viruz7w7/thunderRAR/llms.txt

Use this file to discover all available pages before exploring further.

The main menu is the central dashboard of ThunderRAR and the screen employees land on after a successful login. It is implemented by Activity_menu and launched from MainActivity when the entered credentials match the registered ones. The screen presents four business modules arranged in a 2×2 grid, each represented by an icon button and a label. All modules are currently stubbed and are planned for a future release.

Comunidad

The community module is intended for employee communication and collaboration features. This module is planned for a future update.

Venta

The sales module will handle product listings, pricing, and transaction management. This module is planned for a future update.

Logistica

The logistics module will cover delivery tracking, inventory movement, and supply chain operations. This module is planned for a future update.

Reporte

The reports module will provide business analytics, summaries, and exportable data views. This module is planned for a future update.
All four modules are stubbed for a future release. Tapping any module button currently displays the informational Toast message “para la siguiente actualizacion” and performs no further action.

Module Handler Methods

Each ImageButton in the menu grid declares its corresponding handler method via android:onClick. All four methods in Activity_menu follow the same pattern: they display a short Toast and return. No navigation or business logic is executed yet.
Activity_menu.java
public void men_venta(View view) {
    Toast.makeText(this, "para la siguiente actualizacion",
        Toast.LENGTH_SHORT).show();
}
public void men_comunidad(View view) {
    Toast.makeText(this, "para la siguiente actualizacion",
        Toast.LENGTH_SHORT).show();
}
public void men_logistica(View view) {
    Toast.makeText(this, "para la siguiente actualizacion",
        Toast.LENGTH_SHORT).show();
}
public void men_reporte(View view) {
    Toast.makeText(this, "para la siguiente actualizacion",
        Toast.LENGTH_SHORT).show();
}
The handler-to-button mapping is as follows:
HandlerButton IDModule
men_comunidadimageButton2Comunidad
men_ventaimageButton3Venta
men_logisticaimageButton4Logistica
men_reporteimageButton5Reporte

Layout

The screen uses a ConstraintLayout root with a full-bleed background image (fondo_pantalla_menu_prueba). Inside it, a TableLayout (372 dp × 546 dp) structures the grid as four TableRow entries:
  • Row 1ImageButton for Comunidad, a 100 dp Space separator, ImageButton for Venta.
  • Row 2TextView label “Comunidad”, a 100 dp Space separator, TextView label “Venta”.
  • Spacer — An 80 dp tall Space row creates vertical breathing room between the two module pairs.
  • Row 3ImageButton for Logistica, a 100 dp Space separator, ImageButton for Reporte.
  • Row 4TextView label “Logistica”, a 100 dp Space separator, TextView label “Reporte”.
Each ImageButton has a fully transparent background tint so only the icon graphic is visible against the background image — imageButton2 uses #00FBFBFB while imageButton3, imageButton4, and imageButton5 use #00FFFFFF. Labels are rendered in black at 20 sp with centre gravity.

Build docs developers (and LLMs) love