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 detailand gathering reports on blender startup
--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
There is not much more to report. Getting through drawing code is challenging.
uiii … thats sexy!
#if 0 # include "PIL_time_utildefines.h" #else # define TIMEIT_BENCH(expr, id) (expr) #endif
This week I focused on completing UX design, I made technical layout of desired functionalities, you can find it here: GSoC 2020: Info Editor Improvements - Discussion and Suggestions (logs, reports & friends)
I encounter some complicated problems like:
MEM_set_memory_debug(), what was completely missed in existing api
bpy.app.debugand I also missed it. In some cases debug is checked only during init (like GHOST) and it does not matter what you do with this flag afterwards…
/windowmanager is now completely converted to logs. Now i am going through
/bmesh. I spend some time there to solve some more complicated log-cases.
blender --debug --log-severity 0 --log-level -1 --log "wm.session,wm.operators,bke.report". You can later adjust them in preferences
add copy operators (remember you can use quick favorites in info editor):
next week to come (maybe not all):
– log operators: mute selected log types, function, …
– polishing (debug features in user preferences, report drawing, various todo’s left in code …)
– I will investigate autoscroll options
– logs can change during selecting and you end up selecting sth different
– auto refresh logs
– search in logs uses only log message…
– log syntax highlighting would be nice…
– highlighting found text would be nice…
glog) and integrate them into Info Editor. I will do make design, but it will not make it into this gsoc. I will post later on discussion thread.