hello everyone, this sounds a good improvement imho
anyway thinking about this, i have a pair of questions that maybe someone could answer.

1) Using the new compiller, along with the .EXE, all the .PBDs will still be created? if yes like i guess, there will be one PBD for every folder (ex .PBL)?
2) Imagine we are using InfoMaker and distribute a .PBL containing several reports that we could modify remotely on a client's machine without the need to rebuild and recompile, how to accomplish this task using the new approach? Should we distribuite the source folder containing the source dw reports instead of the old PBL?

"Nobody is going to like that." 

Speak for yourself, the whole world and all new technologies use this characteristic.

Hi Roland;

  FYI: Here is what I see in my PB 2025 alpha version PB App wise. Note that the Workspace object is gone being replaced by the new "Solution" object. PBL's are now folders and PB objects are basically like you would export their source in the current PB 2022 Rx releases ...

HTH

Regards .. Chris

So ...

If I understood Bruce's image (from a presentation by Armeen I still don't know anything about), we are only going to get P-Code based executables?

(I don't mind, I prefer P-Code, but it might be and important thing to know for other people).

We will still maintain the legacy compiler for the long-term so the PBL is not going away if you don't want it to.  The new plain text format is just a choice and not forced on you.  Please look at Bruce's post for more details.

"Nobody is going to like that."

I, for one, say "good riddance". :) No more large binary files that contain both source code and compiled code? Yes, please.

From Armeen's presentation.

From what Im seeing Armeen presenting here at the European seminars:

1.  Its a new option, you can continue to use the PBL if you want to.

2.  When its enabled, the source code is saved separately from the compiled pcode.  The files are stored in folders that mimic the PBL structure (like the source code is stored under ws_objects today for the SVN and Git interfaces)

Question to Roland,

Would you upgrade Wizsource when this change happens?

regards.

I don't see the need for the pbl.  pretty much everything except the IDE itself spends time exporting out to plain text before doing anything anyway. 

I *assume* that the pbl originally was created due to limitations with the windows file system in 1989.   Seems to just cause problems today.

SCC systems such as roland's wizsource may have the bigger problems.

More and more changes and more and more bugs. How do you ever expect us to upgrade our customers? Some new things are really nice, but then next to be undone / destroyed, like the .Net "Framework" support for the DLL importer tool as an example. Appeon has said it wants to totally move away from .Net Framework and migrate to .Net 6/7/8. What about OLE and COM, that won't work anymore then is it? And of course the ever changing RTE control which is never bug free. Native PDF has also never had a bug free version. I'm scared by the idea of this upcoming change. Luckily we don't use Git because that's another PIA. (Thank you Roland for WizSource!!!!).

We need more solid testing on the part of Appeon before expecting us to do the work of testing for them whilst having angry customers. We're not upgrading anything until we see something solid out here.

just my 2cts.

Hi.

Can't say if I like the idea or not. But if it's true, then some things should be handled differently... The plan is to change pbl to folder like pb.net was doing? Or to get rid? If it's the second, what will happen with pbd's? Will be able to customized if we want to still use pbl's or not?

Andreas.