A constellation has a way to specify which drives, directories, files and extensions to include and which drives, directories, files and extensions to exclude. This could be handled with lists, wildcards and/or regexes. You would submit the constellation, or a list of files generated from it to a backup utility, a CD (Compact Disk) burner program to prepare a program for distribution, a FTP (File Transfer Protocol) upload utility, a program like The Replicator, a link checker, an HTML (Hypertext Markup Language) validator, a global search and replace, an indexer, a macro expander, a compiler, a tidier… The nice thing about constellations is they don’t need to be manually adjusted when a few files are added or deleted. Constellations have rules to tell them what to do with the new files.
A constellation should have a name so that it can be specified and updated in one place, and referenced by a short name as a parameter to some utility.
Unfortunately, the concept of constellation has not yet penetrated the programming world, so there is no uniform way to specify them, or reuse them in different programs. There is no standard DTD (Document Type Definition) for the layout. This is primarily a political problem. Hint, hint. I invite you to share your ideas with me.
The definition of a standard constellation file format and constellation library would allow you to easily add filtering to any program designed to process just a single file. It would also the user to define a constellation once, and reuse it with a large number of different utilities. A utility to convert a constellation to a list of files would let you use your constellations with legacy utility that don’t understand constellations, but accept an @include.list of files.
How about some ideas on what the XML syntax for such a beast would look like? I could write a library to read it and let you then convert any single-file processing utility into a constellation-of-files processing utility. I will convert all my multi-file software to the new format and publish all source code. Maybe the idea will catch on. Here is what a constellation file might look like:
Obviously the fine points of the grammar need to be sorted out, but that gives you the general picture.
The file format is pretty geeky, to unfriendly for non-programmers so you would need GUI (Graphic User Interface) tools to create them with check boxes. You could have a uniform pre-check to let you know just what files would be processed. It also might be possible to take a linear list of files and generate a compact constellation description of it. This would give you a skeleton constellation you could manually refine. It would be a lot less work than creating it from scratch.
available on the web at:
optional Replicator mirror
Please email your feedback for publication, letters to the editor, errors, omissions, typos, formatting errors, ambiguities, unclear wording, broken/redirected link reports, suggestions to improve this page or comments to Roedy Green : . If you want your message, your name or email kept confidential, not considered for public posting, please explicitly specify that. Unless you state otherwise, I will treat your message as a letter to the editor that I may or may not publish in the feedback section. After that, it will be too late to retract it. If you disagree with something I said, especially when sending an ad-hominem attack, a rant composed mainly of obscenities or a death threat, please quote the offending passage and cite the web page where you found it, tell me why you think it is wrong, and, if possible, provide some supporting evidence. I can’t very well fix erroneous or ambiguous text if I can’t find it.
Your face IP:[220.127.116.11]
|Feedback||You are visitor number 11.|