Jump to content
You must now use your email address to sign in [click for more info] ×

hperticarati

Members
  • Posts

    35
  • Joined

  • Last visited

Posts posted by hperticarati

  1. 2 hours ago, Mark Oehlschlager said:

    @Patrick Connor @Ben

    Not sure I understand what problem exists here. As Ben wrote:

    If one is laying out a grid of artboards, what's wrong with using the align and distribute commands to align the artboards relative to one another, and be satisfied that the rulers will show a 0,0 origin in the upper left corner of the active artboard?

    I think that probably all main issues with this were mentioned in the previous comments ;) 

    Usually, the align and distribute tools are used 100% of the time to perform these tasks. However, they are not enough and are not fail-proof, because sometimes you need to know one artboard position to place the other one. Also, it does not guarantee that the first selected artboard is placed precisely over an "entire pixel".

    And well, we are not asking anything absurd. This is simply how all other graphic design software work, so if the new feature doesn't introduce any significant benefits with it and causes trouble, I think it should be reconsidered.

    Anyway, the argument of having the 0,0 coordinates on the ruler does not make much sense:

    - if I select the artboard, the coordinates on the ruler should provide relevant information about where the artboard is. If the values displayed are 0,0, it's irrelevant because the reference is the artboard itself.

    - Now, if you select an object INSIDE the artboard, then its position should be relative to the artboard, and the rulers should display the 0,0 coordinates based on the artboard origin.

    - Anyway, since the current implementation has different behaviors for objects and artboards in the canvas, it seems a not well-thought feature. 

  2. I'm not sure about the position not meaning anything. I work with app design and I use to have many artboards in a single file. I use a lot the artboard position to arrange my artboards, separate them, and prepare them to export. If you try to export a 100x100px artboard that is placed on position 10,5px on the global canvas, Affinity designer will export this artboard adding an extra and transparent pixel, so the artboard will be 100x101px. and with some terrible antialiasing. So I also use the artboard position to fix this issue. Also, I use the position to calculate how much I should move other artboards to place them correctly on the file.

    So in my opinion, having a global absolute value to place the artboards is extremely useful, for many reasons.

  3. 2 hours ago, fde101 said:

    Hmm...  if the artboard is "current" then it makes sense that it would be located at (0, 0) relative to itself, but that is not particularly helpful to the user.

    :35_thinking:

     

    Exactly!

    And there is more to it, @Ben

    1) Let's say, artboard A is X:10 and Y:10, and artboard B is X:0 and Y:0.

    2) When I select artboard A, and then artboard B, the properties panel will first display X:0 Y:0, and then X:-10 Y:-10

     

    I assume that the final "bounding box" of the artboards selected is taking into consideration the initial X and Y values relative to the artboard.

  4. Well, what I have to say about this:

    - People really appear and start asking things out of the topic, and that can be annoying (I think I did it sometimes too).

    - But I also think we could have more participative moderators, to guide and orient the new members of the forum.

    - Sometimes, because of cultural and specific language characteristics, what people type here might seem sarcasm or lack of politeness. So I think that all members should try to be polite in their comments, even when they think that they were not treated with courtesy. 

    - But most of all: if you are not in the mood to write a proper answer to a new and confused member, I think you should avoid joining the discussion because the last thing we want is to make new members feel they are not welcome.

     

    @MCFC_4Heatons This thread is specific to follow up what's coming for Affinity Designer 1.7. You are welcome to read all of @Ben's posts in this thread, where the new features are being showcased. Please try to keep suggestions and feedback on the topic (most of Designer 1.7 features are focused in vector editing), and if you have more suggestions, I recommend that you first take a look at the forum topics to see if they were already approached in some way, so you can contribute to the discussions contextually. If you don't find what you are looking for, you are welcome to create new threads, with your suggestions. I think you have plenty of material to contribute :)

     

  5. 36 minutes ago, Hokusai said:

    If the developers add plugin support for Designer (which I'm guessing they will) and once they do, then it is up to the developers of Zeplin to make sure it works with Designer. 

     

     

    ok, so anyway, you agree that "Zeplin.io integration/cooperation" would be precisely inside the matters of having a plugin support, and that this would precisely attend to what we are asking for?

    I'm a bit confused here, because if the answer is yes, then we are all on the same page :)

     

    I really think that the monetization model should not be the focus of this topic.

  6. On 24/04/2018 at 9:00 PM, Hokusai said:

    I've never understood the appeal of plugins like Zeplin (which is a subscription service). You have to rent your software from Adobe or the makers of Sketch (no thanks) and then you have to rent your plugins too? Where does it end?

     

    Now you have the opportunity to use quality, non-rented software like Designer and Photo and you are asking to be able to add subscription plugins to it? No thanks.

     

    I'll try to best clarify the need to integrate to Zeplin or other third-party solutions for development handover (at least based on my daily experiences working as a UX Designer).

     

    - Once you design a UI, you have to deliver it to developers, in a way they are able to implement the front end as closest as possible to design specifications. 

    - Solutions like Zeplin allow you to, with a single click, upload the whole file to a system that can be accessed by many people (mainly stakeholders and developers), where they can check automatically generated specifications and exportable assets (icons in png, svg, etc), with color swatches, font styles, etc. This saves hours and maybe days of unnecessary work.

    - Platforms like Zeplin have a very specific purpose: allow people to review files and get assets, without the need to install and learn specialized design software (which requires buying more licenses).

    - I freelance for companies which usually pay for Zeplin licenses because the content hosted there is their own property, while the software I use (Affinity, Sketch) is my property. So it does not add extra costs to my budget.

     

    Now, looking at Affinity main features and roadmap, we can tell that they are more focused on illustration than on UI design. They made some effort implementing constraints and symbols, but these features are rather limited at the moment.

     

    I think that implementing something as specific as a "Zeplin" module inside Affinity Designer, with a whole new set of features, would cost some tens of thousands of dollars and would benefit only a portion of their user base.

     

    So, why not provide integration to third-party software like Zeplin, which would be far easier to handle and to give support?

     

    In my opinion, if you don't see advantages in this request, maybe you should just not endorse it, or maybe just give a better alternative. Meanwhile, the almost sole reason why I hadn't adopted Affinity Designer as my main UI design tool, is precisely because of the lack of features like these.

     

     

     

  7. 6 hours ago, rubs said:

    This happens in the Mac OS version too... 

     

    9 hours ago, Ben said:

    I can't talk for constraints, symbols or artboards - I've not had much to do with them.

    @Ben Any chances the other developers that worked in these are looking at this thread? Symbols + constraints are some of the most useful features for screen designers. I was using it a lot, until some bugs started to appear and I ended up losing some hard work...

     

    Anyway, for exporting persona, I'd like to see a way that I could add different slices for the same artboard, but for one slice, I'd like that certain layers would be visible, while for the other slices I'd like that other layers were visible.

     

    So, fo example, If I designed an UI and wanted to export some screens, instead of duplicating the same artboard and showing / hiding layers in each one of those artboards to display certain panels over the screen, I could have only one screen, with different slices with those layers visibility attached to them.

  8. On 17/03/2018 at 5:05 PM, Aaron Martin said:

    Does 1.7 include global style feature? A way to control stroke, gradiant, fx simultaniously in several objects?

     

    I think that @Aaron Martin was pretty clear in what he asked: GLOBAL STYLES.

     

    That means:

    - a set of multiple object properties (fill style, stroke style, brush, effects, gradient, transparency, corner radius, etc) that can be configured and saved in a global styles list, with a user given name;

    - the style can be applied to multiple objects;

    - once the style is updated, all objects with that style applied to them would have their appearance updated in real time, without having to find each one of them, select and then update style, which is a tedious non productive task.

     

    It would also be nice to have:

    - Create a global style from the selected object.

    - Save the global styles in a shareable / external library document

    - An object with a global style applied to it, could have it's properties overwritten, without affecting other objects with the same global style. However, user could be able to "update global style from selected object" or "reset changes to match global style".

  9. 50 minutes ago, Aammppaa said:

    @A_B_C @hperticarati Nested symbols are indeed currently possible, but they are very buggy indeed! The nesting often breaks one or both symbols (orange line in Layers panel becomes dashed) or the symbol simply vanishes (at which point Undo will not bring it back).

     

    Nested symbols are a key feature for me in my work, and at present it is a real struggle to use them :(

     

    Yes, that is precisely what I had in mind... afyer having all my symbols unlinked from master a bunch of times, I’m kinda stucked in the decision of re importing all symbols (which is going to be a lot of work, considering that some of them should have been updated with changes I made directly in their instances), or switching to another tool tha handles symbols with more stability. 

     

    So maybe, instead of asking for “nested symbols”, the key words should be “a more stable symbol workflow”.

  10. On 2/16/2018 at 1:36 PM, Mithferion said:

    You could try with the Transformation Panel. I hove the pointer over the width number and use the mouse wheel (Windows user) to increment/decrement by 1 pixel. I'm sure the gestures on the Touch Pad would do the same.

    Best regards!

    Actually, I use a mouse :) I didn't know about the scroll wheel trick. It's fantastic!

    However, I also think that keyboard shortcuts for that would be great.

    Thanks for the tip!

  11. I really like the responsiveness and immediate feedback about symbols in Affinity.

    But managing them is not as easy as it could be, much of that happens because of the lack of some functionalities in Symbols panel.

     

    What I'd love to see in an updated version of the Symbols Panel:

    • List view
    • Custom categories to groups symbols
    • Search bar
    • Ordering options: manual, alphabetical
    • Easier renaming: select one, double click the name, and when finished, press tab to rename the next one

     

    Features to manage symbols in the artboard:

    • Contextual menu to replace a selected instance of a symbol in the artboard by another one on the library
    • Option to, when cmd+click on the symbol, do not select it's layers, but the whole symbol.
      • (This is useful when you want to select a symbol inside a complex hierarchy of groups and layers, but do not want to edit the symbol.)

     

    Other advanced features

    • Ability to nest symbols inside symbols
    • Ability to override nested symbols

     

    Well, this is what I'd like to see regarding symbols. I hope that this adds something to the discussion about the roadmap. :) 

  12. Wow @Ben, I've just downloaded and watched all the clips with the new features. Well, I'm an UX designer and I've been working a lot with icon design lately, so what got me excited about these new features are all the snapping options for the node tool. REALLY AWESOME.

     

    I'm not sure if this should be posted in this topic, but since it's related to shape manipulation, I was wondering if would it be in your roadmap a set of features to resize shapes with keyboard shortcuts. Similar to what Sketch does:

    • cmd+right arrow to increase width by 1px
    • cmd+left arrow to decrease width by 1px
    • cmd+shift+right arrow to increase by 10px (or specified amount in settings)
    • cmd+shift+left arrow to decrease by 10px (or specified amount in settings)

    Also, differently from what Sketch does, we could benefit from the object origin (pivot), so object could shrink or grow from an specific point relative to the shape, instead of just from top left corner.

     

    Congratulations for the awesome work!

     

  13. I love the constraints feature in Affinity.

     

    But I see three major issues that make its use a little more difficult than it should be:

     

    1. Constraints panel is too big and takes too much space on the screen.

    2. Constraints panel is not related to the transform panel, which is a little odd if you take in consideration that constraints are relevant to object's size and position.

    3. The "Min fit" and "Max fit" icons are not clear about what they are supposed to do (even watching the constraints tutorial, I found it very hard to understand how they behave, and what are the practical applications for them)

     

    So I've drafted this redesign proposal merging Transform panel with Constraints panel.

     

    What do you think? I'd love to see something like this on Designer 1.7 :D

    post-60942-0-97334900-1496725436_thumb.png

×
×
  • Create New...

Important Information

Terms of Use | 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.