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

Frank Jonen

Members
  • Posts

    382
  • Joined

  • Last visited

Reputation Activity

  1. Like
    Frank Jonen reacted to michalmph in Scripting   
    @Jon W@Tim France@kimtorch Guys, this is it. This is probably the most important event in this thread, next to the actual feature announcement.
    I understand Kim's irritation. Let's just get over this and work towards a good scripting system that recognizes client's needs.
    I come from the graphic design side. I barely dealt with in-line text formatting. The 400 pages catalog took 24-27 minutes when rendered to viewport in InDesign CS6. This process required saving every 15 pages so InDesign would clear an internal memory buffer, otherwise it could crash randomly. I couldn't get it to work headlessly or by generating the IDML, and there was never time to refactor.
    To give you a scope of the problem:
    I had no idea about the text formatting tags. No one taught me that. I didn't find it in the documentation. I didn't know it existed. I used InDesign's built in formatting tools to set styles (line numbers, paragraphs, etc). I can write an RPA that syncs multi-user input from Photoshop and Illustrator, merge them into an individual asset, and push it to a desired position in an InDesign doc. Or do automatic asset management if you need to develop POS for 30 store locations, each with different dimensional requirements. I could stack hundreds of regexes to process stuff without conflicts. But I didn't know about the text tags up till now. (thanks btw :D).
    I'd suggest you guys figure out how to get meaningful feedback that would let you write a feature spec and gather necessary documentation reference. This thread is peanut gallery, and we need an actual need assessment, and features based on the results.
  2. Like
    Frank Jonen reacted to lpm in Add Markdown file support   
    Hello, fellow creatives and Affinity Publisher enthusiasts,
    As we navigate through the myriad of tools and formats in our digital workflows, one feature request seems to recur within this forum with noticeable frequency: the integration of markdown (md) import capabilities into Affinity Publisher 2.
    Many of us have adopted various workarounds to bridge this gap, such as utilizing the Ulysses app to export md files to docx format—a solution I have personally relied on. However, with the ever-evolving landscape of digital tools, adaptability becomes a challenge. My recent transition to JetBrains Writerside, for drafting and online work, illustrates this perfectly. Writerside’s export limitations to pdf, coupled with Affinity Publisher’s less-than-ideal handling of multi-page text pdfs, underscore a significant workflow disruption. This scenario often leaves us resorting to the cumbersome process of cutting and pasting markdown text directly into Publisher. While this workaround suffices for transferring plain text, it falls short when dealing with md’s more complex features, such as code blocks or tables.
    The essence of our workflows today is increasingly intertwined with markdown due to its simplicity, versatility, and widespread adoption. It is curious, then, that a tool as sophisticated as Affinity Publisher does not yet support markdown in a manner akin to its handling of txt, docx, and rtf file formats. This oversight not only hampers efficiency but also limits the creative potential of those who prefer or are required to work in markdown.
    Incorporating markdown import functionality into Affinity Publisher 2 would significantly streamline the workflow for a vast array of users, eliminating cumbersome workarounds and fostering a more seamless integration of ideas and content. Such an enhancement would not only acknowledge the evolving needs of the digital publishing community but also affirm Affinity’s commitment to user-centric innovation.
    Let’s discuss how this feature could reshape our workflows and potentially elevate the utility and versatility of Affinity Publisher. Your thoughts, experiences, and any additional workaround insights are warmly welcomed and highly appreciated as we collectively advocate for a markdown-friendly future in Affinity Publisher.
    Thank you for considering this feature request and for your ongoing contributions to making Affinity Publisher a tool that truly meets the needs of its user base.
  3. Like
    Frank Jonen got a reaction from Bryan Rieger in Add Markdown file support   
    Pretty much every publishing house is looking for ways to reduce overhead. The first who makes a good enough effort in this space, wins.
  4. Like
    Frank Jonen got a reaction from PaoloT in Add Markdown file support   
    This should've been in the previous release but here it is again. Markdown import so we don't have to convert to legacy formats or use crude copy & paste for each article.
    Solution: Link Markdown files to text frames like the data merge preview.
    That way the documents can be worked on by writers/editors and kept up-to-date via the Resource Manager.
  5. Like
    Frank Jonen got a reaction from PaoloT in Add Markdown file support   
    Pretty much every publishing house is looking for ways to reduce overhead. The first who makes a good enough effort in this space, wins.
  6. Like
    Frank Jonen got a reaction from ben_zen in Add Markdown file support   
    The thing is, this is really easy (I wrote a basic parser that uses frontmatter). Publisher has all the building blocks for it. Yet for some reason they keep deciding against it.
    My experiment with MD in in Publisher was leveraging that. I used the data import for JSON files with veeeery long strings. Each section was stored in its own string value and each chapter as a separate file. The Affinity RegEx limitations ruined it though. You can't automate anything, you have to launch each element replacement and each markup deletion manually for each element group. Takes forever and is error prone. Hence "not worth the effort".
  7. Like
    Frank Jonen got a reaction from PaoloT in Add Markdown file support   
    The thing is, this is really easy (I wrote a basic parser that uses frontmatter). Publisher has all the building blocks for it. Yet for some reason they keep deciding against it.
    My experiment with MD in in Publisher was leveraging that. I used the data import for JSON files with veeeery long strings. Each section was stored in its own string value and each chapter as a separate file. The Affinity RegEx limitations ruined it though. You can't automate anything, you have to launch each element replacement and each markup deletion manually for each element group. Takes forever and is error prone. Hence "not worth the effort".
  8. Like
    Frank Jonen got a reaction from mattaudio in Scaling designs with contraints   
    Anything yet? 
  9. Like
    Frank Jonen got a reaction from Megnusin in Scaling designs with contraints   
    Anything yet? 
  10. Like
    Frank Jonen got a reaction from Ronbo in How to rotate canvas in Affinity Photo on desctop PC   
    Stop giving people harmful advice!
    This answer (and those of the same ilk) should be removed by a moderator or at least flagged as inaccurate as following it will lead to data loss.
    When you crop-rotate a document, you're changing the document itself. The pixels themselves are being changed. Do that a couple of times and you end up with a blurry image and you have to go back to an older backup, losing all the work you did since.
    When you rotate the viewer canvas, you rotate the viewer canvas, nothing about the document changes.
     
  11. Like
    Frank Jonen got a reaction from Ronbo in How to rotate canvas in Affinity Photo on desctop PC   
    Yeah the canvas rotation bug doesn't ever seem to get fixed. It's highly annoying that on a normal working setup you're crippled with step-rotation. Why it doesn't have a key combo that you can hold while dragging to rotate is beyond me.
  12. Like
    Frank Jonen got a reaction from deeds in Find & Replace Tool for Affinity Designer   
    And if my grandma had wheels she'd be a bicycle.
    This was about Designer, not Publisher.
  13. Like
    Frank Jonen got a reaction from krbo in Remove the stupid export preview   
    Why is that even in there? Who went "here's a brilliant idea, let's waste the user's time by forcing them to wait on a beachball for each and every settings change"?! WTF. I wish upon that person zero trusts in their farts for the rest of their life.
  14. Like
    Frank Jonen reacted to debraspicher in Remove the stupid export preview   
    I would've thought surely they'd optimized everything before it were made so preview was the default. Especially so as to not hog other system resources unintentionally. I will say that my impressions is that sometimes the programs are more resource heavy in areas it really shouldn't be. Other programs can do the same functionality without locking the machine up until it finishes. It was mentioned in another thread by a mod that the program pegging CPU to 100% is desired behavior and I remember in the past them saying it is normal for the program to take advantage of every bit of hardware available to it. Which sounds good in theory, but I'm not so sure in practice (leaning more towards unoptimized code). It assumes a lot of about our machines, available resources, etc. I'm not saying it should be able to run on a potato, but maybe not so easily lock up doing simple functions if the tasks are repetitive (if that makes sense)...
  15. Haha
    Frank Jonen got a reaction from PaoloT in Remove the stupid export preview   
    Why is that even in there? Who went "here's a brilliant idea, let's waste the user's time by forcing them to wait on a beachball for each and every settings change"?! WTF. I wish upon that person zero trusts in their farts for the rest of their life.
  16. Like
    Frank Jonen reacted to ashf in Remove the stupid export preview   
    Would be nice if it's possible to set the default state to show/hide the preview in the preferences.
  17. Like
    Frank Jonen got a reaction from deeds in Remove the stupid export preview   
    Should be optional.
    For my use, I compress from an uncompressed, flattened master file. Saves a lot of time. So there that'd hinder me as well. For people who want to go straight to final and tinker around with each image, it could be useful to wait around and fiddle. It doesn't even have a region of interest selection, you always have to wait for the entire layer stack to render.
    I now shudder at the prospect of having to do actual work in Photo which also has this crap now. I have composites of several GB. If I have to wait for that shit, I'm done with Affinity. That's atrocious.
  18. Thanks
    Frank Jonen got a reaction from tlueck in Add Markdown file support   
    This should've been in the previous release but here it is again. Markdown import so we don't have to convert to legacy formats or use crude copy & paste for each article.
    Solution: Link Markdown files to text frames like the data merge preview.
    That way the documents can be worked on by writers/editors and kept up-to-date via the Resource Manager.
  19. Confused
    Frank Jonen got a reaction from 4dimage in Remove the stupid export preview   
    Should be optional.
    For my use, I compress from an uncompressed, flattened master file. Saves a lot of time. So there that'd hinder me as well. For people who want to go straight to final and tinker around with each image, it could be useful to wait around and fiddle. It doesn't even have a region of interest selection, you always have to wait for the entire layer stack to render.
    I now shudder at the prospect of having to do actual work in Photo which also has this crap now. I have composites of several GB. If I have to wait for that shit, I'm done with Affinity. That's atrocious.
  20. Like
    Frank Jonen got a reaction from ashf in Remove the stupid export preview   
    Should be optional.
    For my use, I compress from an uncompressed, flattened master file. Saves a lot of time. So there that'd hinder me as well. For people who want to go straight to final and tinker around with each image, it could be useful to wait around and fiddle. It doesn't even have a region of interest selection, you always have to wait for the entire layer stack to render.
    I now shudder at the prospect of having to do actual work in Photo which also has this crap now. I have composites of several GB. If I have to wait for that shit, I'm done with Affinity. That's atrocious.
  21. Confused
    Frank Jonen got a reaction from 4dimage in Remove the stupid export preview   
    Why is that even in there? Who went "here's a brilliant idea, let's waste the user's time by forcing them to wait on a beachball for each and every settings change"?! WTF. I wish upon that person zero trusts in their farts for the rest of their life.
  22. Like
    Frank Jonen got a reaction from JeroenC in Add Markdown file support   
    This should've been in the previous release but here it is again. Markdown import so we don't have to convert to legacy formats or use crude copy & paste for each article.
    Solution: Link Markdown files to text frames like the data merge preview.
    That way the documents can be worked on by writers/editors and kept up-to-date via the Resource Manager.
  23. Haha
    Frank Jonen got a reaction from thomasp in Remove the stupid export preview   
    Why is that even in there? Who went "here's a brilliant idea, let's waste the user's time by forcing them to wait on a beachball for each and every settings change"?! WTF. I wish upon that person zero trusts in their farts for the rest of their life.
  24. Confused
    Frank Jonen got a reaction from VectorVonDoom in Remove the stupid export preview   
    Why is that even in there? Who went "here's a brilliant idea, let's waste the user's time by forcing them to wait on a beachball for each and every settings change"?! WTF. I wish upon that person zero trusts in their farts for the rest of their life.
  25. Confused
    Frank Jonen got a reaction from Tia Lapis in Remove the stupid export preview   
    Why is that even in there? Who went "here's a brilliant idea, let's waste the user's time by forcing them to wait on a beachball for each and every settings change"?! WTF. I wish upon that person zero trusts in their farts for the rest of their life.
×
×
  • 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.