You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am creating this thread to track multiple discussions with multiple people on the topic.
We are adding more and more file readers and as a result the dropdown list of the widgets gets super long.
To me it seems the best way would be to solve this problem is making a dedicated python module for each instrument manufacturer's readers and then just add that in the Quasar source code. This would enable people to use the readers in other codes that are not based on Orange or Quasar.
This still doesn't handle generic file extensions such as csv or txt, but there we could try the meta readers or going through all specialized readers to see if they can handle that specific file format.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
I am creating this thread to track multiple discussions with multiple people on the topic.
We are adding more and more file readers and as a result the dropdown list of the widgets gets super long.
To me it seems the best way would be to solve this problem is making a dedicated python module for each instrument manufacturer's readers and then just add that in the Quasar source code. This would enable people to use the readers in other codes that are not based on Orange or Quasar.
This still doesn't handle generic file extensions such as
csvortxt, but there we could try the meta readers or going through all specialized readers to see if they can handle that specific file format.Thoughts?
Beta Was this translation helpful? Give feedback.
All reactions