Updated product, DrPoser, this weekend due to opportunity to test and run and compile software using latest Poser Pro 2012.

Version submitted to Marketplace, in review, is for P8 and not for P9 (which I've just posted into the queue) so still runs fine, but some modifications due to defects in PP2012 (namely SM's broken Tkinter & broken thread-handling in P9) now incorporated into full package, making P8 version now P9 compatible.

Any chance of letting me upload the new version for the P8 version before it goes live?

So P8 version can be rereviewed and released nearer P9 version?

TIA

A grateful vendor.

I have directed the MarketPlace staff to this thread so that they can further assist you.

Thanks

TinaK

Hi. I just saw a new product uploaded this morning and put a HOLD on the first one until I could contact you and be sure what you wanted to do with them and release dates. Please send me an email to jennblake@renderosity.com and I will work with you to get the items into the marketplace for you. I need to know if you want to combine both of these products? What makes each seperate instance different from the other, or why you want to sell them as two products. Also when you want them released. Send that email off to me please and we will get this all setup for you. :-)

Thank you.

I will upload the latest P8 version soonest.

The P9 version can be put online as and when the P8 goes in the queue.

Q. Why two?

A. Simple. No choice.

My software can only be released as two separate versions because of design flaws in Poser9/PoserPro2012 and the way in which it handles standard Python.

Most programmers won't come up against them because they don't write software of sufficient rigour or sophistication to encounter the defects in the two implementations in Poser. After only a weekend's trial, I know the GUI implementation and the way Threading works, as well as the memory usage, are significantly dissimilar between Poser versions but I can do nothing about it. I only write Python. It's not my job to fix Poser itself!

These bugs in P9/PP2012 mean that the P9 version of my software can ONLY work on the PC version.

Whereas the P8/PP2010 version works fine, as testers tell me, on both PC and MAC versions.

Since compliled Python ONLY runs on the system version that compiled it, so a P8 version won't run on P9 and vice versa, so there will always be a separate P8 edition and a P9-PC edition.

To avoid offering P9-MAC users two copies of software, neither of which they can run... two clearly labelled versions are more logical and more legally defensible.

Since nobody wants two copies either, makes more sense to separate the software into two versions.

Also allows me to make a back-compatible P7 version (already tested and working albeit Threadless so less pretty!) if the screaming crowds demand it. Nobody has so far so not a priority at the mo.

IF SM had written P9-MAC edition to use a better version of Python OR Python was back-compatible re. compiled versions of code, this problem wouldn't arise. We always seem to be suffering at the hands of unseen, incompetent others in the computer industry, such is the developer's lot. C'est la vie!

Thank you for your help re. release of DrPoser.

DH

Ok. I have put that first product back into review so that you can upload the updated file. :-) Will watch for that and get these through the process for you. Release both items simultaneously then?

I actually had a newer version of the P8 code (1.1.56 rather than the 1.1.55 that's online) to post but since it is now online I cannot update it!

Neve mind.

I wanted to update the previously posted P8 version to the latest 1.1.56.

It was the waiting P9 version (1.1.56) that is the updated version.

Too late now.

Never mind.

Quote - IF SM had written P9-MAC edition to use a better version of Python OR Python was back-compatible re. compiled versions of code, this problem wouldn't arise. We always seem to be suffering at the hands of unseen, incompetent others in the computer industry, such is the developer's lot. C'est la vie!

TkInter support on Macs has been broken for a long while, and isn't SM's fault, it doesn't work in the vanilla Python distribution. If you want a cross platform GUI for a Poser script, you'll need to switch to wxPython (for P8 and above)

Tkinter is better (if implemented properly in the host program) and compiles to a single file.

Thank you.

Quote - Tkinter is better (if implemented properly in the host program) and compiles to a single file.

I'd agree about the "properly implemented", which it never has been in Poser. SM did the sensible thing and did a proper job on reworking the GUI internals and exposing wxWindows (which is what was used internally even in previous versions).

The "single file" bit is a complete red herring as tkInter depends on both tcl and tk both of which have supporting libraries of scripts (in tcl) and other resource files beyond the binary library DLL/SO files.

The need to effectively support a second complete scripting language just to provide tkInter to Python (and similarly for PERL/Tk) is bordering on the bizarre.

AFAIK almost everything about the way SM has implemented Python is broken. Each and every flavour of GUI has 'issues'... it's a case of pick your problem!

Without doing one program in each GUI and picking which fails less, which I couldn't be bothered doing, I picked Tkinter in 2009 and stuck with it. It works well enough for me so I am not too bothered it's a dead end tech.

I picked Tkinter because I began with P7 and it 'kinda' worked there while wxP was a distant unimplemented upstart.

They all have issues.

If it's not broken Threads, it's a half-*ssed or broken something else that works on PC doesn't on MAC or vice versa.

Not much to choose between them to be honest IMHO.

If something ever manages to work on a multitude of platforms, you can be sure it will be crippled by commercial interests, be bought up and destroyed, be unusable without a degree in Swahili and Urdu or become obsolete pretty soon!