Closed bsteubing closed 5 years ago
Where would you put the navigation buttons? If you plan on putting them in the toolbar, we can close #81 . Otherwise I'd like to hear your opinion on the necessity of the toolbar.
please see my answer in #81
Bernhard's answer in #81 with additional ideas for the toolbar. #81 was closed in favour of this issue:
I think the toolbar still has a value and could feature other things. The original version of the AB had a number of functions there, see here:
From left to right:
- search
- search by brightway key
- random activity
- history (tab could appear once the user presses this button)
- back and forwards buttons for "activity BROWSER" type navigation
- edit activity
- calculate LCA results (with functional unit and LCIA method as defined in LCIA tab)
Further, from the modular LCA extension:
- new module
- save module
- open modular LCA database
- add database
- save database
- close database
Graphing:
- show module as graph (type defined in drop-down menu)
- show modular system (several connected modules)
Similar buttons could be used to display a supply chain graph relating to the current activity.
btw: although the current search function using woosh is advanced, having a second search field to search within search results was really useful in the original version to quickly find desired activities...
I think with the recent advancements we can drop this for now.
Forward-backward buttons to re-implement the "Activity Browser" experience The original version of the AB had nice buttons to navigate through the browsing history very quickly. This idea originally inspired the name Activity Browser - to quickly explore LCA data.
Link- (or key) based navigation Each activity in brightway has a key. In addition to the search function, this key provides an alternative way to directly accessing an activity - by providing the link so to speak (the key). This was already present in the original AB and should be re-implemented. Also as the AB is a tool to work smoothly together with brightway2.