Keysharp - the resurrection of IronAHK
Re: Keysharp - the resurrection of IronAHK
Is it possible to add a print function to keysharp? We will run Keysharp in linux and command line is prettey important in linux. Autohotkey is more like combination of an application and a program language, so ahk may never add print. But, keysharp, I thought, is a program language that is most one thought of.
Re: Keysharp - the resurrection of IronAHK
Find yourself an acupunturist. You might have some stagnation inside you.
Re: Keysharp - the resurrection of IronAHK
Waiting for the results! Just found this topic and i'm excited about it!
Thanks for all the hard work!
Thanks for all the hard work!
Re: Keysharp - the resurrection of IronAHK
@jj4156 I am not sure what you mean by print. Do you mean something to write to the console? So in C++, it's printf() or cout, and in C# it's Console.WriteLine(). Something like that? I didn't know that AHK didn't have that. Are you sure? If ti doesn't, then yes, we can add it in Keysharp.
@letacio Thanks for your interest, I am glad you found it. I am working on it regularly, about 4 nights per week. I am aiming for having a testing release available around October, but that is a rough estimate.
I'll post updates here when I have them.
@letacio Thanks for your interest, I am glad you found it. I am working on it regularly, about 4 nights per week. I am aiming for having a testing release available around October, but that is a rough estimate.
I'll post updates here when I have them.
Re: Keysharp - the resurrection of IronAHK
In AHK, you can write to stdout using FileAppend by specifying * for the file name.mfeemster wrote: ↑ @jj4156 I am not sure what you mean by print. Do you mean something to write to the console? So in C++, it's printf() or cout, and in C# it's Console.WriteLine(). Something like that? I didn't know that AHK didn't have that. Are you sure? If ti doesn't, then yes, we can add it in Keysharp.
Re: Keysharp - the resurrection of IronAHK
Right, I had forgotten about that. I have already implemented it in Keysharp, because it was already done in IronAHK.
Re: Keysharp - the resurrection of IronAHK
Any guesses on what the final executable size will be for KeySharp?
Re: Keysharp - the resurrection of IronAHK
It will be about 1.5-2MB, however it will depend on having .NET installed, which is a few hundred MB. But .NET has now become standard on all Windows installs, so it shouldn't be a big deal.
For Linux, adding .NET would generally be thought of as an additional install since .NET is not standard there.
With multi TB drives being the norm these days, this minuscule file size is negligible.
For Linux, adding .NET would generally be thought of as an additional install since .NET is not standard there.
With multi TB drives being the norm these days, this minuscule file size is negligible.
Re: Keysharp - the resurrection of IronAHK
Right I hear ya there. Does it just rely on .Net Core?
Re: Keysharp - the resurrection of IronAHK
See the early messages in this thread to learn about what .NET it'll depend on.
Re: Keysharp - the resurrection of IronAHK
My bad. Thank you for pointing me to that
Re: Keysharp - the resurrection of IronAHK
Yes, write to console. AHK need to call AllocConsole before wirte to it. So, a new console is alway created for wirting. And it is difficult to wirte and read from an exist console.mfeemster wrote: ↑28 Apr 2021, 09:22@jj4156 I am not sure what you mean by print. Do you mean something to write to the console? So in C++, it's printf() or cout, and in C# it's Console.WriteLine(). Something like that? I didn't know that AHK didn't have that. Are you sure? If ti doesn't, then yes, we can add it in Keysharp.
@letacio Thanks for your interest, I am glad you found it. I am working on it regularly, about 4 nights per week. I am aiming for having a testing release available around October, but that is a rough estimate.
I'll post updates here when I have them.
Re: Keysharp - the resurrection of IronAHK
Thanks for reply. But, FileAppend just wirte to stdio not the console. DllCall("AllocConsole") is needed for wirting console. And AllocConsole will always display message in a new consoleboiler wrote: ↑28 Apr 2021, 09:49In AHK, you can write to stdout using FileAppend by specifying * for the file name.mfeemster wrote: ↑ @jj4156 I am not sure what you mean by print. Do you mean something to write to the console? So in C++, it's printf() or cout, and in C# it's Console.WriteLine(). Something like that? I didn't know that AHK didn't have that. Are you sure? If ti doesn't, then yes, we can add it in Keysharp.
Re: Keysharp - the resurrection of IronAHK
Interesting, I was unaware of these problems. We will make sure to look into it when the time comes. Remind me again in the October-December time frame.
Re: Keysharp - the resurrection of IronAHK
Just found this, very interested in helping with testing & possibly code when publicly available. I've been a long time AHK user, but haven't really used it much in the ~2 years since I changed to Linux as my primary OS. Still used a bit at work (Network Eng. & Server Admin), but haven't really written anything complex lately.
I only have a basic grasp of C# (2 semesters in community college about 4 years ago), but can still throw stuff together on occasion. Hoping I can help out on this and brush up on both AHK & C# in the process.
I only have a basic grasp of C# (2 semesters in community college about 4 years ago), but can still throw stuff together on occasion. Hoping I can help out on this and brush up on both AHK & C# in the process.
Re: Keysharp - the resurrection of IronAHK
Thanks for your interest @Elesar . We've got a room in the discord now named #keysharp. I am also on there under the same name, mfeemster. Join us in there if you want. That's where we'll be coordinating testing and such.
Re: Keysharp - the resurrection of IronAHK
mfeemster Cannot wait to use it for Mac!
Tried to do it with pynput for my special application, but it turned out to be rather unwieldy ...
Tried to do it with pynput for my special application, but it turned out to be rather unwieldy ...
Re: Keysharp - the resurrection of IronAHK
Thanks for your enthusiasm @Bernd. My ultimate aim is to get as much of it as possible working on Mac, but please keep in mind that is at least two years away. I am first and foremost a Windows developer, so the aim will be to get it working there first. Then Linux after that, which is easily a year worth of work. Then finally Mac. The problem is that I am not a Mac developer at all. So supporting Mac will depend on how many other experienced Mac developers help contribute. We'll cross that bridge when we get there though.
Re: Keysharp - the resurrection of IronAHK
On 12/5/2020 I made a post announcing that I was going to begin work on the GUI controls. After 6 months of work, I am happy to report that I have implemented all of the functionality under the "Graphical User Interfaces" section of the help page. This was a major undertaking, so I am very happy and relieved that it is done.
There still remains to be implemented the GUI functionality under the Windows/Controls section of the help page. That will likely take 2-3 months.
After that, there will still be various features to implement including anonymous functions, #directives, script pausing/reloading, getting hotkeys/strings working correctly for all cases, and some low level object mechanics and threading stuff that will likely prove to be difficult.
I'll likely be ping ponging between these areas of functionality over the next 6 months.
I am feeling good because I can start to see the light at the end of the tunnel now.
I will post an update whenever I complete a particular area of functionality.
As always, feel free to join us in the #keysharp channel in the Discord.
There still remains to be implemented the GUI functionality under the Windows/Controls section of the help page. That will likely take 2-3 months.
After that, there will still be various features to implement including anonymous functions, #directives, script pausing/reloading, getting hotkeys/strings working correctly for all cases, and some low level object mechanics and threading stuff that will likely prove to be difficult.
I'll likely be ping ponging between these areas of functionality over the next 6 months.
I am feeling good because I can start to see the light at the end of the tunnel now.
I will post an update whenever I complete a particular area of functionality.
As always, feel free to join us in the #keysharp channel in the Discord.
Last edited by mfeemster on 02 Jun 2021, 14:27, edited 1 time in total.
Re: Keysharp - the resurrection of IronAHK
Thanks for the update, @mfeemster, that's great news.
Who is online
Users browsing this forum: No registered users and 4 guests