Autoit или autohotkey что лучше

AutoHotkey versus AutoIT

Чтобы отправить ответ, вы должны войти или зарегистрироваться

Сообщения 2

1 Тема от The gray Cardinal 2008-04-02 14:37:36

Тема: AutoHotkey versus AutoIT

Так же, как и AHK, AutoIt поддерживает вызов функций из DLL:

В последних версиях AutoIt (как и в последних версиях AutoHotkey) появилась поддержка CallBack (обратного вызова):

Подкорректирована передача по ссылке/по значению в DLL-функции:

Changed: DllCall() new method of passing types by reference using *.
Changed: DllCall(): short_ptr, long_ptr, int_ptr types deprecated. Use short*, long* and int* respectively.
Added: DllCall() now accept doubles, int64, uint64, wparam and lparam types.

Выравнивание структур при передаче:

DllStructCreate() added «align» keyword to set structure alignment

Наконец, в последних версиях в комплекте поставки идёт огромнейшее количество User Defined Function (в исходных кодах AutoIt), заметно облегчающих работу и упрощающих обучение языку.

2 Ответ от The gray Cardinal 2008-11-27 16:18:27

Re: AutoHotkey versus AutoIT

В AutoIt есть одна возможность задействовать горячие клавиши:

В UDF присутствует функция:

Вот, пожалуй, и всё. Никаких пропусканий хоткеев «сквозь себя», никаких «#IfWinActive/Exists», никаких hotstrings. Ну, и:

The following hotkeys cannot be set:
Ctrl+Alt+Delete It is reserved by Windows
F12 It is also reserved by Windows, according to its API.
NumPad’s Enter Key Instead, use which captures both Enter keys on the keyboard.
Win+B,D,E,F,L,M,R,U; and Win+Shift+M These are built-in Windows shortcuts. Note: Win+B and Win+L might only be reserved on Windows XP and above.
Alt, Ctrl, Shift, Win These are the modifier keys themselves!
Other Any global hotkeys a user has defined using third-party software, any combos of two or more «base keys» such as ‘‘, and any keys of the form ‘‘ or ‘‘.

Источник

Выбор языка сценариев автоматизации Windows. AutoIt против Autohotkey [закрыто]

Мне как программисту интересно ваше мнение. Как вы думаете, какой из них проще в использовании, более универсальный и более мощный с точки зрения функциональности? Я уже использовал AutoHotkey для личного использования, поэтому я изначально предпочитаю это.

Я очень много использовал и то, и другое.

AutoHotKey очень хорош в управлении горячими клавишами и базовой автоматизацией графического интерфейса. У него ужасный синтаксис, и он не предназначен для больших приложений.

AutoIt имеет почти все функции AutoHotKey и многое другое. Поддержка COM-автоматизации, массивы и довольно хорошая библиотека UDF (User Defined Functions). В AutoIt сложнее создавать сложные горячие клавиши.

Я голосую за AutoHotkey (AHK).

Я использую оба в зависимости от ситуации. AutoHotkey удобен для макросов быстрого нажатия клавиш, а AutoIt имеет гораздо более широкий спектр функций автоматизации, а пользовательские функции (UDF) позволяют использовать ряд полезных вещей, таких как XML и взаимодействие с базой данных. Когда автоматизация требует интенсивного взаимодействия с графическим интерфейсом, я использую AutoIt.

Я попробовал AutoHotkey, но его неуклюжесть и убогий синтаксис меня отключили. Зачем довольствоваться уродливой сестрой, если можно винить и обедать сама принцесса. AutoIt 100%.

Я использовал AutoIt до создания AutoHotkey (когда у него был синтаксис, унаследованный от файлов BAT). У меня недостаточно опыта работы с текущим AutoIt, чтобы провести правильное сравнение. Он имеет довольно обычный синтаксис, в то время как синтаксис AutoHotkey (хотя и значительно улучшенный по сравнению с исходным стилем) кажется странным. Люди, никогда раньше не кодившие, действительно любят этот синтаксис!

Я колебался, читал многочисленные сравнения и, наконец, выбрал AutoHotkey, несмотря на его синтаксис. Отчасти из-за превосходного управления горячими клавишами, отчасти потому, что это был открытый исходный код. Автор был активен (он остановился, но сейчас есть альтернативные ветки) и открыт для предложений. Я показал прототип поддержки регулярных выражений с помощью библиотеки PCRE DLL. Он интегрировал концепции и расширил их (например, поддержка регулярных выражений при обнаружении имени окна).

Документация отличная, подробная и полна примеров с исчерпывающим указателем. Сообщество очень активное и отзывчивое. Бинарный файл компактен, и вы можете создать автономный EXE-файл со своими скриптами. Он также имеет поддержку графического интерфейса (подходит для быстрых простых диалоговых окон).

Не скажу, что один лучше, выбор в основном вопрос вкуса, ощущений и потребностей.

Я работал с AutoHotkey и думал, что язык сложный. Полагаю, это либо приобретенный вкус, либо некоторым людям это нравится. Я долгое время пользовался Perfect Keyboard, но теперь я большой поклонник AutoIt.

Несмотря на то, что это Basic-подобный, я все же могу писать программы на «C», которые наиболее удобны для меня. И библиотеки для AutoIt, что экономит время. Например, библиотека для IE имеет множество замечательных и полезных функций. Хорошая IDE и активное сообщество пользователей.

Я голосую за AutoIt.

Я очень доволен AutoIt. Этот язык представляет собой легкий вариант Basic. Они включают в себя отличные файлы справки, компилятор сценариев, редактор, который понимает не только синтаксис, но и поддерживает F1 помощь и т. Д. У них есть множество примеров кода.

Источник

Autoit или autohotkey что лучше

Hi all. I’m not an AHK user, but have used AutoIt extensively. I’m wondering if anyone can help me understand the key differences between the two. Here is my motivation:

I just read the AHK Wikipedia page and it says that AHK was originally intended to be integrated into AutoIt. As an AutoIt user, this motivated me to look into their differences. The Wikipedia page also indicated one interesting difference (one that is appealing to me), that is AHK is open source while AutoIt is not. The AutoIt Wikipedia page indicates that when AutoIt switched from open to closed source, the project was forked off into AHK, «. where the community is continuing to develop and release the code under the GPL.» This makes it sound like the main (only?) difference between the two is open vs. closed source.

Re: AutoHotKey vs. AutoIt

Without going in to one more big AHK vs AutoIt thing

I will say that both have been developed on for years after the split and ahk no long support autoIt syntax as it once did.

And things like objects/arrays classes and other newer stuff don’t work the same way as the devs have implemented it in there own ways

Maybe simply take a look at the AutoHotkey changelog to know what has happenede in all this time (10 years)

Re: AutoHotKey vs. AutoIt

Re: AutoHotKey vs. AutoIt

@Blackholyman Sorry, I thought I replied to this a while ago.

>> Without going in to one more big AHK vs AutoIt thing

But this is exactly what I’m looking for. Obviously I don’t want to start a new discussion here from scratch. But if such discussions have occurred (in this forum or elsewhere), are you able to point me to one? I realize there will be biases on both sides, so I’ll try to keep that in mind.

Re: AutoHotKey vs. AutoIt

Main difference it the syntax I suppose, AutoIt «more strict & basic like» as opposed to AutoHotkey where you can «mix and match commands and functions» and in AHK you have several methods to achieve the same result with regards to variables either using = or := and %% or not around variable names.

Re: AutoHotKey vs. AutoIt

Re: AutoHotKey vs. AutoIt

Re: AutoHotKey vs. AutoIt

Also interesting screenshot from Google Trends:

Re: AutoHotKey vs. AutoIt

a more accurate google trends diagram I think, from the last 12 months. You would have to combine the yellow and blue lines together, which would far exceed autoit’s red line

Re: AutoHotKey vs. AutoIt

Источник

Выбор языка сценариев автоматизации Windows. AutoIt против Autohotkey

Мне нужно выбрать язык сценариев автоматизации Windows. Какой из них вы рекомендуете; AutoIt, AutoHotkey, или другой?

Меня интересует ваше мнение как программистов. Какой из них, по вашему мнению, проще в использовании, более развертываемым и более мощным с точки зрения функциональности? Я уже использовал AutoHotkey для личного использования, поэтому мои первоначальные предпочтения для этого.

ОТВЕТЫ

Ответ 1

Я использовал оба очень.

AutoHotKey очень хорош в управлении горячими клавишами и базовой автоматизацией графического интерфейса. Этот синтаксис ужасен и не предназначен для больших приложений.

AutoIt имеет почти все функции AutoHotKey и многое другое. Поддержка COM-автоматизации, массивы и довольно приятная библиотека UDF (User Defined Functions). Сложнее создавать сложные горячие клавиши в AutoIt.

Ответ 2

Мое голосование за AutoHotkey (AHK).

Ответ 3

Я использую оба варианта в зависимости от ситуации. AutoHotkey хорош для быстрых макросов нажатия клавиш, и AutoIt имеет гораздо более широкий спектр функций автоматизации, а пользовательские функции (UDF) позволяют использовать целый ряд полезных функций, таких как взаимодействие с XML и базами данных. Когда для автоматизации требуется много графического интерфейса, я использую AutoIt.

Ответ 4

Я попробовал AutoHotkey, но его неуклюжие ощущения и потертый синтаксис меня отключили. Зачем соглашаться на уродливую сестру, когда вы можете выпить и пообедать сама принцесса. AutoIt 100%.

Ответ 5

Я работал с AutoHotkey и думал, что язык был трудным. Я полагаю, что это либо приобретенный вкус, либо некоторые люди имеют сродство к нему. Я был давним пользователем Perfect Keyboard, но теперь стал огромным поклонником AutoIt.

Мое голосование с AutoIt.

Ответ 6

Я использовал AutoIt до того, как был создан AutoHotkey (когда у него был синтаксис, унаследованный от файлов BAT). У меня недостаточно опыта с текущим AutoIt, чтобы сделать правильное сравнение. Он имеет довольно регулярный синтаксис, в то время как синтаксис AutoHotkey (хотя и значительно улучшенный от оригинального стиля) кажется странным. Люди, никогда не закодированные, прежде чем на самом деле любят этот синтаксис!

Я колебался, читал многочисленные сравнения и, наконец, выбрал AutoHotkey, несмотря на его синтаксис. Отчасти из-за его превосходного управления горячими клавишами, отчасти потому, что он был с открытым исходным кодом. Автор был активным (он остановился, но теперь есть альтернативные ветки) и открыт для предложений. Я показал прототип поддержки регулярных выражений, используя PCRE DLL. Он интегрировал концепции и вытолкнул их за пределы (поддержка регулярных выражений в определении имени окна, например).

Документация отличная, подробная и полная примеров с полным индексом. Сообщество очень активно и полезно. Бинарный файл является компактным, и вы можете создавать автономный EXE файл со своими скриптами. Он также имеет поддержку графического интерфейса (хорошо для быстрых простых диалоговых окон).

Я не буду говорить, что лучше, выбор в основном зависит от вкуса, чувства и потребностей.

Ответ 7

Источник

A Comparison and Review of the Free Windows Scripting Languages

by Jack Dunning

Full Disclosure: While I attempt to put aside my personal bias (I’ve written ten AutoHotkey books) and give a fact-based appraisal grounded upon my research and knowledge of programming languages, I do not have the same in depth knowledge of AutoIt that I do of AutoHotkey. Fortunately, there is a good deal of data for review from people who have used both languages.

First, since both AutoHotkey and AutoIt are free to use, there is no reason not to test or use both. I’m a great believer in using the right tool for the job—especially when the tools are free. If you are comfortable with writing scripts, then you may be served well by playing with each language for particular purposes. There may be applications where one is more suitable than the other. The only cost is the time it takes to do it.

It’s important to note that the current versions of the AutoHotkey and AutoIt languages are not interchangeable. Each has its own particular syntax (set of commands and functions) which, while they are capable of accomplishing the same thing, are written in a totally different manner. To make an informed decision you will want to see those differences. A couple of simple examples are provided below.

The Names AutoHotkey and AutoIt

The name of each scripting language gives us insight into the differences between the two. While you can do almost anything in AutoHotkey that you can in AutoIt (and vice versa), there are some noticeable differences. The underlying meaning of the terms AutoIt and AutoHotkey express the original impetus for each program. While both are used for Windows program automation, that is the primary thrust of AutoIt—thus the name. As suggested by the name AutoHotkey, hotkey creation and hotstring replacement through keyboard action is integral to the program. While AutoHotkey has implemented simple ways to create hotkeys and hotstrings, the AutoIt community has never consider those features high priority—although there is a specific function for creating hotkeys in AutoIt—HotKeySet().

It seems that the split occurred after programmer «Chris Mallett’s proposal to integrate hotkey support into AutoIt v2» received little response from the AutoIt community causing Mallett to start writing his own version of the then open source AutoIt—calling it AutoHotkey. The name AutoHotkey demonstrates the primary functional difference between the two scripting languages. AutoHotkey offers simple direct support for one-line assignment of hotkeys and hotstrings while the current version of AutoIt requires the use of functions to implement the same or similar hotkey and hotstring features. (See the comparisons below.) This has caused the two language to be viewed very differently. You might say that AutoIt is for Windows automation and AutoHotkey for easy implementation of Windows hotkeys and hotstrings plus Windows automation. (This is not a completely fair comparison since Windows automation, app development, and hotkey/hotstring implementation can be done with either scripting language. They are just done in a different way.)

The result is that many AutoHotkey users who have switched have been extremely pleased with the results after converting most of their scripts to AutoIt, but, even then, they tend to continue using AutoHotkey for their hotkey/hotstring implementations—especially with long list of hotstrings such as the AutoCorrect scripts. Understand that most of these individuals who made the jump to AutoIt from AutoHotkey are more experienced with script writing and programming.

Update December 17, 2015: After completing a series of blogs on AutoHotkey Hotstrings, I’ve come to realize that there are many people who might want to use AutoHotkey just for the easy built-in Hotstring structure. If you’re a writer, student, or anyone else who does a lot of word processing, then you’ll be amazed at the AutoCorrect and text expansion/replacement capabilities of AutoHotkey. There are many cool text tricks which you can implement with Hotstrings. This applies equally to the simple built-in basic Hotkey structure in AutoHotkey.

For beginning script writers, the syntax for hotkeys and hotstrings (text expansion) is much simpler in AutoHotkey (a couple of colons ::). This attracts novice users since their first scripts often consists of this type of easy coding. As these beginners become more daring, they naturally venture into the other slightly more complex commands found in AutoHotkey. The function oriented language of AutoIt may be intimidating for the newbie while it might be more natural for the experienced programmer.

The commands in the early versions of AutoIt looked very much like those in the current release of AutoHotkey. After the split between the two languages, AutoIt moved in a new direction (version 3) using more BASIC-like functions while AutoHotkey continued with the original command structure used in the early versions of AutoIt. I don’t know that there is a clear advantage of one language structure over the other, but each certainly has its own separate learning curve.

AutoHotkey Versus AutoIt for Hotkeys and Hotstrings

The following is an example of what’s required to set up a hotkey in AutoHotkey:

It’s one line of code that turns the INSERT (Insert) into a hotkey which opens your Windows Documents folder. The percent signs (%) surrounding the built-in variable A_MyDocuments evaluates the path to the Documents folder.

In AutoIt it takes few more lines:

The first line uses the AutoIt function HotKeySet() to assign the INSERT key (Ins) to run the user defined function openDocs(). The openDocs() function uses the Run() function to open the Windows Explorer.exe program at the user’s documents folder—designated by the macro (built-in variable) @MyDocumentsDir. The ampersand (&) appears to be the symbol for concatenation (combining strings). As can be seen, there are a few more lines needed in AutoIt. This is comfortable for experienced script writers, but could be confusing for the average Windows user.

This next example is a text expansion (or hotstring) for the phrase «by the way» in AutoHotkey:

Hotstrings are assigned by placing double colons (::) at the beginning of the line followed by the hotstring and another set of double colons (::btw::). The replacement text (by the way) follows the second set of double colons. Once the script is loaded, anytime «btw» is typed followed by a space or punctuation, it is automatically replaced with «by the way.»

I couldn’t find a built-in hotstring function in AutoIt, but I did locate this example which includes a special AutoIt script (HotString.au3) to create the function HotStringSet():

To replicate the AutoHotkey example would require the use of the AutoIt Send() function in place of the MsgBox() function. If you need text expansion, then it looks like AutoHotkey may be your program of choice. This is not a minor point since the same simple hotstring technique found in AutoHotkey (in a slightly different format) can be used to run a set of commands in the same manner as a hotkey subroutine.

Both languages are capable of much more involved programming and Windows app building which have nothing to do with either automation or hotkeys/hotstrings. AutoHotkey syntax uses primarily text commands whereas AutoIt uses functions. For example, to add a button to a Graphic User Interface (GUI) window AutoHotkey uses the following command:

To create a Gui button in AutoIt the following function is used: This is not a major difference for experienced programmers, but it you’ve grown accustomed to doing it one way, switching to another method requires developing a different mindset. While there is no particular advantage to the AutoHotkey command structure, it may look simpler to the novice.

The Confusing Side of AutoHotkey

In many ways the current AutoIt version is a much cleaner language than AutoHotkey. It has not fallen victim to the confusion caused by maintaining backward compatibility with older scripts. Since virtually any older AutoHotkey script will run with the current 1.1 version (AutoHotkey_L) of AutoHotkey, there are numerous redundant commands and methods for getting the same thing done. This is a source of confusion for AutoHotkey users because, although there is more than one way to get something done, each requires a different implementation.

The classic example is the use of both the equals sign (=) and a colon plus the equals sign (:=) to assign a value to a variable:

and are identical sets of expressions. But if you use the wrong one in the wrong place with the wrong format, your script won’t run properly. There are a number of other examples of this type of duplication caused by legacy AutoHotkey commands included for backward compatibility. Often the different variations may be used in the same script.

There is an attempt underway to fix the problem and clean up the code with version 2.0 of AutoHotkey. (Version 2.0 is still in the alpha stage of development and not recommended for newbies.) It is designed to eliminate the excess baggage. However, that would mean that many of the scripts available today would no longer run properly with the new version of AutoHotkey. It is difficult to know how widely this new, cleaner version would be accepted. The changes which would be required in older scripts are not well documented and many people will not relish the extra work. As far as I know, AutoIt does not have a similar issue.

Interest in AutoHotkey Versus AutoIt

Based upon links found on Google Trends, interest in AutoHotkey appears to have caught up with AutoIt. (See Figure 1.) This is a momentum which is not likely to reverse.

Figure 1. Interest in AutoHotkey in the United States has slowly caught up with AutoIt. The trend favors AutoHotkey.

The primary reason for the growth of AutoHotkey is its initial simplicity. It’s easy for the beginning script writer to get a result with just one line of code in a text file (a hotkey assignment or text string expansion). This is what got me started. Over time, and with a little curiosity, newbies start experimenting with other simple commands and scripts. Eventually, they are hooked and become part of the AutoHotkey community ready to help others.

Since many of the users don’t consider themselves to be programmers, the AutoHotkey community works to help each other and is welcoming to beginning users. There are numerous online tutorials and people don’t usually face impatiences when they ask newbie questions on a forum. (My experience on the AutoHotkey forums is that at any given time there are usually a number of people online willing and able to answer novice questions.) This makes it easier for people who have never before written a program.

Using AutoIt is a bit more daunting for the newbie script writer. If you’re not already a programmer, the concept of using functions can be a little difficult to wrap your brain around. As far as I can see, there is no easy entry point in AutoIt for the complete novice. AutoIt seems to be used more by computing professionals and possibly to a greater degree within corporations. (I have no data to back up this statement, but it was a feeling expressed by AutoIt users.) If I had started with AutoIt first, then, who knows(?), I could be writing AutoIt books. However, I’m not sure the AutoIt users are as likely to need the help. As it is I’m happy with AutoHotkey—even with all of its quirks and idiosyncrasies. It’s good stuff.

Some people suggest that AutoHotkey is not as extensive as AutoIt. I would be forced to differ. While there may be some minor technical advantages to AutoIt, I haven’t seen much bragged about in AutoIt (arrays, object oriented coding, etc.) which isn’t now available in the current version of AutoHotkey 1.1. As far as I can see, both have a great deal of capability for building Windows apps. If more is needed, then possibly the programmers should consider using a programming language such as C++ or Java.

If you’re an experienced programmer and the simple hotkey and hotstring assignment found in AutoHotkey is not a requirement in your work, then I would likely recommend AutoIt as your Windows scripting language. If you’re a beginner, then AutoHotkey may be just what you need. If you’re somewhere in between, then it’s a coin toss. Or, maybe you should use both—depending upon what you want to do.

The second edition with more chapters and an index to the AutoHotkey commands found in the book is available in e-book format from Amazon (and other formats—EPUB and PDF— at the ComputorEdgeBooks Web site linked below). Jack’s A Beginner’s Guide to AutoHotkey, Absolutely the Best Free Windows Utility Software Ever!: Create Power Tools for Windows XP, Windows Vista, Windows 7 and Windows 8 (preferred, EPUB format for iPad, Android, and computers; MOBI for Amazon Kindle; and PDF for printing) offers a gentle approach to learning AutoHotkey. (Also available from Amazon for the Kindle and Kindle software on other devices.)

Building Power Tools for Windows XP, Windows Vista, Windows 7 and Windows 8, AutoHotkey is the most powerful, flexible, free Windows utility software available. Anyone can instantly add more of the functions that they want in all of their Windows programs, whether installed on their computer or while working on the Web. AutoHotkey has a universality not found in any other Windows utility—free or paid.

Based upon the series of articles in ComputorEdge, Jack takes you through his learning experience as he explores writing simple AutoHotkey scripts for adding repetitive text in any program or on the Web, running programs with special hotkeys or gadgets, manipulating the size and screen location of windows, making any window always-on-top, copying and moving files, and much more. Each chapter builds on the previous chapters.

Jack’s second AutoHotkey book, Digging Deeper Into AutoHotkey (preferred, EPUB format for iPad, Android, and computers; MOBI for Amazon Kindle; and PDF for printing) is comprised of updated, reorganized and indexed columns from ComputorEdge is now available. Since the columns were not all written in a linear fashion, the book has been reorganized and broken up into parts by topic. The book is not for the complete beginner since it builds on the information in A Beginner’s Guide to AutoHotkey. However, if a person is reasonably computer literate, they could go directly to this book for ideas and techniques without the first book. (Also available from Amazon for the Kindle and Kindle software on other devices.)

Jack’s third AutoHotkey book AutoHotkey Applications (preferred, EPUB format for iPad, Android, and computers; MOBI for Amazon Kindle; and PDF for printing) is an intermediate level book of ideas and applications based primarily on the AutoHotkey GUI command. The book emphasizes practical applications. The book is not for the complete beginner since it builds on the information in the other two books. However, if a person is reasonably computer literate, they could go directly to this book for ideas and techniques without the other books. There is an extensive index to the ideas and techniques covered in the back of the book. (Also available from Amazon for the Kindle and Kindle software on other devices.)

This Beginner’s Guide to Using Regular Expressions in AutoHotkey is not a beginning level AutoHotkey book, but an introduction to using Regular Expressions in AutoHotkey (or most other programming languages). To get the most from this book you should already have a basic understanding of AutoHotkey (or another programming language). Regular Expressions (RegEx) are a powerful way to search and alter documents without the limitations of most of the standard matching functions. At first, the use of RegEx can be confusing and mysterious. This book clears up the confusion with easy analogies for understanding how RegEx works and examples of practical AutoHotkey applications. «Regular Expressions in AutoHotkey» will take you to the next level in AutoHotkey scripting while adding more flexibility and power to your Windows apps. (This book is also available at Amazon.com)

Источник