Jump to content


  • Content Count

  • Joined

  • Last visited

About Ammoniteii

  • Rank

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. In the My Purchases section after registration - it is only showing the new brush pack, should this note be showing all other content too - I also have the grade ui kit, retro supply font collection Iconic Graphic & Logo Templates by The Vector Lab, Fine Liner Affinity Brushes by The Artifex Forge, Montebello Typeface by Ian Barnard, JR Macros: Channels but only the luminance brush pack is showing up? is this intended
  2. Yes this is a very annoying behaviour, it would be great to be able to set default behaviour even if it was per document or have default set to all pages automatically.
  3. Hi MikeW, I am aware this is a feature request on its own, I was simply trying to show the benefits of allowing plugin support in relation to other requests, mainly through the use of open source programs out there that can be implemented into affinity as a work around until official tools are developed. There are many programmers out there that could develop plugins and there are many whom already contribute to opensource projects, so whilst I understand your price point objection, there are many cases of people working simply to improve tools or add to them. The ultimate point about plugins is this - if the inbuilt tool works better then there is no longer need for the plugin - unless there is a very specific case point where the plugin does a better job, but if the toll does not exist or is never intended to be developed by serif, then plugins would be most helpful in those solutions. Developing the API is the core of what the post is about - but i was providing specific examples where such an API could not only be used, but help to clear up the Forums from lots of posts about the same issues - there are a number of opensource tools that could be turned into plugins and solve issues until serif cna develop the Affinity specific tool. The idea of a premium version upgrade (Affinity (+)) could be offered temporarily, to cover the cost of the API development if it included a number of previous serif tools in plugin form which would also help to fill gaps in the current tool roster, if this path were chosen, you would want to replace plugins with inbuilt tools, so that the need for Affinity (+) would be phased out. for example - lets say one of the biggest issues with this path would be IPADS, Offer (Affinity (+)) only on desktop - make any exportable object have to be a vector / raster for export so there are no conflicting issues with Live filters / plugins. Once Serif Make the Native version of the tool - either remove the tool from Affinity (+) of leave it in as an alternate - Once all tools are implemented, remove Affinity (+) as an option. If people wanted to use the serif tools and not open source ones they could for a premium, but this was of course just a suggestion to cover costs - Ultimately a Plugin API on its own would be Excellent as a number of workarounds could then be made inside Designer until Serif Develops the Affinity Specific tool.
  4. So there are a number of feature requests that could be temporarily solved by the use of open source plugins. Serif want to develop proprietary solutions to many of these tools and i honestly hope they do - however whilst they are working on these tool and on fixing bugs etc, why not allow a framework that can enable plugin implementation or development for the affinity system. Another option to open source would be to have old serif utility modules, such as tools from Page Plus, Draw Plus or Photo Plus - as long as you make the functionality clear and the fact it is a Legacy or Open Plugin, I don't think users would mind and in fact would rather have limited functionality rather than none. I understand the Affinity Suite is a new set of programs and i understand it is built in a fundamentally different way, but in order to be a true replacement of your own software , nevermind an option to replace alternate offerings, more needs to be offered to cover some basic elements of modern software. lets look at some EXAMPLE requests that i know of that could be an easy temporary solution once implemented 1. Measure tool Currently this requires work arounds ...WHY?? we can, draw a line and get its length but we cannot simply measure gaps, objects etc - this one should be an easy and obvious win this shouldn't even require a plugin, but a plugin tool that would allow you to draw a toggleable printable / non printable measurement or group of such measurement lines would be very welcome. 2. Trace Bitmap This is a very commonly requested feature, users that want this functionality currently have to use a separate program, leave affinity boot program, trace the image, then re import into affinity as a vector, by allowing for a plug in framework - for a temporary amount of time users could simply use a plugin built around Potrace - http://potrace.sourceforge.net/ - this is the same technology used in Inkscape - not perfect but works well enough, and if users are currently booting a separate program to do the same thing it would stop that annoying work around, keeping people inside the affinity workflow. 2 (a). Vector Brushes (workaround) by allowing the above method, users could "set" the dynamic raster brushes currently called vector brushes - once they were happy with them, if they wanted to keep dynamics they could simply create a duplicate layer and set then then turn off visibility of the "vector brush" stroke, this would allow brushes to be exported without rasterization, a bitmap trace module would also have other side benefits similar to these 2, using pixel layers to draw textures then vectorising etc etc. 3. Barcode generation / QR generation while one could again make a potrace argument if you had a raster barcode, this would be weird, however there are many other solutions including those developed for previous serif products. Whilst there are of course many many other tools that would benefit from such a system, but the principal is this. if there are open source, or older proprietary tools that can do the jobs being requested, then until such time as development can be completed on the newest gen tool these tools should be available via a plug in system, the performance of these plugins should be made clear, these are to enable users to stay in the affinity workflow whilst completing a job NOT to provide the best result serif can offer, or reflect on serifs ability. Support for these plugins should be limited and down to the Community / OS Developers if the plugin is open source or if proprietary Serif for bug fixes / version clashes only. Plugins should not get new feature requests if Proprietary, however the usage of such plugins may actually aid development of the new generation tool, as users could suggest improvements on a tool basis. Whilst development of a plugin manager / porting code to work with affinity will take time and effort it should be considerably less time than required to develop the new tools, and "should" cover a lot of the bases of missing tools that people currently require or ask about of a regular basis. This could initially be offered as a premium upgrade if necessary to cover time / costs say £10 / £20 for Affinity Designer "(+)" plugin suite containing draw plus / page plus tools) leaving the current version only having the officially developed Affinity Designer tools, and or open source tool compatibility and allowing for the addition of these modules for those whom want them "NOW" at an extra cost, Let me be clear i would not think this is a good strategy long term, Tools should be developed and implemented into the Core Affinity System, i am simply talking about a way of giving people tools Sooner rather than later that is cost effective for the company so that I'm not trying top ask for everything for free. its possible many features and tolls are planned for version 2.0 ...but how long will that be? and where is the roadmap to give us an expectation? this workaround would remove the need for roadmaps etc as when the New version of a tool was ready it would be implemented offering improvements over the plugin version, meanwhile features you don't wish to be implemented natively at this stage could be offered by plugin developers.
  5. I know there have been multiple requests for a trace bitmap function but please let me weigh in on why this is vital for more than just vectoring an existing image. Affinity designers workflow is great, its fat light weight and allows for some great tools, However, i have quickly run into multiple problems. if i want to mask a pattern to a vector group, lets say some damage, then I can - but if i ever want a destructive output its impossible, and the layer must be converted into a raster, this is no good for multiple real world applications, and yes i'm aware i could do a boolean operation with each "layer" / object but when you have a lot of elements this is a massive pain, it would be much better to apply the mask then have the option to destructively re draw the elements - a fast way to do this would be to rasterize the layer as you can now, then apply a trace bitmap to the pixel layer result, drawing as meany "layers" / objects as necessary or grouping by colour (i mean creating layers from each colour making "compound style shapes" If i want to apply a brush stroke to a vector curve, the brush stroke itself is raster not vector, again a Trace function would allow you to make raster brushes, apply them as a vector brush in a non destructive way, and when you are happy trace and output the result as a solid vector. if i want to output in a format that should be vector - these types of elements are forced to be rasterized for various reasons, from a workflow perspective "non destructive" editing is excellent, but from an output perspective its very very limiting, unless everyone is using affinity, I have to export sections of work to a different program just to vectorize them to the re import into affinity if i want to use the workflow available in your apps, this is a monumental pain that has many factors that require trial and error to get right. for example if i take the brushstroke as an example, and apply this to text, with certain fonts and brushstrokes if i export and allow affinity to automatically rasterize, it can actually mess up the geometry - you have to rasterrize the layer before export. This is very annoying, although obviously not something that is intended. I really like the Affinty workflow and have all 3 apps - but this function is sorely needed for many applications especially when alternatives can be very slow.
  • Create New...

Important Information

Please note the Annual Company Closure section in the Terms of Use. These are the Terms of Use you will be asked to agree to if you join the forum. | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.