E-Basic and E-Run in E-Prime 2.0
silvia.panzarasa
I used E-Run in order to edit my e-basic experiment and to compile the
code. Now I see that it is not possible to open an E-basic script with
E-run but it is only possible to run the exercise. Is that feature no
more available in E-Prime 2?How I can do the same things as the past
in the new version?
Thank you
Matt Lenhart
The E-Run 2.0 interface will offer the ability to run experiments from
a dialog graphical user interface. Editing the contents of the script
generated by E-Studio is no longer possible due to enhancements to the
E-Prime system as well as protecting experiment replication and
industrial partner intellectual property. Most scenarios where
directly editing the E-Basic script will be able to be accomplished in
E-Prime 2.0 Professional using Package files and the facilities via
the StartupInfo manager, which permits loading properties into the
Context from external files which can override a number of experiment
settings such as display resolution, subject number, etc. Support for
a Package file editor will be available in a forthcoming build. Formal
announcements will be made on the PST User Forum (http://
support.pstnet.com/forum).
- Matt Lenhart
PST Technical Consultant
http://www.pstnet.com/
On Jan 17, 5:20 am, "silvia.panzarasa" <silvia.panzar...@gmail.com>
wrote:
David McFarlane
Welcome to the club! Jodene and I already complained about this in
the PST Forum back in October, see the thread at
support.pstnet.com/forum/Topic696-12-1.aspx. We both found it very,
very helpful to be able to edit the full E-Basic script directly, it
is the number one feature that initially sold me on E-Prime, and
losing that ability also breaks things like E-Kick, so we are very
sad to see it go. So you're not alone.
As you can see by Matt's response, this change is deliberate and will
stick. FWIW, Package files and the StartupInfo manager may indeed
partially make up for the loss of E-Kick. However, note that Package
files work differently in EP2 Professional vs. non-Pro. As I
understand it, the forthcoming Package file editor will *only* work
in Pro. .ebs2 files designed in Pro and that use Package files
designed in Pro *will* run under non-Pro. However, the Package files
designed with Pro *cannot* be used for Package calls in non-Pro
experiements. By contrast, Package files designed by "industrial
partners" *can* be used in non-Pro experiements. So clearly not all
Package files are created equal (and personally, I have never before
found a use for making our own Package files, perhaps that will
change with EP2). Clear enough?
---
David McFarlane, Systems Designer
Dept. Psychology, Michigan State University
mcfa...@msu.edu www.msu.edu/~mcfarla9
Voice: (517) 353-0799 Fax: (517) 353-1652
silvia.panzarasa
I'm sad to realize that i have understood correctly the situation and
I hope I will be able,
with the new version, to implement all the experiments we are thinking
about.
I don't understand clearly what you mean for "not all Package files
are created equal".
May be I have to explore better the new E-Prime in order to
understand, or (better!!) perhaps
my English is not so good... so sorry and thank you again for
yourhelp!
Silvia
David McFarlane
>I don't understand clearly what you mean for "not all Package files
>are created equal".
Sorry, that was a clumsy expression. I only meant that Package files
that are made by ordinary users like you & me do not work as well as
Package files that are made by PST "industrial partners". But almost
nobody makes their own Package files, so this is probably not important.
---
David McFarlane, Systems Designer
Dept. Psychology, Michigan State University
mcfa...@msu.edu www.msu.edu/~mcfarla9
Matt Lenhart
Just to clear up the incompatibility of package files, what is
essentially happening here is the ability to create and use your own
package files is an E-Prime 2.0 Professional feature. However, we have
many users who work with our industrial partners' (e.g. Tobii, EGI,
etc) products. Integration between E-Prime and their product is
handled via package calls. Thus, since the use of package calls from
industrial partners is not a new feature (i.e. it was available in the
previous version of E-Prime), this will be available in both E-Prime
2.0 "Standard" and E-Prime 2.0 Professional. However, user-created
package files are only supported by E-Prime 2.0 Professional.
- Matt
silvia.panzarasa
On 18 Gen, 20:06, David McFarlane <mcfar...@msu.edu> wrote:
> Silvia,
>
> >I don't understand clearly what you mean for "not all Package files
> >are created equal".
>
> Sorry, that was a clumsy expression. I only meant that Package files
> that are made by ordinary users like you & me do not work as well as
> Package files that are made by PST "industrial partners". But almost
> nobody makes their own Package files, so this is probably not important.
>
> ---
> David McFarlane, Systems Designer
> Dept. Psychology, Michigan State University