[Pharo-users] Typing a | character
Hi everybody, I wrote yesterday night on the same topic, and later in the night Sven proposed a solution. I just tried it, but it didn't work. In fact it doen't work on my computer, as can be seen in the attached picture. Has anyone using a computer with a French KB experienced the same problem? What solution is he/she using to declare variables? Regards, Mark
Re: [Pharo-users] Typing a | character
Le 17/02/2017 à 12:13, Mark Neagu a écrit : > Hi everybody, > > I wrote yesterday night on the same topic, and later in the night Sven > proposed a solution. > > I just tried it, but it didn't work. In fact it doen't work on my computer, > as can be seen in the attached picture. > > Has anyone using a computer with a French KB experienced the same problem? > What solution is he/she using to declare variables? > > Regards, > Mark > What is your keyboard layout? azerty? kwerty? bépo? dvorak? -- Cyril Ferlicot http://www.synectique.eu 2 rue Jacques Prévert 01, 59650 Villeneuve d'ascq France signature.asc Description: OpenPGP digital signature
[Pharo-users] Problem load Magritte
Hello, I am getting the error message while trying to load magritte through the Pharo5 Catalog on a Windows machine: "This package depends on the following classes: GRPharoPlatform You must resolve these dependencies before you will be able to load these definitions: GRPharoPlatform>>#magritteAllSubInstancesOf:do: GRPharoPlatform>>#magritteClassNamed: GRPharoPlatform>>#magritteColorClass GRPharoPlatform>>#magritteEvaluatorClassFor: GRPharoPlatform>>#magritteTimeStampClass GRPharoPlatform>>#magritteTimeStampIfAbsent: GRPharoPlatform>>#magritteUniqueObject Select Proceed to continue, or close this window to cancel the operation." If I 'Proceed' I think magritte don't installs correctly since many classes are missing. I couldn't find the project of GRPharoPlatform so that I could install before magritte. Anyone can help? Thanks, Vitor
Re: [Pharo-users] Typing a | character
Hi, I'm probably missing something but have you tried : altgr + 6 ? On my keyboard altgr is the alt on the right of the spacebar: Le ven. 17 févr. 2017 à 12:14, Mark Neagu a écrit : > Hi everybody, > > I wrote yesterday night on the same topic, and later in the night Sven > proposed a solution. > > I just tried it, but it didn't work. In fact it doen't work on my > computer, as can be seen in the attached picture. > > Has anyone using a computer with a French KB experienced the same problem? > What solution is he/she using to declare variables? > > Regards, > Mark
[Pharo-users] Latest Voyage for Pharo4
Hi, I need to test Voyage for a project in development but... installing Voyage on Pharo4 with Seaside already installed (from Pharo4 configuration) produces a broken Seaside installation. Voyage installation installs Seaside-core, which in turn break the installed Seaside. It is strange Seaside is needed by Voyage. Is there a way to get a recent Voyage installed without altering an existing Seaside set up? Thanks Hilaire -- Dr. Geo http://drgeo.eu
Re: [Pharo-users] Latest Voyage for Pharo4
Some more info. Installing the configuration of Voyage from Pharo4 itself also breaks the installed Seaside, which was previously installed from the Pharo4 configuration too. Now when installing the Voyage configuration, it warns about installing Seaside-Core and the conflict with installed version, there are three options: Load, Merge, Cancel. All break the image. I don't see on Voyage configuration a Seaside dependency, so I guess one of its used configurations do so. -- Dr. Geo http://drgeo.eu
Re: [Pharo-users] Issue with Iceberg
Getting the latest unstable VM is a bit mysterious. Where to get it? Is it available here: http://files.pharo.org/vm/pharo/mac/ ? No idea The latest VM on the files.pharo.org is tagged as 6.0-pre. I guess this is not the latest unstable VM... Alexandre > On Feb 15, 2017, at 1:32 PM, Juraj Kubelka wrote: > > You likely need the latest (unstable) VM because the stable one has corrupted > git library. > > Cheers, > Juraj > >> El 15-02-2017, a las 12:24, Alexandre Bergel >> escribió: >> >> Hi! >> >> I have "Error: External module not found” when trying to clone a repository. >> I have the VM 7.0 (built on Oct 7, 2016) and Pharo 60371 >> https://github.com/npasserini/iceberg/issues/281 >> >> Help appreciated. >> >> Cheers, >> Alexandre >> >> -- >> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >> Alexandre Bergel http://www.bergel.eu >> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >> >> >> >> > > -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexandre Bergel http://www.bergel.eu ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
[Pharo-users] Typing a | character with a French AZERTY keybord : problem solved
Hi Everybody, Someone gave me the unique proper way to type a | , and I want to make it available to every person confronted to this problem. It's enough to maintaind the key AltGR and hit the kay 6 of the KBD (not the numeric pad). I'm not sure it will help anyone since I'm not sure someone as simple as me does exist. But who knows? :| Regards Mark
Re: [Pharo-users] [State Machine] Implementation for pharo (sergio ruiz)
Am 16.02.17 um 22:52 schrieb pharo-users-requ...@lists.pharo.org: Just checking in to see if there were any projects out there that included a stage machine. There is one that I?ve been using in Ruby for awhile that I really like. I would love if we have something like that available.. Thanks! peace, sergio photographer, journalist, visionary You might want to check the AuDSL: http://ss3.gemtalksystems.com/ss/AuDSL3.html with Monticello: MCGemstoneRepository location: 'http://ss3.gemtalksystems.com/ss/AuDSL3' user: '' password: '' As a DSL this package guarantees that your own state machine code is purely stateless & testable. The last version is a port to Pharo 5. Please load: PetitParser stable version (from Catalog Browser) use: ' PPBrowser open ' to see the grammar (apologies for PPBrowser using depricated methods) explore example and tests have fun -- signatur Hartmut Krasemann Königsberger Str. 41 c D 22869 Schenefeld Tel. 040.8307097 Mobil 0171.6451283 krasem...@acm.org
Re: [Pharo-users] Problem load Magritte
On 17/02/17 12:34, Vitor Medina Cruz wrote:StephanEggermont I am getting the error message while trying to load magritte through the Pharo5 Catalog on a Windows machine: Looks like a wrong version of the configuration. It looks like ConfigurationOfMagritte3-TudorGirba.122 did not get copied to the MetaRepo. I've fixed that. You can also download it from smalltalkhub Magritte/Magritte3, and then do a ConfigurationOfMagritte3 load Stephan
Re: [Pharo-users] Issue with Iceberg
curl get.pharo.org/vmLatest60 | bash > Le 17 févr. 2017 à 14:48, Alexandre Bergel a écrit : > > Getting the latest unstable VM is a bit mysterious. Where to get it? > Is it available here: > http://files.pharo.org/vm/pharo/mac/ > ? > No idea > > The latest VM on the files.pharo.org is tagged as 6.0-pre. I guess this is > not the latest unstable VM... > > Alexandre > >> On Feb 15, 2017, at 1:32 PM, Juraj Kubelka wrote: >> >> You likely need the latest (unstable) VM because the stable one has >> corrupted git library. >> >> Cheers, >> Juraj >> >>> El 15-02-2017, a las 12:24, Alexandre Bergel >>> escribió: >>> >>> Hi! >>> >>> I have "Error: External module not found” when trying to clone a repository. >>> I have the VM 7.0 (built on Oct 7, 2016) and Pharo 60371 >>> https://github.com/npasserini/iceberg/issues/281 >>> >>> Help appreciated. >>> >>> Cheers, >>> Alexandre >>> >>> -- >>> _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: >>> Alexandre Bergel http://www.bergel.eu >>> ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. >>> >>> >>> >>> >> >> > > -- > _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: > Alexandre Bergel http://www.bergel.eu > ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;. > > > >
Re: [Pharo-users] Problem load Magritte
Thanks, that works! On Fri, Feb 17, 2017 at 1:06 PM, Stephan Eggermont wrote: > On 17/02/17 12:34, Vitor Medina Cruz wrote:StephanEggermont > >> I am getting the error message while trying to load magritte through the >> Pharo5 Catalog on a Windows machine: >> > > Looks like a wrong version of the configuration. > It looks like ConfigurationOfMagritte3-TudorGirba.122 did not get > copied to the MetaRepo. I've fixed that. > You can also download it from smalltalkhub > Magritte/Magritte3, and then do a ConfigurationOfMagritte3 load > > Stephan > > >
Re: [Pharo-users] Latest Voyage for Pharo4
Trying to understand this problem: >From my development image, I uninstalled all seaside, then I installed Voyage. This time it went fine AND Seaside-core *was not* installed during the process. What the heck is going on? When Seaside was present in my dev. image, installing Voyage make Seaside-core to be installed/upgraded (it was marked as dirty in Monticello, but no code change in fact) and it resulted in a broken Seaside installation?? Is it Metacello voodoo? -- Dr. Geo http://drgeo.eu
Re: [Pharo-users] Team programming with Smalltalk
You have a very strong point. The problem you emphasised, without explicitly naming it, comes from the image. Because the image preserves state it is also a great receptacle and accumulator for entropies, and as we know entropies only increase, never decrease! The direct consequence is that, at some time, after some interactions, installing code in some order, or installing broken code, an image breaks, hit the ground and becomes unusable. The image limit is always the chaos (as long as it is used as a living thing and its evolving state is preserved, saved), Entropies always comes with interacting 'living' system. So Smalltalk image comes with this downside of entropies. I don't see how you can bring argument against that to developer team, because it is the Smalltalk weakness, as well its strong point. Very funny. Of course you can try to limit entropies. Versioning your image is probably what to do, for example host task could save version of your image every two hours, daily, etc. GNU Smalltalk took an original approach: it ships a minimal image you don't modify and you install code on top of it. So really you never save your image, entropies remains constant over time. This approach is not really possible with Pharo. Best wishes Hilaire Le 15/02/2017 à 23:43, horrido a écrit : > In file-based word, the answer is tests and CI. What is the smalltalk way? > And please do not say "It's in the conceptual nature of programming" -- if > the scenario makes no sense in the smalltalk world (maybe you are not > supposed to have 20 people working on the same project?) please say this. > > - > > How would you respond? I know Smalltalk can be used in large team > programming, but since I personally have no experience with this, I cannot > respond intelligently. -- Dr. Geo http://drgeo.eu
Re: [Pharo-users] Team programming with Smalltalk
I've used ENVY for a couple of years, and marginally used Store. Store is nothing compared with ENVY, ENVY is far superior. Store is like Monticello, but as such it lacks the "Configuration Map" part of it, that is offered by Metacello in Pharo/Squeak/GemStone. However I find ENVY to be too cumbersome for an agile way of working. I found Dolphin Smalltalk X6/7 using PAX source format which is file based VCS friendly working with Git to be a very good fit, and we used it in a team of up to 10 commiters to the same repository. Monticello together with Metacello offers a very good balance, with integrated tools that enables you to merge and understand the changes. I haven't used Iceberg yet. Esteban A. Maringolo 2017-02-15 20:53 GMT-03:00 Brad Selfridge : > I have worked with VASmalltalk for 20 years and this included projects > utilizing 10-15 developers. VASmalltalk uses Envy Manager as its VCS. Envy, > in my opinion, is far superior to anything on the market today where it > concerns code management. It has open editions, scratch editions, versions, > application packages, sub-application packages, merges, and doffs. However, > it was built to be used in an internal organization. It is not usable for > open source Smalltalk VCS projects such as Git. I believe that Visualworks > uses a RDBMS product called Store that is similar to Envy. Both of these are > commercial Smalltalks, however. > > > > - > Brad Selfridge > -- > View this message in context: > http://forum.world.st/Team-programming-with-Smalltalk-tp4934508p4934514.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >
Re: [Pharo-users] Latest Voyage for Pharo4
Hilaire, You don't mention how you are loading Voyage. If I had the load expression and Transcript output from the load, I'd pretty much be able to tell pretty much what is going on. I have a couple of theories about what could be going wrong, but without the load expression and Transcript output, I'd only be guessing and of course there is the possibility that you've discovered a bug in Metacello:) If you'd like to get to the bottom of this, send me the load expression and Transcript output and we'll go from there ... Dale On 02/17/2017 08:56 AM, Hilaire wrote: Trying to understand this problem: From my development image, I uninstalled all seaside, then I installed Voyage. This time it went fine AND Seaside-core *was not* installed during the process. What the heck is going on? When Seaside was present in my dev. image, installing Voyage make Seaside-core to be installed/upgraded (it was marked as dirty in Monticello, but no code change in fact) and it resulted in a broken Seaside installation?? Is it Metacello voodoo?
[Pharo-users] Seeking support: Vote for Jigyasa Grover for Red Hat International Women in Open Source Academic Awards 2017
Dear All It feels delighted to be nominated as finalist for *Red Hat International Women in Open Source Academic Awards 2017* owing to my significant contributions to the open source community spanning various organisations & projects viz FOSSASIA, Pharo/Smalltalk, European Smalltalk Users Group (ESUG), Hashkat, Women Who Code, Google Developers Group, Learn IT Girl!, various tech stints in Canada, Europe, Singapore & India, etc. and everyone's best wishes. After initial two rounds, final voting round is open now till March 6, 2017. I request and appeal all of you to kindly bless me with your valuable votes. Folks, Some love & maximum clicks please :wink: Details: https://www.redhat.com/en/about/women-in-open-source Vote here: https://engage.redhat.com/opensourceawards-winners-votingform-2017 -- View this message in context: http://forum.world.st/Seeking-support-Vote-for-Jigyasa-Grover-for-Red-Hat-International-Women-in-Open-Source-Academic-Awar7-tp4934824.html Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.
Re: [Pharo-users] Latest Voyage for Pharo4
Hi Dale, At first I was more thinking of a problem in the dependencies of Voyage, but then it seems not as with unload Seaside, Voyage get load. It did not help anyway becasue Seaside can't be reinstalled (Obsolete class syndrom hit there) Voyage is installed as: "VoyageMongo EstebanLorenzano.47" ConfigurationOfVoyageMongo load The transcript output in the attached document Thanks Le 17/02/2017 à 18:54, Dale Henrichs a écrit : > You don't mention how you are loading Voyage. If I had the load > expression and Transcript output from the load, I'd pretty much be able > to tell pretty much what is going on. > > I have a couple of theories about what could be going wrong, but without > the load expression and Transcript output, I'd only be guessing and of > course there is the possibility that you've discovered a bug in Metacello:) > > If you'd like to get to the bottom of this, send me the load expression > and Transcript output and we'll go from there ... > -- Dr. Geo http://drgeo.eu Loading 1.3.3 of ConfigurationOfVoyageMongo... Fetched -> ConfigurationOfMagritte3-TudorGirba.122 --- http://smalltalkhub.com/mc/Magritte/Magritte3/main/ --- http://smalltalkhub.com/mc/Magritte/Magritte3/main/ Loaded -> ConfigurationOfMagritte3-TudorGirba.122 --- http://smalltalkhub.com/mc/Magritte/Magritte3/main/ --- /home/hilaire/Travaux/Developpement/Cofilair/Code4.0/sources Fetched -> ConfigurationOfMongoTalk-MartinDias.49 --- http://smalltalkhub.com/mc/MongoTalkTeam/mongotalk/main/ --- http://smalltalkhub.com/mc/MongoTalkTeam/mongotalk/main/ Loaded -> ConfigurationOfMongoTalk-MartinDias.49 --- http://smalltalkhub.com/mc/MongoTalkTeam/mongotalk/main/ --- /home/hilaire/Travaux/Developpement/Cofilair/Code4.0/sources Project: Magritte3 stable [3.5.1] Fetched -> ConfigurationOfSeaside3-JohanBrichau.323 --- http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main/ --- http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main/ Loaded -> ConfigurationOfSeaside3-JohanBrichau.323 --- http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main/ --- http://smalltalkhub.com/mc/Seaside/MetacelloConfigurations/main/ Fetched -> ConfigurationOfMagritteGlamourForPharo40-SeanDeNigris.3 --- http://smalltalkhub.com/mc/SeanDeNigris/SeansMetaRepo/main/ --- http://smalltalkhub.com/mc/SeanDeNigris/SeansMetaRepo/main/ Loaded -> ConfigurationOfMagritteGlamourForPharo40-SeanDeNigris.3 --- http://smalltalkhub.com/mc/SeanDeNigris/SeansMetaRepo/main/ --- http://smalltalkhub.com/mc/SeanDeNigris/SeansMetaRepo/main/ Project: Grease release1.2 [1.2.6] Fetched -> Grease-Core-pmm.96 --- http://smalltalkhub.com/mc/Seaside/Grease11/main/ --- http://smalltalkhub.com/mc/Seaside/Grease11/main/ Fetched -> Grease-Tests-Core-pmm.104 --- http://smalltalkhub.com/mc/Seaside/Grease11/main/ --- http://smalltalkhub.com/mc/Seaside/Grease11/main/ Project: MagritteGlamourForPharo40 1.0 Fetched -> GT-Inspector-SeanDeNigris.308 --- http://smalltalkhub.com/mc/Moose/GToolkit/main/ --- http://smalltalkhub.com/mc/Moose/GToolkit/main/ Fetched -> Glamour-Core-SeanDeNigris.301 --- http://smalltalkhub.com/mc/Moose/Glamour/main/ --- http://smalltalkhub.com/mc/Moose/Glamour/main/ Fetched -> Glamour-Magritte-Presentations-AndreiChis.7 --- http://smalltalkhub.com/mc/Moose/Glamour/main/ --- http://smalltalkhub.com/mc/Moose/Glamour/main/ Project: Seaside3 release3.2 [3.2.1] Project: Grease release1.2 [1.2.6] Project: Grease Core Tests release1.2 [1.2.6] Fetched -> Seaside-Core-JohanBrichau.871 --- http://smalltalkhub.com/mc/Seaside/Seaside32/main/ --- http://smalltalkhub.com/mc/Seaside/Seaside32/main/ Fetched -> Seaside-Canvas-JohanBrichau.135 --- http://smalltalkhub.com/mc/Seaside/Seaside32/main/ --- http://smalltalkhub.com/mc/Seaside/Seaside32/main/ Fetched -> Seaside-Session-JohanBrichau.186 --- http://smalltalkhub.com/mc/Seaside/Seaside32/main/ --- http://smalltalkhub.com/mc/Seaside/Seaside32/main/ Fetched -> Seaside-RenderLoop-pmm.99 --- http://smalltalkhub.com/mc/Seaside/Seaside32/main/ --- http://smalltalkhub.com/mc/Seaside/Seaside32/main/ Fetched -> Seaside-Tools-Core-JohanBrichau.27 --- http://smalltalkhub.com/mc/Seaside/Seaside32/main/ --- http://smalltalkhub.com/mc/Seaside/Seaside32/main/ Fetched -> Seaside-Pharo-Tools-Spec-JohanBrichau.19 --- http://smalltalkhub.com/mc/Seaside/Seaside32/main/ --- http://smalltalkhub.com/mc/Seaside/Seaside32/main/ Fetched -> Seaside-Widgets-JohanBrichau.36 --- http://smalltalkhub.com/mc/Seaside/Seaside32/main/ --- http://smalltalkhub.com/mc/Seaside/Seaside32/main/ Fetched -> Seaside-Tools-Web-JohanBrichau.129 --- http://smalltalkhub.com/mc/Seaside/Seaside32/main/ --- http://smalltalkhub.com/mc/Seaside/Seaside32/main/ Fetched -> Seaside-Pharo50-Tools-Web-JohanBrichau.4 --- http://smalltalkhub.com/mc/Seaside/Seaside32/main/ --- http://smalltalkhub.com/mc/Seaside/Seaside32/main/ Fetched -> Seaside-Development-pmm.166 --- http://smalltalkhub.com/mc/Seaside/Seaside32/main/ --- htt
Re: [Pharo-users] Team programming with Smalltalk
On 02/15/2017 02:43 PM, horrido wrote: In file-based word, the answer is tests and CI. What is the smalltalk way? And please do not say "It's in the conceptual nature of programming" -- if the scenario makes no sense in the smalltalk world (maybe you are not supposed to have 20 people working on the same project?) please say this. - Well I think that being able to use git (disk based SCMS) for managing Smalltalk code is one step towards making it practical for large teams to work together ... The major piece that I think is still missing is the ability to have a declarative formula/specification for the contents of an image ... The declarative build formula/specification must be something that can be shared and versioned. Today, the closest we can come to this is an ad hoc Smalltalk script and that really isn't a good answer I think that some of the missing building blocks for an image-level declarative formula specification are covered in my "Dangerous Liaisons: Smalltalk, files, and git "[1] talk, but I really think that there is additional work that needs to be done to make it really practical for large teams to be able work together on large projects. Dale [1] http://fast.org.ar/talks/dangerous-liaisons-smalltalk-files-and-git
Re: [Pharo-users] Latest Voyage for Pharo4
Hilaire, Thanks for the detailed information ... I see that you are using the old-style loading of Voyage (`ConfigurationOfVoyageMongo load`) ... when using this style of loading, Metacello has to guess about which projects are loaded and what version of the project is loaded. I is possible that the behavior you are seeing is a direct result of Metacello guessing wrong. I recommend that you load projects using the new style based on `Metacello new`: Metacello new configuration: 'Voyage'; version: '???'; repository: '???'; load When using this style of loading, Metacello maintains a registry of loaded projects and no longer makes guesses what is loaded in the image... From a cursory glance at the transcript output I see that version 3.2.1 of Seaside is being loaded and there appears to be a pretty much wholesale upgrade of Seaside as a bunch of new package versions are being loaded ... Do you happen to know what version of Seaside you originally loaded. I assume that you have an older version of Seaside loaded -- perhaps even Seaside 3.1? As to "Why is a Seaside load being triggered at all?", there is nothing obvious -- I am suspicious that the old-style loading is causing the problem, but I don't have any hard evidence, yet. I will have to start downloading specific configuration versions to complete my analysis and I have limited time left before I have to run some errands so I might not have answers until later this afternoon. If you want to run an experiment in the meantime, you could try using the new-style Metacello load, just to see what happens ... if Seaside is still upgraded, the Transcript output would be useful as it will give me additional information. If VoyageMongo loads correctly, then you are in business:) BTW, you should probably load the latest version of Metacello into your Pharo4.0 image[1] before using the new-style load. Dale [1] https://github.com/dalehenrich/metacello-work#pharo30-pharo40-and-pharo50 On 02/17/2017 10:14 AM, Hilaire wrote: Hi Dale, At first I was more thinking of a problem in the dependencies of Voyage, but then it seems not as with unload Seaside, Voyage get load. It did not help anyway becasue Seaside can't be reinstalled (Obsolete class syndrom hit there) Voyage is installed as: "VoyageMongo EstebanLorenzano.47" ConfigurationOfVoyageMongo load The transcript output in the attached document Thanks Le 17/02/2017 à 18:54, Dale Henrichs a écrit : You don't mention how you are loading Voyage. If I had the load expression and Transcript output from the load, I'd pretty much be able to tell pretty much what is going on. I have a couple of theories about what could be going wrong, but without the load expression and Transcript output, I'd only be guessing and of course there is the possibility that you've discovered a bug in Metacello:) If you'd like to get to the bottom of this, send me the load expression and Transcript output and we'll go from there ...
[Pharo-users] TextAlignment in Spec
Hello Is possible to do alignment in list? in Label? especially in multilist TextEmphasis work correctly but TextAlignment not " |c| c := OrderedCollection new. 10 timesRepeat: [c add: (Text string: 'a' attribute: TextAlignment centered)]. (ListModel new items: c) openWithSpec. " " |c| c := OrderedCollection new. 10 timesRepeat: [c add: (Text string: 'a' attribute: TextEmphasis bold)]. (ListModel new items: c) openWithSpec " That it's that we have for the moment or we can do better. Thanks, spec is super for newbies. Missatge enviat a través del Webmail de Girona.com http://www.girona.com
Re: [Pharo-users] Latest Voyage for Pharo4
Hi Dale, Thanks for your detailed suggestions. I follow instructions, here the report bellow. Installed newest Metacello, then Voyage with new style: Metacello new baseline: 'Metacello'; repository: 'github://dalehenrich/metacello-work:master/repository'; get. Metacello new baseline: 'Metacello'; repository: 'github://dalehenrich/metacello-work:master/repository'; onConflict: [:ex | ex allow]; load. "Fetch from voyage repo at github" Metacello new repository: 'github://pharo-nosql/voyage/mc'; baseline: 'Voyage'; load: 'mongo tests'. It still have the same error, do an upgrade of Seaside. Enclosed is the transcript for both Metacello and Voyage install. Seaside installed was 3.1.x. I don't know the x digit, it is not documented in an obvious way :( Hope it helps Thanks Hilaire -- Dr. Geo http://drgeo.eu Fetched -> BaselineOfMetacello-TravisCI.93 --- github://dalehenrich/metacello-work:master/repository --- github://dalehenrich/metacello-work:master/repository Loaded -> BaselineOfMetacello-TravisCI.93 --- github://dalehenrich/metacello-work:master/repository --- github://dalehenrich/metacello-work:master/repository Loading baseline of BaselineOfMetacello... Fetched -> BaselineOfFileTree-ThierryGoubier.15 --- github://dalehenrich/filetree:pharo4.0/repository --- github://dalehenrich/filetree:pharo4.0/repository Loaded -> BaselineOfFileTree-ThierryGoubier.15 --- github://dalehenrich/filetree:pharo4.0/repository --- github://dalehenrich/filetree:pharo4.0/repository Fetched -> ConfigurationOfGofer-dkh.45 --- http://seaside.gemtalksystems.com/ss/metacello --- http://seaside.gemtalksystems.com/ss/metacello Loaded -> ConfigurationOfGofer-dkh.45 --- http://seaside.gemtalksystems.com/ss/metacello --- http://seaside.gemtalksystems.com/ss/metacello Project: FileTree baseline Project: OSProcess stable [4.6.4] Project: Pipeability 4.6.15 Project: OSProcess 4.6.4 Project: Pipeability 4.6.15 Fetched -> MonticelloFileTree-Core-ThierryGoubier.132 --- github://dalehenrich/filetree:pharo4.0/repository --- github://dalehenrich/filetree:pharo4.0/repository Fetched -> MonticelloFileTree-FileSystem-Utilities-dkh.28 --- github://dalehenrich/filetree:pharo4.0/repository --- github://dalehenrich/filetree:pharo4.0/repository Project: Gofer stable [1.0.5] Project: Gofer Tests stable [1.0.5] Fetched -> Metacello-Base-topa.124 --- github://dalehenrich/metacello-work:master/repository --- github://dalehenrich/metacello-work:master/repository Fetched -> Metacello-Core-TravisCI.829 --- github://dalehenrich/metacello-work:master/repository --- github://dalehenrich/metacello-work:master/repository Fetched -> Metacello-MC-dkh.731 --- github://dalehenrich/metacello-work:master/repository --- github://dalehenrich/metacello-work:master/repository Fetched -> Metacello-PharoCommonPlatform-TravisCI.17 --- github://dalehenrich/metacello-work:master/repository --- github://dalehenrich/metacello-work:master/repository Fetched -> Metacello-Platform.pharo30-TravisCI.9 --- github://dalehenrich/metacello-work:master/repository --- github://dalehenrich/metacello-work:master/repository Fetched -> Metacello-ToolBox-dkh.147 --- github://dalehenrich/metacello-work:master/repository --- github://dalehenrich/metacello-work:master/repository Fetched -> Metacello-Cypress-TravisCI.7 --- github://dalehenrich/metacello-work:master/repository --- github://dalehenrich/metacello-work:master/repository Fetched -> Metacello-FileTree-dkh.36 --- github://dalehenrich/metacello-work:master/repository --- github://dalehenrich/metacello-work:master/repository Fetched -> Metacello-GitBasedRepository-TravisCI.17 --- github://dalehenrich/metacello-work:master/repository --- github://dalehenrich/metacello-work:master/repository Fetched -> Metacello-Bitbucket-topa.6 --- github://dalehenrich/metacello-work:master/repository --- github://dalehenrich/metacello-work:master/repository Fetched -> Metacello-GitHub-topa.46 --- github://dalehenrich/metacello-work:master/repository --- github://dalehenrich/metacello-work:master/repository Fetched -> Metacello-Reference-dkh.36 --- github://dalehenrich/metacello-work:master/repository --- github://dalehenrich/metacello-work:master/repository Fetched -> Metacello-Tutorial-dkh.26 --- github://dalehenrich/metacello-work:master/repository --- github://dalehenrich/metacello-work:master/repository Fetched -> Metacello-TestsCore-dkh.40 --- github://dalehenrich/metacello-work:master/repository --- github://dalehenrich/metacello-work:master/repository Fetched -> Metacello-TestsMCResources-dkh.33 --- github://dalehenrich/metacello-work:master/repository --- github://dalehenrich/metacello-work:master/repository Fetched -> Metacello-TestsCommonMC.pharo20-dkh.5 --- github://dalehenrich/metacello-work:master/repository --- github://dalehenrich/metacello-work:master/repository Fetched -> Metacello-TestsMCCore-TravisCI.7 --- github://dalehenrich/metacello-work:master/reposito
Re: [Pharo-users] Latest Voyage for Pharo4
Again, thanks for detailed info ... The fact that you loaded Seaside3.1.x is good enough for my purposes .. the fact that Seaside3.2 is getting installed implies that there is a hard dependency on Seaside in one of the projects (Magritte3 perhaps?) ... odd that ConfigurationOfSeaside3 wasn't downloaded this time around --- Can you get the package version of ConfigurationOfSeaside3 that's in the image after the `Metacello new` loads?... I'll have to dive into the configurations now ... Dale On 02/17/2017 12:44 PM, Hilaire wrote: Hi Dale, Thanks for your detailed suggestions. I follow instructions, here the report bellow. Installed newest Metacello, then Voyage with new style: Metacello new baseline: 'Metacello'; repository: 'github://dalehenrich/metacello-work:master/repository'; get. Metacello new baseline: 'Metacello'; repository: 'github://dalehenrich/metacello-work:master/repository'; onConflict: [:ex | ex allow]; load. "Fetch from voyage repo at github" Metacello new repository: 'github://pharo-nosql/voyage/mc'; baseline: 'Voyage'; load: 'mongo tests'. It still have the same error, do an upgrade of Seaside. Enclosed is the transcript for both Metacello and Voyage install. Seaside installed was 3.1.x. I don't know the x digit, it is not documented in an obvious way :( Hope it helps Thanks Hilaire
Re: [Pharo-users] Latest Voyage for Pharo4
The configuration of seaside is the same before and after the 'Monticello new' loads. #278 It match the fact you don't see a ConfigurationOfSeaside3 download in the transcript. As I wrote in a previous email, if Seaside is not installed, the install of Voyage doesn't trigger a Seaside install. Don't know if that specific may help. Thanks Le 17/02/2017 à 22:15, Dale Henrichs a écrit : > The fact that you loaded Seaside3.1.x is good enough for my purposes > .. the fact that Seaside3.2 is getting installed implies that there is a > hard dependency on Seaside in one of the projects (Magritte3 perhaps?) > ... odd that ConfigurationOfSeaside3 wasn't downloaded this time around > --- Can you get the package version of ConfigurationOfSeaside3 that's in > the image after the `Metacello new` loads?... I'll have to dive into the > configurations now ... -- Dr. Geo http://drgeo.eu
Re: [Pharo-users] Team programming with Smalltalk
Am 17.02.2017 um 18:51 schrieb Esteban A. Maringolo: > I've used ENVY for a couple of years, and marginally used Store. Store > is nothing compared with ENVY, ENVY is far superior. Store is like > Monticello, but as such it lacks the "Configuration Map" part of it, > that is offered by Metacello in Pharo/Squeak/GemStone. > > However I find ENVY to be too cumbersome for an agile way of working. And another point is, that the way of ENVYs thinking is also available in the tools they offer for the developer (let it be VW 2.5.2 or VASmalltalk). Same tools on all platforms. This way of thinking is also introduced in the kind of browsers you have - which offers different ways of views on your projects. For me the most and strongest point in the ENVY-Browsers area is the ApplicationBrowser. Its shows you only the part of the image of a specific application (package) , which are new classes introduced by you in this application (package) - but also all the extension methods you added in this application (package) to classes. That means - programmers can stay for the whole life of a project - in only this kind of browsers. A wonderful way of viewing the image. Sadly this is gone or simply only badly implemented. E.g. in Pharo you can select a package - fine, but to know, what has been extended in this package ?. The name of the method categories also define in which package this method is located in. Make a type error and the method goes into a different package and you will not recognize it. Solutions born by the idea: how can we make it simple to have a solution this evening - and these solutions survive over the years. ENVY for the first time used ? Well I remember, that I was crazy about this tool - all this versioning, prerequisites etc ... but now after 20 years ? I'm used to the tools available on the Smalltalk market - but really nice versioning (with several platforms): ENVY is the way to go. And the original version had several user interactions implemented - which have been defined by VASmalltalk (e.g. change the developer role and make this or that in one click). ENVY is also the tool, where I have so much confidence with, because over the last 20 years I've never seen crashes and data losses. A strong point for a closed-source software repository. Marten -- Marten Feldtmann
