[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[sc-dev] Towards SC 4
- To: sc-dev@xxxxxxxxxxxxxxxx
- Subject: [sc-dev] Towards SC 4
- From: Josh Parmenter <josh@xxxxxxxxxxxxxxxxx>
- Date: Mon, 11 Nov 2013 08:06:31 -0800
- Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=realizedsound.net; s=default; h=Mime-Version:Content-Transfer-Encoding:To:Date:Message-Id:Content-Type:From:Subject; bh=BNdIm/oOOvS1hTaZ3Put30cK97Gg1gbyRqbNA0Rse2s=; b=Jh2oJaNzytwhA4+F/e/bHIYr4/qSSjt2RP0pk8zK8L7WSj9kyrqtyROBIaZ1q9gh9vLSl/C/wpfrfNMlxW60/gGMVWBjPJysNB+jxqQ1+LpNN4mpYxM6MH1/I2eKecel;
- List-id: SuperCollider developers mailing list <sc-devel.create.ucsb.edu>
- Reply-to: sc-dev@xxxxxxxxxxxxxxxx
- Sender: owner-sc-dev@xxxxxxxxxxxxxxxx
So, with the current state if things being what they are, what are the major changes / major things we want to keep from SC 3 going forward to SC 4?
Breaking backward compat is of course more in the table then not, though anything that does (I think) should be done with good reason. I think a new project should aim to-
- Cleanly deal with future bit changes (64 bit compatibility, and thinking ahead to things we can do to make any future changes easier)
- Would like to keep the basic language and class structure
- build the language as a set if language plugins
- retain Qt and the IDE
As for the overall architecture, I personally could think of reasons to keep the lang / server divide, but also reasons to bring them closer together as SC 2 did... Thoughts?
Also, what strategies can we use to start and grow as cross platform, rather then working it in after the fact?
No time lines yet, but I seriously want to open this can of worms. I would be interested in hearing who might be up for this project, planning it together and setting some timelines and mapping out tasks.
sc-dev mailing list
info (subscription, etc.): http://www.beast.bham.ac.uk/research/sc_mailing_lists.shtml