Re: [Synfig-devl] Opacity vs Amount (of layer)
Hi! 2014-02-23 21:25 GMT+07:00 David rylle...@gmail.com: On 02/23/2014 02:30 PM, Yu Chen wrote: Remove them from toolbox, and place them in global toolbar (main window toolbar) or in Tool Option Panel. A very good move I think. I vote for tool options panel. Less clutter when the tools is not needed. I would vote to place Default BlendMethod/Opacity to tool options panel as well. My plan is to implement a auto re-sizing toolbox as Gimp does. IIRC, resizable table feature (I mean table, which changes count of columns depending on the allocated space) is available in Gtk3. K. -- Flow-based real-time traffic analytics software. Cisco certified tool. Monitor traffic, SLAs, QoS, Medianet, WAAS etc. with NetFlow Analyzer Customize your own dashboards, set traffic alerts and generate reports. Network behavioral analysis security monitoring. All-in-one tool. http://pubads.g.doubleclick.net/gampad/clk?id=126839071iu=/4140/ostg.clktrk ___ Synfig-devl mailing list Synfig-devl@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synfig-devl
Re: [Synfig-devl] Opacity vs Amount (of layer)
Hi All, Thanks for clarifying and sharing your thoughts about this. I should take more time before sending out the first mail. I hope it is not too late: I didn't intend to JUST remove any UI elements. When I show synfig to my students (adobe photoshop/illustrator advanced users), the are a lot of feedback/concerns regarding UI, the toolbox is one of them: a) File buttons in toolbox is really weird. b) The defaults widgets layout is mess and is hard to understand at the first sight, Opacity particularly. The most of my students complain that it seems like a slider to change the Option above it (Layer Blender Method), and some of them guessing it can adjust the Gradient setting bellow. When I explain them, those two widgets are used to change Opacity and Blender Method, then almost all of them complain why layer blend method and opacity options are exposed on toolbox. In their world, when s/he would like to draw an element with other opacity value than 1, s/he use a color with alpha in a non-zero value. and they also have concerns about other UI things but it is another topic. Based on my experience, I never use Blend Method and Opacity. But yes, I did see some demo from internet showing synfig studio users were using those widgets during creating animation. So I raised this topic and would like to get feedback from you. Thanks you all and now I can get more clear idea. We also should notice that these widgets' width. It will be a big impact to implement a more flexible toolbox. As we can see, Layer Blend Method and Interpolation widgets are quite long(width) and take more than 4 buttons' width. I noticed the current toolbx wastes a lot of screen space due to 5 buttons each row design. My plan is to implement a auto re-sizing toolbox as Gimp does. The outline/fill colors and gradient widgets will be implemented as 2 button size's widget [1]. But for Layer Blend and Opacity widgets, It will become useless if they are also in 2 buttons size. So my conclusion is: Remove them from toolbox, and place them in global toolbar (main window toolbar) or in Tool Option Panel. If they are going to be placed in global toolbar, then they will behave the same as they do in toolbox, if they are going to be placed in Tool Options Panel, then they will be available only while those tools such as geometry tools being selected. Regarding Simplified / Advanced UI options, My idea is to implement a customizable toolbar/toolbox system, User can define which avaliable tools(buttons) be exposed on each toolbox/toolbar( global toolbar, local toolbars, like layer panel toolbar, history panel toolbar etc). And this kind of ability should be a part of workspace system. I mean, Workspace system is not only regarding windows position, size, but also taking care the UI elements on windows. And then user can decide if Opacity and other widgets should be exposed on his/her Synfig Studio. [1] my toolbox/toolbar cleanup branch https://github.com/jcome/synfig/tree/toolbox-toolbar Cheers! ~ yu ___ Synfig-devl mailing list Synfig-devl@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synfig-devl -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk___ Synfig-devl mailing list Synfig-devl@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synfig-devl
Re: [Synfig-devl] Opacity vs Amount (of layer)
On 02/23/2014 02:30 PM, Yu Chen wrote: Remove them from toolbox, and place them in global toolbar (main window toolbar) or in Tool Option Panel. A very good move I think. I vote for tool options panel. Less clutter when the tools is not needed. Regarding Simplified / Advanced UI options, My idea is to implement a customizable toolbar/toolbox system, User can define which avaliable tools(buttons) be exposed on each toolbox/toolbar( global toolbar, local toolbars, like layer panel toolbar, history panel toolbar etc). And this kind of ability should be a part of workspace system. I mean, Workspace system is not only regarding windows position, size, but also taking care the UI elements on windows. And then user can decide if Opacity and other widgets should be exposed on his/her Synfig Studio. Yes! a customizable tool UI, sweet! I think we need to make the different setting files accessible within Synfig so we can easily load and save different UI setups, tool setups, keyboard shortcuts etc. People can then easily share and download great setups, enabling everyone to contribute (easily, without coding skills) in making Synfig easier to use. Better setups will hopefully be adopted and you coding developers can see how people customize Synfig and can use that in developing a better vanilla flavour. -David -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk ___ Synfig-devl mailing list Synfig-devl@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synfig-devl
Re: [Synfig-devl] Opacity vs Amount (of layer)
David wrote:
I think we need to make the different setting files accessible within
Synfig so we can easily load and save different UI setups, tool setups,
keyboard shortcuts etc.
People can then easily share and download great setups, enabling
everyone to contribute (easily, without coding skills) in making Synfig
easier to use.
Better setups will hopefully be adopted and you coding developers can
see how people customize Synfig and can use that in developing a better
vanilla flavour.
-David
The toolbox is hardcoded in app.cpp, but if it was changed to read
a config-file, it could let users customize it with a file like
$HOME/.synfig/toolbox.lst or C:\Program Files\Synfig\toolbox.lst.
I attached some code that is supposed to do this, but it's very C-ish
and my package manager has outdated libs, so I have not tested it.
~Charlie
diff --git a/synfig-studio/src/gui/app.cpp b/synfig-studio/src/gui/app.cpp
index a02da7e..5d4d33f 100644
--- a/synfig-studio/src/gui/app.cpp
+++ b/synfig-studio/src/gui/app.cpp
@@ -83,6 +83,7 @@
#include mainwindow.h
#include docks/dock_toolbox.h
#include onemoment.h
+#include loadtools.h
#include docks/dockmanager.h
@@ -1512,32 +1513,34 @@ App::App(const synfig::String basepath, int *argc, char ***argv):
// Init Tools must be done after load_accel_map() : accelerators keys
// are displayed in toolbox labels
studio_init_cb.task(_(Init Tools...));
- /* editing tools */
- state_manager-add_state(state_normal);
- state_manager-add_state(state_smooth_move);
- state_manager-add_state(state_scale);
- state_manager-add_state(state_rotate);
- state_manager-add_state(state_mirror);
-
- /* geometry */
- state_manager-add_state(state_circle);
- state_manager-add_state(state_rectangle);
- state_manager-add_state(state_star);
- if(!getenv(SYNFIG_DISABLE_POLYGON)) state_manager-add_state(state_polygon); // Enabled - for working without ducks
- state_manager-add_state(state_gradient);
-
- /* bline tools */
- state_manager-add_state(state_bline);
- if(!getenv(SYNFIG_DISABLE_DRAW )) state_manager-add_state(state_draw); // Enabled for now. Let's see whether they're good enough yet.
- if(!getenv(SYNFIG_DISABLE_WIDTH )) state_manager-add_state(state_width); // Enabled since 0.61.09
- state_manager-add_state(state_fill);
- state_manager-add_state(state_eyedrop);
-
- /* other */
- state_manager-add_state(state_text);
- if(!getenv(SYNFIG_DISABLE_SKETCH )) state_manager-add_state(state_sketch);
- state_manager-add_state(state_zoom);
+ if (!studio::loadtools(state_manager)) {
+ /* editing tools */
+ state_manager-add_state(state_normal);
+ state_manager-add_state(state_smooth_move);
+ state_manager-add_state(state_scale);
+ state_manager-add_state(state_rotate);
+ state_manager-add_state(state_mirror);
+
+ /* geometry */
+ state_manager-add_state(state_circle);
+ state_manager-add_state(state_rectangle);
+ state_manager-add_state(state_star);
+ if(!getenv(SYNFIG_DISABLE_POLYGON)) state_manager-add_state(state_polygon); // Enabled - for working without ducks
+ state_manager-add_state(state_gradient);
+
+ /* bline tools */
+ state_manager-add_state(state_bline);
+ if(!getenv(SYNFIG_DISABLE_DRAW )) state_manager-add_state(state_draw); // Enabled for now. Let's see whether they're good enough yet.
+ if(!getenv(SYNFIG_DISABLE_WIDTH )) state_manager-add_state(state_width); // Enabled since 0.61.09
+ state_manager-add_state(state_fill);
+ state_manager-add_state(state_eyedrop);
+
+ /* other */
+ state_manager-add_state(state_text);
+ if(!getenv(SYNFIG_DISABLE_SKETCH )) state_manager-add_state(state_sketch);
+ state_manager-add_state(state_zoom);
+ }
device_tracker-load_preferences();
// If the default bline width is modified before focus a canvas
#include cstdio
#include cstring
#include statemanager.h
#include states/state_eyedrop.h
#include states/state_normal.h
#include states/state_mirror.h
#include states/state_draw.h
#include states/state_fill.h
#include states/state_bline.h
#include states/state_polygon.h
#include states/state_sketch.h
#include states/state_gradient.h
#include states/state_circle.h
#include states/state_rectangle.h
#include states/state_smoothmove.h
#include states/state_scale.h
#include states/state_star.h
#include states/state_text.h
#include states/state_width.h
#include states/state_rotate.h
#include states/state_zoom.h
#define nelem(x) (sizeof(x) / sizeof(*x))
typedef struct {
char *name;
Smach::state_base *state;
} Tool;
static void chomp(char *s);
static FILE *opencfg(char *name);
static void
chomp(char *s)
{
char *nl = strchr(s, '\n');
if (nl) {
*nl = '\0';
}
}
static FILE *
opencfg(char *name, char *mode)
{
char fullname[128];
FILE *f;
if (getenv(HOME)) {
#ifdef __APPLE__
snprintf(fullname, sizeof(fullname), %s/Library/Synfig/%s, getenv(HOME), name);
#else
snprintf(fullname, sizeof(fullname), %s/.synfig/%s, getenv(HOME);
#endif
} else {
Re: [Synfig-devl] Opacity vs Amount (of layer)
2014-02-22 13:49 GMT+07:00 Carlos López González genet...@gmail.com: El sábado, 22 de febrero de 2014, Konstantin Dmitriev ksee.zelga...@gmail.com escribió: On the other hand, there are lot of accidents happening for newbie users, when they have problems with those widgets. Then, my proposal is: disable saving/restoring of Default BlendMethod/Opacity in the SynfigStudio's settings file. In this case at the start of Synfig the Opacity will be always = 1.0 and Blend Method will be always = By layer Default. So, even if the user screwed something during the work, then he can restart SYnfig and work normally. ... Regards, K. That's a good idea. Sorry, Carlos, I forgot to mention that introducing an option for visibility of Default Opacity/BlendMethod is also would be an interesting experiment. We can introduce a Simplified UI option in the parameter dialogue and make it ON by default. When this option is ON, then Default Opacity/BlendMethod are hidden and the Default Opacity for new layers = 1.0, Default Blend Method = By layer Default. Experienced users can turn this option OFF and this will make Default Opacity/BlendMethod widgets visible. This also makes a room for other UI experiments. Regards, K. -- http://morevnaproject.org/ -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk ___ Synfig-devl mailing list Synfig-devl@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synfig-devl
Re: [Synfig-devl] Opacity vs Amount (of layer)
That's the right way to go! ^__^ 2014-02-22 9:31 GMT+01:00 Konstantin Dmitriev ksee.zelga...@gmail.com: 2014-02-22 13:49 GMT+07:00 Carlos López González genet...@gmail.com: El sábado, 22 de febrero de 2014, Konstantin Dmitriev ksee.zelga...@gmail.com escribió: On the other hand, there are lot of accidents happening for newbie users, when they have problems with those widgets. Then, my proposal is: disable saving/restoring of Default BlendMethod/Opacity in the SynfigStudio's settings file. In this case at the start of Synfig the Opacity will be always = 1.0 and Blend Method will be always = By layer Default. So, even if the user screwed something during the work, then he can restart SYnfig and work normally. ... Regards, K. That's a good idea. Sorry, Carlos, I forgot to mention that introducing an option for visibility of Default Opacity/BlendMethod is also would be an interesting experiment. We can introduce a Simplified UI option in the parameter dialogue and make it ON by default. When this option is ON, then Default Opacity/BlendMethod are hidden and the Default Opacity for new layers = 1.0, Default Blend Method = By layer Default. Experienced users can turn this option OFF and this will make Default Opacity/BlendMethod widgets visible. This also makes a room for other UI experiments. Regards, K. -- http://morevnaproject.org/ -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk ___ Synfig-devl mailing list Synfig-devl@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synfig-devl -- Carlos http://synfig.org -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk___ Synfig-devl mailing list Synfig-devl@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synfig-devl
Re: [Synfig-devl] Opacity vs Amount (of layer)
Le 22/02/2014 05:33, Konstantin Dmitriev a écrit : 2014-02-21 0:44 GMT+07:00 Timothée Giet anim...@gmail.com: Hi Konstantin, thanks for the suggestion, but the problem is in this case while drawing the outline and shape are created at the same time, and they should have different opacity and/or blend modes, but I cannot create each in a separate group directly.. Wait, Timothee... In current implementation, when you set default opacity, then it influences both outline and region, at the same time. There is no way to have shape and outline created with different opacity values. My guess is that you creating several outline/region pairs, each pair with different settings, and then you reorder the layers, am I right? In this case I have to agree - the grouping won't work here. Also, when I remember our shadow vectorization workflow (during production of Morevna Project), I have to admit that removing BlenMethod/Opacity widgets wasn't good idea. Oooo indeed you're right, my memory was confused... And your guess is right :) On the other hand, there are lot of accidents happening for newbie users, when they have problems with those widgets. Then, my proposal is: disable saving/restoring of Default BlendMethod/Opacity in the SynfigStudio's settings file. In this case at the start of Synfig the Opacity will be always = 1.0 and Blend Method will be always = By layer Default. So, even if the user screwed something during the work, then he can restart SYnfig and work normally. I agree to reset these values to default at start, good idea. Also your proposal for a Simple/Advanced interface option is good idea too! I may not have this problem if it was easily possible to auto-create shape layers corresponding to selected outline layers, afaik if the shape is not created when drawing outline it's not straight forward to create a new correspong fill shape. Or is there a new magic feature I'm missing? We have Create Region command for Outline layer, but it works for one layer only. I believe that would be easy to make it work for several layers at once. Yéé cool I didn't know this create region button yet, sure that would be useful to can use it for several layers at once.. Should I file a wish in the bugtracker? Yu, my apologies for digressing the topic. I just couldn't resist to put my concerns about removing Blend Method/Opacity. For me it's fine to replace Amount to Opacity as layer parameter name. For me it's also ok to leave things as they are (Opacity as name for default opacity widget and Amount in the layer parameters) I don't feel comfortable with changing Default Opacity to Default Amount (on the toolbox), because that will be a bad impact for intuitivity. +1 ;) Regards, K. -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk ___ Synfig-devl mailing list Synfig-devl@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synfig-devl
Re: [Synfig-devl] Opacity vs Amount (of layer)
Yéé cool I didn't know this create region button yet, sure that would be useful to can use it for several layers at once.. Should I file a wish in the bugtracker? Yes, it's better to file one, so we won't forgot. ^__^ -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk ___ Synfig-devl mailing list Synfig-devl@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synfig-devl
Re: [Synfig-devl] Opacity vs Amount (of layer)
2014-02-21 0:44 GMT+07:00 Timothée Giet anim...@gmail.com: Hi Konstantin, thanks for the suggestion, but the problem is in this case while drawing the outline and shape are created at the same time, and they should have different opacity and/or blend modes, but I cannot create each in a separate group directly.. Wait, Timothee... In current implementation, when you set default opacity, then it influences both outline and region, at the same time. There is no way to have shape and outline created with different opacity values. My guess is that you creating several outline/region pairs, each pair with different settings, and then you reorder the layers, am I right? In this case I have to agree - the grouping won't work here. Also, when I remember our shadow vectorization workflow (during production of Morevna Project), I have to admit that removing BlenMethod/Opacity widgets wasn't good idea. On the other hand, there are lot of accidents happening for newbie users, when they have problems with those widgets. Then, my proposal is: disable saving/restoring of Default BlendMethod/Opacity in the SynfigStudio's settings file. In this case at the start of Synfig the Opacity will be always = 1.0 and Blend Method will be always = By layer Default. So, even if the user screwed something during the work, then he can restart SYnfig and work normally. I may not have this problem if it was easily possible to auto-create shape layers corresponding to selected outline layers, afaik if the shape is not created when drawing outline it's not straight forward to create a new correspong fill shape. Or is there a new magic feature I'm missing? We have Create Region command for Outline layer, but it works for one layer only. I believe that would be easy to make it work for several layers at once. Yu, my apologies for digressing the topic. I just couldn't resist to put my concerns about removing Blend Method/Opacity. For me it's fine to replace Amount to Opacity as layer parameter name. For me it's also ok to leave things as they are (Opacity as name for default opacity widget and Amount in the layer parameters) I don't feel comfortable with changing Default Opacity to Default Amount (on the toolbox), because that will be a bad impact for intuitivity. Regards, K. -- http://morevnaproject.org/ -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk ___ Synfig-devl mailing list Synfig-devl@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synfig-devl
Re: [Synfig-devl] Opacity vs Amount (of layer)
El sábado, 22 de febrero de 2014, Konstantin Dmitriev ksee.zelga...@gmail.com escribió: On the other hand, there are lot of accidents happening for newbie users, when they have problems with those widgets. Then, my proposal is: disable saving/restoring of Default BlendMethod/Opacity in the SynfigStudio's settings file. In this case at the start of Synfig the Opacity will be always = 1.0 and Blend Method will be always = By layer Default. So, even if the user screwed something during the work, then he can restart SYnfig and work normally. ... Regards, K. That's a good idea. -- Carlos http://synfig.org -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk___ Synfig-devl mailing list Synfig-devl@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synfig-devl
[Synfig-devl] Opacity vs Amount (of layer)
Hi, We have Default Opacity dropdown in Toolbox, which affects new layer's Amount. Do you think it would be better to unify this term? Just using Amount, since we have some layers which relevant parameter can not be called Opacity. And even further, do we really need this Opacity preference exposed on UI? Does it really help for users? I remember that in the forums, there were posts by some users( newbies and advanced users), complaining they had no idea why their new layers became transparent, just because they didn't noticed the Default Opacity had been set to a value less than 1. What's your opinion? Cheers! ~ yu -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk___ Synfig-devl mailing list Synfig-devl@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synfig-devl
Re: [Synfig-devl] Opacity vs Amount (of layer)
HI Yu! I have never used the Opacity preference before - it's always 1.0 when I use Synfig Studio. I can't imagine I would ever set it to any other value than 1.0 and I wouldn't mind if this preference was not exposed on the UI. Unifying terms is a hard question. Amount is only opacity when it's set between 0 and 1.0 ; it can be set to values less than 0 and more than 1 and when used with certain layers make a difference other than opacity (for instance brightness). I have sometimes used values of Amount more than 1 in order to get certain effects. Obviously Carlos and Konstantin will know far more about this than me, but I hope this is helpful. All the best, Dave -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk___ Synfig-devl mailing list Synfig-devl@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synfig-devl
Re: [Synfig-devl] Opacity vs Amount (of layer)
Hi! I would like to remove both Default opacity and Default Blend Method widgets. K. 2014-02-20 22:46 GMT+07:00 Dave Jeffery david.richard.jeff...@gmail.com: HI Yu! I have never used the Opacity preference before - it's always 1.0 when I use Synfig Studio. I can't imagine I would ever set it to any other value than 1.0 and I wouldn't mind if this preference was not exposed on the UI. Unifying terms is a hard question. Amount is only opacity when it's set between 0 and 1.0 ; it can be set to values less than 0 and more than 1 and when used with certain layers make a difference other than opacity (for instance brightness). I have sometimes used values of Amount more than 1 in order to get certain effects. Obviously Carlos and Konstantin will know far more about this than me, but I hope this is helpful. All the best, Dave -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk ___ Synfig-devl mailing list Synfig-devl@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synfig-devl -- http://morevnaproject.org/ -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk ___ Synfig-devl mailing list Synfig-devl@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synfig-devl
Re: [Synfig-devl] Opacity vs Amount (of layer)
Hi, I use the opacity value other than 1 sometimes it is very useful, a good example is for tracing outlines with outline+shape where shapes have transparent value (~20% opacity) to can still see the reference drawing behind. Same for blend mode, can be useful to set it directly when drawing rather than having to change it afterward. So please don't remove those from the UI (you can put it somewhere else maybe, but not remove it completly ;.) ) Cheers !! Tim Le 20/02/2014 15:45, Yu Chen a écrit : Hi, We have Default Opacity dropdown in Toolbox, which affects new layer's Amount. Do you think it would be better to unify this term? Just using Amount, since we have some layers which relevant parameter can not be called Opacity. And even further, do we really need this Opacity preference exposed on UI? Does it really help for users? I remember that in the forums, there were posts by some users( newbies and advanced users), complaining they had no idea why their new layers became transparent, just because they didn't noticed the Default Opacity had been set to a value less than 1. What's your opinion? Cheers! ~ yu -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk ___ Synfig-devl mailing list Synfig-devl@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synfig-devl -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk___ Synfig-devl mailing list Synfig-devl@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synfig-devl
Re: [Synfig-devl] Opacity vs Amount (of layer)
2014-02-20 23:29 GMT+07:00 Timothée Giet anim...@gmail.com: Hi, I use the opacity value other than 1 sometimes it is very useful, a good example is for tracing outlines with outline+shape where shapes have transparent value (~20% opacity) to can still see the reference drawing behind. Same for blend mode, can be useful to set it directly when drawing rather than having to change it afterward. In this case the workflow is to group your vector artwork, then apply opacity and blend method settings to the group. And then create new vector elements inside of this group. ~_^ K. Le 20/02/2014 15:45, Yu Chen a écrit : Hi, We have Default Opacity dropdown in Toolbox, which affects new layer's Amount. Do you think it would be better to unify this term? Just using Amount, since we have some layers which relevant parameter can not be called Opacity. And even further, do we really need this Opacity preference exposed on UI? Does it really help for users? I remember that in the forums, there were posts by some users( newbies and advanced users), complaining they had no idea why their new layers became transparent, just because they didn't noticed the Default Opacity had been set to a value less than 1. What's your opinion? Cheers! ~ yu -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk ___ Synfig-devl mailing list Synfig-devl@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synfig-devl -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk ___ Synfig-devl mailing list Synfig-devl@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synfig-devl -- http://morevnaproject.org/ -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk ___ Synfig-devl mailing list Synfig-devl@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synfig-devl
Re: [Synfig-devl] Opacity vs Amount (of layer)
Hi Konstantin, thanks for the suggestion, but the problem is in this case while drawing the outline and shape are created at the same time, and they should have different opacity and/or blend modes, but I cannot create each in a separate group directly.. I may not have this problem if it was easily possible to auto-create shape layers corresponding to selected outline layers, afaik if the shape is not created when drawing outline it's not straight forward to create a new correspong fill shape. Or is there a new magic feature I'm missing? Tim Le 20/02/2014 17:39, Konstantin Dmitriev a écrit : 2014-02-20 23:29 GMT+07:00 Timothée Giet anim...@gmail.com: Hi, I use the opacity value other than 1 sometimes it is very useful, a good example is for tracing outlines with outline+shape where shapes have transparent value (~20% opacity) to can still see the reference drawing behind. Same for blend mode, can be useful to set it directly when drawing rather than having to change it afterward. In this case the workflow is to group your vector artwork, then apply opacity and blend method settings to the group. And then create new vector elements inside of this group. ~_^ K. Le 20/02/2014 15:45, Yu Chen a écrit : Hi, We have Default Opacity dropdown in Toolbox, which affects new layer's Amount. Do you think it would be better to unify this term? Just using Amount, since we have some layers which relevant parameter can not be called Opacity. And even further, do we really need this Opacity preference exposed on UI? Does it really help for users? I remember that in the forums, there were posts by some users( newbies and advanced users), complaining they had no idea why their new layers became transparent, just because they didn't noticed the Default Opacity had been set to a value less than 1. What's your opinion? Cheers! ~ yu -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk ___ Synfig-devl mailing list Synfig-devl@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synfig-devl -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk ___ Synfig-devl mailing list Synfig-devl@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synfig-devl -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk ___ Synfig-devl mailing list Synfig-devl@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synfig-devl
Re: [Synfig-devl] Opacity vs Amount (of layer)
Hi! El jueves, 20 de febrero de 2014, Yu Chen jco...@gmail.com escribió: Hi, We have Default Opacity dropdown in Toolbox, which affects new layer's Amount. Do you think it would be better to unify this term? Just using Amount, since we have some layers which relevant parameter can not be called Opacity. Correct me if I'm wrong, but layers that it's amount doesn't mean opacity aren't affected by this default widget. So if the thing is a question of nomenclature, why don't we change the parameter name from amount to opacity at the layers where it means that? And even further, do we really need this Opacity preference exposed on UI? Does it really help for users? I remember that in the forums, there were posts by some users( newbies and advanced users), complaining they had no idea why their new layers became transparent, just because they didn't noticed the Default Opacity had been set to a value less than 1. I'm not in favour of just remove the widget but better allow expose it or not to save space. This way everyone is happy ^__^ Pulling this to the absurd, why do we need the default brush or the default color widgets? I think that it is very helpful to allow to change the default construction parameters that in my opinion, the opacity is one of the basics. What's your opinion? Cheers! ~ yu -- Carlos http://synfig.org -- Managing the Performance of Cloud-Based Applications Take advantage of what the Cloud has to offer - Avoid Common Pitfalls. Read the Whitepaper. http://pubads.g.doubleclick.net/gampad/clk?id=121054471iu=/4140/ostg.clktrk___ Synfig-devl mailing list Synfig-devl@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/synfig-devl
