2 Jul
2010
2 Jul
'10
3:37 p.m.
On 2 July 2010 11:46, Philipp Überbacher <hollunder(a)lavabit.com> wrote:
Excerpts from Gabriel M. Beddingfield's message of
2010-07-02 01:57:17 +0200:
The window placement algorithm is done, and I spent quite some time
getting it working satisfactorily performance-wise, within real time
constraints. The idea is based upon window-manager window-placement,
but in the distant future - when the app is up and running with a nice
shiny GUI - the user might not ever care nor need to care, that the
boxes that appear simultaneously as notes are played is based upon
window-manager window-placement. I don't think it will be necessary to
place much emphasis on it's origins. It's only that way right now
because I've not evolved my thinking about how to describe it further
than "it's like a window-manager's window-placement" :-)
And what are you referring to as fixed size?
Cheers,
james.
On Thu, 1 Jul 2010, James Morris wrote:
Since most window managers support a 'workspace' concept I guess it's
not a big deal. But who uses xterm? :) And fixed size? What about tiling
window managers? It's like a sequencer in that the user will
be able to create rhythmic
patterns which lack pitch and velocity data, and almost like an
arpeggiator in that it will automatically generate the pitch and
velocity data from an algorithm - and unlike either a sequencer or
arpegiattor, it uses a 2d window-placement like algorithm to generate
pitch/velocity (mapping these to x/y).
The more I think about this... the more fun it sounds.
Have you considered doing an MDI interface? This way you
can go back to spamming windows... but it stays contained in
your applications MainWindow.