On Mar 31, 2012, at 3:34 PM, ale rimoldi wrote:
> well, it won't exists if nobody works on it :-) > > there are systems that exist for branching your work... the question > is: how to make them work for a graphist designer? > > imo, we need graphic designers to invest some time and tell us, how > scribus could do it right. OK..help me out here...you're saying that a nodes-based tool does not yet exist? or that some tool other than layers, which does what layers can do does exist now? Here's where I am...I have a pretty full plate. So, when I try to incorporate open source ware in to my tool kit, I gravitate toward tools and methods that correspond to ones I'm already familiar with. There are compelling reasons for new software developers to build upon existing paradigms rather than re-enventing graphic design apps. You might grab a passionate following amongst those for whom Scribus is the only layout app they have ever used or ever will, but you'll likely discourage those coming from Quark/InDesign backgrounds. Getting back to layers. The concept behind their use is very simple. And there are equally simple and few reasons one would even use layers. If they work, great, if they don't, well, I'm forced to think it's a bug or poor implementation, and then move on. I can tell you that among other art directors and designers such as myself, Scribus is respected but considered a bit behind the times. Some say 10 years or more. There are certain workflows and realities of publishing and print production that demand layout programs do certain things in certain ways. We could spend time discussing it, if we have to, but thus far, it seems like heresy to suggest things about Scribus, and I'm not interested in opening any cans of worms. Scribus is good, can do certain things for me now, and for that, I am grateful to the developers for all of their earnest hard work and dedication. dcat -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.scribus.net/pipermail/scribus/attachments/20120331/64f47f3d/attachment.html>
