December 2017 - Pharo-dev - lists.pharo.org

Re: [Pharo-dev] New Year Wishlist (2018) ?

by Stephane Ducasse

Hi hilaire what is nice is that we have most of the same wishes ;) On Mon, Dec 25, 2017 at 12:33 PM, Hilaire <hilaire(a)drgeo.eu> wrote: > Oh, you asked for that Esteban :) > > 1. stability > > 2. Tonel is a nice way to export file (its granularity is just right, bravo > Esteban!) and commit to arbitrary repository, experimenting it with DrGeo, > and it is nice to commit code[1] along other data files of the project > (graphics, doc, translation, etc.). Got some an when non ascii characters > were present in the source code, people reported it there. Likely to be > fixed :) > > 3. vectorial interface, oh already on its way > > 4. application builder. Smalltalk/X has a GUI to build a standalone > application, was not able to get it working, but it probably worked at some > time in the past (see screenshot). Such a feature in Pharo will be > fantastic, and likely a kill feature for the ones developing stand alone > application; yes there are still some ;-) > > 5. fulfill the promise of tiny image, aka bootstrap and 4. > > All these wishes are under construction, so likely to happen \o/ > > > I have personal three wishes (beside good health of course), sharing it in > case others are interested to hack on it too: > > A. get DrGeo working on P7, particularly on the bootstrap process. > > B. Build an environment in Pharo to develop simple games, targeted for kids. > There are some teenagers in my school likely to get interested on such > courses. If it could result in standalone games build thanks to wish 4., so > good. > > C. Develop a white board application, easy to extend to add third party > features. The OpenBoard[2] we are using in school are merely goods (can't > get the right tooling to do geometry for example), handwriting is not nice, > hacking on it is super complicated (C++ code), not to mention the building > process. A Pharo based one will be fantastic and much easy to hack. > > > Have a nice Christmas! > > > [1] > http://bazaar.launchpad.net/~drgeo-developers/drgeo/trunk/files/head:/src/ > [2] http://openboard.ch > > > Le 23/12/2017 Ã 17:58, Esteban Lorenzano a Ã©crit : >> >> So, letâs those wishes come! > > > -- > Dr. Geo > http://drgeo.eu >

Dec. 25, 2017

Re: [Pharo-dev] New Year Wishlist (2018) ?

by Torsten Bergmann

A GUI builder is always a nice thing ... and there already was an attempt for Pharo: http://www.squeaksource.com/UIBuilder/ Now marked as "Failed attempt of develop a UI builder for Pharo-Smalltalk. That version only works in Pharo 1.1. Is opened for any developer.". Dont know why it failed ... maybe because the UI (especially with Morphic legacy) is still too shaky are in Pharo. But I guess the order will be/needs to be: - good and stable graphics framework (maybe solved with Bloc) - good and stable standardized widget set (maybe solved with Brick) - then place a UI builder on top of it Bye T. > Gesendet: Montag, 25. Dezember 2017 um 12:33 Uhr > Von: Hilaire <hilaire(a)drgeo.eu> > An: pharo-dev(a)lists.pharo.org > Betreff: Re: [Pharo-dev] New Year Wishlist (2018) ? > > Oh, you asked for that Esteban :) > > 1. stability > > 2. Tonel is a nice way to export file (its granularity is just right, > bravo Esteban!) and commit to arbitrary repository, experimenting it > with DrGeo, and it is nice to commit code[1] along other data files of > the project (graphics, doc, translation, etc.). Got some an when non > ascii characters were present in the source code, people reported it > there. Likely to be fixed :) > > 3. vectorial interface, oh already on its way > > 4. application builder. Smalltalk/X has a GUI to build a standalone > application, was not able to get it working, but it probably worked at > some time in the past (see screenshot). Such a feature in Pharo will be > fantastic, and likely a kill feature for the ones developing stand alone > application; yes there are still some ;-) > > 5. fulfill the promise of tiny image, aka bootstrap and 4. > > All these wishes are under construction, so likely to happen \o/ > > > I have personal three wishes (beside good health of course), sharing it > in case others are interested to hack on it too: > > A. get DrGeo working on P7, particularly on the bootstrap process. > > B. Build an environment in Pharo to develop simple games, targeted for > kids. There are some teenagers in my school likely to get interested on > such courses. If it could result in standalone games build thanks to > wish 4., so good. > > C. Develop a white board application, easy to extend to add third party > features. The OpenBoard[2] we are using in school are merely goods > (can't get the right tooling to do geometry for example), handwriting is > not nice, hacking on it is super complicated (C++ code), not to mention > the building process. A Pharo based one will be fantastic and much easy > to hack. > > > Have a nice Christmas! > > > [1] > http://bazaar.launchpad.net/~drgeo-developers/drgeo/trunk/files/head:/src/ > [2] http://openboard.ch > > Le 23/12/2017 Ã 17:58, Esteban Lorenzano a Ã©critÂ : > > So, letâs those wishes come! > > -- > Dr. Geo > http://drgeo.eu > >

Dec. 25, 2017

Re: [Pharo-dev] New Year Wishlist (2018) ?

by Hilaire

Oh, you asked for that Esteban :) 1. stability 2. Tonel is a nice way to export file (its granularity is just right, bravo Esteban!) and commit to arbitrary repository, experimenting it with DrGeo, and it is nice to commit code[1] along other data files of the project (graphics, doc, translation, etc.). Got some an when non ascii characters were present in the source code, people reported it there. Likely to be fixed :) 3. vectorial interface, oh already on its way 4. application builder. Smalltalk/X has a GUI to build a standalone application, was not able to get it working, but it probably worked at some time in the past (see screenshot). Such a feature in Pharo will be fantastic, and likely a kill feature for the ones developing stand alone application; yes there are still some ;-) 5. fulfill the promise of tiny image, aka bootstrap and 4. All these wishes are under construction, so likely to happen \o/ I have personal three wishes (beside good health of course), sharing it in case others are interested to hack on it too: A. get DrGeo working on P7, particularly on the bootstrap process. B. Build an environment in Pharo to develop simple games, targeted for kids. There are some teenagers in my school likely to get interested on such courses. If it could result in standalone games build thanks to wish 4., so good. C. Develop a white board application, easy to extend to add third party features. The OpenBoard[2] we are using in school are merely goods (can't get the right tooling to do geometry for example), handwriting is not nice, hacking on it is super complicated (C++ code), not to mention the building process. A Pharo based one will be fantastic and much easy to hack. Have a nice Christmas! [1] http://bazaar.launchpad.net/~drgeo-developers/drgeo/trunk/files/head:/src/ [2] http://openboard.ch Le 23/12/2017 Ã 17:58, Esteban Lorenzano a Ã©critÂ : > So, letâs those wishes come! -- Dr. Geo http://drgeo.eu

Dec. 25, 2017

How to restore image upgrade? was New Year Wishlist (2018) ?

by Nicolas Cellier

2017-12-24 2:59 GMT+01:00 Alexandre Bergel <alexandre.bergel(a)me.com>: > My four wishes, in no particular order: > - Better code completion > - Git in Pharo as easy as using Git for other languages > The recipe is easy: turn pharo into a file based edit-compile-run language and expunge those live object burden ;) Let me explain why it's not just trolling. Currently we have to download an image made by a bot. Pharo has gradually lost the power to upgrade the image (it's not new). If we recognize that an image acts like a workspace, and want to let the pull/branch switch/etc work again... IOW going from one point to any other in source code graph and experience the full power of git like any other language, that means, in a live IDE, at least solving those two problems: - changing the tools that are used to upgrade the image (Compiler, MethodDictionary, Array, etc...) - correctly initialize all the states (including stange loops) If pharo has not managed to solve this with a linear one way history (the regularly broken update image option), how do you think this is going to be solved in the more general case? I call this the universal boostrap problem. IMO the logical next step is to separate the IDE (the Inanimate Desintegrated Environment of any other language). Maybe we don't have to bend Pharo too much to git if it does not fit. The goal: as easy might be not that easy. - Bloc on Steroid > - Being able to interrupt any process and endless loop using Cmd-. > > Merry Christmas to all of you! > Alexandre > > > > > On Dec 23, 2017, at 1:58 PM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > > > > Hi everybody, > > > > This looks like a good moment of the year to ask all of you what would > you want to see in Pharo next year. > > Features, improvements, radical changes, etcâ¦. whatever you want. > > > > Of course, this list will not be a roadmap and it does not means we will > implement all of it (as always, time drives our possibilities), but is a > good moment for us a a community to check where we are and where we wan to > go next :) > > > > So, letâs those wishes come! > > > > cheers, > > Esteban > > >

Dec. 24, 2017

[ANN] Phanide - Pharo Native IDE

by Ronie Salgado

Hi, I am going to announce a project that I started in November: Phanide, Pharo Native IDE( currently a File Browser, and a syntax highlighting framework): https://github.com/ronsaldo/phanide [image: ImÃ¡genes integradas 3] [image: ImÃ¡genes integradas 4] As for the UI, I am just copying some existing stuff like Atom (the text editor that I am currently using). Now I have a couple of questions to the mailing list: - In the fast table (used for the tree view): - How do I remove or add single elements without collapsing the whole tree? - In the Rubric text editor, how do I a put an icon (such as a breakpoint for GDB) in a specific line of the text, not in a index of the text? Merry Christmas, Ronie

Dec. 24, 2017

Re: [Pharo-dev] New Year Wishlist (2018) ?

by Dimitris Chloupis

For me 100% bootstrap and anything that helps me minimize the image or completely get rid of it. Second place is a GUI designer. Third place, world peace. Santa hates me :D On Sun, Dec 24, 2017 at 8:14 PM Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Hi. > > Not blocking FFI, please > > 2017-12-23 17:58 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > >> Hi everybody, >> >> This looks like a good moment of the year to ask all of you what would >> you want to see in Pharo next year. >> Features, improvements, radical changes, etcâ¦. whatever you want. >> >> Of course, this list will not be a roadmap and it does not means we will >> implement all of it (as always, time drives our possibilities), but is a >> good moment for us a a community to check where we are and where we wan to >> go next :) >> >> So, letâs those wishes come! >> >> cheers, >> Esteban >> > >

Dec. 24, 2017

Re: [Pharo-dev] New Year Wishlist (2018) ?

by Denis Kudriashov

Hi. Not blocking FFI, please 2017-12-23 17:58 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > Hi everybody, > > This looks like a good moment of the year to ask all of you what would you > want to see in Pharo next year. > Features, improvements, radical changes, etcâ¦. whatever you want. > > Of course, this list will not be a roadmap and it does not means we will > implement all of it (as always, time drives our possibilities), but is a > good moment for us a a community to check where we are and where we wan to > go next :) > > So, letâs those wishes come! > > cheers, > Esteban >

Dec. 24, 2017

Re: [Pharo-dev] New Year Wishlist (2018) ?

by Alistair Grant

Hi Esteban, - https://github.com/pharo-project/pharo-vm/pull/142 Thanks! Alistair On 23 December 2017 at 17:58, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi everybody, > > This looks like a good moment of the year to ask all of you what would you want to see in Pharo next year. > Features, improvements, radical changes, etcâ¦. whatever you want. > > Of course, this list will not be a roadmap and it does not means we will implement all of it (as always, time drives our possibilities), but is a good moment for us a a community to check where we are and where we wan to go next :) > > So, letâs those wishes come! > > cheers, > Esteban

Dec. 24, 2017

Re: [Pharo-dev] New Year Wishlist (2018) ?

by Torsten Bergmann

Hi Esteban, Many things come to mind: vm side ======= - working SSL for all platforms supporting newest TLS - Pharo 64 bit VM for Windows - better and more VM plugins (like the camera plugin which would allow us more collaboration) - threaded vm for non-blocking usage - the VM in a DLL image - cleaning up - Calypso inclusion - Class annotations in the default image - Versionner for editing baselines (instead of manually editing dependencies) - unification of all the quality rules - support for other content types in browser (like highlighted XML, JSON, Js, ...) and managing non-smalltalk project code in git too at the level of projects - better completion - Bloc inclusion of blocs - better widgets and UI - a better catalog ("Index") - a better file browser - filing in/filing out Tonel files also in browser, change sorter, file list (similar to st files) - support for I18N (with tools, maybe binding to lib gettext) general - even more tech talks - more collaboration tools Also: - making a stable but updateable launcher the default install which is working on all platforms so one can use it for Pharo installation and sorting out version or platform specific install issues. If the list is too short then tell me ;) Bye T. > Gesendet: Samstag, 23. Dezember 2017 um 17:58 Uhr > Von: "Esteban Lorenzano" <estebanlm(a)gmail.com> > An: members-consortium(a)pharo.org, "Pharo Development List" <pharo-dev(a)lists.pharo.org> > Betreff: [Pharo-dev] New Year Wishlist (2018) ? > > Hi everybody, > > This looks like a good moment of the year to ask all of you what would you want to see in Pharo next year. > Features, improvements, radical changes, etcâ¦. whatever you want. > > Of course, this list will not be a roadmap and it does not means we will implement all of it (as always, time drives our possibilities), but is a good moment for us a a community to check where we are and where we wan to go next :) > > So, letâs those wishes come! > > cheers, > Esteban >

Dec. 24, 2017

Re: [Pharo-dev] New Year Wishlist (2018) ?

by Alexandre Bergel

My four wishes, in no particular order: - Better code completion - Git in Pharo as easy as using Git for other languages - Bloc on Steroid - Being able to interrupt any process and endless loop using Cmd-. Merry Christmas to all of you! Alexandre > On Dec 23, 2017, at 1:58 PM, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi everybody, > > This looks like a good moment of the year to ask all of you what would you want to see in Pharo next year. > Features, improvements, radical changes, etcâ¦. whatever you want. > > Of course, this list will not be a roadmap and it does not means we will implement all of it (as always, time drives our possibilities), but is a good moment for us a a community to check where we are and where we wan to go next :) > > So, letâs those wishes come! > > cheers, > Esteban

Dec. 24, 2017