Open ramonfigueiredo opened 2 days ago
Note: The following text will be in a new PR to the opencue.io page with the extra instructions in the CueWeb README.md file.
OpenCue has facilitated efficient management of rendering jobs through its application, CueGUI, which includes Cuetopia and CueCommander. Previously, OpenCue's capabilities were somewhat restricted as it was primarily limited to desktops/workstations running Qt-based applications. Because of that, the CueWeb system was created. CueWeb is a transformative, web-based application that extends access across multiple platforms, ensuring users can manage their rendering tasks from virtually anywhere.
CueWeb replicates the core functionality of CueGUI (Cuetopia and Cuecommander) in a web-accessible format, enhancing usability while maintaining the familiar interface that users appreciate. This adaptation supports essential operations such as:
show-shot-
as the prefix to reduce the number of results returned.Kill
, Eat
, Retry
, Retry dead frames
.Retry
, Eat
, Kill
.Upon logging in through Okta/Google/GitHub or another authentication method configured using NextAuth.js (Figures 1 or 2), users are welcomed by CueWeb’s main dashboard, as shown in Figure 3 (light mode) or Figure 4 (dark mode). The CueWeb main page contains a paginated table that is populated with the OpenCue jobs.
Here’s what you can expect:
Visual modes: Toggle between light and dark mode to suit your viewing preferences.
Customizable jobs tables: Tailor your dashboard by selecting which columns to display, enhancing readability and focus on critical jobs metrics (see Figure 5)
Finished
, Failing
, Dependency
, In Progress
, Paused
- to streamline management tasks (see Figure 6).green
in the dropdown.The CueWeb system includes actions like eat dead frames
, retry dead frames
, pause
, unpause
, and kill
for selected jobs in the table. Also, the ability to right-click jobs, layers, and frames to get a context menu popup with actions for that object type.
Figure 14 shows the job
context menu with options to un-monitor
, pause
, retry dead frames
, eat dead frames
and kill
jobs and Figure 15 shows the successful message after selecting kill
a job.
kill
a jobFigure 16 shows the layer
context menu with options to kill
, eat
, retry
, and retry dead frames
and Figure 17 shows the successful message after selecting retry
a layer.
retry
a layerFinally, Figure 16 shows the layer
context menu with options to kill
, eat
, retry
, and retry dead frames
and Figure 17 shows the successful message after selecting retry
a layer.
eat
a frameIn conclusion, the CueWeb system marks a significant advancement in rendering job management by providing a powerful, web-based interface that simplifies and enhances user interaction with the OpenCue system. With features like customizable job tables, efficient job filtering, and detailed inspections, along with the ability to view comprehensive logs and switch visual modes, CueWeb ensures that managing rendering jobs is more accessible and adaptable to a variety of user needs.
Hi @DiegoTavares and @bcipriano
The CueWeb code is ready for your review and to be merged into the master.
I already did many reviews throughout the year (from April 2024 to November 2024) and it is working fine inside the SPI infrastructure.
Thanks!
FYI ... @marizf888 @tomi-lui @Zach-Fong
FYI ... @tomi-lui @marizf888 @Zach-Fong
Super happy to see CueWeb getting improved and more features being added 😁
CueWeb is a web-based application that brings the core functionality of CueGUI, including Cuetopia and Cuecommander, to a web-accessible format. This initial version includes most Cuetopia features, with Cuecommander integration planned for the next phase. CueWeb simplifies rendering job management with customizable job tables, advanced filtering, detailed inspections, log viewing, and light/dark mode toggling, making it efficient and accessible across platforms. Finally, CueWeb leverages the OpenCue REST Gateway to provide a REST endpoint for seamless interaction with the OpenCue gRPC API.
CueWeb was developed using React.js, Next.js, ShadCN UI, and NextAuth.js for authentications. Authentication Providers in NextAuth.js are services that can be used to sign in to a user.
There are four ways a user can be signed in:
Core features and code changes:
User authentication:
Job management dashboard:
Job search functionality:
Dark mode toggle:
Optimized search and results loading:
Multi-job management:
Actions and context menu
Table auto-reloading:
View frame logs:
Authorization and security:
Unit testing:
Include some CueWeb screenshots examples: https://github.com/AcademySoftwareFoundation/OpenCue/blob/master/cueweb/interface_screenshots
Link the Issue(s) this Pull Request is related to. Create the first version of the CueWeb system: a web-based application that replicates the core functionality of CueGUI: https://github.com/AcademySoftwareFoundation/OpenCue/issues/1595
Co-authored-by: Mariz Fahmy mfahmy@imageworks.com Co-authored-by: Zachary Fong zfong@imageworks.com Co-authored-by: Tomi Lui tlui@imageworks.com Co-authored-by: Ramon Figueiredo rfigueiredo@imageworks.com