Thursday, April 23, 2009

04/23

8:10 - logged on
  • continue with hazmat udl
    • running load-one repeatedly
    • run dev-prep-data
  • 9:24 - loaded in
  • start on EventHazmatBk and jsfs
  • change model (hopefully only Po's)
  • _OR_ understand MethodExpression (RiscsBackingObject.buildMethodExpression)
  • _OQ_ what is the "key" attribute in the property element supposed to do (not reinsert records?)
  • _OQ_ using the key attribute on the object element reinserts records
    • only when it's combined with another key attribute in a property element
  • _OQ_ Responder.responderType supposed to be a lookup (not a string)?
  • _TODO_ make reference point types hierarcical 
  • spoke w/ Scott

Wednesday, April 22, 2009

04/22

7:00 - signed on
  • event->location
    • fixed bug in event_detail_section.jsff because I couldn't even navigate to event->location
    • changed location.jsff to use new dynamic list of values
    • the above step required me to change the code of locations (list_of_values.xml)
    • overloaded method RiscsElFunctions.lookupSelectItems
    • above attempt resulted in failure of webapp load
    • changed overloaded method to lookupSelectItems2
    • ignore location specific jsff for now
    • added surface lookups to data load (lookups/surface_types.xml)
  • address
    • spoke w/ Dan about address change to strings
  • 9:45
  • event->location
    • implementing EventLocationBk
    • added dynamic toolbar stuff to RiscsBackingObject
  • eclipse
    • validation model -> takes forever!!!
  • event->location
    • EventDetailBaseBk.save is throwing NullPointer because "Work Queue" isn't live
10:55 - signed off
11:25 - signed on
  • event->location
    • modified EventPo (nothing from the event->location screen was configured to persist)
      • used OneToOne in Event->eventLocation.  I did this because the database model would have to be changed otherwise.  This is different than the others I've encountered.
    • modified event_tables.sql and ran dev-prep-data
    • encountered unknown situation
        • the save button submits doesn't populate my bean
        • I mistakenly thought this had something to do with the fact that the save button method wasn't using the same backing bean as the input fields I expected to be populated.
        • To solve that issue, I mapped the EvenBk to EventCurrentBk which would be the bean that the save method uses.
          • this is throwing a NPE
          • realized my mistake was that I hadn't finished the jsf to reference my bean in the input fields and went back to orig.  However, it might be good to still use this approach if we can.
    • 1:07 - checked in this code
    • adding to events.xml (location stuff and reference points)
  • 2:00-3:00 - started chatting w/ Dan (and later Scott) about location, property, vehicle, etc.
    • Scott will make the model changes and we'll check back and discuss later (possibly today - possibly in the morning)
  • event->responders
    • Q for Scott/Dan
      • manage responders popup duplicates the table.  I suggest 
        • pull the table out of the popup
        • move the new button onto the main screen
        • remove "manage ..." button from main screen
        • use edit button to edit
      • same issue as above with event->hazmats
      • should there ever be narratives (or just notes)?
  • event->hazmat
    • TODOs:
      • create hazmat udl
      • create hazmat backing bean
      • modify hazmat jsf
3:30 signed off
8ish and 9:30ish checked for skype message, but found none

Tuesday, April 21, 2009

key codes

_OQ_ = outstanding question
_AQ_ = answered question
_OR_ = outstanding research
_CR_ = completed research
_TODO_ = duh
_SUG_ = suggestions