On 7 Jul 2005 at 16:24, Andrew Stiller wrote: > On Jul 6, 2005, at 1:02 PM, David W. Fenton wrote: > > > It seems to me self-evident that linked parts are the way Finale > > should have been designed from the beginning. ...The data file is a > > database, and there are various report views for showing that data > > and subsets of that data.... Then the only question is whether or > > not the different views are completely independent of each other in > > terms of the "view" characteristics (i.e., layout) or if subviews > > (individual parts) inherit characteristics from the global view > > (score). > > I agree--with this caveat: The Page Setup parameters must be > independently configurable/savable for the score and for each > individual part. Anything less is a deal-breaker as far as I'm > concerned. As of now, I know of no program that allows more than one > Page Setup configuration (at a time) per file, and I have therefore > assumed that this restriction is unavoidable. Correct me if I'm wrong.
The way I've always described dynamic parts has been exactly that way -- that there is independent information stored for each view. If the positioning of a "p" in the flute part can be independent from the score, that means that there is a special data structure dedicated to the flute part for store layout/positioning data specific to that particular part. Including page/system layout definitions in that is a no-brainer. Now, I'd also say there should be a layer intermediate between the score and parts, a "default part layout" definition, so that when you create a part view, it inherits those part layout parameters (much like Finale's current independent page layouts settings for extracted parts). Then, when you edit a particular part (perhaps optimizing and dragging a few systems, or changing the margins of a few system to fit more/fewer systems on a page), those changes would be stored for the part. > And while we're at it, would it be asking too much to figure out some > way to transfer page setup data between platforms? I realize the > operation is done completely differently in Mac vs. Windows, but > information is information isn't it?--and should, therefore, somehow > be retrievable and transferrable. I'm not sure why there's a problem today. If you create a file with page layout definitions in it, you can save a library, or send the file to someone and they can save the library for page layout and import it into their document. Or use Robert's Settings Scrapbook to copy the settings. I'm not sure what you're asking for here that can't be done in a manner that's already pretty consistent with the way these things work in Finale. -- David W. Fenton http://www.bway.net/~dfenton David Fenton Associates http://www.bway.net/~dfassoc _______________________________________________ Finale mailing list Finale@shsu.edu http://lists.shsu.edu/mailman/listinfo/finale
