Jump to content

hperticarati

Members
  • Content count

    27
  • Joined

  • Last visited

About hperticarati

  • Rank
    Newbie

Recent Profile Visitors

310 profile views
  1. 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
  2. @Hokusai I've sent emails for both Affinity and Zeplin support teams. Affinity team said that plugins are not on the roadmap right now, and Zeplin team said that they can't implement the integration with Affinity because there's not a plugin or API system. Maybe we should just create this new topic asking for a plugin system.
  3. 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.
  4. 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.
  5. This happens in the Mac OS version too... @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.
  6. lol I've missed it. +1 to it have being done!
  7. +1 to scale and transform a node selection, the way Inkscape does
  8. 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. 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. @Chris_K thank you, the file is working properly again! Please send my acknowledgment to the developers
  11. hperticarati

    Symbols being unlinked without reason

    Hi Chris_K! Thanks for answering I usually press cmd+J and then drag the artboard, or I hold option key while dragging the name of the artboard on the viewport. Unfortunately, I can't tell which one caused the unlinking, because I use both methods regularly.
  12. hperticarati

    Symbols being unlinked without reason

    I've been making some experiments, trying to design a new version to the open source software Inkscape. For that, I'm using symbols feature a lot: I have an artboard with the icons I'm designing, and another artboard with the actual UI where they are used. All my icons are symbols, and I copy them to the other artboard, so I can look at my icon set as whole, but I can also look at he icons applied to the UI. Using symbols inside constraint groups are not being as delightful as it could be (I have another opened thread about this: ) But now I'm facing a whole new problem with symbols: All symbols in one of the artboards are spontaneously disconnecting from the "master symbol", so if I change one icon, the change won't appear in the UI. Apparently, this could have happened when duplicating the UI artboard a couple of times. Unfortunately, it is a very tedious task to start replacing all the icons manually. Had anybody hear passed by a similar situation?
  13. 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!
  14. Hey guys, I've just started a thread about Symbols and Symbols Panel features: I think that this could be relevant for affinity roadmap, but I didn't want to start a side discussion here. Check it if you are interested, and leave your thoughts
  15. 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.
×