Hello Nick,

On 06 Nov 14 20:35, Nick Andre wrote to Nicholas Boel:

 NB>> Thanks for clarifying. Were there any plans on anyting else in the
 NB>> future, not?

 NA> Yes, absolutely, and then some. Far too often I get inquiries about
 NA> supporting Squish, Jam, TBBS, EzyCom, Renegade and what have you. Not
 NA> just the message formats, but the files those BBS programs use to
 NA> store the actual message areas. Take Renegade. Sure I could toss to
 NA> it, but the Sysop still has to enter in all of those areas; because
 NA> the base-list is in another database.

 NA> So in D'Bridge 4 the plan is to use a completely different
 NA> message-base model. Something that uses actual scripts to define the
 NA> database format. The original author wanted it that way and I want to
 NA> make it happen.

 NA> What it means, is you write a plain-English script that defines the
 NA> various fields and structure types... so, a different script for
 NA> *.MSG, Squish, JAM, Goldbase, etc. The tosser then reads this script
 NA> and knows what to go do with itself when handling messages. Because
 NA> its a script, it means it could be tailored to update whatever
 NA> additional databases the BBS software uses to store the base-list,
 NA> access codes, etc etc.

 NA> It also makes D'Bridge future-proof against any possible changes or
 NA> additions to BBS software... so for example, lets say some other BBS
 NA> program gets a revival from some crazy wicked programmer like G00R00
 NA> for TBBS or Searchlight. Fine, just write a script for D'Bridge and
 NA> presto, its supported.

 NA> It means D'Bridge supports it without me tearing apart the whole code.

That sir, is a hell of an idea. :)

Regards,
Nick

--- GoldED+/LNX 1.1.5-b20130910