From jcastellanos at umail.ucsb.edu Wed May 3 09:27:15 2006 From: jcastellanos at umail.ucsb.edu (Jorge Castellanos) Date: Wed May 3 09:27:26 2006 Subject: [Tdg] fyi In-Reply-To: References: <444D4ECD.9030501@umail.ucsb.edu> Message-ID: <1B139B11-D42D-4978-A038-5A8D57D9F0DA@umail.ucsb.edu> So... we're meeting today at 2 right? Jorge On Apr 26, 2006, at 2:56 PM, solaris wrote: libsndfile - LPGL lua - MIT (like BSD but more flexible) On Apr 24, 2006, at 3:18 PM, Rama Hoetzlein wrote: > Ok. Wed a 2pm it is. 4th fl. South hall. > > Things of gerenal interest that we will start with: > > - Defining goals > - No boring code reviews. High-level design patterns. > - Cross-platform architectures > - General networking architectures > - Software licensing > - Maintaining code separation from thesis work, work for faculty > and outside paid projects while still being able to build and retain > ownership of a useful platform. > > I will be happy to kick off the first meeting by facilitating > discussion and show a few slides. The first goal is to see if we > have the same goals and resolve potential conflicts. There has been > an interest in software licensing issues, so I can briefly discuss > differences between GPL, LGPL and BSD. > > See ya, > Rama > _______________________________________________ > Tdg mailing list > Tdg@mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg _______________________________________________ Tdg mailing list Tdg@mat.ucsb.edu http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg From rch at umail.ucsb.edu Tue May 9 23:43:13 2006 From: rch at umail.ucsb.edu (Rama Hoetzlein) Date: Tue May 9 23:43:21 2006 Subject: [Tdg] Wed Message-ID: <44618B81.2050909@umail.ucsb.edu> Reminder... Bring a sample of how you'd like the TDG library to start up at 2pm: - Focus mostly on startup calls, rather than the body (i.e. run part) of the example. A template is below. - General enough to cover things you're interested in (i.e. different ways you might want system to start) - Specific enough to describe exactly how system should initialize (i.e. not pseudo-code) - While it appears we are leaning toward a global 'Application' class, there are no real constraints yet. Write what you feel the startup should be. Rama #include "...library..." .. objects user must define to startup .. void main () { .. startup code - be specific, no pseudo-code ... } draw (), MyApp::Draw, run() or MyApp::Run () { .. a few examples, nothing detailed .. } From ljputnam at umail.ucsb.edu Mon May 15 13:29:35 2006 From: ljputnam at umail.ucsb.edu (Lance J. Putnam) Date: Mon May 15 13:29:47 2006 Subject: [Tdg] programming mastery Message-ID: <20060515132935.zearaiu3sok40so4@webaccess.umail.ucsb.edu> I'm thinking at some point we need to agree on some standard coding practices. Maybe this will be a good guide. Most of what I've read in this I can agree with. http://www.lomont.org/Software/CodingConventions/CodeImprovement.pdf Lance -- Lance Putnam Graduate Student Media Arts and Technology / UCSB ljputnam@umail.ucsb.edu From ericnewman at umail.ucsb.edu Wed May 24 10:59:34 2006 From: ericnewman at umail.ucsb.edu (Eric Newman) Date: Wed May 24 22:30:14 2006 Subject: [Tdg] test In-Reply-To: <446C4EAA.7040101@umail.ucsb.edu> References: <446A9F89.6070006@umail.ucsb.edu> <446C4EAA.7040101@umail.ucsb.edu> Message-ID: From ericnewman at umail.ucsb.edu Thu May 25 10:22:19 2006 From: ericnewman at umail.ucsb.edu (Eric Newman) Date: Thu May 25 13:07:00 2006 Subject: [Tdg] test In-Reply-To: <4475413D.7080802@umail.ucsb.edu> References: <446A9F89.6070006@umail.ucsb.edu> <446C4EAA.7040101@umail.ucsb.edu> <4475413D.7080802@umail.ucsb.edu> Message-ID: On Wed, 24 May 2006, Rama Hoetzlein wrote: > Try your TDG test again. It should post automatically. If it relays to me > again I'll talk to Joshua. > > -Rama > > Eric Newman wrote: > >> >> _______________________________________________ >> Tdg mailing list >> Tdg@mat.ucsb.edu >> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > > > From rch at umail.ucsb.edu Tue May 30 23:03:23 2006 From: rch at umail.ucsb.edu (Rama Hoetzlein) Date: Tue May 30 23:02:32 2006 Subject: [Tdg] Wed reminder Message-ID: <447D31AB.80703@umail.ucsb.edu> Hey all.. Reminder of meeting tomorrow: 20 names and a start at the API in your domain.. We can break into groups to work on the APIs together but at least try and bring some name ideas. I'll bring the rendering API so far. -R From jcastellanos at umail.ucsb.edu Wed May 31 16:56:16 2006 From: jcastellanos at umail.ucsb.edu (Jorge Castellanos) Date: Wed May 31 16:56:32 2006 Subject: [Tdg] Re: today's meeting Message-ID: Since the meetings started a few weeks ago, I've noticed a pattern of problems all triggered by the same unresolved aspect of Mint. I'm talking about having a clear understanding of what is the API being written for, for whom , etc. The design decisions so far are motivated by personal goals and not by a common ideal of what is the API to do. I propose to go back and start by defining use cases, use scenarios, etc. That will help in the future, and it will avoid stupid discussions & bad design. For example, the use of "Notifications" (I'm referring to what you called messages today, which is misleading) makes a big big difference. It's not just the fact of locks being used or not. The user interaction model is dramatically changed, and that matters the most in any successful API... I could keep going, but I hope we'll opt for freezing the current development state, and go back to the planning stage, where the project is defined. Hope it makes sense, as it will really avoid many problems, discussions and disagreements in the future. Best Jorge Castellanos From jcastellanos at umail.ucsb.edu Wed May 3 09:27:15 2006 From: jcastellanos at umail.ucsb.edu (Jorge Castellanos) Date: Wed, 3 May 2006 09:27:15 -0700 Subject: [Tdg] fyi In-Reply-To: References: <444D4ECD.9030501@umail.ucsb.edu> Message-ID: <1B139B11-D42D-4978-A038-5A8D57D9F0DA@umail.ucsb.edu> So... we're meeting today at 2 right? Jorge On Apr 26, 2006, at 2:56 PM, solaris wrote: libsndfile - LPGL lua - MIT (like BSD but more flexible) On Apr 24, 2006, at 3:18 PM, Rama Hoetzlein wrote: > Ok. Wed a 2pm it is. 4th fl. South hall. > > Things of gerenal interest that we will start with: > > - Defining goals > - No boring code reviews. High-level design patterns. > - Cross-platform architectures > - General networking architectures > - Software licensing > - Maintaining code separation from thesis work, work for faculty > and outside paid projects while still being able to build and retain > ownership of a useful platform. > > I will be happy to kick off the first meeting by facilitating > discussion and show a few slides. The first goal is to see if we > have the same goals and resolve potential conflicts. There has been > an interest in software licensing issues, so I can briefly discuss > differences between GPL, LGPL and BSD. > > See ya, > Rama > _______________________________________________ > Tdg mailing list > Tdg at mat.ucsb.edu > http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg _______________________________________________ Tdg mailing list Tdg at mat.ucsb.edu http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg From rch at umail.ucsb.edu Tue May 9 23:43:13 2006 From: rch at umail.ucsb.edu (Rama Hoetzlein) Date: Tue, 09 May 2006 23:43:13 -0700 Subject: [Tdg] Wed Message-ID: <44618B81.2050909@umail.ucsb.edu> Reminder... Bring a sample of how you'd like the TDG library to start up at 2pm: - Focus mostly on startup calls, rather than the body (i.e. run part) of the example. A template is below. - General enough to cover things you're interested in (i.e. different ways you might want system to start) - Specific enough to describe exactly how system should initialize (i.e. not pseudo-code) - While it appears we are leaning toward a global 'Application' class, there are no real constraints yet. Write what you feel the startup should be. Rama #include "...library..." .. objects user must define to startup .. void main () { .. startup code - be specific, no pseudo-code ... } draw (), MyApp::Draw, run() or MyApp::Run () { .. a few examples, nothing detailed .. } From ljputnam at umail.ucsb.edu Mon May 15 13:29:35 2006 From: ljputnam at umail.ucsb.edu (Lance J. Putnam) Date: Mon, 15 May 2006 13:29:35 -0700 Subject: [Tdg] programming mastery Message-ID: <20060515132935.zearaiu3sok40so4@webaccess.umail.ucsb.edu> I'm thinking at some point we need to agree on some standard coding practices. Maybe this will be a good guide. Most of what I've read in this I can agree with. http://www.lomont.org/Software/CodingConventions/CodeImprovement.pdf Lance -- Lance Putnam Graduate Student Media Arts and Technology / UCSB ljputnam at umail.ucsb.edu From ericnewman at umail.ucsb.edu Wed May 24 10:59:34 2006 From: ericnewman at umail.ucsb.edu (Eric Newman) Date: Wed, 24 May 2006 10:59:34 -0700 (Pacific Standard Time) Subject: [Tdg] test In-Reply-To: <446C4EAA.7040101@umail.ucsb.edu> References: <446A9F89.6070006@umail.ucsb.edu> <446C4EAA.7040101@umail.ucsb.edu> Message-ID: From ericnewman at umail.ucsb.edu Thu May 25 10:22:19 2006 From: ericnewman at umail.ucsb.edu (Eric Newman) Date: Thu, 25 May 2006 10:22:19 -0700 (Pacific Standard Time) Subject: [Tdg] test In-Reply-To: <4475413D.7080802@umail.ucsb.edu> References: <446A9F89.6070006@umail.ucsb.edu> <446C4EAA.7040101@umail.ucsb.edu> <4475413D.7080802@umail.ucsb.edu> Message-ID: On Wed, 24 May 2006, Rama Hoetzlein wrote: > Try your TDG test again. It should post automatically. If it relays to me > again I'll talk to Joshua. > > -Rama > > Eric Newman wrote: > >> >> _______________________________________________ >> Tdg mailing list >> Tdg at mat.ucsb.edu >> http://zydeco.mat.ucsb.edu/mailman/listinfo/tdg > > > From rch at umail.ucsb.edu Tue May 30 23:03:23 2006 From: rch at umail.ucsb.edu (Rama Hoetzlein) Date: Tue, 30 May 2006 23:03:23 -0700 Subject: [Tdg] Wed reminder Message-ID: <447D31AB.80703@umail.ucsb.edu> Hey all.. Reminder of meeting tomorrow: 20 names and a start at the API in your domain.. We can break into groups to work on the APIs together but at least try and bring some name ideas. I'll bring the rendering API so far. -R From jcastellanos at umail.ucsb.edu Wed May 31 16:56:16 2006 From: jcastellanos at umail.ucsb.edu (Jorge Castellanos) Date: Wed, 31 May 2006 16:56:16 -0700 Subject: [Tdg] Re: today's meeting Message-ID: Since the meetings started a few weeks ago, I've noticed a pattern of problems all triggered by the same unresolved aspect of Mint. I'm talking about having a clear understanding of what is the API being written for, for whom , etc. The design decisions so far are motivated by personal goals and not by a common ideal of what is the API to do. I propose to go back and start by defining use cases, use scenarios, etc. That will help in the future, and it will avoid stupid discussions & bad design. For example, the use of "Notifications" (I'm referring to what you called messages today, which is misleading) makes a big big difference. It's not just the fact of locks being used or not. The user interaction model is dramatically changed, and that matters the most in any successful API... I could keep going, but I hope we'll opt for freezing the current development state, and go back to the planning stage, where the project is defined. Hope it makes sense, as it will really avoid many problems, discussions and disagreements in the future. Best Jorge Castellanos