Hi Phyo, given the large scope of qooxdoo, there certainly is much to wish or even ask for. ;-)
We both are in touch by email already, so here just some general remarks about the project's directions. qooxdoo is quite a mature framework. As such, many areas need maintenance only sporadically, while great apps can be created (often unparalleled by other frameworks) or kept in production. Other areas obviously would need more effort and technical advancement to always be up-to-date or even state-of-the-art. The needs of qooxdoo users (including our own) have shown to be quite diverse. So best bet is to pick those parts that fit individual requirements best (web, mobile, desktop), and put quality time yourself into improving, if needed. Independent of any specific technical progress of the framework, it became obvious lately that qooxdoo as an open-source project needed a more concise and future-proof infrastructure. The current systems (e.g. homepage, issue tracking, ...) had become hard to maintain, if not a pain, historically being based on solutions that are legacy (Dokuwiki, Bugzilla, etc.). Much of it is also located on proprietary server hardware, requiring maintenance. There is no alternative to fixing those infrastructure parts first. One of the initial steps: qooxdoo-contrib has been revamped, see http://news.qooxdoo.org/qooxdoo-contrib-3-0 . As pointed out there, opening up the systems for easier management and community participation is the way to go. The transition of framework infrastructure (e.g. towards Github) is currently being evaluated and worked on. Such an opened up infrastructure not only technically but organizationally allows for people to engage with the project and for shared responsibilities. At some later time lets catch-up on how that could look like. For now focus is on replacing outdated infrastructure with alternatives (even if intermediate) that are much easier to handle and evolve. Andreas -- Andreas Ecker Project Lead http://qooxdoo.org Von: Phyo Arkar <phyo.arkarl...@gmail.com<mailto:phyo.arkarl...@gmail.com>> Antworten an: qooxdoo-devel <qooxdoo-devel@lists.sourceforge.net<mailto:qooxdoo-devel@lists.sourceforge.net>> Datum: Freitag, 25. September 2015 13:39 An: qooxdoo-devel <qooxdoo-devel@lists.sourceforge.net<mailto:qooxdoo-devel@lists.sourceforge.net>> Betreff: [qooxdoo-devel] Future of Qooxdoo? Since I stumbled upon Saaj's very balanced and awesome writeup http://recollection.saaj.me/article/qooxdoo-next-and-targeting-website-development.html , i am also worry about qooxdoo's direction. Qooxdoo Original goals very good and Decisions are Sound , but back in that day , browsers aren't that powerful enough, i can agree with qooxdoo's Ambition to follow website path . But today , advancement of web techologies , everything has changed. And I believe it is time for Qooxdoo's original Goals to shine. Angular , React , Emberjs , Polymer , they are all trying what qooxdoo did since 2009-2010 . They may have cool animations and stuff But , they are still NO MATCH for qooxdoo's ZeroHTML and Zero CSS way of doing things. QxWeb sucks , totally . I prefer awful JQuery over qxWeb , they are just similar , nothing sexy about it. I agree with saaj that there is no need to follow that path. QxMobile is also very outdated , not ready. None of the qooxdoo's spinoff projects can compare to qxdesktop. Thats why , in http://phwa.be , we avoid qxweb/qxmobile and trying to work everything in qxdesktop with masurable success so far for Mobile Phones too (just the biggest feature of qooxdoo , Virtual List , is tooo slow for mobile when scrolled , thanks to Fixed positioning) . What i wish for qooxdoo in future, ? (more like a dream list) - Scrap qxWeb , qxMobile , merge all possible features for qxMobile into qxdektop . - Add a new layout that support both QxMobile and QxDesktop at the same time. So like Bootstrap/Material Design Light , only need one UI to develop both Mobile and desktop. - Add New CSS capabilities (many are missing , Multiple shadows and many) Pull requests already exist but none of qxdoo devs care about them : https://github.com/qooxdoo/qooxdoo/pull/139 - Allow more Contributor collaboration with guidelines. - A Convert for CSS to Qooxdoo Theme, that alone will make qooxdoo much easier to theme. JUST SCRAP THAT BUGZILLA , nothing good about it. Use Github for issue management , it is more approachable for everyone, make everyone lifes easier. Those will keep Qooxdoo above all others. But Those may be just dreams? Coz Qxdoo is pretty much dead since July. Thanks Phyo.
------------------------------------------------------------------------------
_______________________________________________ qooxdoo-devel mailing list qooxdoo-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
