angelhdz12
-
Posts
198 -
Joined
-
Last visited
Posts posted by angelhdz12
-
-
Oh sorry, I just noticed I'm on the wrong Forum. I selected "Affinity On Desktop" and I ended in Publisher.
Bye!
-
I make a lot of quick image edits for the web. Each time I import an image, I have to right click > Rasterize Trim, in order to make Raster Editing like marquee tool, selections, inpainting, etc. Not every tool automatically converts the Image to Pixel while trying to use the tool. At least, the Warp Tool uses the Assistant to convert the Image to Pixel.
Am I missing something? Can we make Raster edits on an Image layer? -
Can't find this option in the Preferences. It's a must. I'm tired of having to RightClick > Rasterize Trim every time I import an image.
-
Yup. After reading all comments, TypeScript and Javascript are the most obvious solutions. TypeScript for the ones who love static typing, and Javascript for the ones who want to type less. But also, Serif should consider choosing TypeScript as default, but allowing BINDINGS to other languages so everyone is happy.
-
On 3/27/2019 at 4:48 AM, firstdefence said:
Thinking a bit laterally, until the "scale to text box as you text" feature appears, what about making text styles based on how many characters are in a name, so have a 12 character text style with say a 16pt font and a 15 character text style that has a 12pt font, then type the name and choose the style that fits the amount of characters.
Excellent idea!
-
On 3/27/2019 at 5:00 AM, Dan C said:
Thanks for your video, unfortunately this isn't currently possible automatically. However it's a feature we plan to add to Affinity Publisher and once this is added here I see no reason why the change would not reflect in Photo and Designer.
For the meantime I recommend either manually resizing the text, or setting up custom styles as firstdefence has mentioned
Thanks!
-
A**** Photoshop has this feature. It allows to search for specific layers in an ocean of layers.
-
On 6/11/2019 at 7:36 PM, Pšenda said:
Excuse me, but why would it be appropriate to sort/rearranging layers by their type, name, blend mode, etc?
I by mistake used the term "Sort". I mean "Search". Photoshop has this feature. We can search layer based on queries like locked, unlocked, hidden, visible, by name, by filters, by blend mode.
It helps when you have so many layers and you need to find specific layers and do something with/to them. -
Yup, definitely it should be Javascript and Typescript (for the ones who love static typing).
Typescript is basically Javascript, with static typing added.
Typescript is the best choice, because then we can know at authoring time, the types of the variables, properties, function returns, etc.
For example:
import { Shape, Layer} from "affinity"; import * as affinity from "affinity" var rect:Shape = affinity.document.current.selectedItem(); var rect2:Shape = affinity.document.duplicate(rect); for(var layer:Layer in affinity.document.layers) { affinity.document.select( layer ); }
I have experience with JSFL, an Adobe Flash (now Animate) Authoring environment Javascript API. You can run the actions inside the program, or load an *.jsfl file.
-
-
On 6/26/2019 at 8:19 AM, fde101 said:
This is also a great example of why these features should be in user-provided scripts rather than integrated into the software. The specific corrections are highly specific to the subject material. Running those corrections on a document which includes programming language code could in some cases change the meaning of the code, rendering the document incorrect. Particularly with snake-language (err, Python) as the spacing in front of the code is part of the syntax.
Similarly, if the document uses tab stops to format table data, removing "double tabs" could cause data to show up in the wrong column of the table.
This may work extremely well for some kinds of input, but it is not generically safe. If it is known that the incoming documents are safe to run these corrections on, then allowing the user to write such a script is a great solution for this.
A lot of people complaining about the use of tabs in Python.
So I got a feeling the best 2 languages to automate Affinity programs are Javascript and Typescript (static typing <3 ) .
But something tells me they could end implementing their own language, like Unity with the JScript, Microsoft's dialect of the ECMAScript -
On 6/21/2019 at 7:33 AM, evtonic3 said:
This is such a lengthy topic that I can’t help but wonder what are people’s goals here to have scripts added to the app? I mean what can one do to better the app that the devs aren’t already doing? Just curious.
Not having to wait for the developers to add missing features and advanced macros/actions.
A lot or programs since 90's allow to do this, like Microsoft Office programs using Visual Basic to automate tasks.- Friksel, Copper Star Media and MC909
-
2
-
1
-
58 minutes ago, fde101 said:
I think that looks ugly.
If you like languages with strong data typing, nothing beats Ada, and it is much more readable as well:
procedure Select_Shapes(doc : in Document) is ab : Artboard := Current_Artboard(doc); lay : Layer; begin for i in 1..Layer_Count(ab) loop lay := Layer(ab, i); if Is_Shape(lay) then Select(lay); end if; end loop; end Select_Shapes;
Why it looks ugly? Because it's not your language of preference? Because it has brackets to open and close blocks instead of tabs?
I've seen a few people preaching about ancient languages in here, trying to make it relevant. One preaching about Haskell, others about Lua or Cobol, don't know, and so on.
So your opinions are biased, favoring personal preference and not a generalized overview on users needs and simplicity, accessibility, maintainability, compatibility, etc.
Top programming language of 2019- Python
- Javascript
- Typescript
- C++
- C#
- PHP
- Java
-
19 minutes ago, affi.usr said:
This is key what I think about. Create scripting with inbuild macro recording it is not new thing. I prefer go ahead competitors and ask about:
- How make scripting in Publisher and Affinity Suite more problem solving oriented in place learning new path tool?
- How make it OS idendepented and open for intergration for data providers like servers, e-mails etc. for creating worflow oriented on fitting Affinity Suite with data?
- How make it user friendly that after 5 minutes reading introduction I can create solution for my typical problems (like automate boring stuff in the easiest way possible) without digging in docs?
- How use aproach less code more possibilities?
After few year experience with coding in Python I can say the best with it is the simplicity. You can code with less code lines and it is minimal with extra ; or {. Dear Peter you should think about possibilities that after Python in the future it can be easier and more powerful language. I like using it, but when I start coding with Turbo Pascal when I found C++ I think that it is the best tool on the Earth. VBA, JS, Assembler 8086, PHP are some of langs which I try before I stay with Python for longer time. For some scenarios Python libraries can make faster results than coding in my earlier favorite C++.
I have the same opinion. Afifnity Team use inside Java Script for testing Affinity Suite so they can prefer it as they have some experience with it. Python it the most universal tool now from web developing to data analysis.
Future
Today a lot of people think about graphics like only creating retushing, vectors or DTP publishing. Now it is changing. Data analysis blured line between interactive programming and showing visualistation in real time for information. I see few niches to go inside and take advantage with creating something really new.
Scenario
Client need poster with financial statistics for company. Using Python Pandas we can create analysis of data and with bokeh library create visualisation. Now using OpenCV we can recognise elements in PDF for vectorise it without designer interaction in Affinity Designer. After that we need text classification for typical client document so we can use C++ library for Nvidia Tesla to improve sentimental analysis of text and get thinal thought about how people feel about products. Using C++ is dicted by specific of Nvidia card and better for performance reason. With PHP we can grap form SQL database financial data to get view how many cost new product and put this to Affinity Designer to create graph. Using in other place JS (jquery) we can grap from menager data about marketing strategy because he can add photographies of last events to summary template in Publisher. With machine learning photography are selected for quality like sharpness and avoiding two previous emploees with awful public opinion what support company create with R.
...
For start it's seems strange and too more complicated why not using e-mail or FTP to sharing data, but now automation is in progress. Creating workflow where computer in real time can add data from few other source to graphic project is very interesting start. As designer you can use infrastructure created by someone else and concentrate how creativly improve visual communication and make your work better. If retoucher work with similar projects like party events photography using templates for drafting can make work easier. Creating base for integrating other tools for working inside Affinity Suite it is not only choose language but make it easier for anyone. If programmer with 20 years old experience in C++ can create solution in place learning for X project python it is big deal.
I Agree on Python, because its power, and syntax simplicity. But if they go the HTTP requests route and let developers choose their own language, I would choose Typescript or C# because I love static typed languages.
Let's say:
Something like that. Beautiful! -
-
Totally agree. Preferences window is a mess.
- brunoczech, Ed Lyons, Nikola Kovac and 1 other
-
4
-
On 6/8/2019 at 4:20 PM, affi.usr said:
I can't understand why the most people think about using one language for scripting in place make this independent?
Solution
1. Create Affinity Controler App
2. Create API to interact with controller
3. Using GET / POST request with your favorite language to control Affinity Suite without bodering about what language is used.
1) Affinity Controler App - is local webserver. When someone is calling it's function it is start controlling choosen app.
2. API is local adress with choosen port to make calls fx.
localhost:2019/ad/open/file&name=test.afdesing
localhost:2019/ad/export&format=pdf&preset=print&rasterdpi=300
It is powerful. It need some effort to make inside call in Affinity Suite, not only Publisher, but it is worth. You can share script between platforms in easy way. You can automate workflow using another system too fx. save data from client on Samba server, from Linux call computer with Windows to open and run application to make template filled with photos (fx. Atlas of mushrooms) and after preparation designer will have to work with text.
3. Calling local API for application is simple way to avoid locking possibilities for specific branch of person. I skip ActionScript in Photoshop, because I do not have time to learn it when I need fast work done. I use another software to prepare files as it was simpler and faster when clock ticking...
At the end
I suggest using seperate application for calling all apps, because in my vision Affinity Suite can send virtually data between fx. create some part in Photo, add in Designer and create final PDF with Publisher.
This! OMG! Never thought about this! This way, developers can control Affinity programs in any language flavor they want. I would use Python and Typescript. <3
-
Thank you for the video and for replying. Sorry for the delay. I'm programmer and have been very busy building some apps and learning some new technologies and languages.
Let me explain what my cousin needs:
-
On 10/22/2018 at 12:15 PM, Mesquito said:
I would second this request. While I like the macro availability it is limiting. Having an API to allow us to create our own scripts (preferably in python) would be a major plus.
I can't react anymore for 24 hours LOL I'm banned! I reacted with a heart on your reply.
Other developers are talking about this. Python, TypeScript and Javascript are the language more voted. I'd vote for Python or Javascript because they are not static typed, easier for building actions/macros/extensions to automate tasks in Affinity programs. It's a must! So every programmer out there can develop these so less feature requests the Affinity developers will have. -
-
On 3/17/2019 at 8:18 AM, Pšenda said:
And Rotate.
Yeah, but at least we can rotate manually or by setting the rotation in the Transform Panel, but not with Flip Vertical/Horizontal.
Cheers! -
Affinity Vectors
Affinity Pixels
Affinity Pages
*MIND BLOWN* -
13 hours ago, jmwellborn said:
Strikes me that you all have too much time on your hands with too little to do. Why not write your own apps and then call them whatever you like? I write and publish. “Affinity Publisher” is perfectly fine with me. I do not “layout” books like laundry out of the dryer.
That could be also applied to you mate. Strikes me that you have too much time on your hands and you come here to attack people on their opinions. Who says your opinion is better than everyone else's opinion? Keyboard warrior much?
-
On 3/18/2019 at 2:33 PM, v_kyr said:
Scripting? - Well, as far as it isn't stepmotherly treated like macros here then and would further also be usable cross-application wise for/on all supported platforms. I guess they probably would reuse something like Javascript/Typescript here and thus orient themselves on already existing things also used by other field players, or what's lately widely used and easier to adopt here. - However, most interpreters used in app scripting solutions aren't that performant in terms of fast execution speeds, so it will be interesting to see how things will then work and perform here.
Considering Typescript is the language to develop VSCode extensions... yeah, most probably they go the Javascript/Typescript rute.
- Andy Hayes and SrPx
-
2
O
Rasterizing Image On Import
in Feedback for Affinity Photo V1 on Desktop
Posted
Can't find this option in the Preferences. It's a must. I'm tired of having to RightClick > Rasterize Trim every time I import an image.
There are tools that can't work on an Image layer like inpainting, marquee tool, etc. Others automatically converts the Image to Pixel with Assistant.