Bug 277926 - Provide an alternate dependency tree view as project navigator
Summary: Provide an alternate dependency tree view as project navigator
Status: CONFIRMED
Alias: None
Product: KEXI
Classification: Applications
Component: General (show other bugs)
Version: unspecified
Platform: Compiled Sources Linux
: NOR wishlist
Target Milestone: ---
Assignee: Kexi Bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-07-16 22:33 UTC by Dimitrios T Tanis
Modified: 2019-02-18 19:36 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:
staniek: Usability+


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dimitrios T Tanis 2011-07-16 22:33:47 UTC
Version:           2.4 alpha3 (Calligra 2.4 alpha3) (using KDE 4.6.0) 
OS:                Linux

This is an idea to have a more dependency aware view of the database objects.

Reproducible: Didn't try



Expected Results:  
There could be an alternative project navigator. Let's call the current representation Type tree, and a new one called Dependency tree.
In that dependency tree view top level nodes would be all the tables and have as childs the reports and forms that depend on the table. Furthermore, reports and forms would have as childs the script objects that are connected to them.

That would give a very precise representation of UI availability (eg. do I have a form/report for that table?)

Dummy forms/reports (with no datasource) and other script types could be listed at the bottom as a top level node named "undefined"

I believe filling the tree would be somewhat easy to do as it can be done parsing the table names, data source properties and object script properties.

There is a dark spot however regarding queries. Where would they fit in the tree? As tables' childs or better as top level nodes also?
Comment 1 Jarosław Staniek 2011-07-17 22:11:04 UTC
Good ideas!