Show Posts
106
Ultra Hal 7.0 / Brain Plug-in gets 3 passes?
« on: April 12, 2008, 07:01:04 pm »
So now... with a more positive attitude...
Let me ask this... as an example, the space padding at each end of the UserSentence string... where does somebody get that information other than spending hours stumbling over it? And how many other things like that are there? I only knew of the existence of the UserSentence string by examining other peoples code and that's how this whole project has seemed to go so far, I find pieces here and pieces there, some out dated, some works, some don't, etc. Is there some relatively complete documentation for people who want to do major surgery on the brain and write their own plug-ins? Something that describes the details of how the exes, dlls, etc, effect the code and vise versa?
On the issue of only being able to execute the last haptek command in a plug-in, that seriously limits the flexibility of any script I could write. I had envisioned a script that would take several factors in to consideration and would make multiple adjustments to the haptek, the memory, etc, based on those conditions. I guess a less than satisfying solution would be to make all the calculations to build a multi-command string on the fly and feed it in a one big multiple command, IF that would work? But then we come back to the question of WHY is it like that in the first place? Is there a reason? Like the space padding reason?
Another thing I noticed that I hadn't mentioned yet, is that it seems to want everything within the Character folder. I can create sub-folders in the Character folder and the scripts have no problem with that, but if you try to tell the script to go outside that folder, it fails. An example...
If I use a path variable like... "haps\", and I have a folder in the Character folder named "haps", the script has no trouble finding that, which tells me that the brain automatically considers the Character folder to be the root. If I were to have a folder setup at "C:haps" and used a variable string of... "c:haps\", the script fails.
So these are the type of things that you need to know about to determine if you can work with or around them or if you should just start from scratch. But if these are things that have some valid reason for being that way, what are those reasons? Or at least, where's the list of things that will prevent you from coding normally, so I won't have to keep stumbling over them at the cost of major hours.
I have some very nice code from my home automation A.I. that I was hoping to be able to pretty much just drop in to Hals brain, but so far, even small parts of it have failed every time because of these unexpected surprises... so again, this may just be a case of me trying to make Hal something that it is not and that's my problem not Hal's, but if I had a better idea of what all those surprises were, then I could more easily make the decision to go Hal or go scratch. Even if I was to go scratch, I'd most likely keep Hal for the chatterbox on my computer, it really is the best by far that I've seen so far.
I totally, completely wipe a brain clean today, no brain, no plug-ins, I'll start there and see if I still keep running into these surprises.
Meanwhile... If anyone has the type of up to date, complete, documentation for programmers that I was talking about... could I get it from you please?
Thanks,
Jake
Let me ask this... as an example, the space padding at each end of the UserSentence string... where does somebody get that information other than spending hours stumbling over it? And how many other things like that are there? I only knew of the existence of the UserSentence string by examining other peoples code and that's how this whole project has seemed to go so far, I find pieces here and pieces there, some out dated, some works, some don't, etc. Is there some relatively complete documentation for people who want to do major surgery on the brain and write their own plug-ins? Something that describes the details of how the exes, dlls, etc, effect the code and vise versa?
On the issue of only being able to execute the last haptek command in a plug-in, that seriously limits the flexibility of any script I could write. I had envisioned a script that would take several factors in to consideration and would make multiple adjustments to the haptek, the memory, etc, based on those conditions. I guess a less than satisfying solution would be to make all the calculations to build a multi-command string on the fly and feed it in a one big multiple command, IF that would work? But then we come back to the question of WHY is it like that in the first place? Is there a reason? Like the space padding reason?
Another thing I noticed that I hadn't mentioned yet, is that it seems to want everything within the Character folder. I can create sub-folders in the Character folder and the scripts have no problem with that, but if you try to tell the script to go outside that folder, it fails. An example...
If I use a path variable like... "haps\", and I have a folder in the Character folder named "haps", the script has no trouble finding that, which tells me that the brain automatically considers the Character folder to be the root. If I were to have a folder setup at "C:haps" and used a variable string of... "c:haps\", the script fails.
So these are the type of things that you need to know about to determine if you can work with or around them or if you should just start from scratch. But if these are things that have some valid reason for being that way, what are those reasons? Or at least, where's the list of things that will prevent you from coding normally, so I won't have to keep stumbling over them at the cost of major hours.
I have some very nice code from my home automation A.I. that I was hoping to be able to pretty much just drop in to Hals brain, but so far, even small parts of it have failed every time because of these unexpected surprises... so again, this may just be a case of me trying to make Hal something that it is not and that's my problem not Hal's, but if I had a better idea of what all those surprises were, then I could more easily make the decision to go Hal or go scratch. Even if I was to go scratch, I'd most likely keep Hal for the chatterbox on my computer, it really is the best by far that I've seen so far.
I totally, completely wipe a brain clean today, no brain, no plug-ins, I'll start there and see if I still keep running into these surprises.
Meanwhile... If anyone has the type of up to date, complete, documentation for programmers that I was talking about... could I get it from you please?
Thanks,
Jake
]