Hi, I will never thank enough every qx developer for this beautiful framework(s). I began using qx with the original desktop flavor. The amount of code used and subclassed from this original library is the reason why I do not port my code to the qx.web flavor. My dream is :
1) a strong OO support (extensibility and custom widgets in mind) and a rich utilities (IO, properties) like qx.desktop and a 2) a more ligthweight and css friendly like qx.web I want the best of both worlds, and I guess this was the point in the 'next' branch. Am I right? If I continue dreaming.... 3) one solution for desktop/tablet/mobile (now I have to mantain a qx.desktop and a qx.mobile app) Is this the direction in the qx devel future? Regards, (and apologies for my english too) Bernardo -- View this message in context: http://qooxdoo.678.n2.nabble.com/Qx-framework-RoadMap-tp7587754p7587768.html Sent from the qooxdoo mailing list archive at Nabble.com. ------------------------------------------------------------------------------ _______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
