David W. Fenton wrote:
Of course, I also seem to remember something about pre-defined
vertical positioning having been added in a recent version of Finale,
so I may be late with the idea.
Indeed. In fact, expression positioning goes far beyond anything
articulation can offer. The two are differ
On 24 Feb 2005 at 10:13, Jari Williamsson wrote:
> David W. Fenton wrote:
>
> > What I *would* support is if the text expression dialog's text box
> > at the top were instead replaced with the standard Finale text
> > editor. Then you could put anything in the text expression that you
> > could p
At 11:58 AM 2/24/05 +0100, Johannes Gebauer wrote:
>It still escapes me why this kind of thing cannot live happily in two
>different tools.
jef suggested two.
My followup suggestion was to combine at least seven tools (text,
expression, articulation, chord, lyrics, clef, time signature) and let a
Dennis Bathory-Kitsz wrote:
Have a look at this:
http://maltedmedia.com/photos/toolbar.gif
It still escapes me why this kind of thing cannot live happily in two
different tools.
Before the expression tool was improved I could see that there was some
overlap between measure text blocks and measure
On the other hand I am pretty sure the feature set for 2k6 has already
been decided anyway, so we are talking about 2k7, maybe 2k8, so that
really shouldn't be a reason.
Johannes
Kurt Gnos wrote:
At 09:15 23.02.2005, you wrote:
It's a nice list, but I think that getting compact and reliable PS,
Kurt Gnos wrote:
At 09:15 23.02.2005, you wrote:
It's a nice list, but I think that getting compact and reliable PS,
EPS, and PDF output would be sufficient for one year's upgrade. If
this is supposed to be a tool for publishing, it has got to be able to
output in the principle formats for publ
David W. Fenton wrote:
What I *would* support is if the text expression dialog's text box at
the top were instead replaced with the standard Finale text editor.
Then you could put anything in the text expression that you could put
into the text editor, and the user interface would be exactly the
At 11:54 PM 2/23/05 -0600, Noel Stoutenburg wrote:
>I don't think they are interchangeable texts at all, because they have
>different funnctions in the music. For one thing, text expressions have
>a specific impact upon way the music itself is to be realized, for
>example, how loud, or how fas
Responding my to my comment, in part:
One can certainly have different tools that
operate on the same object, and different objects acted on by the same
tool. But just because the objects are acted on by the same tool, even
if they happened to look the same, doesn't autmatically and necessarily
At 12:10 AM 2/24/05 +0100, Johannes Gebauer wrote:
>I am not against this, but I fail to see how I would benefit? There is
>no reason why I would want my title text blocks appear in the expression
>list, it would only convolut it more. OK, I know that you have ideas on
>how to get more organizat
On 23 Feb 2005 at 15:30, Brad Beyenhof wrote:
> On Wed, 23 Feb 2005 18:07:32 -0500, Dennis Bathory-Kitsz
> <[EMAIL PROTECTED]> wrote:
> > At 04:16 PM 2/23/05 -0600, Noel Stoutenburg wrote:
> > >Jef did not originally, and you do not in your supporting post,
> > >address the issue of merging the li
On 24 Feb 2005 at 0:10, Johannes Gebauer wrote:
> There is
> no reason why I would want my title text blocks appear in the
> expression list, it would only convolut it more. OK, I know that you
> have ideas on how to get more organization into these lists.
>
> I have been thinking about this sev
At 07:41 23.02.2005, you wrote:
Because of overlapping functionality, the previous expression tool and
text tool have been combined into one powerful text tool which offers all
the previous features of both tools, albeit with some revolutionary
improvements.
I would NOT mingle the two tools sinc
At 09:15 23.02.2005, you wrote:
It's a nice list, but I think that getting compact and reliable PS, EPS,
and PDF output would be sufficient for one year's upgrade. If this is
supposed to be a tool for publishing, it has got to be able to output in
the principle formats for publication.
Amen! Ju
On Wed, 23 Feb 2005 18:07:32 -0500, Dennis Bathory-Kitsz
<[EMAIL PROTECTED]> wrote:
> At 04:16 PM 2/23/05 -0600, Noel Stoutenburg wrote:
> >Jef did not originally, and you do not in your supporting post,
> >address the issue of merging the lists that Jef seems to propose.
>
> I'm just being supple
Dennis Bathory-Kitsz wrote:
I don't think I'm being clear. These all all interchangeable texts, with
aspects of function assigned. They are only different in Finale because the
program started out making them different. They were once all engraved with
the same tools, and software separated them ou
At 04:16 PM 2/23/05 -0600, Noel Stoutenburg wrote:
>Jef did not originally, and you do not in your supporting post,
>address the issue of merging the lists that Jef seems to propose.
I'm just being supplementary. But think of a Palm and how it organizes
addresses by categories. It's a droplist of
At 04:16 PM 2/23/05 -0600, Noel Stoutenburg wrote:
>One can certainly have different tools that
>operate on the same object, and different objects acted on by the same
>tool. But just because the objects are acted on by the same tool, even
>if they happened to look the same, doesn't autmaticall
Dennis Bathory-Kitsz wrote:
At 05:31 AM 2/23/05 -0600, Noel Stoutenburg wrote:
you could please address the issue of what benefits you
see arising from your proposal to merging what is currently the list of
the text subset of the expression tool, with the list of the text tool.
I think me
At 06:31 AM 02/23/2005, Noel Stoutenburg wrote:
>5) the inability to group expressions into collections, so that in my
>expression list, I could define a group, "dynamics", place all the
>dynamics related expressions into that, and collapse the group when I
>wanted to view only the "tempo" related
At 01:41 AM 02/23/2005, shirling & neueweise wrote:
>* The height of the individual item lines in the
>Text List has been increased by 25-50%
>(previously, any Text above 14pt fixed and many
>music symbols - usually 24pt - were only
>partially visible). The user can define the size
>of the lines in
At 05:31 AM 2/23/05 -0600, Noel Stoutenburg wrote:
>you could please address the issue of what benefits you
>see arising from your proposal to merging what is currently the list of
>the text subset of the expression tool, with the list of the text tool.
I think merging all the text-like types is
On Feb 23, 2005, at 1:41 AM, shirling & neueweise wrote:
GENERAL
* Text can be assigned to an individual note or measure (as with the
old Expression Tool) or to a page or range of pages (as with the old
Text Tool).
* Once assigned, default positioning of the individual Text can be
altered or ove
Jef
I too, have changes I'd like to see with the text tool, and some of them
are consistent with some of what you propose, but before I comment
further, perhaps you could please address the issue of what benefits you
see arising from your proposal to merging what is currently the list of
the te
The other thing is that I am not convinced that merging the text and the
expression tools is such a good idea. Instead I would prefer to have
some better options for placing text blocks and for handling them in
part extraction. My main requests are:
1) Allow measure attached text blocks to be p
shirling & neueweise wrote:
hi all,
i am submitting a proposal to CODA,
It's a nice list, but I think that getting compact and reliable PS, EPS,
and PDF output would be sufficient for one year's upgrade. If this is
supposed to be a tool for publishing, it has got to be able to output in
the p
hi all,
i am submitting a proposal to CODA, and invite
your additions: please feel free to let me know
if there are things i have missed which you feel
need updating, improvement, implementation, or if
you feel certain points i have made need to be
altered, clarified, or otherwise edited.
dis
27 matches
Mail list logo
