Jump to content

Search the Community

Showing results for tags 'documentation'.



More search options

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Affinity Support & Questions
    • Feature Requests, Suggestions & Discussions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • Report a Bug in Affinity Designer
    • Report a Bug in Affinity Photo
    • Report a Bug in Affinity Publisher
    • (Pre 1.7) Affinity Range Bugs Forums
  • Beta Software Forums
    • Affinity Designer Beta Forums
    • Affinity Photo Beta Forums
    • Affinity Publisher Beta Forums

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


AIM


MSN


Website URL


ICQ


Yahoo


Jabber


Skype


Location


Interests

Found 10 results

  1. Hey all, Long time lurker til the last few weeks when I reinstalled the Publisher beta to check up on it - I understand that AFP is predominantly a page layout focussed system (and after reading all the ePub threads I see that's a bug-bear for many people and I suspect "Affinity Writer" might be a good direction/bridge but let's avoid that for now). I see that we can link/embed images so we can update the visual assets independently of the layout, but I've not seen anything similar for textual assets - which when writing more book/manual type content would be rather useful. Coming from the tech world (software developer primarily) what I'd love to see is something like the following (that may be doable with simple scripting if/when that comes available): Write my main content in a .txt file, or .md Markdown file - which is becoming a de facto markup format in the developer world Processor app/script that takes the markdown, and converts that to a AFP source - mapping the relevant heading 1/2/3, bullet point, body, code styles to AFP styles before including that in an initial text frame. Content appears in AFP rendered, with styles applied This would allow me update the .md files independent of page layout, using an editing environment more suited to writing content, running the document thru Grammarly/ProWritingAid. I guess this could all come under a "Writing" persona. Is this is a crazy idea, or something worth thinking about? ´╗┐
  2. Stokestack

    The Help file is blank

    Anyone notice that the Help appears to be totally blank in 1.6.1? Check out this informative topic lookup. AffinityNoHelp.mov
  3. Hello ! Quite a few times, I find myself in a situation where being able to handle/modify .afdesign and .afphoto programmatically would have been really handy. However, after a couple of google searches, I couldn't find any information about those formats. I've tried to decompile the AD and AP apps using decompiler such as dotPeek and dnSpy, but didn't make any progress. Analyzing the files with binwalk or strings was of no help either. Now, I'd like to develop a tool that would generate .afdesign files based on user input, and it is impossible to do without even any basic information about this format. Anyway, as you've probably guessed, I'm posting here to ask if we could get some information about the files formats. I know writing documentation for a piece of software instead of working on new features or patching bugs can be really boring and time-consuming, so I'm not asking you for a full-blown documentation, but at least a sufficient level of information to work with those files programmatically and maybe being able to create/modify them, that may include the different memory sections/segments, how shapes/colours/palettes/text/filters/effects/references are stored, etc... I know it's probably not gonna happen, because it's too time-consuming or costs too much, but I sincerely hope that it will be a resource soon available to the community. Thanks for reading, waiting for your reply.
  4. John Rostron

    Error in documentation

    In the Help Page on Field Epressions´╗┐, in the section on general arithmetic, that for input '/2', the result is 'divide by a half'! I am told that this error is present in both the Windows and the Mac versions, and in both 1.6 and 1.7. John
  5. Please, can you release an "official" version of the online manual in PDF format??? Or any other format that I can download and read on something other than my computer when Affinity is running??? I frequently travel to places where an internet connection is unavailable (one of the reasons I use Affinity instead of the cussed subscription only program) so the live website is not always available to me. I learn programs like this by reading and studying the manual, over and over. It is my bedtime reading. I can't take my computer to bed like I can my iPad... Right now the only way I can do this is an out of date "pirated" version. This is not hard if you have all the text in hand.
  6. I was wondering if it would be interesting to create space for a notes field in the file properties (I'm aware I'm opening a can of worms there, IMHO there should also be room for data such as creator, company and copyright which then inevitably segways into a discussion about EXIF data too - allow me to stay away from that for now). I've seen someone talk about a description/information layer but that's inside the design, what I'm talking about is the ability to store meta data with the document which describes content, with or without tags and other fun stuff that you could actually search for if the search facility, file system or DAM supports it. At the moment, the only means to store data with a design is to add a box somewhere with some description or rely on a DAM to add external tags to a file which can get lost and which do not travel with the file in a makeshift collaborative environment. Ironically, document properties are a default feature in wordprocessors such as MS Office and LibreOffice which are the one facility that needs it less because you can actually search in the file contents - no such luck with graphics.. Opinion?
  7. Just a tiddler for the documentation folks. AP 1.6. Go to Help. Search on 'colour management'. First item on 'Colour management' says 'Set up colour profiles for colour mmanagement'. Ooh.
  8. Hi. Recently I wanted to make an Affinity Designer importer for Unity3D, but I didn't find any documentation about what are the Affinity files and there is no documentation about it. It would be awesome to have some information about them, then we will be able to add some more plugins and importers and extend affinity designer. For example, we need documentation for .afphoto and .afdesign files. Thanks.
  9. F1gur471v31y_5p34k1ng

    You know what would be helpful.

    What would be of great value is to have the documentation that is found by clicking the ? in the landing page of AF. This is really a terrific resource, but it is a nuisance to have to exit out of an editing session and then navigate back to the landing page to make a query and search the documentation. Rinse, Repeat & Recycle. Is it possible to have this content published into a document or better: port the content and make it available online? Thoughts?
  10. This would be awfully useful for anyone that uses AD for design work. Especially web and UI designers that work together with developers and need to give them the full detail of the design.
×