A Person, Artist, Software Engineer, Geologist.

I've been working on my iPad application and ran across an issue that I did not understand how to implement using iOS Core Date.  After following a dead end or two (at my age you get a good feeling when your headed down a dead end) I decided to ask the web for help. Sure enough you could see where others have followed the same paths that I did before learning the "easy" way to solve my problem.  It was nice to see that I was not alone in my original false thinking of what I wanted and that (at least for me) I was able to understand the Core Data method of providing a simple solution. I did not see my final solution right away, there was the "try this code" solution that would not and did not work, the brute force methods that were written about but no code presented and then there was the "you need as sub-query for scanning the child entity........ that was the ticket I needed.  Along with the solution was a explanation of "why" this solution

I've been busy the last couple of weeks.  I've been working on my iPad application and again and I can see light at the end of the tunnel.  On the biggest challenges in it's development for me (besides learning all the different tools and technology) is the flattening out the user interface. By "flattening out" I mean the work flow to 1) make it as fluid as possible with 2) very few dialogs or context shifts.  The end result should be as fluid as possible with the workflow as transparent as possible.  This has been fun.  One problem I had was with the selection of colors.  I could have used a spinner in a popup but did not like that solution.  I ended up using 16 predefined colors that they can select from and placing it right in the setting page.  This prevented a context switch and gave instance feedback.  The limit of 16 is not a problem as the app will be most effective with a limited number of graphic elements.  Solution solved. Got my domain name already