- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] I will rename FFI-NB to UnifiedFFI

by Torsten Bergmann

Esteban Lorenzano wrote: > People has pointed (and they are right) that the name of the new FFI front-end is misleading. "People" means more than just a single person (me). Glad that I'm not the only one who lamented ;) > So yesterday I was talking with Stef and we think UnifiedFFI (or UFFI, for short) is a >better nameâ¦ and to keep packages prox. to regular FFI I was thinking on rename FFI-NB >packages to FFI-Unifiedâ¦ but maybe is better just to rename them as UFFI or UnifiedFFIâ¦ > what do you think? +1 Given that we already have abbreviations in "NB" and "FFI" it's not a problem to go for "UFFI". But "UnifiedFFI" would be fine as well. Damien Pollet >UniFFIed ? Would be funny, but given that some people already have a problem with "SmallTalk" vs. "Smalltalk" I would not use it. Thanks T. << THE HARDEST PART IN PROGRAMMING IS FINDING PROPER NAMES >>

Jan. 12, 2016

Re: [Pharo-dev] I will rename FFI-NB to UnifiedFFI

by Damien Pollet

UniFFIed ? On 12 January 2016 at 17:40, Max Leske <maxleske(a)gmail.com> wrote: > In order of preference: > > 1. UnifiedFFI > 2. FFI-Unified (suggests that there may be multiple FFI implementations) > 3. UFFI (not clear to me that this is an FFI) > > Cheers, > Max > > > On 12 Jan 2016, at 16:55, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > > > Hi, > > > > People has pointed (and they are right) that the name of the new FFI > front-end is misleading. > > So yesterday I was talking with Stef and we think UnifiedFFI (or UFFI, > for short) is a better nameâ¦ and to keep packages prox. to regular FFI I > was thinking on rename FFI-NB packages to FFI-Unifiedâ¦ but maybe is better > just to rename them as UFFI or UnifiedFFIâ¦ > > what do you think? > > > > Esteban > > > > > > > -- Damien Pollet type less, do more [ | ] http://people.untyped.org/damien.pollet

Jan. 12, 2016

[pharo-project/pharo-core]

by GitHub

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

Jan. 12, 2016

[pharo-project/pharo-core] 980d4d: 50523

by GitHub

Branch: refs/heads/5.0 Home: https://github.com/pharo-project/pharo-core Commit: 980d4dfa986e3db8067a7ffc1f4a7b43f6454f91 https://github.com/pharo-project/pharo-core/commit/980d4dfa986e3db8067a7ffc… Author: Jenkins Build Server <board(a)pharo-project.org> Date: 2016-01-12 (Tue, 12 Jan 2016) Changed paths: M ConfigurationOfFastTable.package/ConfigurationOfFastTable.class/instance/symbolic versions/stable_.st A ConfigurationOfFastTable.package/ConfigurationOfFastTable.class/instance/versions/version082_.st M Morphic-Widgets-FastTable.package/FTBasicItem.class/instance/accessing/calculateChildren.st A Morphic-Widgets-FastTable.package/FTBasicItem.class/instance/accessing/getChildren.st M Morphic-Widgets-FastTable.package/FTExamples.class/class/tree examples/exampleTree1.st M Morphic-Widgets-FastTable.package/FTExamples.class/class/tree examples/exampleTree2.st M Morphic-Widgets-FastTable.package/FTExamples.class/class/tree examples/exampleTreeWithAllItemsFilter.st M Morphic-Widgets-FastTable.package/FTExamples.class/class/tree examples/exampleTreeWithAllItemsSearch.st M Morphic-Widgets-FastTable.package/FTExamples.class/class/tree examples/exampleTreeWithRootFilter.st M Morphic-Widgets-FastTable.package/FTExamples.class/class/tree examples/exampleTreeWithRootSearch.st M Morphic-Widgets-FastTable.package/FTExamples.class/class/tree examples/exampleTreeWithVisibleItemsFilter.st M Morphic-Widgets-FastTable.package/FTExamples.class/class/tree examples/exampleTreeWithVisibleItemsSearch.st A Morphic-Widgets-FastTable.package/FTFunction.class/instance/protocol/disable.st A Morphic-Widgets-FastTable.package/FTFunctionWithField.class/instance/protocol/disable.st A Morphic-Widgets-FastTable.package/FTNilFunction.class/instance/protocol/disable.st M Morphic-Widgets-FastTable.package/FTTableContainerMorph.class/instance/drawing/drawOn_.st M Morphic-Widgets-FastTable.package/FTTableMorph.class/instance/accessing/disableFunction.st M Morphic-Widgets-FastTable.package/FTTableMorph.class/instance/geometry/extent_.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50522.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - scripts/script50523.st R ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50522.st A ScriptLoader50.package/ScriptLoader.class/instance/pharo - updates/update50523.st M ScriptLoader50.package/ScriptLoader.class/instance/public/commentForCurrentUpdate.st A SmartSuggestions.package/SugsGlamourCodeContext.class/README.md A SmartSuggestions.package/SugsGlamourCodeContext.class/definition.st A SmartSuggestions.package/SugsGlamourCodeContext.class/instance/refactoring/sourceTextArea.st A SmartSuggestions.package/SugsGlamourCodeContext.class/instance/selection/selectedClass.st A SmartSuggestions.package/SugsGlamourCodeContext.class/instance/selection/selectedMethod.st A SmartSuggestions.package/extension/GLMRubricSmalltalkTextModel/instance/sugsContext.st R System-BasicCommandLineHandler.package/BasicCommandLineHandler.class/class/accessing/helpDescription.st R System-BasicCommandLineHandler.package/BasicCommandLineHandler.class/instance/printing/printHelp.st R Tools-Test.package/DebuggerTest.class/README.md R Tools-Test.package/DebuggerTest.class/definition.st R Tools-Test.package/DebuggerTest.class/instance/testing/testBasic.st A Tools-Test.package/SpecDebuggerTest.class/README.md A Tools-Test.package/SpecDebuggerTest.class/definition.st A Tools-Test.package/SpecDebuggerTest.class/instance/testing/testBasic.st Log Message: ----------- 50523 17355 Rename DebuggerTest to SpecDebuggerTest https://pharo.fogbugz.com/f/cases/17355 17372 New ConfigurationOfFastTable (see description for details) https://pharo.fogbugz.com/f/cases/17372 17378 Improve command line handler documentation and help https://pharo.fogbugz.com/f/cases/17378 17146 Suggestions in the playground--> Error https://pharo.fogbugz.com/f/cases/17146 http://files.pharo.org/image/50/50523.zip

Jan. 12, 2016

Re: [Pharo-dev] I will rename FFI-NB to UnifiedFFI

by Thierry Goubier

2016-01-12 18:08 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > > 2016-01-12 17:58 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > >> UFFI reminds me UFO which can be translated like Unified Foreign Objects. >> And it has some relation to Alien name. > > > And objects outside image look really like unidentified flying objects. > It's just address, blob of bytes and they fly outside smalltalk world > :) Let's go outside and watch in the starry night UFFI objects ! Thierry

Jan. 12, 2016

Re: [Pharo-dev] I will rename FFI-NB to UnifiedFFI

by Denis Kudriashov

2016-01-12 17:58 GMT+01:00 Denis Kudriashov <dionisiydk(a)gmail.com>: > UFFI reminds me UFO which can be translated like Unified Foreign Objects. > And it has some relation to Alien name. And objects outside image look really like unidentified flying objects. It's just address, blob of bytes and they fly outside smalltalk world

Jan. 12, 2016

Re: [Pharo-dev] I will rename FFI-NB to UnifiedFFI

by Denis Kudriashov

Hi UFFI reminds me UFO which can be translated like Unified Foreign Objects. And it has some relation to Alien name. But maybe it is too much funny name 2016-01-12 16:55 GMT+01:00 Esteban Lorenzano <estebanlm(a)gmail.com>: > Hi, > > People has pointed (and they are right) that the name of the new FFI > front-end is misleading. > So yesterday I was talking with Stef and we think UnifiedFFI (or UFFI, for > short) is a better nameâ¦ and to keep packages prox. to regular FFI I was > thinking on rename FFI-NB packages to FFI-Unifiedâ¦ but maybe is better just > to rename them as UFFI or UnifiedFFIâ¦ > what do you think? > > Esteban > > >

Jan. 12, 2016

Re: [Pharo-dev] I will rename FFI-NB to UnifiedFFI

by Max Leske

In order of preference: 1. UnifiedFFI 2. FFI-Unified (suggests that there may be multiple FFI implementations) 3. UFFI (not clear to me that this is an FFI) Cheers, Max > On 12 Jan 2016, at 16:55, Esteban Lorenzano <estebanlm(a)gmail.com> wrote: > > Hi, > > People has pointed (and they are right) that the name of the new FFI front-end is misleading. > So yesterday I was talking with Stef and we think UnifiedFFI (or UFFI, for short) is a better nameâ¦ and to keep packages prox. to regular FFI I was thinking on rename FFI-NB packages to FFI-Unifiedâ¦ but maybe is better just to rename them as UFFI or UnifiedFFIâ¦ > what do you think? > > Esteban > >

Jan. 12, 2016

I will rename FFI-NB to UnifiedFFI

by Esteban Lorenzano

Hi, People has pointed (and they are right) that the name of the new FFI front-end is misleading. So yesterday I was talking with Stef and we think UnifiedFFI (or UFFI, for short) is a better nameâ¦ and to keep packages prox. to regular FFI I was thinking on rename FFI-NB packages to FFI-Unifiedâ¦ but maybe is better just to rename them as UFFI or UnifiedFFIâ¦ what do you think? Esteban

Jan. 12, 2016

Re: [Pharo-dev] [Moose-dev] Re: [Survey] Forking Operating System Proces in Pharo

by Dimitris Chloupis

Done ! I am very excited about this project. There a lot of gui apps that offer an interface via command line and I am interested into running Pharo on multiple cores. On Tue, 12 Jan 2016 at 17:21, Mariano Martinez Peck <marianopeck(a)gmail.com> wrote: > Dear all, > > This is a simple reminder in case someone missed it. > > I also wanted to thank everybody that already took the time for filling > it! Very much appreciated. > > > > On Sat, Jan 2, 2016 at 10:44 AM, Mariano Martinez Peck < > marianopeck(a)gmail.com> wrote: > >> Dear all, >> >> As I mentioned in the thread "Pharo Consortium Sponsored Development >> Effort" [1] I built a survey about Forking Operating System Processes in >> Pharo. >> >> The idea of the survey is simple: I want to understand what people needs >> the most, which features would be useful, which ones would not, what is >> missing, what is wrong, etc etc etc. As always, since we have limited >> resources, we should optimize them as much as possible. >> >> I count with you so that we can make a roadmap together on this project. >> Please, feel free to forward this survey anywhere where there could be an >> interest. >> >> https://www.surveymonkey.com/r/DHR22TL >> >> Best regards, >> >> [1] >> http://forum.world.st/ANN-Pharo-Consortium-Sponsored-Development-Effort-td4… >> >> -- >> Mariano >> http://marianopeck.wordpress.com >> > > > > -- > Mariano > http://marianopeck.wordpress.com > _______________________________________________ > Moose-dev mailing list > Moose-dev(a)list.inf.unibe.ch > https://www.list.inf.unibe.ch/listinfo/moose-dev >

Jan. 12, 2016