Optional or Declared User Libs

[Dare2]

Would it be possible for PB to optionally load user libs?

My thinking goes like this:

• User libs are stored anywhere. The lib, associated residents and associated help all in the one folder.
  
  Programs could have a special compiler directive, say:

  Code: Select all

  CompilerUse "pathqualifier\libname"

  (or whatever is a good directive word) and that lib is then used.
  
  Anything stored in the "standard" user library area is handled as per current setup.

This would reduce clutter in the "Pure" folders; Make initial lib evaluation, acceptance and elimination a little easier (I'm lax); Provide an additional degree of latitude in project organisation; And possible also help reduce naming conflicts.

I would love this and see no harm in it, as anyone preferring to use the existing method could just drop their chosen libs in the existing folders.

[dontmailme]

Yes!

I like this idea.... especially for somebody like me who doesn't document very well.... it's so easy to forget which libs you have used in a program.

This would document the libs used by default, which would be very nice

Go on, put it in

[Kale]

Or also maybe a 'Collect for Distribution' command in the editor which copies all the used user libs into a folder called 'User Libraries' into the project folder where the source is located.

[PolyVector]

I would give a lung for either of these features! Especially the first

[blueznl]

we'll give you both features, now any specific words on that stone?