- Pharo-users - lists.pharo.org

Re: [Pharo-users] How to take care that the + before a number is ignored
by Roelof Wobben Dec. 2, 2018

Dec. 2, 2018

Op 2-12-2018 om 12:19 schreef Benoit St-Jean via Pharo-users: oke, and if I understand your code files is then the variable that holds the file. Roelof

2 1

Iceberg + BaselinOf + Metacello - how to manage interdependencies ?
by CÃ©drick BÃ©ler Dec. 2, 2018

Dec. 2, 2018

Hi all, Iâm trying to declare a BaselinOf to load lots of Packages. My aim is to have a kind of distribution (so students donât have to load packages). Iâm new to Iceberg + BaselinOf + Metacello. I target only P7. Let's say I want to load Teapot and NeoJSON (development version). Teapot depends on NeoJSON (#stable). So, whatever the order of declaration in the BaselineOfMyProject, Iâd like not to have the following conflict: So is it possible to tell to load : - Teapot , then NeoJSON (updating to NeoJSON the dependancies of Teapot) - NeoJSON (#latest) then Teapot (ignoring the NeoJSON stable of Teapot baseline). I know I risk breaking Teapot (but I donât care :), I want latest NeoJSON. So is it possible to define such constraints ? Iâm aware of that way of loading from Metacello : Metacello new baseline: 'NeoCSV'; repository: 'gitlocal://../../iceberg/svenvc/NeoCSV' ; onConflict: [ :err | err useIncoming ]; onUpgrade: [ :err | err useIncoming ]; load Still, not sure, of the meaning of #useIncoming (#allow #disallow). 1) Does one mean keep/load the latest ? 2) is it possible to launch such Metacello installation from Iceberg ? TIA, CÃ©drick

6 7

old folder names being picked up in settings
by Sanjay Minni Dec. 2, 2018

Dec. 2, 2018

I am using Windows 10 PharoLauncher->Pharo 7.0.0rc1 I find when installing a new image, the folder names of an earlier is picked up by default, as such when loadig packages / cofigurations they are all placed in the earlier directory I saw the names in the settings Pharo->settings->system->local directory Pharo->Settings->Software Configuration Management->Monticell->Local Cache Directory how to resolve ----- cheers, Sanjay -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

1 0

Re: [Pharo-users] How to take care that the + before a number is ignored
by Roelof Wobben Dec. 2, 2018

Dec. 2, 2018

Op 2-12-2018 om 11:55 schreef Benoit St-Jean via Pharo-users: Nope, only the part how I can read the file. Roelof

3 3

Re: [Pharo-users] How to take care that the + before a number is ignored
by Roelof Wobben Dec. 2, 2018

Dec. 2, 2018

Op 2-12-2018 om 11:43 schreef Benoit St-Jean via Pharo-users: if you can learn me that. Right now., the input is a method. I think I can do the rest from there

2 1

Re: [Pharo-users] Spec + Graphics?
by Dan Wilczak Dec. 2, 2018

Dec. 2, 2018

Thanks, Sean! I think I've found the adapter you referred to - MorphicTickingWindowAdapter. It seems that TickingSpecWindow and TickingWindowModel would be used in conjunction with it. Cheers, Dan On Fri, Nov 30, 2018 at 11:13 PM Sean P. DeNigris via Pharo-users < pharo-users(a)lists.pharo.org> wrote: > Dan Wilczak wrote > > I'm interested in using Pharo to create a simulation > > Sounds like a cool project! > > > Dan Wilczak wrote > > Can I use Spec for such a thing? > > Yes, for the vanilla parts you described e.g. toolbar > > > Dan Wilczak wrote > > I don't see any way to embed a graphical > > pane in a Spec application > > There is a Morphic adapter, but I don't have an image at hand to give you > more detail. > > > Dan Wilczak wrote > > Bloc and Sparta look very appealing but aren't officially released yet. > > Yes, ATM Morphic is the standard option. Hopefully, Bloc will be ready to > replace it soon. > > > > ----- > Cheers, > Sean > -- > Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html > >

3 2

What is the actual way of managing code in Pharo
by Ichiseki Dec. 1, 2018

Dec. 1, 2018

Hi there, I am trying the new Pharo 7 and a very elemental question arose. What I should use to manage my code? Monticello Metacello Iceberg It seems I am quite confused regarding the role of each of these tools. Documentation, I am afraid, does not apply to Pharo 7. The chapters covering Monticello and Metacello in Deep in to Pharo, are still relevant in Pharo 7? Please I need profound and detailed help on this. Thanks so much best Ichi -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

4 4

Spec + Graphics?
by Dan Wilczak Dec. 1, 2018

Dec. 1, 2018

Hi, I'm interested in using Pharo to create a simulation with animated 2-D graphical output. The user can start/stop the simulation, change display modes, zoom in and out, and change various settings during operation. That means that, in addition to a graphical pane, I need a menu bar or maybe a panel of buttons which create popup windows. Can I use Spec for such a thing? I don't see any way to embed a graphical pane in a Spec application. The Spec examples don't include one either. Secondly, if it is possible to use Spec, what would you recommend for the graphics? Bloc and Sparta look very appealing but aren't officially released yet. The long-term futures of the other options aren't clear to me. Thanks, Dan Wilczak -- Sent from: http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html

2 1

subpackages in P7
by Roelof Wobben Dec. 1, 2018

Dec. 1, 2018

Hello, Right now I have three seperate packages. Project Project-test Project-Actions Is it possible in P7 to have something like this Project ---Â Â Tests ----Â Actions and if so, how to I make it work,

4 5

Loading Metacello with Seaside
by Vitor Medina Cruz Nov. 30, 2018

Nov. 30, 2018

Hello! WIndows 10 here with Pharo 7 32 bits. Here is my baseline: baseline: spec > > <baseline> > > spec for: #'common' do: [ > spec blessing: #'baseline'; > repository: 'gitlab://vitormcruz/employees:master/pharo/'; > > project: 'Magritte3' with: [ spec repository: > 'github://magritte-metamodel/magritte:v3.5.3/source'; > className: > 'ConfigurationOfMagritte3'; > loads: #(Seaside Core) > ]; > > package: 'Employees' with: [ spec requires: #('Magritte3'). > ]; > > group: 'default' with: #('core'); > group: 'core' with: #('Employees') When I execute: Metacello new baseline: #Employees; > repository: > 'gitlab://vitormcruz/employees:master/pharo/'; load: #(core) > I got: "project group, or package named: 'Seaside-Pharo-Development' not found > when used in requires: or includes: field of package: > 'Seaside-Tests-Pharo-Development' for version: baseline of > BaselineOfSeaside3." > It seems there is a problem with Magrite ConfigurationOf, am I correct? Some general information: 1- Using https://github.com/magritte-metamodel/magritte instead /magritte:v3.5.3/ of 'github://magritte-metamodel/magritte:v3.5.3/source don't work; 2- You must provide className otherwise it does no work, even if docs says itis not needed; 3- Metacello fail in ways it is hard to understand what happened; 4- On Pharo 64bits, Iceberg commit fails. <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_cam…> Livre de vÃrus. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_cam…>. <#DAB4FAD8-2DD7-40BB-A1B8-4E2AA1F9FDF2>

2 6