Design

[davidlatwe]

• Python 3.7+
• Qt5

Things that need to be implemented :

Package Family listing widget ⭐⭐⭐

Listing package from package paths.

At first, I was thinking that maybe I could make this multi-threaded, one thread per package path to lookup packages. But then I thought, that might be overkilled. Maybe simply caching search result into one JSON file for next run would do the job, and when user selecting a package (family), do a quick health check to update latest status of that package. Scan duration and timestamp should be logged.

For interface, I was thinking flippable card-based design, but that's.. too fancy and hard, so an old-school Address Book style it is. That's for browsing packages, still need one other tab for searching and viewing search result. Fuzzy search might be needed.

This widget could be able to register custom menu action to act on selected package, like for, open vcs link, viewing package/variation with custom viewer, open dir where that package has been auth/built from, send selected package to suite editing page/widget, etc.

Other then search by package name, maybe we could search by tool name, or even search by any column, or, package requests.

Package info view widget ⭐

Might need a widget for viewing one package family, across versions/variants. Not sure.

Suite editing page ⭐⭐⭐

One editing panel should be enough, no need tabs for editing multiple suites in one widget I think.

It should be able to:

• Save suite, of course
• Open old suite, edit and save
• Import old suite, edit and save as another suite
• Making template suite
• Editing tool names
• Detect and fix conflicted tools
• Resolved context/environment viewer (sys path excluded ?)
• Testing tools accessibility, e.g. using command which

.. to be continued