- Pharo-dev - lists.pharo.org

[Pharo-project] White rectangles
by Torsten Bergmann Jan. 13, 2010

Jan. 13, 2010

>Yes it is a known issue. This is a bug in the VMs. >It was recently discussed in the thread "Core font" that >you have started. Yes, the interesting thing is that I just had a flickering when we started the above discussion (which was acceptable). Now I get fully painted white rectangles - which is another and now really ugly effect. Thx T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

1 0

[Pharo-project] White rectangles
by Torsten Bergmann Jan. 13, 2010

Jan. 13, 2010

When I drag a window in latest core it is not fully painted. I get white rectangles at any place where usually text is displayed (browser code pane, category list and the like). Related to font changes? Any comments? Thx T. -- GRATIS fÃ¼r alle GMX-Mitglieder: Die maxdome Movie-FLAT! Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

2 1

[Pharo-project] Object Buffer (implementation tryout)
by CÃ©drick BÃ©ler Jan. 13, 2010

Jan. 13, 2010

Hi, I've always found the need to copy/paste object (not string) between say, an inspector/explorer and a workspace. So I did a small class called ObjectBuffer and some extension that provide this fonctionnality (see the attached picture). I added menu command so that 'buffer it' is accessible from text selection, inspector and explorer. I doubt the implementation is optimal but this is working so I decided to share and see if people would like it too To get the object stored: self buffer or ObjectBuffer buffer hth, -- CÃ©drick

13 39

[Pharo-project] InputSensor next step cleanup
by StÃ©phane Ducasse Jan. 13, 2010

Jan. 13, 2010

> >> do you have one example so that I can evaluate? > > there are differents use cases of referencing Sensor (Except examples which could simple be removed from the image). > > - asking for the current cursor position (which is the majority of the references) > e.g. > 'Scanning ', aFile localName, '...' > displayProgressAt: Sensor cursorPoint > from: startPosition to: stopPosition > during: [:bar | > > This could be replaced by Display center, the current active Window position or things like that. > > - asking for the state of modifier keys > > shift := Sensor leftShiftDown. > > This needs some refactoring to hand down the current event into these methods. I already refactored a few of these methods when cleaning up the unicode handling but not all. > > > - the worst offender is actually polling > e.g. > newRectFrom: newRectBlock > > ... > [ Sensor nextEvent isNil ] whileFalse. > buttonNow := Sensor anyButtonPressed. > newRect := newRectBlock value: rect. > ... > > Not always easy to code around this, as you need stateful event handling to replace the polling. On the other hand it looks like the method could simply be removed as there don't seem to be any important callers left. > > Michael

3 4

[Pharo-project] Issue 1788: SMTPClient does not send HELO or EHLO, session is not initiated
by Matthias Berth Jan. 13, 2010

Jan. 13, 2010

Hi, I fixed a regression with sending email when using SMTPClient without login. Can someone have a look please? http://code.google.com/p/pharo/issues/detail?id=1788 Cheers Matthias

3 3

[Pharo-project] InputSensor next step cleanup
by StÃ©phane Ducasse Jan. 13, 2010

Jan. 13, 2010

> >> what are the next steps with should do for the >> >> Sensor references in the system >> 166 >> and the >> >> I would really to do some steps in the direction of cleaning what should be >> left to do. >> >> I'm confused by the comment >> >> "The usage of these funtions is discouraged. " >> so what should be done? > > the callers need to be rewritten. Right now they still use the old event polling Sensor functions, blocking the Morphic process. They would need to be rewritten to use event handling. > > Michael >

1 0

[Pharo-project] ODBC additions; very early GUI layer
by Schwab,Wilhelm K Jan. 13, 2010

Jan. 13, 2010

I put two packages in PharoTaskForces. To any and all interested parties, I've added catalog methods to the existing ODBC wrapper. See the extension methods in ODBCConnection. You will have to excuse some gratuitous selectors that make my Dolphin ODBC code feel a little less unwelcome than it otherwise might. Gary, please take a quick look at the GUI package, in particular the TreeModel. Try TreePresenter example. I plan to make analogs to the staples from Dolphin's MVP framework: text, lists, trees, images. Value adapters will appear "soon." The handling of view resources will be a challenge. The usual caveats about backups appply, just in case. Bill

3 2

[Pharo-project] Problem with Inspector [WAS] Fwd: [BetaTesting] [ANN] Pharo1.0-10505-rc1dev10.01.1
by Mariano Martinez Peck Jan. 13, 2010

Jan. 13, 2010

2010/1/12 Serge Stinckwich <serge.stinckwich(a)gmail.com> > Thank you for your good work Mariano. I use your image for my > development right now. The inspector is crashing in unexpected ways. > > Just try : #(1 2 3 4 5 6 7 9 10) inspect. > and in the panel below on the right, just evaluate for example : 3+7 with > CTRL-D > several times. After a while, the following screen appears. > > Thanks Serge for the report. I could reproduce it even in my first cmd d to 3 +7 I created the issue: http://code.google.com/p/pharo/issues/detail?id=1783 I cc Frederic as it seems to be a problem with the inspector. Cheers Mariano > 2010/1/10 Mariano Martinez Peck <marianopeck(a)gmail.com>: > > Hi Folks/Beta-Testers! > > > > I have prepare a new PharoDev image. This image, has same differences > with > > the previous ones that you should know: > > > > 1) This is the first Dev image I ever prepare. I adapt to Mac OS Damien's > > bash scripts to build them and I also cleanup all the Squeak stuff from > > those bash scripts. So, maybe there are some problems. Forgive me if this > is > > the case. I would like you to check, not only the Image in itself but > also > > the zip. The package.txt, changelog, the fonts, etc. > > > > 2) This image puts TrueType fonts again. We won't put StrikeFonts or > DejaVu > > package until there is big bug with them. We know those fonts are faster, > > but still a bit buggy. If you fix those issues, cool! > > > > 3) This image DOES NOT include O2. I know there are a lot of people who > use > > it (mostly in Moose), but unfortunately, this was a decision taken. O2 > > depends and overrides OB making this more unstable sometimes. The same as > > the TrueType, we will put O2 again when this can be perfectly load in a > > PharoCore image without anything about OB. > > Sorry, but we rather affect only O2 users and not all. If you want > packages > > support, then help in O2 development. > > > > 4) In previous Dev images only tests from PharoCore were included. Now, > it > > also includes the tests from the external packages loaded. > > > > 5) This image was build using Metacello configurations. If you want, > compare > > the installScript.st from this image to the previous one. > > > > 6) There is no Web image this time. If you want to install Seaside 2.8.4 > > evaluate: > > > > Gofer new > > squeaksource: 'MetacelloRepository'; > > package: 'ConfigurationOfSeaside28'; > > load. > > > > (Smalltalk at: #ConfigurationOfSeaside28) load > > > > And if you want Seaside 3.0 evaluate: > > > > Gofer new > > squeaksource: 'MetacelloRepository'; > > package: 'ConfigurationOfSeaside30'; > > load. > > > > (Smalltalk at: #ConfigurationOfSeaside30) loadLatestVersion > > > > However, I am not sure if this is perfectly working in Pharo. > > > > > > > > Ok .... Here is the link: > > > https://gforge.inria.fr/frs/download.php/25156/pharo1.0-10505-rc1dev10.01.1… > > > > I will wait a couple of days now and I will also start to use this image > for > > my development. If there are issues, report them. If we have big issues, > > this image is not release. On the other hand, if it works well, we > release > > it. > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > -- > Serge Stinckwich > UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam > Smalltalkers do: [:it | All with: Class, (And love: it)] > http://doesnotunderstand.org/ > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

2 2

[Pharo-project] Corrupted Monticello
by John Toohey Jan. 12, 2010

Jan. 12, 2010

Hi, I've just built a new image based on PharoCore1.0rc1 Latest update: #10496, and MC freezes the image whenever I try to open a package. I can view a repo, but not open or load the packages. Is there anyway to rebuild MC, without rebuilding the entire image again? There is no debug file written out, just the CPU pegged at 99% and an unresponsive image. -- -JT

5 26

[Pharo-project] ConfigurationOfPharo
by Torsten Bergmann Jan. 12, 2010

Jan. 12, 2010

evaluating Gofer new squeaksource: 'MetacelloRepository'; package: 'ConfigurationOfPharo'; load. ((Smalltalk at: #ConfigurationOfPharo) project version: '1.0-rc2.10505.2') load. in latest core gives: Can't find dependency "Nile-Base-cyrille_delauney.80". Same with the other version. Any ideas? Thx T. -- Jetzt kostenlos herunterladen: Internet Explorer 8 und Mozilla Firefox 3.5 - sicherer, schneller und einfacher! http://portal.gmx.net/de/go/atbrowser

2 1