Imagine (or better yet, use modern design studios as users for testing, researching and interviewing) that you are in an agency and you have a mobile product that you building, lets say it is an app for sharing garage space as storage. I realize that it is a huge task to create that in axure as a developer, but I think invision is promising that in Motion when they bring that out and then all other prototype apps will be obsolete.Īxure has leverage features such as variables etc that trump invision, however, without sketch integration as everyone has mentioned Axure will be toast when Motion is released. I would also need to sync my artboard in sketch to Axure so that any updates in the sketch file will auto reflect in axure. BUT as others have mentioned… the fact that I can’t import an artboard to Axure is a deal breaker for workflow. I pasted the SVG and converted to objects easily by selecting all of the groups in a Sketch artboard. As of currently, when Sketch exports to SVG, they don’t export the the capitalisation (for certain versions), and they don’t export the superscript for text. Importing SVGs from Sketch can only be successful, though, if Sketch exports the features to the SVG itself. Proprietary formats have been more of a moving target, but as you said, would give us direct access to the data which could be really nice. We thought that SVG support would be a good addition regardless of tool-specific implementations. SVG gives you access to a lot of published resources and vector data from a variety of tools. We’ve seen that and we’re interested in the opportunities there. I think that this made importing sketch files way easier than before.ĭear Axure team, are you actively looking into this?īecause there you have all the assets and all the detailed information in plain text. New file format in Sketch 43 - Sketch Developers With version 43 sketch changed their file format. I am wondering why do you go this path of converting SVGs to get access to the Sketch data. Please float that by your dev team and see what they think… But if you did not name it special like this then it would continue to work as you’ve already implemented it - as custom shapes in Axure. Would make it so it would be incredibly unlikely to do this unless you intended to. Or if it was named “AxureInputbox - something” then Axure would attempt to combine both 2 layers into an input box and try to style it (where it could).ĭoes that make sense? This would make it a conscious decision to pull in items and have them map to appropriate Axure elements. But perhaps, if you give a Sketch Layer or GROUP a specific name, then the Paste could be smart enough to translate that specially named group of items into 1 kind of Axure element.įor example, let’s say you have a Sketch group consisting of a rounded rectangle with a text field placed inside it - if the group were named, “AxureTextbox - something” then when you pull in that group, those 2 Sketch shapes could be combined to an Axure rectangle named “something” containing that text with the corner radius properties set appropriately.
I gave it some thought, and wondered if the default way to bring shapes in, should be the way it currently works - bringing them in as several custom shapes. So some thought is required in the design for this.
#Justinmind sketch plugin how to#
This also begs the bigger question of how to map groups to Axure elements besides Axure custom shapes, since Axure has more “smarts” in its elements than Sketch (or SVG) does. Obviously converting random complex shapes might be cumbersome, but since we are often dealing with textbox-style shapes, keeping the editability of shapes when you can - so you can tweak properties in Axure - would be ideal where possible. While I get that by design that is the easiest dev way to bring in SVG as custom shapes - it would be great if for simple shapes such as Rectangles, that there is a way to map attributes to control points and make a “smart” Axure shape like a rectangle with editable attributes like corner radius (much like photoshop’s live shapes vs regular shapes). Nonetheless, I’ll be happy to pass this along to our product team about the ability to round corners on custom shapes. So while images/rectangles can have rounded corners, custom shapes cannot. You’ll see the same thing when using the Pen tool to create a custom shape or converting a Box widget into a custom shape in Axure RP where its rounded corner attributes will not be available to edit. When converting the SVG into a custom shape, that SVG is now a vector shape in RP. I was able to reproduce this bug where the SVG loses its dashed border after converting the Sketch SVG into a custom shape in RP 8, and I’ve gotten it filed with our QA team.Īs for the issue with the corner radius, I talked to our dev team about this and it turns out this is actually by design.
0 kommentar(er)
