VO GUI Classes to Winforms

robert · Post by **robert** » Tue Jun 16, 2020 3:12 pm

Bernhard,
I don't think we will port RP to the new GUI classes.
We might consider to move the preview window to the Windows Forms classes and use Unicode drawing api to paint the strings so we can support unicode there too.

Robert

TimothyS · Post by **TimothyS** » Tue Jun 16, 2020 11:44 pm

Does this mean that RP3 can be made to work with the new GUI classes?

robert · Post by **robert** » Wed Jun 17, 2020 6:19 am

Timothy,
I don't think Rp3 will be ported to the new UI classes, unless someone else wants to do that.
Rp3 uses the Classmate UI, and this is different from the VO GUI.
We might be able to port the RP3 preview window, but that is as far as I would go.
Things would change of course if there were enough customers willing to invest in this development.

Robert

Bernhard Mayer · Post by **Bernhard Mayer** » Wed Jun 17, 2020 6:28 am

Hi Robert!

Currently the RP2 printing relies on having a Vulcan.VO.Window based owner; do you think it would be possible to change that to a IWin32Window based one?

BR,
Bernhard

robert · Post by **robert** » Wed Jun 17, 2020 6:44 am

Bernhard,

What I have in mind for Rp2 is to create a new PtrPreview window (there is a Dialog and childapp window at this moment) that uses the PrintPreviewDialog control from Windows.Forms. Of course we also need to change the printer engine , especially the Print() methods in each of the field types, because that version will not work with a VO compatible PtrDevice class but with a .Net class to print.
Almost all other code (the logic behind the report) can stay the same.
And yes, I would want to design the new preview window in such a way that it will not depend on the VO compatible window objects.

Robert

Joachim Bieler · Post by **Joachim Bieler** » Wed Jun 17, 2020 7:20 am

Hi Bernhard,

many things are conceivable and also desirable. But in the first step the bBrowser must be ported first. That must be a lot of work. Which further data sources are supported later depends then also on the acceptance of the new bBrowser.

Joachim

SHirsch · Post by **SHirsch** » Wed Jun 17, 2020 10:03 am

robert wrote:Timothy,
I don't think Rp3 will be ported to the new UI classes, unless someone else wants to do that.
Rp3 uses the Classmate UI, and this is different from the VO GUI.
We might be able to port the RP3 preview window, but that is as far as I would go.
Things would change of course if there were enough customers willing to invest in this development.
Robert

I have also very strong interest in porting Classmate and RP3 to new UI classes.
Is it possible to make classmate open source so everyone with interest could contribute?

Stefan

wriedmann · Post by **wriedmann** » Wed Jun 17, 2020 10:07 am

Hi Stefan,
it is impossible to port Classmate to the new GUI classes - ClassMate is not using the VO GUI classes in any way as it is a cmplete replacement.
For ClassMate the same process must be made as for the VO GUI classes: they must be moved from the Windows API to Windows Forms.
ReportPro 3 is another thing: it is an ActiveX, so it should be usable directly in the new GUI classes as every other ActiveX.

Wolfgang

robert · Post by **robert** » Wed Jun 17, 2020 10:24 am

Wolfgang,

wriedmann wrote:Hi Stefan,
ReportPro 3 is another thing: it is an ActiveX, so it should be usable directly in the new GUI classes as every other ActiveX.

That would be a possibility but that would mean that the reports are still Ansi only.

Robert

robert · Post by **robert** » Wed Jun 17, 2020 10:26 am

Stefan,

SHirsch wrote: I have also very strong interest in porting Classmate and RP3 to new UI classes.
Is it possible to make classmate open source so everyone with interest could contribute?
Stefan

I am afraid that will not be easy.
This code is owned by the people from DataPro.
We have their permission to keep it "up to date" and provide support to VO users.
Moving the code to Open source is a different thing.

Robert

Main menu