January 2010 - Pharo-dev - lists.pharo.org

[Pharo-project] What happens with new preferences?

by Mariano Martinez Peck

Hi Alain. I have a simple question. I know you migrated all preferences from 1.0 to 1.1 to your new cool scheme. Now....what happened with the new preferences that we crated in 1.0 since you did the migration ? Is there a list of "pending" migrations so that we are aware to put them then in 1.1 ? Right now I remember two: - Enable/disable the update stream - Use old / new NetNameResolver. Cheers Mariano

Jan. 28, 2010

Re: [Pharo-project] UseOldNetwork possible workaround Was: Re: Bug in NetNameResolver on PharoCore 10508?

by Mariano Martinez Peck

2010/1/28 Levente Uzonyi <leves(a)elte.hu> > On Thu, 28 Jan 2010, Mariano Martinez Peck wrote: > > Thanks Miguel. I tried but here in the residence I have a proxy to with >> user >> and password. To use Monticello or whatever, I always need to evaluate >> this: >> >> HTTPSocket useProxyServerNamed: '10.100.1.4' port: 9090 >> proxyUser: 'XXX' password: 'YYY' >> >> or >> >> HTTPSocket proxyUser: 'XXX' password: 'YYY'. >> >> >> The problem is that with NetNameResolver I cannot get trough the proxy. >> Do >> > > If you only have an HTTP proxy, DNS won't work (but you don't really need > that, because the proxy will resolve the domain names). So that's normal. > > Thanks Levente. As you can see, I am a totally newbie with this stuff :( Ok, this time I cannot be tester. > > Levente > > > someone know how can I set the username and password so that to use >> NetNameResolver? >> >> Sorry, I tried to test it ;) >> >> Mariano >> >> On Thu, Jan 28, 2010 at 6:38 PM, StÃ©phane Ducasse < >> stephane.ducasse(a)inria.fr >> >>> wrote: >>> >> >> Really thanks for all your energy on that. >>> I have some administrative taks to do now but I will give a try just >>> after. >>> >>> On Jan 28, 2010, at 6:06 PM, Miguel Enrique CobÃ¡ Martinez wrote: >>> >>> >>>> From Socket class >> initializeNetwork: >>>>> >>>> >>>> "Initialize the network drivers and the NetNameResolver. Do nothing >>>> >>> if >>> >>>> the network is already initialized." >>>> "Note: The network must be re-initialized every time Squeak starts >>>> >>> up, >>> >>>> so applications that persist across snapshots should be prepared to >>>> re-initialize the network as needed. Such applications should call >>>> 'Socket initializeNetwork' before every network transaction. " >>>> >>>> NetNameResolver initializeNetwork >>>> >>>> This explains why the initializeNetwork must be called *before* every >>>> network transaction. Between image restarts the network isn't guaranteed >>>> to remain. >>>> >>>> I propose to create a new preference (I know that they are banned but we >>>> need a workaround for 1.0 release) and then each user can, without >>>> modify the NetNameResolver class >>initializeNetwork, change the setting >>>> to the value that works for him/her. >>>> >>>> First evaluate: >>>> >>>> Preferences addPreference: #useOldNetwork categories: >>>> #(general network) >>>> default: false balloonHelp: 'Enable/disable the use of the old >>>> network code in making network connections. You need to save and restart >>>> the image to this preference to take effect' >>>> projectLocal: false changeInformee: nil changeSelector: nil. >>>> >>>> to create the preference in a PharoCore 10508 image. >>>> >>>> Then load >>>> >>>> Network-Kernel-MiguelCoba.22 >>>> >>>> from PharoInbox. >>>> >>>> Pay attention that when you change the preference, it is not refected >>>> immediately. You need to: >>>> >>>> 1. Open the image with the wrong value of the Preference >>>> 2. Change the preference >>>> Preferences enable: #useOldNetwork >>>> >>>> or >>>> >>>> Preferences disable: #useOldNetwork >>>> 3. Save the image >>>> 4. Restart the saved image >>>> 5. Evaluate: >>>> NetNameResolver initializeNetwork >>>> >>>> or some way use the network (open a monticello browser for example, so >>>> that initializeNetwork is called) >>>> >>>> 6. Test that the preference is being used: >>>> >>>> NetNameResolver useOldNetwork -> value of preference >>>> >>>> 7. Test that resolves correctly an address: >>>> >>>> NetNameResolver addressForName: 'www.yahoo.com' -> >>>> 209.131.36.158(f1.www.vip.sp1.yahoo.com),0(0) >>>> >>>> 8. Save the new image, now with the new preference. >>>> >>>> I added this workaround as a fix to issue 1884 and changed status to >>>> fixed. >>>> >>>> Can you give it a try please and if so, generate a new image for >>>> PharoCore? >>>> >>>> Cheers >>>> -- >>>> Miguel CobÃ¡ >>>> http://miguel.leugim.com.mx >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 28, 2010

Re: [Pharo-project] Fun with ProfStef

by Mariano Martinez Peck

Danny: You don't have an idea of how much important this is for the Pharo community. Having good documentation, tutorials and so on, is a KEY aspect from my point of view. So thanks to Laurent for the initiative and you for the work too. Regarding your changes, I like them. I have a couple of thoughts: - I would revome the buttons to go next and return. Actually, I wouldn't just remove the "next" button until it was not first done by code. Then you can show it (for that lesson). There are some places where the author has to think to go to the text lesson. For example, in the double cascade method. So, if you have the button...that good trick has no sense. - I really like the idea that when someone does a tool, it can register its own tutorial somewhere. Then you can browse all the tutorials. Take this 3 examples: * WorkingSets from Romain: there is a cool workspace that explains that. But....who see it ? nobody.... * Algernon. The same. It has a welcome workspace. Who see it ? nobody * ScriptManager: the same So...I would really love that each of those projects can define in a class side initialize method for example, something like this: Algernon class >> initialize ProfStef registerNewTutorial: self algernonTutorial. ProfStef registerNewTutorial: aTutorial self addTutorial: aTutorial or something like that... BTW, can someone create tutorials for that? the workspaces are already written, so maybe it is too much work. - I found a little bug in the UI. If you double click on a lesson, a debugger comes. Can you reproduce it ? - Maybe you can integrate this in "Tools -> More -> ProfStef Tutorials" - For Pharo 1.0 release, I will include the workspace version (the old one) as I don't want to incorporate new stuff. Only IMPORTANT bug fixes. But of course, it will included in next images. Continue with your work!!! Cheers Mariano 2010/1/28 Danny Chan <chan_dhf(a)yahoo.de> > Hi all! > I have pushed a version to Monticello that has a bit of a GUI with nicer > navigation, see the screenshot. I did not find out how to place the buttons > better, and I don't know how to tell the tree morph to select another entry > when I navigate through the lessons using the buttons or the workspace > contents. Please tell me what you think about this. Since I know how little > Smalltalk I really know, I certainly managed to destroy something, so > please > have a look and tell me what to do better. > > Here are a few ideas I've had, which I as a relative beginner would find > really > neat in an interactive tutorial application. As time allows, I would try to > implement at least some of the points below: > > - Clickable items in the text window. So that a tutorial writer could for > example write something like this: > <code>SystemWindow new openInWorld</code> > , and the code together with a button saying 'doit' would appear. So in > principle a markup language for interactive tutorials which adds a bit of > interesting short cut functionality and eye candy to the tutorial. > > - Tabbed browsing for having several tutorials opened at the same time > > - A button saying 'save lesson', that overwrites the appropriate method > with > the current state of the workspace; users can annotate the tutorial with > their > own notes or experiments; also the ability to add additional lessons > > - A button to push the current tutorial with all the additional annotations > to > a Monticello repository, from which future versions for everyone can be > generated. Wiki for interactive tutorials! > > - Some additional functionality to generate a whole new tutorial from > within > the tutorial browser > > - (Semi-)Automatic update of tutorials > > - And, of course, many, many tutorials. Wouldn't it be great to have a > tutorial for all the important and interesting aspects of a system, and > even > for every additional package you download? With the system Laurent > designed, > writing a tutorial is only so very slightly harder than writing example > classes and methods, but so much more expressive and approacheable for > someone > new. > > Cheers, Danny > > > Am Mittwoch, 27. Januar 2010 19:00:25 schrieb laurent laffont: > > 2010/1/27 Mariano Martinez Peck <marianopeck(a)gmail.com> > > > > > I forgot to ask.... > > > > > > Does the DEVImageWorkspaces openGettingStartedWorkspace still make > > > sense having ProfStef ? > > > > > > Can you take a look and "merge" it to ProfStef if there is something > cool > > > not included by Stef ? :) > > > > > > I would like to have only one reference form the Pharo welcome > workspace. > > > > > > Thanks > > > > > > Mariano > > > > I agree for merging > > > > I will put these snippets from getting started in ProfStef: > > 42 explore > > Date today explore > > 'abc' asUppercase. > > 'Hello World' reverse. > > > > There's cool comments too. > > > > I put global Read & Write on ProfStef so everybody can destroy it :) > > > > > > Laurent > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 28, 2010

Re: [Pharo-project] Fun with ProfStef

by Dale Henrichs

Danny, I like what I see...As the number of tutorials goes up there might be the need for more nesting levels (Library-->Books-->Chapters->>Lessons?) and a search feature ... just thinking out loud. In putting together a couple of ProfStef tutorials last weekend, I found that I'd like to be able to #goto a lesson (out of sequence), essentially hitting a branch point where the student can skip a set of lessons or move to a different set of lessons. My thought was something like: ProfStef goto: #lesson15 "jump to lesson15" ProfStef push: AnotherTutorial "start AnotherTutorial in-place" ProfStef pop "exit AnotherTutorial and return push point" ProfStef push: AnotherTutorial to: #lesson15 "start AnotherTutorial at lesson15" Since goto doesn't exist yet, I ended up doing a #goOn to another tutorial when I hit a branch in the lesson, but that leads to an unnecessary explosion in the number of tutorials I had to create. Good work! Dale ----- "Danny Chan" <chan_dhf(a)yahoo.de> wrote: | Hi all! | I have pushed a version to Monticello that has a bit of a GUI with | nicer | navigation, see the screenshot. I did not find out how to place the | buttons | better, and I don't know how to tell the tree morph to select another | entry | when I navigate through the lessons using the buttons or the workspace | | contents. Please tell me what you think about this. Since I know how | little | Smalltalk I really know, I certainly managed to destroy something, so | please | have a look and tell me what to do better. | | Here are a few ideas I've had, which I as a relative beginner would | find really | neat in an interactive tutorial application. As time allows, I would | try to | implement at least some of the points below: | | - Clickable items in the text window. So that a tutorial writer could | for | example write something like this: | <code>SystemWindow new openInWorld</code> | , and the code together with a button saying 'doit' would appear. So | in | principle a markup language for interactive tutorials which adds a bit | of | interesting short cut functionality and eye candy to the tutorial. | | - Tabbed browsing for having several tutorials opened at the same | time | | - A button saying 'save lesson', that overwrites the appropriate | method with | the current state of the workspace; users can annotate the tutorial | with their | own notes or experiments; also the ability to add additional lessons | | - A button to push the current tutorial with all the additional | annotations to | a Monticello repository, from which future versions for everyone can | be | generated. Wiki for interactive tutorials! | | - Some additional functionality to generate a whole new tutorial from | within | the tutorial browser | | - (Semi-)Automatic update of tutorials | | - And, of course, many, many tutorials. Wouldn't it be great to have a | | tutorial for all the important and interesting aspects of a system, | and even | for every additional package you download? With the system Laurent | designed, | writing a tutorial is only so very slightly harder than writing | example | classes and methods, but so much more expressive and approacheable for | someone | new. | | Cheers, Danny | | | Am Mittwoch, 27. Januar 2010 19:00:25 schrieb laurent laffont: | > 2010/1/27 Mariano Martinez Peck <marianopeck(a)gmail.com> | > | > > I forgot to ask.... | > > | > > Does the DEVImageWorkspaces openGettingStartedWorkspace still | make | > > sense having ProfStef ? | > > | > > Can you take a look and "merge" it to ProfStef if there is | something cool | > > not included by Stef ? :) | > > | > > I would like to have only one reference form the Pharo welcome | workspace. | > > | > > Thanks | > > | > > Mariano | > | > I agree for merging | > | > I will put these snippets from getting started in ProfStef: | > 42 explore | > Date today explore | > 'abc' asUppercase. | > 'Hello World' reverse. | > | > There's cool comments too. | > | > I put global Read & Write on ProfStef so everybody can destroy it | :) | > | > | > Laurent | > | | _______________________________________________ | Pharo-project mailing list | Pharo-project(a)lists.gforge.inria.fr | http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 28, 2010

Re: [Pharo-project] Fun with ProfStef

by laurent laffont

Hi Danny, > I have pushed a version to Monticello that has a bit of a GUI with nicer > navigation, see the screenshot. I did not find out how to place the buttons > better, and I don't know how to tell the tree morph to select another entry > when I navigate through the lessons using the buttons or the workspace > contents. Please tell me what you think about this. Since I know how little > Smalltalk I really know, I certainly managed to destroy something, so > please > have a look and tell me what to do better. > The GUI you write is great, it push ProfStef from an interactive tutorial to an integrated help system. But :) I think we should keep the idea of the interactive tutorial (the basic LessonView) using ProfStef go. Because ProfStef go is a little game, it must be attractive, funny. I like the idea of ProfStef which talk to the user and interact. My inspiration was http://tryruby.org/ So IMHO you should put all your changes in a new class, like TutorialBrowser. So we will have: - "ProfStef go" for the interactive tutorial - "TutorialBrowser open" for the pseudo-help system. This way we can keep existing classes clean. And take care of unit tests and class comments :) . Cheers, Laurent > > Here are a few ideas I've had, which I as a relative beginner would find > really > neat in an interactive tutorial application. As time allows, I would try to > implement at least some of the points below: > > - Clickable items in the text window. So that a tutorial writer could for > example write something like this: > <code>SystemWindow new openInWorld</code> > , and the code together with a button saying 'doit' would appear. So in > principle a markup language for interactive tutorials which adds a bit of > interesting short cut functionality and eye candy to the tutorial. > > - Tabbed browsing for having several tutorials opened at the same time > > - A button saying 'save lesson', that overwrites the appropriate method > with > the current state of the workspace; users can annotate the tutorial with > their > own notes or experiments; also the ability to add additional lessons > > - A button to push the current tutorial with all the additional annotations > to > a Monticello repository, from which future versions for everyone can be > generated. Wiki for interactive tutorials! > > - Some additional functionality to generate a whole new tutorial from > within > the tutorial browser > > - (Semi-)Automatic update of tutorials > > - And, of course, many, many tutorials. Wouldn't it be great to have a > tutorial for all the important and interesting aspects of a system, and > even > for every additional package you download? With the system Laurent > designed, > writing a tutorial is only so very slightly harder than writing example > classes and methods, but so much more expressive and approacheable for > someone > new. > > Cheers, Danny > > > Am Mittwoch, 27. Januar 2010 19:00:25 schrieb laurent laffont: > > 2010/1/27 Mariano Martinez Peck <marianopeck(a)gmail.com> > > > > > I forgot to ask.... > > > > > > Does the DEVImageWorkspaces openGettingStartedWorkspace still make > > > sense having ProfStef ? > > > > > > Can you take a look and "merge" it to ProfStef if there is something > cool > > > not included by Stef ? :) > > > > > > I would like to have only one reference form the Pharo welcome > workspace. > > > > > > Thanks > > > > > > Mariano > > > > I agree for merging > > > > I will put these snippets from getting started in ProfStef: > > 42 explore > > Date today explore > > 'abc' asUppercase. > > 'Hello World' reverse. > > > > There's cool comments too. > > > > I put global Read & Write on ProfStef so everybody can destroy it :) > > > > > > Laurent > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

Jan. 28, 2010

Re: [Pharo-project] Fun with ProfStef

by Danny Chan

Hi all! I have pushed a version to Monticello that has a bit of a GUI with nicer navigation, see the screenshot. I did not find out how to place the buttons better, and I don't know how to tell the tree morph to select another entry when I navigate through the lessons using the buttons or the workspace contents. Please tell me what you think about this. Since I know how little Smalltalk I really know, I certainly managed to destroy something, so please have a look and tell me what to do better. Here are a few ideas I've had, which I as a relative beginner would find really neat in an interactive tutorial application. As time allows, I would try to implement at least some of the points below: - Clickable items in the text window. So that a tutorial writer could for example write something like this: <code>SystemWindow new openInWorld</code> , and the code together with a button saying 'doit' would appear. So in principle a markup language for interactive tutorials which adds a bit of interesting short cut functionality and eye candy to the tutorial. - Tabbed browsing for having several tutorials opened at the same time - A button saying 'save lesson', that overwrites the appropriate method with the current state of the workspace; users can annotate the tutorial with their own notes or experiments; also the ability to add additional lessons - A button to push the current tutorial with all the additional annotations to a Monticello repository, from which future versions for everyone can be generated. Wiki for interactive tutorials! - Some additional functionality to generate a whole new tutorial from within the tutorial browser - (Semi-)Automatic update of tutorials - And, of course, many, many tutorials. Wouldn't it be great to have a tutorial for all the important and interesting aspects of a system, and even for every additional package you download? With the system Laurent designed, writing a tutorial is only so very slightly harder than writing example classes and methods, but so much more expressive and approacheable for someone new. Cheers, Danny Am Mittwoch, 27. Januar 2010 19:00:25 schrieb laurent laffont: > 2010/1/27 Mariano Martinez Peck <marianopeck(a)gmail.com> > > > I forgot to ask.... > > > > Does the DEVImageWorkspaces openGettingStartedWorkspace still make > > sense having ProfStef ? > > > > Can you take a look and "merge" it to ProfStef if there is something cool > > not included by Stef ? :) > > > > I would like to have only one reference form the Pharo welcome workspace. > > > > Thanks > > > > Mariano > > I agree for merging > > I will put these snippets from getting started in ProfStef: > 42 explore > Date today explore > 'abc' asUppercase. > 'Hello World' reverse. > > There's cool comments too. > > I put global Read & Write on ProfStef so everybody can destroy it :) > > > Laurent >

Jan. 28, 2010

Re: [Pharo-project] For those who use Nabble ....

by Stan Shepherd

Nice one. Is it possible to get Metacello in the mix as well? ...Stan -- View this message in context: http://n4.nabble.com/For-those-who-use-Nabble-tp1310998p1392340.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

Jan. 28, 2010

Re: [Pharo-project] ConfigurationOfSeaside available

by Dale Henrichs

Miguel, There were several factors: 1) It isn't possible to upgrade from Seaside2.8 to Seaside3.0. In a single configuration, I expect to be able to #load: '2.0' and later #load: '2.4' and have the right thing happen 2) 2.8 and 3.0 are more like separate web frameworks. If you use #loadLatestVersion you will get 3.0 every time. There needs to be a way to #loadLatestVersion for 2.8 independent of 3.0 3) The code bases for Magritte and Pier have forked as well. And the issues in point 1 and 2 apply to Magritte and Pier. 4) ConfigurationOfSeaside detects whether 2.8 or 3.0 is loaded and will not allow you to "mix the streams". This would be doable but much more complex if it was necessary to add the same logic to all 8 configs involved. 5) To load Magritte/Pier one must choose which version of Seaside to use, so I think it is much more obvious layed out in ConfigurationOfSeaside, especially with the doits. I think that the simple Seaside workspace makes the complex problem understandable. 6) ConfigurationOfSeaside has many parrallels to ConfigurationOfPharo or ConfigurationOfGLASS. You need a simple starting point and once you understand what you want to do, you can clone ConfigurationOfSeaside and pare it down to the projects important to you and add in your own projects as well. In the end I think it is a good strategy to create a "configuration of projects" (like ConfigurationOfPharo) to bring the collection of related projects together. There probably should be a ConfigurationofWebFrameworks that provides one stop shopping for Aida, Iliad, and Seaside and any other web frameworks... Dale ----- "Miguel Enrique CobÃ¡ Martinez" <miguel.coba(a)gmail.com> wrote: | El mar, 26-01-2010 a las 17:14 -0800, Dale Henrichs escribiÃ³: | > First load the configuration: | > Gofer new | > squeaksource: 'MetacelloRepository'; | > package: 'ConfigurationOfSeaside'; | > load. | > | > Then pick the Seaside variant you want to load: | > | > "Seaside 2.8" | > ConfigurationOfSeaside project latestVersion load: 'Seaside 2.8'. | > ConfigurationOfSeaside project latestVersion load: 'Seaside 2.8 | Examples'. | > ConfigurationOfSeaside project latestVersion load: 'Magritte'. | > ConfigurationOfSeaside project latestVersion load: 'Magritte | Tests'. | > ConfigurationOfSeaside project latestVersion load: 'Pier'. | > ConfigurationOfSeaside project latestVersion load: 'Pier Tests'. | > ConfigurationOfSeaside project latestVersion load: 'Pier AddOns'. | > | > "Seaside 3.0" | > ConfigurationOfSeaside project latestVersion load: 'Seaside 3.0'. | > ConfigurationOfSeaside project latestVersion load: 'Seaside 3.0 | Tests'. | > ConfigurationOfSeaside project latestVersion load: 'Magritte2'. | > ConfigurationOfSeaside project latestVersion load: 'Magritte2 | Tests'. | > ConfigurationOfSeaside project latestVersion load: 'Pier2'. | > ConfigurationOfSeaside project latestVersion load: 'Pier2 Tests'. | > ConfigurationOfSeaside project latestVersion load: 'Pier2 | AddOns'. | > | > I've tested the various loads with PharoCore-1.0-10508rc2. Should | work fine in Dev variants as well... | > | | Hi Dale, | | first I thought that you had merged the ConfigurationOfSeaside28 and | ConfigurationOfSeaside30 in a single configuration but I saw, when | loading this new config, that it only references the old ones. | There is a reason to do this and not to unify them in a single | package? | | I must say that externally isn't a problem, it works perfect. Just | want | to know the "how-to" part of this. Maybe there is some guideline | underlying here that I would like to know :) | | Thanks | | | | > Dale | > | > _______________________________________________ | > Pharo-project mailing list | > Pharo-project(a)lists.gforge.inria.fr | > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project | | -- | Miguel CobÃ¡ | http://miguel.leugim.com.mx

Jan. 28, 2010

Re: [Pharo-project] UseOldNetwork possible workaround Was: Re: Bug in NetNameResolver on PharoCore 10508?

by Levente Uzonyi

On Thu, 28 Jan 2010, Mariano Martinez Peck wrote: > Thanks Miguel. I tried but here in the residence I have a proxy to with user > and password. To use Monticello or whatever, I always need to evaluate this: > > HTTPSocket useProxyServerNamed: '10.100.1.4' port: 9090 > proxyUser: 'XXX' password: 'YYY' > > or > > HTTPSocket proxyUser: 'XXX' password: 'YYY'. > > > The problem is that with NetNameResolver I cannot get trough the proxy. Do If you only have an HTTP proxy, DNS won't work (but you don't really need that, because the proxy will resolve the domain names). So that's normal. Levente > someone know how can I set the username and password so that to use > NetNameResolver? > > Sorry, I tried to test it ;) > > Mariano > > On Thu, Jan 28, 2010 at 6:38 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr >> wrote: > >> Really thanks for all your energy on that. >> I have some administrative taks to do now but I will give a try just after. >> >> On Jan 28, 2010, at 6:06 PM, Miguel Enrique CobÃ¡ Martinez wrote: >> >>> >>>> From Socket class >> initializeNetwork: >>> >>> "Initialize the network drivers and the NetNameResolver. Do nothing >> if >>> the network is already initialized." >>> "Note: The network must be re-initialized every time Squeak starts >> up, >>> so applications that persist across snapshots should be prepared to >>> re-initialize the network as needed. Such applications should call >>> 'Socket initializeNetwork' before every network transaction. " >>> >>> NetNameResolver initializeNetwork >>> >>> This explains why the initializeNetwork must be called *before* every >>> network transaction. Between image restarts the network isn't guaranteed >>> to remain. >>> >>> I propose to create a new preference (I know that they are banned but we >>> need a workaround for 1.0 release) and then each user can, without >>> modify the NetNameResolver class >>initializeNetwork, change the setting >>> to the value that works for him/her. >>> >>> First evaluate: >>> >>> Preferences addPreference: #useOldNetwork categories: >>> #(general network) >>> default: false balloonHelp: 'Enable/disable the use of the old >>> network code in making network connections. You need to save and restart >>> the image to this preference to take effect' >>> projectLocal: false changeInformee: nil changeSelector: nil. >>> >>> to create the preference in a PharoCore 10508 image. >>> >>> Then load >>> >>> Network-Kernel-MiguelCoba.22 >>> >>> from PharoInbox. >>> >>> Pay attention that when you change the preference, it is not refected >>> immediately. You need to: >>> >>> 1. Open the image with the wrong value of the Preference >>> 2. Change the preference >>> Preferences enable: #useOldNetwork >>> >>> or >>> >>> Preferences disable: #useOldNetwork >>> 3. Save the image >>> 4. Restart the saved image >>> 5. Evaluate: >>> NetNameResolver initializeNetwork >>> >>> or some way use the network (open a monticello browser for example, so >>> that initializeNetwork is called) >>> >>> 6. Test that the preference is being used: >>> >>> NetNameResolver useOldNetwork -> value of preference >>> >>> 7. Test that resolves correctly an address: >>> >>> NetNameResolver addressForName: 'www.yahoo.com' -> >>> 209.131.36.158(f1.www.vip.sp1.yahoo.com),0(0) >>> >>> 8. Save the new image, now with the new preference. >>> >>> I added this workaround as a fix to issue 1884 and changed status to >>> fixed. >>> >>> Can you give it a try please and if so, generate a new image for >>> PharoCore? >>> >>> Cheers >>> -- >>> Miguel CobÃ¡ >>> http://miguel.leugim.com.mx >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >

Jan. 28, 2010

Re: [Pharo-project] UseOldNetwork possible workaround Was: Re: Bug in NetNameResolver on PharoCore 10508?

by StÃ©phane Ducasse

> Thanks Miguel. I tried but here in the residence I have a proxy to with user and password. To use Monticello or whatever, I always need to evaluate this: > > HTTPSocket useProxyServerNamed: '10.100.1.4' port: 9090 > proxyUser: 'XXX' password: 'YYY' > > or > > HTTPSocket proxyUser: 'XXX' password: 'YYY'. > > > The problem is that with NetNameResolver I cannot get trough the proxy. Do someone know how can I set the username and password so that to use NetNameResolver? > > Sorry, I tried to test it ;) mariano did you check the entry torsten just posted http://code.google.com/p/pharo/issues/detail?id=1888 Stef > > Mariano > > On Thu, Jan 28, 2010 at 6:38 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > Really thanks for all your energy on that. > I have some administrative taks to do now but I will give a try just after. > > On Jan 28, 2010, at 6:06 PM, Miguel Enrique CobÃ¡ Martinez wrote: > > > > >> From Socket class >> initializeNetwork: > > > > "Initialize the network drivers and the NetNameResolver. Do nothing if > > the network is already initialized." > > "Note: The network must be re-initialized every time Squeak starts up, > > so applications that persist across snapshots should be prepared to > > re-initialize the network as needed. Such applications should call > > 'Socket initializeNetwork' before every network transaction. " > > > > NetNameResolver initializeNetwork > > > > This explains why the initializeNetwork must be called *before* every > > network transaction. Between image restarts the network isn't guaranteed > > to remain. > > > > I propose to create a new preference (I know that they are banned but we > > need a workaround for 1.0 release) and then each user can, without > > modify the NetNameResolver class >>initializeNetwork, change the setting > > to the value that works for him/her. > > > > First evaluate: > > > > Preferences addPreference: #useOldNetwork categories: > > #(general network) > > default: false balloonHelp: 'Enable/disable the use of the old > > network code in making network connections. You need to save and restart > > the image to this preference to take effect' > > projectLocal: false changeInformee: nil changeSelector: nil. > > > > to create the preference in a PharoCore 10508 image. > > > > Then load > > > > Network-Kernel-MiguelCoba.22 > > > > from PharoInbox. > > > > Pay attention that when you change the preference, it is not refected > > immediately. You need to: > > > > 1. Open the image with the wrong value of the Preference > > 2. Change the preference > > Preferences enable: #useOldNetwork > > > > or > > > > Preferences disable: #useOldNetwork > > 3. Save the image > > 4. Restart the saved image > > 5. Evaluate: > > NetNameResolver initializeNetwork > > > > or some way use the network (open a monticello browser for example, so > > that initializeNetwork is called) > > > > 6. Test that the preference is being used: > > > > NetNameResolver useOldNetwork -> value of preference > > > > 7. Test that resolves correctly an address: > > > > NetNameResolver addressForName: 'www.yahoo.com' -> > > 209.131.36.158(f1.www.vip.sp1.yahoo.com),0(0) > > > > 8. Save the new image, now with the new preference. > > > > I added this workaround as a fix to issue 1884 and changed status to > > fixed. > > > > Can you give it a try please and if so, generate a new image for > > PharoCore? > > > > Cheers > > -- > > Miguel CobÃ¡ > > http://miguel.leugim.com.mx > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Jan. 28, 2010