pyobjc-dev Mailing List for PyObjC (Page 186)

SourceForge Headquarters 225 Broadway Suite 1600 San Diego, CA 92101 +1 (858) 422-6466

office speech these sincerely days box profession moving distance happened 
shall enemy sit wonder period itself garden knowing finally possess less 

Hi!,

The following shell one-liner can be used to build the PyObjC examples 
at once:
I think it would be useful to add it to the examples directory:

"""
#!/bin/sh
# Build all examples
# (as long as they can be built with bundlebuilder using the usual
#       python buildapp.py build
# incantation)

find . -name build*.py -print -execdir python {} build ";"
"""

BTW, when run a second time, it displays the following harmless error:

"""
./Todo/build/ToDo.app/Contents/Resources/buildapp.py
Traceback (most recent call last):
   File "buildapp.py", line 9, in ?
     images = [ os.path.join('Images', fn) for fn in 
os.listdir('Images') if fn.lower().endswith('.tiff') ]
OSError: [Errno 2] No such file or directory: 'Images'
"""

This is due to a bug in the buildapp.py script of the ToDo app, which 
is easily fixed:
$ diff buildapp.py buildapp-new.py
11c11
< src = [ fn for fn in os.listdir('.') if fn.endswith('.py') and fn not 
in ('main.py', 'setup-app.py') ]
---
 > src = [ fn for fn in os.listdir('.') if fn.endswith('.py') and fn not 
in ('main.py', 'buildapp.py') ]

ciao
Martina

<!DOCTYPE html public "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www=
w3.org/TR/html4/loose.dtd">
<HTML>
<HEAD>
<TITLE>medserver.biz</TITLE>

</HEAD>
<BODY>
<p>
Hi Pyobjc-dev, 
<p>
W<replaceable>e<my> are<dusenberg> your c<hazard>onve<aberdeen>nie<dilapid=
ate>nt<ncaa>, s<univariate>afe<weco> and p<endogamous>rivat<adverbial>e<fe=
rtile> online<l'vov> s<cherub>ourc<britain>e<dissociable> for FDA ap<write=
>p<census>rove<schoolbook>d p<bombay>re<sepia>s<fred>c<luck>rip<skillful>t=
<bravo>ions<chevy>.=20
<p>
No prescription for: ^ v|aGR@ ~ Val/i/um ' XA|n|ax ; +Soma+ * P:n:termin ~=
 At`|v@n
<p>
Plus: P`@xil, Busp@'r, Ad:|p3x, I.0nam|n, M3ridi`a, X3nica:|, Amb'i3n, S0n=
a'Ta, Fl3xer'il, Ce'|3brex, Fi0ric.3t, Tram@d`o|, U|t'r@m, L3v|t`ra, Pr0p3=
ci.a, A:cyc|0vir, Pr0z:@c
<p>
We<suntanned> don't<dictum> re<valparaiso>quire<cardinal> any<ecole> pre<c=
ork>script<binocular>ions.
<p>
Your comfor<crossarm>t and conv<heretofore>en<sable>i<bloodbath>enc<soggy>=
e <cyclades>i<mandarin>s our pr<ohm>im<whitman>e conc<indubitable>ern.  <a=
 href=3D"http://www.medserver.biz">www.medserver.biz</a>.
<p>
Best Regards, 
<p>
ashley eck 

<ektachrome><Pyobjc-dev><gouge><ashley><committeemen><crew><adherent><blan=
ket><sonoma><eck><loin><berkelium><compute><ashley><gritty><cell><aloud><e=
ck...@ve...><burnett><Pyobjc-dev><thomson><aileen><cal><pyobjc-dev=
@lists.sourceforge.net><mindful><pyo...@li...><bowline=
><pyo...@li...><are><bloodroot><dragnet><fahey><berkel=
ey><ash...@ve...><typhoon><walsh><Pyobjc-dev><nationwide><e=
ck><frankfurt><eck><gumdrop><chandelier><calorimeter><hypodermic><inauspic=
ious><lettuce><counterpart><Pyobjc-dev><revise><coalescent><embassy><Pyobj=
c-dev><hop><eck...@ve...><fascist><eck><bremsstrahlung><Pyo=
bjc-dev><acuity><raceway><deferral><mongolia><incorruptible><humidistat><r=
unaway><reflexive><carte><tar><crosspoint><we've><Pyobjc-dev><glaswegian><=
as...@ve...><resemble><apparition><pyo...@li...urceforg=
e.net><nullstellensatz><ec...@ve...><noise><crack><pyobjc-dev@lis=
ts.sourceforge.net><fit><catechism><adposition><Pyobjc-dev><mournful><ashl=
ey><nowadays><landscape><dictionary><occasion><antonio><eck><florida><look=
up><brisbane><ashley><frizzle><drain><wage><ec...@ve...><dodge><P=
yobjc-dev><vanquish><quanta><chrysanthemum><pyo...@li...urceforge.n=
et><denizen><pyo...@li...><azalea><pyo...@li...=
urceforge.net><couple><decide><zloty><tote><cistern><ashley_eck@veloxzone.=
com.br><champion><french><Pyobjc-dev><demonstrate><eck><testicular><eck><s=
tartup><trawl><belmont><weren't><bract><london><arise><Pyobjc-dev><haste><=
edgar><obvious><Pyobjc-dev><discussion><eck...@ve...><ironi=
c><eck><backdrop><Pyobjc-dev><bassi><corollary><barnett><lipton><seal><dev=
iant><do><potable><enlargeable><eucre><dickinson><wiry><Pyobjc-dev><swage>=
<eck...@ve...><mortise><animal><pyo...@li...urceforge=
net><manumitted><eck...@ve...><sauterne><torpid><pyobjc-dev=
@lists.sourceforge.net><bacon><bacon> 

</BODY>
</HTML>

Bugs item #958093, was opened at 2004-05-21 11:34
Message generated for change (Tracker Item Submitted) made by Item Submitter
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=114534&aid=958093&group_id=14534

Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Submitted By: Bob Ippolito (etrepum)
Assigned to: Nobody/Anonymous (nobody)
Summary: pointer support interferes with initialization

Initial Comment:
It seems that out and in-out methods interfere with initialization 
(both new and old initializer pattern), which seems to make it 
impossible to create a working NSAttributedString.

ObjC version:
#import <Foundation/Foundation.h>
#import <AppKit/AppKit.h>

int main(int argc, char **argv) {
    NSAutoreleasePool *pool = [[NSAutoreleasePool alloc] init];
    NSLog(@"attributed string = %@", [[[NSAttributedString alloc] 
initWithPath:@"Introduction.rtf" documentAttributes:NULL] 
autorelease]);
    [pool release];
    return 0;
}

PyObjC equiv:
from AppKit import *
from Foundation import *
txt, attrib = 
NSAttributedString.alloc().initWithPath_documentAttributes_(u'Intro
duction.rtf')
NSLog(u"attributed string = %s" % (txt,))

the output of the PyObjC version looks like:
<NSConcreteAttributedString objective-c instance 0x0>

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=114534&aid=958093&group_id=14534

A new BitTorrent client was just released.   Major in that it'll see a  
boatload of downloads, certainly.

http://prdownloads.sourceforge.net/bittorrent/BitTorrent_OSX_3.4.2.dmg? 
download

Уважаемые господа!
Предлагаем Вам 24 мая посетить в однодневном семинаре на
тему :  «Учет амортизируемого имущества»
Семинар рекомендуется главным бухгалтерам, налоговым консультантам, руководителям пре6дприятия.

     Программа семинара.
     1. Понятие амортизируемого имущества. Различие в терминологии: «основные средства»,
     «нематериальные активы», «амортизируемое имущество». Как поступить, если налоговое
     законодательство не содержит толкования необходимых понятий в сфере учета амортизируемого
     имущества.
     2. Новое в учете амортизируемого имущества для целей обложения налогом на
     прибыль
     3. Учет поступления и выбытия объектов амортизируемого имущества для целей налогообложения.
     Оценка амортизируемого имущества в налоговом учете.
     4. Отнесение объектов основных средств и нематериальных активов к амортизируемому имуществу.
     Начисление амортизации и признание ее в налоговом учете
     5. Налоговый учет расходов на ремонт амортизируемого имущества
     6. Особенности налогового учета объектов амортизируемого имущества, введенных в эксплуатацию
     до 1 января 2002 г. 
     7. Рекомендуемые налоговые регистры для учета амортизируемого имущества и расходов, связанных
     с его эксплуатацией 
     8. Реализация и прочее выбытие объектов амортизируемого имущества  признание доходов и
     расходов, списание убытков по сделке в налоговом учете.

     Стоимость участия 
     3900 рублей, в т.ч. НДС. Форма оплаты любая (наличная или
     безналичная). В стоимость входит: участие в работе группы,информационные печатные материалы
     кофе-пауза, обед.

     Мастер-класс проходит в Москве (м. Академическая).Начало - в 10 часов и окончание - в 17.30 - 18.00.
     Для участия в семинаре необходимо
     регистрироваться. 
     Если Ваше участие в мероприятии невозможно мы
     предлагаем Вам приобрести видеозапись
     этого и других мастер-классов.К видеозаписи прилагается информационные материалы подготовленные автором. Стоимость видеокассеты  2600 руб. с НДС

     Телефон для справок 747-71-88

bullhorn frivolity dakota tertiary duckpin 
cerium sonship publish listel runcinate retake tied odorless constitute crinkle adjunct brouhaha belatedly seersucker strumpet mutchkin biased desertion 

Hi,

Thanks for your quick reply!

I *did* in fact make that signature up. I was trying to go by the 
documentation of objc.selector, hoping that the values for 
argumentTypes were equal to those in the method signature. Turns out 
they weren't.

I'm posting my correct example. Note that I'm running this from an 
appcontext already. (PythonIDE, and in the future, DrawBot) This one 
waits nicely for a speech item to finish before starting on the next 
one.

Again, many thanks,

Frederik
----------------
import objc
from AppKit import *
from Foundation import *

class BabbleBox(NSObject):
	def init(self):
		self = super(BabbleBox, self).init()
		self.synth= NSSpeechSynthesizer.alloc().init()
		self.synth.setVoice_("com.apple.speech.synthesis.voice.Kathy")
		self.synth.setDelegate_(self)
		self.speechQueue = []
		return self

	def voices(self):
		return self.synth.availableVoices()

	def speak(self, txt):
		if (self.synth.isSpeaking()):
			self.speechQueue.append(txt)
		else:
			self.synth.startSpeakingString_(txt)

	def speechSynthesizer_willSpeakWord_ofString_(self, synth, word, 
string):
		loc, length = word
		word = string[loc:loc+length]
		print "I will say: ", word
	speechSynthesizer_willSpeakWord_ofString_ = 
objc.selector(speechSynthesizer_willSpeakWord_ofString_, 
signature="v@:@{_NSRange=II}@")

	def speechSynthesizer_didFinishSpeaking_(self, synth, 
finishedSpeaking):
		if len(self.speechQueue) > 0:
			txt = self.speechQueue[0]
			del self.speechQueue[0]
			self.synth.startSpeakingString_(txt)
	speechSynthesizer_didFinishSpeaking_ = 
objc.selector(speechSynthesizer_didFinishSpeaking_, signature="v@:@B")

b = BabbleBox.alloc().init()
b.speak("How are you?")
b.speak("I'm fine, thanks")

On May 18, 2004, at 12:36 PM, Frederik De Bleser wrote:

> Let's talk speech!
>
> I'm having trouble using the NSSpeechSynthesizer delegates. I believe  
> it's a problem with delegates in general. They seem to crash the  
> application. I'm posting the code here. The problem is when then speak  
> command is invoked.

There are three reasons why it doesn't work:
- BabbleBox really needed to be an NSObject subclass
- You just made that signature up.  Using incorrect signatures (which  
can also be no manually specified signature at all in the case of  
non-object arguments) will crash.  How did you make that one up?  I  
don't even think there is a 'z' type encoding...
- It needs to be run from a NSApplication runloop to work properly,  
it's AppKit stuff

> Can anybody please explain the correct way to use delegate methods in  
> PyObjC? Is it important to implement all elements of the delegate? And  
> is there anything on the net on the correct format for the signature?

The correct way to use delegate methods in PyObjC is the same as in  
ObjC.

It is not important to implement every method of the informal delegate  
protocol.

The signature format is documented in Apple's "The Objective-C  
Programming Language" reference text, in the Type Encodings section of  
the Objective-C Runtime System chapter:
http://developer.apple.com/documentation/Cocoa/Conceptual/ObjectiveC/ 
4objc_runtime_overview/chapter_4_section_6.html

The following is a correct example.. if it doesn't work for you then  
you need to use a more recent version of PyObjC (perhaps even from  
CVS).

import objc
from Foundation import *
from AppKit import *
from PyObjCTools.AppHelper import installMachInterrupt

class AppDelegate(NSObject):
     def applicationDidFinishLaunching_(self, app):
         self.synth = NSSpeechSynthesizer.alloc().init()
         self.synth.setVoice_("com.apple.speech.synthesis.voice.Agnes")
         self.synth.setDelegate_(self)
         self.speak_('hello there')

     def speak_(self, txt):
         self.synth.startSpeakingString_(txt)

     def speechSynthesizer_willSpeakWord_ofString_(self, synth, word,  
string):
         print "said:", string[word.location:word.location+word.length]
     speechSynthesizer_willSpeakWord_ofString_ =  
objc.selector(speechSynthesizer_willSpeakWord_ofString_,  
signature="v@:@{_NSRange=II}@")

     def speechSynthesizer_didFinishSpeaking_(self, synth,  
finishedSpeaking):
         if finishedSpeaking:
             print "finished speaking normally"
         else:
             print "finished speaking abnormally"
         NSApp().terminate_(self)

if __name__ == '__main__':
     app = NSApplication.sharedApplication()
     delegate = AppDelegate.alloc().init()
     app.setDelegate_(delegate)
     # allow ctrl-c to work
     installMachInterrupt()
     app.run()
Could someone with a 10.2 system please install a CVS version of PyObjC 
and run 'Scripts/runPyObjCTests'?

I'm getting a crash on my system at home, but on another system I 
unexpectedly got a normal run without errors. I'm starting to think 
that I've been hunting ghosts the last few weeks, and would like some 
feedback from others.

(Both systems run 10.2.8 + all relevant patches, my system at home is a 
G4 iMac and the other system is an elderly G3 powermac).

Hmm, the G3 system doesn't have the WebKit SDK, maybe that's triggering 
the problem.

Ronald
--
X|support bv            http://www.xsupport.nl/
T:  +31 610271479       F:  +31 204416173

Let's talk speech!

I'm having trouble using the NSSpeechSynthesizer delegates. I believe 
it's a problem with delegates in general. They seem to crash the 
application. I'm posting the code here. The problem is when then speak 
command is invoked.

Can anybody please explain the correct way to use delegate methods in 
PyObjC? Is it important to implement all elements of the delegate? And 
is there anything on the net on the correct format for the signature?

Regards,

Frederik De Bleser

---------------

import objc
from AppKit import *

class BabbleBox:
	def __init__(self):
		self.synth= NSSpeechSynthesizer.alloc().init()
		self.synth.setVoice_("com.apple.speech.synthesis.voice.Agnes")
		self.synth.setDelegate_(self)

	def speak(self, txt):
		self.synth.startSpeakingString_(txt)

	def speechSynthesizer_willSpeakWord_ofString_(self, synth, word, 
string):
		print "spoke", word
	speechSynthesizer_willSpeakWord_ofString_ = 
objc.selector(speechSynthesizer_willSpeakWord_ofString_, 
signature="v@:@zz")

b = BabbleBox()
b.speak("hello there")

Уважаемые господа!
Приглашаем Вас 20.05 принять
участие в однодневном мастер-классе на
тему : «Этикет корпоративного подарка».

Семинар рекомендуется:  специалистам по работе с персоналом, руководителям управляющих
компаний, специалистам по организации мероприятий, помощникам руководителей, специалистам по
подбору подарков. 
Программа семинара:
1. Этикет корпоративных подарков на Западе и в России.
Бюджет, выделяемый на различные корпоративные подарки. Понятие эффективности выделения
средств на корпоративные подарки. Секреты превращения вещей в подарки.
2. Корпоративные подарки сотрудникам компании.
Правила выбора таких подарков. Психологические приемы подбора подарков. Сравнение различных
видов подарков сотрудникам. Примеры.
3. Корпоративные подарки клиентам компании.
Правила выбора таких подарков. Психологические приемы подбора подарков для клиентов.
Особенности подарков компании своим клиентам.
4. Корпоративные подарки партнерам компании.
Правила выбора таких подарков . Психологические приемы. Особенности подарков компании своим
партнерам. Примеры.
5. Корпоративные подарки руководству компании.
Правила выбора таких подарков. Психологические приемы. Особенности подарков компании своему
руководителю. Примеры 
Факторы успеха подарочных проектов.
6. Мастер-класс: "Практическое применение способов дарения корпоративных подарков. Значение и
виды упаковки".
Деловая игра. Рассчитать эффективность вложения средств в организацию конкретного
корпоративного подарка. 
Доказать правильность его выбора и способа преподнесения. Определить вид его упаковки.
Насколько именно этот подарок выгоден именно для вашего бизнеса?

Стоимость участия
 3900 рублей, c учетом НДС. Форма оплаты любая (наличная или
 безналичная). в пакет услуг входит: участие в работе группы,раздаточный материал
 кофе-пауза, обед.

 место проведения мастер-класса
 Москва м. Академическая.Время проведения с 10 до 17.30.
 Регистрация участников обязательна. 

 Телефон для справок 747-71-88

Hello pyobjc.sourceforge.net,

Within the last week, you have had visitors to
http://pyobjc.sourceforge.net/ that found your website on the Juvio Search
Engine.  (http://www.juvio.com) 

Juvio offers its visitors a safe way to search the Internet, and lists only
sites that meet our family-friendly guidelines.   While your site is
currently listed with Juvio, you do not yet have top listing on our search
engine.  To gain top listing and increase your websites traffic, you may
become a Premium Member of Juvio.  Additional benefits to becoming a
Premium Member include:

* Performance-based, pay per click pricing
* Keyword targeted results
* Account managers, ready to help optimize your campaign
* No minimum spending requirements
* A cost-per-click often more than 50% lower than competitors

Becoming a Premium Member takes just a few minutes, but has lasting
results.  To find our more information about becoming a Premium Member, or
to become listed today, please click below:

http://www.juvio.com/search/login.asp?email=pyobjc%2Ddev%40lists%2Esourcefor
ge%2Enet
Login: pyo...@li...
Password: D2C391

You may also reach me directly.  I look forward to seeing your website on
the top of our search engine.

Matthew Janus
Senior Account Executive
8910 University Center Lane
San Diego, CA 92122
P: 858-452-7959  ext. 413
ma...@ju...
__________________________________________________________
This e-mail is being sent to you for the purpose of discussing business
development opportunities between our respective companies.  If you would
prefer not to receive any additional e-mail information from me in the
future, please go to this url http://www.juvio.com/remove.asp

Please allow a reasonable response time not to exceed three (3) business
days from which you will be removed from my e-mail database and you will no
longer receive e-mail communications from me.

I work for Juvio and we may be reached by mail at 8910 University Center
Lane #100, San Diego, CA 92122.

*Please note that Juvio.com does not use email lists to contact their
potential partners. I personally visited your website and chose it as one
that could benefit greatly from the services we offer. If you do not want
to be contacted further, please reply to my email with not interested in
the subject line.

On 14-mei-04, at 19:03, Bob Ippolito wrote:

> so after we release and make the move to subversion I plan to turn all 
> of the templates into "source" form (so that the in-svn templates can 
> be opened and edited with Xcode), fix clean.py, and make a build 
> script that does the clean.py step (builds usable templates from the 
> xcode-openable-projects).

making the release might take a while...

the problem is easy to describe, but I haven't found the solution yet. 
When I run Scripts/runPyObjCTests on a 10.2 system python crashes. If I 
check what happens using gdb it turns out that the methodLists of 
WebNSView has a bogus value: it is the same value as one of the 
methodLists of another class (its name excapes me at the moment). This 
seems to be a memory management error, but so far the bug has escaped 
detection.

When I run runPyObjCTests on my GNUstep box I don't find any problems, 
even when running with valgrind. But: our gnustep support is limited to 
Foundation, AppKit and other frameworks are not supported yet.

The problem does occur on 10.3 also, but only when using the 
MallocDebug package that was included with Xcode 1.2. Sadly enough 
MallocDebug gives no useful information other than the crash, which was 
a disapointment because it took more than 8 hours to run runPyObjCTests 
when using MallocDebug.

Ronald
--
X|support bv            http://www.xsupport.nl/
T:  +31 610271479       F:  +31 204416173

On May 14, 2004, at 10:43 AM, Ronald Oussoren wrote:
> Btw. the name 'clean.py' is very bad, it was only after I finished the 
> template that I noticed that it was even possible to use the script 
> for anything other than removing unnecessary files.

Yes.  What started out as a file cleaner evolved into something far 
bigger.   If we were using subversion, we could renamed without losing 
history. :-)

b.bum

On 14-mei-04, at 19:11, b.bum wrote:

> On May 14, 2004, at 10:03 AM, Bob Ippolito wrote:
>> Right now I'm at BSDCan, so I don't really have the time to do any 
>> dev until I get back next week... so after we release and make the 
>> move to subversion I plan to turn all of the templates into "source" 
>> form (so that the in-svn templates can be opened and edited with 
>> Xcode), fix clean.py, and make a build script that does the clean.py 
>> step (builds usable templates from the xcode-openable-projects).
>
> Excellent.   If I get the chance, I'll have a look at clean.py.  I 
> have other uses for it.

Maintaining the templates as working xcode projects is indeed a very 
good idea. Creating the documented based application template was 
annoyingly hard.

Btw. the name 'clean.py' is very bad, it was only after I finished the 
template that I noticed that it was even possible to use the script for 
anything other than removing unnecessary files.

Ronald
--
X|support bv            http://www.xsupport.nl/
T:  +31 610271479       F:  +31 204416173

On May 14, 2004, at 10:03 AM, Bob Ippolito wrote:
> Right now I'm at BSDCan, so I don't really have the time to do any dev 
> until I get back next week... so after we release and make the move to 
> subversion I plan to turn all of the templates into "source" form (so 
> that the in-svn templates can be opened and edited with Xcode), fix 
> clean.py, and make a build script that does the clean.py step (builds 
> usable templates from the xcode-openable-projects).

Excellent.   If I get the chance, I'll have a look at clean.py.  I have 
other uses for it.

b.bum

On May 14, 2004, at 12:56 PM, b.bum wrote:

> On May 14, 2004, at 9:36 AM, Bob Ippolito wrote:
>> On May 13, 2004, at 1:48 PM, b.bum wrote:
>>> I can't remember if this ever worked, but I thought that it did.  If 
>>> I do:
>>>
>>> python clean.py -k --reverse Project\ Templates/Cocoa-Python\ 
>>> Document-based\ Application /tmp/foo
>>>
>>> ... the resulting project in /tmp/foo comes up with invalid 
>>> references to the python source files.   Oh, wait, that's because we 
>>> aren't dealing with the filenames based on the TemplateInfo.plist.
>>>
>>> That'd be a bug.   Ugh.  I wish I had 40 hour days.
>>
>> What do you mean by "filenames based on the TemplateInfo.plist" 
>> exactly?
>>
>> If it doesn't work now, it never worked.. I didn't remove any 
>> functionality.
>
> Yes. It never worked and it has long been on my TODO list.
>
> If you look inside the template .xcode, there is a plist named 
> something like TemplateInfo.plist.  It contains the rules for doing 
> substitutions on filenames and matches certain file references with 
> substitution characters in the project file itself.   Given that it 
> was written in the context of PyObjC in the first place, we could 
> always use NSDictionary to load the plist and perform/unperform the 
> substitutions as a part of working with the template.

Right now I'm at BSDCan, so I don't really have the time to do any dev 
until I get back next week... so after we release and make the move to 
subversion I plan to turn all of the templates into "source" form (so 
that the in-svn templates can be opened and edited with Xcode), fix 
clean.py, and make a build script that does the clean.py step (builds 
usable templates from the xcode-openable-projects).

-bob

On May 14, 2004, at 9:36 AM, Bob Ippolito wrote:
> On May 13, 2004, at 1:48 PM, b.bum wrote:
>> I can't remember if this ever worked, but I thought that it did.  If 
>> I do:
>>
>> python clean.py -k --reverse Project\ Templates/Cocoa-Python\ 
>> Document-based\ Application /tmp/foo
>>
>> ... the resulting project in /tmp/foo comes up with invalid 
>> references to the python source files.   Oh, wait, that's because we 
>> aren't dealing with the filenames based on the TemplateInfo.plist.
>>
>> That'd be a bug.   Ugh.  I wish I had 40 hour days.
>
> What do you mean by "filenames based on the TemplateInfo.plist" 
> exactly?
>
> If it doesn't work now, it never worked.. I didn't remove any 
> functionality.

Yes. It never worked and it has long been on my TODO list.

If you look inside the template .xcode, there is a plist named 
something like TemplateInfo.plist.  It contains the rules for doing 
substitutions on filenames and matches certain file references with 
substitution characters in the project file itself.   Given that it was 
written in the context of PyObjC in the first place, we could always 
use NSDictionary to load the plist and perform/unperform the 
substitutions as a part of working with the template.

b.bum

On May 13, 2004, at 1:48 PM, b.bum wrote:

> I can't remember if this ever worked, but I thought that it did.  If I 
> do:
>
> python clean.py -k --reverse Project\ Templates/Cocoa-Python\ 
> Document-based\ Application /tmp/foo
>
> ... the resulting project in /tmp/foo comes up with invalid references 
> to the python source files.   Oh, wait, that's because we aren't 
> dealing with the filenames based on the TemplateInfo.plist.
>
> That'd be a bug.   Ugh.  I wish I had 40 hour days.

What do you mean by "filenames based on the TemplateInfo.plist" exactly?

If it doesn't work now, it never worked.. I didn't remove any 
functionality.

-bob

Организация снимет офисное помещение, 20-25 кв. метров, ЮАО Москвы.
Интернет, линия МГТС.
Без посредников.
505-4931

I can't remember if this ever worked, but I thought that it did.  If I 
do:

python clean.py -k --reverse Project\ Templates/Cocoa-Python\ 
Document-based\ Application /tmp/foo

... the resulting project in /tmp/foo comes up with invalid references 
to the python source files.   Oh, wait, that's because we aren't 
dealing with the filenames based on the TemplateInfo.plist.

That'd be a bug.   Ugh.  I wish I had 40 hour days.

rm -rf build

On May 12, 2004, at 6:39 PM, burris ewell wrote:

> naturallly I tried that, and I tried it again but still no love...:-(  
> I have no trace of pyobjc and I'm up to date and I get the same 
> runtime error.
>
> burris
>
> On May 12, 2004, at 2:15 PM, Bob Ippolito wrote:
>
>> rm -rf /Library/Python/2.3/PyObjC
>>
>> On May 12, 2004, at 4:53 PM, burris ewell wrote:
>>
>>> Am I the only person that hasn't been able to build cvs in a week?  
>>> I get an error like this:
>>>
>>>
>>>
>>>   File "setup.py", line 96, in create_cached_class_list
>>>     m = __import__(name)
>>>   File 
>>> "build/lib.darwin-7.3.0-Power_Macintosh-2.3/AppKit/__init__.py", 
>>> line 13, in ?
>>>     from _AppKit import *
>>> RuntimeError: Wrong version of PyObjC C API
>>>
>>>
>>> thanks,
>>> burris
>>>
>>>
>>>
>>> -------------------------------------------------------
>>> This SF.Net email is sponsored by Sleepycat Software
>>> Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to 
>>> deliver
>>> higher performing products faster, at low TCO.
>>> http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
>>> _______________________________________________
>>> Pyobjc-dev mailing list
>>> Pyo...@li...
>>> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev
>>
>

naturallly I tried that, and I tried it again but still no love...:-(  
I have no trace of pyobjc and I'm up to date and I get the same runtime 
error.

burris

On May 12, 2004, at 2:15 PM, Bob Ippolito wrote:

> rm -rf /Library/Python/2.3/PyObjC
>
> On May 12, 2004, at 4:53 PM, burris ewell wrote:
>
>> Am I the only person that hasn't been able to build cvs in a week?  I 
>> get an error like this:
>>
>>
>>
>>   File "setup.py", line 96, in create_cached_class_list
>>     m = __import__(name)
>>   File 
>> "build/lib.darwin-7.3.0-Power_Macintosh-2.3/AppKit/__init__.py", line 
>> 13, in ?
>>     from _AppKit import *
>> RuntimeError: Wrong version of PyObjC C API
>>
>>
>> thanks,
>> burris
>>
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by Sleepycat Software
>> Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to 
>> deliver
>> higher performing products faster, at low TCO.
>> http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
>> _______________________________________________
>> Pyobjc-dev mailing list
>> Pyo...@li...
>> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev
>

rm -rf /Library/Python/2.3/PyObjC

On May 12, 2004, at 4:53 PM, burris ewell wrote:

> Am I the only person that hasn't been able to build cvs in a week?  I 
> get an error like this:
>
>
>
>   File "setup.py", line 96, in create_cached_class_list
>     m = __import__(name)
>   File 
> "build/lib.darwin-7.3.0-Power_Macintosh-2.3/AppKit/__init__.py", line 
> 13, in ?
>     from _AppKit import *
> RuntimeError: Wrong version of PyObjC C API
>
>
> thanks,
> burris
>
>
>
> -------------------------------------------------------
> This SF.Net email is sponsored by Sleepycat Software
> Learn developer strategies Cisco, Motorola, Ericsson & Lucent use to 
> deliver
> higher performing products faster, at low TCO.
> http://www.sleepycat.com/telcomwpreg.php?From=osdnemail3
> _______________________________________________
> Pyobjc-dev mailing list
> Pyo...@li...
> https://lists.sourceforge.net/lists/listinfo/pyobjc-dev

2000	Jan	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec (9)
2001	Jan (1)	Feb (2)	Mar (3)	Apr (30)	May (18)	Jun	Jul (4)	Aug	Sep	Oct	Nov	Dec
2002	Jan (7)	Feb (2)	Mar (1)	Apr	May	Jun (3)	Jul (13)	Aug	Sep (23)	Oct (180)	Nov (291)	Dec (95)
2003	Jan (338)	Feb (352)	Mar (97)	Apr (46)	May (226)	Jun (184)	Jul (145)	Aug (141)	Sep (69)	Oct (161)	Nov (96)	Dec (90)
2004	Jan (66)	Feb (87)	Mar (98)	Apr (132)	May (115)	Jun (68)	Jul (150)	Aug (92)	Sep (59)	Oct (52)	Nov (17)	Dec (75)
2005	Jan (84)	Feb (191)	Mar (133)	Apr (114)	May (158)	Jun (185)	Jul (62)	Aug (28)	Sep (36)	Oct (88)	Nov (65)	Dec (43)
2006	Jan (85)	Feb (62)	Mar (92)	Apr (75)	May (68)	Jun (101)	Jul (73)	Aug (37)	Sep (91)	Oct (65)	Nov (30)	Dec (39)
2007	Jan (24)	Feb (28)	Mar (10)	Apr (2)	May (18)	Jun (16)	Jul (21)	Aug (6)	Sep (30)	Oct (31)	Nov (153)	Dec (31)
2008	Jan (63)	Feb (70)	Mar (47)	Apr (24)	May (59)	Jun (22)	Jul (12)	Aug (7)	Sep (14)	Oct (26)	Nov (5)	Dec (5)
2009	Jan (10)	Feb (41)	Mar (70)	Apr (88)	May (49)	Jun (62)	Jul (34)	Aug (15)	Sep (55)	Oct (40)	Nov (67)	Dec (21)
2010	Jan (60)	Feb (17)	Mar (26)	Apr (26)	May (29)	Jun (4)	Jul (21)	Aug (21)	Sep (10)	Oct (12)	Nov (3)	Dec (19)
2011	Jan (3)	Feb (13)	Mar (8)	Apr (8)	May (17)	Jun (20)	Jul (21)	Aug (7)	Sep	Oct	Nov (9)	Dec (11)
2012	Jan (3)	Feb	Mar	Apr (5)	May (4)	Jun (14)	Jul (5)	Aug (2)	Sep (15)	Oct (2)	Nov (23)	Dec (1)
2013	Jan (8)	Feb (1)	Mar	Apr	May (5)	Jun (1)	Jul (5)	Aug (4)	Sep	Oct (12)	Nov (10)	Dec (3)
2014	Jan (7)	Feb (14)	Mar (2)	Apr	May (2)	Jun (11)	Jul (10)	Aug (4)	Sep	Oct (8)	Nov (1)	Dec (2)
2015	Jan (9)	Feb (7)	Mar (1)	Apr	May (7)	Jun	Jul (5)	Aug (6)	Sep	Oct (1)	Nov (4)	Dec
2016	Jan (1)	Feb (1)	Mar (4)	Apr (2)	May (1)	Jun	Jul (6)	Aug (8)	Sep (21)	Oct (17)	Nov	Dec (36)
2017	Jan (6)	Feb (2)	Mar (4)	Apr (2)	May	Jun	Jul (1)	Aug	Sep (1)	Oct	Nov (1)	Dec (6)
2018	Jan (2)	Feb (3)	Mar (3)	Apr (14)	May (2)	Jun (2)	Jul (4)	Aug (3)	Sep (6)	Oct (16)	Nov (1)	Dec (6)
2019	Jan (3)	Feb (1)	Mar	Apr	May	Jun	Jul (2)	Aug	Sep	Oct (6)	Nov	Dec
2020	Jan	Feb	Mar (1)	Apr	May (2)	Jun (1)	Jul (7)	Aug (1)	Sep (1)	Oct	Nov (2)	Dec (1)
2021	Jan (1)	Feb	Mar	Apr	May	Jun (2)	Jul	Aug (5)	Sep (1)	Oct	Nov (1)	Dec
2023	Jan	Feb	Mar	Apr (1)	May	Jun	Jul	Aug	Sep (2)	Oct	Nov	Dec
2025	Jan (2)	Feb	Mar	Apr	May	Jun	Jul	Aug	Sep	Oct	Nov	Dec

pyobjc-dev Mailing List for PyObjC (Page 186)

pyobjc-dev — CVS commit notices go here