Source language: Translate to:

hpwNewLISP - interface plugin to newLISP

Questions about NeoBook PlugIns

Moderator: Neosoft Support

hpwNewLISP

Postby HPW » Sun Jul 25, 2004 11:22 am

Just upload hpwNewLISP 1.10:

newLISP.DLL has a new command 'newlispEvalStr' instead of 'dllEvalStr'.
So with hpwNewLISP 1.10 this new command is used for calling newLISP.

Details: http://newlisp.org/index.cgi?News


(Edited by HPW at 8:23 pm on July 25, 2004)
HPW
 

hpwNewLISP

Postby HPW » Thu Aug 12, 2004 12:34 pm

Upload a new zip.

with newLISP.DLL 8.1.0

http://newlisp.org/downloads/newLISP_81 ... Notes.html

Since this is a official release I post it here.
In the past there were several development release of newLISP, where I upload a new ZIP, but did not post here. There is a release-number on the plugin page for the contained DLL. So users who are interested in development releases can check there for the latest release.
HPW
 

hpwNewLISP

Postby HPW » Tue Sep 21, 2004 8:23 am

Upload a new zip.

with newLISP.DLL 8.2.0

http://newlisp.org/downloads/newLISP_82 ... Notes.html

Since this is a official release I post it here.
In the past there were several development release of newLISP, where I upload a new ZIP, but did not post here. There is a release-number on the plugin page for the contained DLL. So users who are interested in development releases can check there for the latest release.
HPW
 

hpwNewLISP

Postby David Esperalta » Tue Sep 21, 2004 7:14 pm

Hello,

This message is single to say incredible Hans Peter!

Thanks HPW,
David Esperalta
 

hpwNewLISP

Postby HPW » Thu Sep 30, 2004 11:01 am

Just upload hpwNewLISP 1.11:

A more flexibel handling with the return-string.
You can now return newlisp's native string format.
The plugin converts them on the fly to neobook-format.

This makes the use of (silent(print ...)) obsolet.
We need to prevent the use of print because Sam found out that it has a memory leak.

So what do I do:
I scan the return string for
first and last char = "
or:
first six and last seven chars = [text][/text]

This text-flags are then deleted.
Then I do a replace:
\" to "
\r to chr(13)
\n to chr(10)
\t to chr(9)
\\ to \

This could cause some changes in current neobook sources using hpwNewLISP. But I think the simpler usage is worth the change.
HPW
 

hpwNewLISP

Postby Sam Cox » Thu Sep 30, 2004 5:35 pm

Hans-Peter,

Thank you, thank you!

My little application which was calling the newLisp.dll via hpwNewLispCall about 20 times per second (and therefore leaking as much as 40K bytes per second to the operating system) now works perfectly.

Wonderful work, and so quickly too.

P.S., I would have responded earlier but I spent a good part of the day in my dentist's chair experiencing periodontal (gum) surgery. Ouch!
Sam Cox
 

hpwNewLISP

Postby datadon » Thu Sep 30, 2004 8:39 pm

Ouch is right Sam.  Are you having soup tonight?

I was just looking through the plugin section and thinking about how far things have come in a few years.  Absolutely amazing.  I'm surprised we don't have 300,000 members,.... if they only knew.  And it is about to get even better later this year.  

My thanks to all the contributors including HPW and ALL the rest (including those who took the chance to try their first plugins) who have made it all so interesting.  Not that NB isn't interesting enough in itself.  I think it was one of the best choices of my life  (note to wife: it's ok, honey you were first)

whew almost forgot to add that or I'd have a lot of explaining to do later...

best to all and keep em comin'

Don
datadon
 

hpwNewLISP

Postby HPW » Thu Sep 30, 2004 10:39 pm

>leaking as much as 40K bytes per second to the operating system

As Lutz pointed out this happens because he use a MS function inside the print command which is known to use system resources without releasing them. So this is a workaround for a MS bug!
HPW
 

hpwNewLISP

Postby HPW » Fri Oct 01, 2004 2:48 am

>My little application which was calling the newLisp.dll via hpwNewLispCall about 20 times per second

Just for the interest, what do you do in newLISP 20 times per second?
;-)
HPW
 

hpwNewLISP

Postby HPW » Wed Oct 06, 2004 8:01 am

Upload a new zip.

with newLISP.DLL 8.2.1

This is not a official release, but this time I post it here.

A new option in the lisp command (write-buffer ..) allows a much faster construktion of script-strings in newLISP.

This results for example in the 'Tower of Hanoi' demo in the sample pub from a generation time of 950 ms to 15 ms (on my P4).
HPW
 

Postby Guest » Sun Oct 17, 2004 1:59 pm

But sorting by date seems not always properly.
Ths last message here was on 6.10, but does not show up in that order.

But new post show up correctly!
Guest
 

Postby Guest » Fri Nov 05, 2004 8:49 am

Just upload hpwNewLISP 1.12:

Added hpwNewLISP.ini in plugin-directory to be able to translate plugin comments.
This allow multi-language use of the plugin in the NeoBook-IDE.

Content of hpwNewLISP.ini:
Code: Select all
[PlugInHeader]
PlugInHint=Plugin for interfacing newlisp.dll >= 8.0.15 from neobook|Language-Strings in hpwNewLISP.ini|Next Line|Another Line

[GroupDescription]
1=Lisp-Calling
2=General

[CommandDescription]
hpwNewLispCall=Call a newLISP-function and get a return-string.|Next Line|Another Line
hpwSetNewLispDir=Set directory for newLISP.dll.|Next Line|Another Line
hpwSetNewLispErr=Set error-variable-name in neobook for returning errors from newLISP.dll.|Next Line|Another Line
hpwNewLispFileRead=Read Textfile to a Variable without pipe-handling!|Next Line|Another Line


(Pipe is used for line-breaks)

Now the user is able to translate/improve the descriptions of the plugin and the commands. Other plugins may follow.

Translations are wellcomed and could be included in the distribution.
Guest
 

Postby Guest » Mon Nov 15, 2004 9:32 am

Just upload hpwNewLISP 1.13:

Action: hpwNewLispFreeDll - Free newLISP.dll from memory.

Use with care. All variables inside newLISP will be lost.
Guest
 

Postby Guest » Tue Nov 16, 2004 12:09 am

Oops, seems that I have not upload the new ZIP.


Later:

Just checked it again. Seems to be the right one on the server.
Could be a problem with the proxy in the office.
So when the plugin is V1.13 it is the right one.
Guest
 

Postby Guest » Mon Nov 22, 2004 10:21 am

Upload a new zip.

with newLISP.DLL 8.3.0

http://newlisp.org/download/newLISP_83_ ... Notes.html

This is the next stable official release of newLISP.
Guest
 

PreviousNext

Return to PlugIn Discussions

Who is online

Users browsing this forum: No registered users and 1 guest

cron