PackageCall support
 
 
 
PST User Forum
Home       Members    Calendar    Who's On
Welcome Guest ( Login | Register )
        



PackageCall support Expand / Collapse
Author
Message
Posted 11/9/2007 10:01:26 AM
Forum Guru

Forum GuruForum GuruForum GuruForum GuruForum GuruForum GuruForum GuruForum Guru

Group: Forum Members
Last Login: 2 days ago @ 5:23:48 PM
Posts: 137, Visits: 380
Could somebody please straighten out the situation with PackageCalls in E-Prime 2.0 standard vs. Professional? In a separate thread ("e-run script editing"), PST staff (Brandon) wrote, "Most scenarios where directly editing the E-Basic script will be able to be accomplished in E-Prime 2.0 Professional using Package files." Does this mean that Standard cannot use PackageCalls at all? Or does it mean that Standard can *use* PackageCalls, but only Professional will include a Package file editor? The second scenario is the only one that makes sense, but we need to know so that we know what versions we need to buy and install. In particular, if we build an E-Prime program in Professional using Package files that we made with the Package file editor, will we still be able to run the resulting E-Run file using E-Run Standard, or will that run only with E-Run Professional? For that matter, is there any difference at all between E-Run standard and Professional, or are all the differences just in E-Studio standard vs. Professional?

Also, Brandon said, "Support for a Package file editor will be available in a forthcoming release." Does that mean that at the moment we have no way to make Package files for 2.0? As I recall, in 1.x there was no Package editor since these were just done with any old text editor, but that's impossible now that everything is bin.base64 encoded xml. This probably affects almost no one, but I still look forward to the forthcoming Package file editor.

Thanks for your help.
Post #835
Posted 11/9/2007 12:08:24 PM
Forum MVP

Forum MVPForum MVPForum MVPForum MVPForum MVPForum MVPForum MVPForum MVP

Group: Administrators
Last Login: 2 days ago @ 8:36:44 AM
Posts: 480, Visits: 1,064
Thanks for this discussion topic.

E-Prime 2.0 will permit for package call and package objects created by Industrial Partners.  Examples of package files that are or will be capable of being used in E-Prime 2.0 are (but not limited to) E-Prime Extensions for Tobii, E-Prime Extensions for NetStation, and E-Prime Extensions for fMRI.

E-Prime 2.0 Professional will offer the ability to author and use end user package call and package files.  Thus, if your desire is to author and share the library of calls with your lab or other labs, they will require E-Prime 2.0 Professional.  A release of the PackageFile editor is scheduled in Jan 2008.  A couple of screen grabs are attached.

-Brandon

  Post Attachments 
PackageEditor1.gif (11 views, 31.13 KB)
PackageEditor2.gif (7 views, 30.23 KB)

Post #837
Posted 11/9/2007 3:24:07 PM
Forum Guru

Forum GuruForum GuruForum GuruForum GuruForum GuruForum GuruForum GuruForum Guru

Group: Forum Members
Last Login: 2 days ago @ 5:23:48 PM
Posts: 137, Visits: 380
Brandon, thank you very much for your response. I'm still just a little confused. By "E-Prime 2.0" do you include Standard? Or are we to understand that what linguists call the "unmarked" use of the term "E-Prime 2.0" always refers to the "Standard" version, and only the "marked" case with "Professional" appended means the Professional version? Or does the unmarked case sometimes refer to both Standard and Professional, and sometimes just Standard, and we are supposed to disambiguate this from context?

Perhaps it's just me, but the whole new PST terminology just confuses me. Is there any way that we can adopt a consistent terminology to disambiguate our discussions for simpletons like me, e.g., always use "Standard" when referring to Standard, "Professional" when referring to Professional, and "Standard and Professional" when referring to both Standard and Professional?

Thanks for your thoughts.
Post #838
Posted 11/9/2007 3:33:39 PM
Forum Guru

Forum GuruForum GuruForum GuruForum GuruForum GuruForum GuruForum GuruForum Guru

Group: Forum Members
Last Login: 2 days ago @ 5:23:48 PM
Posts: 137, Visits: 380
Oh, and more importantly... If E-Prime 2.0 (Standard?) will permit for packages created by Industrial Partners, and Pro will offer the ability to author and use end user package call and package files, then does that mean that Standard will *not* permit for packages created by end users (built using Pro) since it only permits for packages created by Industrial Partners?

(You should know by now that, just like the electronic systems that I so expertly manage, if there is a way to misconstrue and find ambiguity, then I will find it. So I ask you to pick your expressions carefully just like you would for any other logic-bound system .)

Thank you again.
Post #839
Posted 11/9/2007 5:25:46 PM
Forum Guru

Forum GuruForum GuruForum GuruForum GuruForum GuruForum GuruForum GuruForum Guru

Group: Forum Members
Last Login: 2 days ago @ 5:23:48 PM
Posts: 137, Visits: 380
There was supposed to be a grin at the end of that parenthetical comment, but this system does not like expressions enclosed in angle brackets, so here's the grin using the icons from the Forum posting interface:
Post #840
Posted 11/14/2007 9:14:51 AM
Forum Guru

Forum GuruForum GuruForum GuruForum GuruForum GuruForum GuruForum GuruForum Guru

Group: Forum Members
Last Login: 2 days ago @ 5:23:48 PM
Posts: 137, Visits: 380
Jodene did a simple test: Made an experiment with E-Prime 2.0 Pro, and tried to run it under E-Prime 2.0 non-Pro. So the answer to my question seems to be that, not only will non-Pro *not* permit for packages created by end users (built using Pro), non-Pro will not run *anything* made with Pro. This presents a real problem.
Post #862
Posted 11/14/2007 9:27:31 AM
Forum Guru

Forum GuruForum GuruForum GuruForum GuruForum GuruForum GuruForum Guru