AutoHotkey Community

That's an interesting observation (and it's actually on-topic here). Not that I disagree, but your definition of simple macro program appears very narrow. In theory, would a single complex feature redefine an entire application? Is a language with 99 simple macro features and 1 complex programming feature no longer a scripting language?

I find it interesting that DllCall() seems to have made AutoHotkey less of a simple automation language by obsoleting much of the development. Very few things require AutoHotkey itself to be developed further, because they can now simply be scripted. The introduction of native COM makes this process simpler. As a simple example, we will probably never have the Process, List subcommand (which seems to have been a planned addition originally) because it is only a few lines of COM. It is common to see a wish dismissed because it is not frequently used/requested and at the same time can be scripted and put into a UDF, often with DllCall(). (This is not necessarily a bad thing.) The most important development going on involves new syntax (such as classes) and AutoHotkey v2.

_________________
Autofire, AutoClick, Toggle, Spam • Window Control Tools
Recommended: AutoHotkey_L

The definitions of composing macros, scripting, and programming are vague in this context. As Tunkay says, they are all automation. Composing macros could be complex as programming and programming could be too simple as composing macros.

I used the term, simple macro program, to emphasize that the program was for non-programmers, especially for those who have limited computer experiences, like those who have even having hard time typing characters.

It depends on the weight and the balance. In the case of AutoHotkey Basic, most scripts for Basic available on the forums are heavily depending on the functionalities of DllCall(), VarsetCapacity(), NumPut(), and NumGet(). And why I call AutoHotkey Basic no longer a simple macro program is that one wouldn't be able to use those functions without a programming background. Of course, there are some exceptions but I'm talking about it in general.

Again it depends, but in the case of AutoHotkey Basic and its implementation of DllCall(), I think so. It is said that humans and chimpanzees have merely one percent of difference in DNA. A slight difference in amount doesn't mean it does not have enough impact to be thought as it is the same as the other. Similarly, AutoHotkey Basic without DllCall() and AutoHotkey Basic are totally different although the amount of changes in the source code may be merely a few percentage of the total.

The same thing could be said to the relationship between AutoHotkey Basic and _L. _L has objects like Basic has DllCall(). So one might argue that it is normal to complain that _L is so difficult as DllCall() was introduced. Wrong. They don't complain that Basic has DllCall() but complain _L has objects. What a double standard is that.

It's all about understanding. Classes and objects and whatever may have been added to the new version(s), are simply too opaque to be understood. I'm not a genius, but I'm not stupid either (or at least let me think so); however, I could never wrap my head around objects and classes, neither in AHK nor in C++, C# or similar languages. I did catch on DllCall() right away, though. A bit of MSDN reading (online or offline) and on with the work.

One big problem is that predefined objects and classes are just that: fixed things to work with. If there's any incompatibility or fault, tweaking may be hard to impossible. On the other hand, using separate DllCall() sequences with the ability of tweaking/adding/removing each of them at will, provides the required flexibility. Right now, the new AHK shows me rigor mortis in this regard, as far as I can see. In some way, I'm glad it pushed away Win9x compatibility, because I would've wasted too much time trying to figure out how to (re)do certain things and why others behave so sh!tty from one OS version to another without any way to fix them.

Anyway, to sum it up, my opinion is that current AHK has become too complex, too rigid and too opaque for the potential average user. Unfortunately and without any intention to offend Lexikos or anybody else working on it. And, obviously, I may well be wrong.

_________________
AHK tools by Drugwash (AHK 1.0.48.05 and Win98SE)

So as DllCall().

On the contrary, I could have never wrapped my head around DllCall() and the concepts of structures and variable types, until I learned C++. I did catch on objects right away, though with a bit of manual reading offline.

So as DllCall().

Like what? Your remark is baseless.

Like what? Provide a vivid example.

In what regard are you talking about? The bottom line is _L is in progress and Basic has finished. Why does _L have to be criticized like that? You cannot be thankful but nothing else for the fact that AutoHotkey is still being developed. You just can't stand people don't look back your favorite old tools. I sort of understand that but it's nothing to do with _L development. It's your problem. Create a thread to complain about Microsoft's win9x abandonment.

Why are you using Win9x? Even Microsoft doesn't support them any more and how can an individual developer can support that.

I totally disagree. AutoHotkey Basic is already too complex for average users. Stop hindering Lexikos's achievements by saying such thing.

I have a strong sense that you are. Just follow the examples of the manual on the Object page. At least, you would grasp what it does. However, DllCall(), I couldn't have at the first attempt because it requires some other programming concepts.

You just don't understand the nature of progression. If you want to stay with the abandoned tool, fine, just don't complain and don't insult those who are trying to make progress.

This isn't so much about the language itself, but on how it's presented - both in the documentation & in the community. Couldn't python/ruby be presented & used as a simple automation language? I firmly believe it would be possible to have a website with AHK the programming language & a separate one with AHK the windows automation tool (not that I'm suggesting this).

_________________

Recommended: AutoHotkey_L
Basic Webpage Controls

tell you what i would like to see.
is an automation forum not tied to a language. no application writing allowed just automation.

each forum on a seperate subject such as browsers, spread sheets,game.

then within each of those people can post any script in any language they want

_________________
No matter what your oppinion Please join this discussion
Formal request to Polyethene

@tank
Interesting thought.

I like that idea a lot. It would give me a good chance of picking up other languages while accomplishing the same tasks.

_________________
COM Tutorial for Webpages
COM Tutorial for Excel

http://stackoverflow.com/search?tab=new ... ion%20game
http://stackoverflow.com/search?tab=new ... 20browsers
http://stackoverflow.com/search?tab=new ... d%20sheets

Similar idea but not what i had in mind

I have long disliked stack overflow's forum software. I think i might register a domain and give it a go

_________________
No matter what your oppinion Please join this discussion
Formal request to Polyethene

Lemme know! I'll be the first to register.

_________________
COM Tutorial for Webpages
COM Tutorial for Excel

It sounds like a very interesting project. It would be really nice. Learning and knowing a single language is impossible - one has to master many languages and use for different things. It'd be a good programmer's resource. If you need design or interaction-design opinions, gimme a shout.

A word of warning though: It might be wise to start off in a specific end, to avoid empty forums. I would even consider moving some AHK discussion there.

_________________
~sumon • Appifyer• AHK Nova halted • Recommended: AHK_L (Why?)

I have a few domain names already registered and unlimited server space on FatCow. Haven't used it yet, been working on a site for a friend. Let me know, i'm looking to play around.

@Carcophan
That's what she said.

_________________
COM Tutorial for Webpages
COM Tutorial for Excel

I like it. Please let me know it too.

_________________
{1:"ahkstdlib", 2:"my libs", 3:"my apps", 4:"my license"}
--> Don't feed the troll! <--