Changes between Version 1 and Version 2 of BalticHistory

Show
Ignore:
Timestamp:
02/12/09 21:23:12 (13 years ago)
Author:
eskil
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • BalticHistory

    v1 v2  
    11== History of Baltic == 
    22 
    3 Development began in 2007, as a small C++ library implementing 
    4 the ZHL16 algorithm, and the frontend was just a simple 
    5 command-line tool. Initially this was all just a mental 
    6 excersise, trying to get a better understanding of deco theory. 
     3Development began in 2007, as a small C++ library implementing the 
     4ZHL16 algorithm, and the frontend was just a simple command-line 
     5tool. Initially this was all just a mental excersise, trying to get a 
     6better understanding of deco theory. 
    77 
    88In late 2007 and early 2008, a gtk+/gnome frontend was written, 
    99complete with profile graphs, compartment loads and pressure 
    1010profile. During this period I got a lot of input from some of the 
    11 local divers, and particularly on the layout of the result by my 
    12 TDI instructor. 
     11local divers, and particularly on the layout of the result by my TDI 
     12instructor. 
    1313 
    14 Sometime in May 2008 I bought a !MacBook Pro and fell in love 
    15 with the thing (despite being a linux user since 94, and 
    16 open-sorce contributor for many many years). I started porting 
    17 the app to MacOS, but still with the gtk+/gnome frontend. 
     14Sometime in May 2008 I bought a !MacBook Pro and fell in love with 
     15the thing (despite being a linux user since 94, and open-sorce 
     16contributor for many many years). I started porting the app to MacOS, 
     17but still with the gtk+/gnome frontend. 
    1818 
    19 However, gtk+/gnome UIs on MacOS don't look good, so in the 
    20 summer of 08 while living back home in Copenhagen for a while, I 
    21 installed the developer package and first looked at bit writing a 
    22 native MacOS app, but my dive buddy urged me to look at the 
    23 iPhone instead. So I started looking at the iPhone SDK, and 
    24 around August, the first version was up and running, a very 
    25 simple UI with a picker for depth & bottom time plus two sliders 
    26 for oxygen and helium content, and the profile was just dumped in 
    27 a textview. 
     19However, gtk+/gnome UIs on MacOS don't look good, so in the summer of 
     2008 while living back home in Copenhagen for a while, I installed the 
     21developer package and first looked at bit writing a native MacOS app, 
     22but my dive buddy urged me to look at the iPhone instead. So I started 
     23looking at the iPhone SDK, and around August, the first version was up 
     24and running, a very simple UI with a picker for depth & bottom time 
     25plus two sliders for oxygen and helium content, and the profile was 
     26just dumped in a textview. 
    2827 
    29 At this point I started focusing on implementing the VPM/B 
    30 algorithm in C++, by reading the fortran implementation by Erik 
    31 C. Baker. Part of this was done by instrumenting the fortran code 
    32 to generate C++ unittest code to validate the output of the 
    33 individual parts of the algorithm. VPM/B was definitely a 
    34 challenge and most harder to understand than Buhlmann's ZHL16, 
    35 but from peoples reports of diving using VPM/B planned dives, I 
    36 felt it was worth it. 
     28At this point I started focusing on implementing the VPM/B algorithm 
     29in C++, by reading the fortran implementation by Erik C. Baker. Part 
     30of this was done by instrumenting the fortran code to generate C++ 
     31unittest code to validate the output of the individual parts of the 
     32algorithm. VPM/B was definitely a challenge and most harder to 
     33understand than Buhlmann's ZHL16, but from peoples reports of diving 
     34using VPM/B planned dives, I felt it was worth it. 
    3735 
    38 By late 08, the implementation was mostly done, and around this 
    39 time I had finally actually bought an iPhone. This meant 
    40 that the UI got more attention again, ie. the profile moved from 
    41 text view into tables, settings moved away from the system 
    42 settings page and into the app using pickers and sliders. Luckily 
    43 a friend of mine is a Apple UI designer, and he gave a lot of 
    44 good suggestions on best and most common-place iPhone UI design 
    45 choices, such as use of tables and sections, editing and input 
    46 widgets. 
     36[[Image(oldiphoneapp.png)]]  
     37 
     38By end of sumer 08, the implementation was mostly done, and around 
     39this time I had finally actually bought an iPhone. This meant that the 
     40UI got more attention again, ie. the profile moved from text view into 
     41tables, settings moved away from the system settings page and into the 
     42app using pickers and sliders. Luckily a friend of mine is a Apple UI 
     43designer, and he gave a lot of good suggestions on best and most 
     44common-place iPhone UI design choices, such as use of tables and 
     45sections, editing and input widgets. 
    4746 
    4847I'm not a CCR diver myself (plan to be some day...), but one of 
     
    5251would bring the app around with me on a few dive trips, and have 
    5352random boat-buddies try it to see what they thought, and what how 
    54 the UI worked for them. 
     53the UI worked for them.   
    5554 
    5655Finally the last bells and wistles like bookmarks and such were 
    57 added, and the app went to the !AppStore. 
     56added, and the app went to the !AppStore.   
    5857 
    5958