Comments for Genome Studio http://www.genomestudio.net A Collaborative Multiuser Music Sequencer Thu, 17 Jun 2010 17:37:23 +0000 hourly 1 http://wordpress.org/?v=3.0 Comment on About by Genome up and running on the iPad « Genome Studio http://www.genomestudio.net/about/comment-page-1/#comment-313 Genome up and running on the iPad « Genome Studio Thu, 17 Jun 2010 17:37:23 +0000 http://www.genomestudio.net/?page_id=2#comment-313 [...] About [...] [...] About [...]

]]> Comment on Hiatus alert by admin http://www.genomestudio.net/2009/05/hiatus-alert/comment-page-1/#comment-300 admin Sat, 24 Apr 2010 14:35:05 +0000 http://www.genomestudio.net/?p=117#comment-300 There are some big similarities. Haven't tried out Ohmstudio yet, so I can't say how close they are. There are some big similarities. Haven’t tried out Ohmstudio yet, so I can’t say how close they are.

]]> Comment on Hiatus alert by Al http://www.genomestudio.net/2009/05/hiatus-alert/comment-page-1/#comment-299 Al Thu, 08 Apr 2010 08:10:06 +0000 http://www.genomestudio.net/?p=117#comment-299 I wonder how Genome is related to the recently announced Ohmstudio? It looks very similar. I wonder how Genome is related to the recently announced Ohmstudio? It looks very similar.

]]> Comment on Hiatus alert by bleep!BOX, a groovebox app for your iPhone » Blog Archive » What’s next? http://www.genomestudio.net/2009/05/hiatus-alert/comment-page-1/#comment-175 bleep!BOX, a groovebox app for your iPhone » Blog Archive » What’s next? Mon, 17 Aug 2009 12:54:44 +0000 http://www.genomestudio.net/?p=117#comment-175 [...] at most to do, get the same placement in the app store that the quality apps that might have taken 3 months to do. So please tell your friends, tweet, post stuff online, [...] [...] at most to do, get the same placement in the app store that the quality apps that might have taken 3 months to do. So please tell your friends, tweet, post stuff online, [...]

]]> Comment on BleepBOX! screenshots by admin http://www.genomestudio.net/2009/06/bleepbox-screenshots/comment-page-1/#comment-171 admin Fri, 31 Jul 2009 15:38:47 +0000 http://www.genomestudio.net/?p=168#comment-171 libNUI, yeah ( http://www.libnui.net/ ) libNUI, yeah ( http://www.libnui.net/ )

]]> Comment on BleepBOX! screenshots by Christian Moore http://www.genomestudio.net/2009/06/bleepbox-screenshots/comment-page-1/#comment-159 Christian Moore Tue, 30 Jun 2009 11:49:21 +0000 http://www.genomestudio.net/?p=168#comment-159 These are looking very interesting indeed :) This is built in NUI library aye? These are looking very interesting indeed :) This is built in NUI library aye?

]]> Comment on Day 3 learning objective c by Steve High http://www.genomestudio.net/2009/06/day-3-learning-objective-c/comment-page-1/#comment-153 Steve High Fri, 19 Jun 2009 13:44:23 +0000 http://www.genomestudio.net/?p=153#comment-153 The autorelease pool serves as a flushing mechanism, mainly for objects fetched through foundation calls (example: [NSMutableArray arrayWithCapacity:0]) where you yourself are not allocating these objects. When theyre returned to you, they are set to autorelease (this is the Apple standard and anyone who makes such methods should definitely follow it). So basically, anything created and set to autorelease within a pool will be released when the pool is released. So basically its just a memory optomization technique. Exception handling on ObjC is not nearly as useful as in other languages. The stack traces only point you to memory addresses and nothing useful (at least...as far as I can tell). Look up how to enable NSZombie in your code. This will at least give you more insight into those 'BAD_ACCESS' errors. The autorelease pool serves as a flushing mechanism, mainly for objects fetched through foundation calls (example: [NSMutableArray arrayWithCapacity:0]) where you yourself are not allocating these objects. When theyre returned to you, they are set to autorelease (this is the Apple standard and anyone who makes such methods should definitely follow it).
So basically, anything created and set to autorelease within a pool will be released when the pool is released. So basically its just a memory optomization technique.

Exception handling on ObjC is not nearly as useful as in other languages. The stack traces only point you to memory addresses and nothing useful (at least…as far as I can tell). Look up how to enable NSZombie in your code. This will at least give you more insight into those ‘BAD_ACCESS’ errors.

]]> Comment on Thoughts on Objective C by admin http://www.genomestudio.net/2009/06/thoughts-on-objective-c/comment-page-1/#comment-152 admin Thu, 18 Jun 2009 21:44:35 +0000 http://www.genomestudio.net/?p=135#comment-152 Dynamic typing is cool (flash is capable of some pretty extensive dynamic typing). It is most helpful for keeping loosely defined connections between your classes (and enabling easier interprocess communication). However, there's still no reason why [someobj somefunc] couldn't be written as someobj.somefunc. Flash has dynamic typing and works this way. That said, flash is a scripting language and maybe there was some technical reason why objective C chose not to work do this. The thing that seems to really suck about this scheme is that if you mess up a method call (ie, pass the wrong parameter to a method or call a method that doesn't exist) then you get a crash with no ability to find out what line the crash occurred on. Also, no error at compile time. This can be a real pain for debugging. Also, with the retain / release scheme, if you release something you shouldn't have, the crash doesn't always occur until the memory pool is released (which also is a nightmare to debug).. in C/C++, if you release the same memory twice or access a bad pointer you get a crash right away and it's pretty easy to debug. The bugs that are hard to catch are buffer overruns since they don't always cause a crash where you expect. Anyway, I guess I was just kinda hoping that since apple is regarded as being so visionary when it comes to designing devices, that their choice for programming language would offer something over .NET, Java, etc.. My experience is that it has a higher learning curve and is just as crashy, if not more so than other languages I've used. Just look at how many iphone apps crash or leak memory. if the iphone was made by microsoft, apple would be all over that. Instead people pretty much ignore it. Strange how that works. ;) But, enough venting - I'm sure in a week or two I'll be totally comfortable with the language and won't care about it's shortcomings. Dynamic typing is cool (flash is capable of some pretty extensive dynamic typing). It is most helpful for keeping loosely defined connections between your classes (and enabling easier interprocess communication). However, there’s still no reason why [someobj somefunc] couldn’t be written as someobj.somefunc. Flash has dynamic typing and works this way. That said, flash is a scripting language and maybe there was some technical reason why objective C chose not to work do this. The thing that seems to really suck about this scheme is that if you mess up a method call (ie, pass the wrong parameter to a method or call a method that doesn’t exist) then you get a crash with no ability to find out what line the crash occurred on. Also, no error at compile time. This can be a real pain for debugging. Also, with the retain / release scheme, if you release something you shouldn’t have, the crash doesn’t always occur until the memory pool is released (which also is a nightmare to debug).. in C/C++, if you release the same memory twice or access a bad pointer you get a crash right away and it’s pretty easy to debug. The bugs that are hard to catch are buffer overruns since they don’t always cause a crash where you expect. Anyway, I guess I was just kinda hoping that since apple is regarded as being so visionary when it comes to designing devices, that their choice for programming language would offer something over .NET, Java, etc.. My experience is that it has a higher learning curve and is just as crashy, if not more so than other languages I’ve used. Just look at how many iphone apps crash or leak memory. if the iphone was made by microsoft, apple would be all over that. Instead people pretty much ignore it. Strange how that works. ;) But, enough venting – I’m sure in a week or two I’ll be totally comfortable with the language and won’t care about it’s shortcomings.

]]> Comment on Thoughts on Objective C by Dennis http://www.genomestudio.net/2009/06/thoughts-on-objective-c/comment-page-1/#comment-151 Dennis Thu, 18 Jun 2009 17:44:31 +0000 http://www.genomestudio.net/?p=135#comment-151 Objective-c Language is definitely tough to get used to coming from a JAVA/C#/C++ background. In theory, the reason for the strange syntax (basically passing method names as string parameters) is because of Objective C's Dynamic Typing which enables Message passing and forwarding. The syntax is therefore based in the languages roots in Small-talk. Hence, the parsing of method calls happens during run-time , leading to further frustration for developers. It should be noted though, that message passing and dynamic typing can be extremely powerful, especially in mobile apps which, I believe, was the reason for incorporating it into the iphone platform. Objective-c Language is definitely tough to get used to coming from a JAVA/C#/C++ background. In theory, the reason for the strange syntax (basically passing method names as string parameters) is because of Objective C’s Dynamic Typing which enables Message passing and forwarding. The syntax is therefore based in the languages roots in Small-talk. Hence, the parsing of method calls happens during run-time , leading to further frustration for developers. It should be noted though, that message passing and dynamic typing can be extremely powerful, especially in mobile apps which, I believe, was the reason for incorporating it into the iphone platform.

]]> Comment on Hiatus alert by admin http://www.genomestudio.net/2009/05/hiatus-alert/comment-page-1/#comment-138 admin Mon, 01 Jun 2009 18:48:18 +0000 http://www.genomestudio.net/?p=117#comment-138 Cool, thanks Sebastien, you've been very responsive so far ;) I plan on doing a post comparing the two frameworks and the pro's and cons with both. Cool, thanks Sebastien, you’ve been very responsive so far ;) I plan on doing a post comparing the two frameworks and the pro’s and cons with both.

]]>