May (in general):
- searching thru code and woking on design Project Details
May (in general):
soc-2020-info-editor, details in commit messages (in future I will document changes in phabricator, I am still learning though) D7950
In principle I agree, there should be a way to share logic. However I see this as a much bigger project than what can be handled as part of this GSoC project.
We have multiple use-cases for text editing: Text editor, console, text widget (hopefully multi-line soon), 3D text object edit mode, the VSE team was recently looking into a way to edit text strips within the preview region, etc. For all these a decent experience is needed, with all the expected cursor navigation (arrow keys, modifier + arrow keys, home key, etc), select-navigation, shortcuts (e.g.
Ctrl+A to select all), copy/paste, … And in some cases you’d want syntax highlighting, line-wrapping and I think some basic rich text editing features and spell checking are also something we might want soon.
Point is, yes we should unify this somehow. But I think this should be done “the right way” from the get-go, with a careful design that allows all these things. My idea is to have a reusable text editing widget at the core that manages all or most of this, with options and/or variants to extend it further.
My suggestion is that you keep the focus on your project. It’s easy to get side tracked by things like this, so that you end up delivering too little.
Thank for summary.
That was also my conclusion, it is too big for this project. I was mainly looking if there is (easy) way to get syntax highlighting in info editor.
The Info Editor uses some icons to represent different classes of reports. Many of those icons were just selected from what was already available by some amateur without much thought really. So if you want anything different, or better, or just something else, post a quick note on this thread and something new will magically appear for you.
Unfortunately I could not work on blender this week as I prioritized studies (this is final week of studies, exams). Due to pandemic this is very disorganised both from my and my teacher’s perspective.
And here is your eye candy:
look in console for detail(UX nighmare). I think I have solution (although review will be needed)
--log-levelcontrols info level, severity warn and error will always show if logger is on, now:
--log-verbosityfor level of detail in severity verbose
G_DEBUG_WMhas now almost now uses in code, completely replaced by logs
G_DEBUG_JOBSis completely replaced by logs