March 2009 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] OT Tools for remote browsing/debugging (Was: Re: OTChasingInspector preview)

by Dale Henrichs

----- "Igor Stasenko" <siguctua(a)gmail.com> wrote: | Dale, i wanted to ask you, how easy OB-Tools could be targeted to | make | own remote debugger/browser? | And is your code free for use (under MIT)? | I'm just considering the how much of my blood could take to implement | these tools for use them in Hydra... :) Igor, OB-Tools is under the MIT license - all of the hard work was done by Lukas. For GLASS, the work involved adapting the debugger commands to the GemStone Process/Context model. In GLASS, the debugger runs on the server-side and we use Morphic on the client-side to display all of the OB windows, so it wasn't necessary to anything (okay just a bit of process fiddling:) to get the Debugger windows to display on the remote client. For Hydra, I would think that remote access to the process/context model would be the ticket - and this would be straightforward with the OTDebugger. With that said, I'm not too familiar with the inter-vm communication model. If I had another debugger to do, I would definitely start with the OTDebugger:) Dale

March 5, 2009

Re: [Pharo-project] soap and Pharo

by CÃ©drick BÃ©ler

Actually, I think it's ok for yaxo (which I think is XMLSupport)... Loading is ok, but I have failing tests (I did a bad initialization)... so I need to load it again to have a better idea. I join the sar in case some others want to try. Cheers, CÃ©drick 2009/3/5 Michael Rueger <m.rueger(a)acm.org>: > CÃ©drick BÃ©ler wrote: >> Do you know if soap(core) load in Pharo ? >> >> There's a dependancy on Yaxo which doesn't load because of some >> mimetype problem. >> Maybe I'm wrong but there is already xml support in Pharo but not >> trough Yaxo... ? > > Oh, Yaxo needs to work on Pharo, need to check. > > Michael > >

March 5, 2009

Re: [Pharo-project] soap and Pharo

by Michael Rueger

CÃ©drick BÃ©ler wrote: > Do you know if soap(core) load in Pharo ? > > There's a dependancy on Yaxo which doesn't load because of some > mimetype problem. > Maybe I'm wrong but there is already xml support in Pharo but not > trough Yaxo... ? Oh, Yaxo needs to work on Pharo, need to check. Michael

March 5, 2009

[Pharo-project] Preference Implementation collaboration ? (Fwd: [squeak-dev] Re: [ANN] Preference pragmas)

by CÃ©drick BÃ©ler

---------- Forwarded message ---------- From: Andreas Raab <andreas.raab(a)gmx.de> Date: 2009/3/5 Subject: [squeak-dev] Re: [ANN] Preference pragmas To: The general-purpose Squeak developers list <squeak-dev(a)lists.squeakfoundation.org> Igor Stasenko wrote: > > http://n2.nabble.com/Preference-refactoring-again-tt2403814.html Oh. That is indeed quite similar. Two comments: * There is really no need to specify a #setter: in the pragma - the name of the setter can be derived from the getter (read-only preferences would be pointless, no? ;-) * There is really no need to specify the default explicitly - it can be derived from the current value when the preference is registered. Other than that it looks good. It would be trivial to adjust my version to use this pragma pattern but I would still prefer it if we could collaborate on the implementation. Cheers, Â - Andreas > 2009/3/5 Andreas Raab <andreas.raab(a)gmx.de>: >> >> Edgar J. De Cleene wrote: >>> >>> I trust you and your implementation should go to current .image ASAP. >>> If at some point some guy of different secta come with a better code, we >>> don >>> reject for "heretic" =:) >> >> To the contrary. Let's give collaboration a chance. It would be stupid if we >> ended up with just enough difference to make us incompatible at such a >> superficial level. At the very least we should be waiting for a week or two >> to see if there's any reaction from the Pharo folks. Even if there is no >> reaction we should try to make it compatible at the interface (pragma) >> level. I'd be willing to do at least that but I'd need to know what their >> pragma spec actually looks like (can anyone subscribed to Pharo post an >> example or point me to ti?) >> >> Cheers, >> Â - Andreas >> >> > > > -- CÃ©drick

March 5, 2009

[Pharo-project] OT Tools for remote browsing/debugging (Was: Re: OTChasingInspector preview)

by Igor Stasenko

2009/3/5 Dale Henrichs <dale.henrichs(a)gemstone.com>: > I made a blood sacrifice to the OB gods yesterday and they led me to an acceptable (initial) implementation of a chasing inspector:) > > The code is in OB-Tools-dkh.66 (make sure you've loaded OmniBrowser-dr.442 as well). It'll need a couple more sacrifices to the OB gods before it's really ready (primarily reducing the text pane screen real estate), but you can take it for a spin, if you're interested: > > Â Â OTChasingInspector openOn: { > Â Â Â Â #key->('Smalltalk'->Smalltalk). > Â Â Â Â Dictionary with: #blue->'1' with: #green->'2' }. > > I'll be using it in GLASS, but if there's interest in a Pharo/Squeak version I'll make sure to keep it up to snuff. > > Dale > Dale, i wanted to ask you, how easy OB-Tools could be targeted to make own remote debugger/browser? And is your code free for use (under MIT)? I'm just considering the how much of my blood could take to implement these tools for use them in Hydra... :) > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Best regards, Igor Stasenko AKA sig.

March 5, 2009

Re: [Pharo-project] Fonts in Linux

by CÃ©drick BÃ©ler

Cool, thanks for the information Robert ;) 2009/3/5 Robert Roland <rob.roland(a)gmail.com>: > > John and everyone else, > > Thanks for your help here! > > I used John's idea and grabbed the FT2Plugin from the SophieReader archive > and my fonts look great now! Â Bitstream Vera Sans is much more pleasant than > Accuny! :) > > If anyone else is trying to do the same, the reader archive has FT2Plugin > inside > > Sophie Reader.app/Contents/Linux686/FT2Plugin > > I copied this to /usr/local/lib/squeak/3.10-4 > > I compiled SqueakVM myself. Â If you're using the Ubuntu packaged Squeak, > this would go in > > /usr/lib/squeak/3.9-8 > > Thanks all, > > Robert > > -- CÃ©drick

March 5, 2009

Re: [Pharo-project] OB enhancement Object>>asArray considered harmful

by Igor Stasenko

2009/3/5 CÃ©drick BÃ©ler <cdrick65(a)gmail.com>: >>> removed Â Object>>asArray >> >> so fast?! Â i expected a discussion and arguments :) >> My argument: >> this method belongs to a collections protocol (like #isEmpty) and >> should not have a default implementation. >> > I quite agree... and your 2 hours looking for the error is a good > reason to me (unexpected behavior). > > and it doesn't seem to be used in OB Enhancement anymore, so ok to > remove it ? ;) > haha... We givng you my permission > CÃ©drick > - Show quoted text - > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Best regards, Igor Stasenko AKA sig.

March 5, 2009

Re: [Pharo-project] OTChasingInspector preview

by Damien Cassou

On Thu, Mar 5, 2009 at 5:48 PM, Dale Henrichs <dale.henrichs(a)gemstone.com> wrote: > I made a blood sacrifice to the OB gods yesterday and they led me to an acceptable (initial) implementation of a chasing inspector:) > > The code is in OB-Tools-dkh.66 (make sure you've loaded OmniBrowser-dr.442 as well). It'll need a couple more sacrifices to the OB gods before it's really ready (primarily reducing the text pane screen real estate), but you can take it for a spin, if you're interested: > > Â Â OTChasingInspector openOn: { > Â Â Â Â #key->('Smalltalk'->Smalltalk). > Â Â Â Â Dictionary with: #blue->'1' with: #green->'2' }. > > I'll be using it in GLASS, but if there's interest in a Pharo/Squeak version I'll make sure to keep it up to snuff. Thank you very much Dale. I hope people will like it. -- Damien Cassou http://damiencassou.seasidehosting.st

March 5, 2009

[Pharo-project] OTChasingInspector preview

by Dale Henrichs

I made a blood sacrifice to the OB gods yesterday and they led me to an acceptable (initial) implementation of a chasing inspector:) The code is in OB-Tools-dkh.66 (make sure you've loaded OmniBrowser-dr.442 as well). It'll need a couple more sacrifices to the OB gods before it's really ready (primarily reducing the text pane screen real estate), but you can take it for a spin, if you're interested: OTChasingInspector openOn: { #key->('Smalltalk'->Smalltalk). Dictionary with: #blue->'1' with: #green->'2' }. I'll be using it in GLASS, but if there's interest in a Pharo/Squeak version I'll make sure to keep it up to snuff. Dale

March 5, 2009

Re: [Pharo-project] OB enhancement Object>>asArray considered harmful

by CÃ©drick BÃ©ler

>> removed Â Object>>asArray > > so fast?! Â i expected a discussion and arguments :) > My argument: > this method belongs to a collections protocol (like #isEmpty) and > should not have a default implementation. > I quite agree... and your 2 hours looking for the error is a good reason to me (unexpected behavior). and it doesn't seem to be used in OB Enhancement anymore, so ok to remove it ? ;) CÃ©drick

March 5, 2009