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

Re: [Pharo-dev] Voronoi diagram

by Alexandre Bergel

Hi! I have planned to have some people on having Voronoi in Roassal in March. Alexandre > On 7 Dec 2013, at 13:59, Natalia Tymchuk <natalia.tymchuk(a)unikernel.net> wrote: > > Hello. > I started implementing visualization of Voronoi diagrams and I need to do a lot of operations on the lines and polygons. I have some questions: > Is it implemented somewhere? > Did somebody do something with the Voronoi diagrams? > > Best regards, > Natalia >

Dec. 8, 2013

Re: [Pharo-dev] It would be too expensive to add a description for packages in Configuration Browser?

by StÃ©phane Ducasse

On Dec 8, 2013, at 11:16 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > The reason is simple: when I wrote the config browser > there was no such additional description on the configs itself > and one would have to load the config into the image first. > > Think of 2000 config's (note each is a package) loading in the future when > the config browser opens. This will take ages. I think this is not good > since the app should be responsive. > > Maybe a "show details" button helps when the package is selected. > > > I would rather see: > 1. Either a simple hosted seaside app "Pharo Store" that one can use to > register a config for a specific pharo version (similar like squeakmap) > maybe directly from the STHub interface with description, â¦ Indeed open and downloading all the files containing the configuration does not scale Now having the descriptions in the configuration let us build the catalog on a server > > This app can be queried by the config browser (JSON/XML/Fuel/...) > to display infos on the package, maybe also a rating about downloads, ... > > 2. Or a general mechanism that loads the configs, runs tests and if > OK provides them for the config browser as "yes these config really work" I will ask inria for an engineer to do 1 and 2 > > Bye > T. >

Dec. 8, 2013

Re: [Pharo-dev] It would be too expensive to add a description for packages in Configuration Browser?

by Alain Plantec

> Nobody payed attention to this but this is really nice and supporting self documentation. i said i will weeks ago. I will try today. Alain > > > > <Screen Shot 2013-11-07 at 16.14.26.png> > > > stef

Dec. 8, 2013

Re: [Pharo-dev] It would be too expensive to add a description for packages in Configuration Browser?

by StÃ©phane Ducasse

>> really simple 4 class side methods > > OK, I see that this can be in Pier syntax. No problem for me, but that does mean that weâll need a Pier parser and renderer in the base image, no ? Else tools will not be able to show this, right ? For the description and the keywords this is plain text. After the server is crawling the configurations and generating HTML using Pillar (now it is broken I have to check why). Note also that the fly by help of Nautilus shows this description as shown by guille a while ago. Nobody payed attention to this but this is really nice and supporting self documentation. stef

Dec. 8, 2013

Re: [Pharo-dev] It would be too expensive to add a description for packages in Configuration Browser?

by Torsten Bergmann

The reason is simple: when I wrote the config browser there was no such additional description on the configs itself and one would have to load the config into the image first. Think of 2000 config's (note each is a package) loading in the future when the config browser opens. This will take ages. I think this is not good since the app should be responsive. Maybe a "show details" button helps when the package is selected. I would rather see: 1. Either a simple hosted seaside app "Pharo Store" that one can use to register a config for a specific pharo version (similar like squeakmap) maybe directly from the STHub interface with description, ... This app can be queried by the config browser (JSON/XML/Fuel/...) to display infos on the package, maybe also a rating about downloads, ... 2. Or a general mechanism that loads the configs, runs tests and if OK provides them for the config browser as "yes these config really work" Bye T.

Dec. 8, 2013

Re: [Pharo-dev] It would be too expensive to add a description for packages in Configuration Browser?

by Sven Van Caekenberghe

On 08 Dec 2013, at 09:31, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > really simple 4 class side methods OK, I see that this can be in Pier syntax. No problem for me, but that does mean that weâll need a Pier parser and renderer in the base image, no ? Else tools will not be able to show this, right ?

Dec. 8, 2013

Re: [Pharo-dev] It would be too expensive to add a description for packages in Configuration Browser?

by StÃ©phane Ducasse

On Dec 7, 2013, at 11:46 PM, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > Ok. I am taking a look now, still trying to figure out how Spec manage the layout offsets. Should I commit changes as a Slice in http://smalltalkhub.com/mc/Pharo/Pharo30Inbox/main ? Yes with a bug entry. I will be great liek that I can browse my configruation :) Stef > > HernÃ¡n > > > 2013/12/7 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > > On Dec 7, 2013, at 8:44 PM, HernÃ¡n Morales Durand <hernan.morales(a)gmail.com> wrote: > > > Is there a specific reason why this was not implemented? Is someone working on this? > > We added catalog metadata to configuration now > - the tools should take into account about that > - people should add such metadata to their configuration > > If you modify the package browser to present description it will be in the system > > > Stef > > > See the "Perl Package Manager" for example. > > > > When you launch it, takes some time to update but each item displays the Details and you have an Abstract colum. > > > > Cheers, > > > > HernÃ¡n > > > > > > >

Dec. 8, 2013

Re: [Pharo-dev] It would be too expensive to add a description for packages in Configuration Browser?

by StÃ©phane Ducasse

>> We added catalog metadata to configuration now >> - the tools should take into account about that >> - people should add such metadata to their configuration >> >> If you modify the package browser to present description it will be in the system > > Stef, what is the spec, the API, is there an example config with description in the image already ? really simple 4 class side methods catalogDescription ^ 'Soup is a frameworks for scrapping HTML. It offers a simplified query mechanism to abstract over the XML and HTML structures of a document.' catalogKeywords ^ #(HTML web query scrapping Soup XPath) catalogChangeLog ^ '- Version 1. 4 21/02/2013 migrated to SmalltalkHub [[[ (ConfigurationOfSoup project version: ''1.4'') load ]]] - Version 1.3 adding better stable version. [[[ (ConfigurationOfSoup project version: ''1.3'') load ]]] ' catalogKeyClassesAndExample ^ 'It is composed of some keys classes: - ==SoupElement== is the root of elements that are extracted during the parsing of an HTML document. Contrary to traditional HTML Parser, Soup produces a limited set of elements which approximate the HTML elements but supports querying and extracting information. - Soup. ==Soup== is the main public class of the package. It is the class to interact with as shown by the tests. The best way to get started is to get a soup of html elements using ==Soup class>>fromString:== as follows: [[[ Soup fromString: ''http://www.bedetheque.com/album-105582-BD-Atomium-Express.html'' asUrl retrieveContents ]]] Tests of the ==Soup== class are the place to start to learn the API.' have a look at SOUP

Dec. 8, 2013

Re: [Pharo-dev] Pharo magic

by S Krish

Smalltalk has always been the crucible of inventions... http://www.tomshardware.com/news/alan-kay-steve-jobs-ipad-iphone,10209.html Pharo can take its rightful place in near future, amongst Java and C# to give a credible choice for an interactive development platform. Dynabook with Pharo .. as Kay imagined..? or adapted to be mass produced. I like the thought in mash-up of objects rather than standalone apps in an App Store comment. On Sat, Dec 7, 2013 at 3:22 AM, Marcus Denker <marcus.denker(a)inria.fr>wrote: > > On 07 Dec 2013, at 00:24, Nicolai Hess <nicolaihess(a)web.de> wrote: > > > This seems to be a good place to introduce myself. > > > > Welcome! > > > My Name is Nicolai Hess, > > I follow the squeak (and pharo) community for some years (~10). > > (Not as an *active* member in that time, but a little bit more the last > days:-) > > I am a software developer, most time working with c++ and java. > > Every time I start to dive into smalltalk world (again), > > even if all i have done are bugreports or small bugfixes, > > it impressed me how much more fun it makes. > > > Very nice small fixes :-) Thanks a lot for those! > > > Looking at smalltalks history I was always deeply impressed about all > > its development and *inventions*. > > (And a bit sad, it is not as recognized as it > > could be, and seeing how others again reinventing these things.) > > > > Yes, and it is important that we move the system forward so we are not > out-invented > by the worldâ¦ > > Marcus > > >

Dec. 8, 2013

[pharo-project/pharo-core]

by GitHub

Branch: refs/tags/30632 Home: https://github.com/pharo-project/pharo-core

Dec. 8, 2013