AutoHotkey Community

[compuboy_r]

@Chris !!!

AHK is going Great but for one of my scripting needs i had to revert to AutoIt3 for GUI. Any chance GUI features getting added to AHK soon?

I have used the Autoit3 Gui syntax and its quite easy.
What do all others say ?


compuboy_r

[Chris]

It's on the list, hopefully within the next month or so.

[Beastmaster]

I'm not to keen on that. As AU3 isn't to far away from VisualBasic (which seems the "visual basic" standard in GUI building), IMHO it don't need another VB clone.

To keep it stupid simple (KISS-principle) should be the main attitude.

I take AHK as the perfect replacement for AU2 and wouldn't be happy if it has to compete with AU3. Especially as Chris currently seems to do the AHK development as a one man show, requesting a tool/feature which is already available will put unnecessary pressure on the AHK development.
Which I doubt would be a good thing.

As I primarily use AHK in a proffesional/office/backoffice environment reliability/stability is the main thing to care about. AHK in my case is working as an interface between existing apps/processes. Target is a full automation of repetitive tasks. Therefore I'm definitely closer to the commandline then to a GUI.

If you need a GUI in an office environment follow the standard (and cover your ass this way) and start using VB/Delphi/...

If you need a GUI to provide a tool with advanced functionality for cheating games (just a sample ), that would be another story which I think shouldn't get a high priority.

Thanks.

[Chris]

I want the AHK project to be responsive to what users want. For example, anyone can feel free to set up a forum poll to try to draw support for a feature they want, or a poll to vote on the priority order the planned features should be done in.

Since GUI functionality is something that I expect at least 5% of AHK users would want or find a use for (though I myself would probably not use it much), I've responded to that by putting it on the planned features list.

The intent here is not to copy VB or Au3 syntax. Also, the intent is not something nearly so grand as Gui4Cli. My preliminary plan is just to have the ability to create an arbitrary number of windows (like SplashImage or Progress) in which you can have an arbitrary number and type of standard controls (combo boxes, buttons, edit fields, etc.) The philosophy of simplicity and empowerment will still be adhered to as much as possible.

[Beastmaster]

Thanks Chris.
feeling better now, with knowing a byte of the masterplan

[Rajat]

The question here is not 'competetion' with au3, it'd be absurd and its out of the question.

Past tells me the reason for addition of a certain feature in ahk is based on two criteria:
1. Demand from users.
2. Ease of implementation.

For the first, I can say that the demand seems nice seeing that just after the declaration of to-do list by Chris, some guys (including me) showed their preferences in future features, and GUI figured on almost all (if not all) of them.

For the second, I know that this is not a regular 'think of it - add it' feature. This is complex, but seeing the uses IMHO its justified. Also, the implementation should not be VERY difficult seeing that AU3 beta and Larry's Au3GUIXP are open - source. They can be of some help.

and the uses (Beastmaster) are not game-related. rather they'd not even be 5% of the possibilities. As I come to think of it, games rather don't need any GUIs, they'd rather be content with hotkeys, key sending, pixel and joystick commands.

the power to make anything considering tray menu, GUI, hotkeys, and all the other powerful features of AHK is tremendous. msgboxes or splash/progress windows don't and can't cater to many needs.

just for instance, if i'd like to make a script that takes the employee's name/address/age/leaves/salary details etc. and make a database then a single window with multiple input fields would be certainly be better than 10 input boxes one after another.
_________________

[Beastmaster]

[Payam]

EXACTLY MY PROBLEM

I think GUI support would be tremendously helpful!

just for instance, if i'd like to make a script that takes the employee's name/address/age/leaves/salary details etc. and make a database then a single window with multiple input fields would be certainly be better than 10 input boxes one after another.[/quote]