- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Voronoi diagram

by Alexandre Bergel

Hi! I have just integrated it. I was not sure whether you have finished it or not. Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. On Dec 8, 2013, at 11:02 AM, Yuriy Tymchuk <yuriy.tymchuk(a)me.com> wrote: > Yeah, by the way, is my rectangle packing layout integrated? > > Uko > > On 08 Dec 2013, at 14:36, Alexandre Bergel <alexandre.bergel(a)me.com> wrote: > >> 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. 9, 2013

Re: [Pharo-dev] Query STHub from outside

by Torsten Bergmann

> It doesnât find the teams and their projects When I run (NeoJSONReader fromString: (ZnEasy get: 'http://smalltalkhub.com/hub/users?term=') entity string) size I get only 839, the website says 926 users registered So is the rest for teams? Maybe I should dig into the code of STHub. Thanks for the tip. Thx T.

Dec. 8, 2013

Re: [Pharo-dev] Query STHub from outside

by Stephan Eggermont

Hi Torsten, Just take a look at: http://smalltalkhub.com/mc/StephanEggermont/DeprecationFinder/main It is deliberately rate-limited. It doesnât find the teams and their projects. The API you can find by downloading the SmalltalkHub image from ci. That wants a MongoDB running with default ports Stephan

Dec. 8, 2013

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

by HernÃ¡n Morales Durand

El 08/12/2013 19:04, Torsten Bergmann escribiÃ³: > Hi Hernan, > the problem is not the button - but the missing standard and > standardized descriptions > on the configs... I see. Let's attack the real problem then. > For instance I also write markup docu on my configs (see > ConfigurationOfINIFile) - it > is loadable as a usual config but adds two class side methods: > #documentation > and #tutorialOn: using the <onlineTutorial> pragma. > The documentation is stored as class comment in markdown format on the > ConfigurationOfINIFile class. I use the same description then for the > STHub project page. I am not a big fan of pragmas, but if people is fine with them I can parse the markup. However I imagine that would require a parser preloaded in the image... > If one loads additionally the "PharoOnlineHelp" package afterwards it > will also appear > magically in my Pharo online help as a tutorial. This was my proposal - > but so far it looks > like nobody is really interested. > > Maybe because often this ends in "which syntax" discussions and due to > the lack of > good in image default text display facilities for markup, pier-syntax, ... Please let's take a decision and live with it. The real point is that only a friendly String saying "The selected package does this" would improve usability, specially for newcomers. Do not forget we can just enforce a method in the ConfigurationOf... packageDescription ^ 'My purpose is to blabla' > In general it can be done easily, but we have to agree on some kind of > "common standard" > for configurations and documentation on > - how to describe a package (also the format, either markdown or pier > syntax with http://smalltalkhub.com/#!/~Pier/Pillar > <https://3c.gmx.net/mail/client/dereferrer?redirectUrl=http%3A%2F%2Fsmalltal…>) > - how to name the methods or pragmas that are used > Stef also did something (with Catalog), the ConfigurationOfINIFile for > instance has two supporting > methods: #catalogDescription and #repositoryUrlString. > Still Catalog uses Pier and is not really visible - and STHub does > support markdown by default. Ok, just waiting for a decision here. > As of today I would like to see Pharo moving into the following direction: > - using the configs for describing the help/documentation/package > descriptions > - also tagging with package categories (for instance there are > packages/projects for "database access", others for "parsers", or "games") > - maybe use pier syntax for descriptions (it can be parsed by Pillar > and other formats like HTML, markdown, Latex, ... be generated) > - generate pages like catalog > https://ci.inria.fr/pharo-contribution/job/PharoProjectCatalog/HTML_Report/? > but with a better design and visibility like > "http://packages.pharo.org" > together with a loadable list for the config browser > - when one uploads such a ConfigurationOfMyKillerApp to STHub it > should automagically update the > STHub description (which is currently only possible via the web > interface) > - additional rankings (number of downloads like on STHub, successful > CI builds, member rankings, ...) > - automated verfication > - ... <snip>lot of other ideas</snip> > Bye > T. > *Gesendet:* Sonntag, 08. Dezember 2013 um 22:12 Uhr > *Von:* "HernÃ¡n Morales Durand" <hernan.morales(a)gmail.com> > *An:* "Pharo Development List" <pharo-dev(a)lists.pharo.org> > *Betreff:* Re: [Pharo-dev] It would be too expensive to add a > description for packages in Configuration Browser? > Hi Torsten, > 2013/12/8 Torsten Bergmann <astares(a)gmx.de> > > 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 agree (see attached screenshot). I have added the button but the thing > is: Package can be fetched from the repository, but there is no package > description. There are only textual descriptions of commits. > So anyone see any workaround here? > > > 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" > > Absolutely. Configurations should be certified. > > HernÃ¡n

Dec. 8, 2013

Query STHub from outside

by Torsten Bergmann

Is it possible to query STHub from within the image (so is there a web API to query for available users, projects, project descritions, ...) Thx T.

Dec. 8, 2013

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

by Torsten Bergmann

Dec. 8, 2013

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

by StÃ©phane Ducasse

> I agree (see attached screenshot). I have added the button but the thing is: Package can be fetched from the repository, but there is no package description. There are only textual descriptions of commits. If you have a look at the packages I maintain I added catalog metadata to htem and I generate automatically https://ci.inria.fr/pharo-contribution/job/PharoProjectCatalog/HTML_Report/? Now this would require to load all the configruatiion files in the images and this is not what you want. > > So anyone see any workaround here? What we could do is to extend the catalog builder server to emit STON files in addition to the html one and the browser could just load these files without having to download all the configurationOf. If somebody want to help, the code of the catalog builder is available and the jenkins job up and running here: https://ci.inria.fr/pharo-contribution/job/PharoProjectCatalog/ > > > 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" > > > Absolutely. Configurations should be certified. > > > HernÃ¡n > > > <Configuration browser.png>

Dec. 8, 2013

Re: [Pharo-dev] Smalltalk in a C World

by StÃ©phane Ducasse

> Yes - still alive and kicking. But I'm sure you did not notice since there > are no "big" announcements or advertising for it. > ObjectConnect follows the "time is better invested into technology" strategy. > It is one of the most interesting Smalltalks ever implemented. http://www.objectconnect.com/stmt_overview.htm I like the idea that you can get 50kb applications. Now since this is a closed system and windows-centric. But I like that it shows that Smalltalk does not have to be the image centric way. > > The newest ST/MT 6.3 version (now 64 bit) is from end of November 2013 Now it is not a community thing. :) And the web site stop and 5.6 in 2009. Last time I talk to tarrick he told me that he could control the "no gc in the next 250 frames on PS2" but it was in 1998 :) Stef

Dec. 8, 2013

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

by HernÃ¡n Morales Durand

Hi Torsten, 2013/12/8 Torsten Bergmann <astares(a)gmx.de> > 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 agree (see attached screenshot). I have added the button but the thing is: Package can be fetched from the repository, but there is no package description. There are only textual descriptions of commits. So anyone see any workaround here? > > 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" > > Absolutely. Configurations should be certified. HernÃ¡n

Dec. 8, 2013

Re: [Pharo-dev] Smalltalk in a C World

by Marcus Denker

On 08 Dec 2013, at 21:47, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > On 08 Dec 2013, at 21:44, Torsten Bergmann <astares(a)gmx.de> wrote: > >>> Is Smalltalk/MT still "alive"? >> >> Yes - still alive and kicking. But I'm sure you did not notice since there >> are no "big" announcements or advertising for it. > > For me this is a nice way of saying âits deadâ. I am sure I will not put a link to this at esug.org: http://www.objectconnect.com Webrings? I mean seriously: What does this website communicate? âWe are irrelevant and oldâ. Marcus

Dec. 8, 2013