-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[ui] Python Script Editor Improvements #2587
Conversation
horizontalAlignment: Text.AlignHCenter | ||
Layout.fillWidth: true | ||
} | ||
MSplitView { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This needs to be discussed but I wonder if it wouldn't be better to have the split view be horizontal instead of vertical... As such, it's is pretty much unusable unless we expand the Script Editor's tab, which may not be ideal.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your feedback @cbentejac, I do agree with how the widgets are placed in Meshroom at the moment, the best layout is a RowLayout.
Have reverted back in terms of Layout and I guess we can keep it till the time we have a better location/placement of Script Editor.
2bd93ff
to
52b52b8
Compare
52b52b8
to
dd40d93
Compare
Thanks for the suggestions @yann-lty |
dd40d93
to
d0ecb8a
Compare
…xceptions ScriptEditorManager now also allows the code to be saved and retrieved back. Exceptions are now shown with a better output to the user.
ScriptEditor is now part of a ColumnLayout in an MSplitView allowing more control over what is being viewed.
Python syntax within the script editor is now highlighted making it easier to understand and write smaller code in it.
A Row Layout is more practical for using script editor with the current placement of meshroom GUI.
Updated Icons for ScriptEditor Script Editor shows a confirmation dialog before clearing history
d0ecb8a
to
49052df
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## develop #2587 +/- ##
========================================
Coverage 69.93% 69.93%
========================================
Files 121 121
Lines 7088 7088
========================================
Hits 4957 4957
Misses 2131 2131 ☔ View full report in Codecov by Sentry. |
*/ | ||
|
||
// Replace the text to be RichText Supportive | ||
return "<font color=#49a1f3>" + "Result: " + replace(text, "\n", "<br>") + "</font><br><br>" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
return "<font color=#49a1f3>" + "Result: " + replace(text, "\n", "<br>") + "</font><br><br>" | |
return "<font color=#49a1f3>> Result:<br>" + replace(text, "\n", "<br>") + "</font><br>" |
*/ | ||
|
||
// Replace the text to be RichText Supportive | ||
return "<font color=#868686>" + replace(text, "\n", "<br>") + "</font><br><br>" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
return "<font color=#868686>" + replace(text, "\n", "<br>") + "</font><br><br>" | |
return "<font color=#868686>>Input:<br>" + replace(text, "\n", "<br>") + "</font><br>" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
…flickables Formatted the input and output text for output display text area
On execution, we should scroll the output to the end. |
Could it be a SplitView between the Editor and the Output. |
Maybe also disable the button if there is no action to perform on the "Get Previous/Next Script". |
The first click on "Get Previous Script" is not working. You need to click a second time to do the action. |
…of scripts hasPreviousScript and hasNextScript are getters for history if that is available
It feels like that actually, but it is actually working, Then I executed but I would not notice any difference because my current text in script editor input is still I think in the first version of script editor we used to clear the input as soon as it was executed so this made it work as expected but now that we're not clearing the script contents, it feels like this is not working.... |
It would be good to scroll the output to the end on execution. |
It looks surprising to me that clearing the history is not only clearing the history but also the current code in the script editor. But if I close and re-open Meshroom, this code is back magically (so the history has not been fully cleared). If we do not remove the current code, then it would be fine to have it when you close and re-open. |
Layout.fillHeight: true | ||
width: root.width | ||
MSplitView { | ||
id: scriptSplitView; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think we do not put the extra ";" in general.
Description
ScriptEditor Improvements
Features list