nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Improved search in the model browser

medini_1024120963

Status : feature requested Priority : Minor, #18 Schedule : (according to Project Owner) Current state : You can search in the model browser with an eclipse standard functionality Critisism on current state :usability is difficult if you have 3k+Elements Objective of the change : efficient workflow Proposed change : Improve the search in the model browser Original Author : Peter Ploß searching for objects in medini is currently not streamlined; looking for example an element type with the ID "635-02107-xx" can be done by entering it into the Model Browser's filter, but has several draw backs: - it is slow - it hides the rest of the model - upon clearing the filter, the open models are uncollapsed for all locations, where a matching entry was found (why not restore the previous view?) searching using the search dialog works ok, but is a lot of clicking effort proposal: introduce a "goto" dialog that is basically the same modal dialog "select artifacts" used to make a reference to a related artifact in a checklist editor. current workaround: use a "search" checklist to efficiently filter for the object under examination 2019-12-11 PP with ANSYS: accepted as feature request a parent node: Search, line 91"

Find more posts tagged with

medini

medini legacy

Accepted answers

medini_1024120963

This also relates with this ticket: https://medini.freshdesk.com/discussions/topics/1000095538 Ticket Number #9429

All comments

medini_1036016653

Related to this issue: - First search: select a project - Second search: again the checkbox has "all projects selected" Proposed behavior: Keep last selected scope: Furthermore, once a search finishes (not including what I wanted to search for), directly again invoking the search window results in the lower bullet point being disabled, as the search window does not qualify as belonging to the current project. As a workaround one has to remember that inconvinience and first select again some item of the model browser, to make medini aware, which the current project is (tedious!):

medini_1024120963

This also relates with this ticket: https://medini.freshdesk.com/discussions/topics/1000095538 Ticket Number #9429

medini_1036016653

Was progress made on this topic?

medini_1024169437

Hi Peter, we in the Po team decided more or less replace the current search feature completely by a more google like search. Means the tool is indexing the project in the background into a database optimized for search and a simple search app can be sued to query for any text. In best case that reduces the search to two clicks only. If you have tested 21.1: it most likely will look and behave similar to the EPRD/NPRD application. Jan

medini_1036016653

Hi Jan, thank you for the update. v21.1 is not available to me (as far as I know). I'm looking forward to this improvement. I'll gladly give it a try, if you make a test version available to me. Best regards Peter

medini_1036016653

Please check, if the referenced ticket https://medini.freshdesk.com/support/discussions/topics/1000095538 is also improved with the newly proposed search. Filtering in medini currently is not very performant :-)

medini_1024169437

Hi Peter, that was maybe a misunderstanding, the feature is not yet in 21.1, but there is a similar feature that offers a search app for failure rates of mechanichal compoennts and we wanted to build a similar app for search. We are working on the app but its rather something for 21.1. Once we have an alpha version, we will of course pass it down to you to get your feedback. The search in the model browser is somewhat limited by eclipse and the approach of asynchronously expanding the tree and searching for matching nodes, its a rather "dead end" for performance improvements I'm afraid. However, we can work at least get this "do not search by each character" (there is already some delay for characters I think). Jan

medini_1024169437

Hi Peter, we found a way to improve the tree search to allow users to search by word, not character without the need to patch any eclipse code. We basically injected some delay so that the user has the chance to enter further characters, once he stops for a certain time (currently 400ms) the filtering starts as before. I personally think the feature works but I got mixed emotions from some testers. So at some point in time it would be good to get your feedback as well. Regards Jan

medini_1036016653

Hi Jan, sure, I can give it a go. Personally I feel, even apart from the "search initiating condition" (timeout after character), the search itself is really too slow. If you want to see it behaving in one of my workspaces, we can set up a very short meeting so you can experience it yourself. Related to this, deleting a filter has the not nice side-effect that the previous view of the model browser is lost (model tree expansion, scroll location, selection, etc.). Recently I showed "Sublime Text"'s "command palette" to Krasimira. It also has a "goto anything" feature, which I personally love for quickly navigate in my files, ref. https://www.thisprogrammingthing.com/maximizing-your-efficiency-in-sublime-text/goto-anything/ . It would be lovely to have a workflow/functionality in medini where a "ctrl+p" opens an interactive view - like the view that allows to select related artifacts in the checklist editor - where you can start typing and then select one ore more of the remaining entries. After confirming with enter, those elements are selected in model browser. (I'm rather positive that I had raised that as a feature request before.) Hopefully, my explanation makes sense. Best regards Peter

medini_1036016653

sorry to spam -- my proposal from five minutes ago is described in the inital post. I've never heard back on that seemingly accepted feature request: proposal: introduce a "goto" dialog that is basically the same modal dialog "select artifacts" used to make a reference to a related artifact in a checklist editor. current workaround: use a "search" checklist to efficiently filter for the object under examination

medini_1024169437

Hi Peter, es wird ein wenig unübersichtlich, daher versuch ich mal das zu ordnen bzw. nochmal die einzelnen Punkte zu klären. Davor sei aber gesagt, dass diese "Filterfunktion für Bäume" eine Eclipse Komponente ist, die wir benutzen und die schwer "veränderbar ist". Im Eclipse ist dieser Text Filter auch bei großen Bäumen (wahrschinlich mit Intention) nicht vorhanden, wir haben den damals in den Model Browser dennoch eingebaut. "search initiation": hier haben wir einen Weg gefundn das zu verbessern, wie gesagt, ein wenig fine tuning wäre notwendig "search performance": das ist ein inhärentes Problem dieser Funktion, die ansychon über den Baum läuft und permanent den Baum ausklappt, einklappt usw. das müssten wir komplett selber re-implementieren, ich denke da schalten wir die Funktion eher ab "search reset": das ist in der Tat noch ein Punkt, den wir vielleicht tweaken können, gute Idee. Wir schauen uns das mal an. Idee wäre, dass die Selektion bestehen bleibt, verstehe "go to": zunächst dachte ich, das wäre unser "go into" feature, aber nun verstehe ich das besser, eine Art "suche außerhalb des browsers um dann die gefundenen Elemente im Browser anzuzeigen". Das ginge recht einfach denke ich, allerdings ist (1) die Suche dann dort nicht schneller und (2) wäre das mit unser neuen "google like" Suche obsolete. Da fällt mir ein, dass man das auch mit einem Script lösen könnte, ich werde das mal versuchen und im Forum anbieten

medini_1036016653

Hi Jan, * "search initiation": ok * "search performance": ok * "search reset": ok * "go to": "go into" kenne ich nicht; guter Punkt mit dem Skript: Man kann ja auch ein UI fenster öffnen und die verbliebenen Einträge könnte man ja dann als selection setzten. Hakelig ist lediglich der Aufruf des Skripts. Ich fände es ja toll, wenn man Skripte mit einem Shortcut belegen könnte oder aber mit einem Icon in der Leiste oben ablegen kann. (MATLAB erlaubt beides. Falls Du das nicht kennst, kann ich mal schauen ob das kostenlose octave das nachgebaut hat. ref. https://de.mathworks.com/matlabcentral/fileexchange/14140-explorer-toolbar-shortcut)

medini_1024169437

Ja genau meine Idee, schau mal ins Scripting Forum, habe ein erste Version dort abgelegt, Start ist natürlich hekelig, das stimmt. Man kann Scripte auch isn menu packane und sogar mit einem Shortcut versehen, das wäre aber nur über ein eclipse plugin möglich. "Go Into" ist das Feature im browser, mit dem du den Scope einschränken kannst. Die Suche ist das reduziert und schneller, wird aber nichts gefundne, löst er den Scope auf:

medini_1036016653

Danke Jan, das Skript probiere ich gleich mal aus und gebe im Forum Feedback. Dieses "go into" um den Scope auf eine Sub-Ebene zu setzten kenne ich -- nur beim Begriff hat es vorhin nicht "klick" gemacht. Über welches "eclipse plugin" könnte man solche Shortcuts realisieren? Könntest Du/jemand dazu bitte einen knowledge base-Artikel verfassen? Danke!

medini_1024169437

Das wäre ein komplett eigenes plugin, in dem im einfachsten Fall nur ein xml File und das Script liegt. Grüße Jan

medini_1024169437

Hallo Peter, hier ein Beispiel,wie man das Script in ein Plugin verpackt und es (1) zum Context Menu, (2) zur Toolbar und (3) zu einem keycode bindet (im beispiel F7). Ich habe das mit Absicht nicht ins Forum gepackt, da das kein offizielles Feature ist. Grüße Jan

medini_1036016653

Hi Jan,
finally I tested your example plugin. It works as advertised. Here my notes on how to get going:
How to install script.custom_1.0.0.202011231112.jar
edit "C:\Program Files\ANSYS Germany GmbH\medini analyze 2020 R2\Program\mediniAnalyze.ini"
the line after "-noverify" has to read "-Dosgi.framework.extensions=javax.xml,org.apache.xml.serializer,org.apache.xml.resolver,org.apache.xerces,script.custom"

place the "script.custom*.jar" in C:\Program Files\ANSYS Germany GmbH\medini analyze 2020 R2\Program\plugins
Result
Press icon or "F7" to call script. In this case selectAnything.js which is bundled in the plugin.
Is there also a way to do the installation without necessity of admin rights (changes in the programs folder)?
Thank you!
Best regards
Peter

medini_1036016653

now screenshot attached

medini_1024169437

Hi Peter, thanks for testing. There is currently no way to install bundles outside of the plugins folder of the installation, so if that was installed with admin rights, you need that too. With 21.1.1 resp. 21.2 there will be a way t do it "by user" and outside of the installation folder. Jan