Jump to content

bryanrieger

Members
  • Content count

    19
  • Joined

  • Last visited

About bryanrieger

  • Rank
    Newbie

Recent Profile Visitors

92 profile views
  1. Any chance it might be possible to provide an option NOT to crop a layer when rasterising it? Often I find I'll bring in an image that I want to work with at a larger size and as soon as I rasterise it it's cropped to the size of the canvas. This is particularly useful when creating elements to be used in motion graphics, or simply creating a 'mood board' of elements to be used in other documents.
  2. Having Affinity Designer export Apple Motion shape files (.molo or .motn) would be a nice complement to the current export as Final Cut Pro/Motion compatible PSD option. Of course you can bring PDF files into Motion, but you loose the ability to work directly with the geometry. Bumping this similar conversation from last year.
  3. bryanrieger

    Missing Geometry with Copy/Paste from Designer to Glyphs

    Hi Chris, I have no idea what format Glyphs is expecting, but I'm assuming PDF and/or SVG on the clipboard. It's obviously recognizing the data, but appears to be misinterpreting the path directly after the origin node. I've cross-posted this to the Glyphs forum just-in-case anyone there can shed some more light on this issue.
  4. I keep running into a strange (and annoying) problem when copy/pasting objects from Designer to Glyphs in that some geometry is lost in translation from Designer to Glyphs (see attached image, files.zip also provided). If I export to SVG and then import into Glyphs everything is fine (but this makes the process much more laborious), as is also the case when I convert the origin node to a smooth curve, etc. If I simply leave the origin node as is it appears that the node immediately after the origin node is omitted on copy/paste. I'm not sure if this is a Designer issue or Glyphs issue, but I thought I'd start here as I only have this problem when copy/pasting geometry from Designer. files.zip
  5. A few months back I found Patternodes https://www.lostminds.com/patternodes2/ which is a parametric/flow design tool specifically for creating patterns. It has a node-based interface similar to Quartz Composer and exports to a variety of formats. While there's a certain logic in mirroring features found in other tools (especially in regards to user adoption), I think there's a real opportunity now to look at what our future tools could be given that many designers and artists are no longer scared of code-based and parametric tools. Tools like Grasshopper http://www.grasshopper3d.com/ and Houdini https://www.sidefx.com/products/houdini-fx/ are enabling designers and artists to bring to life ideas that would have been unimaginable a few years ago. Currently there seems to be an opportunity for a 'code-based'/parametric 2D design tool to really disrupt things and set the standard for the future.
  6. Finding I occasionally run into situations where upon importing or copy/pasting some artwork from another app (Comic Life, OmniGraffle, Illustrator, Preview/PDF, etc) I run into situations where what was once a continuous flow of text has been broken down into individual text frames. Sometimes this division is based on single lines, other times individual characters. Having the ability to select all of the related text frames and combine them into a new text frame would be really helpful. Of course determining what order the frames go in is a little complicated, I wonder if a 'best guess' based on the reading order of the document (ie: top down, left to right for western languages) would give a 'good enough' result in most circumstances with the ability to quickly copy/paste move text around in the combined frame after allowing users to fix any errors that may have crept in.
  7. Having used Macromedia Fireworks (I remember ye fondly) for many years I find myself still missing many of it's lovely little features that made working in it such a pleasure. One of these features was the ability to apply a feather effect to a stroke, shape, edge or even mask. This enabled all sort of quick and easy styles (vignettes, gradient fades, reflections, etc). I've tried doing these in Affinity designer using effects (using a gradient to 0% alpha and outer glow effects), but when you mask an image within the shape it reverts to it's hard edge. The wonderful thing with this approach was the 'shape/mask' remained vector (and editable), while enabling you to create more complex alpha masks that are typically done (in Photoshop) using bitmaps.
  8. bryanrieger

    Tight FCP X/ Motion Integration!!

    One feature I'd love is the ability to export Motion shape files (.molo or .motn) without having to resort to Vekpo (http://scottash.com/vekpo/) and Autodesk Graphic. That said, the latest version of Motion apparently no longer recognises it's own file format; see http://scottash.com/motion-5-3-file-import/ and http://scottash.com/motion-5-3-file-browser-workaround/ so it might not be an easy thing to support. Ideally, being able to export a Designer file to Motion included shapes, text, images, groups and masks would be fantastic, but I suspect the the file format is a moving, publicly undocumented target.
  9. Having the ability to align text (top, centre, bottom) contained within a frame (via Frame Text Tool) would be insanely useful in Designer as well as Publisher. For UI comps I'm increasingly finding myself cursing at having to constantly realign text boxes when the content contained within changes. Bonus points for the ability to apply margins and padding. :)
  10. bryanrieger

    Colour fonts

    Somewhat related this would be really useful in being able to include Apple (and others) emoji's in UX designs.
  11. bryanrieger

    Open File Format

    +1 on supporting the Sketch open file format. I've come to rely on it to create workflows between Flinto, Framer, Kite, Principle and Paint Code. Being able to take advantage of AD's symbols and constraints within an existing Sketch based workflow would make life so much easier.
  12. I'm finding that when I expand strokes within Affinity Designer I'm often left with dozens of nodes that can often lead to performance issues on mobile devices in complex compositions. In Adobe Illustrator these convert to stroke to path operations are much more efficient and can be further optimised by using the 'simplify' command to further reduce the number of nodes in the resulting shape. Often going from hundreds of points to a few dozens without any significant change in the overall shape. This has a significant impact when using SVGs exported from Affinity Designer in apps/websites as the files themselves tend to be quite bloated and the additional nodes can lead (in excessive cases) to redraw performance issues (aka: 'jank') when scrolling. For a very simple example the variable width line in the attached file has two nodes as a line, and over 60 nodes as a shape (it's also very jagged with many of the curves being translated to straight lines). The result is the exported SVG files is over 6Kb (for a line) and even when run through SVGOMG https://jakearchibald.github.io/svgomg/it's over 1.5Kb. In Illustrator this shape would likely be in the range of 12 nodes and less than 1Kb when exported and run through SVGOMG. excessive nodes.afdesign
  13. One thing I find I still require Illustrator for is the ability to automagically clean up and optimise vector art (really important when going to SVG/the web - but also useful to just simplify logos, shapes, etc). Any chance we might see similar features available in AD one day? Would be really useful if/when the ability to trace/generate vector art from photos, scans, etc is added.
  14. Ah, thanks for that. Makes perfect sense in hindsight but for some reason it wasn't obvious. I always see that as a 'share' button, not 'export' (although both actions could be considered similar/related). Thanks again.
×