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

GarageGlorp

by Stephane Ducasse

Hi for a tutorial I wanted to load Glorp in Pharo 60 as described in the Glorp doc. Metacello new smalltalkhubUser: 'DBXTalk' project: 'Garage'; configuration: 'GarageGlorp'; version: #stable; load. I get an error stating that The symbolic version stable is not defined in the configuration for the ... for the platform. I changed the loading instruction to Metacello new smalltalkhubUser: 'DBXTalk' project: 'Garage'; configuration: 'GarageGlorp'; version: '0.2'; load. And it seems to work. May be we should publish a symbolic version for pharo 60. I do not think that I have commit right. Stef

April 29, 2017

Re: [Pharo-dev] Smalltalk Internet Browser

by askoh

Let me clarify that this browser is to enhance software development and not for mainstream use - at least not yet. Imagine have the full power of Smalltalk IDE while browsing the internet. I click on a photo and run image processing on it to see if it is natural or artificial, recognize objects or people, etc. I can have my own algorithm to suppress ads or popups. I can invent and test security models. I can download and upload from within the environment. I can search the environment and web at the same time. Indeed, Smalltalk lacks many technologies. But internet technologies are so so important we must have them ASAP. Having a GOAL to create a Smalltalk native Internet Browser (SIB) inside the environment will ensure we are not left behind. The synergy (IDE+SIB) will bring software development to the next level. Again it's something Smalltalk can pioneer. Every Smalltalk application will be web enabled automatically. Javascript is popular because it is embedded into all internet browsers. Google intentionally embed Dart into Chrome. We can have Smalltalk in SIB. SIB will improve Smalltalk programming productivity. We start out by embedding Chrome inside the IDE. Make them communicate well. We then port bit by bit to Smalltalk based on needs and priorities. All the best, Aik-Siong Koh -- View this message in context: http://forum.world.st/Smalltalk-Internet-Browser-tp4944879p4944902.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 29, 2017

Re: [Pharo-dev] Smalltalk Internet Browser

by H. Hirzel

And for simple HTML pages this might be interesting https://github.com/HPI-SWA-Teaching/Scamper (8 contributors, 380 commits) On 4/29/17, Denis Kudriashov <dionisiydk(a)gmail.com> wrote: > Hi. > > I remember Esteban integrated Chrome into Pharo. Would be interesting to > know details. > > 2017-04-29 8:58 GMT+02:00 Nicolas Cellier < > nicolas.cellier.aka.nice(a)gmail.com>: > >> >> >> 2017-04-29 4:11 GMT+02:00 askoh <askoh(a)askoh.com>: >> >>> Being connected to the internet is going to be a necessity for any piece >>> of >>> software in the immediate future. So every Smalltalk development >>> environment >>> or application should have that capability as default. To push that >>> envelop, >>> every image should have a Smalltalk native Internet Browser. By >>> developing >>> that Internet Browser, we are demonstrating the power of Smalltalk. >>> There >>> is >>> no reason why Smalltalk cannot be as intimate to the World Wide Web as >>> Javascript. We can have the IDE in Smalltalk, Internet Browser in >>> Smalltalk >>> and a WWW language in Smalltalk. As is uniquely Smalltalk, every bit of >>> code >>> is visible, modifiable and debuggable. This supped up environment will >>> grow >>> and grow to be a full OS. >>> >>> How can we gather the relevant Smalltalk code and necessary plugins to >>> make >>> an Internet Browser? I remember Croquet had internet browser and video >>> player. What is missing? >>> >>> All the best, >>> Aik-Siong Koh >>> >>> >>> >> html5, javascript, etc... Good luck! >> What is the size of teams for building Firefox, Safari or Edge? >> Just browse https://github.com/mozilla for curiosity >> For example, just the core: https://github.com/mozilla/gecko-dev >> Not sure that the million $ that Tim is asking regularly would bring us >> any close to those references. >> You'll have to implement a bunch of technologies... At least, the good >> point is that it would make sure that we have a truly open smalltalk ;) >> >> >> >>> >>> -- >>> View this message in context: http://forum.world.st/Smalltal >>> k-Internet-Browser-tp4944879.html >>> Sent from the Pharo Smalltalk Developers mailing list archive at >>> Nabble.com. >>> >>> >> >

April 29, 2017

Re: [Pharo-dev] IMPORTANT: iceberg home changed

by Damien Pollet

the reason that SBA exists is to get ISBN numbers for the books. It's an adhoc editor like Apress or O'Reilly, if you will. And it was created at the time of Squeak by Example, so probably a bit before Pharo. On 29 April 2017 at 03:04, Ben Coman <btc(a)openinworld.com> wrote: > > On Fri, Apr 28, 2017 at 11:07 PM, Dimitris Chloupis <kilon.alios(a)gmail.com > > wrote: > >> Why not make a Pharo team , we already have one for the books which also >> has a weird name "square bracker associates" , >> > > I don't think its weird. Square brackets "[ ]" to delineate blocks of > code is one thing that distinguishes Smalltalk from those weird cult of > curly brace "{ }" !! > > cheers -ben > > >> we should make a pharo team and put all the repos there so people can >> find them in one place >> >> On Fri, Apr 28, 2017 at 11:31 AM Esteban Lorenzano <estebanlm(a)gmail.com> >> wrote: >> >>> Hi, >>> >>> not really, but we want to promote pharo related stuff with the pharo >>> prefix on the organisations (and those who in someway will fall under our >>> umbrella).. >>> >>> pharo-project -> core pharo >>> pharo-vcs -> iceberg, libgit2 bindings, in the future: an iceberg page, >>> maybe other backends. >>> pharo-graphics -> block/brick and upcoming graphical cool stuff >>> pharo-gtools -> gtools + glamour, etc. >>> pharo-nosql -> voyage family >>> pharo-? -> I donât know, whatever >>> >>> in the future, with the upcoming versions of iceberg + bootstrap, >>> projects like iceberg, gtools, etc. will be âsubtreesâ of pharo-core so is >>> good to have them well organised. >>> >>> of course people are free to name their projects/organisation as they >>> want, but I was trying to figure out a way for *us* :) >>> (and since is very easy to change, we could just reorganise everything >>> under pharo-project if we decide to put everything in just one repository). >>> >>> Esteban >>> >>> >>> On 28 Apr 2017, at 10:11, Stephane Ducasse <stepharo.self(a)gmail.com> >>> wrote: >>> >>> esteban do we have a naming convention on github? >>> pharo-xxx? >>> >>> Stef >>> >>> On Thu, Apr 27, 2017 at 5:51 PM, Esteban Lorenzano <estebanlm(a)gmail.com> >>> wrote: >>> >>>> As part of our work for release, I changed the home of Iceberg into his >>>> own place: https://github.com/pharo-vcs/iceberg >>>> >>>> So, now to install you will need: >>>> >>>> Metacello new >>>> baseline: 'Iceberg'; >>>> repository: 'github://pharo-vcs/iceberg:dev-0.4'; >>>> load. >>>> >>>> I also uploaded a Configuration to the *catalog>http://catalog.pharo. >>>> org*, so you can load while >>>> doing the transition. >>>> >>> >>> >>> > -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

April 29, 2017

Re: [Pharo-dev] Smalltalk Internet Browser

by Denis Kudriashov

Hi. I remember Esteban integrated Chrome into Pharo. Would be interesting to know details. 2017-04-29 8:58 GMT+02:00 Nicolas Cellier < nicolas.cellier.aka.nice(a)gmail.com>: > > > 2017-04-29 4:11 GMT+02:00 askoh <askoh(a)askoh.com>: > >> Being connected to the internet is going to be a necessity for any piece >> of >> software in the immediate future. So every Smalltalk development >> environment >> or application should have that capability as default. To push that >> envelop, >> every image should have a Smalltalk native Internet Browser. By developing >> that Internet Browser, we are demonstrating the power of Smalltalk. There >> is >> no reason why Smalltalk cannot be as intimate to the World Wide Web as >> Javascript. We can have the IDE in Smalltalk, Internet Browser in >> Smalltalk >> and a WWW language in Smalltalk. As is uniquely Smalltalk, every bit of >> code >> is visible, modifiable and debuggable. This supped up environment will >> grow >> and grow to be a full OS. >> >> How can we gather the relevant Smalltalk code and necessary plugins to >> make >> an Internet Browser? I remember Croquet had internet browser and video >> player. What is missing? >> >> All the best, >> Aik-Siong Koh >> >> >> > html5, javascript, etc... Good luck! > What is the size of teams for building Firefox, Safari or Edge? > Just browse https://github.com/mozilla for curiosity > For example, just the core: https://github.com/mozilla/gecko-dev > Not sure that the million $ that Tim is asking regularly would bring us > any close to those references. > You'll have to implement a bunch of technologies... At least, the good > point is that it would make sure that we have a truly open smalltalk ;) > > > >> >> -- >> View this message in context: http://forum.world.st/Smalltal >> k-Internet-Browser-tp4944879.html >> Sent from the Pharo Smalltalk Developers mailing list archive at >> Nabble.com. >> >> >

April 29, 2017

Re: [Pharo-dev] Smalltalk Internet Browser

by Nicolas Cellier

2017-04-29 4:11 GMT+02:00 askoh <askoh(a)askoh.com>: > Being connected to the internet is going to be a necessity for any piece of > software in the immediate future. So every Smalltalk development > environment > or application should have that capability as default. To push that > envelop, > every image should have a Smalltalk native Internet Browser. By developing > that Internet Browser, we are demonstrating the power of Smalltalk. There > is > no reason why Smalltalk cannot be as intimate to the World Wide Web as > Javascript. We can have the IDE in Smalltalk, Internet Browser in Smalltalk > and a WWW language in Smalltalk. As is uniquely Smalltalk, every bit of > code > is visible, modifiable and debuggable. This supped up environment will grow > and grow to be a full OS. > > How can we gather the relevant Smalltalk code and necessary plugins to make > an Internet Browser? I remember Croquet had internet browser and video > player. What is missing? > > All the best, > Aik-Siong Koh > > > html5, javascript, etc... Good luck! What is the size of teams for building Firefox, Safari or Edge? Just browse https://github.com/mozilla for curiosity For example, just the core: https://github.com/mozilla/gecko-dev Not sure that the million $ that Tim is asking regularly would bring us any close to those references. You'll have to implement a bunch of technologies... At least, the good point is that it would make sure that we have a truly open smalltalk ;) > > -- > View this message in context: http://forum.world.st/ > Smalltalk-Internet-Browser-tp4944879.html > Sent from the Pharo Smalltalk Developers mailing list archive at > Nabble.com. > >

April 29, 2017

Smalltalk Internet Browser

by askoh

Being connected to the internet is going to be a necessity for any piece of software in the immediate future. So every Smalltalk development environment or application should have that capability as default. To push that envelop, every image should have a Smalltalk native Internet Browser. By developing that Internet Browser, we are demonstrating the power of Smalltalk. There is no reason why Smalltalk cannot be as intimate to the World Wide Web as Javascript. We can have the IDE in Smalltalk, Internet Browser in Smalltalk and a WWW language in Smalltalk. As is uniquely Smalltalk, every bit of code is visible, modifiable and debuggable. This supped up environment will grow and grow to be a full OS. How can we gather the relevant Smalltalk code and necessary plugins to make an Internet Browser? I remember Croquet had internet browser and video player. What is missing? All the best, Aik-Siong Koh -- View this message in context: http://forum.world.st/Smalltalk-Internet-Browser-tp4944879.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

April 29, 2017

Re: [Pharo-dev] IMPORTANT: iceberg home changed

by Ben Coman

On Fri, Apr 28, 2017 at 11:07 PM, Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > Why not make a Pharo team , we already have one for the books which also > has a weird name "square bracker associates" , > I don't think its weird. Square brackets "[ ]" to delineate blocks of code is one thing that distinguishes Smalltalk from those weird cult of curly brace "{ }" !! cheers -ben > we should make a pharo team and put all the repos there so people can find > them in one place > > On Fri, Apr 28, 2017 at 11:31 AM Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > >> Hi, >> >> not really, but we want to promote pharo related stuff with the pharo >> prefix on the organisations (and those who in someway will fall under our >> umbrella).. >> >> pharo-project -> core pharo >> pharo-vcs -> iceberg, libgit2 bindings, in the future: an iceberg page, >> maybe other backends. >> pharo-graphics -> block/brick and upcoming graphical cool stuff >> pharo-gtools -> gtools + glamour, etc. >> pharo-nosql -> voyage family >> pharo-? -> I donât know, whatever >> >> in the future, with the upcoming versions of iceberg + bootstrap, >> projects like iceberg, gtools, etc. will be âsubtreesâ of pharo-core so is >> good to have them well organised. >> >> of course people are free to name their projects/organisation as they >> want, but I was trying to figure out a way for *us* :) >> (and since is very easy to change, we could just reorganise everything >> under pharo-project if we decide to put everything in just one repository). >> >> Esteban >> >> >> On 28 Apr 2017, at 10:11, Stephane Ducasse <stepharo.self(a)gmail.com> >> wrote: >> >> esteban do we have a naming convention on github? >> pharo-xxx? >> >> Stef >> >> On Thu, Apr 27, 2017 at 5:51 PM, Esteban Lorenzano <estebanlm(a)gmail.com> >> wrote: >> >>> As part of our work for release, I changed the home of Iceberg into his >>> own place: https://github.com/pharo-vcs/iceberg >>> >>> So, now to install you will need: >>> >>> Metacello new >>> baseline: 'Iceberg'; >>> repository: 'github://pharo-vcs/iceberg:dev-0.4'; >>> load. >>> >>> I also uploaded a Configuration to the *catalog>http://catalog.pharo.org*, >>> so you can load while >>> doing the transition. >>> >> >> >>

April 29, 2017

Re: [Pharo-dev] IMPORTANT: iceberg home changed

by Dimitris Chloupis

And here some info about the HOW TO (teams for Github are named "organisations") https://github.com/blog/674-introducing-organizations On Fri, Apr 28, 2017 at 6:07 PM Dimitris Chloupis <kilon.alios(a)gmail.com> wrote: > Why not make a Pharo team , we already have one for the books which also > has a weird name "square bracker associates" , we should make a pharo team > and put all the repos there so people can find them in one place > > On Fri, Apr 28, 2017 at 11:31 AM Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > >> Hi, >> >> not really, but we want to promote pharo related stuff with the pharo >> prefix on the organisations (and those who in someway will fall under our >> umbrella).. >> >> pharo-project -> core pharo >> pharo-vcs -> iceberg, libgit2 bindings, in the future: an iceberg page, >> maybe other backends. >> pharo-graphics -> block/brick and upcoming graphical cool stuff >> pharo-gtools -> gtools + glamour, etc. >> pharo-nosql -> voyage family >> pharo-? -> I donât know, whatever >> >> in the future, with the upcoming versions of iceberg + bootstrap, >> projects like iceberg, gtools, etc. will be âsubtreesâ of pharo-core so is >> good to have them well organised. >> >> of course people are free to name their projects/organisation as they >> want, but I was trying to figure out a way for *us* :) >> (and since is very easy to change, we could just reorganise everything >> under pharo-project if we decide to put everything in just one repository). >> >> Esteban >> >> >> On 28 Apr 2017, at 10:11, Stephane Ducasse <stepharo.self(a)gmail.com> >> wrote: >> >> esteban do we have a naming convention on github? >> pharo-xxx? >> >> Stef >> >> On Thu, Apr 27, 2017 at 5:51 PM, Esteban Lorenzano <estebanlm(a)gmail.com> >> wrote: >> >>> As part of our work for release, I changed the home of Iceberg into his >>> own place: https://github.com/pharo-vcs/iceberg >>> >>> So, now to install you will need: >>> >>> Metacello new >>> baseline: 'Iceberg'; >>> repository: 'github://pharo-vcs/iceberg:dev-0.4'; >>> load. >>> >>> I also uploaded a Configuration to the *catalog>http://catalog.pharo.org*, >>> so you can load while >>> doing the transition. >>> >> >> >>

April 28, 2017

Re: [Pharo-dev] IMPORTANT: iceberg home changed

by Dimitris Chloupis

Why not make a Pharo team , we already have one for the books which also has a weird name "square bracker associates" , we should make a pharo team and put all the repos there so people can find them in one place On Fri, Apr 28, 2017 at 11:31 AM Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > Hi, > > not really, but we want to promote pharo related stuff with the pharo > prefix on the organisations (and those who in someway will fall under our > umbrella).. > > pharo-project -> core pharo > pharo-vcs -> iceberg, libgit2 bindings, in the future: an iceberg page, > maybe other backends. > pharo-graphics -> block/brick and upcoming graphical cool stuff > pharo-gtools -> gtools + glamour, etc. > pharo-nosql -> voyage family > pharo-? -> I donât know, whatever > > in the future, with the upcoming versions of iceberg + bootstrap, projects > like iceberg, gtools, etc. will be âsubtreesâ of pharo-core so is good to > have them well organised. > > of course people are free to name their projects/organisation as they > want, but I was trying to figure out a way for *us* :) > (and since is very easy to change, we could just reorganise everything > under pharo-project if we decide to put everything in just one repository). > > Esteban > > > On 28 Apr 2017, at 10:11, Stephane Ducasse <stepharo.self(a)gmail.com> > wrote: > > esteban do we have a naming convention on github? > pharo-xxx? > > Stef > > On Thu, Apr 27, 2017 at 5:51 PM, Esteban Lorenzano <estebanlm(a)gmail.com> > wrote: > >> As part of our work for release, I changed the home of Iceberg into his >> own place: https://github.com/pharo-vcs/iceberg >> >> So, now to install you will need: >> >> Metacello new >> baseline: 'Iceberg'; >> repository: 'github://pharo-vcs/iceberg:dev-0.4'; >> load. >> >> I also uploaded a Configuration to the *catalog>http://catalog.pharo.org*, >> so you can load while >> doing the transition. >> > > >

April 28, 2017