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

angelhdz12

Members
  • Posts

    201
  • Joined

  • Last visited

Reputation Activity

  1. Haha
    angelhdz12 got a reaction from chessboard in Scripting   
    import {app, type Document} from 'affinity/app' import {ArtisticText} from 'affinity/tools' const doc: Document = app.documents.current doc.insert(new ArtisticText('Affinity Scripting API, let\'s go!!!🔥🎉👀😍👏'))  
  2. Like
    angelhdz12 reacted to Affinity__User in Scripting   
    @Tim France
    I hope those involved within Affinity will benefit greatly from the increased investment now with the Canva acquisition. This scripting feature within Affinity is assuredly a highly requested feature over the years. Regarding those coming directly from Adobe / ExtendScript along with Affinity users in general.
    What you've shown as a sneak peek looks wonderful. 😍
  3. Like
    angelhdz12 reacted to chessboard in Questions on Canva acquiring Affinity   
    I've been in the graphics business since the early 90s and have seen a few of these takeovers. Experience teaches us not to trust the acquiring company, because these companies are primarily interested in the customer base of the acquired company and the money of its users, not in making the products better.
    And the announcements about the pricing model are just as similar as the statements made by the CEOs of the acquired companies. "A great future in a great partnership with the new partner. Great things are already shining on the horizon." And so on, and so on. All heard umpteen times before. And the real development has been seen umpteen times.
    And the contributions to the discussion are the same every time, including the call to have a little faith in the companies. It's all been done before.
  4. Haha
    angelhdz12 reacted to voitek in Questions on Canva acquiring Affinity   
    Aged like milk. 

  5. Like
    angelhdz12 reacted to Tim France in Scripting   
    This.
    The scripting devs are going to have to dedicate a significant amount of time towards documentation. We can't expect our docs team to document the ins and outs of an API (technically multiple APIs), it's simply not fair or realistic. Besides, we'd have to tell them what to write, which would mean pretty much writing the documentation anyway. Sure, they'll be able to present it in a way that looks good and integrated with the normal app documentation, but the devs are going to have to provide much of the content.
    We're planning to use one of the many available documentation tools to do most of actual generation for us. The current favourite is Doxygen, largely because most of us have had at least some exposure to it.
    Please remember too that the scripting team sometimes has to do bits of work away from scripting development. As the dev who wrote the DWG/DXF importer (and now exporter - see here 🙂), I tend to be the one tasked with its fixes and improvements. The same goes for Move and Shape Data Entry. Everyone in dev could put in those fixes, but it makes so much more sense if I do them because I'm most familiar with the code and should be able to do the work faster. The members of the scripting team do spend most of their time doing scripting work, but it's not 100%.
  6. Like
    angelhdz12 reacted to Seneca in Scripting   
    Any progress report on this front is more than appreciated.
    From what I know a lot of new development in inDesign is done in JavaScript, so I'm not surprised at all that JavaScript is performing so well in Affinity apps too.
  7. Like
    angelhdz12 reacted to CM0 in Scripting   
    I sincerely appreciate the time to just drop a small comment here and let us know a bit how things are going.
  8. Like
    angelhdz12 reacted to Tim France in Scripting   
    Hi all,
    The team has been making good progress. I don't have any updates on a release date but please be assured we are not sitting on our haunches - we want to get this feature out as much as you want it out!
    Naturally we've been exposing more of the apps' functionality to scripts, but we've been working on plugin-specific technology too. For example, there's a new asynchronous file i/o and networking API, initially driven by the Javascript layer but then we thought it would be good for the lower level C/C++ plugins to have access too. Obviously with local and remote i/o, we've had to be careful that a script isn't covertly sending user data somewhere, so we've introduced a permissions system for Javascript plugins - unless you allow a particular script network access, it won't be able to use the networking API. It may not be a big shiny WOW! feature, but it's important to get these things right.
    Anecdotally, I can tell you we've actually used some scripts internally to do some genuinely useful stuff that would have taken literally days to do manually. One script I wrote optimised a document and removed about 60000 layers. There have also been relatively simple layout and alignment tasks that scripts can munch through in the blink of an eye. Last week I wrote a script that split a pixel layer into new pixel layers containing the blocks of grouped pixels. Even the pixel processing was done in the script - I didn't have to rely on the app to do the heavy lifting for me because our performance is good enough to implement DBSCAN in Javascript.
    Please be patient. We know you all want scripting available yesterday, but we're getting there!
  9. Like
    angelhdz12 reacted to Pan Przemysław in No backwards compatibility??   
    Oh wow, I just realized the backward (in)compatibility issue. I designed a menu for a friend's restaurant and recommended that they buy a license of Designer to make edits to the ever-changing menu. They bought the license and we have been co-editing the afdesign files for the last six months. And then I upgraded to Affinity 2 and my files are no longer compatible with my client's program. They are willing to upgrade, but still..
  10. Like
    angelhdz12 reacted to Jon_TA in Scripting   
    I am very glad the Affinity Team is getting around to automation in their software. From my point of view, they are adding a complex infrastructure in the apps to enable automation that we need. Keep in mind they are dealing with a very large code base and it is manual labor for computer science; so the bottle-neck are the developers themselves; I would rather they are responsible for their health first and not over tax their individual wellbeing. 
  11. Like
    angelhdz12 got a reaction from Frozen Death Knight in Scripting   
    I want to give appreciation to the Affinity team, I know all the hard work they have and are doing. 
    The fact that we have an alternative to the expensive competition, it's already a big fresh of air.

    Now that scripting is being worked on, and that JavaScript (and by direct relationship TypeScript) has been selected, 
    I feel in good hands. I will be so excited when I can see the types of the elements highlighted in VSCode, and having intellisense of their properties 🔥🤯👏😍

    Loved the video of the example, props to the person who coded it and recorded it! The circles animation was mindblowing! And the color pallete one too.

    I've been very closely following this thread, and my feelings used to be disappointment. 

    Now I have a smile on my face.

    All the possibilities that scripting will bring to the Affinity Suite... wow...

    All the repetitive tasks that will be avoided and all the time that will be gained... all the creative stuff people will come up with!

    Feeling like a kid on Christmas! 😁🎁🎉🎊

    Most of us in this thread are programmers, so let's be real, this will be implemented by version 3.0 or 4.0. Programming is a hard and time consuming job, even with the aid of A.I. we have today.
    There are many recent libraries and frameworks that for example [INSERT THE MOST FAMOUS A.I. NAME HERE NOT TO ATTRACT SPAM] is not being able to provide correct information about.

    Let's appreciate the fact that at least they are finally doing "something about it" and taking decisions and taking our feedback into consideration.

    Most of the features I've requested in this forum have already been implemented and I shocked to realize the fact (only Live/Bitmap trace remaining).

    Good things need time. Rushed things get messy. And this comes from a very impatient person with generalized anxiety.

    I used to have a lot of fun coding VisualBasic to control MS Power Point 2007 and JSFL (JSAPI) for Ad*** Flash Professional CS6.

    Will have fun with TypeScript controlling the Affinity Suite to automate my design flow and possibly sprite generating flow for some basic Turn-based/Adventure RPG games.

    Wishing health, peace, and success to everyone, and my apologies if I've hurt someone with my comments. I used to be very angry all the time. Learned to pick my battles. This world needs more kindness, empathy, personal responsibility, forgiveness, patience. 
  12. Like
    angelhdz12 reacted to Patrick Connor in Scripting   
    What? Almost everything is missing, this is not releasable! it's a demonstration
  13. Like
    angelhdz12 reacted to Tim France in Scripting   
    Hi folks,
    I thought I'd give you a quick progress update and let you see some of things we've been working on at Serif Labs.  We now have a scripting core that we're reasonably happy with and have put together a little test area where we can run Javascript code, so I thought I'd show you some of that. Things to note:
    This is all VERY early, like pre-pre-pre-alpha. The JS API is extremely fluid and is constantly changing. This is not how the Affinity suite will run scripts and plugins; it is just a sandbox window for internal testing. There is still a huge amount of work to be done. I can't provide any timescales for when scripting will be publicly released, for Beta or Retail. Constructive feedback is welcomed, but I won't be able to answer all questions - see previous points. I'm not claiming any of these examples are particularly useful on their own; they're just to demonstrate some basic scripting functionality. Re Javascript async - yes, we support it, I've just not recorded anything yet. The sleep calls are there for screen-recording purposes only. Here are some demos as low-res gifs. If you want to take a closer look, movs are attached.
    Create a Mandelbrot image

    Some dodgy physics

    Insert a dragon curve

    "Emojification" (translation?) of text

    Create a grid of colours
     
    Select and hide based on hue

    Replay a document's edit history

    mandelbrot.mov
    balls.mov
    dragon.mov
    grid.mov
    hue.mov
    replay.mov
    emoji.mov
  14. Like
    angelhdz12 reacted to v_kyr in Scripting   
    Since the Affinity scripting team already spend some amount of time into it's JS implementation, it's now too late for voting and other script language suggestions. Thus people will have to adapt/wrap their prefered prog languange on their own. And in order to be able to do that at all, having a good reference documentation and some related code examples are mandantory essential here.
  15. Like
    angelhdz12 reacted to rui_mac in Scripting   
    If we can't add new characteristics to existing tools, I hope we can, at least detect clicks/double clicks/drags/drag&drop, etc, in documents/artboards, so that we could implement new "tools".
  16. Like
    angelhdz12 reacted to Old Bruce in Scripting   
    What I would like is to be able to select a number of groups in the layers panel and run a script which would rename the layers in the group with the group's name and incrementing numbers. So there would be Items 1, and Items 2 plus Shapes 1, Shapes 2, and Shapes 3.

    ==============
    I would also like to be able to take the name of the group and prepend/append it to the names of the layers in those groups. So I have Bob Left Arm and Alice Left Arm etc.

    ===============
    Search for named layers using regular expressions would be useful too. Then I could get rid of the various file extensions in Placed files.

    ==============
     
  17. Like
    angelhdz12 reacted to Jon W in Scripting   
    I'm happy to report that SDK development is progressing well. We are steadily working towards exposing enough app functionality to make useful plugins, but there's still quite a lot to do before we can consider even a "technology preview" release. 
  18. Like
    angelhdz12 got a reaction from Peter Panino in Export To .ico   
    It would be really nice to be able to create icons from Designer as in Gimp.
  19. Like
    angelhdz12 reacted to Dan C in Many issues in version 1.9   
    No problem at all!
    Thanks for letting me know, as far as I'm aware we did implement a few rendering based fixes into 1.9.1 - so it's likely this issue was inadvertently resolved through one of these.
    In version 1.8.5 (the version previous to 1.9.0), this tool did not have a 'From Centre' checkbox available, which is why you likely don't recall seeing the option. This option was added during the 1.9 beta and when it was added, it was also set to be ON by default. AFAIK since it has been added to the application, it has always been defaulted to ON
  20. Like
    angelhdz12 reacted to TonyB in Scripting   
    There isn't any scripting support in V2 yet. We have a dedicated scripting team here typing very quickly but still no definite timeline for release yet. 
  21. Like
    angelhdz12 reacted to Patrick Connor in Still no javascripting or python support in Photo???   
    Developer response here
     
  22. Like
    angelhdz12 reacted to Jose Alvarez in Still no javascripting or python support in Photo???   
    COPY / PASTE from Scripting Forum, TonyB (Moderator):
    Affinity will support Javascript and also have a 'C' based API binding interface that people can use to write plugins. We will also have the ability to create UI to support their scripts and plugins with dialogs and panels. 
    We have a team developing this but the amount of work is very large so unfortunately users will need to be patient.
     
    Crystal clear, mates.
  23. Like
    angelhdz12 reacted to FRworld in Byebye Affinity?   
    As a graphic designer how would you react if a client would ask you to work for free on their 2023 commercial brochure because they already paid for their 2022 brochure you did last year?
    Sorry but this section of the forum has become a spoiled brats playground.
  24. Like
    angelhdz12 reacted to LSDJE in V2 has been GREAT   
    I'm taking the time to sort through some differences - and I have absolutely NO complaints.
    I was finding V1 to be somewhat glitchy before - now I realize Serif's attention was to work on and release V2.
     
    MUCH appreciated for making such a fine suite of tools for us.
  25. Like
    angelhdz12 reacted to Michael in Ability to export icon files (*.ico) in Designer   
    I'm working on web design a lot and I love Affinity Designer. This week I had to create an icon (favicon to be precise), which I obviously designed in Designer.
     
    So far so good, but there seem to be no way of exporting an image as *.ico.
     
    Are there any plans for adding support for ico files?
×
×
  • 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.