Recent Posts

Pages: [1] 2 3 ... 10
1
Scripting Languages / Re: Script BASIC COM
« Last post by John on January 15, 2018, 10:22:35 PM »
I wanted to post an update to where the SBCOM project is at this point. I would like to thank Mike for extending the interface to work with Sage BOI.


This is an example of using the Script BASIC multi-threaded application server (that runs as a Windows service) and Sage 100 BOI to generate an ABC demo company contact list in the launcher web control.

Code: Script BASIC
  1. ' BOI Customer Contact - Web Page
  2.  
  3. IMPORT cgi.sbi
  4. IMPORT boi.sbi
  5.  
  6. oscript = BOI::CREATE(:SET, "ProvideX.Script")
  7. BOI::CBN oScript, "Init", :CALL, "C:\\Sage\\Sage 100 Advanced ERP\\MAS90\\HOME"
  8. osession = BOI::CBN(oscript, "NewObject", :SET, "SY_Session")
  9. BOI::CBN osession, "nSetUser", :CALL, "JRS", "MyPassword"
  10. BOI::CBN osession, "nsetcompany", :CALL, "ABC"
  11. BOI::CBN osession, "nSetDate", :CALL, "A/R", "20171218"
  12. BOI::CBN osession, "nSetModule", :CALL, "A/R"
  13. ocust = BOI::CBN(oscript, "NewObject", :SET, "AR_Customer_svc", osession)
  14.  
  15. cgi::Header 200,"text/html"
  16. cgi::FinishHeader
  17.  
  18. PRINT """
  19. <html>
  20. <header>
  21. <title>Customer Contacts</title>
  22. </header>
  23. <body>
  24. <table>
  25. <center><h1>ABC - Customer Contacts</h1></center>
  26. <table style="width:100%">
  27.  <tr>
  28.    <th>Customer Number</th>
  29.    <th>Company Name</th>
  30.    <th>Phone Number</th>
  31.  </tr>
  32. """
  33.  
  34. BOI::CBN ocust,"nMoveFirst"
  35. DO UNTIL BOI::CBN(ocust, "nEOF", :GET)
  36.   PRINT "  <tr>\n"
  37.   PRINT "    <td>",BOI::CBN(ocust, "sCUSTOMERNO", :GET),"</td>\n"
  38.   PRINT "    <td>",BOI::CBN(ocust, "sCUSTOMERNAME", :GET),"</td>\n"
  39.   PRINT "    <td>",BOI::CBN(ocust, "sTELEPHONENO", :GET),"</td>\n"
  40.   PRINT "  </tr>\n"
  41.   BOI::CBN ocust, "nMoveNext"
  42. LOOP
  43. PRINT """
  44. </table>
  45. </body>
  46. </html>
  47. """
  48.  
  49. BOI::CBN ocust, "DropObject"
  50. BOI::CBN osession, "DropObject"
  51. BOI::RELEASE oscript
  52.  


2
Interpreters / Re: Introducing BASIC8
« Last post by wangrenxin on January 12, 2018, 08:37:33 PM »
Thanks for your kindness.
3
Interpreters / Re: Introducing BASIC8
« Last post by John on January 12, 2018, 05:30:31 PM »
Quote
(Not intending to be spam, but this may really sound like an ad, feel free to delete this if it's not proper to post here.)

There is no restrictions on this forum to only free or open source software.

Looks great and only $15.


4
Interpreters / Re: Introducing BASIC8
« Last post by AlyssonR on January 12, 2018, 01:47:33 AM »
Looks good.

I'll probably take a look when I have time.
5
Interpreters / Introducing BASIC8
« Last post by wangrenxin on January 11, 2018, 10:17:08 PM »
(Not intending to be spam, but this may really sound like an ad, feel free to delete this if it's not proper to post here.)

As MY-BASIC getting close to its first stable release, I've put my efforts on a MY-BASIC powered project for months. Which is called BASIC8. I'm using MY-BASIC as the language kernel for this software, with some extra extended syntax, such as bitwise operators, coroutine, linear algebra... and more libraries for game and other program development. The idea is similar to PICO-8, but BASIC8 is designed mostly from my own purpose and design. And it's BASIC, instead of Lua. This is something I'd been looking for to make quick prototype, and weekend projects. Don't know how many people would be interest in it, but anyway hope it could make the experience enjoyable.

Homepage: https://paladin-t.github.io/b8/

6
Open Forum / Re: Back to the future
« Last post by Charles Pegge on December 23, 2017, 02:34:22 AM »
I don't think stdcall and cdecl can be improved, given the limitations on Pentium registers. I use something very similar to cdecl for non-exported functions when compiling 64-bit in OxygenBasic.
7
Open Forum / Re: Back to the future
« Last post by AlyssonR on December 22, 2017, 01:54:09 AM »
64-bit helps Kernel developers but does little for high-level languages and applications. And I moan about the 64-bit calling conventions at every opportunity. They are totally wacko.

You mean that the 32-bit conventions aren't?

Mind you, I'm still thinking in 16-bit, here   :o
8
Open Forum / Re: Back to the future
« Last post by John on December 20, 2017, 04:22:10 PM »
The funny thing is that Linux people have put 32 bit behind them long ago. A completely different mentality with where Microsoft is going (or not) with Windows 64 bit.
9
Open Forum / Re: Back to the future
« Last post by Charles Pegge on December 20, 2017, 08:38:45 AM »
64-bit helps Kernel developers but does little for high-level languages and applications. And I moan about the 64-bit calling conventions at every opportunity. They are totally wacko.
10
Open Forum / Re: Back to the future
« Last post by AlyssonR on December 18, 2017, 02:31:23 AM »
64-bit windows is a pretty useless evolution -

It gives no benefit in speed, arithmetical precision or process capacity.

It doesn't even seem to improve memory handling.

The extra memory is useful, but that costs more money.


The 2GB limit on Access DB seems to be down to a 32-bit codebase simply compiled for 64 bit - like so many other programs.
Pages: [1] 2 3 ... 10