> what are the points you are working on and that would deserve more focus and > help from the community?
I once started with a refactored version of GetText, covered with tests and tools. Code status I reached so far is here: http://www.smalltalkhub.com/#!/~TorstenBergmann/Gettext Idea was to be lean, no dependency on Seaside or others and get a well documented easy to use I18N solution. This would open up the possibility for more internationalized Pharo image and Pharo based apps. Would be nice if this could be completed and become part of our infrastructure to get a wider audience and globally usable applications. Additionally I would like to see: - investigation in the Win Pharo VM for being able to run again as a Windows Service (as it was possible for Squeak) to be able to easily provide, deploy and administrate a web app on Windows - image size management under control (as Philip already suggested) - better support for REST based systems (as Philip already suggested) - modern "Material style" UI (as Philip already suggested) but additionally with better out of the box Spec support and examples for regular widgets (Accordion, draggable Toolbars, calendar widget, date/time picker, ...) - clear rules to not accept undocumented classes/packages in the image And a clear separation in packages between CORE/BASE stuff and TESTS on top. Because TEST are usually only for development and for production/deployment of an app TESTS usually should be thrown out. Christmas list would include: - 64 Bit support - an out of the box Pharo Pi VM + image on the website Bye T.
