Deprecated: Assigning the return value of new by reference is deprecated in /home/journler/www/www/blog/wp-includes/cache.php on line 36

Deprecated: Assigning the return value of new by reference is deprecated in /home/journler/www/www/blog/wp-includes/query.php on line 21

Deprecated: Assigning the return value of new by reference is deprecated in /home/journler/www/www/blog/wp-includes/theme.php on line 507

Warning: Cannot modify header information - headers already sent by (output started at /home/journler/www/www/blog/wp-includes/cache.php:36) in /home/journler/www/www/blog/wp-includes/feed-rss2-comments.php on line 2
Comments on: The Proxy Application: Strategies in Software Development http://www.journler.com/blog/2007/06/25/the-proxy-application-strategies-in-software-development/ Phil Dow on Journer on the Net Sat, 04 Feb 2012 17:38:38 +0000 http://wordpress.org/?v=2.2 By: dancingbrook http://www.journler.com/blog/2007/06/25/the-proxy-application-strategies-in-software-development/#comment-70 dancingbrook Tue, 26 Jun 2007 14:57:31 +0000 http://www.journler.com/blog/2007/06/25/the-proxy-application-strategies-in-software-development/#comment-70 Can't wait to see it and wish I had time to offer to help. Can’t wait to see it and wish I had time to offer to help.

]]> By: Phil http://www.journler.com/blog/2007/06/25/the-proxy-application-strategies-in-software-development/#comment-69 Phil Mon, 25 Jun 2007 22:42:16 +0000 http://www.journler.com/blog/2007/06/25/the-proxy-application-strategies-in-software-development/#comment-69 I'm actually still trying to decide if AppleScript will make it into the 1.0 release. I can't do applescript as a proxy in itself because scripting applies to the data model which guides the project as a whole. I think I am, however, going to try to implement script support in some of the proxy applications on a small scale, just to make sure I can get it working before adding it to Lex proper. The problem is Core Data. AppleScript was tough to implement in Journler because scripting is just plain hard. Well, it's doubly hard with a Core Data application because of "ordered" and "unordered sets." AppleScript uses ordered sets, but Core Data deals exclusively with unordered sets. For folks who aren't sure what we're talking about, think of a bag of apples. AppleScript pulls the apples out of the bag in the same order every time. Core Data just gives them to you in any old order. Going back and forth between ordered and unordered data is apparently a pain in the butt. I have to implement a middle man which gets the apples in any old order but puts them into the expected order before handing them off to AppleScript. Thankfully a long time coder has provided a sample project which demonstrates how to do it. I already have my hands on the project and have been going over it. Keep your fingers crossed! I’m actually still trying to decide if AppleScript will make it into the 1.0 release. I can’t do applescript as a proxy in itself because scripting applies to the data model which guides the project as a whole. I think I am, however, going to try to implement script support in some of the proxy applications on a small scale, just to make sure I can get it working before adding it to Lex proper.

The problem is Core Data. AppleScript was tough to implement in Journler because scripting is just plain hard. Well, it’s doubly hard with a Core Data application because of “ordered” and “unordered sets.” AppleScript uses ordered sets, but Core Data deals exclusively with unordered sets. For folks who aren’t sure what we’re talking about, think of a bag of apples. AppleScript pulls the apples out of the bag in the same order every time. Core Data just gives them to you in any old order.

Going back and forth between ordered and unordered data is apparently a pain in the butt. I have to implement a middle man which gets the apples in any old order but puts them into the expected order before handing them off to AppleScript. Thankfully a long time coder has provided a sample project which demonstrates how to do it. I already have my hands on the project and have been going over it.

Keep your fingers crossed!

]]> By: NovaScotian http://www.journler.com/blog/2007/06/25/the-proxy-application-strategies-in-software-development/#comment-68 NovaScotian Mon, 25 Jun 2007 22:12:15 +0000 http://www.journler.com/blog/2007/06/25/the-proxy-application-strategies-in-software-development/#comment-68 Sounds like a very intelligent way to do a design (and that comes from a guy who taught an Advanced Engineering Design grad course at MIT for 8 years and worked for several years on a concept we called "Axiomatic Design"). This latest post convinces me that with the AppleScript savvy you discussed once before (one of your proxy plug-in apps, I surmise), Lex will be a must have for Scripters, replacing Daniel Jalkut's now aging FastScripts and Spotlight for finding stuff. Though FS has an entirely different basis, Lex, with a little scripting, can be made to do everything it does and serve as the basis for your scripting projects. I suspect coders in other languages will feel the same. Looking forward to it. Sounds like a very intelligent way to do a design (and that comes from a guy who taught an Advanced Engineering Design grad course at MIT for 8 years and worked for several years on a concept we called “Axiomatic Design”).

This latest post convinces me that with the AppleScript savvy you discussed once before (one of your proxy plug-in apps, I surmise), Lex will be a must have for Scripters, replacing Daniel Jalkut’s now aging FastScripts and Spotlight for finding stuff. Though FS has an entirely different basis, Lex, with a little scripting, can be made to do everything it does and serve as the basis for your scripting projects. I suspect coders in other languages will feel the same.

Looking forward to it.

]]>