Forum: Poser - OFFICIAL

Subject: poserpython.com is open!

bushi opened this issue on Jun 08, 2002 ยท 6 posts

bushi posted Sat, 08 June 2002 at 10:48 PM

Attached Link: http://poserpython.com

It doesn't have the bushi3d stuff on it but everything from home.velocitus.net/bushi is there. I'll be bring the bushi3d items online over the next week. If you hit the new site and find links that don't match up, please let me know. I've been through the whole thing twice but there's always the possibility that I missed something. Oh, and the domain name just went active this morning so it's still being propagated to the nameservers. It might not be available in all areas yet.

kjlintner posted Sat, 08 June 2002 at 11:15 PM

Thank you for posting about your new site. I am glad to finally lay my hands on a copy of MorphSqueeze. I've heard may good things about it :)

Cris_Palomino posted Sun, 09 June 2002 at 4:34 AM

Hi, Bushi....wonderful! patiently waits for word about Mac Thanks, Cris

Poppi posted Sun, 09 June 2002 at 4:51 AM

Thanks ever so much. i loved your 3d stuff. i had so many uses for that egg....i know. sounds silly, and all, but in bryce that egg could work wonders of magic in a number of ways.

stewer posted Sun, 09 June 2002 at 7:53 AM

First, congrats for the site. As for the Mac problem: In general, the Python APIs for Mac and Windows are identical, the major problem there is are path seperators. Make sure you never hard-code for : or as path separator but use os.path.split(). IIRC there's also a slight inconcistency in the TextureMapFileName() function: When called on a material with no texture, the Mac version returns a directory and the Windows version returns null. This also applies for the corresponding transparency/bump/reflection map functions.

bushi posted Sun, 09 June 2002 at 1:05 PM

Thanks for the comments! I'll announce it when the bushi3d stuff is back online. stewer - Yes, I understand where your coming from there. The problem though isn't with distributing the scripts as .py files. I can fix that using os.path methods as you suggested. The problem I'm having is with the embedded paths that Python puts into the .pyc files. I've tried, as have several others on the Python forum, to figure out a way around them with no success. The only way that works so far is to compile the .py files on both platforms. If you have a way that works, I'd be very pleased to hear it. Please drop me a note at: bushi@velocitus.net if you'd like to discuss this further.