I ran into a problem with my implementation of FlickableFrame for SIWLExtensions. It turns out that ItemWidgets will block their containing Frame from receiving pointer pressed events. I'm not crystal clear under exactly what circumstances this happens (I believe it is when the pointer is pressed inside of a widget's bounding box), but it is my assessment that flickable frames with widgets are not feasible without lower-level access into SIWL*.
Note, there are ways around this, such as drawing text and images directly onto the frame (i.e. not using StaticText or StaticImage widgets for display) or using a ListFrame (though that's fraught with limitations too). However, unless I can find a way to get around recalculating widget positions every time a layout is drawn, the drawing of Frames is too slow for flicking anyway. This demonstrates the importance of robust event-handling and flexible windowing systems on mobile touch devices, and on tactile devices in general. This is what I'm trying to do with OpenSIWL.
* even as I made that pronouncement I started thinking of a method using a transparent widget covering the drawable area of the frame that intercepts all pointer events and, if they do not match the flick signature, calls the appropriate pointer event handlers on the frame (or rather some other functions that call the handlers, since they're declared protected and final in Frame).