- Pharo-dev - lists.pharo.org

Re: [Pharo-dev] Voyage cannot be load

by Norbert Hartl

Am 20.03.2014 um 16:06 schrieb Esteban Lorenzano <estebanlm(a)gmail.com>: > is not a problem of voyage. > Is a problem in grease or magritte :P I know. But what do you think is the cheapest way to get your attention? :P > > I will check itâ¦ but this kind of problems arise time to time and Iâm frankly a bit fed up of them :( > complex system dependencies are often not well managed and metacello is not really good at deciding versions or reporting incompatibilitiesâ¦ so you change the stable in projectB.C and projectA.C reports a problem :( > > honestlyâ¦ not the best :( > > anyway, rant apartâ¦ I will check it as soon as I can spare some minutes. > I know. I would wish we would stop having metacello versions that contain dependencies to symbolic versions. A tool like versionner should rewrite every symbolic version to a number version when producing a release. But this is not that kind of problem. Otherwise I wouldnât have that much trouble to find the cause of the problem. I simply donât get it. thanks for your time, Norbert > Esteban > > On 20 Mar 2014, at 15:47, Norbert Hartl <norbert(a)hartl.name> wrote: > >> I encountered a strange problem while loading voyage. It seems the configuration for magritte or grease is strange. If I load voyage from the configuration browser I get the following screen >> >> <Bildschirmfoto 2014-03-20 um 15.43.56.png> >> >> Any ideas? >> >> Norbert >> > >

March 20, 2014

Re: [Pharo-dev] Voyage cannot be load

by Esteban Lorenzano

is not a problem of voyage. Is a problem in grease or magritte :P I will check itâ¦ but this kind of problems arise time to time and Iâm frankly a bit fed up of them :( complex system dependencies are often not well managed and metacello is not really good at deciding versions or reporting incompatibilitiesâ¦ so you change the stable in projectB.C and projectA.C reports a problem :( honestlyâ¦ not the best :( anyway, rant apartâ¦ I will check it as soon as I can spare some minutes. Esteban On 20 Mar 2014, at 15:47, Norbert Hartl <norbert(a)hartl.name> wrote: > I encountered a strange problem while loading voyage. It seems the configuration for magritte or grease is strange. If I load voyage from the configuration browser I get the following screen > > <Bildschirmfoto 2014-03-20 um 15.43.56.png> > > Any ideas? > > Norbert >

March 20, 2014

Re: [Pharo-dev] Voyage cannot be load

by Sven Van Caekenberghe

This is the second report of Grease-Pharo20-Core not loading properly, I believe it might have something to do with an error that was made with a Seaside configuration, see the Seaside mailing list (but there are no details there, apart from the fact that an existing version was changed) On 20 Mar 2014, at 15:47, Norbert Hartl <norbert(a)hartl.name> wrote: > I encountered a strange problem while loading voyage. It seems the configuration for magritte or grease is strange. If I load voyage from the configuration browser I get the following screen > > <Bildschirmfoto 2014-03-20 um 15.43.56.png> > > Any ideas? > > Norbert >

March 20, 2014

Nautilus keyboard behavior

by Stephan Eggermont

13100 triggered me to take a look at keyboard based navigation in Nautilus. These should probably be a number of different issues. There seems to be no way to get from the text pane back to methods-categories-classes-packages , both tab and right-arrow are captured. How do I open the menu on one of the top panes in Nautilus? How do I open the History navigator? Iâd expect groups and hierarchy to be selectable with a key combination when the packages pane is selected. Menu behaves interesting when use with tab key - if you are in a submenu you can tab back to the higher level menu and back down with shift-tab - if you go too far up it only reacts to shift-tab - if there is no submenu, the menu is deselected and it only reacts to shift-tab If I select a class, open the menu, select with keyboard Refactoring, right arrow to select Code rewriting, left arrow to go back and again right arrow, I get a MNU receiver of âboundsâ is nil The world menu behaves slightly different, it has no MNU but just doesnât open the submenu a second time. Moving down and up again restores the submenu. The removeEmtyCategoriesFrom menu item can be selected when there is no class selected. This gives a MNU Stephan

March 20, 2014

Voyage cannot be load

by Norbert Hartl

I encountered a strange problem while loading voyage. It seems the configuration for magritte or grease is strange. If I load voyage from the configuration browser I get the following screen Any ideas? Norbert

March 20, 2014

Re: [Pharo-dev] Phexample / new test framework (was: FileSystem-Git status update 2)

by Max Leske

On 20.03.2014, at 14:33, Sean P. DeNigris <sean(a)clipperadams.com> wrote: > Max Leske wrote >> rewriting our tests with SUnit, moving away from Phexample (for several >> reasons) > > I'm curious about those reasonsâ¦ I think that Phexample is pretty cool and I enjoyed writing tests with it (yes, devs donât usually say that about writing tests :) ). As Esteban said, we donât want to introduce the dependency to Phexample because of the integration. But that is only one reason. Personally I have three issues with Phexample: 1. the more complex a project becomes, the more complex the dependencies between tests get (in my case, chain lengths of 8 - 10). Problems this causes: 1.a there is no visual cue for the dependencies, so you have to try your best with protocols and naming but it just gets very confusing 1.b it becomes more likely to introduce cycles (which often crash your imageâ¦) 1.c it becomes more likely to introduce errors *because of* dependencies (e.g. because I used the wrong selector) and since you assume the dependencies to be fineâ¦ 2. #setUp and #tearDown are executed for every test *even if the test is a dependency*. But in my case I depend on the state that has been established by a test (so maybe I misused Phexample. Unit tests should be self contained. But then again, if they were self contained, would there be a need for dependenciesâ¦?). But that state is destroyed by #setUp and #tearDown. Then again, I *do* need to initialize and destroy some stuff sometimes (which I could to manually, I know; just saying). 3. Especially if you test things that run longer than a couple of milliseconds, the test execution time will grow very fast because of the dependencies. Every test will be run by the suite (n) + every test in a dependency chain (0 < m < inf). That amounts to roughly ~ O(n^2), which is fine for short tests but not if you have longer running tests in there So my take away message from Phexample is: itâs cool to work with and you become pretty fast. Phexample is also cool for TDD because it lets you focus on the problem at hand and everything als can just be assumed to be #given:. But: I would only recommend it for small projects / projects with low complexity (or low number of dependencies). Git has notoriously many dependencies, so I might also just be an outlier (or I may not have understood how Phexample is supposed to work). Sean, regarding your proposal, I am *not* happy with SUnit, so Iâm very happy about any ideas you have :) Cheers, Max > > > > ----- > Cheers, > Sean > -- > View this message in context: http://forum.world.st/FileSystem-Git-status-update-2-tp4749696p4749970.html > Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com. >

March 20, 2014

Re: [Pharo-dev] Couchbase client

by Sven Van Caekenberghe

I am using http://www.squeaksource.com/memcached.html in Pharo On 20 Mar 2014, at 15:36, Benjamin Pollack <benjamin(a)bitquabit.com> wrote: > On Tue, Mar 18, 2014, at 07:06 PM, Esteban A. Maringolo wrote: >> I don't know the exact difference between the clients of Couchbase and >> CouchDB. >> >> I know Couchbase forked from CouchDB, and the REST API is the same. >> Hopefully the CouchDB client will work. > > It probably won't. Couchbase's protocol is basically memcache (and you > can indeed use a memcache library to talk to Couchbase in a pinch), > whereas CouchDB uses a REST protocol over HTTP. I know there used to be > at least one memcache client on Squeaksource; I'd probably see if it's > migrated to SmalltalkHub or similar. > > --Benjamin >

March 20, 2014

Re: [Pharo-dev] Class vars and inst vars of a class

by Sean P. DeNigris

Uko2 wrote > what is the difference between the class variable... pharo-users(a)lists.pharo.org is a better place to ask questions like this, so that they do not get missed amongst the dev threads, and to give the devs' inboxes a break. ----- Cheers, Sean -- View this message in context: http://forum.world.st/Class-vars-and-inst-vars-of-a-class-tp4749910p4749998… Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 20, 2014

Re: [Pharo-dev] Couchbase client

by Benjamin Pollack

On Tue, Mar 18, 2014, at 07:06 PM, Esteban A. Maringolo wrote: > I don't know the exact difference between the clients of Couchbase and > CouchDB. > > I know Couchbase forked from CouchDB, and the REST API is the same. > Hopefully the CouchDB client will work. It probably won't. Couchbase's protocol is basically memcache (and you can indeed use a memcache library to talk to Couchbase in a pinch), whereas CouchDB uses a REST protocol over HTTP. I know there used to be at least one memcache client on Squeaksource; I'd probably see if it's migrated to SmalltalkHub or similar. --Benjamin

March 20, 2014

Re: [Pharo-dev] FileSystem-Git status update 2

by Sean P. DeNigris

On Mar 20, 2014, at 9:43 AM, EstebanLM [via Smalltalk] <ml-node+s1294792n4749977h75(a)n4.nabble.com> wrote: > phexample will notâ¦ be a part of the system Iâd love to standardize on a cutting edge testing framework. There have been so many great ideas (think ruby rspec) in recent times. Right now we have a chicken and egg problem... On one hand we canât express ourselves in ways that are: 1) easy to write 2) document the usage of our code i.e. easy for users to understand, and 3) reduce duplication On the other hand, we canât use libraries that help us do these things for core code. Thus, IMHO - core tests are often the poorest. My must-haves are: - mocks - phexemple-like building-on-previous-test - partial stubs - tables for input My wish list would be a real UI, taking advantage of Smalltalkâs strength, instead of leaning on the code browser and class structure, which are implementation details which constrain our thought unnecessarily. ----- Cheers, Sean -- View this message in context: http://forum.world.st/FileSystem-Git-status-update-2-tp4749696p4749982.html Sent from the Pharo Smalltalk Developers mailing list archive at Nabble.com.

March 20, 2014