[RESOLVED] Edit tbForm file as a text file?

[AAraya]

Is it possible to edit a tbForm file as a text file? I have a couple dozen VBCCR18 TextBoxW controls on a form that I want to quickly convert to a regular tB TextBox. In VB6 I could edit the .FRM file and change the type of the control in a text editor from "VBCCR18.TextBoxW" to "VB.TextBox". I'm looking to do similar with the tbForm file.

I found a way to view the tbForm as a JSON file by right clicking on it in the Project Explorer but the contents are not editable.

If not, is there another way in tB to do this task?

TIA

[WaynePhillipsEA]

Is it possible to edit a tbForm file as a text file? I have a couple dozen VBCCR18 TextBoxW controls on a form that I want to quickly convert to a regular tB TextBox. In VB6 I could edit the .FRM file and change the type of the control in a text editor from "VBCCR18.TextBoxW" to "VB.TextBox". I'm looking to do similar with the tbForm file.

I found a way to view the tbForm as a JSON file by right clicking on it in the Project Explorer but the contents are not editable.

If not, is there another way in tB to do this task?

TIA

Unfortunately you can't edit the designer files directly just yet. The workaround is to export the project (File menu >Export), make the modifications to the raw files, and then import into a new project file (option on the New project dialog).

[xiaoyao]

The best way to do this is to develop twinbasic plug-ins and use them to add controls or change control types automatically.
If in a few years. We have 100 to 300 plug-ins, and then the brand moment is really stable and mature.There is no plug-in. Without nuget. Exe, without NPM. Exe, the average developer cannot contribute to your company.

So we see a version update every day, with a lot of bugs and mynahs.
All functions can only be completed by the author. It's very scary and very hard.
If it can be done like Google Chrome, community members contribute most of the code.

[xiaoyao]

Unfortunately you can't edit the designer files directly just yet. The workaround is to export the project (File menu >Export), make the modifications to the raw files, and then import into a new project file (option on the New project dialog).

I very much hope that many forms and module files can be shared by multiple projects. If I have 200 modules and 50 forms to be used repeatedly in many projects, it will be a disaster, because you can't do this function at all now.

I wrote the coreldraw CpG plugin the other day.With two t1b references, the entire project becomes 2mb. If referenced, it will generate some dummy header files, if it can be saved under a directory. Multiple projects can use it together.

In China, there is a programming language more than 20 years ago,Easy language development tool, such as VB6 and vc6, but one of its projects has only one file, which is encrypted.
As a modern development language, this is fatal.
In case of accidental hard disk damage or code problems, the source code of the whole project is completely scrapped and can not be repaired.

[fafalone]

Yes using external files like a .vbp is planned for v1.0 last I heard, so shouldn't be too far off.

[xiaoyao]

It is better to be compatible with the original format, so that the BAS module file of VB6 and TWINBASIC can be shared. The project supports adding existing VB6 source files (keep the original format).

[fafalone]

Yes I'm sure the external file support will have the same support for .cls and .bas like the internal version; if you've exported a project from tB, you see that .bas/.cls is still in the same proper format for VB6. .frm is another matter; that's a one way conversion afaik and I don't think making it two-way is really worth the time and complications from supporting essentially a whole new, more limited form format. So you'll likely be able to share those with other tB projects but not VB6. Wayne can correct me if I'm wrong.