Guise Framework development is being held back because it currently depends on the legacy URF implementation, and its automatic Ploop conversion to Java.
The biggest roadblock right now is the application definition, which dynamically loads a Java graph from legacy TURF using Ploop. The new URF doesn't (currently?) have anything like constructors, and automatically creating an arbitrary Java graph is probably not a good idea anyway. While considering how to proceed with this, we can take it out altogether and require web.xml to indicate, instead of an <param-name>application</param-name>, an <param-name>application.class</param-name>. That class can do all the implementation for now, sidestepping the format of the configuration file. (JAX-RS does this sort of thing anyway.) We may want to use annotations in the future. The biggest things is to remove the reliance on legacy URF.
We need to switch to Rincl for this anyway. For the meantime maybe we can redo the code to use the latest URF. It shouldn't be too hard.
Themes also use legacy URF, with an intricate structure of selectors. Maybe we can disable themes altogether for the moment. The long-term plan for theming Guise is unclear in after the makeover, anyway.