v1.0.24 released: FormatTime, GUI drag-and-drop
#1
Posted 09 December 2004 - 05:09 PM
If you're waiting for a feature you think is important, and you haven't heard anything about it for a while, feel free to mention it.
#2
Posted 09 December 2004 - 06:46 PM
#3
Posted 09 December 2004 - 11:28 PM
that's a great idea with the command-lists in the extra directory.
Tekl
#4
Posted 09 December 2004 - 11:54 PM
Thanks Chris!
#5
Posted 10 December 2004 - 01:29 PM
I don't know if some Editors may have problems with commandnames.txt. There are some commands with Parameters and I think most editor accept only one word:
If Var [not] in value1,value2,...
should be:
If
Else
Also I think, the directives could be in a separate file.
Tekl
#6
Posted 10 December 2004 - 01:47 PM
Rajat had some reasons for doing it that way. If he sees this, I'll let him explain it.If Var [not] in value1,value2,...
should be:
If
Else
You could check if the first character is # to detect whether it's a directive. That seems better than having to maintain a separate file.Also I think, the directives could be in a separate file.
Thanks.
#7
Posted 10 December 2004 - 02:14 PM
but if you have files, it's easier to create the colorgroups. So it could be done with only one array-loop. But it's no problem to use your way. Maybe all Syntax-files should be replaced with a script.
Tekl
#8
Posted 10 December 2004 - 05:36 PM
while doing the master files, my topmost consideration was to take care of all current and possibly future needs.Rajat had some reasons for doing it that way. If he sees this, I'll let him explain it.
now, the 'if' cmd can be (as u see urself) used in many different ways... so if we just put an 'if' for every corresponding if-based cmd in commands.txt then it'd not be clear which does what in clip-library like uses.
And if the use requires essentially just one word cmd then its easy to do [StringGetPos + StringLeft] but on the other hand, its kind of difficult to get the different full cmds from just 'if'.
i hope its clear now.
#9
Posted 10 December 2004 - 09:25 PM
That's an interesting idea. It would be nice some day to have a single GUI front-end that auto-detects the editors you have installed, sets the corresponding checkboxes for you (only by default -- you could uncheck them if you want), has some other checkboxes/radios/etc. to indicate your preferred background and syntax colors, and then reconfigures all the selected editors to support AutoHotkey syntax.Maybe all Syntax-files should be replaced with a script.
#10
Posted 11 December 2004 - 08:16 PM
I'm speaking about commandnames.txt. I thougt it should be used to build syntax-highlighting. All my Editors only want one single word for a command. For cliplibraries you're right, there should be all if-commands listed.
Hi Chris,
so someone should make a base-script with gui, where subroutines for every editor could be added or included, like plugins. For every editor there must be a detection-subroutine, so the gui displays only installed editors and a installation-routine for installing the syntax. The subroutines should set some global variables (if install successfull etc.) for the gui.
Tekl
#11
Posted 12 December 2004 - 02:26 AM
Perhaps you could omit all lines containing spaces as you process the file? Something like:All my Editors only want one single word for a command.
IfInString, A_LoopReadLine, %A_Space%, Continue
Yes, that sounds good. It would probably be a lot of work to research all the different editors, their registry entries, and the differences among their version numbers (if any). But hopefully someday.so someone should make a base-script with gui, where subroutines for every editor could be added or included
#12
BoBo
Posted 12 December 2004 - 01:06 PM
Tekl wrote:
All my Editors only want one single word for a command.
Chris wrote:
Perhaps you could omit all lines containing spaces as you process the file? Something like:
@ Tekl
I've extracted AHK's commands by parsing the Command reference which is provided in the forum. I've done that to keep the original command (first colum of that table) but split its description (2nd column) to translate that to German.
I guess a plain list (a word per line) could be the source to be converted in whatever format.
Eh, but maybe I've lost you ... ?
#13
Posted 12 December 2004 - 01:56 PM
#14
Posted 13 December 2004 - 01:07 AM
#15
Posted 15 December 2004 - 04:23 AM




