Hello!
Please test preview of SuperCollider code sharing service at http://sccode.org/
Current features:
* code, description, category tagging, uid (example http://sccode.org/1-5 )
* anonymous and private code entries ( accessible only by direct url )
* syntax highlight with clickable (to scdoc) classes and methods
(when available)
* community (reception) tagging ( like "good,loud,whatever" ) and comments
* json access: http://sccode.org/1-5/json
* login using email or social service
Planning features:
* bug fixing )
* JSON API (read-write)
* fixing spelling&orthography
* looking of used classes in code submissions and adding them to
special tag category ( i.e. "class" )
* editing comment
* history of editing code w/diff
* forking
* site performance tweaking&caching
* rating?
* collections?
* syntax checking using code evaluation on server?
* ..?
at some point, after some code cleanup, I will open github repo of
this project to public.
p.s.
Any suggestions, problem reports and comments will be appreciated.
On 6 August 2011 15:15, LFSaw <lf...@lfsaw.de> wrote:
>
> thanks for your insights, felix and thanks to Juan and Roberto.
>
> As for the tips examples I wrote yesterday, I decided to first go with a very simple combination of (a) adding a hashtag (#scTip) to the description and (b) naming the relevant files <filename>.scd such that I can properly open them in sclang as a Document.
> The problem with using a specific file in a gist to provide tags is that the API currently does not support on-site search, i.e. we have to get all gist descriptions (for a specific user) and then search in the descriptions. the file content is not part of the returned json dict.
>
> my more general problem currently is that I am somehow unsure wether or not to trust github... their gist system is all but open source, I don't pay them and all info for all snippets is on their server and only there... unfortunately, I haven't discovered a similar service yet which would provide e.g. a backup download or hosting your own version-controlled snippet system.
> I increasingly liket the idea to have version control, forking, and thelike
>
>
> cheers :-)
> Till
>
> On 02.08.2011, at 15:01, felix wrote:
>
> >
> > this is my personal report of how my own aesthetic/judging system works.
> > just in case it helps anybody or triggers any creative thoughts in other people regarding tagging/metadata of sounds.
>
>
> _______________________________________________
> sc-users 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-users/
> search: http://www.listarc.bham.ac.uk/lists/sc-users/search/