About the development of SuperCollider

GitHub | 21 Aug 2012 16:14

[supercollider/supercollider] a22df0: scide: save-as dialog - provide separate entries f...

  Branch: refs/heads/master
  Home:   https://github.com/supercollider/supercollider
  Commit: a22df055fd84183cfb710996e1f6f8bdeb41dbbc
      https://github.com/supercollider/supercollider/commit/a22df055fd84183cfb710996e1f6f8bdeb41dbbc
  Author: Tim Blechmann <tim@...>
  Date:   2012-08-21 (Tue, 21 Aug 2012)

  Changed paths:
    M editors/sc-ide/widgets/main_window.cpp

  Log Message:
  -----------
  scide: save-as dialog - provide separate entries for scd and sc files

Signed-off-by: Tim Blechmann <tim@...>

headers

Jonatan Liljedahl | 21 Aug 2012 18:42

Re: [supercollider/supercollider] a22df0: scide: save-as dialog - provide separate entries f...

On 08/21/2012 04:14 PM, GitHub wrote:
>    Branch: refs/heads/master
>    Home:   https://github.com/supercollider/supercollider
>    Commit: a22df055fd84183cfb710996e1f6f8bdeb41dbbc
>        https://github.com/supercollider/supercollider/commit/a22df055fd84183cfb710996e1f6f8bdeb41dbbc
>    Author: Tim Blechmann<tim@...>
>    Date:   2012-08-21 (Tue, 21 Aug 2012)
>
>    Changed paths:
>      M editors/sc-ide/widgets/main_window.cpp
>
>    Log Message:
>    -----------
>    scide: save-as dialog - provide separate entries for scd and sc files

And .schelp would be nice? (And editing .schelp without automatic 
indenting, and with correct syntax highlighting :)

/Jonatan

_______________________________________________
sc-dev mailing list

info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml
archive: http://www.listarc.bham.ac.uk/marchives/sc-dev/
search: http://www.listarc.bham.ac.uk/lists/sc-dev/search/

headers

Tim Blechmann | 21 Aug 2012 18:55

Re: [supercollider/supercollider] a22df0: scide: save-as dialog - provide separate entries f...

>>    Branch: refs/heads/master
>>    Home:   https://github.com/supercollider/supercollider
>>    Commit: a22df055fd84183cfb710996e1f6f8bdeb41dbbc
>>        https://github.com/supercollider/supercollider/commit/a22df055fd84183cfb710996e1f6f8bdeb41dbbc
>>    Author: Tim Blechmann<tim@...>
>>    Date:   2012-08-21 (Tue, 21 Aug 2012)
>>
>>    Changed paths:
>>      M editors/sc-ide/widgets/main_window.cpp
>>
>>    Log Message:
>>    -----------
>>    scide: save-as dialog - provide separate entries for scd and sc files
> 
> And .schelp would be nice? (And editing .schelp without automatic 
> indenting, and with correct syntax highlighting :)

there is already an entry for .schelp.
syntax highlighting for scdoc would definitely be doable and is easier
than for sclang, but not entirely trivial. also, i don't think, we
should use the CodeEditor for it, but implement a separate class, which
shares some functionality with CodeEditor. or we subclass CodeEditor and
have an SclangCodeEditor and SchelpCodeEditor.

but for now that is not a high priority ... unless some people want to
get their hands dirty ;)

cheers, tim

_______________________________________________

(Continue reading)

headers

Jonatan Liljedahl | 21 Aug 2012 18:57

Re: [supercollider/supercollider] a22df0: scide: save-as dialog - provide separate entries f...

On 08/21/2012 06:55 PM, Tim Blechmann wrote:
>>>     Branch: refs/heads/master
>>>     Home:   https://github.com/supercollider/supercollider
>>>     Commit: a22df055fd84183cfb710996e1f6f8bdeb41dbbc
>>>         https://github.com/supercollider/supercollider/commit/a22df055fd84183cfb710996e1f6f8bdeb41dbbc
>>>     Author: Tim Blechmann<tim@...>
>>>     Date:   2012-08-21 (Tue, 21 Aug 2012)
>>>
>>>     Changed paths:
>>>       M editors/sc-ide/widgets/main_window.cpp
>>>
>>>     Log Message:
>>>     -----------
>>>     scide: save-as dialog - provide separate entries for scd and sc files
>>
>> And .schelp would be nice? (And editing .schelp without automatic
>> indenting, and with correct syntax highlighting :)
>
> there is already an entry for .schelp.
> syntax highlighting for scdoc would definitely be doable and is easier
> than for sclang, but not entirely trivial. also, i don't think, we
> should use the CodeEditor for it, but implement a separate class, which
> shares some functionality with CodeEditor. or we subclass CodeEditor and
> have an SclangCodeEditor and SchelpCodeEditor.

Or perhaps just a PlainTextEditor? There are other cases where you may 
have other ascii data files for projects.. Or for editing configuration 
files, etc..

> but for now that is not a high priority ... unless some people want to

(Continue reading)