Smalltalk › Instantiations

make executable

_‹ Previous Topic Next Topic _›

Classic

List

Threaded

13 messages Options

ipstools.project

make executable

Trying to make executable for the first time.

My application is without visual parts, just pure Smalltalk class.

For that case documentations says, that in the Windows to show at startup field we need to select <None>. Moreover, the class we want to open must contain a class method named runtimeStartUp.

The most interesting moment is that documentation gives a reference to the non-existent documentation VA Smalltalk Base User's Guide and gives no example of code for many Smalltalk application examples given in documentation itself.

To start up my application I execute the following command: IpsTools new open. So what method runtimeStartUp should contain in my example? Tried some evident code sequences, but still get error message (after wrong packaging).

Sergei.

--
You received this message because you are subscribed to the Google Groups "VA Smalltalk" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To post to this group, send email to [hidden email].
Visit this group at https://groups.google.com/group/va-smalltalk.
For more options, visit https://groups.google.com/d/optout.

rjuli...@gmail.com

Re: make executable

Hi there.

You want to create that #runtimeStartUp method on the class side, of the class that has the same name as your application.

So...if you have an App named IpsToolsApp, then you will automatically have a class with that name.

Go into that class, turn to the class side, and create this...

runtimeStartUp

^IpsTools new open

Now, for every application that gets included in your package, each associated application class

will be sent the message #runtimeStartUp...so you can actually implement that method in other

of your apps too.

For simplictity, though, I tend to create a top level app, which will then define

the prerequisites for your finished product.

It is this top level application that I select to package.

And I implement #runtimeStartUp in only that one class.

This way, the initial start up is very simple.

I hope that is helpful....

Good luck!

Julian

On Monday, February 18, 2019 at 11:52:20 AM UTC-5, [hidden email] wrote:

Trying to make executable for the first time.

My application is without visual parts, just pure Smalltalk class.
For that case documentations says, that in the Windows to show at startup field we need to select <None>. Moreover, the class we want to open must contain a class method named runtimeStartUp.

The most interesting moment is that documentation gives a reference to the non-existent documentation VA Smalltalk Base User's Guide and gives no example of code for many Smalltalk application examples given in documentation itself.

To start up my application I execute the following command: IpsTools new open. So what method runtimeStartUp should contain in my example? Tried some evident code sequences, but still get error message (after wrong packaging).

Sergei.

ipstools.project

Re: make executable

Hi Julian,

I very much appreciate your response because I was afraid no one would answer my question.

I tried to fulfill your recommendations, both with original application and with a new test one, but still get an error:
Procedure entry point EsGetUPtr not found in dynamic link library D:\Working\Smalltalk Projects\Test\exe\Test.exe (translated by me).

I attach a source and exe files of TestApp. Can you take a look at this example ant say where my mistake is?

Best regards,
Sergei.

четверг, 21 февраля 2019 г., 5:17:00 UTC+3 пользователь [hidden email] написал:

Hi there.

You want to create that #runtimeStartUp method on the class side, of the class that has the same name as your application.
So...if you have an App named IpsToolsApp, then you will automatically have a class with that name.
Go into that class, turn to the class side, and create this...

runtimeStartUp

^IpsTools new open

Now, for every application that gets included in your package, each associated application class
will be sent the message #runtimeStartUp...so you can actually implement that method in other
of your apps too.

For simplictity, though, I tend to create a top level app, which will then define
the prerequisites for your finished product.
It is this top level application that I select to package.
And I implement #runtimeStartUp in only that one class.
This way, the initial start up is very simple.

I hope that is helpful....
Good luck!

Julian

On Monday, February 18, 2019 at 11:52:20 AM UTC-5, [hidden email] wrote:
Trying to make executable for the first time.

My application is without visual parts, just pure Smalltalk class.
For that case documentations says, that in the Windows to show at startup field we need to select <None>. Moreover, the class we want to open must contain a class method named runtimeStartUp.

The most interesting moment is that documentation gives a reference to the non-existent documentation VA Smalltalk Base User's Guide and gives no example of code for many Smalltalk application examples given in documentation itself.

To start up my application I execute the following command: IpsTools new open. So what method runtimeStartUp should contain in my example? Tried some evident code sequences, but still get error message (after wrong packaging).

Sergei.

Solveig

Re: make executable

Sergei,

If you are a supported customer, feel free to pass the zip files on to customer support at [hidden email]. We will track down what is going on.

We are updating the online documentation, Smalltalk User's Guide ( the 9.1 version is at https://www.instantiations.com/docs/91/wwhelp/wwhimpl/js/html/wwhelp.htm#href=sg/stug.html) to extend an existing example to demonstrate how to package it and how to run the packaged image. It will be available with VA Smalltalk Version 9.2.

Regards,

Solveig

On Thursday, February 21, 2019 at 10:58:37 AM UTC-5, [hidden email] wrote:

Hi Julian,

I very much appreciate your response because I was afraid no one would answer my question.

I tried to fulfill your recommendations, both with original application and with a new test one, but still get an error:
Procedure entry point EsGetUPtr not found in dynamic link library D:\Working\Smalltalk Projects\Test\exe\Test.exe (translated by me).

I attach a source and exe files of TestApp. Can you take a look at this example ant say where my mistake is?

Best regards,
Sergei.

P.S. The forum blocks from attaching files. AN alternative link is: <a href="http://www.univerge.ru/files/Test.zip" target="_blank" rel="nofollow" onmousedown="this.href='http://www.google.com/url?q\x3dhttp%3A%2F%2Fwww.univerge.ru%2Ffiles%2FTest.zip\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFcnt1EM0Hea7AHkSByrHE1Q29fiA';return true;" onclick="this.href='http://www.google.com/url?q\x3dhttp%3A%2F%2Fwww.univerge.ru%2Ffiles%2FTest.zip\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFcnt1EM0Hea7AHkSByrHE1Q29fiA';return true;">www.univerge.ru/files/Test.zip

четверг, 21 февраля 2019 г., 5:17:00 UTC+3 пользователь [hidden email] написал:
Hi there.

You want to create that #runtimeStartUp method on the class side, of the class that has the same name as your application.
So...if you have an App named IpsToolsApp, then you will automatically have a class with that name.
Go into that class, turn to the class side, and create this...

runtimeStartUp

^IpsTools new open

Now, for every application that gets included in your package, each associated application class
will be sent the message #runtimeStartUp...so you can actually implement that method in other
of your apps too.

For simplictity, though, I tend to create a top level app, which will then define
the prerequisites for your finished product.
It is this top level application that I select to package.
And I implement #runtimeStartUp in only that one class.
This way, the initial start up is very simple.

I hope that is helpful....
Good luck!

Julian

On Monday, February 18, 2019 at 11:52:20 AM UTC-5, [hidden email] wrote:
Trying to make executable for the first time.

My application is without visual parts, just pure Smalltalk class.
For that case documentations says, that in the Windows to show at startup field we need to select <None>. Moreover, the class we want to open must contain a class method named runtimeStartUp.

The most interesting moment is that documentation gives a reference to the non-existent documentation VA Smalltalk Base User's Guide and gives no example of code for many Smalltalk application examples given in documentation itself.

To start up my application I execute the following command: IpsTools new open. So what method runtimeStartUp should contain in my example? Tried some evident code sequences, but still get error message (after wrong packaging).

Sergei.

ipstools.project

Re: make executable

Hi Solveig,

unfortunately I`m not your customer :)) just standalone beginner in Smalltalk and in programming itself. And I`m happy the documentation on VA Smalltalk constantly gets updated by Instantiations. Thank you.

I have today managed to fix the problem. The code is absolutely correct (thanks to Julian), I simply replaced all dlls in an application folder with a new set of ones. And it worked!. The reason of error is still unknown to me.

By the way, while you are here with us, can you, or someone else, give advice how reliably kill the forked process? It was a discovery for me to learn that terminate method doesn`t not necessary stop the active process at all !!!

Here is a test piece of code which utilizing TCP/IP socket calls that I`m struggling with:

cmdTest

    | result mainProcess control |
    
    [Transcript clear] when: ExError do: [:sig | sig exitWith: nil].
    
    self semaphore: AbtSemaphore new.
    control := AbtSemaphore new.
    
    mainProcess := [
        1 to: 300 do: [ :e |
        self sm sendRecv: #[16r1F].
        (self glAt: 'IpsTools') append: '!'].
        result := AppMessage new id: MSG_OK.
        self semaphore signal] fork.
        
    [control wait. mainProcess terminate. self semaphore signal] fork.
    self semaphore wait.

    result isNil
        ifTrue: [^AppMessage new id: MSG_ERROR; text: 'connection timed out2', LineDelimiter]
        ifFalse: [^result]
    

After executing 'mainProcess terminate',

mainProcess continues to run !

Best regards,

Sergei.

среда, 27 февраля 2019 г., 20:57:20 UTC+3 пользователь Solveig написал:

Sergei,

If you are a supported customer, feel free to pass the zip files on to customer support at <a href="javascript:" target="_blank" gdf-obfuscated-mailto="3MSObNU3BAAJ" rel="nofollow" onmousedown="this.href='javascript:';return true;" onclick="this.href='javascript:';return true;">vast-s...@instantiations.com. We will track down what is going on.

We are updating the online documentation, Smalltalk User's Guide ( the 9.1 version is at <a href="https://www.instantiations.com/docs/91/wwhelp/wwhimpl/js/html/wwhelp.htm#href=sg/stug.html" target="_blank" rel="nofollow" onmousedown="this.href='https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.instantiations.com%2Fdocs%2F91%2Fwwhelp%2Fwwhimpl%2Fjs%2Fhtml%2Fwwhelp.htm%23href%3Dsg%2Fstug.html\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHN58wH8xsQtJfcDH29L0xifw7Xfw';return true;" onclick="this.href='https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.instantiations.com%2Fdocs%2F91%2Fwwhelp%2Fwwhimpl%2Fjs%2Fhtml%2Fwwhelp.htm%23href%3Dsg%2Fstug.html\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNHN58wH8xsQtJfcDH29L0xifw7Xfw';return true;">https://www.instantiations.com/docs/91/wwhelp/wwhimpl/js/html/wwhelp.htm#href=sg/stug.html) to extend an existing example to demonstrate how to package it and how to run the packaged image. It will be available with VA Smalltalk Version 9.2.

Regards,
Solveig

On Thursday, February 21, 2019 at 10:58:37 AM UTC-5, <a href="javascript:" target="_blank" gdf-obfuscated-mailto="3MSObNU3BAAJ" rel="nofollow" onmousedown="this.href='javascript:';return true;" onclick="this.href='javascript:';return true;">ipstools...@... wrote:
Hi Julian,

I very much appreciate your response because I was afraid no one would answer my question.

I tried to fulfill your recommendations, both with original application and with a new test one, but still get an error:
Procedure entry point EsGetUPtr not found in dynamic link library D:\Working\Smalltalk Projects\Test\exe\Test.exe (translated by me).

I attach a source and exe files of TestApp. Can you take a look at this example ant say where my mistake is?

Best regards,
Sergei.

P.S. The forum blocks from attaching files. AN alternative link is: <a href="http://www.univerge.ru/files/Test.zip" rel="nofollow" target="_blank" onmousedown="this.href='http://www.google.com/url?q\x3dhttp%3A%2F%2Fwww.univerge.ru%2Ffiles%2FTest.zip\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFcnt1EM0Hea7AHkSByrHE1Q29fiA';return true;" onclick="this.href='http://www.google.com/url?q\x3dhttp%3A%2F%2Fwww.univerge.ru%2Ffiles%2FTest.zip\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFcnt1EM0Hea7AHkSByrHE1Q29fiA';return true;">www.univerge.ru/files/Test.zip

четверг, 21 февраля 2019 г., 5:17:00 UTC+3 пользователь [hidden email] написал:
Hi there.

You want to create that #runtimeStartUp method on the class side, of the class that has the same name as your application.
So...if you have an App named IpsToolsApp, then you will automatically have a class with that name.
Go into that class, turn to the class side, and create this...

runtimeStartUp

^IpsTools new open

Now, for every application that gets included in your package, each associated application class
will be sent the message #runtimeStartUp...so you can actually implement that method in other
of your apps too.

For simplictity, though, I tend to create a top level app, which will then define
the prerequisites for your finished product.
It is this top level application that I select to package.
And I implement #runtimeStartUp in only that one class.
This way, the initial start up is very simple.

I hope that is helpful....
Good luck!

Julian

On Monday, February 18, 2019 at 11:52:20 AM UTC-5, [hidden email] wrote:
Trying to make executable for the first time.

My application is without visual parts, just pure Smalltalk class.
For that case documentations says, that in the Windows to show at startup field we need to select <None>. Moreover, the class we want to open must contain a class method named runtimeStartUp.

The most interesting moment is that documentation gives a reference to the non-existent documentation VA Smalltalk Base User's Guide and gives no example of code for many Smalltalk application examples given in documentation itself.

To start up my application I execute the following command: IpsTools new open. So what method runtimeStartUp should contain in my example? Tried some evident code sequences, but still get error message (after wrong packaging).

Sergei.

rjuli...@gmail.com

Re: make executable

In reply to this post by ipstools.project

Hello, Sergei.

I think the answer is actually quite simple.

There is a certain set of required runtime files for any packaged image.

And at least in the folder you sent, not all of the runtime files are there.

When I try to run your EXE, I get the message that the procedure can not be found in DLL

ESVM40.DLL.....this is telling you that the DLL named esvm40.dll must also be included in your

runtime folder. You can copy this file from the VASmalltalk installation folder.

I know there will be other files you need as well, but that list will depend on your application

(for my application, there are something like 80 required files.

I saw your message that you are not currently a customer...I am not sure what the rules are

on releasing runtime images, if you are not a customer. Certainly, there are some files you will

have no access to, and so at best, your runtime will include pop-ups indicating the Trial status.

Which of course is only fair...given you get to play with the development environment for free.

But if you are just trying it all out, you may just need to copy files from the installation folder

(also look in the nls folder...and I think there are a couple files from the bitmaps folder).

So...I think yo umay well have done everything right....you just need the correct list of supporting

files for your OS.

I hope that is helpful...

Regards,

Julian Ford

On Thursday, February 21, 2019 at 10:58:37 AM UTC-5, [hidden email] wrote:

Hi Julian,

I very much appreciate your response because I was afraid no one would answer my question.

I tried to fulfill your recommendations, both with original application and with a new test one, but still get an error:
Procedure entry point EsGetUPtr not found in dynamic link library D:\Working\Smalltalk Projects\Test\exe\Test.exe (translated by me).

I attach a source and exe files of TestApp. Can you take a look at this example ant say where my mistake is?

Best regards,
Sergei.

P.S. The forum blocks from attaching files. AN alternative link is:

четверг, 21 февраля 2019 г., 5:17:00 UTC+3 пользователь [hidden email] написал:
Hi there.

You want to create that #runtimeStartUp method on the class side, of the class that has the same name as your application.
So...if you have an App named IpsToolsApp, then you will automatically have a class with that name.
Go into that class, turn to the class side, and create this...

runtimeStartUp

^IpsTools new open

Now, for every application that gets included in your package, each associated application class
will be sent the message #runtimeStartUp...so you can actually implement that method in other
of your apps too.

For simplictity, though, I tend to create a top level app, which will then define
the prerequisites for your finished product.
It is this top level application that I select to package.
And I implement #runtimeStartUp in only that one class.
This way, the initial start up is very simple.

I hope that is helpful....
Good luck!

Julian

On Monday, February 18, 2019 at 11:52:20 AM UTC-5, [hidden email] wrote:
Trying to make executable for the first time.

My application is without visual parts, just pure Smalltalk class.
For that case documentations says, that in the Windows to show at startup field we need to select <None>. Moreover, the class we want to open must contain a class method named runtimeStartUp.

The most interesting moment is that documentation gives a reference to the non-existent documentation VA Smalltalk Base User's Guide and gives no example of code for many Smalltalk application examples given in documentation itself.

To start up my application I execute the following command: IpsTools new open. So what method runtimeStartUp should contain in my example? Tried some evident code sequences, but still get error message (after wrong packaging).

Sergei.

ipstools.project

Re: make executable

Hi Julian,

great post from you again.

Have some small comments:

четверг, 28 февраля 2019 г., 6:47:30 UTC+3 пользователь [hidden email] написал:

Hello, Sergei.

I think the answer is actually quite simple.

There is a certain set of required runtime files for any packaged image.
And at least in the folder you sent, not all of the runtime files are there.

When I try to run your EXE, I get the message that the procedure can not be found in DLL
ESVM40.DLL.....this is telling you that the DLL named esvm40.dll must also be included in your
runtime folder. You can copy this file from the VASmalltalk installation folder.

I get a different message. I have a localized version of Windows (not english) and on my platform I get message, saying that "Procedure entry point EsGetUPtr not found in dynamic link library D:\Working\Smalltalk Projects\Test\exe\Test.exe." (translated by me).

I also got messages like there was no DLL xxxxxxx.dll when the folder with the test application contained no dlls at all. So I copied the ones displayed in the error messages including esvm40.dll.

I know there will be other files you need as well, but that list will depend on your application
(for my application, there are something like 80 required files.

I think I`ll never reach such a quantity in my apps :)

I saw your message that you are not currently a customer...I am not sure what the rules are
on releasing runtime images, if you are not a customer. Certainly, there are some files you will
have no access to, and so at best, your runtime will include pop-ups indicating the Trial status.
Which of course is only fair...given you get to play with the development environment for free.

At current I develop for my pleasure :)) Like Smalltalk...And trial pop-up doesn`t bother me at all.

But if you are just trying it all out, you may just need to copy files from the installation folder
(also look in the nls folder...and I think there are a couple files from the bitmaps folder).

So...I think yo umay well have done everything right....you just need the correct list of supporting
files for your OS.

I hope that is helpful...

Thanks for your help.

Regards,
Julian Ford

On Thursday, February 21, 2019 at 10:58:37 AM UTC-5, [hidden email] wrote:
Hi Julian,

I very much appreciate your response because I was afraid no one would answer my question.

I tried to fulfill your recommendations, both with original application and with a new test one, but still get an error:
Procedure entry point EsGetUPtr not found in dynamic link library D:\Working\Smalltalk Projects\Test\exe\Test.exe (translated by me).

I attach a source and exe files of TestApp. Can you take a look at this example ant say where my mistake is?

Best regards,
Sergei.

P.S. The forum blocks from attaching files. AN alternative link is:

четверг, 21 февраля 2019 г., 5:17:00 UTC+3 пользователь [hidden email] написал:
Hi there.

You want to create that #runtimeStartUp method on the class side, of the class that has the same name as your application.
So...if you have an App named IpsToolsApp, then you will automatically have a class with that name.
Go into that class, turn to the class side, and create this...

runtimeStartUp

^IpsTools new open

Now, for every application that gets included in your package, each associated application class
will be sent the message #runtimeStartUp...so you can actually implement that method in other
of your apps too.

For simplictity, though, I tend to create a top level app, which will then define
the prerequisites for your finished product.
It is this top level application that I select to package.
And I implement #runtimeStartUp in only that one class.
This way, the initial start up is very simple.

I hope that is helpful....
Good luck!

Julian

On Monday, February 18, 2019 at 11:52:20 AM UTC-5, [hidden email] wrote:
Trying to make executable for the first time.

My application is without visual parts, just pure Smalltalk class.
For that case documentations says, that in the Windows to show at startup field we need to select <None>. Moreover, the class we want to open must contain a class method named runtimeStartUp.

The most interesting moment is that documentation gives a reference to the non-existent documentation VA Smalltalk Base User's Guide and gives no example of code for many Smalltalk application examples given in documentation itself.

To start up my application I execute the following command: IpsTools new open. So what method runtimeStartUp should contain in my example? Tried some evident code sequences, but still get error message (after wrong packaging).

Sergei.

Seth Berman

Re: make executable

Greetings Sergei,

I just wanted to provide an additional route to using VA Smalltalk that you might not be aware of.

We're happy to provide a trial license so folks can evaluate what they get before purchasing the product.

It offers a 45-day window from which the user can evaluate the usage of our product for commercial purposes.

What you might think about doing is applying for one of our open-source licenses.

While you can not use this license for commercial purposes, it gives you a way to use our product for open-source projects.

In return, we ask that you commit to an open-source project. Preferably for VA Smalltalk (http://vastgoodies.com/) but we're open

to others.

I believe this will ultimately work better for everyone because we're all participating in community building.

See more here: https://www.instantiations.com/company/open-source.html

- Seth

On Thursday, February 28, 2019 at 1:30:47 PM UTC-5, [hidden email] wrote:

Hi Julian,
great post from you again.

Have some small comments:

четверг, 28 февраля 2019 г., 6:47:30 UTC+3 пользователь [hidden email] написал:
Hello, Sergei.

I think the answer is actually quite simple.

There is a certain set of required runtime files for any packaged image.
And at least in the folder you sent, not all of the runtime files are there.

When I try to run your EXE, I get the message that the procedure can not be found in DLL
ESVM40.DLL.....this is telling you that the DLL named esvm40.dll must also be included in your
runtime folder. You can copy this file from the VASmalltalk installation folder.

I get a different message. I have a localized version of Windows (not english) and on my platform I get message, saying that "Procedure entry point EsGetUPtr not found in dynamic link library D:\Working\Smalltalk Projects\Test\exe\Test.exe." (translated by me).
I also got messages like there was no DLL xxxxxxx.dll when the folder with the test application contained no dlls at all. So I copied the ones displayed in the error messages including esvm40.dll.

I know there will be other files you need as well, but that list will depend on your application
(for my application, there are something like 80 required files.
I think I`ll never reach such a quantity in my apps :)

I saw your message that you are not currently a customer...I am not sure what the rules are
on releasing runtime images, if you are not a customer. Certainly, there are some files you will
have no access to, and so at best, your runtime will include pop-ups indicating the Trial status.
Which of course is only fair...given you get to play with the development environment for free.
At current I develop for my pleasure :)) Like Smalltalk...And trial pop-up doesn`t bother me at all.

But if you are just trying it all out, you may just need to copy files from the installation folder
(also look in the nls folder...and I think there are a couple files from the bitmaps folder).

So...I think yo umay well have done everything right....you just need the correct list of supporting
files for your OS.

I hope that is helpful...
Thanks for your help.

Regards,
Julian Ford

On Thursday, February 21, 2019 at 10:58:37 AM UTC-5, [hidden email] wrote:
Hi Julian,

I very much appreciate your response because I was afraid no one would answer my question.

I tried to fulfill your recommendations, both with original application and with a new test one, but still get an error:
Procedure entry point EsGetUPtr not found in dynamic link library D:\Working\Smalltalk Projects\Test\exe\Test.exe (translated by me).

I attach a source and exe files of TestApp. Can you take a look at this example ant say where my mistake is?

Best regards,
Sergei.

P.S. The forum blocks from attaching files. AN alternative link is:

четверг, 21 февраля 2019 г., 5:17:00 UTC+3 пользователь [hidden email] написал:
Hi there.

You want to create that #runtimeStartUp method on the class side, of the class that has the same name as your application.
So...if you have an App named IpsToolsApp, then you will automatically have a class with that name.
Go into that class, turn to the class side, and create this...

runtimeStartUp

^IpsTools new open

Now, for every application that gets included in your package, each associated application class
will be sent the message #runtimeStartUp...so you can actually implement that method in other
of your apps too.

For simplictity, though, I tend to create a top level app, which will then define
the prerequisites for your finished product.
It is this top level application that I select to package.
And I implement #runtimeStartUp in only that one class.
This way, the initial start up is very simple.

I hope that is helpful....
Good luck!

Julian

On Monday, February 18, 2019 at 11:52:20 AM UTC-5, [hidden email] wrote:
Trying to make executable for the first time.

My application is without visual parts, just pure Smalltalk class.
For that case documentations says, that in the Windows to show at startup field we need to select <None>. Moreover, the class we want to open must contain a class method named runtimeStartUp.

The most interesting moment is that documentation gives a reference to the non-existent documentation VA Smalltalk Base User's Guide and gives no example of code for many Smalltalk application examples given in documentation itself.

To start up my application I execute the following command: IpsTools new open. So what method runtimeStartUp should contain in my example? Tried some evident code sequences, but still get error message (after wrong packaging).

Sergei.

rjuli...@gmail.com

Re: make executable

In reply to this post by ipstools.project

OK....different error message...but the first part if the message is identical (I didn't put the name of the entry point

in my message, because it was the same...only the name of the DLL was different).

Now, I am not sure why the message you see would say the procedure could not be found in your EXE.....it will never be

in an EXE...it is a procedure in a DLL.

When I copy your EXE and ICX files into my own runtime directory (I then use my own INI file, renamed to TEST.INI, to

make sure it is right for my own paths), the program starts up.

But I do get a runtime error message saying UndefinedObject does not understand new.

Your runtimeStartUp method says Test new open.....so that suggests the Test class was not included.

And sure enough, when I look in the classes.es file (which describes what happened to all of the classes),

the Test class is marked as "excluded".

This will happen if a class is unreferenced, or if the Application containing that class has not been marked

as a prerequisite of the top level Application (the one you packaged).

Now, I realize you have only 1 Application, and you are referencing Test in your runtimeStartUp method...

I only mention it, in case it sparks any other thoughts.

I am not able to do much more, as I no longer have access to a 9.0 image...I have upgraded to the latest.

You might try making a simple visual part, instead of the Test class....something like TestView.

This will also give you some exposure to the GUI builder.

Then change your runtimeStartUp to open that, instead of your current Test class.

From what I can see, though, you have the right idea with your runtimeStartUp, which was what I offered to help

with originally.

I still think there is something missing with the support files, or your INI file has something incorrect in it

(sorry I cannot help with that one....your paths would definitely be different than mine).

Beyond that, I'm afraid I do not know what else to say....

If I think of anything else, though, I'll pass it along.

I hope you are able to get it working...

Regards,

Julian

On Thursday, February 28, 2019 at 1:30:47 PM UTC-5, [hidden email] wrote:

Hi Julian,
great post from you again.

Have some small comments:

четверг, 28 февраля 2019 г., 6:47:30 UTC+3 пользователь [hidden email] написал:
Hello, Sergei.

I think the answer is actually quite simple.

There is a certain set of required runtime files for any packaged image.
And at least in the folder you sent, not all of the runtime files are there.

When I try to run your EXE, I get the message that the procedure can not be found in DLL
ESVM40.DLL.....this is telling you that the DLL named esvm40.dll must also be included in your
runtime folder. You can copy this file from the VASmalltalk installation folder.

I get a different message. I have a localized version of Windows (not english) and on my platform I get message, saying that "Procedure entry point EsGetUPtr not found in dynamic link library D:\Working\Smalltalk Projects\Test\exe\Test.exe." (translated by me).
I also got messages like there was no DLL xxxxxxx.dll when the folder with the test application contained no dlls at all. So I copied the ones displayed in the error messages including esvm40.dll.

I know there will be other files you need as well, but that list will depend on your application
(for my application, there are something like 80 required files.
I think I`ll never reach such a quantity in my apps :)

I saw your message that you are not currently a customer...I am not sure what the rules are
on releasing runtime images, if you are not a customer. Certainly, there are some files you will
have no access to, and so at best, your runtime will include pop-ups indicating the Trial status.
Which of course is only fair...given you get to play with the development environment for free.
At current I develop for my pleasure :)) Like Smalltalk...And trial pop-up doesn`t bother me at all.

But if you are just trying it all out, you may just need to copy files from the installation folder
(also look in the nls folder...and I think there are a couple files from the bitmaps folder).

So...I think yo umay well have done everything right....you just need the correct list of supporting
files for your OS.

I hope that is helpful...
Thanks for your help.

Regards,
Julian Ford

On Thursday, February 21, 2019 at 10:58:37 AM UTC-5, [hidden email] wrote:
Hi Julian,

I very much appreciate your response because I was afraid no one would answer my question.

I tried to fulfill your recommendations, both with original application and with a new test one, but still get an error:
Procedure entry point EsGetUPtr not found in dynamic link library D:\Working\Smalltalk Projects\Test\exe\Test.exe (translated by me).

I attach a source and exe files of TestApp. Can you take a look at this example ant say where my mistake is?

Best regards,
Sergei.

P.S. The forum blocks from attaching files. AN alternative link is:

четверг, 21 февраля 2019 г., 5:17:00 UTC+3 пользователь [hidden email] написал:
Hi there.

You want to create that #runtimeStartUp method on the class side, of the class that has the same name as your application.
So...if you have an App named IpsToolsApp, then you will automatically have a class with that name.
Go into that class, turn to the class side, and create this...

runtimeStartUp

^IpsTools new open

Now, for every application that gets included in your package, each associated application class
will be sent the message #runtimeStartUp...so you can actually implement that method in other
of your apps too.

For simplictity, though, I tend to create a top level app, which will then define
the prerequisites for your finished product.
It is this top level application that I select to package.
And I implement #runtimeStartUp in only that one class.
This way, the initial start up is very simple.

I hope that is helpful....
Good luck!

Julian

On Monday, February 18, 2019 at 11:52:20 AM UTC-5, [hidden email] wrote:
Trying to make executable for the first time.

My application is without visual parts, just pure Smalltalk class.
For that case documentations says, that in the Windows to show at startup field we need to select <None>. Moreover, the class we want to open must contain a class method named runtimeStartUp.

The most interesting moment is that documentation gives a reference to the non-existent documentation VA Smalltalk Base User's Guide and gives no example of code for many Smalltalk application examples given in documentation itself.

To start up my application I execute the following command: IpsTools new open. So what method runtimeStartUp should contain in my example? Tried some evident code sequences, but still get error message (after wrong packaging).

Sergei.

ipstools.project

Re: make executable

In reply to this post by Seth Berman

Greetings Seth,

пятница, 1 марта 2019 г., 0:28:55 UTC+3 пользователь Seth Berman написал:

Greetings Sergei,

I just wanted to provide an additional route to using VA Smalltalk that you might not be aware of.
We're happy to provide a trial license so folks can evaluate what they get before purchasing the product.
It offers a 45-day window from which the user can evaluate the usage of our product for commercial purposes.

You just opened my eyes on 45-days evaluation, I thought it was timeless. This finally caused me read carefully the License Agreement on the product. Maybe you should add a 45-days limitation info in the current pop-up message for those who doesn`t read the LA?

What you might think about doing is applying for one of our open-source licenses.
While you can not use this license for commercial purposes, it gives you a way to use our product for open-source projects.
In return, we ask that you commit to an open-source project. Preferably for VA Smalltalk (<a href="http://vastgoodies.com/" target="_blank" rel="nofollow" onmousedown="this.href='http://www.google.com/url?q\x3dhttp%3A%2F%2Fvastgoodies.com%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFuxnr60lH1eJZumpU0ZdEEA3DfSQ';return true;" onclick="this.href='http://www.google.com/url?q\x3dhttp%3A%2F%2Fvastgoodies.com%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFuxnr60lH1eJZumpU0ZdEEA3DfSQ';return true;">http://vastgoodies.com/) but we're open
to others.

This might be a solution, but I`m very afraid that the piece of code I develop may not fit your requirements, because:

a) it`s a very specific, for some telecom equipment; I`m sure no one from smalltalk community on this board will be interested in this software

b) it`t very simple by look and feel and from end user point of view; but it`s difficult for me as smalltalk beginner;

c) for me as beginner this project may result in a long-term development period, even for beta version

d) it is a hobby, at least at current time

I believe this will ultimately work better for everyone because we're all participating in community building.

See more here: <a href="https://www.google.com/url?q=https%3A%2F%2Fwww.instantiations.com%2Fcompany%2Fopen-source.html&sa=D&sntz=1&usg=AFQjCNFqDiC1C0xusKcWLVoRSeNC6bL_xQ" target="_blank" rel="nofollow" onmousedown="this.href='https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.instantiations.com%2Fcompany%2Fopen-source.html\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFqDiC1C0xusKcWLVoRSeNC6bL_xQ';return true;" onclick="this.href='https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.instantiations.com%2Fcompany%2Fopen-source.html\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFqDiC1C0xusKcWLVoRSeNC6bL_xQ';return true;">https://www.instantiations.com/company/open-source.html

I will read.

- Seth

Sergei

On Thursday, February 28, 2019 at 1:30:47 PM UTC-5, <a href="javascript:" target="_blank" gdf-obfuscated-mailto="Tb1uyZ7yAgAJ" rel="nofollow" onmousedown="this.href='javascript:';return true;" onclick="this.href='javascript:';return true;">ipstools...@... wrote:

Hi Julian,
great post from you again.

Have some small comments:

четверг, 28 февраля 2019 г., 6:47:30 UTC+3 пользователь [hidden email] написал:
Hello, Sergei.

I think the answer is actually quite simple.

There is a certain set of required runtime files for any packaged image.
And at least in the folder you sent, not all of the runtime files are there.

When I try to run your EXE, I get the message that the procedure can not be found in DLL
ESVM40.DLL.....this is telling you that the DLL named esvm40.dll must also be included in your
runtime folder. You can copy this file from the VASmalltalk installation folder.

I get a different message. I have a localized version of Windows (not english) and on my platform I get message, saying that "Procedure entry point EsGetUPtr not found in dynamic link library D:\Working\Smalltalk Projects\Test\exe\Test.exe." (translated by me).
I also got messages like there was no DLL xxxxxxx.dll when the folder with the test application contained no dlls at all. So I copied the ones displayed in the error messages including esvm40.dll.

I know there will be other files you need as well, but that list will depend on your application
(for my application, there are something like 80 required files.
I think I`ll never reach such a quantity in my apps :)

I saw your message that you are not currently a customer...I am not sure what the rules are
on releasing runtime images, if you are not a customer. Certainly, there are some files you will
have no access to, and so at best, your runtime will include pop-ups indicating the Trial status.
Which of course is only fair...given you get to play with the development environment for free.
At current I develop for my pleasure :)) Like Smalltalk...And trial pop-up doesn`t bother me at all.

But if you are just trying it all out, you may just need to copy files from the installation folder
(also look in the nls folder...and I think there are a couple files from the bitmaps folder).

So...I think yo umay well have done everything right....you just need the correct list of supporting
files for your OS.

I hope that is helpful...
Thanks for your help.

Regards,
Julian Ford

On Thursday, February 21, 2019 at 10:58:37 AM UTC-5, [hidden email] wrote:
Hi Julian,

I very much appreciate your response because I was afraid no one would answer my question.

I tried to fulfill your recommendations, both with original application and with a new test one, but still get an error:
Procedure entry point EsGetUPtr not found in dynamic link library D:\Working\Smalltalk Projects\Test\exe\Test.exe (translated by me).

I attach a source and exe files of TestApp. Can you take a look at this example ant say where my mistake is?

Best regards,
Sergei.

P.S. The forum blocks from attaching files. AN alternative link is:

четверг, 21 февраля 2019 г., 5:17:00 UTC+3 пользователь [hidden email] написал:
Hi there.

You want to create that #runtimeStartUp method on the class side, of the class that has the same name as your application.
So...if you have an App named IpsToolsApp, then you will automatically have a class with that name.
Go into that class, turn to the class side, and create this...

runtimeStartUp

^IpsTools new open

Now, for every application that gets included in your package, each associated application class
will be sent the message #runtimeStartUp...so you can actually implement that method in other
of your apps too.

For simplictity, though, I tend to create a top level app, which will then define
the prerequisites for your finished product.
It is this top level application that I select to package.
And I implement #runtimeStartUp in only that one class.
This way, the initial start up is very simple.

I hope that is helpful....
Good luck!

Julian

On Monday, February 18, 2019 at 11:52:20 AM UTC-5, [hidden email] wrote:
Trying to make executable for the first time.

My application is without visual parts, just pure Smalltalk class.
For that case documentations says, that in the Windows to show at startup field we need to select <None>. Moreover, the class we want to open must contain a class method named runtimeStartUp.

The most interesting moment is that documentation gives a reference to the non-existent documentation VA Smalltalk Base User's Guide and gives no example of code for many Smalltalk application examples given in documentation itself.

To start up my application I execute the following command: IpsTools new open. So what method runtimeStartUp should contain in my example? Tried some evident code sequences, but still get error message (after wrong packaging).

Sergei.

ipstools.project

Re: make executable

In reply to this post by rjuli...@gmail.com

пятница, 1 марта 2019 г., 1:09:02 UTC+3 пользователь [hidden email] написал:

OK....different error message...but the first part if the message is identical (I didn't put the name of the entry point
in my message, because it was the same...only the name of the DLL was different).

Now, I am not sure why the message you see would say the procedure could not be found in your EXE.....it will never be
in an EXE...it is a procedure in a DLL.

Bug on a non-English version?

When I copy your EXE and ICX files into my own runtime directory (I then use my own INI file, renamed to TEST.INI, to
make sure it is right for my own paths), the program starts up.
But I do get a runtime error message saying UndefinedObject does not understand new.

Your runtimeStartUp method says Test new open.....so that suggests the Test class was not included.
And sure enough, when I look in the <a href="http://classes.es" target="_blank" rel="nofollow" onmousedown="this.href='http://www.google.com/url?q\x3dhttp%3A%2F%2Fclasses.es\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF1i-vogVGqspSglEGVy4Q1muuK5w';return true;" onclick="this.href='http://www.google.com/url?q\x3dhttp%3A%2F%2Fclasses.es\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNF1i-vogVGqspSglEGVy4Q1muuK5w';return true;">classes.es file (which describes what happened to all of the classes),
the Test class is marked as "excluded".
This will happen if a class is unreferenced, or if the Application containing that class has not been marked
as a prerequisite of the top level Application (the one you packaged).
Now, I realize you have only 1 Application, and you are referencing Test in your runtimeStartUp method...
I only mention it, in case it sparks any other thoughts.

I am not able to do much more, as I no longer have access to a 9.0 image...I have upgraded to the latest.

You might try making a simple visual part, instead of the Test class....something like TestView.
This will also give you some exposure to the GUI builder.
Then change your runtimeStartUp to open that, instead of your current Test class.

From what I can see, though, you have the right idea with your runtimeStartUp, which was what I offered to help
with originally.

And it did help. Thanks again.

I still think there is something missing with the support files, or your INI file has something incorrect in it
(sorry I cannot help with that one....your paths would definitely be different than mine).

Beyond that, I'm afraid I do not know what else to say....
If I think of anything else, though, I'll pass it along.

I hope you are able to get it working...

Again very informative post +++

Regards,
Julian

Sergei

On Thursday, February 28, 2019 at 1:30:47 PM UTC-5, [hidden email] wrote:
Hi Julian,
great post from you again.

Have some small comments:

четверг, 28 февраля 2019 г., 6:47:30 UTC+3 пользователь [hidden email] написал:
Hello, Sergei.

I think the answer is actually quite simple.

There is a certain set of required runtime files for any packaged image.
And at least in the folder you sent, not all of the runtime files are there.

When I try to run your EXE, I get the message that the procedure can not be found in DLL
ESVM40.DLL.....this is telling you that the DLL named esvm40.dll must also be included in your
runtime folder. You can copy this file from the VASmalltalk installation folder.

I get a different message. I have a localized version of Windows (not english) and on my platform I get message, saying that "Procedure entry point EsGetUPtr not found in dynamic link library D:\Working\Smalltalk Projects\Test\exe\Test.exe." (translated by me).
I also got messages like there was no DLL xxxxxxx.dll when the folder with the test application contained no dlls at all. So I copied the ones displayed in the error messages including esvm40.dll.

I know there will be other files you need as well, but that list will depend on your application
(for my application, there are something like 80 required files.
I think I`ll never reach such a quantity in my apps :)

I saw your message that you are not currently a customer...I am not sure what the rules are
on releasing runtime images, if you are not a customer. Certainly, there are some files you will
have no access to, and so at best, your runtime will include pop-ups indicating the Trial status.
Which of course is only fair...given you get to play with the development environment for free.
At current I develop for my pleasure :)) Like Smalltalk...And trial pop-up doesn`t bother me at all.

But if you are just trying it all out, you may just need to copy files from the installation folder
(also look in the nls folder...and I think there are a couple files from the bitmaps folder).

So...I think yo umay well have done everything right....you just need the correct list of supporting
files for your OS.

I hope that is helpful...
Thanks for your help.

Regards,
Julian Ford

On Thursday, February 21, 2019 at 10:58:37 AM UTC-5, [hidden email] wrote:
Hi Julian,

I very much appreciate your response because I was afraid no one would answer my question.

I tried to fulfill your recommendations, both with original application and with a new test one, but still get an error:
Procedure entry point EsGetUPtr not found in dynamic link library D:\Working\Smalltalk Projects\Test\exe\Test.exe (translated by me).

I attach a source and exe files of TestApp. Can you take a look at this example ant say where my mistake is?

Best regards,
Sergei.

P.S. The forum blocks from attaching files. AN alternative link is:

четверг, 21 февраля 2019 г., 5:17:00 UTC+3 пользователь [hidden email] написал:
Hi there.

You want to create that #runtimeStartUp method on the class side, of the class that has the same name as your application.
So...if you have an App named IpsToolsApp, then you will automatically have a class with that name.
Go into that class, turn to the class side, and create this...

runtimeStartUp

^IpsTools new open

Now, for every application that gets included in your package, each associated application class
will be sent the message #runtimeStartUp...so you can actually implement that method in other
of your apps too.

For simplictity, though, I tend to create a top level app, which will then define
the prerequisites for your finished product.
It is this top level application that I select to package.
And I implement #runtimeStartUp in only that one class.
This way, the initial start up is very simple.

I hope that is helpful....
Good luck!

Julian

On Monday, February 18, 2019 at 11:52:20 AM UTC-5, [hidden email] wrote:
Trying to make executable for the first time.

My application is without visual parts, just pure Smalltalk class.
For that case documentations says, that in the Windows to show at startup field we need to select <None>. Moreover, the class we want to open must contain a class method named runtimeStartUp.

The most interesting moment is that documentation gives a reference to the non-existent documentation VA Smalltalk Base User's Guide and gives no example of code for many Smalltalk application examples given in documentation itself.

To start up my application I execute the following command: IpsTools new open. So what method runtimeStartUp should contain in my example? Tried some evident code sequences, but still get error message (after wrong packaging).

Sergei.

Seth Berman

Re: make executable

In reply to this post by ipstools.project

Greetings Sergei,

You would not be the first to download trials and use them indefinitely, so don't worry...I'm not upset:)

Just know from a business perspective, the concept of indefinite trials does nothing for us.

Their a mechanism so folks can get a limited-time look before purchasing the product. That's its only purpose.

This is our business model...its how we stay in business..its how we keep VA Smalltalk alive and well.

The opensource license is our way to

Give back to the community with our engineering abilities
Get some promotion (although on our page I linked you see its not even a requirement to do that)
Hopefully, find that folks use it to better our VA Smalltalk community ecosystem (though, again...notice we only require committing to an open-source project...not even specifically VA Smalltalk).
and honestly, get folks using the product who otherwise wouldn't buy it anyway. Naturally this is limited to open-source projects...but I think that is more than fair

Yes, it requires something from those that want it...but again I don't think is that onerous.

You've been posting since Jan of 2017, which means you have at least 2 years experience with VA. You seem very smart from the posts I've read and our exchanges.

So for you, I would definitely recommend contributing some sort of small useful utility library or project to vastgoodies, and then send us an email as detailed here: https://www.instantiations.com/company/open-source.html

I don't recall that we have ever turned anyone down. We are simply asking folks to get involved and contribute, and in return they get a full opensource license to use for the entire product.

That doesn't seem like such a bad deal...right?:)

-- Seth

On Friday, March 1, 2019 at 9:31:45 AM UTC-5, [hidden email] wrote:

Greetings Seth,

пятница, 1 марта 2019 г., 0:28:55 UTC+3 пользователь Seth Berman написал:
Greetings Sergei,

I just wanted to provide an additional route to using VA Smalltalk that you might not be aware of.
We're happy to provide a trial license so folks can evaluate what they get before purchasing the product.
It offers a 45-day window from which the user can evaluate the usage of our product for commercial purposes.

You just opened my eyes on 45-days evaluation, I thought it was timeless. This finally caused me read carefully the License Agreement on the product. Maybe you should add a 45-days limitation info in the current pop-up message for those who doesn`t read the LA?

What you might think about doing is applying for one of our open-source licenses.
While you can not use this license for commercial purposes, it gives you a way to use our product for open-source projects.
In return, we ask that you commit to an open-source project. Preferably for VA Smalltalk (<a href="http://vastgoodies.com/" rel="nofollow" target="_blank" onmousedown="this.href='http://www.google.com/url?q\x3dhttp%3A%2F%2Fvastgoodies.com%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFuxnr60lH1eJZumpU0ZdEEA3DfSQ';return true;" onclick="this.href='http://www.google.com/url?q\x3dhttp%3A%2F%2Fvastgoodies.com%2F\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFuxnr60lH1eJZumpU0ZdEEA3DfSQ';return true;">http://vastgoodies.com/) but we're open
to others.

This might be a solution, but I`m very afraid that the piece of code I develop may not fit your requirements, because:
a) it`s a very specific, for some telecom equipment; I`m sure no one from smalltalk community on this board will be interested in this software
b) it`t very simple by look and feel and from end user point of view; but it`s difficult for me as smalltalk beginner;
c) for me as beginner this project may result in a long-term development period, even for beta version
d) it is a hobby, at least at current time

I believe this will ultimately work better for everyone because we're all participating in community building.
See more here: <a href="https://www.google.com/url?q=https%3A%2F%2Fwww.instantiations.com%2Fcompany%2Fopen-source.html&sa=D&sntz=1&usg=AFQjCNFqDiC1C0xusKcWLVoRSeNC6bL_xQ" rel="nofollow" target="_blank" onmousedown="this.href='https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.instantiations.com%2Fcompany%2Fopen-source.html\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFqDiC1C0xusKcWLVoRSeNC6bL_xQ';return true;" onclick="this.href='https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.instantiations.com%2Fcompany%2Fopen-source.html\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFqDiC1C0xusKcWLVoRSeNC6bL_xQ';return true;">https://www.instantiations.com/company/open-source.html

I will read.

- Seth

Sergei

On Thursday, February 28, 2019 at 1:30:47 PM UTC-5, [hidden email] wrote:
Hi Julian,
great post from you again.

Have some small comments:

четверг, 28 февраля 2019 г., 6:47:30 UTC+3 пользователь [hidden email] написал:
Hello, Sergei.

I think the answer is actually quite simple.

There is a certain set of required runtime files for any packaged image.
And at least in the folder you sent, not all of the runtime files are there.

When I try to run your EXE, I get the message that the procedure can not be found in DLL
ESVM40.DLL.....this is telling you that the DLL named esvm40.dll must also be included in your
runtime folder. You can copy this file from the VASmalltalk installation folder.

I get a different message. I have a localized version of Windows (not english) and on my platform I get message, saying that "Procedure entry point EsGetUPtr not found in dynamic link library D:\Working\Smalltalk Projects\Test\exe\Test.exe." (translated by me).
I also got messages like there was no DLL xxxxxxx.dll when the folder with the test application contained no dlls at all. So I copied the ones displayed in the error messages including esvm40.dll.

I know there will be other files you need as well, but that list will depend on your application
(for my application, there are something like 80 required files.
I think I`ll never reach such a quantity in my apps :)

I saw your message that you are not currently a customer...I am not sure what the rules are
on releasing runtime images, if you are not a customer. Certainly, there are some files you will
have no access to, and so at best, your runtime will include pop-ups indicating the Trial status.
Which of course is only fair...given you get to play with the development environment for free.
At current I develop for my pleasure :)) Like Smalltalk...And trial pop-up doesn`t bother me at all.

But if you are just trying it all out, you may just need to copy files from the installation folder
(also look in the nls folder...and I think there are a couple files from the bitmaps folder).

So...I think yo umay well have done everything right....you just need the correct list of supporting
files for your OS.

I hope that is helpful...
Thanks for your help.

Regards,
Julian Ford

On Thursday, February 21, 2019 at 10:58:37 AM UTC-5, [hidden email] wrote:
Hi Julian,

I very much appreciate your response because I was afraid no one would answer my question.

I tried to fulfill your recommendations, both with original application and with a new test one, but still get an error:
Procedure entry point EsGetUPtr not found in dynamic link library D:\Working\Smalltalk Projects\Test\exe\Test.exe (translated by me).

I attach a source and exe files of TestApp. Can you take a look at this example ant say where my mistake is?

Best regards,
Sergei.

P.S. The forum blocks from attaching files. AN alternative link is:

четверг, 21 февраля 2019 г., 5:17:00 UTC+3 пользователь [hidden email] написал:
Hi there.

You want to create that #runtimeStartUp method on the class side, of the class that has the same name as your application.
So...if you have an App named IpsToolsApp, then you will automatically have a class with that name.
Go into that class, turn to the class side, and create this...

runtimeStartUp

^IpsTools new open

Now, for every application that gets included in your package, each associated application class
will be sent the message #runtimeStartUp...so you can actually implement that method in other
of your apps too.

For simplictity, though, I tend to create a top level app, which will then define
the prerequisites for your finished product.
It is this top level application that I select to package.
And I implement #runtimeStartUp in only that one class.
This way, the initial start up is very simple.

I hope that is helpful....
Good luck!

Julian

On Monday, February 18, 2019 at 11:52:20 AM UTC-5, [hidden email] wrote:
Trying to make executable for the first time.

My application is without visual parts, just pure Smalltalk class.
For that case documentations says, that in the Windows to show at startup field we need to select <None>. Moreover, the class we want to open must contain a class method named runtimeStartUp.

The most interesting moment is that documentation gives a reference to the non-existent documentation VA Smalltalk Base User's Guide and gives no example of code for many Smalltalk application examples given in documentation itself.

To start up my application I execute the following command: IpsTools new open. So what method runtimeStartUp should contain in my example? Tried some evident code sequences, but still get error message (after wrong packaging).

Sergei.

ipstools.project

Re: make executable

Greetings Seth,

you are absolutely right, with one small correction: beginners like me, which learn Smalltalk by themselves and without coworkers help or discussions, and which are doing only first steps in Smalltalk, highly unlikely can contribute something helpful. And 2-years experience you mentioned tells nothing as individuals have different learning abilities. And for some other reasons. As to me, at current, I have a very limited understanding of Smalltalk, limits of which are defined by my application itself. It uses the simplest GUI ever possible (a terminal window), callbacks, threads, collections and string classes mainly. Not much. I event could compile Smalltalk code just about a week ago only with the help of ST community. And this code is even not a betta, it`s pre-pre alfa with not achieved even basic, minimum functionality. As a result, for contributing purpose and for learning by beginners, 45-days trial seems to be insufficient at all.
As for the open source project - I simply don`t have any idea what I can contribute with my current knowledge of Smalltalk.

So I have a suggestion :)) You allow me to evaluate the VA Smalltalk without time restrictions (I don't even need the fully licensed product), and this, as a result, allows to achieve the following:
1) Another Smalltalk fellow appears in the world - Smalltalk community growth - excellent Smalltalk statistic and trend :)
2) I make my current project, yes, very specific project, open-sourced (I didn`t have such plans until now) - anyone interested in it can join it ( I know at least one guy in Australia who might be interested in it) - look at p.1 :)
3) I create a home page for the project.
4) I place on page one of those "built with... " images.
5) Besides VA Smalltalk trial pop-up I add an implicit message, saying that my application is built with VA Smalltalk by Instantiations on terminal (i.e. my app) load.
6) When I "old and wise" :) I can give help to other beginners :)
And the last (but not the least) - the project I am currently working on, I guess, is on the first place, and the development tools - only on the second.

Regards,
Sergei.
пятница, 1 марта 2019 г., 18:50:29 UTC+3 пользователь Seth Berman написал:

Greetings Sergei,

You would not be the first to download trials and use them indefinitely, so don't worry...I'm not upset:)
Just know from a business perspective, the concept of indefinite trials does nothing for us.
Their a mechanism so folks can get a limited-time look before purchasing the product. That's its only purpose.
This is our business model...its how we stay in business..its how we keep VA Smalltalk alive and well.

The opensource license is our way to
Give back to the community with our engineering abilities
Get some promotion (although on our page I linked you see its not even a requirement to do that)
Hopefully, find that folks use it to better our VA Smalltalk community ecosystem (though, again...notice we only require committing to an open-source project...not even specifically VA Smalltalk).
and honestly, get folks using the product who otherwise wouldn't buy it anyway. Naturally this is limited to open-source projects...but I think that is more than fair
Yes, it requires something from those that want it...but again I don't think is that onerous.
You've been posting since Jan of 2017, which means you have at least 2 years experience with VA. You seem very smart from the posts I've read and our exchanges.
So for you, I would definitely recommend contributing some sort of small useful utility library or project to vastgoodies, and then send us an email as detailed here: <a href="https://www.instantiations.com/company/open-source.html" target="_blank" rel="nofollow" onmousedown="this.href='https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.instantiations.com%2Fcompany%2Fopen-source.html\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFqDiC1C0xusKcWLVoRSeNC6bL_xQ';return true;" onclick="this.href='https://www.google.com/url?q\x3dhttps%3A%2F%2Fwww.instantiations.com%2Fcompany%2Fopen-source.html\x26sa\x3dD\x26sntz\x3d1\x26usg\x3dAFQjCNFqDiC1C0xusKcWLVoRSeNC6bL_xQ';return true;">https://www.instantiations.com/company/open-source.html

I don't recall that we have ever turned anyone down. We are simply asking folks to get involved and contribute, and in return they get a full opensource license to use for the entire product.
That doesn't seem like such a bad deal...right?:)

-- Seth