Page 3 of 14

hpwNewLISP

PostPosted: Sun Dec 21, 2003 3:51 pm
by HPW
Just released hpwNewLISP 1.07:

Features:

All custom-command parameters are internally surrounded by curly braces.

The last one is the return-variable and always needed. You can create a dummy var if not needed.

(Edited by HPW at 11:52 pm on Dec. 21, 2003)

hpwNewLISP

PostPosted: Mon Dec 22, 2003 3:15 pm
by NeoSoft Support
>>For Hanoi.lsp I have tried to measure the time in newLISP. But I don't know if it is that fast or if the neobook timer just not work as long as the DLL works in the process. I start the timer before calling the plugin and the stop is the first command in the action-string which is started with nbPlayAction.<<

NeoBook's timers do work while other apps and dlls are running, but they may not have high enough resolution to be useful for timing computer activity. How are you using a timer to track the activity in Lisp?

hpwNewLISP

PostPosted: Mon Dec 22, 2003 3:19 pm
by HPW
Just using newlisp internal timer commands to measure the time. The only thing which could be made better is the time when it is displayed. It should be displayed when the drawing starts, not at the end. But this is only kosmetic.

hpwNewLISP

PostPosted: Fri Dec 26, 2003 12:19 pm
by HPW
Just released hpwNewLISP 1.08:

Features:

Changes on Error-handling.
newLISP timer in Hanoi now display before drawing.
First version of Sam's nlcStrTrim.

hpwNewLISP

PostPosted: Mon Dec 29, 2003 2:24 pm
by HPW
Just upload my first extension.DLL for newLISP.

Download:
http://hpwickern.bei.t-online.de/anmeld ... wLISP.html

Exported functions:

hpwMimeEncodeFile,
hpwMimeDecodeFile,
hpwZlibCompressFile,
hpwZlibDeCompressFile,
hpwMimeEncodeString,
hpwMimeDecodeString,
hpwZlibCompressString,
hpwZlibDeCompressString;


Sample usage:

(import "hpwNLUtility.dll" "hpwMimeEncodeFile")
(import "hpwNLUtility.dll" "hpwMimeDecodeFile")
(import "hpwNLUtility.dll" "hpwZlibCompressFile")
(import "hpwNLUtility.dll" "hpwZlibDeCompressFile")
(import "hpwNLUtility.dll" "hpwMimeEncodeString")
(import "hpwNLUtility.dll" "hpwMimeDecodeString")
(import "hpwNLUtility.dll" "hpwZlibCompressString")
(import "hpwNLUtility.dll" "hpwZlibDeCompressString")

(get-string(hpwMimeEncodeFile "mySource.ext" "myTarget.ext"))
(get-string(hpwMimeDecodeFile "mySource.ext" "myTarget.ext"))
(get-string(hpwZlibCompressFile "mySource.ext" "myTarget.ext"))
(get-string(hpwZlibDeCompressFile "mySource.ext" "myTarget.ext"))

(setq mytest(get-string(hpwMimeEncodeString "This is a Teststring!This is a Teststring!This is a Teststring!")))
(setq mytest1(get-string(hpwMimeDecodeString mytest)))
(setq mytest(get-string(hpwZlibCompressString "This is a Teststring!This is a Teststring!This is a Teststring!")))
(setq mytest1(get-string(hpwZlibDeCompressString mytest)))

When it is possibble in neobook, why not in newLISP ;-)


(Edited by HPW at 10:25 pm on Dec. 29, 2003)


(Edited by HPW at 8:30 pm on Dec. 30, 2003)

hpwNewLISP

PostPosted: Tue Dec 30, 2003 12:29 pm
by HPW
I have setup a web-page for newLISP-extensions:

http://hpwickern.bei.t-online.de/anmeld ... wLISP.html

hpwNewLISP

PostPosted: Tue Dec 30, 2003 2:40 pm
by Sam Cox
Hi Hans-Peter,

In a future release of the hpwNewLisp plug-in, would it be possible to let programmer's specify the name of the NeoBook variable that is updated during an error return?  The most freedom I can imagine would let me specify the variable name at the time I put together the error return string.  Another completely acceptable way would be to specify the name of the NeoBook error return variable when the hpwNewLisp plug-in is initialized along the lines of the 'hpwSetNewLispDir' command.  If neither of these are possible or worth your effort, can we use a variable name other than [LastError] -- perhaps [nlcError] or [hpwError]?

My reason for this request is that since NeoBook itself uses the [LastError] variable, some NeoBook programmers may believe that *only* NeoBook itself is allowed to update this variable.  When an error they don't understand is reported in [LastError], they may contact NeoSoftware Support directly or on this Forum for help.  I think I can prevent many of these support calls if I report errors in a different variable -- especially if the variable's name is related to the function or library name (e.g., [nlcError].

Thanks,
-- Sam

hpwNewLISP

PostPosted: Wed Dec 31, 2003 12:53 am
by HPW
Just released hpwNewLISP 1.09:

Features:

Action: hpwSetNewLispErr Set error-variable-name in neobook for returning errors from newLISP.dll.
Variable: [nbNewLispErr] Contains the current error variable.

hpwSetNewLispErr used with empty varname set it to [LastError].
So now you can do it even on runtime.
Complete freedom.

Last, but not least: newlisp.dll 7.402

Since this is the last plugin news for this year, I wish all neobookers a happy and healthy new year!


(Edited by HPW at 9:03 am on Dec. 31, 2003)

hpwNewLISP

PostPosted: Wed Dec 31, 2003 9:10 am
by HPW
Just upload another extension for newLISP.

Download:
http://hpwickern.bei.t-online.de/anmeld ... wLISP.html

hpwNLAutoItDll is a header for AutoItDll.dll. No wrapper-dll is needed.

Exports:

AUTOIT_Sleep
AUTOIT_BlockInput
AUTOIT_ClipGet
AUTOIT_ClipPut
AUTOIT_DetectHiddenText
AUTOIT_IfWinActive
AUTOIT_IfWinExist
AUTOIT_IniRead
AUTOIT_IniWrite
AUTOIT_IniDelete
AUTOIT_LeftClick
AUTOIT_LeftClickDrag
AUTOIT_MouseMove
AUTOIT_MouseGetPosX
AUTOIT_MouseGetPosY
AUTOIT_RightClick
AUTOIT_RightClickDrag
AUTOIT_SetCapslockState
AUTOIT_SetStoreCapslockMode
AUTOIT_Send
AUTOIT_SetKeyDelay
AUTOIT_SetTitleMatchMode
AUTOIT_SetWinDelay
AUTOIT_Shutdown
AUTOIT_WinWait
AUTOIT_WinWaitActive
AUTOIT_WinWaitNotActive
AUTOIT_WinWaitClose
AUTOIT_WinHide
AUTOIT_WinRestore
AUTOIT_WinMinimize
AUTOIT_WinMaximize
AUTOIT_WinMinimizeAll
AUTOIT_WinActivate
AUTOIT_WinClose
AUTOIT_WinMove
AUTOIT_WinSetTitle
AUTOIT_WinGetActiveTitle
AUTOIT_WinShow
AUTOIT_WinMinimizeAllUndo

hpwNewLISP

PostPosted: Thu Jan 01, 2004 7:53 am
by HPW
Just upload another extension.DLL for newLISP.
(SQLite.dll 2.8.8 included)

Download:
http://hpwickern.bei.t-online.de/anmeld ... LISP4.html


Exported functions:

hpwSQLiteCreate
hpwSQLiteQuery


Sample usage:

(import "hpwNLSQLite.dll" "hpwSQLiteCreate")
(import "hpwNLSQLite.dll" "hpwSQLiteQuery")

(get-string(hpwSQLiteCreate "c:/newlisp/mytest.db" "^"))

(get-string(hpwSQLiteQuery "c:/newlisp/NL.db" "Select * FROM SQLITE_MASTER" "|" "^"))
(get-string(hpwSQLiteQuery "c:/newlisp/NL.db" "Select ROWID as ID, * from Simpsons" "|" "^"))
(get-string(hpwSQLiteQuery "c:/newlisp/NL.db" "Update Simpsons Set Firstname='Chief1' where Lastname='Wiggum 1'" "|" "^"))


The parameter "|" is used for delimiting the database-fields in a record.

The parameter "^" is used for delimiting the result-string from SQLite variables:
ChangeCount
LastError
LastErrorMessage

hpwNewLISP

PostPosted: Sun Jan 04, 2004 10:15 am
by HPW
Just reload hpwNewLISP 1.09:

New develoment-release newlisp.dll 7.405.
Minor fix in demo-pub because change in retunvalue of '(sys-info)'.

hpwNewLISP

PostPosted: Sat Jan 10, 2004 1:13 am
by HPW
Upload a new zip.

New development release of newLISP.dll 7.407

Allow optional parameter for calling conventions on import of DLL.
Other fixes.


(Edited by HPW at 9:14 am on Jan. 10, 2004)

hpwNewLISP

PostPosted: Sun Jan 11, 2004 11:21 am
by HPW
Lutz has posted a new sample lisp to use SQLite directly from newLISP. So no more wrapper-DLL necessary. Even hpwSQLite for neobook is obsolete now. You can use SQLite via hpwNewLisp. (Of cource there are other feature in hpwSQLite like the Grid or the Column-Combo)

You can find it here:

http://newlisp.org/download/development/

hpwNewLISP

PostPosted: Wed Jan 21, 2004 11:02 am
by HPW
Upload a new zip.

New final release of newLISP.dll 7.500

hpwNewLISP

PostPosted: Sat Feb 07, 2004 1:31 pm
by HPW
Upload a new zip.

New development release of newLISP.dll 7.502

New arrays in newLISP.