Menu
▾
▴
scrhostplugin-impl — Programming
You can subscribe to this list here.
| 2001 |
Jan
|
Feb
|
Mar
|
Apr
|
May
(8) |
Jun
(1) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
(1) |
|---|
|
From: Max B. <be...@ma...> - 2001-12-13 08:50:26
|
Hello scrhostplugin-impl, Разработка SHP CE идет полным ходом. в CVS добавлены два модуля: crasy и sunit. Результаты можно посмотреть там. -- Best regards, Max mailto:be...@ma... http://belugin.newmail.ru ICQ:9406811 |
|
From: Slava P. <sl...@ba...> - 2001-06-13 07:29:46
|
Hot devel news: Added stuff to build "hpp.exe" to automatically generate "Const.idl" from FAR SDK headers. To build the utility flex tool from UNIX world is required. The nearest task: iparser utility. ".i" files are intended for replacement of all ".h"/".cpp" files of disp objects. ".i" file format will be simple enough to maintain. All routine stuff of IUknown/IDispach methods will be autogenerated. Also we will be able to autogenerated debug stuff for all methods and to solve bug with SetFileApis. To build iparser we use flex+bison (lex+yacc - if it sounds clearer), UNIX tools ported to Win32. Look in CVS for source/iparser/*.* The thing to reseach in is IScript.ConnectObject(Prefix, Object). All I found is that using IProvideClassInfo[2] gives IID of [default,source] and ITypeInfo of class object. So we can obtain typeinfo of event interface. How can we work with it? - to provide event proxying to script sink we must know event dispmethods names -> to form script function name "UserPrefix_EventMehtodName". |
|
From: Max B. <be...@ma...> - 2001-05-23 09:04:43
|
Hello Slava, Wednesday, May 23, 2001, 1:03:20 PM, you wrote: SP> We have got 2 message about strange behaviour of InputBox. SP> The dialog disappears immediately after any key is pressed. SP> I cannot reproduce the bug. SP> The situation is likely to be caused by improper heap operation. So it is SP> very hard to catch with debugger (a mess in the heap appears in debugger in SP> the form of GPF- it may happen with a pointer or it may not). SP> Does anybody know how to check heap? Afair there are some tools for memory leaks detecting. http://search.dmoz.org/cgi-bin/search?search=memory+leak&all=yes&cat=Computers -- Best regards, Max mailto:be...@ma... http://belugin.newmail.ru ICQ:9406811 |
|
From: Slava P. <sl...@ba...> - 2001-05-23 08:51:38
|
We have got 2 message about strange behaviour of InputBox. The dialog disappears immediately after any key is pressed. I cannot reproduce the bug. The situation is likely to be caused by improper heap operation. So it is very hard to catch with debugger (a mess in the heap appears in debugger in the form of GPF- it may happen with a pointer or it may not). Does anybody know how to check heap? |
|
From: Slava P. <sl...@ba...> - 2001-05-22 11:43:49
|
> I see several tasks that we need to solve to successfully code the
project:
>
> 1) typelibrary generation is based on Far headers. I did convertion from
.H
> to .IDL manually and used 1702 headers. We can write perl script to
> automate the process. Also some constants are taken from "winuser.h" and
> "winnt.h"
>
> 2) We can wrap all dispatch method implementations in custom file format.
> Consider AutoGen toolkit for unix systems. I thought we could do C macros
> wrappers but it might not solve all problems. E.g.:
>
> GET(FileName)
> EditorInfo ei;
> if (!g_Info.EditorControl(ECTL_GETINFO, &ei))
> return E_FAIL;
> *pRetVal = SysAllocString(CHAR_TO_OLE(ei.FileName));
>
> expands to
>
> STDMETHODIMP CEditor::get_FileName(BSTR *pRetVal)
> {
> PTR(pRetVal);
> EditorInfo ei;
> if (!g_Info.EditorControl(ECTL_GETINFO, &ei))
> return E_FAIL;
> *Val = SysAllocString(CHAR_TO_OLE(ei.FileName));
> return S_OK;
> };
>
> The file format is negotiable. We do our own precompiler!
> This prevents us from dealing with IDispatch and other interfaces
> implementation routine.
>
> 3) Error handling is implemented ugly. No strategy. There is no useful
> logging in debug build. ISupportErrorInfo is not implemented - we need
this
> feature to report detailed descriptions of errors to script (appears in
VBS
> as "Err" object).
>
> 4) The compile time and run-time script errors can be and must be
> distinguished - but they do not. E.g. compile error results in dialog to
> allow user edit the script. Run-time error additinally may offer
> "ignore"/"ignore all" option.
>
> 5) Why the resulting image is so big? (even with startup code)
|
|
From: Slava P. <sl...@ba...> - 2001-05-21 12:37:51
|
SP> 1) using http://sf.net services (CVS) - requires you to have account on SP> sf.net, it is free SP> Project root at http://sf.net/projects/scrhostplugin 1.1) Using the patch tracker - > http://sourceforge.net/tracker/?atid=383137&group_id=25028&func=browse > SP> About how sources are organized I will send additional email. > SP> About how Active Scripting works -""- > SP> About what I think to be a nearest tasks -"- Or it will be some pages on http://scrhostplugin.sf.net |
|
From: Slava P. <sl...@ba...> - 2001-05-21 12:28:50
|
Ondrej, Hi. Here is the sources: http://cvs.sourceforge.net/cvstarballs/scrhostplugin-cvsroot.tar.gz see in /scrhostplugin/sources/*.* It seems there are 2 ways to work together 1) using http://sf.net services (CVS) - requires you to have account on sf.net, it is free Project root at http://sf.net/projects/scrhostplugin 2) using the list (I apply our changes to sources to CVS myself) You must know that the plugin is at stage of technology preview. So everything is negotiable and may be changed! To build the project from sources some tools are required: 1) bcc55 free, http://www.borland.com/bcppbuilder/freecompiler/ 2) optionally there is a debugger, http://www.borland.com/bcppbuilder/turbodebugger/ 3) to build some files Perl is needed, http://aspn.activestate.com/ASPN/Downloads/ActivePerl/ 4) to compile IDL files MS MIDL compiler is needed, http://www.microsoft.com/msdownload/platformsdk/setuplauncher.asp or MS VS6 is installed 5) to view model of COM API Rational Rose is needed http://www.rational.com/tryit/evals/roseeval.jsp or Max Belugin always does IDL or DOC files to view the model Current version of plugin is 0.1.6 0.2 is only been planning. BTW you subscribed only to one list. The 2nd is already in english http://lists.sourceforge.net/lists/listinfo/scrhostplugin-devel Actually there a shape of 0.2 is discussing. About how sources are organized I will send additional email. About how Active Scripting works -""- About what I think to be a nearest tasks -"- Ask questions. Again thanks for interest - it is very boring to be alone! |
|
From: Max B. <be...@ma...> - 2001-05-21 08:10:19
|
Hello Slava, Monday, May 21, 2001, 12:01:46 PM, you wrote: SP> 1) using http://sf.net services (CVS) - requires you to have account on SP> sf.net, it is free SP> Project root at http://sf.net/projects/scrhostplugin 1.1) Using the patch tracker - http://sourceforge.net/tracker/?atid=383137&group_id=25028&func=browse SP> 2) using the list (I apply our changes to sources to CVS myself) SP> About how sources are organized I will send additional email. SP> About how Active Scripting works -""- SP> About what I think to be a nearest tasks -"- SP> Again thanks for interest - it is very boring to be alone! Maybe you place it one the webpage -- Best regards, Max mailto:be...@ma... http://belugin.newmail.ru ICQ:9406811 |
|
From: Slava P. <sl...@ba...> - 2001-05-21 07:50:09
|
Ondrej, Hi. Here is the sources: http://cvs.sourceforge.net/cvstarballs/scrhostplugin-cvsroot.tar.gz see in /scrhostplugin/sources/*.* It seems there are 2 ways to work together 1) using http://sf.net services (CVS) - requires you to have account on sf.net, it is free Project root at http://sf.net/projects/scrhostplugin 2) using the list (I apply our changes to sources to CVS myself) You must know that the plugin is at stage of technology preview. So everything is negotiable and may be changed! To build the project from sources some tools are required: 1) bcc55 free, http://www.borland.com/bcppbuilder/freecompiler/ 2) optionally there is a debugger, http://www.borland.com/bcppbuilder/turbodebugger/ 3) to build some files Perl is needed, http://aspn.activestate.com/ASPN/Downloads/ActivePerl/ 4) to compile IDL files MS MIDL compiler is needed, http://www.microsoft.com/msdownload/platformsdk/setuplauncher.asp or MS VS6 is installed 5) to view model of COM API Rational Rose is needed http://www.rational.com/tryit/evals/roseeval.jsp or Max Belugin always does IDL or DOC files to view the model Current version of plugin is 0.1.6 0.2 is only been planning. BTW you subscribed only to one list. The 2nd is already in english http://lists.sourceforge.net/lists/listinfo/scrhostplugin-devel Actually there a shape of 0.2 is discussing. About how sources are organized I will send additional email. About how Active Scripting works -""- About what I think to be a nearest tasks -"- Ask questions. Again thanks for interest - it is very boring to be alone! |
|
From: Slava P. <sl...@ba...> - 2001-05-18 14:37:34
|
I see several tasks that we need to solve to successfully code the project:
1) typelibrary generation is based on Far headers. I did convertion from .H
to .IDL manually and used 1702 headers. We can write perl script to
automate the process. Also some constants are taken from "winuser.h" and
"winnt.h"
2) We can wrap all dispatch method implementations in custom file format.
Consider AutoGen toolkit for unix systems. I thought we could do C macros
wrappers but it might not solve all problems. E.g.:
GET(FileName)
EditorInfo ei;
if (!g_Info.EditorControl(ECTL_GETINFO, &ei))
return E_FAIL;
*pRetVal = SysAllocString(CHAR_TO_OLE(ei.FileName));
expands to
STDMETHODIMP CEditor::get_FileName(BSTR *pRetVal)
{
PTR(pRetVal);
EditorInfo ei;
if (!g_Info.EditorControl(ECTL_GETINFO, &ei))
return E_FAIL;
*Val = SysAllocString(CHAR_TO_OLE(ei.FileName));
return S_OK;
};
The file format is negotiable. We do our own precompiler!
This prevents us from dealing with IDispatch and other interfaces
implementation routine.
3) Error handling is implemented ugly. No strategy. There is no useful
logging in debug build. ISupportErrorInfo is not implemented - we need this
feature to report detailed descriptions of errors to script (appears in VBS
as "Err" object).
4) The compile time and run-time script errors can be and must be
distinguished - but they do not. E.g. compile error results in dialog to
allow user edit the script. Run-time error additinally may offer
"ignore"/"ignore all" option.
5) Why the resulting image is so big? (even with startup code)
|