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

Search the Community

Showing results for tags 'technical'.

  • Search By Tags

    Type tags separated by commas.
  • Search By Author

Content Type


Forums

  • Affinity Support
    • News and Information
    • Frequently Asked Questions
    • Affinity Support & Questions
    • Feedback & Suggestions
  • Learn and Share
    • Tutorials (Serif and Customer Created Tutorials)
    • Share your work
    • Resources
  • Bug Reporting
    • V2 Bugs found on macOS
    • V2 Bugs found on Windows
    • V2 Bugs found on iPad
    • Reports of Bugs in Affinity Version 1 applications
  • Beta Software Forums
    • 2.4 New Features and Improvements
    • Other New Bugs and Issues in the Betas
    • Beta Software Program Members Area
    • [ARCHIVE] Reports from earlier Affinity betas

Find results in...

Find results that contain...


Date Created

  • Start

    End


Last Updated

  • Start

    End


Filter by number of...

Joined

  • Start

    End


Group


Website URL


Location


Interests


Member Title

Found 6 results

  1. I've been following the forums for a while now since I've decided to switch from the "A" suite and, of all the features requested by users, the most are support for a given file format. Also some users have been heavily requesting for an API they could use to automate stuff (or build stuff - some ideas also came to my mind while writing this) and I think these could be handled with a little bit more of effort in building an API. Since most programming languages are object-oriented I'm also thinking in such terms while I write, however I'm not being specific on language. I believe two kinds of plugins could be allowed: SCRIPTS, which would only help in automating repetitive tasks (think about closing a document for printing) and mostly would only manipulate the document without any sort of argument, and PLUGINS, which would be developed on a chosen platform (I'm pretty sure the Affinity suite relies on .NET) and would enable usage of every feature the platform has to offer. This dual approach is adopted by apps such as ZWCAD and could be great for different uses but it is not a mandatory thing. As for the API itself, the idea would be to enable means to programmatically: access a document (either by creating a new one or retrieving one currently open), layout the document (creating slices on AD or new pages on AP, for example), create, retrieve, modify and/or objects in the document (create shapes, change attributes like colour, add text, etc.), request users to select objects or a point on the document (to ask the user where action will take place). Basically that is allowing anything on an app to be done programatically (yes, with the right script, one could simply automate a complete complex drawing, I'm not asking why would you). I'm thinking of basic object-oriented programming here: // in some pseudo language doc = new document rect = new rectangle object set brush in rect to X add rect to doc ... I'm also well aware the amount of effort and code required to implement this API so I'm not expecting this to be available tomorrow (or in the next version) but I think we'd have to start gathering ideas about this somewhere. Here are some examples of what I would expect that could be achieved with this API: import/export to X file format (PLUGIN): triggered by selecting a file in a recognised format, it would (1) read from a file and create a document and the objects in it using the API representing the contents of the file or (2) traverse a document (or a slice of it in AD) and write it to a file in the chosen format, QR code (PLUGIN): it would open a dialog for the user to enter the info on the QR code (format version, size, tint, text, etc.) and create a group of rectangle objects based on that info. After that, it is just a series or rectangles and does not depend on the plugin (of course this approach does not allow the QR code to be edited, or even its info to be viewed, but I'm sure some other approaches can be taken - like storing arbitrary metadata on objects and groupings and even restricting some of these to be undone), create a draft in PDF format (SCRIPT): this would just add the word "DRAFT" in the background of every page (in a publication - to the original or a copy of the document that exists only in memory), trigger the export to PDF function (it is already embedded on the app, so why not make it accessible) and then remove the "DRAFT" word from every page (since it is not meant to be part of the final document). This could also be done as a PLUGIN if one would like to specify the tag text and colour. Perhaps the biggest concert of Serif in providing us an API is related to security/privacy of its users and that's a noble reason for not releasing an API yet. Of course PLUGINS could be more dangerous than SCRIPTS from this point of view since they have a broader access to the native API of the platform (from enumerating/reading/writing files arbitrarily, to spanning threads, to sending data over the internet) but I've never seen anyone complaining about those issues on Photoshop or any other app that enable the use of plugins. You choose to use plugins from a reliable source and Serif could even be a curator for one of those reliable sources, but nothing mandatory. Another solution to this (and this would take a more considerable amount of time) would be Serif to create a full development platform with each and every API exposed (file access, document access, etc.) in order to minimise the existance of malicious plugins (and someone will always find a way to bypass it, trust me) and restrict programming languages to the one Serif itself choses (I'm not really fond of it but it seems the most claimed in the forums is Javascript). I could live with that with the right API. I'm not in anyway affiliated with Serif and I don't know if they have already decided on any of the issues I raised and my intent here is not to discuss the exact implementation the API will take (thou it could certainly be fun) but to gather opinions on it, specially on whether the API should use an open platform or a more strict one to prevent malicious extensions, and to gather things people would be interested in doing with the API and are not sure I covered above. I would also like if this space were to be used by Serif to talk to us about how they view the issue of the API and how/when they are planning to handle it and to it discuss with us in order to create something really useful for everyone.
  2. Hello all, I am looking to upgrade my basic iPad and was wondering if the new iPad Air 256g with the A14 Bionic chip with 64‑bit architecture will be powerful enough to run Affinity for iPad, I have a basic iPad 6th Generation, which often struggles with the layers, bless its only 64G. Others have suggested an iPad Pro, the new Air has a newer and allegedly faster chip. Don't want to purchase the wrong product. Thanks in advance Alex
  3. So I just bought Affinity Photo for my windows 10 pc, No viruses, malware, etc on this computer; I cannot open the application to begin with; there's nothing popping up on the screen, or anything of the sort, there's a small blue ball spinning by the cursor and then nothing happens, nothing in the task manager is open, which means the computer isn't even opening the application, I installed it on the default directory which is the C drive for me, I need some help because I got this for half off with the deal they're having and I hope that I can use it soon, can anyone help me? I used a PowerShell command to check the integrity of all the files on my computer, no corrupted files from windows and the such. Please, if anyone can help it'd be greatly appreciated. Thank you in advance, stay safe and take care of yourselves as well.
  4. HELLO, I'M CAM AND I'VE BEEN WORKING WITH AFFINITY PHOTO FOR A LITTLE WHILE NOW. I HAVE NOT HAD THIS ISSUE TILL RECENTLY, HONESTLY I'M NOT SURE WHY. BUT WHEN I FIRST USED THE SOFTWARE I WOULD DRAG AN IMAGE TO LAYER BEHIND THE BACKGROUND. BASICALLY REPEATING THE SAME TECHNIQUE TO GET THE BACK BACKGROUND BUT OBVIOUSLY THE APP TITLES IT AS "IMAGE" BECAUSE WE ALREADY HAVE A BACKGROUND. SIMPLE STUFF, BUT FOR SOME REASON MY IMAGE LAYER IS SHOWING THE PICTURE I HAVE DRAGGED OUT OF MY FILES IN THE BOTTOM RIGHT LAYERS AREA... YET WHEN I CLICK THE CHECK ON MY BACKGROUND TO SEE THE NEW IMAGE WITH OUT THE BACKGROUND IT SHOWS A BLANK PIXEL LAYER.... WHICH DID NOT HAPPEN BEFORE. SOME PLEASE HELP IM SURE ITS AN EASY FIX BUT RIGHT NOW I CANT SEEM TO FIGURE IT OUT. THANKS
  5. HI guys, the is my first work made with AD, normally I use AI (Mac) and CorelDraw (depends on the job). vectors only, AD is a nice App!
  6. My first vector work and my first time using Affinity Designer, some 1980's and 1990's computers for a project I'm working on.
×
×
  • 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.