Today we prepared the Conference, which is planned to have a workshop about visualFORTH, the organizers on the other side of the Atlantic, and me myself here.
The idea was to have a Conference-Call-Video-Connection tomorrow, using Skype.
This would it make possible for me to attend the Conference, and it would be possible for the attending listeners to ask questions directly.
There have been a lot of obstacles, the hardest one was to find a place in this rural area here with High Speed Internet-Connection. I was lucky to find a friend in the Computer Business who granted me to use his equipment. I ordered some Web-Cams, today the parcel arrived, and the first test could be made. After some normal problems to find out how works what we got a connection, first by audio, then by video.
It was amazing. I do not know if it was because I did see friends again after fifteen years and whom I now am sure I missed, even if it did not come to my consciousness, or because it was because of suddenly adapting a new technology I did not believe it really works.
I guess it was the first - or the second, partly, too? May be it was both. I am an Engineer used to look at things from a scientific emotionless point of view, but remember the time when the first affordable wireless phones came up, I was responsible for a project and had to be accessible all the time. I did not buy one of theses sneaky little cell phones * with everything inside to put it on the ear, but I bought a box with a real handset and a shoulder-strap, because I did not like to put the microwave onto my head to microwave my brain.
This was the first time I had this kind of emotional experience. Somehow I was proud to carry around this box so that everybody could see it (later I hided it in a briefcase, because meanwhile I was ashamed of myself), see how important I am (nowadays the bluetooth ear clips have this function).
It was great, it was fun, it was emotion to test this teleconferencing thing. I exceptional enjoyed it! I nearly could not let it go. But I had to. Midnight was approaching at the other end of the world, people got tired, and suddenly I remembered I had another appointment tonight I promised to be back for early enough.
A little, but important work I did before this test, waiting for the UPS-delivery. I made screenshots for a documentation which shall help to use the Installation-Batch I did yesterday.
Tomorrow I will put it together into a PDF, and next week, I hope, I have time to write the text documentation. I am really anxiously looking forward to our Workshop-Video-Conference on Friday.
*) By the way, seven years later in Luxembourg I worked for the son of the inventor of the cell phone!
Donnerstag, 26. März 2009
Mittwoch, 25. März 2009
Packaging
I am very happy about having finished the visualFORTH-Alpha-Version.
It took a lot of pressure from me, because I met the "shipping date", even some days earlier.
And I got an application done to demonstrate some special features of my visualFORTH.
Today's goal was the packaging. For ease of distribution everything has to be packed together - I hate installation procedures which tell you to put different things on different places.
I do not have the sources to manufacture an self-unpacking EXE, but I like to make it as easy as possible.
Since a lot of users already have their Win32Forth loaded from Sourceforge.net only a feature-patch is needed, and the simplest way to do this is to build a patch.bat and put it together with all feature folders into a zip-file named "program files".
This is the trick:
Downloading this zip-file into the root-directory C will with unzipping copy the batch-file and the feature-folders into the folder "Program Files", then select "Program Files, click on the batch file, and the "patchwork" is done by itself. I was really proud finding this out today. Microsoft did a great job making this possible.
It took a lot of pressure from me, because I met the "shipping date", even some days earlier.
And I got an application done to demonstrate some special features of my visualFORTH.
Today's goal was the packaging. For ease of distribution everything has to be packed together - I hate installation procedures which tell you to put different things on different places.
I do not have the sources to manufacture an self-unpacking EXE, but I like to make it as easy as possible.
Since a lot of users already have their Win32Forth loaded from Sourceforge.net only a feature-patch is needed, and the simplest way to do this is to build a patch.bat and put it together with all feature folders into a zip-file named "program files".
This is the trick:
Downloading this zip-file into the root-directory C will with unzipping copy the batch-file and the feature-folders into the folder "Program Files", then select "Program Files, click on the batch file, and the "patchwork" is done by itself. I was really proud finding this out today. Microsoft did a great job making this possible.
Dienstag, 24. März 2009
Alpha-Version finished
Nearly a week it's now since my last writing here. As you can imagine, the last days of finishing a product steal away all free time which is normally available every day.
I worked hard, but I made it. I worked on the connection to the underlying Forth Operating System, and I started with a helpful program I found somewhere as a useful example, and I really had to spend more than a day on that - five days it took to bring all the right things together, including making a sample application (which needed nearly a day, because it was connected with improvements of the redirect-files).
This little example program source "FileEmit.f" by Bertrand André Jacques was really helpful.
This program was to redirect the output to a file, and I first added the redirection to a Multiline TextBox, so I could compare what is visible on the MTxtBox and what is written into the file.
This way I could find out how the output to the screen worked. It took me more than two days, to do the adaptation in the right way, it was really tricky. The computer-screen and the Textbox have - as far as I found out - different rules.
I did not know about Row/Column-Addressing of the Textbox (I should have googled it, but I did not think that way), and the screen-output uses XY-addressing for every line and for each character when typed. With a lot of tricks I got it working. When finished, I removed the redirection to a file, I did not use it any more.
That was the easy part.
The next part was to redirect the input, i.e. to use PushButtons of a form instead of the normal keys of the computer keypad to connect to the operating system.
Both parts together that means, to use a Multiline TextBox and PushButtons of a form as Console to the Forth Operating System in an easy way, so that everybody can use it.
It needed as long as the first part, it works, but switching between keyboard and pushbutton array (remember the arrays I wrote about?) has a little hurdle, because - so I guess - the operating system is waiting for an input, still after the input is switched to the PushButton-Array. The result is: a last time before the switchover is in effect a key of the keyboard has to be pressed, and then it works properly.
I found if I start a program on the normal console which emits characters regularly, the switchover works fine. But I did not find out how to get it working with starting this program by another program. It should work somehow, I am sure of that, but I am not familiar enough with the internals of the operating system.
Thing is, most of these modules which have been written in machine language at times of DOS are now calls to the Windows-System, and there I have no chance to change that.
But behold, writing this, I remember I looked for input redirecting within Windows a while ago.
This is the second time now, that writing my Blog - telling the story to you - helps me to get some insight by myself. And now I remember I tried to find out input redirection, because I liked to insert a Barcode-Reader Converter Software Module into the keyboard input stream, and I did not find out how, not even with looking up on the Internet and not with looking at all my XP-Books. Finally I was happy to find a module on the Internet which just did the Barcode-Thing.
To type single characters using the Form-Pushbuttons works perfect, but one remaining part is to write complete words by pushing a single button. Here I am the first time to have to ask the experts. A few days from now is the first hands-on workshop for the Alpha-Version of visualFORTH, and next week I will ask experts and find out if they have a solution to fix this remaining problem.
I worked hard, but I made it. I worked on the connection to the underlying Forth Operating System, and I started with a helpful program I found somewhere as a useful example, and I really had to spend more than a day on that - five days it took to bring all the right things together, including making a sample application (which needed nearly a day, because it was connected with improvements of the redirect-files).
This little example program source "FileEmit.f" by Bertrand André Jacques was really helpful.
This program was to redirect the output to a file, and I first added the redirection to a Multiline TextBox, so I could compare what is visible on the MTxtBox and what is written into the file.
This way I could find out how the output to the screen worked. It took me more than two days, to do the adaptation in the right way, it was really tricky. The computer-screen and the Textbox have - as far as I found out - different rules.
I did not know about Row/Column-Addressing of the Textbox (I should have googled it, but I did not think that way), and the screen-output uses XY-addressing for every line and for each character when typed. With a lot of tricks I got it working. When finished, I removed the redirection to a file, I did not use it any more.
That was the easy part.
The next part was to redirect the input, i.e. to use PushButtons of a form instead of the normal keys of the computer keypad to connect to the operating system.
Both parts together that means, to use a Multiline TextBox and PushButtons of a form as Console to the Forth Operating System in an easy way, so that everybody can use it.
It needed as long as the first part, it works, but switching between keyboard and pushbutton array (remember the arrays I wrote about?) has a little hurdle, because - so I guess - the operating system is waiting for an input, still after the input is switched to the PushButton-Array. The result is: a last time before the switchover is in effect a key of the keyboard has to be pressed, and then it works properly.
I found if I start a program on the normal console which emits characters regularly, the switchover works fine. But I did not find out how to get it working with starting this program by another program. It should work somehow, I am sure of that, but I am not familiar enough with the internals of the operating system.
Thing is, most of these modules which have been written in machine language at times of DOS are now calls to the Windows-System, and there I have no chance to change that.
But behold, writing this, I remember I looked for input redirecting within Windows a while ago.
This is the second time now, that writing my Blog - telling the story to you - helps me to get some insight by myself. And now I remember I tried to find out input redirection, because I liked to insert a Barcode-Reader Converter Software Module into the keyboard input stream, and I did not find out how, not even with looking up on the Internet and not with looking at all my XP-Books. Finally I was happy to find a module on the Internet which just did the Barcode-Thing.
To type single characters using the Form-Pushbuttons works perfect, but one remaining part is to write complete words by pushing a single button. Here I am the first time to have to ask the experts. A few days from now is the first hands-on workshop for the Alpha-Version of visualFORTH, and next week I will ask experts and find out if they have a solution to fix this remaining problem.
Donnerstag, 19. März 2009
Some minor improvements
Today I had some kind of a lazy day, on the other hand I have to think about preparing myself for the conference end of March.
One-Click-Turnkey was a great achievement, the Button-Array was very complex and a lot to test, it's done. Today I removed some annoying behavior, changed some menu points for better accessibility, and introduced ctrl+F to start Forth-Console, ctrl+I to start the IDE, ctrl+E to edit an object, and I am sure this will help to do some things easier - for somebody who likes shortcuts, as I do, too.
Ah, yes, and I started with the connection to the underlying Forth Operating System. Somewhere I found a little program as example, but again, the devil is in the detail.
I guess I have to spend more than a day on that. Was a little bit frustrating today,
I have to improve my working strategy.
So long!
One-Click-Turnkey was a great achievement, the Button-Array was very complex and a lot to test, it's done. Today I removed some annoying behavior, changed some menu points for better accessibility, and introduced ctrl+F to start Forth-Console, ctrl+I to start the IDE, ctrl+E to edit an object, and I am sure this will help to do some things easier - for somebody who likes shortcuts, as I do, too.
Ah, yes, and I started with the connection to the underlying Forth Operating System. Somewhere I found a little program as example, but again, the devil is in the detail.
I guess I have to spend more than a day on that. Was a little bit frustrating today,
I have to improve my working strategy.
So long!
Mittwoch, 18. März 2009
Arrays done
This was the most complex task I worked on to get a feature I liked to have and I was sure it will be needed. Now an Array of up to 4x16 Buttons (or other objects) can be easily put into a form, only a few clicks needed, every one of these starts the same program module when clicked on it.
The click-started program module gets the information which button it was by reading the value Control#, it gets back the number of the object for identification.
I thought it took me longer than a week, but looking back on my own blog, it seems to be I just started on Monday. Looks really fast that way. It's a good thing to have a blog and therefore the written knowledge what work has been done. Marvelous!
Now I need a break. The next step will be an easy to use I/O-Interface to the Win32Forth Operating System.
So long!
The click-started program module gets the information which button it was by reading the value Control#, it gets back the number of the object for identification.
I thought it took me longer than a week, but looking back on my own blog, it seems to be I just started on Monday. Looks really fast that way. It's a good thing to have a blog and therefore the written knowledge what work has been done. Marvelous!
Now I need a break. The next step will be an easy to use I/O-Interface to the Win32Forth Operating System.
So long!
Dienstag, 17. März 2009
Arrays need an Index
Arrays need an Index to make them useful. I decided that if a button is clicked on, the number of this button will be put into a value which can be read by the program which is started by the Buttonclick. Sounds complicated, but I guess, this is the easiest way to do it and the easiest way to understand. Today I added this function , and the next step will be to clone the function of the first button to all other buttons of this array.
As a result this function has to be written only once, and depending on the number value of the activated button it can be executed differently or with different values. If you use a Button-Array as a numerical keypad, the number value of the button can be used just as the numerical value the button is intended to deliver. Easy, isn't it?
Today I had some other work to do, so the rest of it has to be postponed until tomorrow.
It seems to be we have springtime now: We do not have snow since two weeks and it was pleasant warm today, snowdrops are there since a week, and tulips are showing their first green tips. Squirrels are still feeding themselves on the birdseed.
Take care!
As a result this function has to be written only once, and depending on the number value of the activated button it can be executed differently or with different values. If you use a Button-Array as a numerical keypad, the number value of the button can be used just as the numerical value the button is intended to deliver. Easy, isn't it?
Today I had some other work to do, so the rest of it has to be postponed until tomorrow.
It seems to be we have springtime now: We do not have snow since two weeks and it was pleasant warm today, snowdrops are there since a week, and tulips are showing their first green tips. Squirrels are still feeding themselves on the birdseed.
Take care!
Montag, 16. März 2009
Steps forward in Button-Arrays
A new week again. First tests of the visualFORTH Alpha-Version have been done by our Alpha-Tester, and first experiences have been made. As usual, things happen which never happened when I was working with it, but I could immediately make an update. It is so easy, if the files to update are in the same Folder structure than all files of the Application, then with a simple copy-paste action all Files find their right place. I appreciate that Microsoft has done a great work to accomplish this. It is real great for updating, patching, and synchronizing. If these Update-Patches are done in chronological order, everything will be okay. And so it was.
Today I worked on Button-Arrays. I solved the problem of crashes when the array was more than 4x6 - I had to recognize that I used local variable definitions on places they do not belong.
After removing the obsolete dangerous definitions, it worked without crash. Some corrections I had to make depending on the size of the array, and I decided to stop working on this and to restrict arrays to a maximum size of 4x16, I think this is enough for the Beta-Version, range extensions will follow later.
The next step will be to make it possible to do the same action with each Array-Button, and delivering the Array-Button Number to the executing program.
Up to now I extracted the number, works fine, and tomorrow the remaining part will follow. Then I have to look for packaging.
See ya!
Today I worked on Button-Arrays. I solved the problem of crashes when the array was more than 4x6 - I had to recognize that I used local variable definitions on places they do not belong.
After removing the obsolete dangerous definitions, it worked without crash. Some corrections I had to make depending on the size of the array, and I decided to stop working on this and to restrict arrays to a maximum size of 4x16, I think this is enough for the Beta-Version, range extensions will follow later.
The next step will be to make it possible to do the same action with each Array-Button, and delivering the Array-Button Number to the executing program.
Up to now I extracted the number, works fine, and tomorrow the remaining part will follow. Then I have to look for packaging.
See ya!
Abonnieren
Posts (Atom)
