Blend Algebra and Program icons
IgorB - they are beautiful! I am sure there will be no objections. On Mon, Mar 3, 2025 at 11:04 AM Igor BEGHETTO via Cin < [email protected]> wrote:
(I am sorry, better to re-send in HTML) If you want, I created the icons for the new BlendAlgebra/Progam plugins. If Georgy think they are good,... I put them here to use in Cinelerra-GG. In the compressed file there are ALL of them (square and circle). I put here the two square icons as preview. Thank you.
IgorBeg
blendalgebra.png
blendprogram.png -- Cin mailing list [email protected] https://lists.cinelerra-gg.org/mailman/listinfo/cin
On Mon, 3 Mar 2025, Phyllis Smith via Cin wrote:
If you want, I created the icons for the new BlendAlgebra/Progam plugins.
Yes, I expected, IgorBeg will not miss the opportunity to create beautiful icons! One more detail: for BlendAlgebra several new environment variables were introduced: CIN_EDITOR, CIN_CC, CIN_USERLIB, etc. They are documented in the plugin's section of the manual. Perhaps there is reason to mention these environment variables additionally in the other section, dealing with all the CinGG environment variables. It might even happen that some of them later could be used by some other parts of CinGG software, who knows... _______________________________________________________________________________ Georgy Salnikov NMR Group Novosibirsk Institute of Organic Chemistry Lavrentjeva, 9, 630090 Novosibirsk, Russia Phone +7-383-3307864 Email [email protected] _______________________________________________________________________________
We can put these new variables in the chapter Developer's Section --> Configuaration Features: https://cinelerra-gg.org/download/CinelerraGG_Manual/Configuration_Features.... by adding them in the final part (“Some influential environment variables:”), accompanied by a description similar to: "Introduced with Blend Algebra and Blend program plugins; can be used globally in \CGG{} for new developments." Suggestions on other sections where to mention them and maybe improve their description?
On Tue, 4 Mar 2025, Andrea paz wrote:
We can put these new variables in the chapter Developer's Section --> Configuaration Features:
https://cinelerra-gg.org/download/CinelerraGG_Manual/Configuration_Features....
Andrea, I meant the following section: https://cinelerra-gg.org/download/CinelerraGG_Manual/Environment_Variables_C... with only a brief description. Just because it would be confusing to list one half of variables in one place and another half somewhere far from the first half. _______________________________________________________________________________ Georgy Salnikov NMR Group Novosibirsk Institute of Organic Chemistry Lavrentjeva, 9, 630090 Novosibirsk, Russia Phone +7-383-3307864 Email [email protected] _______________________________________________________________________________
Thank you so much! And thank you for the "CinGG-20250228-alternative_shortcuts.AppImage" version. IgorBeg
I had completely forgotten that section of the manual. :) I attach the Latex @Phyllis; I revised the Latex of the chapter on plugins so that some of the images are repositioned correctly. This should make the pdf easier to read. The html version is not affected. See if that is okay.
Checked into GIT, the BlendAlgebra/BlendProgram environment variables that Georgy added into the Configuration section as latexed by Andrea. As usual I added some punctuation in various places and rearranged things a little. Also added that the variables "may be used in the future for other purposes" as that could be especially relevant for CIN_EDITOR. Question for Georgy? Added CIN_CC, but I did not add just CC like Andrea had because I think it is superfluous? Commentary for Georgy! so far I have found no problems with using the plugins from AppImage except you have to pay attention when you use Attach with an empty Function field with what comes up in the "Select function source file" menu for Project and Userlib. Which is also true of a regular build and this is not an issue once set up by an ordinary user who will want to use their own setup. Syslib works just fine in this case and if you click on "Edit..." the file comes up as Read-Only (at least in gedit) as it should. I am still going through the Manual changes locally (not checking in changes until done) and testing. One thing I noted and will add to the "Refresh" commentary is that you have to move the pointer before the "Refresh" action is displayed on the timeline/compositor. One more detail: for BlendAlgebra several new environment variables were
introduced: CIN_EDITOR, CIN_CC, CIN_USERLIB, etc. They are documented in the plugin's section of the manual. Perhaps there is reason to mention these environment variables additionally in the other section, dealing with all the CinGG environment variables. It might even happen that some of them later could be used by some other parts of CinGG software, who knows...
_______________________________________________________________________________
On Tue, 4 Mar 2025, Phyllis Smith wrote:
Question for Georgy? Added CIN_CC, but I did not add just CC like Andrea had because I think it is superfluous?
$CC is a common (not specific to CinGG) variable recognized by default by eg make and designating the C compiler. Perhaps it is not necessary to add it to the list of CinGG variables. A programmer could even expect from the compiling script to take into account $CC if set.
Commentary for Georgy! so far I have found no problems with using the plugins from AppImage except you have to pay attention when you use Attach with an empty Function field with what comes up in the "Select function source file" menu for Project and Userlib. Which is also true of a regular build and this is not an issue once set up by an ordinary user who will want to use their own setup. Syslib works just fine in this case and if you click on "Edit..." the file comes up as Read-Only (at least in gedit) as it should.
I'll look once more what happens after Attach from an empty name. Shamanism...
I am still going through the Manual changes locally (not checking in changes until done) and testing. One thing I noted and will add to the "Refresh" commentary is that you have to move the pointer before the "Refresh" action is displayed on the timeline/compositor.
Perhaps I can clarify this. Any function which is to be recompiled (because not up to date) will be recompiled on first access. For example, if timeline cursor sits on an updated function, and then in a few seconds, comes another, outdated function, then that function will not be recompiled until cursor reaches it. Pressing Refresh does not necessarily lead to immediate recompilation. It just sets a flag (more precisely, global timestamp) that all functions are not known anymore to be up to date and must be tested (and if they will be found outdated, recompiled). They will be checked also on first access. A function may not be recompiled after Refresh is pressed, if: if timeline cursor does not reach that function while playing track if function source is not newer than its earlier compiled object (i.e. function was not edited after its last compilation) _______________________________________________________________________________ Georgy Salnikov NMR Group Novosibirsk Institute of Organic Chemistry Lavrentjeva, 9, 630090 Novosibirsk, Russia Phone +7-383-3307864 Email [email protected] _______________________________________________________________________________
participants (4)
-
Andrea paz -
Georgy Salnikov -
Igor BEGHETTO -
Phyllis Smith