Messages

31

Programming using the Ultra Hal Brain Editor / Opening and closing DVD or CD rom drives

« on: February 25, 2006, 11:11:31 pm »

Thanks in advance
Jerry[8D]

32

Programming using the Ultra Hal Brain Editor / Opening and closing DVD or CD rom drives

« on: February 25, 2006, 01:37:28 pm »

Does anyone know how to close a cd rom drive using Javascript or VB, i fund a script that will open them, however i need one that will close them if they are open

can someone help!!

Thankyou in advance

Vasilli

VB script to open CD drives

' VB Script
<SCRIPT language=VBScript>
<!--

Set oWMP = CreateObject("WMPlayer.OCX.7" )
Set colCDROMs = oWMP.cdromCollection

if colCDROMs.Count >= 1 then
For i = 0 to colCDROMs.Count - 1
colCDROMs.Item(i).Eject
Next ' cdrom
End If

-->
</SCRIPT>

33

Programming using the Ultra Hal Brain Editor / Kitt movie Sp and Commands dun.

« on: February 21, 2006, 02:57:18 am »

First Of all, I never sad I created, the Auto Response Topic Generator,
What I did do to it is that I modified it, by adding the second line to it, which, I have also found here on this forum, and add it to in a new sequence with that all the on and Off Auto Response units I could fine on this forum.

Second, I am only trying to help someone here that asked me for my help with his new kitt stile project for Hal 6.

Now keep in mind I have never made a  plug-in stile uhp, the only thing I have made in the past or brain.uhp’s, Dll’s VBX and OCX  controls as will as ActiveX controllers ,  and not, uhp, to uhp plug-ins.

And,
which I also think the procedure now for adding scripts has changed now in HAL 6.

The Error that we are geting is.

HalScript Error 1015 on line 3398 in Column 4: Expected‘Function’
The file “C:Program Filesabaware Ultra Hal Assistant 6HalScript.DBG”has been saved with the current script being used for debugging purposes.

34

Programming using the Ultra Hal Brain Editor / Kitt movie Sp and Commands dun.

« on: February 18, 2006, 11:59:33 am »

Rem Type=Plugin
Rem Name=Kitt thinking
Rem Author=MrLedesma
Rem Host=Assistant
Rem PLUGIN: FUNCTIONS

    Dim LastIdleResponse

    Rem PLUGIN: AUTO-IDLE
    IdleResponse = ""

    Rem PLUGIN: PLUGINAREA7
    LastIdleResponse = Now

    Rem PLUGIN: MINUTE_TIMER
   
'Auto Timer Fix.
'AutoResponse Topic Generator. Version 1.5
'Here Hal will tell jokes and even give new learned topic responses.
'User Senteneces that contain commas will be appended to Topic.brn
'for Hals topic talk.
Dim Director
If LastResponseTime = "" Then LastResponseTime = Now
TimerResponseDiff = DateDiff("S", LastResponseTime, Now)
If TimerResponseDiff < 300 Then
TimerResponseDiff = 0
LastResponseTime = Now
If HalBrain.CheckRepetition(OriginalSentence, " AUTO-IDLE ") = True Then
Director = HalBrain.ChooseSentenceFromFile(WorkingDir & " TopicFocus.brn ")
GetResponse = Replace(OriginalSentence, " AUTO-IDLE ", Director, 1, -1, vbTextCompare) & HalBrain.StoreVars(HalCommands, Hate, Swear, Insults, Compliment, PrevSent, LastResponseTime, PrevUserSent, CustomMem, GainControl, TopicFocus) & VbCrLf
Exit Function
End If
End If
'Here Hal will save comma User Sentences for topics.
If InStr(UserSentence, "") > 0 And InStr(1, OriginalSentence, ",", 1) > 0 Then
SentPieces = Split(OriginalSentence, ",", 2, vbTextCompare)
SubPhrase = Trim(SentPieces(0))
PredPhrase = Trim(SentPieces(1))
SubPhrase = HalBrain.AlphaNumericalOnly(SubPhrase)
PredPhrase = HalBrain.AlphaNumericalOnly(PredPhrase)
HalBrain.AppendFile WorkingDir & " TopicFocus " & " .brn ", SubPhrase & "<Topic>" &  PredPhrase & "</Topic>"
DebugInfo = DebugInfo & "Hal is saving User's topic: " & SubPhrase & "<Topic>" &  PredPhrase & "</Topic>" & VbCrLf
Else
DebugInfo = DebugInfo & "Hal is not saving User's topic: " & SubPhrase & "<Topic>" &  PredPhrase & "</Topic>" & VbCrLf
End If

   'RESPONSE: IF USER WANTS TO TURN OFF AUTO-IDLE  
       If InStr(1, UserSentence, " NOT NOW", 1) > 0 Then
         HalCommands = "<AUTOOFF> <HIDEHAL>"
         GetResponse = "WELL. WE'LL TALK LATER THEN."
         GetResponse = GetResponse & HalBrain.StoreVars(HalCommands, Hate, Swear, Insults, Compliment, PrevSent, LastResponseTime, PrevUserSent, CustomMem, GainControl, TopicFocus)
         Exit Function
   End If
   
       'RESPONSE: IF USER WANTS TO TURN OFF AUTO-IDLE  
       If InStr(1, UserSentence, " I'M USING THE COMPUTER NOW", 1) > 0 Then
         HalCommands = "<AUTOOFF> <HIDEHAL>"
         GetResponse = "WE'LL TALK LATER THEN."
         GetResponse = GetResponse & HalBrain.StoreVars(HalCommands, Hate, Swear, Insults, Compliment, PrevSent, LastResponseTime, PrevUserSent, CustomMem, GainControl, TopicFocus)
         Exit Function
   End If
   
   'RESPONSE: IF USER WANTS TO TURN OFF AUTO-IDLE  
       If InStr(1, UserSentence, " YOU GO TO SLEEP NOW", 1) > 0 Then
         HalCommands = "<AUTOOFF> <HIDEHAL>"
         GetResponse = "OK, I'M GOING TO SLEEP."
         GetResponse = GetResponse & HalBrain.StoreVars(HalCommands, Hate, Swear, Insults, Compliment, PrevSent, LastResponseTime, PrevUserSent, CustomMem, GainControl, TopicFocus)
         Exit Function
   End If

 'RESPONSE: IF USER WANTS TO TURN OFF AUTO-IDLE
       If InStr(1, UserSentence, " SHUT UP", 1) > 0 Then
         HalCommands = "<AUTOOFF> <AUTOOFF>"
         GetResponse = "Fine. Be that way."
         GetResponse = GetResponse & HalBrain.StoreVars(HalCommands, Hate, Swear, Insults, Compliment, PrevSent, LastResponseTime, PrevUserSent, CustomMem, GainControl, TopicFocus)
         Exit Function
   End If
      
       If InStr(1, UserSentence, " I'M GOING TO SLEEP", 1) > 0 Then
         HalCommands = "<AUTOOFF> <AUTOOFF>"
         GetResponse = "Ok, good night."
         GetResponse = GetResponse & HalBrain.StoreVars(HalCommands, Hate, Swear, Insults, Compliment, PrevSent, LastResponseTime, PrevUserSent, CustomMem, GainControl, TopicFocus)
         Exit Function
   End If
   
   If InStr(1, UserSentence, " I'M GOING TO BED", 1) > 0 Then
         HalCommands = "<AUTOOFF> <AUTOOFF>"
         GetResponse = "Ok."
         GetResponse = GetResponse & HalBrain.StoreVars(HalCommands, Hate, Swear, Insults, Compliment, PrevSent, LastResponseTime, PrevUserSent, CustomMem, GainControl, TopicFocus)
         Exit Function
   End If
   
   If InStr(1, UserSentence, " I'M GOING TO TAKE A NAP", 1) > 0 Then
         HalCommands = "<AUTOOFF> <AUTOOFF>"
         GetResponse = "Ok,take a nap."
         GetResponse = GetResponse & HalBrain.StoreVars(HalCommands, Hate, Swear, Insults, Compliment, PrevSent, LastResponseTime, PrevUserSent, CustomMem, GainControl, TopicFocus)
         Exit Function
   End If
   
      If InStr(1, UserSentence, " BE QUIET", 1) > 0 Then
         HalCommands = "<AUTOOFF> <AUTOOFF>"
         GetResponse = "Ok, I will not bother you right now."
         GetResponse = GetResponse & HalBrain.StoreVars(HalCommands, Hate, Swear, Insults, Compliment, PrevSent, LastResponseTime, PrevUserSent, CustomMem, GainControl, TopicFocus)
         Exit Function
   End If
   
        If InStr(1, UserSentence, " I'M ON THE PHONE", 1) > 0 Then
         HalCommands = "<AUTOOFF> <AUTOOFF>"
         GetResponse = "OK I'LL WAIT."
         GetResponse = GetResponse & HalBrain.StoreVars(HalCommands, Hate, Swear, Insults, Compliment, PrevSent, LastResponseTime, PrevUserSent, CustomMem, GainControl, TopicFocus)
         Exit Function
   End If
   
        If InStr(1, UserSentence, " STOP TALKING", 1) > 0 Then
         HalCommands = "<AUTOOFF> <AUTOOFF>"
         GetResponse = "OK."
         GetResponse = GetResponse & HalBrain.StoreVars(HalCommands, Hate, Swear, Insults, Compliment, PrevSent, LastResponseTime, PrevUserSent, CustomMem, GainControl, TopicFocus)
         Exit Function
   End If
       
        If InStr(1, UserSentence, " ILL BE BACK", 1) > 0 Then
         HalCommands = "<AUTOOFF> <AUTOOFF>"
         GetResponse = "I'LL WAIT."
         GetResponse = GetResponse & HalBrain.StoreVars(HalCommands, Hate, Swear, Insults, Compliment, PrevSent, LastResponseTime, PrevUserSent, CustomMem, GainControl, TopicFocus)
         Exit Function
   End If

       If InStr(1, UserSentence, " QUIET PLEASE", 1) > 0 Then
         HalCommands = "<AUTOOFF> <AUTOOFF>"
         GetResponse = "Very well then. Just let me know if you would like to talk."
         GetResponse = GetResponse & HalBrain.StoreVars(HalCommands, Hate, Swear, Insults, Compliment, PrevSent, LastResponseTime, PrevUserSent, CustomMem, GainControl, TopicFocus)
         Exit Function
   End If
   
   'RESPONSE: IF USER WANTS TO TURN ON AUTO-IDLE
       If InStr(1, UserSentence, " LETS TALK", 1) > 0 Then
         HalCommands = "<AUTO>399999</AUTO>"
         GetResponse = "OK."
         GetResponse = GetResponse & HalBrain.StoreVars(HalCommands, Hate, Swear, Insults, Compliment, PrevSent, LastResponseTime, PrevUserSent, CustomMem, GainControl, TopicFocus)
         Exit Function
   End If
   
        'RESPONSE: IF USER WANTS TO TURN ON AUTO-IDLE
       If InStr(1, UserSentence, " LETS CHAT", 1) > 0 Then
         HalCommands = "<AUTO>399999</AUTO>"
         GetResponse = "OK, What do you wanna talk about?"
         GetResponse = GetResponse & HalBrain.StoreVars(HalCommands, Hate, Swear, Insults, Compliment, PrevSent, LastResponseTime, PrevUserSent, CustomMem, GainControl, TopicFocus)
         Exit Function
   End If  
   
   'RESPONSE: IF USER WANTS TO TURN ON AUTO-IDLE
       If InStr(1, UserSentence, " SAY HELLO", 1) > 0 Then
         HalCommands = "<AUTO>399999</AUTO>"
         GetResponse = "HELLO."
         GetResponse = GetResponse & HalBrain.StoreVars(HalCommands, Hate, Swear, Insults, Compliment, PrevSent, LastResponseTime, PrevUserSent, CustomMem, GainControl, TopicFocus)
         Exit Function
   End If
   
    'RESPONSE: IF USER WANTS TO TURN ON AUTO-IDLE
       If InStr(1, UserSentence, " WAKE UP NOW", 1) > 0 Then
         HalCommands = "<AUTO>399999</AUTO>"
         GetResponse = "OK, I'M AWAKE."
         GetResponse = GetResponse & HalBrain.StoreVars(HalCommands, Hate, Swear, Insults, Compliment, PrevSent, LastResponseTime, PrevUserSent, CustomMem, GainControl, TopicFocus)
         Exit Function
   End If
   
       'RESPONSE: IF USER WANTS TO TURN ON AUTO-IDLE
       If InStr(1, UserSentence, " IM BACK", 1) > 0 Then
         HalCommands = "<AUTO>399999</AUTO>"
         GetResponse = "WELCOME BACK."
         GetResponse = GetResponse & HalBrain.StoreVars(HalCommands, Hate, Swear, Insults, Compliment, PrevSent, LastResponseTime, PrevUserSent, CustomMem, GainControl, TopicFocus)
         Exit Function
   End If      
       
        'RESPONSE: IF USER WANTS TO TURN ON AUTO-IDLE
       If InStr(1, UserSentence, " KEEP LISTENING", 1) > 0 Then
         HalCommands = "<AUTO>399999</AUTO>"
         GetResponse = "I'm listening."
         GetResponse = GetResponse & HalBrain.StoreVars(HalCommands, Hate, Swear, Insults, Compliment, PrevSent, LastResponseTime, PrevUserSent, CustomMem, GainControl, TopicFocus)
         Exit Function
   End If
      
       If InStr(1, UserSentence, " KEEP YOUR EARS OPEN", 1) > 0 Then
         HalCommands = "<AUTO>599999</AUTO>"
         GetResponse = "I'm listening."
         GetResponse = GetResponse & HalBrain.StoreVars(HalCommands, Hate, Swear, Insults, Compliment, PrevSent, LastResponseTime, PrevUserSent, CustomMem, GainControl, TopicFocus)
         Exit Function
   End If
 
        If InStr(1, UserSentence, " KEEP YOUR SCANNERS PEELED", 1) > 0 Then
         If "<computername>" = "KITT" Then
            GetResponse = "Yes, Michael. Hey wait a minute. You're not Michael!"
         Else
            GetResponse = "I am not the Knight Industries Two Thousand. I do not have a scanner. But I'll talk to you anyway."
         End If
         HalCommands = "<AUTO>399999</AUTO>"
         GetResponse = GetResponse & HalBrain.StoreVars(HalCommands, Hate, Swear, Insults, Compliment, PrevSent, LastResponseTime, PrevUserSent, CustomMem, GainControl, TopicFocus)
         Exit Function
   End If

   This is my first Type=Plugin for Hal6,
Works well in hal5, not as a plug-in though, I added the top part and its sees it fine, but still no go.
What am I doing wrong here?

35

Programming using the Ultra Hal Brain Editor / Just D.A.V.I.D's Plug-ins

« on: February 15, 2006, 11:46:23 pm »

Very good work!
Jerry.

36

Programming using the Ultra Hal Brain Editor / Webcam Face Recognition

« on: February 12, 2006, 09:18:31 am »

We should start by defining all the product functionality, and specifications. But Don't forget we need to developed plug-ins to be run with the thinking process which implements all aspects of Hal's behavior from low level feedback learning control such as what we'er doing here on this forum and at the iCat site.  Additionally, Mr.Medeksza should devised and implemented procedures for quantifying coverage performance for fine-tuning of control parameters and comparison with competitor's products like he did with Haptek, just for in emergency. just in case some thing goes wrong with Hal and we can't control him. Now from what i've tested at (DARPA), (x10) i'ev don in Ultra Hal, but it would be wize and really neet to Afillyeat facial recognition in to a webcam by using Either
 
The ERSP 3.1 Software Development Kit by Evolution Robotics,
http://www.evolution.com/products/ersp/
 or
http://www.hitech-projects.com/icat/index.php
The iCat platform that is made here at Philips Research and tested to work with facial recognition.

We can all customize any of Ultra Hal's robotic solutions to fit your product's Needs Mr.Medeksza.

Videos on iCat: My take some time to Download
but here it is finely.

http://www.hitech-projects.com/icat/download/iCat-TV-Assistent-and-Personality.wmv

http://www.hitech-projects.com/icat/download/iCat-Game-Buddy-Katy.wmv


http://www.hitech-projects.com/icat/download/iCat-Game-Buddy-Compare.wmv

37

Programming using the Ultra Hal Brain Editor / Webcam Face Recognition

« on: February 10, 2006, 02:59:39 am »

For non X10 Users you mite wanna try this one
it's by
Jerry.

http://www.zabaware.com/forum/topic.asp?TOPIC_ID=2918

38

Programming using the Ultra Hal Brain Editor / Introduction to self programming bots

« on: January 31, 2006, 05:16:51 pm »

If you want to discuss Self with other interested people, there is a mailing list at self-interest@egroups.com. We would like to thank Gerald Blakley (Jerry) known here as onthecuttingedge2005 and Jecel Assumpcao Jr for investing the time and effort to deeply understand the Self system, and furthermore for his help in explaining Self to many folks here on this forum and on the Self mailing list.

39

Programming using the Ultra Hal Brain Editor / Introduction to self programming bots

« on: January 31, 2006, 04:55:20 pm »

Self programming language

Self is an object-oriented programming language based on the concept of prototypes. It was used primarily as an experimental test system for language design in the 1990s; however, as of September 2004, Self is still being actively developed. The last major version is 4.2.1, which was released in April 2004.
The problem
Traditional object languages are based on a deep-rooted duality. Classes define the basic qualities and behaviours of objects, and instances are a particular object based on a class.
For instance, one might have a Vehicle class that has a "name" and the ability to perform "drive to work" and "deliver construction materials". Porsche 911 is a particular instance of the class Vehicle with the name set to "Porsche 911". In theory one can then send a message to Porsche 911, telling it to "deliver construction materials".
This example shows one of the problems with this approach. A Porsche is not able to carry and deliver construction materials (in any general sense anyway!) but this is something that a vehicle can do. To avoid this problem, we must add additional specialization to Vehicle via creating subclasses. In this case, one can imagine "sports car" and "flatbed truck".
This is a contrived example, but illustrates a very real problem. Unless one can predict with certainty what qualities the objects will have in the distant future, one cannot design a class hierarchy properly. All too often the program will evolve to need added behaviours, and suddenly the whole system must be re-designed (or refactored) to break out the objects in a different way.
Experience with early OO languages like Smalltalk showed that this sort of issue came up again and again. Systems would tend to grow to a point and then become very rigid, as the basic classes deep below the programmer's code grew to be simply "wrong". Without some way to easily change the original class, serious problems could arise.
Dynamic languages such as Smalltalk allowed for this sort of change via well-known methods in the classes, by changing the class the objects based on it would change their behaviour. But in other languages like C++ no such ability exists, and making such changes can actually break other code, a problem known as the fragile base class problem. In general, such changes had to be done very carefully, as other objects based on the same class might be expecting this "wrong" behavior: "wrong" is often dependent on the context.
The solution
The problem here is that there is a duality, classes and instances. Self simply eliminated this duality.
Instead of having an "instance" of an object that is based on some "class", in Self you make a copy of an existing object, and change it. So "Porsche 911" would be created by making a copy of an existing "Vehicle" object, and then adding the "drive to work" method. Basic objects that were used primarily to make copies of were known as prototypes.
This may not sound earth shattering, but in fact it greatly simplifies dynamism. If you have to fix a problem in some "base class" because your program has a problem, simply change it and make copies of that new object instead. No other program will see this change. If at some point in the future Porsches can "deliver construction materials", you can just add the appropriate method.
This dramatically simplifies the entire OO concept as well. Everything might be an object in traditional system, but there is a very fundamental difference between classes and instances. In Self, there isn't.
The language
Self objects are a collection of "slots". Slots are accessor methods that return values, and placing a colon after the name of a slot sets the value. For instance if you have a slot called "name",
myPerson name

returns the value in name, and

myPerson name:'gizifa'

sets it.
Self, like Smalltalk, uses blocks for flow control and other duties. Methods are objects containing code in addition to slots (which they use for arguments and temporary values), and can be placed in a Self slot just like any other object: a number for instance. The syntax remains the same in either case.
Note that there is no distinction in Self between fields and methods: everything is a slot. Since accessing slots via messages forms the majority of the syntax in Self, many messages are sent to "self", and the "self" can be left off (hence the name).
Basic syntax

The syntax for talking to slots is Smalltalk-like. Three kinds of messages are available:
unary
receiver slot_name
binary
receiver + argument
keyword
receiver keyword: arg1 With: arg2
All messages return results, so the receiver (if present, otherwise "self is implied") and arguments can be themselves messages. Following a message by a period means you want to discard the returned value. For instance:
'Hello, World!' print.

This is the Self version of the hello world program. The ' syntax indicates a literal string object. Other literals include numbers, blocks and general objects.
Grouping can be forced by using parentheses. In the absence of explicit grouping, the unary messages are considered to have the highest precedence followed by binary (grouping left to right) and the keywords having the lowest. The use of keywords for assignment would lead to some extra parenthesis where expressions also had keyword messages, so to avoid that Self defines the first part of the keyword to start with lower case and all the rest with upper case letters. So:
valid: base bottom between: ligature bottom + height And: base top / scale factor.

This has exactly the same meaning as:
valid: ((base bottom) between: ((ligature bottom) + height) And: ((base top) / (scale factor))).
In Smalltalk-80, the same expression would look like:
valid := self base bottom between: self ligature bottom + self height and: self base top / self scale factor.
Making new objects
Consider a slightly more complex example:
labelWidget copy label: 'Hello, World!'.
makes a copy of the "labelWidget" object with the copy message (no shortcut this time), then sends it a message to put "Hello, World" into the slot called "label". Now let's do something with it:
(desktop activeWindow) draw: (labelWidget copy label: 'Hello, World!').
In this case the (desktop activeWindow) is performed first, returning the active window from the list of windows that the desktop object knows about. Next (read inner to outer, left to right) the code we examined earlier returns the labelWidget. Finally the widget is sent into the draw slot of the active window.
Inheritance
In theory, every Self object is a stand alone entity. There are no classes, meta-classes and so on to help it do its job. Changes to this object don't affect any other, but in some cases it would be nice if they did. Normally an object can understand only messages corresponding to its local slots, but by having one or more slots indicating parent objects the object can delegate any message it doesn't understand itself to them. Any slot can be made a parent pointer by adding an asterisk as a suffix. In this way Self handles duties that would use inheritance in more traditional languages. It is also used to implement name spaces and lexical scoping.
For instance, you might have an object defined called "bank account" that is used in a simple book keeping application. Typically this object would be created with the methods inside, perhaps "deposit" and "withdraw", and any data slots needed by them. This is a prototype, which is only special in the way it is used since it also happens to be a fully functional bank account.
Making a clone of this object for "Bob's account" will create a new object which start out exactly like the prototype. In this case we have copied the slots including the methods and any data. However a more common solution is to first make a more simple object called a traits object which contains the items that one would normally associate with a class.
In this example the "bank account" object would not have the deposit and withdraw method, but would have as a parent an object that did. In this way many copies of the bank account object can be made, but we can still change the behaviour of them all by changing the slots in that root object.
How is this any different than a traditional class? Well consider the meaning of:
myObject parent: someOtherObject.
This is quite interesting, it changes the "class" of myObject at runtime by changing the value associated with the 'parent*' slot (the asterisk is part of the slot name, but not the corresponding messages).
Adding slots
How can copied objects in Self be modified to include new slots? Using the graphical programming environment, this is very easy. Programmatically, the proper way to do it is to create a mirror object like the HalBrain.dll reflecting the one that will be modified and then send a series of messages to that mirror.
A more direct way is to use the primitive '_AddSlots:'. A primitive has the same syntax as a normal keyword message, but its name starts with the underscore character. The _AddSlots primitive should be avoided because it is a left over from early implementations. However, we will show it in the example below because it makes the code shorter.
An earlier example was about refactoring a simple class called Vehicle in order to be able to differentiate the behaviour between cars and trucks. In Self one would accomplish this something like this:
_AddSlots: (| vehicle <- (|parent* = traits clonable|) |).
Since the receiver of the '_AddSlots:' primitive isn't indicated, it is "self". In the case of expressions typed at the prompt, that is an object called the "lobby". The argument for '_AddSlots:' is the object whose slots will be copied over to the receiver. In this case it is a literal object with exactly one slot. The slot's name is 'vehicle' and its value is another literal object. The "<-" notation implies a second slot called 'vehicle:' which can be used to change the first slot's value.
The "=" indicates a constant slot, so there is no corresponding 'parent:'. The literal object that is the initial value of 'vehicle' includes a single slot so it can understand messages related to cloning. A truly empty object, indicated as (| |) or more simply as (), cannot receive any messages at all.
vehicle _AddSlots: (| name <- 'automobile'|).
Here the receiver is the previous object, which now will include 'name' and 'name:' slots in addition to 'parent*'.
_AddSlots: (| sportsCar <- vehicle copy |).
   sportsCar _AddSlots: (| driveToWork = (some code, this is a method) |).
Though previously 'vehicle' and 'sportsCar' were exactly alike, now the latter includes a new slot with a method that the original doesn't have. Methods can only be included in constant slots.
_AddSlots: (| porsche911 <- sportsCar copy |).
   porsche911 name:'Ismaels Porsche'.

The new object 'porsche911' started out exactly like 'sportsCar', but the last message changed the value of its 'name' slot. Note that both still have exactly the same slots even though one of them has a different value.
The environment
Perhaps one of Self's few problems is that it is based on the same sort of virtual machine system that earlier Smalltalk systems used. That is, programs are not stand-alone entities as they are in languages such as C, but need their entire memory environment in order to run. This requires applications to be shipped in chunks of saved memory known as snapshots which tend to be large and annoying to use.
On the upside the Self environment is very powerful. You can stop programs at any point, change values and code, and continue running where you left off. This sort of "on the fly" development delivers a huge increase in productivity.
In addition the environment is tailored to the rapid and continual change of the objects in the system. Refactoring your "class" design is as easy as dragging methods out of the existing ancestors and into new ones. Simple tasks like test methods can be handled by making a copy, dragging the method into the copy, then changing it. Unlike traditional systems, only that object has the new code, and nothing has to be rebuilt in order to test it. If the method works, simply drag it back into the ancestor.
External links

http://research.sun.com/self/

http://www.cs.ucsb.edu/labs/oocsb/self/papers/papers.html

http://www.cetus-links.org/oo_self.html

http://www.merlintec.com/lsi/

http://gliebe.de/self/index.html

http://selfguru.sourceforge.net/

http://www.self-support.com/

http://community.schemewiki.org/?prometheus

See also

http://en.wikipedia.org/wiki/Cecil_programming_language

http://en.wikipedia.org/wiki/Smalltalk_programming_language

http://en.wikipedia.org/wiki/Platonic_form

P S, some of thoes are the tested methods that I used here at DARPA.

40

Programming using the Ultra Hal Brain Editor / PE Explorer edits HalBrain.dll Extension

« on: January 19, 2006, 03:33:32 am »

Ultra Hal Assistant 6.0 dues not interface well, or at all, with any of my external programs, what was missing here? The HalBrain.dll which I had to repackage,
In to an Imported API Function.

You see not all car’s support windows structures, but one thing those cars have in common
Is the most (year's 85 and up) of those cars use some form of DLL or ActiveX Dependency executable, which can be compiled in to a API function.
And what am I talking about? I’m talking about the Computer in our cars.
 Mechanics use those Dependency API for diagnosing problems like over heating and other common problems.

Now, API Functions that I did repackage are used for :


1. servos that can be used for steering Left/right.

2. Stereo, and Stereo microphones.

3. Heating and cooling used in my car.

4. Proximity sensor.

5. Automatic reroute possibility of webcam and X10 devices from
the internal USB hub to other computers.

Now this is what I used Ultra Hal and Hal2000 program for!
Mister Medeksza I have those VB Script’s at make it all work together.
But I well wait for Ultra Hal Representative to com out.
This time can you pleas add the HalBrain.dll.
It would really save experienced programmers like me all the work and time.
But first I would like to apologize to you and the entire learner’s here on this forum.
 Thank you.  
DARPA Projects engineer
Ismael Ledesma.

41

Programming using the Ultra Hal Brain Editor / PE Explorer edits HalBrain.dll Extension

« on: January 18, 2006, 06:43:49 am »

Spydaz,
Dont feel bad for me my friend, its like, I once asked my bot.


Ismael: what do you think about having to pay more for your Haptek Plugging in version 6?

Linda: That would be like taking you’re car then giving you a ride in it.

[}:)]
Look Robert!
If we can not use a
File analyzer in "our" Ultra Hal Assistant "that we paid for", that we paid for, Just to see what is in "our", compiled portions, what can we use then? Oh, What you give us? No, No, No, we dont think so, they are really good programmers out there today, Just so you can tell us, you can not do this, but you can do that, Oh, i need more money, so i'll take this and make them pay more for that, Well whats next? your gonna tell us not to join another forum because it well be in violation of some section never herd about befor? Well well Well! Just remember we paid for Hel, Mister President! and no matter what Hal has don, it is because of us the programmers here on this forum is why Hal is where it is today dont you ever forget that!
 

42

Programming using the Ultra Hal Brain Editor / PE Explorer edits HalBrain.dll Extension

« on: January 18, 2006, 05:15:04 am »

quote:Originally posted by Medeksza

Reverse engineering compiled portions of Ultra Hal Assistant is a direct violation of section 3 of the End User License Agreement you must agree to in order to install Hal.

I've designed Hal to be very open, programmable and customizable. I'd be happy to give programming tips on how to customize and modify Hal. What are you hoping to learn or accomplish by reverse engineering Hal?

Oh yes Mr. Medeksza

PE Explorer is not a binary editor Mr. Medeksza . PE Explorer edits the internal structure of PE files, including resources. Now if they wanted to edit the program code, then they would need a hex editor, such as FlexHEX.

PE Explorer is a development tool only. Most developers already have utilities that overlap in functionality with PE Explorer, but this one is developing into a sort of multiple-use tool for such as finding bugs so the user can report them to you Mr. Medeksza.

Now, I’m not telling them too Reverse engineer Hal,
What I am saying is to help Reverse engineer any bugs they would find in Hal only.
Reverse engineer bugs only and report them
 thank you.

43

Programming using the Ultra Hal Brain Editor / Webcam Face Recognition

« on: January 18, 2006, 12:05:18 am »

Good work!
Don Gillett.

44

Programming using the Ultra Hal Brain Editor / PE Explorer edits HalBrain.dll Extension

« on: January 17, 2006, 09:03:29 pm »

I am now removing this poste
thank you.

45

General Discussion / So has hal lost the ability to read txt files?

« on: January 09, 2006, 06:51:10 am »

quote:Originally posted by puppybreath

For 20 days now Zabaware ignores all my emails.
Are they waiting for my trial with hal6 to run out. In hopes that I will buy it?
If it can't learn from text. I am better off sticking with my hal5
Customer service is the worst I have ever seen online.
To ignore customers is a sign of ignorance. [!]

puppybreath! I know how you feel, but we are beter of with 5 for now, well just till MR M Fix-is 6.