Study Twinbasic FOR FORMS.* APP.*

[xiaoyao]

/Packages/WinNativeCommonCtls/Packages/WinNativeFormsBASE/Sources/BASE/BaseForm.twin

/Packages/WinNativeCommonCtls/Packages/VBRUN/Sources/VBRUN.twin
/Packages/WinNativeCommonCtls/Packages/WinNativeFormsBASE/Sources/SUPPORT
/Packages/WinNativeCommonCtls/Packages/WinNativeFormsBASE/Sources/BASE

[ InterfaceId ("45046D60-08CA-11CF-A90F-00AA0062BB4C") ]
Public Interface PropertyBag_VB5 Extends stdole.IDispatch
	Function ReadProperty(ByVal Name As String, Optional ByVal DefaultValue As Variant) As Variant
	Sub WriteProperty(ByVal Name As String, ByVal Value As Variant, Optional ByVal DefaultValue As Variant)
End Interface

[ InterfaceId ("4495AD01-C993-11D1-A3E4-00A0C90AEA82") ]
Public Interface _PropertyBag Extends PropertyBag_VB5
	Property Get Contents() As Variant
	Property Let Contents(ByVal value As Variant)
End Interface

[ CoClassId ("D5DE8D20-5BB8-11D1-A1E3-00A0C90F2731") ]
[ CoClassCustomConstructor ("[_HiddenModule].CreatePropertyBagObject") ]
Public CoClass PropertyBag
    [ Default ] Interface _PropertyBag
End CoClass

[xiaoyao]

why twinbasic have vb5 code?

If you want to develop your own IDE, like VB6, you can learn a lot of core code from TWINBASIC
VB Syntax, VB6 & VB5 - Binary Compatibility Broken
http://computer-programming-forum.co...a3b62ba12b.htm

Hello,
I have two UserControls written using VB5 but when I compile them using VB6
I get these two Binary Compatibility Broken Messages:
Message for the first usercontrol)
Original definition:
Event ReadProperties(PropBag As VBRUN.PropertyBag)
Message for the second usercontrol)
Original definition:
Property Get Font() As stdole.Font
Current definition:
Property Get Font() As Font
For the first case, I tried using VBRUN.PropertyBag_VB5 and still didn't
work.
In the ObjectBrowser the following was mentioned on the PropertyBag_VB5
class:
Member of VBRUN
VB5 version of PropertyBag interface.
Use this interface to maintain binary compatibility with VB5
projects that use this interface.
For the second case, I added the word "stdole" in front of "Font" and it
didn't help.
I would really appreciate your help. It won't make sense for me upgrading to
VB6 if I have to break the version compatibility of all my usercontrols.
Thanks in advance,
Arthur S.

[fafalone]

twinBASIC's compatibility target is vb6. So a bug prevents it from working in VB6, that's really outside of scope, and may cause problems for vb6 compatibility.

[Darkbob]

Has Twinbasic reached the point that it's useful? Or still heavily into the development/beta stage?

[xiaoyao]

has twinbasic reached the point that it's useful? Or still heavily into the development/beta stage?

it's support small project

[fafalone]

Has Twinbasic reached the point that it's useful? Or still heavily into the development/beta stage?

Both really.

It covers 100% of the pure syntax, has dozens of new features already in place, all basic UI controls are available along with about half of mscomctl controls. The list of unimplemented features/methods is getting quite short. The biggest ones at this point are MDI forms and the Printer object.

A good way to see how useful it is it to check out some of the complex projects I've ported to it and updated for x64:

Carles PV's Lemmings


ucShellBrowse / ucShellTree - Can compile these UCs to 64bit to use in 64bit Office.


ETW File Activity Monitor


It uses RC5 so 32bit only but ColinE66's PacMan clone works too.

Then there's a bunch more on my GitHub, including an example of calling CreateThread directly with no hacks needed.

So yes, it's already very useful. It can import and run a lot of complex projects.

But it's also still beta software under development, so you have a few missing features and will run into some bugs.

[VB6 Programming]

Both really.

It covers 100% of the pure syntax, has dozens of new features already in place, all basic UI controls are available along with about half of mscomctl controls. The list of unimplemented features/methods is getting quite short. The biggest ones at this point are MDI forms and the Printer object.

A good way to see how useful it is it to check out some of the complex projects I've ported to it and updated for x64:

Carles PV's Lemmings


ucShellBrowse / ucShellTree - Can compile these UCs to 64bit to use in 64bit Office.


ETW File Activity Monitor


It uses RC5 so 32bit only but ColinE66's PacMan clone works too.

Then there's a bunch more on my GitHub, including an example of calling CreateThread directly with no hacks needed.

So yes, it's already very useful. It can import and run a lot of complex projects.

But it's also still beta software under development, so you have a few missing features and will run into some bugs.

The big missing feature for me is support of MDI forms

[fafalone]

Yeah that's a pretty big standout at this point, but it's a v1 must-have according to Wayne so hopefully not too much longer. I've got a few projects I'd like to bring to tB waiting in the wings for it too.