[Pharo-dev] Is it possible to load and display pdfs inside pharo ?

I was wondering if there is a library to load and display or at least parse pdf files for pharo.

Re: [Pharo-dev] MessageNotUnderstood: SmallInteger>>isEmpty

Ciao Eliot, > Hi Dario, > > > On Tue, Dec 10, 2013 at 8:12 AM, Dario Trussardi > wrote: > Ciao, > > i work with a new Pharo 2.0 20628 image. > > I do first : > A) Gofer new url: > 'http://smalltalkhub.com/mc/DiegoLont/QCMagritte/main'; package: > 'Confi

[Pharo-dev] self item returns a string

Hi ben Im trying to fix the problem of the finder putting too many string around the arguments. if you type 'a' . 'b' . 'ab' and example you will get '''a''' . '''b''' so I found that displayString self halt. ^ self item asString self item returns a byteString and item is no

[Pharo-dev] is the through working on the debugger?

Hi guys with pavel we think that we found a bug on the through of the debugger (to jump inside a block). Is it a well-known bug? Stef

Re: [Pharo-dev] is the through working on the debugger?

False alert it is working. On Dec 11, 2013, at 10:01 AM, Stéphane Ducasse wrote: > Hi guys > > with pavel we think that we found a bug on the through of the debugger (to > jump inside a block). > Is it a well-known bug? > > Stef

Re: [Pharo-dev] is the through working on the debugger?

reported is only 10332 Issues when using “Through" https://pharo.fogbugz.com/f/cases/10332 On 11 Dec 2013, at 10:01, Stéphane Ducasse wrote: > Hi guys > > with pavel we think that we found a bug on the through of the debugger (to > jump inside a block). > Is it a well-known bug? >

Re: [Pharo-dev] self item returns a string

Sorry but I wrote part of this code 3 years ago, so I really do not remember :( Ben On 11 Dec 2013, at 09:51, Stéphane Ducasse wrote: > Hi ben > > Im trying to fix the problem of the finder putting too many string around the > arguments. > if you type 'a' . 'b' . 'ab' and example > you will g

[Pharo-dev] enabled: and menuRegistration problem

Hi I got a bug with menu (I'm trying to reproduce it but this is a real bug) because in interpretRegistration: aRegistration item enabled ifNil: [ node enabled: boolean not ] ifNotNil: [:boolean | node enabled: boolean ]. I will not

Re: [Pharo-dev] self item returns a string

On Dec 11, 2013, at 10:31 AM, Benjamin wrote: > Sorry but I wrote part of this code 3 years ago, so I really do not remember > :( No problem. We tried during 30 min with pavel but failed. We should have a look again. Stef > > Ben > > On 11 Dec 2013, at 09:51, Stéphane Ducasse wrote: > >

Re: [Pharo-dev] enabled: and menuRegistration problem

Could you provide a way to reproduce it ? Because debugging from within Mail is quite tedious :P Ben On 11 Dec 2013, at 10:20, Stéphane Ducasse wrote: > Hi > > I got a bug with menu (I'm trying to reproduce it but this is a real bug) > > because in > > interpretRegistration: aRegistratio

Re: [Pharo-dev] [ANN] Neo-Caching

This is awesome! Thanks Sven :) Nico Sven Van Caekenberghe writes: > On 10 Dec 2013, at 23:09, Stéphane Ducasse wrote: > >> Sven thanks a lot >> How can we resist to push this in Pharo 30 :) > > That is the idea, and I will do it, but I would first like some > feedback/validation. > >> Stef >>

Re: [Pharo-dev] enabled: and menuRegistration problem

We fixed it :) We moved the extensions to the packages so that we can unload nautilus. > Could you provide a way to reproduce it ? we could not without unloading Nautilus :) > > Because debugging from within Mail is quite tedious :P oh yes. Stef > > Ben > > On 11 Dec 2013, at 10:20, Stéphane

[Pharo-dev] could we stop to create spaghetti code?

EyeInspector should not depend on Nautilus. icon ^ (self value iconOrThumbnailOfSize: 16) ifNil: [ self value class nautilusIcon ] ^^ https://pharo.fogbugz.com/f/cases/12392/EyeInspector-should-not-depend-on-Naut

[Pharo-dev] New screenshots of Roassal 3d

Hi! We are uploaded new screenshots of Roassal 3d: https://www.facebook.com/media/set/?set=a.552518388168096.1073741834.340543479365589&type=3 Roassal3d supports textures, new light model, using camera as a texture, … Cheers, Alexandre -- _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;: Alexan

Re: [Pharo-dev] New screenshots of Roassal 3d

That’s coool :P Ben On 11 Dec 2013, at 11:21, Alexandre Bergel wrote: > Hi! > > We are uploaded new screenshots of Roassal 3d: > https://www.facebook.com/media/set/?set=a.552518388168096.1073741834.340543479365589&type=3 > > Roassal3d supports textures, new light model, using camera a

[Pharo-dev] Nautilus extensions questions

Ben with pavel we are looking at Nautilus extensions because some of them should be moved to the extended packages. Now I was wondering why TClassDescription is extended with menu see below. I imagine that this is because you do not have a classWrapper for the UI. Is it correct? Then I wonder

Re: [Pharo-dev] Nautilus extensions questions

Ask Sebastien since it seems he is the author. I can not help more Ben On 11 Dec 2013, at 11:31, Stéphane Ducasse wrote: > Ben > > with pavel we are looking at Nautilus extensions because some of them should > be moved to the extended packages. > Now I was wondering why > TClassDescription

[Pharo-dev] Package unloading and extensions

This is strange so I report it. When we unload Nautilus package we still get the methods in ThemeIcons with category *Nautilus-contents and antoher one *Nautilus-icons so we thought that unload does not unload extensions whose name is composed (*Nautilus vs. *Nautilus-icons) so we built a case w

Re: [Pharo-dev] Package unloading and extensions

On Dec 11, 2013, at 11:45 AM, Stéphane Ducasse wrote: > This is strange so I report it. > When we unload Nautilus package we still get the methods in ThemeIcons with > category > *Nautilus-contents and antoher one *Nautilus-icons > > so we thought that unload does not unload extensions whose

[Pharo-dev] [Pharo Trick: #0001] - Simple TODO list

Hi, the mailinglist, stackoverflow and other Pharo related medias are typically used in the "here is a question to problem" followed by an "answer from community" style. But lets also think the other way around: if we already have a solution for a problem that others may have too or may have

Re: [Pharo-dev] Nautilus extensions questions

On 11 déc. 2013, at 11:31, Stéphane Ducasse wrote: > Ben > > with pavel we are looking at Nautilus extensions because some of them should > be moved to the extended packages. > Now I was wondering why > TClassDescription is extended with menu see below. > I imagine that this is because you do

Re: [Pharo-dev] [ANN] Neo-Caching

On Tue, Dec 10, 2013 at 11:09 PM, Stéphane Ducasse < stephane.duca...@inria.fr> wrote: > Sven thanks a lot > yes! really cool! > How can we resist to push this in Pharo 30 :) > over my dead body :) but in Pharo 4... > > Stef > > On Dec 10, 2013, at 4:54 PM, Sven Van Caekenberghe wrote: > >

Re: [Pharo-dev] self item returns a string

2013/12/11 Stéphane Ducasse > > On Dec 11, 2013, at 10:31 AM, Benjamin < > benjamin.vanryseghem.ph...@gmail.com> wrote: > > Sorry but I wrote part of this code 3 years ago, so I really do not > remember :( > > > No problem. > We tried during 30 min with pavel but failed. We should have a look aga

Re: [Pharo-dev] self item returns a string

Thanks a lot. I will check and resolve the bug. I wanted to continue working on unloading code so this is why we time bombed our investigation. Stef > > printing strings with quotes and doubling this quotes is done in > Finder>>computeWithMethodFinder: > > node formattedCode printOn: strm. > >

Re: [Pharo-dev] [ANN] Neo-Caching

On Dec 11, 2013, at 12:29 PM, Esteban Lorenzano wrote: > > > > On Tue, Dec 10, 2013 at 11:09 PM, Stéphane Ducasse > wrote: > Sven thanks a lot > > yes! really cool! > > How can we resist to push this in Pharo 30 :) > > over my dead body :) > but in Pharo 4… you are saying that you wil

Re: [Pharo-dev] [ANN] Neo-Caching

Hi, By default, no concurrent access protection takes place, but optionally a semaphore for mutual exclusion can be used. This slows down access. cache useSemaphore. There was enough "awesomes" already :-) so now some critics :-) Wouldn't it be better to rename #useSemaphore to #beThreadSa

Re: [Pharo-dev] Package unloading and extensions

We did another experience: we moved all the methods in *Nautilus extension and unloaded it but it failed. The methods were not unloaded. On Dec 11, 2013, at 11:45 AM, Stéphane Ducasse wrote: > This is strange so I report it. > When we unload Nautilus package we still get the me

Re: [Pharo-dev] Package unloading and extensions

> We did another experience: > we moved all the methods in *Nautilus extension and unloaded it but it > failed. > The methods were not unloaded. In fact this is worse: - we create a new package extensions - did RPackageOrganizer initializeDefaultFromMC. - mov

Re: [Pharo-dev] could we stop to create spaghetti code?

On 11 Dec 2013, at 11:14, Stéphane Ducasse wrote: > EyeInspector should not depend on Nautilus. > > icon > ^ (self value iconOrThumbnailOfSize: 16) > ifNil: [ self value class nautilusIcon ] > > ^^ > > https://pharo

Re: [Pharo-dev] [ANN] Neo-Caching

Hi Jan, On 11 Dec 2013, at 12:49, Jan Vrany wrote: > Hi, > >> By default, no concurrent access protection takes place, but optionally a >> semaphore for mutual exclusion can be used. This slows down access. >> >> cache useSemaphore. >> > > There was enough "awesomes" already :-) so now some

Re: [Pharo-dev] could we stop to create spaghetti code?

And if we are at it, the SpecDebugger still requires the EyeInspector to be the default inspector: https://pharo.fogbugz.com/f/cases/12055/The-Spec-Debugger-should-not-require-the-registered-inspector-to-be-built-on-Spec Cheers, Doru On Wed, Dec 11, 2013 at 1:15 PM, Marcus Denker wrote: > > On

Re: [Pharo-dev] [ANN] Neo-Caching

On 11 Dec 2013, at 12:48, Stéphane Ducasse wrote: > > On Dec 11, 2013, at 12:29 PM, Esteban Lorenzano wrote: > >> >> >> >> On Tue, Dec 10, 2013 at 11:09 PM, Stéphane Ducasse >> wrote: >> Sven thanks a lot >> >> yes! really cool! >> >> How can we resist to push this in Pharo 30 :) >>

[Pharo-dev] Fwd: Categories, packages, and tags [cont'd]

Hi guys, I have a question about the new “PackageTreeModel”… In a previous discussion (https://www.mail-archive.com/pharo-dev@lists.pharo.org/msg09271.html) we discussed about the new package model. Now I understood it but I am wondering one thing. Since Stef said that categories will be remo

Re: [Pharo-dev] [ANN] Neo-Caching

On 11/12/13 12:20, Sven Van Caekenberghe wrote: Hi Jan, On 11 Dec 2013, at 12:49, Jan Vrany wrote: Hi, By default, no concurrent access protection takes place, but optionally a semaphore for mutual exclusion can be used. This slows down access. cache useSemaphore. There was enough "awe

Re: [Pharo-dev] [ANN] Neo-Caching

On 11 Dec 2013, at 13:42, Jan Vrany wrote: > On 11/12/13 12:20, Sven Van Caekenberghe wrote: >> Hi Jan, >> >> On 11 Dec 2013, at 12:49, Jan Vrany wrote: >> >>> Hi, >>> By default, no concurrent access protection takes place, but optionally a semaphore for mutual exclusion can be u

[Pharo-dev] [pharo-project/pharo-core] d296eb: 30636

Branch: refs/heads/3.0 Home: https://github.com/pharo-project/pharo-core Commit: d296eb7bef29cc140bfcb99f7bd1af703295e70b https://github.com/pharo-project/pharo-core/commit/d296eb7bef29cc140bfcb99f7bd1af703295e70b Author: Jenkins Build Server Date: 2013-12-11 (Wed, 11 Dec 2013

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/30636 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] Searchbar in the browser

El 11-12-2013, a las 4:09, Stéphane Ducasse escribió:On Dec 10, 2013, at 11:42 PM, Juraj Kubelka wrote:We can use any regular _expression_. For that reason I am thinking how to do the filter feature more apparent. Maybe a ghost text is enough. I

Re: [Pharo-dev] Searchbar in the browser

Does it means, when I start to type “-P” it will display all the packages which contain class with character “p” or “P”? In order to be consists we should use the same regular expressions as for packages. So, If I want all packages which contain class beginning with “p”, it should be “-^p”. Regu

[Pharo-dev] Tell me about your workflow

Are you using git with your Pharo based software? If you do, are you using filetree? I ask because I'm worried about scale. I have packages (in the order of hundreds of classes) and save delays and package click delays are starting to demand patience in a way that doesn't feel like the right p

Re: [Pharo-dev] Tell me about your workflow

Le 11/12/2013 15:18, Sebastian Sastre a écrit : Are you using git with your Pharo based software? Yes If you do, are you using filetree? gitfiletree (it uses the filetree code path for writing, and a git archive path for reading) I ask because I'm worried about scale. I have packages

Re: [Pharo-dev] Tell me about your workflow

Hi Thierry On Dec 11, 2013, at 12:43 PM, Goubier Thierry wrote: >> >> I have packages (in the order of hundreds of classes) and save delays >> and package click delays are starting to demand patience in a way that >> doesn't feel like the right path > > Which operations ? I didn't remember noti

Re: [Pharo-dev] Tell me about your workflow

I should breath before I type, but you probably already got that I meant redundant writes (not reads)... Anyway.. I was talking with Esteban and he mentions some kind of compatibility metadata. If I'm going to give a leap of faith to filetree repos to save code why should I care about mcz comp

Re: [Pharo-dev] Tell me about your workflow

I know there is a version of filetree without metadata (more compelling for projects that will never use other formats). Dale told me that there was a preview somewhere, but I didn't tested yet (lack of time) and now I cannot find the mail... Dale, can you re-send the link? cheers, Esteban On We

Re: [Pharo-dev] Tell me about your workflow

Le 11/12/2013 15:44, Sebastian Sastre a écrit : Hi Thierry On Dec 11, 2013, at 12:43 PM, Goubier Thierry wrote: I have packages (in the order of hundreds of classes) and save delays and package click delays are starting to demand patience in a way that doesn't feel like the right path Whi

Re: [Pharo-dev] Tell me about your workflow

Esteban, Sebastian, In the filetree code, you will find a format without metadata, but it's not in use anymore. If you use gitfiletree, it will write the metadata for compatibility reasons with filetree, but it will never read it back. I'm pushing code to make filetree robust to absence of

[Pharo-dev] [ANN] traversal-enabled objects with DeepTraverser

Hi, I put together a little implementation for traversals. It is inspired by an original implementation from Mariano. Using DeepTraverser, you can traverse arbitrary graphs by describing the traversal and by specifying the actions you want to perform on the nodes and relations. The code is availa

Re: [Pharo-dev] Tell me about your workflow

Thierry, I know there is a working version... let me search... (5 mins later) here: https://github.com/rjsargent/CypressReferenceImplementation Dale says Richard made a metadata-less version. We should take a look at that. Esteban On Wed, Dec 11, 2013 at 4:28 PM, Goubier Thierry wrote: >

Re: [Pharo-dev] Tell me about your workflow

ah, and IMHO the problem is not about reading... is about writing (if it has to write the metadata each time...). Esteban On Wed, Dec 11, 2013 at 4:24 PM, Esteban Lorenzano wrote: > Thierry, I know there is a working version... let me search... > > (5 mins later) > > > here: > > https://github.

Re: [Pharo-dev] Tell me about your workflow

Thanks. I'll have a look. If this format solves the git merge conflicts, I'll be porting it. But I'll make sure first it doesn't have the performance problems Sebastian is telling about. Because if it is just removing writing the metadata in gitfiletree, it's a 5 minutes job :). Thierry L

Re: [Pharo-dev] Tell me about your workflow

that would be sooo cool. Thanks Thierry! Esteban On Wed, Dec 11, 2013 at 4:39 PM, Goubier Thierry wrote: > Thanks. I'll have a look. > > If this format solves the git merge conflicts, I'll be porting it. But > I'll make sure first it doesn't have the performance problems Sebastian is > telling

Re: [Pharo-dev] Tell me about your workflow

Le 11/12/2013 16:27, Esteban Lorenzano a écrit : ah, and IMHO the problem is not about reading... is about writing (if it has to write the metadata each time...). But, personnaly, I don't know if this is the reason for the lack of performance... I have three hypothesis for Sebastian proble

Re: [Pharo-dev] New screenshots of Roassal 3d

Nice! -C -- Craig Latta www.netjam.org/resume +1 510 984 8117 (Skype rings this until 31 January 2014)

Re: [Pharo-dev] Tell me about your workflow

Without entering in details, a cause for slow package write is dumping all every time. For that strategy, we already have the image save which is magically fast. So, if we make something to scan the code and write only when it's different from what's on disk, then we would be preventing tons of

[Pharo-dev] [Spec] whenSelectedItemsChanged: on TreeModel

Hi, I am experiencing problems with #whenSelectedItemsChanged: on a TreeModel. In particular, the block (i.e., argument of #whenSelectedItemsChanged: gets randomly executed a couple of times (3/4) the second time that the selection happens. The first time is fine. It looks like the registration

[Pharo-dev] Workaround for File Out Package

Hi! I am having a problem when trying to export a Package to .st using Right Click -> Fileout. Here is the case: https://pharo.fogbugz.com/f/cases/7519 Do anyone know a workaround? A way to do it via code? This is a feature we use at several universities in order to provide fast and simple code

Re: [Pharo-dev] Searchbar in the browser

Juraj Kubelka wrote: El 11-12-2013, a las 4:09, Stéphane Ducasse escribió: On Dec 10, 2013, at 11:42 PM, Juraj Kubelka wrote: We can use any regular _expression_. For that reason I

Re: [Pharo-dev] New screenshots of Roassal 3d

Nice indeed. Could you add some of the pictures on the Moose news? Doru On Wed, Dec 11, 2013 at 11:21 AM, Alexandre Bergel wrote: > Hi! > > We are uploaded new screenshots of Roassal 3d: > > https://www.facebook.com/media/set/?set=a.552518388168096.1073741834.340543479365589&type=3 > > Roassal

Re: [Pharo-dev] Tell me about your workflow

Yes, you're right in the general case. But a solution to that general problem will take time to be implemented (time I lack at the moment, sadly) and if the main gain is a few % because it's writing the version file and the metadata for methods which are the "slow" factors, then we'll have wor

Re: [Pharo-dev] Workaround for File Out Package

Hi Alf, that's not the case :) anyway... if you check at the implementation of RPackage>>#fileOut, you will be able to build a workaround. cheers, Esteban On Wed, Dec 11, 2013 at 4:46 PM, Alfredo Sanzo wrote: > Hi! > > I am having a problem when trying to export a Package to .st using Right

[Pharo-dev] [pharo-project/pharo-core]

Branch: refs/tags/30637 Home: https://github.com/pharo-project/pharo-core

Re: [Pharo-dev] [ANN] Neo-Caching

On 11 Dec 2013, at 14:03, Sven Van Caekenberghe wrote: > > On 11 Dec 2013, at 13:42, Jan Vrany wrote: > >> On 11/12/13 12:20, Sven Van Caekenberghe wrote: >>> Hi Jan, >>> >>> On 11 Dec 2013, at 12:49, Jan Vrany wrote: >>> Hi, > By default, no concurrent access protection tak

Re: [Pharo-dev] Tell me about your workflow

ok, if saving is dumping all, then 3 is confirmed? After the first commit, I'd say so. about 2, I don't know. I'm available to make tests and measure results have a nice trip, keep us tuned about any progress On Dec 11, 2013, at 2:09 PM, Goubier Thierry wrote: > Yes, you're right in the

Re: [Pharo-dev] Workaround for File Out Package

Oh, sorry, wrong link. https://pharo.fogbugz.com/f/cases/12409/DNU-RPackage-item-when-FileOut 2013/12/11 Alfredo Sanzo > Hi! > > I am having a problem when trying to export a Package to .st using Right > Click -> Fileout. > Here is the case: > https://pharo.fogbugz.com/f/cases/7519 > > Do anyon

Re: [Pharo-dev] Workaround for File Out Package

"Alfredo Sanzo" wrote: >Oh, sorry, wrong link. >https://pharo.fogbugz.com/f/cases/12409/DNU-RPackage-item-when-FileOut   I can confirm the slice #12409 from Esteban is working, see issue @Alfredo: either load it from Pharo30Inbox or wait until it is integrated Bye T.

Re: [Pharo-dev] [Spec] whenSelectedItemsChanged: on TreeModel

As I said to Martin, I will investigate why, but it’s a bit tricky Must be some issue in MorphTreeMorph I introduced recently Ben On 11 Dec 2013, at 16:46, Roberto Minelli wrote: > Hi, > > I am experiencing problems with #whenSelectedItemsChanged: on a TreeModel. > > In particular, the block

Re: [Pharo-dev] MessageNotUnderstood: SmallInteger>>isEmpty

Hi Dario, On Wed, Dec 11, 2013 at 12:41 AM, Dario Trussardi < dario.trussa...@tiscali.it> wrote: > Ciao Eliot, > > > Hi Dario, > > > On Tue, Dec 10, 2013 at 8:12 AM, Dario Trussardi < > dario.trussa...@tiscali.it> wrote: > >> Ciao, >> >> i work with a new Pharo 2.0 20628 image. >> >>

Re: [Pharo-dev] MessageNotUnderstood: SmallInteger>>isEmpty

On 11 Dec 2013, at 19:37, Eliot Miranda wrote: > Hi Dario, > > > On Wed, Dec 11, 2013 at 12:41 AM, Dario Trussardi > wrote: > Ciao Eliot, > > >> Hi Dario, >> >> >> On Tue, Dec 10, 2013 at 8:12 AM, Dario Trussardi >> wrote: >> Ciao, >> >> i work with a new Pharo 2.0 20628 im

[Pharo-dev] Which tests should be run in CI?

I notice that several builds are green, though I added a breaking test to Pharo 3. That probably means that those builds don't run all of the Pharo tests. Most builds probably don't need to run all tests (all the time), but it might be useful to be able to mark tests as integration tests, that are

Re: [Pharo-dev] Which tests should be run in CI?

Hi Stephan, that depends - for instance for "Bootstrap" I follow the pattern that most other contributions have configured: I only run the tests of the Bootstrap package to see when my own stuff breaks. If I would run all tests it may never be green because the underlying platform may be on the m

Re: [Pharo-dev] Which tests should be run in CI?

Torsten, For unit tests building on green builds might be enough, but what about integration/smoke tests? Concrete case: I added a test to check that no class implements >>packages That is a test that should be run by all builds, but is not. The consequence is that Moose and Pharo3 based builds u

Re: [Pharo-dev] Using TreeModel>>selectAll

One thing I didn't understand is, are valueholders supposed to announce changes, even if the "value" didn't changed? |log node | log := OrderedCollection new. node:= TreeNodeModel new content: $a; whenSelectedChanged:[:item | self halt.log add:item]; selected: true; selected: true; selected: true.

Re: [Pharo-dev] MessageNotUnderstood: SmallInteger>>isEmpty

I will promote the latest vm (latest before spur) as stable tomorrow morning. So I suppose he can try that :) Pharo-VM-mac-latest.zip cheers, Esteban On Wed, Dec 11, 2013 at 7:41 PM, Sven Van Caekenberghe wrote: > > On 11 Dec 2013,

Re: [Pharo-dev] Voronoi diagram

Hello. Cool. It is easy to download. Does anybody know how to use it, because there are no comments and tests? Best regards, Natalia 2013/12/10 NISHIHARA Satoshi > Voronoi-2d-Diagram, you can install from Configuration browser of 2.0. ;-) > > 2013/12/8 Hernán Morales Durand : > > Check this

Re: [Pharo-dev] Using TreeModel>>selectAll

That’s the default behaviour I was thinking today of introducing a special one which act as you described Ben On 11 Dec 2013, at 21:49, Nicolai Hess wrote: > One thing I didn't understand is, are valueholders supposed to announce > changes, even if > the "value" didn't changed? > > |log node

Re: [Pharo-dev] Voronoi diagram

Load it and then check class side methods in the classes of the packages There are many methods starting with "example" - just run them   Bye T.  

Re: [Pharo-dev] Which tests should be run in CI?

Hi Stephan, Thanks for pushing the #packages problem. The Moose jobs run the Moose-specific tests (those defined in the Tests group in the configuration). But, it's strange that the Pharo3 build is not red. Could it be that the test was not integrated into Pharo? Cheers, Doru Cheers, Doru

Re: [Pharo-dev] Tell me about your workflow

If you would be ready to profile a package save on your repository, it would be great. In the mean time, I'll make available a special gitfiletree package to test. Which version of Pharo you are using? 2.0 or 3.0? Regards, Thierry De : Pharo-dev [pharo-dev-bou

Re: [Pharo-dev] Which tests should be run in CI?

On 12 Dec 2013, at 06:31, Tudor Girba wrote: > Hi Stephan, > > Thanks for pushing the #packages problem. > > > But, it's strange that the Pharo3 build is not red. Could it be that the test > was not integrated into Pharo? > the test tests that there is no #packages in Pharo on the class sid

Re: [Pharo-dev] Using TreeModel>>selectAll

In the midterm would it not be better to start a new implementation? Stef On Dec 11, 2013, at 11:18 PM, Benjamin wrote: > That’s the default behaviour > > I was thinking today of introducing a special one which act as you described > > Ben > > On 11 Dec 2013, at 21:49, Nicolai Hess wrote:

Re: [Pharo-dev] Which tests should be run in CI?

Hi, On Thu, Dec 12, 2013 at 7:59 AM, Marcus Denker wrote: > > On 12 Dec 2013, at 06:31, Tudor Girba wrote: > > > Hi Stephan, > > > > Thanks for pushing the #packages problem. > > > > > > But, it's strange that the Pharo3 build is not red. Could it be that the > test was not integrated into Phar

Re: [Pharo-dev] Which tests should be run in CI?

> We need to reconsider how we approach continuous integration for pharo-based > images. can you expand ?

Re: [Pharo-dev] could we stop to create spaghetti code?

>> > > I think the idea here is that maybe a class should have an icon. Independend > of Nautilus.\ > (either just icon or toolIcon). Yes we got the idea :) Now we faced extensions management problems with pavel so we could not fix it. We did not want to produce more mess. But this is the next

Re: [Pharo-dev] Which tests should be run in CI?

On 12 Dec 2013, at 08:14, Tudor Girba wrote: > Hi, > > > On Thu, Dec 12, 2013 at 7:59 AM, Marcus Denker wrote: > > On 12 Dec 2013, at 06:31, Tudor Girba wrote: > > > Hi Stephan, > > > > Thanks for pushing the #packages problem. > > > > > > But, it's strange that the Pharo3 build is not red

Re: [Pharo-dev] could we stop to create spaghetti code?

I will check but probably next firday during the sprint. On Dec 11, 2013, at 1:25 PM, Tudor Girba wrote: > And if we are at it, the SpecDebugger still requires the EyeInspector to be > the default inspector: > https://pharo.fogbugz.com/f/cases/12055/The-Spec-Debugger-should-not-require-the-regi

[Pharo-dev] [Pharo Trick: #0003] - halt in button

[Pharo Trick: #0003] - halt in button when you are building a user interface and you want to define the behavior of a button but you do not really know. you can use self halt or self inspect and you get an inspector/debugger on your application model Stef

Re: [Pharo-dev] Categories, packages, and tags [cont'd]

On Dec 11, 2013, at 1:40 PM, Roberto Minelli wrote: > Hi guys, > > I have a question about the new “PackageTreeModel”… > > In a previous discussion > (https://www.mail-archive.com/pharo-dev@lists.pharo.org/msg09271.html) we > discussed about the new package model. Now I understood it but I a

Re: [Pharo-dev] Which tests should be run in CI?

+1 I do not really get it because we mentioned that several times. Grease maintainers should simply produce a new version and Seaside/users should use this new version. >> > But *Grease* still is the problem: in the tradition of the wonderful > philosophy “Lets keep all smalltalk crappy >

Re: [Pharo-dev] Categories, packages, and tags [cont'd]

Thx Stef! I also found RPackage organizer packages ;) Cheers, R On Dec 12, 2013, at 8:25 AM, Stéphane Ducasse wrote: > > On Dec 11, 2013, at 1:40 PM, Roberto Minelli wrote: > >> Hi guys, >> >> I have a question about the new “PackageTreeModel”… >> >> In a previous discussion >> (https://