Slow work

I'm sorry to report that I haven't been working too much on the port. Christmas, New Year and all the activities of the closing year have kept me really busy with life. Now I'm less than a month away from my wedding and there are still so many things to finish so there is no way I'll have much time to sit on the computer and program code. Still I have some code that needs to be commited to the CVS, and I'll see if I can find time to do that.

Just hoping that people can solve the problams they have with the trunk.

back on track again

After a pause I'm back at the code again. So far I have only manage to get a handle to the menu, I had to implement the WinPopupMenu API, and I'm thinking that maybe I should go ahead and do the same with WinCreateMenu. Right now I'm using WinCreateWindow with WC_MENU as the window class.

Next, implement the rest of the methods.

Pretty lost

After going all the steps I described before I began to come across some problems caused by my ignorance.
The first thing I noticed was that Menu class derives from Widget class, that means you skipped the whole Control class tree. Looking at the Win32 code I see the use of OS.CreateMenu() to create a menu with a bar and OS.CreatePopupMenu () to create a popup menu.
You could argue that we could use WinCreateMenu or WinCreateWindow with WC_MENU class to create a menu with a bar and WinPopUpMenu to create a popup. Looking at the docs clearly it takes a lot more than just calling those APIs to come up with a menu in OS/2. First question: is this so?.
The menu API is rich and I'm pretty confident that once I have a handle of a living menu we could quickly replicate the behavior we need.
Any ideas?. In any case I'm going to start calling these APIs and finding out what they do, but in case anyone has experience a helping hand would be reslly good.

Trying to set the Env.

I'm trying to set 7up the environment needed to compile the project using the branch for Watcom.

I installed OW and downloaded ANT. I already have Java141. I modified the env.cmd to point to my directories... now what. I realize there where no ant.cmd under the branch.... mmm wonder if I'm missing a big chunck of something.

I also finished adding the C stuctures and created the swt009_08 testcase that will be the base to test the Menu class.

Here goes a picture of the Group testscase

On to Menu class

I decided to begin the work on the Menu class. After going over the code I considered it not to be as hard as I thought to be.

I created the MENUITEM and OWNERITEM classes and added the constants needed by the API. Next I will go into the C code to add the stuctures for the new classes and then I'll prepare a testcase. Finally I'll begin the work on the class, method by method, like always.

After the menu class,,, I don't know, maybe someone will join me.. it feels pretty lonely here.

Little time

I'm picking up on the work on my RC model airplane. I have been working on it for years and from time to time I get the itch and I work on it. Besides that, I don't really do any computer work on weekends.

That said, I would say that there has been little progress on the launcher. It now shows the splash window and that's cool but as expected it fails. To test it I dowloaded the Eclipse 2.0.1 runtime for windows. After looking at the directories, I created the necessary ones following the naming convention and copying the necesary DLLs and JAR files from the port. I realized that the ant that I use doesn't create the swt.jar and in my opinion it should everytime we build the classes.

Since I'm stuck on the launcher and to be honest, I got bored, I decided that I'm going back to the Java code. Since I have no idea where to start with the Menu class, I'll just do some preparatory work, adding the constants, creating a testcase and adding the classes stubs to the project. I'll have more fun that way. At least I'm going to be feeling like I'm adding something new to the code.

I donwloaded a progress bar control that I found in a russian site, with examples. It looks cool and complete. Maybe that code can be added to the port since we don't have any progress bar code so far.

Launcher success

Yesterday I fixed the sources of the launcher2 program. First I dicovered that the library was a utility library done by the developer to simplify the development. Since adding that library was more trouble for me, I decided to replace the library with the code.

You get more lines but what the hell. After a successfukll compilation I included the ico file into the executable.

Finally I decided to go ahead and try the program. I searched the hard drive for a startup.jar file. The one that came up was one included with the sources I recieved. I moved the file into the exe directory and tested. The result... a java screen (awt I think) displaying the parameters passed onto the program and a nice message saying that everything was going OK.

I copied the original startup.jar file from the Eclipse distribution into the same directory, overwriting the one I used first to see if the results were the same.
Well the results were not the same. This time I got a message saying that the instalation directory wasn't found. A .workspace directory was created and a log file was written saying that the Eclipse structure wasn't found.

I'll experiment creating a Eclipse structure and trying then to see what happens.

The only problem that really bugs me it's the fact that I can't debug the C code under VAC++ 4.0. I'll be asking around about this.