Hi all,

I'm working on allowing "split view" mode in QuteCsound. It's now
somewhat implemented in current svn, (it might eat your files... well,
hopefully not, but be careful...), but I'm writing to ask for ideas
and feedback about the implementation. Currently, when you select
split mode, the csd is parsed and split into all the different
components,including orc, sco, CsOptions, Binary embedded files, etc.
However, it seems to me it's not very clear what you are editing since
there are so many possible sections. I'm attaching a screenshot, so
let me know your thoughts.

BTW, this new change also allows editing the ordinary score within a
csd file just like a live event sheet (even with live triggering and
python processing).

Cheers,
Andres

hi andrés -

wow - this looks really really promising! can you make possible in the
split view to hide some of the parts? for instance, just see the orc
when working on the orc, or just see the score when performing?

ways ahead ... =)

best -

	joachim


Am 18.02.2011 10:57, schrieb Andres Cabrera:
> Hi all,
> 
> I'm working on allowing "split view" mode in QuteCsound. It's now
> somewhat implemented in current svn, (it might eat your files... well,
> hopefully not, but be careful...), but I'm writing to ask for ideas
> and feedback about the implementation. Currently, when you select
> split mode, the csd is parsed and split into all the different
> components,including orc, sco, CsOptions, Binary embedded files, etc.
> However, it seems to me it's not very clear what you are editing since
> there are so many possible sections. I'm attaching a screenshot, so
> let me know your thoughts.
> 
> BTW, this new change also allows editing the ordinary score within a
> csd file just like a live event sheet (even with live triggering and
> python processing).
> 
> Cheers,
> Andres
> 
> 
> 
> ------------------------------------------------------------------------------
> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> 
> 
> 
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/list

Hi,

Yes, that's the idea. I'm just worried right now about how to know
what you are editing since there are so many panels...

Cheers,
Andres

On Fri, Feb 18, 2011 at 10:56 AM, joachim heintz  wrote:
> hi andrés -
>
> wow - this looks really really promising! can you make possible in the
> split view to hide some of the parts? for instance, just see the orc
> when working on the orc, or just see the score when performing?
>
> ways ahead ... =)
>
> best -
>
>        joachim
>
>
> Am 18.02.2011 10:57, schrieb Andres Cabrera:
>> Hi all,
>>
>> I'm working on allowing "split view" mode in QuteCsound. It's now
>> somewhat implemented in current svn, (it might eat your files... well,
>> hopefully not, but be careful...), but I'm writing to ask for ideas
>> and feedback about the implementation. Currently, when you select
>> split mode, the csd is parsed and split into all the different
>> components,including orc, sco, CsOptions, Binary embedded files, etc.
>> However, it seems to me it's not very clear what you are editing since
>> there are so many possible sections. I'm attaching a screenshot, so
>> let me know your thoughts.
>>
>> BTW, this new change also allows editing the ordinary score within a
>> csd file just like a live event sheet (even with live triggering and
>> python processing).
>>
>> Cheers,
>> Andres
>>
>>
>>
>> ------------------------------------------------------------------------------
>> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
>> Pinpoint memory and threading errors before they happen.
>> Find and fix more than 250 security defects in the development cycle.
>> Locate bottlenecks in serial and parallel code that limit performance.
>> http://p.sf.net/sfu/intel-dev2devfeb
>>
>>
>>
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>
> ------------------------------------------------------------------------------
> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel
>

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/l

don't worry, i'd say. or give option to make user-defined colours, for
instance the orc panel green with red points, and the score pink with
yellow stripes ...
(sorry ...=)
	joachim

Am 18.02.2011 12:50, schrieb Andres Cabrera:
> Hi,
> 
> Yes, that's the idea. I'm just worried right now about how to know
> what you are editing since there are so many panels...
> 
> Cheers,
> Andres
> 
> On Fri, Feb 18, 2011 at 10:56 AM, joachim heintz  wrote:
>> hi andrés -
>>
>> wow - this looks really really promising! can you make possible in the
>> split view to hide some of the parts? for instance, just see the orc
>> when working on the orc, or just see the score when performing?
>>
>> ways ahead ... =)
>>
>> best -
>>
>>        joachim
>>
>>
>> Am 18.02.2011 10:57, schrieb Andres Cabrera:
>>> Hi all,
>>>
>>> I'm working on allowing "split view" mode in QuteCsound. It's now
>>> somewhat implemented in current svn, (it might eat your files... well,
>>> hopefully not, but be careful...), but I'm writing to ask for ideas
>>> and feedback about the implementation. Currently, when you select
>>> split mode, the csd is parsed and split into all the different
>>> components,including orc, sco, CsOptions, Binary embedded files, etc.
>>> However, it seems to me it's not very clear what you are editing since
>>> there are so many possible sections. I'm attaching a screenshot, so
>>> let me know your thoughts.
>>>
>>> BTW, this new change also allows editing the ordinary score within a
>>> csd file just like a live event sheet (even with live triggering and
>>> python processing).
>>>
>>> Cheers,
>>> Andres
>>>
>>>
>>>
>>> ------------------------------------------------------------------------------
>>> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
>>> Pinpoint memory and threading errors before they happen.
>>> Find and fix more than 250 security defects in the development cycle.
>>> Locate bottlenecks in serial and parallel code that limit performance.
>>> http://p.sf.net/sfu/intel-dev2devfeb
>>>
>>>
>>>
>>> _______________________________________________
>>> Csound-devel mailing list
>>> Csound-devel@lists.sourceforge.net
>>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
>> ------------------------------------------------------------------------------
>> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
>> Pinpoint memory and threading errors before they happen.
>> Find and fix more than 250 security defects in the development cycle.
>> Locate bottlenecks in serial and parallel code that limit performance.
>> http://p.sf.net/sfu/intel-dev2devfeb
>> _______________________________________________
>> Csound-devel mailing list
>> Csound-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/csound-devel
>>
> 
> ------------------------------------------------------------------------------
> The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
> Pinpoint memory and threading errors before they happen.
> Find and fix more than 250 security defects in the development cycle.
> Locate bottlenecks in serial and parallel code that limit performance.
> http://p.sf.net/sfu/intel-dev2devfeb
> _______________________________________________
> Csound-devel mailing list
> Csound-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/csound-devel

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net
https://list

Hello,

I agree with Jim Aikins idea, that it is important good to have big working area but I personally like the split-view possibility, like when workind befor with kate (KDE Advanced Text Editor), I mostly had a split view - lower one for score and upper for some instrument. Very Handy.

Also the table-like score format seems absolutely great!

greetings,
tarmo

On Friday 18 February 2011 11:57:09 Andres Cabrera wrote:
> Hi all,
> 
> I'm working on allowing "split view" mode in QuteCsound. It's now
> somewhat implemented in current svn, (it might eat your files... well,
> hopefully not, but be careful...), but I'm writing to ask for ideas
> and feedback about the implementation. Currently, when you select
> split mode, the csd is parsed and split into all the different
> components,including orc, sco, CsOptions, Binary embedded files, etc.
> However, it seems to me it's not very clear what you are editing since
> there are so many possible sections. I'm attaching a screenshot, so
> let me know your thoughts.
> 
> BTW, this new change also allows editing the ordinary score within a
> csd file just like a live event sheet (even with live triggering and
> python processing).
> 
> Cheers,
> Andres
> 

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net

Hi,

Thanks all for the feedback. I think I will use font colors to
indicate which section is being edited. Of course you will be able to
toggle between normal csd view and split view, so don't worry Jim. You
can also already hide/show any panels you need, e.g. to see the score
only. The separator bars can also be dragged to change the size of any
of the sections.

Cheers
Andres

On Fri, Feb 18, 2011 at 8:05 PM, Tarmo Johannes  wrote:
> Hello,
>
> I agree with Jim Aikins idea, that it is important good to have big working area but I personally like the split-view possibility, like when workind befor with kate (KDE Advanced Text Editor), I mostly had a split view - lower one for score and upper for some instrument. Very Handy.
>
> Also the table-like score format seems absolutely great!
>
> greetings,
> tarmo
>
> On Friday 18 February 2011 11:57:09 Andres Cabrera wrote:
>> Hi all,
>>
>> I'm working on allowing "split view" mode in QuteCsound. It's now
>> somewhat implemented in current svn, (it might eat your files... well,
>> hopefully not, but be careful...), but I'm writing to ask for ideas
>> and feedback about the implementation. Currently, when you select
>> split mode, the csd is parsed and split into all the different
>> components,including orc, sco, CsOptions, Binary embedded files, etc.
>> However, it seems to me it's not very clear what you are editing since
>> there are so many possible sections. I'm attaching a screenshot, so
>> let me know your thoughts.
>>
>> BTW, this new change also allows editing the ordinary score within a
>> csd file just like a live event sheet (even with live triggering and
>> python processing).
>>
>> Cheers,
>> Andres
>>
>

------------------------------------------------------------------------------
The ultimate all-in-one performance toolkit: Intel(R) Parallel Studio XE:
Pinpoint memory and threading errors before they happen.
Find and fix more than 250 security defects in the development cycle.
Locate bottlenecks in serial and parallel code that limit performance.
http://p.sf.net/sfu/intel-dev2devfeb
_______________________________________________
Csound-devel mailing list
Csound-devel@lists.sourceforge.net