Changes between Version 5 and Version 6 of MPFramworkGSocWk

Timestamp:

Jul 3, 2008, 7:42:24 AM (16 years ago)

Author:

armahg@…

Comment:

--

MPFramworkGSocWk

@@ -33 +33 @@
 
 = Weeks 4 & 5 =
-This is a quick post. I'll elaborate and rewrite more later.
-
 I have completed documenting (with some gaps and holes) all of
 the Foundation Framework's classes. Of course that will undergo
@@ -40 +38 @@
 
 I also, completed bare, smoke Unit Tests for the MPMacPorts and all of those
-run successfully.
+run successfully. I will be unit testing more thoroughly later. For the most
+part, the current tests check that return values are not null, as opposed to 
+checking for correctness which I think they should do.
 
 We currently have a way to implement NSNotifications from within the
@@ -47 +47 @@
 be an acceptable solution to the Notfications issue.
 
-I did a build of Macports from trunk for the first time, applied a patch
-that will allow the Notifications code to work appropriately (it enables
-one to redefine the ui_init method in macports.tcl much in the same way
-that ui_prefix and ui_channels work). I was able to get the Framework running
-and passing Tests on the new MacPorts build with the patch. 
-
-I ran into a problem with Pextlib 1.0 not being found. If you try to install
+I am currently using a build of MacPorts from the source code in trunk.
+This was my first time doing this. I have been able to get the Framework
+running and passing tests on this new build (which includes a patch to
+allow for the Notifications sending).
+ 
+Whilst installing MacPorts from source, I ran into a problem with Pextlib 1.0 
+not being found. A little Googling showed me that this problem has occured before
+for some other users. If you try to install
 MacPorts from a trunk source build and have that problem, symlink tclsh
 in /usr/bin/ to tclsh8.4.7, it would have previously been pointing to tclsh8.4.
+That cleared up the problem for me.
+