Jump to content


  • Content count

  • Joined

  • Last visited

About JGD

Profile Information

  • Gender
  • Location
    Lisbon, Portugal
  • Interests
    Typography, type design, modular geometric type design, grid systems, information design

Recent Profile Visitors

1,244 profile views
  1. This is way too complicated to describe in detail, and you know I have a penchant to write 300-page essays on simple stuff, so… please just watch the video and tell me what you think. index bugs.mov Basically the Index panel is all over the place, and when it reaches the final state, when the “Options” section disappears altogether, it becomes unusable. And this is completely reproducible, by the way. The only way to restore it is by force-quitting Publisher Beta, and I haven't even tried quitting and restarting it properly out of fear that the Index panel might become corrupted for good and force me to trash Publisher's preferences. I will try making a backup of those and see if a soft relaunch does the trick, though.
  2. Thank you. For your remarks and especially your demo, which I should've done earlier but now you saved me the trouble. I never did a full degree in UX/UI, but I did study ergonomics at my Uni and, you know, being a communication designer and all, I'm extra sensitive to this kind of stuff. I've been reading on it a lot since I got an internet connection, and probably knew about UX principles like Fitts's Law back when I was 17 (shortly before switching to the Mac, which makes extensive use of it; I eventually learnt about it by starting here: https://guidebookgallery.org ). And I do remember recognising Windows 95 as a Mac OS clone from having used System 7 on a friend's Mac Color Classic a handful of times (and, conversely, remembering just how similar the latter was to Digital Research's GEM, way before I learnt about Apple's lawsuit against that company), and noticing even the minute differences between Windows 3.0 and 3.1, so I definitely had an eye for it even earlier still (yeah, as far back as when I was six/seven years old!). It doesn't take a degree, or working professionally in the field, to know that needlessly obscuring UI chrome is a big no-no, but it's refreshing to finally see someone who is incidentally very much in Serif's target demographic chime in. As for users shrugging and moving on, I agree, but I'll add that a crucial detail, “to where”, depends on a few factors. If they can afford a CC subscription, they may shrug their shoulders and… move back whence they came. Considering its promise, it would be a very sad state of affairs if a sizeable portion of Affinity users were just silently tolerating it because it's cheap and they have already invested on a license.
  3. Well, duh. Also this. It's either a case of lack of testing, lack of use, or both. Devs are, first and foremost, devs, not designers, and even if they dabble with their own apps every now and then, they only do that, dabble. These apps aren't something like Brent Simmon's awesome new NetNewsWire, i.e. a simple but generic app that anyone may use daily, including the head developer himself. Also, sure, we know for a fact that Serif does have an in-house design team, but if not a single one of its members uses separated mode, boom, it ceases to be a priority. And if none of the 90%ile target demographic for their apps, i.e. digital illustrators/photographers on a budget on small 13'' or 15'' MacBooks and PC laptops, use it either, boom, it will stay that way. Serif desperately needs professional testers on their QA team, even if it means hiking prices a bit. I've said it before, and I'll say it again.
  4. Again, devs beware. When users do this, in the middle of August, it means that it's serious. “Lousy” and “irritating”, is even stronger language than my own at my worst, wow. But I concur; it is, indeed, “lousy UX”. Sure, it may affect 0,0001% of your user base, or some person who opened the trial just to check the app out, but… what if it's another influencer? Separated Mode is a complete, useless shambles, and it does Serif no favours having it in its current state on a shipping product. It feels more of a bug than a conscious decision.
  5. A million times this. There are a lot of shortcomings in Affinity apps that I let slide; it's only when I get into “it doesn't feel good” territory that I actually take the time to come here and create entire threads on those. Just a heads up, in case you find any other shortcomings yourself and feel the need to point them out: you should either get a thousand reactions and replies to your thread, or produce a >100 word request in the first place; otherwise, the Serif team will outright ignore you, no matter how sound your argument is. [Funnily enough, that reply was exactly 100 words long, ha. Guess my training here on the forums has paid off, after all. ]
  6. All fixes to font rendering and embedding, especially when it comes to OpenType features, deserve my sincere commendation. It's good to know that Publisher will play well with those in all scenarios and that advanced typography is a true priority at Serif. A good “set-it-and-forget-it” default preset that preserves type designers' hard word and prevents end-user confusion – which might otherwise turn them away from those features – is always a win in my book.
  7. Both fair and related points. If Serif ever becomes big enough to manage such a diverse forum – and keep it civil; otherwise, what's the point? –, it will be a welcome addition, but I think we will all have to agree that making do for now is an acceptable compromise. I, for one, don't mind discussing those issues and be educated on the matter if need be via PM. Anyhoo, and back to the topic at hand, I'll translate my latest observations into animated demos soon. You know, to make it easier for the team at Serif. Stay tuned! As for modifiers and the way they are totally scrambled, eh. This isn't the right place to discuss that, either, and the subject probably warrants its own thread. Once this low-hanging fruit (because that's what “ghosts” are) is addressed, we should consider creating one. If any of you think it's a priority, sure, go ahead and do it right away, and you'll have my full support; but I, for one, don't, and am picking my “battles”, so to speak.
  8. Yeah, you are, for the most part, correct. In any case and by the way, I'm probably the worst offender when it comes to all things off-topic. Still, don't you reckon that if the user count booms it may one day become necessary (even if you personally don't use it, which is just fine anyway)? Just a thought.
  9. I was, obviously, being a bit facetious with my remark. I will say, however, that as a native Portuguese speaker, I understand and agree with most (if not all) points you made. If the mods wish to move that discussion to an off-topic thread (and Affinity forums could certainly use an “off-topic” section; call it “Community”, or something), I'd be more than happy to comment on them. I do have some likely interesting thoughts on the matter but, as it stands and for approximately the same reasons you mentioned (I wouldn't go as far as calling the topic “PC ‘garbage’”, but I do agree it sometimes breaks the flow of debate), I won't be adding them here. I'm already verbose enough when it comes to my tools, haha.
  10. Even when Apple is explicit, they sometimes leave some stuff omitted (and I can't seem to find anything on Command+dragging), but the best practice is to keep it as consistent with the pre-installed apps (and not necessarily all the first-party ones – do you guys remember the dark days of “brushed metal”? And what about GarageBand and its wooden trim? –, but mostly those, too) as humanly possible. As for the other modifiers and the Pen Tool, I haven't tested them enough for that to be able to express a final opinion on that. But I will stress that Command+dragging should not result in duplication, ever. If it even nullifies it in, of all apps, the Finder, it stands to reason that it should never, ever do the opposite. No matter what ergonomics tell you. In my 16+ years of experience as a Mac user, I can assure you that's just not how 99% of macOS apps are developed, period. @Ben, this shouldn't be a case of accommodating users who “can't cope” with a non-standard behaviour (there's so much troubling stuff to unpack in that statement that I don't know where to begin), but instead fixing something that was patently wrong in the first place. If you wish to make things simpler and have two modes in Affinity apps, “Standard” and “Optimised for Ergonomics”, so be it, but at least respect conventions in some way and give users, pun unintended, some options on the matter. Look, I've studied ergonomics. I know that if I'm not careful enough I may get RSI and CPS (if I don't suffer from them already; I'm 34 and have been working and playing with PCs since I was 7, after all…), so you're preaching to the choir, here. But the default behaviour should always be to have shortcuts (all of them, as in both key combos and mouse+modifier combos) be as consistent with the host OS and apps as possible. And if someone is such a power user that having to move one of their fingers an extra inch might cause them RSI or slow them down considerably, add it as an alternative preference for them, then. Or if you're so afraid that users will injure themselves with (or be pissed about) that new default, keep this current weird behaviour as it is and add the other one for “lite” users (which, as it has been so eloquently stated here more than once, may eventually become your biggest user group) who may enjoy a bigger level of consistency across their OS. Those are the ones who will, after all, be using other first- and third-party apps for longer and who'll have to face the worst muscle memory conflicts when firing up Affinity apps (if you're a power user, you may deal with those conflicts more frequently and, bothersome as they may be, you eventually get used to them, just as I did when I had to deal with that “UX turd” of an app that was QuarkXPress; “lite” users, on the other hand, will just get frustrated all the time).
  11. Not explicitly as such, but implicitly, yes. Much like there's the letter of the law, and the spirit of the law, if the only mention (that I could find, at least) [see: Pointers > Drag copy] in Apple's HIG to Option+dragging is to a cursor (which, while I'm at it, you should consider using if this “ghost” functionality is to be implemented, to further visually distinguish such a “dragCopy” operation from a regular operation), well… you're not supposed to use other modifiers for the same function. UX redundancy in such a context is undesirable. It's not different enough to feel like it's an alternative (like, say, an explicit duplicate command, with a menu item and a keyboard shortcut of its own, or regular ol' copy'n'paste) and confuses the user instead. Why you're still arguing with me about this eludes me, and just feels petty at this point. I'll suggest you try doing other Modifier+drag operations in other apps just to see what they do, but I can assure you (and I'll bet both my kidneys on it) that it's never a duplication. Control+dragging is probably not even an option in most cases (see: Keyboard > Keyboard Shortcuts > Defining Keyboard Shortcuts): As for Command+dragging, in the Finder, for instance, it forces it to always move a file even when the default, unmodified action would be to copy (such as when dragging to any kind of external R/W media); perhaps Command+dragging objects across Affinity apps could have the same effect, and I'd expect all other apps to adhere to this convention – written or otherwise…
  12. Well… On the other hand, many Corel users are running oooooold versions. They just keep on going. And legally so, because, you know, perpetual licenses. Offering them something new and fresh, that respects some of their favourite app's conventions (at least when it comes to object selection, which is a biggie) and optimizes the UI/UX greatly, might be an interesting value proposition.
  13. Fair enough. “Gentleperson” it is, then, since there aren't, AFAIK, gender-neutral honorific titles (though the good people at Serif, being British subjects and all, might be able to enlighten us on those. ).
  14. Isn't the last screenshot actually of Mac Paint? I mean, compare it to the screenshot on its Wikipedia entry; it is Mac Paint. So… you're absolutely right, Apple came up with that UI, in 1984. https://en.wikipedia.org/wiki/MacPaint#/media/File:MacpaintWP.png
  15. Yet more interesting clarification. You, sir, are on to something. That would make a lot of people very happy. Serif would totally kill Corel if they did that, by the way. The market you're describing seems to be very much dominated by them (here in Portugal, at least). And once they had those niches nailed, they could then go on to fry the bigger fish.