diff --git a/ui (gen4)/features/ui-widgets.js b/ui (gen4)/features/ui-widgets.js
index 7ea07570..1cc97c89 100755
--- a/ui (gen4)/features/ui-widgets.js	
+++ b/ui (gen4)/features/ui-widgets.js	
@@ -964,6 +964,12 @@ module.Dialogs = core.ImageGridFeatures.Feature({
 // XXX EXPERIMENT...
 // 		- which is more logical the generic make.Field(..) or the 
 // 			.makeEditor(..) and friends???
+// 			or should we have both??
+// 			...there is merit in having a "storable" dialog so regardless 
+// 			of the final architecture, it would be logical to have:
+// 				- simple generic Array / Object / JSON constructors...
+// 				- storable "full" format constructors...
+// 				- the make(..) and friends API for custom stuff...
 // 		- how do we handle the ImageGrid context here (i.e. actions)???
 // 			...one way would be to split the fields into two levels, the 
 // 			generic and the domain-specific...