- @nnnik: Thanks for your post.
- If I'm honest, it's your AHK v2 proposals that concern me the most. Mostly because they are very complex and often non-AHKish. Whereas I try to keep things simple. That said, sometimes big things do need adding.
- I'm tempted to say that if we followed through with your ideas, AHK would never be finished, and AHK would be nothing like AHK.
- (Although I do actually very much respect many aspects of, and the coherence of, your overall vision.)
- I'm interested in any criticisms you have of my approach, it's just that so far you haven't given me much that is concrete to benefit from. I'd need examples for your 2nd paragraph, I don't recall anything like that ever happening.
- 1. Solutions that would never be implemented.
- Your suggestion for InputBox to return an object is nothing like anything else in AutoHotkey.
- Did you actually think that that had a chance of being implemented like that? Otherwise it's time-wasting or it looks like flippancy.
- You don't appear to put yourself in the mindset of the main developer. Before I make any suggestion, I ask myself, is this a good fit for AHK.
- Something in line with AHK might be either of these 2 suggestions. Re. knowing if the InputBox was exited.
InputBox(vPrompt,,, vDefault, ByRef vInputBoxResult) ;add a parameter
A_InputBoxResult
- I would suggest pick one, or pick both, and move on to the next problem.
- I feel similarly about StrReplace. Add StartPos and CaseSen parameters and move on.
- (That said, I think it's good to get all of the ideas out, and reflect for a few months, before setting things in stone.)
- 2. Here, there and everywhere wish list ideas.
- I've seen you casually suggest ideas that could take months of development, in random places, without even starting new threads for them.
- I think it could take ten years to implement all of your ideas. The least you could do is be clear about what you want, and outline your wishes in one place.
- Plus, I would be interested to see your vision in full.
- 3. I 'know' it's right.
- Anyone can fall into this trap. (I try to always look at any idea of mine from everyone else's view.)
- People learn something in one or two languages, and just assume it's normal, and insist that AutoHotkey should be like that.
- This can affect anyone from newbies to experienced programmers. The idea is not as 'standard' as they think.
- Here are my ideas:
Wish List 2.0 - AutoHotkey Community
https://autohotkey.com/boards/viewtopic ... 13&t=36789
- I intend to do a grand simplification and overhaul of the list, based on recent and future investigations into the source code.
- [EDIT:] Re.
From your recent posts I can only conclude that you do not want to change the language with your suggestions immediately but just discuss it and talk about it without ever changing anything in the AHK source.
- There are two steps, write the code, get lexikos to approve it.
- Everything that I will write, apart from some 'hello world' examples, will be intended as viable AHK source code. I simply accept that there is no guarantee of getting approval.