[Synfig-devl] [synfig/synfig] 069faa: Fix Enhancement #589 - Some actions cpp files ar...
Branch: refs/heads/master Home: https://github.com/synfig/synfig Commit: 069faab28481fa7fdb2f8ce26cb713972d1809f3 https://github.com/synfig/synfig/commit/069faab28481fa7fdb2f8ce26cb713972d1809f3 Author: Carlos Lopez genet...@gmail.com Date: 2014-02-23 (Sun, 23 Feb 2014) Changed paths: M synfig-studio/po/POTFILES.in Log Message: --- Fix Enhancement #589 - Some actions cpp files are not parsed in transiflex -- 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] [synfig/synfig] 5ef62f: Link to Bone action should replace existing Bone L...
Branch: refs/heads/master Home: https://github.com/synfig/synfig Commit: 5ef62fc46ff353ebf317b56df1a4992641d35293 https://github.com/synfig/synfig/commit/5ef62fc46ff353ebf317b56df1a4992641d35293 Author: Konstantin Dmitriev ksee.zelga...@gmail.com Date: 2014-02-23 (Sun, 23 Feb 2014) Changed paths: M synfig-studio/src/synfigapp/actions/valuedescbonelink.cpp Log Message: --- Link to Bone action should replace existing Bone Link. -- 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 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 {
[Synfig-devl] Branch improve-valuebase
Hi! Is https://github.com/blackwarthog/synfig/tree/improve-valuebase a branch that can be built? I have several errors when running building scripts. Cheers! -- Carlos http://synfig.org -- 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
