Printable View
My understanding is that twinBASIC already supports multi-threading, but language syntax to support the feature needs to be added.Quote:
Originally Posted by yereverluvinuncleber
You can see the multi-threading capabilities from the debug console.
multithreading in twinBASIC example
I once had a wish-list for VB6 and it had certain items in it, some were just nice-to-haves. As time has progressed the main things for me have concreted to become 64bitness, multi-threading and multi-platform support. 64bitness as any target platform support for 32bit is likely to end sooner than I want it to, whether or not I am happy with 32 bits myself, MS will make that step one day. Some Linuxes and os/x are already there.
Multiplatform support as I am ready to rid myself of the Microsoft shackles, Win10 was a hint to leave and never return.
https://www.youtube.com/watch?v=WuDwUnhwPAk
That was what Win10 told me.
Multi-threading? As I compare my VB6 program with a program I am currently cloning I find there are some clear points where multi-threading would drastically alter my program's performance with those tasks that have to occur concurrently at the moment.
Support for modern image types was always another but that is off my wish list as that support will come by default I am assuming.
Nearly two weeks without a visible update. Something good must be hatching.
twinBASIC status update
twinBASIC update May 23 2021
Having no news is still some news :-))Quote:
Originally Posted by VB6 Programming
cheers,
</wqw>
Updated version of twinBASIC out now - v0.10.313
https://marketplace.visualstudio.com...asic/changelog
https://twinbasic.com/preview.html
It would be great if we could get something definitiive about support for existing vb6 forms.
On one page there is this statement that doesn't mention .FRM files
while on this page it saysQuote:
There will also be support for VB6 .BAS and .CLS files in the future versions.
I know that Schmidt does not expect support for existing forms.Quote:
Forms / GUI support, including full backwards compatibility with existing VB6 forms.
The plan is that we will be offering two types of forms in twinBASIC. One will be Windows-only, and will be fully backwards compatible with VB6 forms. The second type will be available cross-platform, but will lose some compatibility (though we will try to keep things generally very similar, as much as possible). I hope that answers your question, but let me know if you need any further clarification.Quote:
Originally Posted by vbrad
That's great, thanks. Sounds like a good solution to me!Quote:
Originally Posted by WaynePhillipsEA
That sounds indeed great to make two form objects.
One which is a "VB6" form object (windows-only) and another "tB" form object (cross-platform) which is as compatible as possible.
Im looking forward to the "cross-platform" mode.
one thing that Im thinking about is "sound" support
theres no real good sound support in vb6, thats why we use typelibs/API, but if we have a cross-platform we can not use that.
will there be a build-in cross-platform alternative for that?
and, the .png/opacity image support that vb6 dont have, again, a build-in cross-platform alternative.
If TB will use Cairo in background then support for PNG will be by default available!
twinBASIC status update
https://nolongerset.com/twinbasic-update-may-30-2021/
Wayne says: "Very soon we'll be moving on to the next big phase... GUI support"
"In other news, I thought it worth mentioning here that I've now decided on the approach for GUI support. twinBASIC will eventually offer two types of GUI forms. One for Windows-only, which is fully backwards compatible with VB6, and a second type of form that supports cross-platform but is not 100% backwards compatible. I'll be making every effort to make the cross-platform forms 'feel' like VB6 forms as much as possible, and the form designer will be shared between them both."
twinBASIC status update:-
https://nolongerset.com/twinbasic-update-june-6-2021/
Lots of progress in twinBASIC this week...
https://nolongerset.com/twinbasic-update-june-13-2021/
including
- Create New Project
- Support new 'Like' operator
- Lots of bug fixes
a big step for TwinBasic :)
Attachment 181682
Allows to build the executable for RC6 with events like the example :
"Visualizing a Recordset (multiple Columns and CheckBoxes)"
without any code modification
Attachment 181683
how would I do that?Quote:
Originally Posted by VB6 Programming
I am not familiar with visual studio code
the programming language is VB6 / VBA, Visual Studio Code is the IDEQuote:
Originally Posted by Semke
You will find all installation instructions here:
https://www.twinbasic.com/preview.html
https://code.visualstudio.com/docs/g...ips-and-tricksQuote:
Originally Posted by Semke
Start VSCode (e.g. Start->Run: code) and press Ctrl+Shift+P and type "twin" without the quotes to find available commands.
cheers,
</wqw>
twinBASIC status update:
https://nolongerset.com/twinbasic-update-june-20-2021/
Lots of progress this week.
There has now been over 600 downloads of the twinBASIC preview.
twinBASIC status update:
https://nolongerset.com/twinbasic-update-june-27-2021/
Major developments this week, including support for (external) version control; the code prettifier; support for embedded resources; and support for visual styles via manifest files.
https://twinbasic.com/preview.html
twinBASIC status:
Lots of improvements ...
https://nolongerset.com/twinbasic-update-july-4-2021/
And an early look at the VS Code based forms editor ...
https://twitter.com/WaynePhillipsEA/...66748296306690
Another early look at the twinBASIC form editor
https://twitter.com/WaynePhillipsEA/...01290518867975
twinBASIC status update:
A sneak peek at the yet-to-be-released form editor, a teaser about possible control inheritance, and a future option for version control ...
https://nolongerset.com/twinbasic-update-july-11-2021/
twinBasic status update:
https://nolongerset.com/twinbasic-update-july-18-2021/
twinBasic status update:
First release expected in 2-3 months (there is already a preview release available).
https://nolongerset.com/twinbasic-update-july-25-2021/
so, theres a subscription plan, and ordering that now, you get a discount, since the features are not in place yet they want to give you a discount for helping out now with the development costs.
what are everyone thoughts about this, anyone already subscribing?
For me, as I make money from VB6, it feels like a sensible thing to do to support this project.Quote:
Originally Posted by baka
I've signed up and if it all works out it should prove to have been a good investment.
If for some reason it doesn't, well them's the breaks as the saying goes.
I haven't yet but I intend to.Quote:
Originally Posted by baka
I'm just trying to decide between Professional and Ultimate.
My big requirement is to upgrade existing VB6 software to 64 bit (for Windows 10/11). So that suggests the Professional version.
I can't see I'm ever going to need a Mac OS version, not sure about Linux (I know Linux is the desktop OS of tomorrow, but I just can't wait that long ;) ). Maybe Linux for server?
Android is always interesting, I've no requirement at the moment - but that could change.
So do I go Ultimate or Professional?
twinBasic status update:
https://nolongerset.com/twinbasic-update-august-1-2021/
You can go for Professional. If for whatever reason in the future you need Ultimate you can migrate and you keep still 40% discount. (Only 10% loss)Quote:
Originally Posted by VB6 Programming
This seems to be coming along nicely.
Wasn't me this time.Quote:
Originally Posted by Shaggy Hiker
I think that is probably the best approach.Quote:
Originally Posted by Krool
Coincidentally I now have an immediate requirement to develop an Android app. Unfortunately twinBASIC won't be ready in time for that.
If you are referring to the progress of twinBASIC I totally agree with you :)Quote:
Originally Posted by Niya
What twinBASIC offers already is stunning.
It's sad really that Microsoft could have done this years ago with VB6 but chose not to (I don't expect you to agree with me on that ;) )
twinBasic status update:
https://nolongerset.com/twinbasic-update-august-8-2021/
I don't think it's sad. They made the right move. They had to sacrifice VB6 for the greater good.Quote:
Originally Posted by VB6 Programming
However, what they should have done, is open sourced VB6 after .Net became mature. It wouldn't have made sense to do it earlier because no one would have given .Net a try, including me. I would have stayed in VB6 if it was developed alongside VB.Net and I would have missed out big time. However at this point in time, I believe it makes sense to open source VB6 and let the community do with it what they want with it. There is no need for force anyone to give .Net try because at this time, those of us who are here already know how great it is and those that stayed behind are never going to move so they might as well throw them a bone and let them be happy.
Also, it can't hurt to be able to spruce up old VB6 applications with some modern features without breaking your back. Personally, I wouldn't write any new apps in it but it would be nice to breath some life into all those old VB6 programs I have lying around and the ones still in active meantainance.
twinBASIC 12-MONTH ROADMAP
The 12 month roadmap for twinBASIC...
https://github.com/WaynePhillipsEA/twinbasic/issues/335
Expected release dates:
- FILE I/O SUPPORT (September 2021)
- 64-BIT COMPILER SUPPORT (October 2021)
- OPTIMIZED COMPILATIONS (November 2021)
- FORMS GUI SUPPORT
- form designer and cross-platform forms engine (November 2021)
- VB6-compatible Forms engine (February 2022)
- Reimplementation of all remaining VB6 shipped controls (August 2022)- MULTI-THREADING LANGUAGE SUPPORT (December 2021)
- INHERITANCE LANGUAGE SUPPORT (December 2021)
- EDIT & CONTINUE SUPPORT (March 2022)
- CROSS PLATFORM SUPPORT
- Initial support for x86 and x64 builds on Linux and Mac OS (May 2022)
- Support for ARM CPU architectures, and Android OS (August 2022)- VBWATCHDOG SUPPORT (December 2021)
- and many other features
I just gave TwinBasic an actual try and HOLY **** IM IMPRESSED!!!
Now, it's very far from being a production ready version of VB6 but for all the talk I've heard over the years about a new VB6 IDE, this one is really for real. I mean I believed in it's promise ever since I first heard of it here on these forums but I had no idea how advanced it really was already. I just took some semi-complex code I wrote in this post and popped it in, expecting a problem or two but the damn thing just worked, without needing a single change. This is really good progress, especially on the promise on VB6 compatibility.
Looks like you guys are getting your new VB6 after all. You guys have been waiting decades for this. Don't let this fail now.
Now, there are a couple pain points that I think may need to be worked out but I'll do that in a follow up post. Gonna play with for a little bit and see what comes up.
Couple of pain points in the intellisense. It doesn't work with enum type parameters. You actually need to type out the enum type with the dot for the enum choices to come up.
Also it's really hard to get a sense of what is what when reading the intellisense description of functions and subs. Visual Studio uses different colours/text styles so you can easily differentiate parameter names, function/sub name and parameter types. Sometimes I just want to know what the parameters are at a glance and having different colours represent different things goes a very very long way. It doesn't even have to be colours alone. Simply bolding or using italics can help. The VB6 intellisense bolds function/sub parameters you're currently typing so you can tell at a glance what you're looking it and where you are.
I know these seem minor but they are huge productivity boosts.
EDIT:
Just noticed the intellisense underlines the parameter you're currently typing. It's not noticeable enough. Maybe bold it too or perhaps use a different colour like modern versions of Visual Studio does.
Another thing, whenever I create a new project, it opens a new instance of VS Code. That is really annoying. It would be nice if it did it in the same instance.