- Pharo-users - lists.pharo.org

Re: [Pharo-users] Problem with Mongo on Pharo5 ("collection already exists")

by Sabine Manaa

Hi Steph, thank you for your explanation. I was reading a little bit this morning about pharo and github. I am looking forward to the solution you will provide in future and use sthub till then. Regards Sabine -- View this message in context: http://forum.world.st/Problem-with-Mongo-on-Pharo5-collection-already-exist… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 26, 2016

Re: [Pharo-users] One comment to new Pharo5 debugger

by stepharo

Thanks Sabine! This is important that you report such problems. Several people including me already reported this problem that we will have to address for real. Stef Le 25/5/16 Ã 21:43, Sabine Manaa a Ã©crit : > Hi, > > today I moved to Pharo5. It is great to get feedback and solutions for > problems so quickly. It is a pleasure to work with Pharo and to have the > community. I am grateful for having this. > > I have one comment. I don't want to complain, I can use it but I was > wondering about the new position and size of the debugger buttons. > > There is a longer distance now from code text pane to the buttons - I see > this as disadvantage to earlier versions of Pharo from the user experience. > The buttons are a lot of smaller - same disadvantage - both if you use the > mouse. > > Ok, after seeing that, I thought "Sabine, you should use keyboard shortcuts > here, too" (I use much of them but interesting - til now not in the > debugger). > > Then I saw the shortcuts for > Proceed cmd+r > Restart cmd-shift-a > Into cmd-e > over cmd-shift-o > through cmd-shift-t > > especially into, over and through have so different key combinations, two > with shift, one without shift. When I debug, I often use for example > into-into-over-over-over-throuhg-through--into-into etc...and with the > combinations cmd-e and cmd-shit-e, it is more "finger-work". It would be > better to have all those shortcuts with or all shortcuts without shift. And > the letters not so far away at the keyboard (e-o-t) > > This is only my opinion and my first impression after one day with Pharo5. I > am sure, after a few days, I forgot that this was uncomfortable because I > have the shortcuts coming automatically into my fingers. > > Regards > Sabine > > > > > > > -- > View this message in context: http://forum.world.st/One-comment-to-new-Pharo5-debugger-tp4897390.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

May 26, 2016

Re: [Pharo-users] One comment to new Pharo5 debugger

by Denis Kudriashov

Hi. Maybe me should give chance to standard Moose debugger view? (where stack pane on the left) 2016-05-26 9:37 GMT+02:00 Christophe Demarey <christophe.demarey(a)inria.fr>: > Hi Sabine, > > this point was also Â« discussed Â» (no answer) here: > http://forum.world.st/gtdebugger-debug-actions-buttons-td4874316.html > Yes, the new buttons are counter-productive and there is even no setting > to have them usable â¦ > You can still with to the SpecDebugger through settings > > > Le 25 mai 2016 Ã 22:49, Peter UhnÃ¡k <i.uhnak(a)gmail.com> a Ã©crit : > > Hi, > > yes, this question was raised before, but there are some disagreements > over how it should be, so it may take some time > http://forum.world.st/GTDebugger-shortcuts-usability-td4890316.html > > You can also use a startup script to reassign them, such as this one. > https://github.com/peteruhnak/pharo-scripts/blob/master/config/5.0/uniformD… > But a startup script is a temporary solution. > > On Wed, May 25, 2016 at 9:43 PM, Sabine Manaa <manaa.sabine(a)gmail.com> > wrote: > >> Hi, >> >> today I moved to Pharo5. It is great to get feedback and solutions for >> problems so quickly. It is a pleasure to work with Pharo and to have the >> community. I am grateful for having this. >> >> I have one comment. I don't want to complain, I can use it but I was >> wondering about the new position and size of the debugger buttons. >> >> There is a longer distance now from code text pane to the buttons - I see >> this as disadvantage to earlier versions of Pharo from the user >> experience. >> The buttons are a lot of smaller - same disadvantage - both if you use the >> mouse. >> >> Ok, after seeing that, I thought "Sabine, you should use keyboard >> shortcuts >> here, too" (I use much of them but interesting - til now not in the >> debugger). >> >> Then I saw the shortcuts for >> Proceed cmd+r >> Restart cmd-shift-a >> Into cmd-e >> over cmd-shift-o >> through cmd-shift-t >> >> especially into, over and through have so different key combinations, two >> with shift, one without shift. When I debug, I often use for example >> into-into-over-over-over-throuhg-through--into-into etc...and with the >> combinations cmd-e and cmd-shit-e, it is more "finger-work". It would be >> better to have all those shortcuts with or all shortcuts without shift. >> And >> the letters not so far away at the keyboard (e-o-t) >> >> This is only my opinion and my first impression after one day with >> Pharo5. I >> am sure, after a few days, I forgot that this was uncomfortable because I >> have the shortcuts coming automatically into my fingers. >> >> Regards >> Sabine >> >> >> >> >> >> >> -- >> View this message in context: >> http://forum.world.st/One-comment-to-new-Pharo5-debugger-tp4897390.html >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com >> <http://nabble.com>. >> >> > >

May 26, 2016

Re: [Pharo-users] One comment to new Pharo5 debugger

by Christophe Demarey

Hi Sabine, this point was also Â« discussed Â» (no answer) here: http://forum.world.st/gtdebugger-debug-actions-buttons-td4874316.html <http://forum.world.st/gtdebugger-debug-actions-buttons-td4874316.html> Yes, the new buttons are counter-productive and there is even no setting to have them usable â¦ You can still with to the SpecDebugger through settings > Le 25 mai 2016 Ã 22:49, Peter UhnÃ¡k <i.uhnak(a)gmail.com> a Ã©crit : > > Hi, > > yes, this question was raised before, but there are some disagreements over how it should be, so it may take some time http://forum.world.st/GTDebugger-shortcuts-usability-td4890316.html <http://forum.world.st/GTDebugger-shortcuts-usability-td4890316.html> > > You can also use a startup script to reassign them, such as this one. https://github.com/peteruhnak/pharo-scripts/blob/master/config/5.0/uniformD… <https://github.com/peteruhnak/pharo-scripts/blob/master/config/5.0/uniformD…> > But a startup script is a temporary solution. > > On Wed, May 25, 2016 at 9:43 PM, Sabine Manaa <manaa.sabine(a)gmail.com <mailto:manaa.sabine@gmail.com>> wrote: > Hi, > > today I moved to Pharo5. It is great to get feedback and solutions for > problems so quickly. It is a pleasure to work with Pharo and to have the > community. I am grateful for having this. > > I have one comment. I don't want to complain, I can use it but I was > wondering about the new position and size of the debugger buttons. > > There is a longer distance now from code text pane to the buttons - I see > this as disadvantage to earlier versions of Pharo from the user experience. > The buttons are a lot of smaller - same disadvantage - both if you use the > mouse. > > Ok, after seeing that, I thought "Sabine, you should use keyboard shortcuts > here, too" (I use much of them but interesting - til now not in the > debugger). > > Then I saw the shortcuts for > Proceed cmd+r > Restart cmd-shift-a > Into cmd-e > over cmd-shift-o > through cmd-shift-t > > especially into, over and through have so different key combinations, two > with shift, one without shift. When I debug, I often use for example > into-into-over-over-over-throuhg-through--into-into etc...and with the > combinations cmd-e and cmd-shit-e, it is more "finger-work". It would be > better to have all those shortcuts with or all shortcuts without shift. And > the letters not so far away at the keyboard (e-o-t) > > This is only my opinion and my first impression after one day with Pharo5. I > am sure, after a few days, I forgot that this was uncomfortable because I > have the shortcuts coming automatically into my fingers. > > Regards > Sabine > > > > > > > -- > View this message in context: http://forum.world.st/One-comment-to-new-Pharo5-debugger-tp4897390.html <http://forum.world.st/One-comment-to-new-Pharo5-debugger-tp4897390.html> > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

May 26, 2016

Re: [Pharo-users] One comment to new Pharo5 debugger

by Sabine Manaa

Hi Peter, Thanks. I geht all the nabble mails and try to read at least the subject but I missed this one. I create my own shortcuts as first solution. Regards Sabine Am Mittwoch, 25. Mai 2016 schrieb Peter UhnÃ¡k [via Smalltalk] : > Hi, > > yes, this question was raised before, but there are some disagreements > over how it should be, so it may take some time > http://forum.world.st/GTDebugger-shortcuts-usability-td4890316.html > > You can also use a startup script to reassign them, such as this one. > https://github.com/peteruhnak/pharo-scripts/blob/master/config/5.0/uniformD… > But a startup script is a temporary solution. > > On Wed, May 25, 2016 at 9:43 PM, Sabine Manaa <[hidden email] > <http:///user/SendEmail.jtp?type=node&node=4897397&i=0>> wrote: > >> Hi, >> >> today I moved to Pharo5. It is great to get feedback and solutions for >> problems so quickly. It is a pleasure to work with Pharo and to have the >> community. I am grateful for having this. >> >> I have one comment. I don't want to complain, I can use it but I was >> wondering about the new position and size of the debugger buttons. >> >> There is a longer distance now from code text pane to the buttons - I see >> this as disadvantage to earlier versions of Pharo from the user >> experience. >> The buttons are a lot of smaller - same disadvantage - both if you use the >> mouse. >> >> Ok, after seeing that, I thought "Sabine, you should use keyboard >> shortcuts >> here, too" (I use much of them but interesting - til now not in the >> debugger). >> >> Then I saw the shortcuts for >> Proceed cmd+r >> Restart cmd-shift-a >> Into cmd-e >> over cmd-shift-o >> through cmd-shift-t >> >> especially into, over and through have so different key combinations, two >> with shift, one without shift. When I debug, I often use for example >> into-into-over-over-over-throuhg-through--into-into etc...and with the >> combinations cmd-e and cmd-shit-e, it is more "finger-work". It would be >> better to have all those shortcuts with or all shortcuts without shift. >> And >> the letters not so far away at the keyboard (e-o-t) >> >> This is only my opinion and my first impression after one day with >> Pharo5. I >> am sure, after a few days, I forgot that this was uncomfortable because I >> have the shortcuts coming automatically into my fingers. >> >> Regards >> Sabine >> >> >> >> >> >> >> -- >> View this message in context: >> http://forum.world.st/One-comment-to-new-Pharo5-debugger-tp4897390.html >> Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. >> >> > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://forum.world.st/One-comment-to-new-Pharo5-debugger-tp4897390p4897397.… > To start a new topic under Pharo Smalltalk Users, email > ml-node+s1294792n1310670h65(a)n4.nabble.com > <javascript:_e(%7B%7D,'cvml','ml-node%2Bs1294792n1310670h65(a)n4.nabble.com');> > To unsubscribe from Pharo Smalltalk Users, click here > <http://forum.world.st/template/NamlServlet.jtp?macro=unsubscribe_by_code&no…> > . > NAML > <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> > -- View this message in context: http://forum.world.st/One-comment-to-new-Pharo5-debugger-tp4897390p4897442.… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 26, 2016

Monthly Pharo Newsletter

by marcus.denker＠inria.fr

Hi, Some time ago we set up a very low traffic âPharo Newsletterâ Mailinglist. The idea is that this gets: -> a mail for the release -> *one* mail at the end of the month with 2-4 topics It seems to work well. We have until now send two monty mails and the mail for the Pharo5 release. If you want to be on it, here is a link to subscribe: http://pharo.us11.list-manage.com/subscribe?u=6f667565c2569234585a7be77&id=… If you follow all blogs, twitter + read all mails, there might not be anything new, but as things get even hard to follow for me it might be a good way to keep up with the most important things happening. And: if you have an idea for content (e.g. highlighting a project or a success story), please get in touch! Marcus

May 26, 2016

Re: [Pharo-users] One comment to new Pharo5 debugger

by Peter UhnÃ¡k

Hi, yes, this question was raised before, but there are some disagreements over how it should be, so it may take some time http://forum.world.st/GTDebugger-shortcuts-usability-td4890316.html You can also use a startup script to reassign them, such as this one. https://github.com/peteruhnak/pharo-scripts/blob/master/config/5.0/uniformD… But a startup script is a temporary solution. On Wed, May 25, 2016 at 9:43 PM, Sabine Manaa <manaa.sabine(a)gmail.com> wrote: > Hi, > > today I moved to Pharo5. It is great to get feedback and solutions for > problems so quickly. It is a pleasure to work with Pharo and to have the > community. I am grateful for having this. > > I have one comment. I don't want to complain, I can use it but I was > wondering about the new position and size of the debugger buttons. > > There is a longer distance now from code text pane to the buttons - I see > this as disadvantage to earlier versions of Pharo from the user experience. > The buttons are a lot of smaller - same disadvantage - both if you use the > mouse. > > Ok, after seeing that, I thought "Sabine, you should use keyboard shortcuts > here, too" (I use much of them but interesting - til now not in the > debugger). > > Then I saw the shortcuts for > Proceed cmd+r > Restart cmd-shift-a > Into cmd-e > over cmd-shift-o > through cmd-shift-t > > especially into, over and through have so different key combinations, two > with shift, one without shift. When I debug, I often use for example > into-into-over-over-over-throuhg-through--into-into etc...and with the > combinations cmd-e and cmd-shit-e, it is more "finger-work". It would be > better to have all those shortcuts with or all shortcuts without shift. And > the letters not so far away at the keyboard (e-o-t) > > This is only my opinion and my first impression after one day with Pharo5. > I > am sure, after a few days, I forgot that this was uncomfortable because I > have the shortcuts coming automatically into my fingers. > > Regards > Sabine > > > > > > > -- > View this message in context: > http://forum.world.st/One-comment-to-new-Pharo5-debugger-tp4897390.html > Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com. > >

May 25, 2016

Re: [Pharo-users] Problem with Mongo on Pharo5 ("collection already exists")

by Esteban Lorenzano

Hi, yes, I recommend you to use the github version, we are moving there. But anyway we are keeping the sthub as mirrorâ¦ it just got de-sync. And the only reason why I needed the merge, and not a simple copy is because metadataless format got activated and I lost the history, so I rather merge to recover history in some wayâ¦ :) cheers! Esteban > On 25 May 2016, at 21:23, Sabine Manaa <manaa.sabine(a)gmail.com> wrote: > > Hi Esteban, > > great, now it works. Thank you! > > In the comments, I see "merged with github". I am curious about using github in future, too. > > Regards > Sabine > > 2016-05-25 21:01 GMT+02:00 EstebanLM [via Smalltalk] <[hidden email] <x-msg://138/user/SendEmail.jtp?type=node&node=4897384&i=0>>: > hi Sabine, > > please update to latest packages of Voyageâ¦ there was a de-sync problem with the API change in MongoTalk, that *should* fix your issue. > > cheers, > Esteban > > >> On 25 May 2016, at 16:29, Sabine Manaa <[hidden email] <http://user/SendEmail.jtp?type=node&node=4897378&i=0>> wrote: >> >> note that it only occurs (hanging image) if you do >> "VORepository current reset" >> before. Or have a new Image. >> >> >> 2016-05-25 15:38 GMT+02:00 Sabine Manaa <[hidden email] <http://user/SendEmail.jtp?type=node&node=4897378&i=1>>: >> I have a non-responding image with the original code (with the signal) >> >> 2016-05-25 15:14 GMT+02:00 Holger Freyther [via Smalltalk] <[hidden email] <http://user/SendEmail.jtp?type=node&node=4897348&i=0>>: >> >> > On 25 May 2016, at 15:42, Esteban Lorenzano <[hidden email] <http://user/SendEmail.jtp?type=node&node=4897346&i=0>> wrote: >> > >> > >> >> Hi, >> >> >> > No I donâtâ¦ in part because is not me who make that code, but also because it is expected: after, you have: >> > >> > getCollection: aString >> > ^ [ self addCollection: aString capped: false size: nil max: nil ] >> > on: MongoCollectionAlreadyExists >> > do: [ :err | >> > MongoCollection database: self name: aString ] >> > >> > so the idea is to refine the error to separate MongoCollectionAlreadyExists so it can later be catch and handled properly. >> >> when adding capped collection support it seemed like a good idea to fail if a collection already exists that might not be capped, but given the follow up issues I wonder if I/we should restore the original behavior that just ignored all errors? >> >> holger >> >> >> If you reply to this email, your message will be added to the discussion below: >> http://forum.world.st/Problem-with-Mongo-on-Pharo5-collection-already-exist… <http://forum.world.st/Problem-with-Mongo-on-Pharo5-collection-already-exist…> >> To start a new topic under Pharo Smalltalk Users, email [hidden email] <http://user/SendEmail.jtp?type=node&node=4897348&i=1> >> To unsubscribe from Pharo Smalltalk Users, click here <>. >> NAML <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> >> >> View this message in context: Re: Problem with Mongo on Pharo5 ("collection already exists") <http://forum.world.st/Problem-with-Mongo-on-Pharo5-collection-already-exist…> >> >> Sent from the Pharo Smalltalk Users mailing list archive <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> at Nabble.com <http://nabble.com/>. >> > > > > If you reply to this email, your message will be added to the discussion below: > http://forum.world.st/Problem-with-Mongo-on-Pharo5-collection-already-exist… <http://forum.world.st/Problem-with-Mongo-on-Pharo5-collection-already-exist…> > To start a new topic under Pharo Smalltalk Users, email [hidden email] <x-msg://138/user/SendEmail.jtp?type=node&node=4897384&i=1> > To unsubscribe from Pharo Smalltalk Users, click here <applewebdata://C0C1A6A1-AED1-43DA-8E46-B9DBA605F718>. > NAML <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> > > View this message in context: Re: Problem with Mongo on Pharo5 ("collection already exists") <http://forum.world.st/Problem-with-Mongo-on-Pharo5-collection-already-exist…> > Sent from the Pharo Smalltalk Users mailing list archive <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> at Nabble.com <http://nabble.com/>.

May 25, 2016

Re: [Pharo-users] Having a more robust PharoLauncher in low-bandwidth conditions

by Peter UhnÃ¡k

> something like wget or curl there's also zeroconf as the alternative, or directly downloading the zip http://files.pharo.org/image/ Also Stef made a flash stick with Pharo, videos, etc. exactly for places like this (with bad or no internet). But of course PharoLauncher shouldn't crash. Alternatively PharoLauncher as far as I know has a local cache, so maybe if you need just a fresh image and not the latest one you could reuse that? Peter On Wed, May 25, 2016 at 6:37 PM, Serge Stinckwich < serge.stinckwich(a)gmail.com> wrote: > Dear all, > > in low-bandwidth countries, this is almost impossible to use > PharoLauncher to dl new images from the CI. The problem is not really > the speed (you just have to wait) but the robustness of the system. > Most of the time, you PharoLauncher crash or you have an error like : > "can't find EOCD position" before the end the of the download. > > I dunno exactly how PharoLauncher download images, but is it possible > to think about a more robust way to dl images ? To be able to continue > a dl if a network problem occurs (something like wget or curl) ? > > Thank you. > -- > Serge Stinckwich > UCBN & UMI UMMISCO 209 (IRD/UPMC) > Every DSL ends up being Smalltalk > http://www.doesnotunderstand.org/ > >

May 25, 2016

Re: [Pharo-users] Problem with Mongo on Pharo5 ("collection already exists")

by Sabine Manaa

Hi Esteban, do you know a documentation/entry point about moving to github? Is it in experimental state or recommended for all Pharo users? How/where to start? Regards Sabine 2016-05-25 21:54 GMT+02:00 EstebanLM [via Smalltalk] < ml-node+s1294792n4897394h9(a)n4.nabble.com>: > Hi, > > yes, I recommend you to use the github version, we are moving there. > But anyway we are keeping the sthub as mirrorâ¦ it just got de-sync. And > the only reason why I needed the merge, and not a simple copy is because > metadataless format got activated and I lost the history, so I rather merge > to recover history in some wayâ¦ :) > > cheers! > Esteban > > On 25 May 2016, at 21:23, Sabine Manaa <[hidden email] > <http:///user/SendEmail.jtp?type=node&node=4897394&i=0>> wrote: > > Hi Esteban, > > great, now it works. Thank you! > > In the comments, I see "merged with github". I am curious about using > github in future, too. > > Regards > Sabine > > 2016-05-25 21:01 GMT+02:00 EstebanLM [via Smalltalk] <<a > href="x-msg://138/user/SendEmail.jtp?type=node&node=4897384&i=0" > target="_top" rel="nofollow" link="external" class="">[hidden email]>: > >> hi Sabine, >> >> please update to latest packages of Voyageâ¦ there was a de-sync problem >> with the API change in MongoTalk, that *should* fix your issue. >> >> cheers, >> Esteban >> >> >> On 25 May 2016, at 16:29, Sabine Manaa <[hidden email] >> <http://user/SendEmail.jtp?type=node&node=4897378&i=0>> wrote: >> >> note that it only occurs (hanging image) if you do >> "VORepository current reset" >> before. Or have a new Image. >> >> >> 2016-05-25 15:38 GMT+02:00 Sabine Manaa <[hidden email] >> <http://user/SendEmail.jtp?type=node&node=4897378&i=1>>: >> >>> I have a non-responding image with the original code (with the signal) >>> >>> 2016-05-25 15:14 GMT+02:00 Holger Freyther [via Smalltalk] <[hidden >>> email] <http://user/SendEmail.jtp?type=node&node=4897348&i=0>>: >>> >>>> >>>> > On 25 May 2016, at 15:42, Esteban Lorenzano <[hidden email] >>>> <http://user/SendEmail.jtp?type=node&node=4897346&i=0>> wrote: >>>> > >>>> > >>>> >>>> Hi, >>>> >>>> >>>> > No I donâtâ¦ in part because is not me who make that code, but also >>>> because it is expected: after, you have: >>>> > >>>> > getCollection: aString >>>> > ^ [ self addCollection: aString capped: false size: nil max: nil ] >>>> > on: MongoCollectionAlreadyExists >>>> > do: [ :err | >>>> > MongoCollection database: self name: aString ] >>>> > >>>> > so the idea is to refine the error to separate >>>> MongoCollectionAlreadyExists so it can later be catch and handled properly. >>>> >>>> >>>> when adding capped collection support it seemed like a good idea to >>>> fail if a collection already exists that might not be capped, but given the >>>> follow up issues I wonder if I/we should restore the original behavior that >>>> just ignored all errors? >>>> >>>> holger >>>> >>>> >>>> ------------------------------ >>>> If you reply to this email, your message will be added to the >>>> discussion below: >>>> >>>> http://forum.world.st/Problem-with-Mongo-on-Pharo5-collection-already-exist… >>>> To start a new topic under Pharo Smalltalk Users, email [hidden email] >>>> <http://user/SendEmail.jtp?type=node&node=4897348&i=1> >>>> To unsubscribe from Pharo Smalltalk Users, click here. >>>> NAML >>>> <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> >>>> >>> >>> >>> ------------------------------ >>> View this message in context: Re: Problem with Mongo on Pharo5 >>> ("collection already exists") >>> <http://forum.world.st/Problem-with-Mongo-on-Pharo5-collection-already-exist…> >>> >>> Sent from the Pharo Smalltalk Users mailing list archive >>> <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> at >>> Nabble.com <http://nabble.com/>. >>> >> >> >> >> >> ------------------------------ >> If you reply to this email, your message will be added to the discussion >> below: >> >> http://forum.world.st/Problem-with-Mongo-on-Pharo5-collection-already-exist… >> To start a new topic under Pharo Smalltalk Users, email <a >> href="x-msg://138/user/SendEmail.jtp?type=node&node=4897384&i=1" >> target="_top" rel="nofollow" link="external" class="">[hidden email] >> To unsubscribe from Pharo Smalltalk Users, click here. >> NAML >> <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> >> > > > ------------------------------ > View this message in context: Re: Problem with Mongo on Pharo5 > ("collection already exists") > <http://forum.world.st/Problem-with-Mongo-on-Pharo5-collection-already-exist…> > Sent from the Pharo Smalltalk Users mailing list archive > <http://forum.world.st/Pharo-Smalltalk-Users-f1310670.html> at Nabble.com > <http://nabble.com/>. > > > > > ------------------------------ > If you reply to this email, your message will be added to the discussion > below: > > http://forum.world.st/Problem-with-Mongo-on-Pharo5-collection-already-exist… > To start a new topic under Pharo Smalltalk Users, email > ml-node+s1294792n1310670h65(a)n4.nabble.com > To unsubscribe from Pharo Smalltalk Users, click here > <http://forum.world.st/template/NamlServlet.jtp?macro=unsubscribe_by_code&no…> > . > NAML > <http://forum.world.st/template/NamlServlet.jtp?macro=macro_viewer&id=instan…> > -- View this message in context: http://forum.world.st/Problem-with-Mongo-on-Pharo5-collection-already-exist… Sent from the Pharo Smalltalk Users mailing list archive at Nabble.com.

May 25, 2016