pyobjc-dev

[Pyobjc-dev] re: My second roadblock

[Gary R. <gro...@tr...>]

> Yes, but if you follow Apple's tutorial up to the the step listed in
> the tutorial, you don't have the two instances ConverterController and
> Converter... So there's a missing step somewhere.

Wait, I figured it out. My silliness.

The PyObjC tutorial says stop when you get to "Implementing the Classes of
Currency Converter" in the Apple tuturial.

However, I stopped when I got to "Defining the Classes of Currency
Converter" which is very different!

Seems like Zac did the same thing??


Even tho this was my error, to make sure other people don't fall into the
same silliness, you might want to change the tutorial to say: "Work through
Defining the Classes of Currency Converter, Connecting ConverterController
to the Interface, and stop at  Implementing the Classes of Currency
Converter".

HOWEVER, I still have a problem. The CurrencyConverter.py I get after doing
all that is identical to step4-CurrencyConverter.py, except the latter
contains 

    from Foundation import NSObject, NSObject

as the first line, and mine doesn't have any line importing NSObject.

Of course I can manually edit the file to add the import, but does anybody
have any idea why it wasn't put there automatically?



--Gary

-- 
[http://ThisURLEnablesEmailToGetThroughOverzealousSpamFilters.org]

Gary Robinson
CEO
Transpose, LLC
gro...@tr...
207-942-3463
http://www.transpose.com
http://radio.weblogs.com/0101454

Re: [Pyobjc-dev] re: My second roadblock

[Just v. R. <ju...@le...>]

Gary Robinson wrote:

> HOWEVER, I still have a problem. The CurrencyConverter.py I get after
> doing all that is identical to step4-CurrencyConverter.py, except the
> latter contains 
> 
>     from Foundation import NSObject, NSObject
> 
> as the first line, and mine doesn't have any line importing NSObject.
> 
> Of course I can manually edit the file to add the import, but does
> anybody have any idea why it wasn't put there automatically?

Because it shouldn't be needed, the file in the tutorial was generated
with an earlier version of NibClassBuilder.py, and someone forgot to
update the tutorial (me). So: the code should be just fine...

Just

Re: [Pyobjc-dev] re: My second roadblock

[Zachery B. <zb...@ur...>]

On Tuesday, May 6, 2003, at 04:14 PM, Gary Robinson wrote:

>> Yes, but if you follow Apple's tutorial up to the the step listed in
>> the tutorial, you don't have the two instances ConverterController and
>> Converter... So there's a missing step somewhere.
>
> Wait, I figured it out. My silliness.
>
> The PyObjC tutorial says stop when you get to "Implementing the 
> Classes of
> Currency Converter" in the Apple tuturial.
>
> However, I stopped when I got to "Defining the Classes of Currency
> Converter" which is very different!
>
> Seems like Zac did the same thing??

d'oh.

> Even tho this was my error, to make sure other people don't fall into 
> the
> same silliness, you might want to change the tutorial to say: "Work 
> through
> Defining the Classes of Currency Converter, Connecting 
> ConverterController
> to the Interface, and stop at  Implementing the Classes of Currency
> Converter".

+1

Zac

Re: [Pyobjc-dev] re: My second roadblock

[Just v. R. <ju...@le...>]

Zachery Bir wrote:

> > Even tho this was my error, to make sure other people don't fall
> > into the same silliness, you might want to change the tutorial to
> > say: "Work through Defining the Classes of Currency Converter,
> > Connecting ConverterController to the Interface, and stop at 
> > Implementing the Classes of Currency Converter".
> 
> +1

Done, thanks.

Just

Re: [Pyobjc-dev] re: My second roadblock - lessons learned

[Jack J. <Jac...@cw...>]

First of all: thanks to Gary and Zachary for following the tutorial to 
the letter and reporting bugs like these!

Second, I think there's an important lesson in here: as the tutorial is 
going to be the very first thing newcomers will try it must be 
absolutely bug-free. In other words, before the next release we should 
do a code freeze and at that point someone should follow the tutorial 
(and follow it to the letter) to see that it still makes sense.

I think it might be a good idea to create a document 
"distribution-build.txt" or something like that in which we record the 
steps that need to be taken when creating a new distribution. This 
could include stuff like testing the tutorial, but also the 
incantations needed to create the installers, addresses of mailing 
lists and websites where we want to post announcements, etc. I have 
such a document for MacPython distributions (in 
Mac/Distributions/readme.txt), and I find that with every distribution 
I do there's one of the steps that cause the "oh! good that I wrote 
this down, otherwise I would have forgotten" sensation.
--
Jack Jansen, <Jac...@cw...>, http://www.cwi.nl/~jack
If I can't dance I don't want to be part of your revolution -- Emma 
Goldman