Next version new features

[GeoTrail]

This looks like an exiting new path for B4PPC.
Maybe one day we can compile DLL's directly from the IDE

[Erel]

Originally Posted by agraham

I think Modules are a very good idea and only involve a single addition to the B4ppc syntax 'Public'. I assume that the mechanism will be based on the existing capability of referencing source files as components so keeping compatibility with the device IDE which I assume (maybe wrongly?) won't support tabbed editing

I am less sure about the need for module name prefixing, the .NET languages get away without it for objects in referenced assemblies except where it is needed in the case of a name clash. It might also make AutoComplete a bit clumsy.

Only the desktop IDE will support tabbed editing.

You can think of modules as singleton objects (or static / shared objects).
I think that the module prefix together with AutoComplete (which will only show the public fields) will be very handy.
The code should be more clear as you will be able to see right away where does each sub come from.

[WZSun]

I see lots of possibilities using modules..

Imagine this:

Program.exe (small size, actually a simple loader)
Menu.mod (encrypted modules)
Program1.mod (encrypted modules)
Program2.mod (encrypted modules)
...
Program3.mod (encrypted modules)


Program.exe loads menu.mod and display a screen selection. User can select Option 1, 2, or 3.. and it will then load the ProgramX into memory; and offload Menu.mod so that memory is optimized.

This is useful for anyone who writes different modular addons for projects.

[agraham]

I don't think the Modules that Erel is proposing will help at all for this sort of thing. A B4ppc program implemented in modules will compile into a single application. The modules will be a (welcome) way of compartmentalising code and hiding implementation details by only having Public interfaces exposed to other Modules and the main program.

To implement what you describe in B4ppc requires separately compiled applications implemented as exe or dll.

[Mr_Gee]

Originally Posted by klaus

It would be interesting that the modules could be in different directories. In my programs there is some common code that could be in one or several modules in a general directory and the specific code for a specific program in it's specific directory. So all projects look for these general modules in the same directory and no need to copy them to all project directories.

I love this idea maybe AppPath and the default install folder under/BAS
that way you can put the frequently used items under the install dir, and project specific items under the AppPath.

Also an easy way to import these .BAS files would also be nice
e.g. Tools>Modules>
import - would give you a OpenFile dialog
select - would show you the modules in the B4P install folder


Just being curious, when is the next release scheduled?
and where can i sign up for the beta test

[Erel]

I want to update you all that controls and objects will not be global as I first wrote.
Instead each module will have its own set of controls and objects (which will be accessible by other modules). Making it much easier to reuse modules.

Originally Posted by Mr_Gee

Just being curious, when is the next release scheduled?
and where can i sign up for the beta test

I hope to release a beta version during September. Any help with testing the beta version will be highly appreciated
You will be able to join the beta testers group after the release.