visible versioning scheme for UserLibraries

[mskuma]

There seems to no way to determine what PB version a UserLibrary is meant for. I'm sure many of you have picked up a UserLibrary, put it aside, then found it again wondering which version it was designed for. A UserLibrary is a file with no extension - quite naked - and has no identifiers or properties to indicate version. It would be nice if a property or at least an extension could be used to indicate which PB version it can be used with.

[PB]

UserLibraries can have any filename, so I'd suggest the authors of them should
name them appropriately when releasing them (eg. MyLibrary_400). Of course
this means you can also rename them yourself if you like.

[mskuma]

It's a good idea, the only problem is of course - it's a totally manual process that's up to the developer or user to figure it out and add it. It would be far better if there was a hand-off process that automatically adds it, but it's a moot point, since there is no official lib builder. If it eventually becomes a bonafide compile-option (like dll etc), it would be great to have a version property in the builder tool, so the version info becomes part of the lib file itself, so it can readable later by some other tool or method. Maybe it's something that can be done in the tailbite program in the meantime (not sure, my speculation only - maybe there's an unused area in the lib that could be used as a comment or version info?).

[naw]

I'd like to have a Library navigator / report that lists the commands contained within each Library. It would be very handy to identify command-name conflicts.

Also, in PB, would be nice to be able to switch on/off libraries easily - perhaps even switch off specific commands in libraries.

Because these features dont exist - I try to avoid using any non-standard libraries.

My programs arent particularly sophisticated, so I can do pretty much everything I want with standard PB...

[Flype]

I'd like to have a Library navigator / report that lists the commands contained within each Library. It would be very handy to identify command-name conflicts.

Also, in PB, would be nice to be able to switch on/off libraries easily - perhaps even switch off specific commands in libraries.

Because these features dont exist - I try to avoid using any non-standard libraries.

My programs arent particularly sophisticated, so I can do pretty much everything I want with standard PB...

1/ about a navigator :
it's possible, i've done it for fun, not really finished but it works.
But yes it should be integrated to the IDE.

2/ about switching on/off :
it's possible by moving files from a directory to another and restarting the compiler. But yes it should be integrated to the IDE.

one day

[Kiffi]

long time ago, ts-soft and i wrote a Tool for switching Userlibraries and
resident-files. if i understand you correctly, this tool may be usefull for you:



the tool has also an english gui.

Download here

Greetings ... Kiffi

[Flype]

sorry but dead link :roll:

[Fluid Byte]

The posted link seems to be messed, try this:

http://www.tuebben.de/kiffi/downloads/ulrs.zip

[Kiffi]

The posted link seems to be messed, try this:

yes, sorry, my **** downloadcounter is broken. I've corrected the link above.

Greetings ... Kiffi

[Flype]

that's really good kiffy - didn't know this one.

might be really one step better if you could include the parsing of the resident files. because in these files there are also really good stuff : constante, macro, interface and prototype. i have source code for that if you want.

[ricardo]

long time ago, ts-soft and i wrote a Tool for switching Userlibraries and
resident-files. if i understand you correctly, this tool may be usefull for you:



the tool has also an english gui.

Download here

Greetings ... Kiffi

Excellent!! 5 starts for you!!

This is exactly what i was looking for!!

Thanks!