Page 3 of 3 FirstFirst 123
Results 21 to 25 of 25

Thread: scintilla (texteditor) example :)

  1. #21
    thinBasic author ErosOlmi's Avatar
    Join Date
    Sep 2004
    Location
    Milan - Italy
    Age
    57
    Posts
    8,777
    Rep Power
    10
    thinBasic Programming Language engine is all inside thinCore.dll.
    It is the language, it is the core of all, it is the glue that connects to all other modules.

    thinBasic modules (any module) cannot be used without thinCore.dll.
    Every module talks with thinCore.dll, thinCore.dll drive modules needed by the scripts.

    thinBasic.exe and/or thinBasicc.exe are just executor and loader of thinCore.dll
    Maybe we can talk more about modules and how to create one of them.

    Regarding os_shellexecute and os_shell they are two completely different commands.
    os_shellexecute execute a command (Open, Print, Run, ... or whatever) of a registered shell extension
    os_shell instead creates a process executing an application (with or without some command line params)

    Ciao
    Eros
    www.thinbasic.com | www.thinbasic.com/community/ | help.thinbasic.com
    Windows 10 Pro for Workstations 64bit - 32 GB - Intel(R) Xeon(R) W-10855M CPU @ 2.80GHz - NVIDIA Quadro RTX 3000

  2. #22
    @eros:

    thanks btw for you last answer some month ago too

    '------------------------------------------------------------------------>
    text part of thinbasic journal #2:

    1.1 Application layer
    It is the execution process, the main application.
    This layer must accomplish 3 steps:
    initialize the underline Core layer,
    tells to Core Layer which thinBasic application
    (we will call it “script” for the rest of the article)
    to execute de-initialize the Core engine.

    Two applications type: A) console, b) GUI

    1.2 Core layer
    This is the most important part of thinBasic programming language.
    It is the glue that keeps together all the different parts that
    play a role in thinBasic execution.
    It contains the main thinBasic Core language and is in charge of:
    load and parse the script manage all memory
    handling (allocation / de-allocation of variables,
    function stacks, internal structures in place for module handling)
    expose a series of functions interface used by
    modules to communicate with main thinBasic
    engine module handling on request (find the correct module dll,
    opening it, link the keywords with the module functions,
    call functions implemented by modules, releasing modules when needed)
    '------------------------------------------------------------------------>
    my question is how the saved textfile buffer for interpreting (for example my last tb scintilla file at this board) reach the thinair.exe or thincore.dll ? what's the initialisation "kick" that start the parser or interpreter for working?

    nice week-end there to italy, here the snowy winter
    in germany starts for a short moment to come back at the moment, bye largo

  3. #23
    thinBasic author ErosOlmi's Avatar
    Join Date
    Sep 2004
    Location
    Milan - Italy
    Age
    57
    Posts
    8,777
    Rep Power
    10
    To invoke a script file to be executed, just pass its name (full path name) to thinBasic.exe executable as parameter.
    See instructions in help or online help at http://www.thinbasic.com/public/prod...l?howtouse.htm
    www.thinbasic.com | www.thinbasic.com/community/ | help.thinbasic.com
    Windows 10 Pro for Workstations 64bit - 32 GB - Intel(R) Xeon(R) W-10855M CPU @ 2.80GHz - NVIDIA Quadro RTX 3000

  4. #24
    hello! I've a simple problem to understand about working behaviour of different editor (here for example: scintilla based).

    If I have a DLL (for example "prometheus.dll", perhaps a parser or such thingy) and this dll was built by freebasic it's not possible to load and work with another editor (thinair, powerbasic editor (SED), "scite" for oxygen and much more) for interpreting or running this parser, isn't it? anybody can give hints or links or example to understand this behaviour? it's obvious you have to bind in same language the editor and the parser or interpreter or compiler for working, but I don't understand that, because it's possible to load a library (*.dll) and "embed" this "prometheus.dll" in every editor you can imagine. after that I can bind the function for parsing or what else. I am right or wrong?

    bye, largo
    Last edited by largo_winch; 13-02-2013 at 12:18.

  5. #25
    thinBasic author ErosOlmi's Avatar
    Join Date
    Sep 2004
    Location
    Milan - Italy
    Age
    57
    Posts
    8,777
    Rep Power
    10
    largo,

    ...assuming that your DLL is a standard flat 32bit DLL ...

    to be able to work with a .DLL you need to know the syntax of SUB/FUNCTION exported by that .DLL:
    1. names of SUB or FUNCTION
    2. number, sequence and type of each parameters (if any) needed by SUB or FUNCTION
    3. type of FUNCTION return values

    Having that inside a declare source code (called also header files), you can use DLL functionalities

    Without that info, it would be impossible to guess how to call functions inside of that DLL
    Plus (of course) you need to have some info on how that DLL works
    www.thinbasic.com | www.thinbasic.com/community/ | help.thinbasic.com
    Windows 10 Pro for Workstations 64bit - 32 GB - Intel(R) Xeon(R) W-10855M CPU @ 2.80GHz - NVIDIA Quadro RTX 3000

Page 3 of 3 FirstFirst 123

Members who have read this thread: 0

There are no members to list at the moment.

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •