date:20100706

Accepted and committed as alpha: 1.13 in
http://squeaksource.com/PharoGoodies/

modified api is:

newBldr := XMLBuilder new.
newBldr xmlPreprocessor; attributes: #(‘a=”6″‘ ‘b=”7″‘);
  test: ‘welcome to builders’
  with: [ newBldr attributes: #('a="1"' 'b="2"'); trial: '';
 attributes: #('a="3"' 'b="4"'); trial: 'testing..' ;
 trial ].

to get:

'welcome to builderstesting..'


hope this aligns.. lots more stil to be cleaned for plugins, will do so by
the next commit..

-Skrish
*

There is an interest! Please submit/publish it...
Now What is the exact API I found cNode: a bit a bad name. What does
it mesn childrenNode:


newBldr := XMLBuilder new xmlPreprocessor.
newBldr mbAttr: #(‘a=”6″‘ ‘b=”7″‘); test: ‘welcome to builders’

why new and xmlPreprocessor

mbAttr: sucks also!

Could you shine a bit the API to be reader friendly?


Stef
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] feedup of selecting doit or typing " above and below expressions in comments?

> Again: when I have a method
>
>       foo
>         self sendMessage: myMessage with: text.
>         self sendSecondMessage: myMessage.
>
> B) In Pharo (with OB): I can only check the senders/implementors
>              of #foo which is limiting and makes it hard to search
>              for s/i of the other messages sent from within the
>              method body.
>
> => So I'm limited with Pharo(OB) compared to Standard browser in Core.

In OB you select (in the list or in the source code) whatever you want
to browse/references/implementors/senders of. There are no additional
pop-ups or questions.

And please Torsten could you *finally* fix your e-mail client/account?
You are the only one in the whole Smalltalk world that constantly
messes up the mail threading.

Lukas

-- 
Lukas Renggli
www.lukas-renggli.ch

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

[Pharo-project] Mysql Port of Josh Mcdonald Driver

Hi,

 Can anyone forward the latest version of Alan Reider's fixes of the Mysql
driver. I cant access the squeak map I get link of..

-Skrish
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] Pharo on OLPC XO kid notebook

2010-07-06 Thread Serge Stinckwich

On Tue, Jul 6, 2010 at 11:24 PM, Hilaire Fernandes
 wrote:
> OLPC moto is based from day one on the use of dynamic language to design the
> content coming with their notebook.
>
> It is to write content but also to allow kids to examine source code, edit
> it and test it ; as we are doing continuously in Smalltalk.
> They even think about a source-code key in the keyboard to instantaneously
> open a source code browser exposing the code of a running application.
>
> Now that Pharo 1.1 is in good sigh and as we are not ashame any more to show
> how Smalltalk looks like we could also produce a release of Pharo for OLPC
> XO Sugar environment. It is definitely a good opportunity to bring an
> interesting tool to neutral mind (kids). In the other hand, it will
> definitely help to bring awareness about Pharo.  For example, without any
> action of my part, DrGeoII was downloaded about 180'000 times in one year
> for XO.
>
> Any takers?

I'm interested ! I'm involved in OLPC Vietnam and we would like to
develop more contents in Vietnamese. Our website is here:
http://olpc.vn/

Some vietnamese students (one of them is in CC on this message) are
working to port Magic Words (http://comikit.se/page_magicwords.html )
to the XO and we are looking for an Smalltalk image for deployment (at
the moment we are considering using the EToys image).

What should be done:
- build a specific VM (reuse EToys work),
- port D-BUS to Pharo : http://wiki.laptop.org/go/D-BUS This is mostly
used to communicate with OLPC-services. There is already an EToys
version: http://www.squeaksource.com/dbus.html
- package Pharo as an xo package,
- adapt PBE to have a PBE-Sugar edition.

> Hilaire
>
> PS: I have a couple of XO machines for testing purpose.

I've got one.
Regards,
-- 
Serge Stinckwich
UMI UMMISCO 209 (IRD/UPMC), Hanoi, Vietnam
Every DSL ends up being Smalltalk
http://doesnotunderstand.org/

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

[Pharo-project] feedup of selecting doit or typing " above and below expressions in comments?

>This was removed on request of Stef and I completely agree on this:
>for me it is time consuming to be forced to search for the selector in
>a sorted list when the selector is written/selected right in front of
>me.

Maybe I dont understand what you wrote - but if I understand you
correctly OB had the same behavior as in Core and this was removed
from OB on request of Stef?


Again: when I have a method
   
   foo
 self sendMessage: myMessage with: text.
 self sendSecondMessage: myMessage.


A) In Core: I'm able to browse the senders/implementors of all
   three selectors using the sorted list provided by the
   "Senders of..."/"Implementors of..." menu:

#(foo, sendMessage:with:, sendSecondMessage:)

   where the methods selector (#foo) of the selected method
   is explicitly at the top.

B) In Pharo (with OB): I can only check the senders/implementors 
  of #foo which is limiting and makes it hard to search 
  for s/i of the other messages sent from within the 
  method body.

=> So I'm limited with Pharo(OB) compared to Standard browser in Core.

Bye
T.
-- 
GMX DSL: Internet-, Telefon- und Handy-Flat ab 19,99 EUR/mtl.  
Bis zu 150 EUR Startguthaben inklusive! http://portal.gmx.net/de/go/dsl

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] feedup of selecting doit or typing " above and below expressions in comments?

cool

On Jul 6, 2010, at 10:54 PM, Lukas Renggli wrote:

>>> Another thing that is related to the above and to the different browsers:
>>> 
>>> In Core: When I select a method I can choose "Senders of..."
>>> and "Implementors of..." to either search for senders/implementors
>>> of the selected method AND the messages sent into the selected
>>> method.
>>> 
>>> In Pharo: with OB I can just do "senders" and "implementors"
>>>  which looks for the senders/implementors of the selected method
>>>  One is NOT able to search for senders/implementors of
>>>  the messages sent within the selected method.
>>>  Here I have to select the entire selector which is
>>>  time consuming as described above.
>> 
>> enter a bug entry.
> 
> This was removed on request of Stef and I completely agree on this:
> for me it is time consuming to be forced to search for the selector in
> a sorted list when the selector is written/selected right in front of
> me.
> 
>>> So Pharo with OB is (compared to core) really a step backwards here.
>> 
>> I imagine that the enh I did also to get Cmd-M on class name browsing the 
>> class and Cmd-B on
>> selectors do an implementors should also be pushed in OB.
> 
> The Cmd-B was always part of OB, I've done the same for Cmd-M. Also I
> updated the edit pane menu to match the one of the standard browser.
> 
> Lukas
> 
> -- 
> Lukas Renggli
> www.lukas-renggli.ch
> 
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] Markup Builder in Smalltalk

>>I may perhaps be unaware of the XML/SGML builder generation from Seaside, 
>>love to be pointed out to.., The Html generation of
>>Seaside uses explicit construct of classes ( WA**Tags) to do so.. Builders in 
>>dynamic manner
>> use doesNotUnderstand: construct to generate the stream..
>
> While it may seem desirable to have an API that uses #doesNotUnderstand: (or 
> its equivalent in other languages) to facilitate markup generation by 
> accepting arbitrary messages and taking them to be the names of tags, this 
> approach is not a good idea for at least two reasons: 1) namespace prefixes 
> cannot be specified in this way, as ":" is not a legal character within 
> identifiers in Smalltalk (or in most other languages, for that matter), and 
> 2) unary messages intended to be treated as tag names can collide with 
> already-defined unary messages in the writer class or its superclasses.

3) The approach with #doesNotUnderstand: absolutely doesn't scale.
Tools break in subtle ways (editors, debuggers, program checkers).
Debugging is a pain. And it is slow. We've had that in Seaside up to
version 2.6.

Lukas

-- 
Lukas Renggli
www.lukas-renggli.ch

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] Issue 2635 - methods recategorization

code:

SystemNavigation organization renameCategory: '*multilingual-editor'
toBe: '*Multilingual-Encodings'.
Project class organization classify: #spawnNewProcessIfThisIsUI:
under: '*Morphic'.
Project class organization removeCategory:'squeaklet on server'.
ImmX11 organization classify: #keyboardFocusForAMorph: under: '*Morphic'.
FileStream class organization classify:
#fileReaderServicesForFile:suffix: under: '*Tools-FileList'.
FileStream class organization classify: #serviceFileIn under: '*Tools-FileList'.
FileStream class organization classify: #serviceRemoveLineFeeds under:
'*Tools-FileList'.
FileStream class organization classify: #services under: '*Tools-FileList'.
Character organization classify: #macRomanToUnicode under:
'*Multilingual-TextConversion'.
Character organization classify: #unicodeToMacRoman under:
'*Multilingual-TextConversion'.
TranscriptStream organization classify: #codePaneMenu:shifted: under:
'*Tools-Base'.
TranscriptStream class organization classify: #openMorphicTranscript
under: '*Morphic'.

description:

SystemNavigation organization renameCategory: '*multilingual-editor'
toBe: '*Multilingual-Encodings'.
- move the single method allSelect: to a base Multilingual package

Project class organization classify: #spawnNewProcessIfThisIsUI:
under: '*Morphic'.
Project class organization removeCategory:'squeaklet on server'.
- UI specific and sent only from Morphic dependent methods

ImmX11 organization classify: #keyboardFocusForAMorph: under: '*Morphic'.
- used only for Morphic

FileStream class organization classify:
#fileReaderServicesForFile:suffix: under: '*Tools-FileList'.
FileStream class organization classify: #serviceFileIn under: '*Tools-FileList'.
FileStream class organization classify: #serviceRemoveLineFeeds under:
'*Tools-FileList'.
FileStream class organization classify: #services under: '*Tools-FileList'.
- FileList files associations. However a deeper refactoring is welcome.

Character organization classify: #macRomanToUnicode under:
'*Multilingual-TextConversion'.
Character organization classify: #unicodeToMacRoman under:
'*Multilingual-TextConversion'.
- both packages in the PharoKernel. Move to a more fitting package.

TranscriptStream organization classify: #codePaneMenu:shifted: under:
'*Tools-Base'.
TranscriptStream class organization classify: #openMorphicTranscript
under: '*Morphic'.

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] Markup Builder in Smalltalk

2010-07-06 Thread jaayer



 On Tue, 06 Jul 2010 02:37:38 -0700 Sudhakar Krishnamachari  wrote  

>I may perhaps be unaware of the XML/SGML builder generation from Seaside, love 
>to be pointed out to.., The Html generation of
>Seaside uses explicit construct of classes ( WA**Tags) to do so.. Builders in 
>dynamic manner 
> use doesNotUnderstand: construct to generate the stream..

While it may seem desirable to have an API that uses #doesNotUnderstand: (or 
its equivalent in other languages) to facilitate markup generation by accepting 
arbitrary messages and taking them to be the names of tags, this approach is 
not a good idea for at least two reasons: 1) namespace prefixes cannot be 
specified in this way, as ":" is not a legal character within identifiers in 
Smalltalk (or in most other languages, for that matter), and 2) unary messages 
intended to be treated as tag names can collide with already-defined unary 
messages in the writer class or its superclasses.


___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] Issue 2635 - methods recategorization

On Tue, Jul 6, 2010 at 11:05 PM, Michael Roberts  wrote:
>>> 2) e.g you move somethings to *Tools and some things to *Tools-Explorer
>>> is that not going to create the same problem that happened to System,
>>> with both parent and child packages defined in the same image?
>>
>> There's only one MC package named Tools and this package is not
>> splitted. But we may make future split of this package easier if we
>> will use a category name Tools-Base (or more fitting one) instead of
>> Tools.
>>
>
> ok fair enough. but if i look in #12038 there appear a few cases:
> Graphics-Stef.256
> Graphics-*
>
> Multilingual-Markus.2
> Multilingual-*

At least the Multilingual package is automatically registered because
of one method in the Character class and the fix is already mentioned
in this thread. However I have no idea why MC registers automatically
the Graphics package

Cheers,
-- Pavel

>
> this needs fixing before applying more recategorisation?
>
>
> thanks,
> Mike
>
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] Issue 2635 - methods recategorization

2010-07-06 Thread Michael Roberts

>> 2) e.g you move somethings to *Tools and some things to *Tools-Explorer
>> is that not going to create the same problem that happened to System,
>> with both parent and child packages defined in the same image?
>
> There's only one MC package named Tools and this package is not
> splitted. But we may make future split of this package easier if we
> will use a category name Tools-Base (or more fitting one) instead of
> Tools.
>

ok fair enough. but if i look in #12038 there appear a few cases:
Graphics-Stef.256
Graphics-*

Multilingual-Markus.2
Multilingual-*

this needs fixing before applying more recategorisation?


thanks,
Mike

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] Markup Builder in Smalltalk (XMLWriter)

2010-07-06 Thread jaayer



 On Tue, 06 Jul 2010 03:19:48 -0700 Torsten Bergmann  wrote  

>Just check "XMLWriter-tbn.5" which can be found in 
>"http://squeaksource.com/PharoGoodies/"; 
> 
>-- 
>|writer| 
>writer := XMLTagWriter xml. 
>writer comment: 'A new xml file'. 
>writer tag: 'package' with: [ 
>writer cData: 'name' with: 'XMLWriter'. 
>]. 
>writer contents 
> 
>returns 
> 
> 
> 
> 
>  
> 
>-- 
> 
>You can also access the stream (writer stream). 
>Indenting is not yet working fully but at least 
>it should give you idea. Check out the test cases for 
>more. 
> 
>I once saw such an XMLWriter written by Ernest Micklei 
>in VAST (credits for the idea) and rebuilt it in Pharo. 
> 
>Bye 
>T. 
>-- 
>GMX DSL: Internet-, Telefon- und Handy-Flat ab 19,99 EUR/mtl. 
>Bis zu 150 EUR Startguthaben inklusive! http://portal.gmx.net/de/go/dsl 
> 
>___ 
>Pharo-project mailing list 
>Pharo-project@lists.gforge.inria.fr 
>http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project 
> 

The next version of XMLSupport will feature an XMLWriter with an API similar to 
XMLTagWriter. I had decided a few weeks that any API using explicit start/end 
methods was unsmalltalk-like and should be replaced with one based on 
execute-around methods, though I was unaware of XMLTagWriter and instead 
modeled the API loosely on Seaside's HTML generation. You now send XMLWriter 
messages that create markup-writing objects for the parts of a document. These 
objects can then be configured using messages like #attributeAt:put: and 
written to the document explicitly with a serialization message (which 
typically accepts content) or implicitly by creating another markup writer 
after it. The new API looks like this:

| writer |
((writer := XMLWriter new)
enablePrettyPrinting;
xmlDeclaration;
tag: 'foo')
xmlnsAt: 'foo' put: 'http://foo';
attributeAt: 'a' put: 'one';
attributeAt: 'b' put: 'two';
content: [
writer tag: 'bar' content: [
(writer
string: 'test';
tag: 'baz';
tag: 'foobar')
content: 'test']]
which produces:
 
http://foo"; a="one" b="two">
test
test




___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] Morph rendering with antialiasing

2010-07-06 Thread Henrik Sperre Johansen


 On 06.07.2010 22:28, Denis Kudriashov wrote:

Hello.

Is somebody implement morphs rendering with antialiasing?
Maybe it is already possible?

In practice I need circle button. But without antialiasing it seems 
really ugly.


If there is no existed solution. How do you think It can be implemented?

I know that fonts rendered with antialiasing. How its approach can be 
applyed for morphs?


I notice browser buttons (senders, implementors..) has rounded 
corners. And its nice rendered. What secrete? Can it be done for any 
morph corner rounding

Using shape rendering primitives, no.
Balloon does AA, though you'll have problems with small thin lines 
(which is why smaller sized TTFonts doesn't exactly look stellar).
The "secret" method used by both fonts and browser buttons is to instead 
display AA'd bitmaps (ie. you use the alpha channel), instead of 
rendering shapes.


Cheers,
Henry

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] feedup of selecting doit or typing " above and below expressions in comments?

>> Another thing that is related to the above and to the different browsers:
>>
>> In Core: When I select a method I can choose "Senders of..."
>>         and "Implementors of..." to either search for senders/implementors
>>         of the selected method AND the messages sent into the selected
>>         method.
>>
>> In Pharo: with OB I can just do "senders" and "implementors"
>>          which looks for the senders/implementors of the selected method
>>          One is NOT able to search for senders/implementors of
>>          the messages sent within the selected method.
>>          Here I have to select the entire selector which is
>>          time consuming as described above.
>
> enter a bug entry.

This was removed on request of Stef and I completely agree on this:
for me it is time consuming to be forced to search for the selector in
a sorted list when the selector is written/selected right in front of
me.

>> So Pharo with OB is (compared to core) really a step backwards here.
>
> I imagine that the enh I did also to get Cmd-M on class name browsing the 
> class and Cmd-B on
> selectors do an implementors should also be pushed in OB.

The Cmd-B was always part of OB, I've done the same for Cmd-M. Also I
updated the edit pane menu to match the one of the standard browser.

Lukas

-- 
Lukas Renggli
www.lukas-renggli.ch

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] Issue 2635 - methods recategorization

code:

MethodReference organization moveCategory: '*Kernel-Traits' to:
'*Traits-Kernel'.
LRUCache organization moveCategory: '*Polymorph-Widgets-override' to:
'accessing'.
Project class organization moveCategory: 'utilities' to: '*Morphic'.
Character organization moveCategory: '*Multilingual' to:
'*Multilingual-Encodings'.
TranscriptStream organization moveCategory: 'toolbuilder' to:
'*ToolBuilder-Kernel'.
TranscriptStream class organization moveCategory: 'toolbuilder' to:
'*ToolBuilder-Kernel'.

description:

MethodReference organization moveCategory: '*Kernel-Traits' to:
'*Traits-Kernel'.
- swap package name parts to a more logical ownership. It contains
only a method actualClass that has no other kernel implementation.
Both packages will be in the kernel image.

LRUCache organization moveCategory: '*Polymorph-Widgets-override' to:
'accessing'.
- only one method. Declared as override but has no old version in the
history and has general functionality

Project class organization moveCategory: 'utilities' to: '*Morphic'.
- all methods have no real senders or are called only from Morphic

Character organization moveCategory: '*Multilingual' to:
'*Multilingual-Encodings'.
- only fix MC package name

TranscriptStream organization moveCategory: 'toolbuilder' to:
'*ToolBuilder-Kernel'.
- single method buildWith:, used only for the Toolbuilder

TranscriptStream class organization moveCategory: 'toolbuilder' to:
'*ToolBuilder-Kernel'.
- the same

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] Issue 2635 - methods recategorization

today we were discussing with jannik and jean-remi to build a little tool to 
identify SCC and showing them.
So we could then check per package or group of package SCC (strongly connected 
components) and 
we will start cutting inside large package.

Stef
On Jul 6, 2010, at 10:42 PM, Pavel Krivanek wrote:

> Hi,
> 
> On Tue, Jul 6, 2010 at 10:32 PM, Michael Roberts  wrote:
>> Hi,
>> 
>> 1) do MC packages already exist for all re-categorization?
> 
> no
> 
>> 2) e.g you move somethings to *Tools and some things to *Tools-Explorer
>> is that not going to create the same problem that happened to System,
>> with both parent and child packages defined in the same image?
> 
> There's only one MC package named Tools and this package is not
> splitted. But we may make future split of this package easier if we
> will use a category name Tools-Base (or more fitting one) instead of
> Tools.
> 
> -- Pavel
> 
>> thanks,
>> Mike
>> 
>> ___
>> Pharo-project mailing list
>> Pharo-project@lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>> 
> 
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] Issue 2635 - methods recategorization

Hi,

On Tue, Jul 6, 2010 at 10:32 PM, Michael Roberts  wrote:
> Hi,
>
> 1) do MC packages already exist for all re-categorization?

no

> 2) e.g you move somethings to *Tools and some things to *Tools-Explorer
> is that not going to create the same problem that happened to System,
> with both parent and child packages defined in the same image?

There's only one MC package named Tools and this package is not
splitted. But we may make future split of this package easier if we
will use a category name Tools-Base (or more fitting one) instead of
Tools.

-- Pavel

> thanks,
> Mike
>
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] Issue 2635 - methods recategorization

2010-07-06 Thread Michael Roberts

Hi,

1) do MC packages already exist for all re-categorization?

2) e.g you move somethings to *Tools and some things to *Tools-Explorer
is that not going to create the same problem that happened to System,
with both parent and child packages defined in the same image?

thanks,
Mike

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

[Pharo-project] Morph rendering with antialiasing

2010-07-06 Thread Denis Kudriashov

Hello.

Is somebody implement morphs rendering with antialiasing?
Maybe it is already possible?

In practice I need circle button. But without antialiasing it seems really
ugly.

If there is no existed solution. How do you think It can be implemented?

I know that fonts rendered with antialiasing. How its approach can be
applyed for morphs?

I notice browser buttons (senders, implementors..) has rounded corners. And
its nice rendered. What secrete? Can it be done for any morph corner
rounding?
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] Issue 2635 - methods recategorization


On Jul 6, 2010, at 10:20 PM, Pavel Krivanek wrote:

> Hi Stef,
> 
> of course, I will do that. For faster processing I filtered the
> commands that only change caps in the package names.

good idea

> Added as a
> comment 10 to this issue. It needs only a patch from comment 5 that
> adds a method that enables categories merging.
> 
> !Categorizer methodsFor: 'accessing' stamp: 'pavel.krivanek 7/4/2010 11:54'!
> moveCategory: sourceCategory to: destinationCategory
> 
>   self classifyAll: (self listAtCategoryNamed: sourceCategory) under:
> destinationCategory.
>   self removeCategory: sourceCategory.
>   ! !

Ok I will have a look.

> 
> MethodReference organization renameCategory: '*fixunderscores' toBe:
> '*FixUnderscores'.
> MethodReference organization renameCategory: '*monticello' toBe: 
> '*Monticello'.
> MethodReference organization renameCategory: '*packageinfo-base' toBe:
> '*PackageInfo-Base'.
> FileStream organization renameCategory: '*compression' toBe: '*Compression'.
> FileStream organization renameCategory: '*network-uri' toBe: '*Network-URI'.
> FileStream organization renameCategory: '*network-url' toBe: '*Network-URL'.
> FileStream organization renameCategory: '*tools' toBe: '*Tools'.
> FileStream class organization renameCategory: '*network-uri' toBe:
> '*Network-URI'.
> PositionableStream organization renameCategory: '*compression' toBe:
> '*Compression'.
> TranscriptStream organization renameCategory: '*morphic' toBe: '*Morphic'.
> Boolean class organization renameCategory: '*system-settings-browser'
> toBe: '*System-Settings-Browser'.
> SmartRefStream organization renameCategory: '*compression' toBe: 
> '*compression'.
> StandardFileStream class organization renameCategory: '*network-uri'
> toBe: '*Network-URI'.
> Magnitude organization renameCategory: '*kernel-extensions-streaming'
> toBe: '*Kernel-Extensions-Streaming'.
> MacFileDirectory class organization renameCategory: '*network-uri'
> toBe: '*Network-URI'.
> Object organization renameCategory: '*system-settings-browser' toBe:
> '*System-Settings-Browser'.
> Object organization renameCategory: '*system-support' toBe: '*System-Support'.
> Object organization renameCategory: '*tools-browser' toBe: '*Tools-Browser'.
> Object organization renameCategory: '*tools-explorer' toBe: '*Tools-Explorer'.
> Behavior organization moveCategory: '*system-support' to: '*System-Support'.
> Integer organization moveCategory: '*files' to: '*Files'.
> Integer organization moveCategory: '*system-hashing-core' to:
> '*System-Hashing-Core'.
> Integer organization moveCategory: '*tools-explorer' to: '*Tools-Explorer'.
> OrderedCollection organization moveCategory: '*tools-inspector' to:
> '*Tools-Inspector'.
> SystemOrganizer organization moveCategory: '*gofer-core-accessing' to:
> '*Gofer-Core-Accessing'.
> Trait organization moveCategory: '*monticello' to: '*Monticello'.
> TraitBehavior organization moveCategory: '*tools-browser' to: 
> '*Tools-Browser'.
> String organization moveCategory: '*compression' to: '*Compression'.
> String organization moveCategory: '*files' to: '*Files'.
> String organization moveCategory: '*monticello' to: '*Monticello'.
> String organization moveCategory: '*morphic' to: '*Morphic'.
> String organization moveCategory: '*network-mime' to: '*Network-MIME'.
> String organization moveCategory: '*network-protocols' to: 
> '*Network-Protocols'.
> String organization moveCategory: '*network-uri' to: '*Network-URI'.
> String organization moveCategory: '*network-url' to: '*Network-Url'.
> String organization moveCategory: '*st80' to: '*ST80'.
> String organization moveCategory: '*system-settings-browser' to:
> '*System-Settings-Browser'.
> Text organization moveCategory: '*morphic-converting' to: 
> '*Morphic-Converting'.
> Announcer organization moveCategory: '*announcements-view' to:
> '*Announcements-View'.
> Announcement organization moveCategory: '*announcements-view' to:
> '*Announcements-View'.
> ClassDescription organization moveCategory: '*system-support' to:
> '*System-Support'.
> WeakSet organization moveCategory: '*tools-inspector' to: '*Tools-Inspector'.
> Class organization moveCategory: '*monticello' to: '*Monticello'.
> FloatArray organization moveCategory: '*tools-inspector' to: 
> '*Tools-Inspector'.
> Collection organization moveCategory: '*tools-explorer' to: '*Tools-Explorer'.
> Stream organization moveCategory: '*monticello' to: '*Monticello'.
> BitBlt organization moveCategory: '*FreeType-addition' to: 
> '*FreeType-Addition'.
> ReadWriteStream organization moveCategory: '*compression' to: '*Compression'.
> RunArray class organization moveCategory: '*system-changes' to:
> '*System-Changes'.
> Color organization moveCategory: '*morphic' to: '*Morphic'.
> Color class organization moveCategory: '*system-settings-browser' to:
> '*System-Settings-Browser'.
> AcornFileDirectory class organization moveCategory: '*network-uri' to:
> '*Network-URI'.
> ImageSegment organization moveCategory: '*tests-system'

Re: [Pharo-project] Issue 2635 - methods recategorization

Hi Stef,

of course, I will do that. For faster processing I filtered the
commands that only change caps in the package names. Added as a
comment 10 to this issue. It needs only a patch from comment 5 that
adds a method that enables categories merging.

!Categorizer methodsFor: 'accessing' stamp: 'pavel.krivanek 7/4/2010 11:54'!
moveCategory: sourceCategory to: destinationCategory

self classifyAll: (self listAtCategoryNamed: sourceCategory) under:
destinationCategory.
self removeCategory: sourceCategory.
! !

MethodReference organization renameCategory: '*fixunderscores' toBe:
'*FixUnderscores'.
MethodReference organization renameCategory: '*monticello' toBe: '*Monticello'.
MethodReference organization renameCategory: '*packageinfo-base' toBe:
'*PackageInfo-Base'.
FileStream organization renameCategory: '*compression' toBe: '*Compression'.
FileStream organization renameCategory: '*network-uri' toBe: '*Network-URI'.
FileStream organization renameCategory: '*network-url' toBe: '*Network-URL'.
FileStream organization renameCategory: '*tools' toBe: '*Tools'.
FileStream class organization renameCategory: '*network-uri' toBe:
'*Network-URI'.
PositionableStream organization renameCategory: '*compression' toBe:
'*Compression'.
TranscriptStream organization renameCategory: '*morphic' toBe: '*Morphic'.
Boolean class organization renameCategory: '*system-settings-browser'
toBe: '*System-Settings-Browser'.
SmartRefStream organization renameCategory: '*compression' toBe: '*compression'.
StandardFileStream class organization renameCategory: '*network-uri'
toBe: '*Network-URI'.
Magnitude organization renameCategory: '*kernel-extensions-streaming'
toBe: '*Kernel-Extensions-Streaming'.
MacFileDirectory class organization renameCategory: '*network-uri'
toBe: '*Network-URI'.
Object organization renameCategory: '*system-settings-browser' toBe:
'*System-Settings-Browser'.
Object organization renameCategory: '*system-support' toBe: '*System-Support'.
Object organization renameCategory: '*tools-browser' toBe: '*Tools-Browser'.
Object organization renameCategory: '*tools-explorer' toBe: '*Tools-Explorer'.
Behavior organization moveCategory: '*system-support' to: '*System-Support'.
Integer organization moveCategory: '*files' to: '*Files'.
Integer organization moveCategory: '*system-hashing-core' to:
'*System-Hashing-Core'.
Integer organization moveCategory: '*tools-explorer' to: '*Tools-Explorer'.
OrderedCollection organization moveCategory: '*tools-inspector' to:
'*Tools-Inspector'.
SystemOrganizer organization moveCategory: '*gofer-core-accessing' to:
'*Gofer-Core-Accessing'.
Trait organization moveCategory: '*monticello' to: '*Monticello'.
TraitBehavior organization moveCategory: '*tools-browser' to: '*Tools-Browser'.
String organization moveCategory: '*compression' to: '*Compression'.
String organization moveCategory: '*files' to: '*Files'.
String organization moveCategory: '*monticello' to: '*Monticello'.
String organization moveCategory: '*morphic' to: '*Morphic'.
String organization moveCategory: '*network-mime' to: '*Network-MIME'.
String organization moveCategory: '*network-protocols' to: '*Network-Protocols'.
String organization moveCategory: '*network-uri' to: '*Network-URI'.
String organization moveCategory: '*network-url' to: '*Network-Url'.
String organization moveCategory: '*st80' to: '*ST80'.
String organization moveCategory: '*system-settings-browser' to:
'*System-Settings-Browser'.
Text organization moveCategory: '*morphic-converting' to: '*Morphic-Converting'.
Announcer organization moveCategory: '*announcements-view' to:
'*Announcements-View'.
Announcement organization moveCategory: '*announcements-view' to:
'*Announcements-View'.
ClassDescription organization moveCategory: '*system-support' to:
'*System-Support'.
WeakSet organization moveCategory: '*tools-inspector' to: '*Tools-Inspector'.
Class organization moveCategory: '*monticello' to: '*Monticello'.
FloatArray organization moveCategory: '*tools-inspector' to: '*Tools-Inspector'.
Collection organization moveCategory: '*tools-explorer' to: '*Tools-Explorer'.
Stream organization moveCategory: '*monticello' to: '*Monticello'.
BitBlt organization moveCategory: '*FreeType-addition' to: '*FreeType-Addition'.
ReadWriteStream organization moveCategory: '*compression' to: '*Compression'.
RunArray class organization moveCategory: '*system-changes' to:
'*System-Changes'.
Color organization moveCategory: '*morphic' to: '*Morphic'.
Color class organization moveCategory: '*system-settings-browser' to:
'*System-Settings-Browser'.
AcornFileDirectory class organization moveCategory: '*network-uri' to:
'*Network-URI'.
ImageSegment organization moveCategory: '*tests-system' to: '*Tests-System'.
ChangeRecord organization moveCategory: '*monticello' to: '*Monticello'.
Form organization moveCategory: '*morphic' to: '*Morphic'.
Number class organization moveCategory: '*system-settings-browser' to:
'*System-Settings-Browser'.
DosFileDirectory class organi

Re: [Pharo-project] Fix the other dependencies of asContextWithSender:

2010-07-06 Thread Eliot Miranda

On Tue, Jul 6, 2010 at 12:51 PM, stephane ducasse
wrote:

> Eliot
>
> should this fix be applied to pharo?
>http://code.google.com/p/pharo/issues/detail?id=2655

Yes please.  Almost everything I'm likely to put in Compiler, Kernel or
System on Squeak 4.1 belongs in all dialects using the closure compiler.

>
> Is there a dependency?
>

What's happing here is that very old primitive failure code that allowed the
closure system to run on old VMs without closure support depended on
BlockClosure>>asContext, which had a bug in it.  So the changes reflect the
bug fix but are enclosed in false ifTrue: [] because they really are
obsolete, but the code is retained because its useful documentation of how
the closure primitives should work.  I hope this makes sense!

best
Eliot

>
> Stef
>
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] Cleaning WriteBarrier (as used in Magma)

2010-07-06 Thread Chris Muller

It makes use of the old ByteCodeGenerator from NewCompiler, can't
remember why at the moment..

WriteBarrier generates overriding methods for all mutating methods of
a class.  They capture the pre-state of all modified vars, call super,
then check the post-state of the vars and, if different, sends
#modified: to the handler  Something like that.

I'm sure it could be updated to not use ByteCodeGenerator, I just
haven't had time to do it..

 - Chris

On Tue, Jul 6, 2010 at 2:25 PM, Stéphane Ducasse
 wrote:
> What is missing to make it work in Pharo?
>
> Stef
> On Jul 6, 2010, at 8:16 PM, Chris Muller wrote:
>
>> Thanks, I will look for your updated WriteBarrier package to include
>> with the next Magma.  I have just copied my own latest WriteBarrier to
>> the MagmaTester project of squeaksource.
>>
>> ---
>> Name: WriteBarrier-cmm.27
>> Author: cmm
>> Time: 19 June 2010, 4:41:13.886 pm
>> UUID: 84945d10-b0eb-419b-a6bc-2de227aac87a
>> Ancestors: WriteBarrier-pmm.26
>>
>> Removed PseudoContext extension for compatibility with Squeak 4.2+.
>> --
>>
>> WriteBarrier unfortunately doesn't work in either of Pharo or Squeak
>> 4.1+.  I am tempted to remove it from the suite altogether, but to do
>> so would break backward compatibility with 3.9 who may be using
>> WriteBarrier, because the implementation requires the handler
>> (MaTransaction) to inherit from the WriteBarrier class itself..  :-(
>>
>> Thanks,
>>  Chris
>>
>>
>> On Tue, Jul 6, 2010 at 4:44 AM, Torsten Bergmann  wrote:
>>> Hi Avi,
>>>
>>> how is life at Twitter ;)
>>>
>>> Would it be possible that you add me as a developer on
>>>
>>> http://www.squeaksource.com/WriteBarrier
>>>
>>> so I can clean up underscore assignment in the package.
>>>
>>> WriteBarrier is used in Magma (see ConfigurationOfMagma)
>>> which is installable right from a workspace in the
>>> upcoming Pharo 1.1 release. Currently this fails since
>>> by default underscore assignment is not allowed in Pharo.
>>>
>>> Thanks
>>> Torsten
>>> --
>>> GMX DSL: Internet-, Telefon- und Handy-Flat ab 19,99 EUR/mtl.
>>> Bis zu 150 EUR Startguthaben inklusive! http://portal.gmx.net/de/go/dsl
>>>
>>> ___
>>> Pharo-project mailing list
>>> Pharo-project@lists.gforge.inria.fr
>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>>>
>>
>> ___
>> Pharo-project mailing list
>> Pharo-project@lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
>

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

[Pharo-project] Fix the other dependencies of asContextWithSender:

2010-07-06 Thread stephane ducasse

Eliot

should this fix be applied to pharo?
http://code.google.com/p/pharo/issues/detail?id=2655
Is there a dependency?

Stef

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

[Pharo-project] Markup Builder in Smalltalk

> More or less exactly the same..except the syntax.. 

I think the syntax in my XMLWriter package is more oriented towards clean 
Smalltalk, while yours reminds me on some cryptic languages I used 
in the past ;)

What does #mbAttr: mean, "markup builder" or "my bytes" or ...?

I will never understand why people invent languages to save
bytes in writing/typing...especially after autocompletion was invented.

>see means of merging the frameworks for best use..

I doubt I will accept this syntax style. So it is better when you 
provide an own package.

An additional idea:
===
I can also imagine another kind of XMLBuilder where one can use the 
DNU trick to write any tag (with all the pro and cons of the DNU hack): 

builder := XMLBuilder xml.
builder person: [
 builder 
  name: 'Luke';
  planet: 'Moon' number: 12]
builder xml

then results in 


  
 Luke
 Moon
  


  
Bye
T.
-- 
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] Cleaning WriteBarrier (as used in Magma)

What is missing to make it work in Pharo?

Stef
On Jul 6, 2010, at 8:16 PM, Chris Muller wrote:

> Thanks, I will look for your updated WriteBarrier package to include
> with the next Magma.  I have just copied my own latest WriteBarrier to
> the MagmaTester project of squeaksource.
> 
> ---
> Name: WriteBarrier-cmm.27
> Author: cmm
> Time: 19 June 2010, 4:41:13.886 pm
> UUID: 84945d10-b0eb-419b-a6bc-2de227aac87a
> Ancestors: WriteBarrier-pmm.26
> 
> Removed PseudoContext extension for compatibility with Squeak 4.2+.
> --
> 
> WriteBarrier unfortunately doesn't work in either of Pharo or Squeak
> 4.1+.  I am tempted to remove it from the suite altogether, but to do
> so would break backward compatibility with 3.9 who may be using
> WriteBarrier, because the implementation requires the handler
> (MaTransaction) to inherit from the WriteBarrier class itself..  :-(
> 
> Thanks,
>  Chris
> 
> 
> On Tue, Jul 6, 2010 at 4:44 AM, Torsten Bergmann  wrote:
>> Hi Avi,
>> 
>> how is life at Twitter ;)
>> 
>> Would it be possible that you add me as a developer on
>> 
>> http://www.squeaksource.com/WriteBarrier
>> 
>> so I can clean up underscore assignment in the package.
>> 
>> WriteBarrier is used in Magma (see ConfigurationOfMagma)
>> which is installable right from a workspace in the
>> upcoming Pharo 1.1 release. Currently this fails since
>> by default underscore assignment is not allowed in Pharo.
>> 
>> Thanks
>> Torsten
>> --
>> GMX DSL: Internet-, Telefon- und Handy-Flat ab 19,99 EUR/mtl.
>> Bis zu 150 EUR Startguthaben inklusive! http://portal.gmx.net/de/go/dsl
>> 
>> ___
>> Pharo-project mailing list
>> Pharo-project@lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>> 
> 
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] [SPAM] should we move pharo to use webclient?

I agree and this is why I asked.
I'm not good in network but the code of network always made me nearly faint 
because it was clearly not designed.
Now why interested people would not do a little task forces to bullet proof the 
integration and we prepare together
its integration...
remember pharo is also your smalltalk :)

On Jul 6, 2010, at 3:04 PM, Sven Van Caekenberghe wrote:

> Yes!!
> 
> It now loads without patches into Pharo 1.1 rc2
> I used its client and server part, seaside adaptor, it all works.
> 
> The code is quite readable/understandable/malleable.
> 
> I did not yet test the WebClient-HTTP package which patches HTTPSocket to 
> replace the old code,
> which is obviously important (it then gets used by MC and the rest of 
> Smalltalk).
> 
> The unit tests also have to be double checked.
> 
> What do others, like Lukas and other Seaside people think of it ?
> 
> The basic point it: it can only be better than the older code.
> But on the other hand, maybe the leap could be even bigger still ?
> Having a facade for a pluggable http client is one step.
> 
> Having a good basic HTTP client and server is very important.
> 
> Sven
> 
> On 06 Jul 2010, at 09:30, Stéphane Ducasse wrote:
> 
>> to replace the old code?
>> 
>> Stef
>> 
>> ___
>> Pharo-project mailing list
>> Pharo-project@lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
> 
> 
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] Pharo on OLPC XO kid notebook


On Jul 6, 2010, at 6:24 PM, Hilaire Fernandes wrote:

> OLPC moto is based from day one on the use of dynamic language to design the 
> content coming with their notebook.
> 
> It is to write content but also to allow kids to examine source code, edit it 
> and test it ; as we are doing continuously in Smalltalk.
> They even think about a source-code key in the keyboard to instantaneously 
> open a source code browser exposing the code of a running application.
> 
> Now that Pharo 1.1 is in good sigh and as we are not ashame any more to show 
> how Smalltalk looks like we could also produce a release of Pharo for OLPC XO 
> Sugar environment. It is definitely a good opportunity to bring an 
> interesting tool to neutral mind (kids). In the other hand, it will 
> definitely help to bring awareness about Pharo.  For example, without any 
> action of my part, DrGeoII was downloaded about 180'000 times in one year for 
> XO.
> 
> Any takers?

any idea of the task?
what does it implies?

> Hilaire
> 
> PS: I have a couple of XO machines for testing purpose.

I gave mine to richie for SqueakNOS :)
> 
> 
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] [BetaTesting] [ANN] Pharo-1.1-11406-rc3dev10.07.1

thanks david
It would be great to start removing what does not work or rethink then like the 
smart groups.
I love smart groups but you were diving in your PhD and they need a bit love 
and care.

Stef

On Jul 6, 2010, at 3:00 PM, David Röthlisberger wrote:

> I fixed O2 to make it work in latest Pharo.
> Please test.
> 
> Cheers,
> David
> 
> > I vote for fixing O2!
> > On 05 Jul 2010, at 11:16, Alexandre Bergel wrote:
> >
> >> It is not clear what we (or at least I) should do.
> >> Maintaining two browsers is clearly not an option.
> >> Cheers,
> >> Alexandre
> >>
> >>
> >> On 5 Jul 2010, at 16:53, Johan Fabry wrote:
> >>
> >>> BTW it's even worse than initially thought: no classes are shown when I 
> >>> click on a category, and doing a find class yields a DNU. So the browser 
> >>> is basically broken.
> >>>
> >>> On 05 Jul 2010, at 10:39, Alexandre Bergel wrote:
> >>>
>  I can have a look at it within the next few days (I am currently in 
>  half-holidays).
> 
>  Cheers,
>  Alexandre
> 
> 
>  On 2 Jul 2010, at 22:27, Mariano Martinez Peck wrote:
> 
> >
> > 2010/7/2 Johan Fabry 
> >
> > This RC has problems with 02, I get the below 3 deprecated warnings 
> > when opening a new browser. Who do I notify?
> >
> >
> > To the O2 "mainteiners". Alexandre Bergel and David Röthlisberger as I 
> > am aware. I cc'ed them.
> >
> > Cheers
> >
> > Mariano
> >
> > The method Collection asSortedArray has been deprecated.
> > Use asArray sort
> > The method Collection asSortedArray has been deprecated.
> > Use asArray sort
> > The method Boolean and:and:and:and: has been deprecated.
> > Use and: instead
> >
> > On 01 Jul 2010, at 18:29, Mariano Martinez Peck wrote:
> >
> >> Hi folks. I am glad to announce the Pharo 1.1 RC3. It has not too much 
> >> changes in compare to RC2. The main change is the menu structure. I 
> >> also updated to newest version of external packages.
> >> Here is the image:
> >>
> >> https://gforge.inria.fr/frs/download.php/27241/Pharo-1.1-11406-rc3dev10.07.1.zip
> >>
> >> We would really appreaciate feedback and help to fix the failing tests.
> >> Cheers
> >>
> >> Mariano
> >> ___
> >> Pharo-project mailing list
> >> Pharo-project@lists.gforge.inria.fr
> >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
> > --
> > Johan Fabry   jfa...@dcc.uchile.cl - http://dcc.uchile.cl/~jfabry
> > PLEIAD Lab - Computer Science Department (DCC) - University of Chile
> >
> >
> >
> >
> > ___
> > Pharo-project mailing list
> > Pharo-project@lists.gforge.inria.fr
> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
> >
>  --
>  _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
>  Alexandre Bergel  http://www.bergel.eu
>  ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.
> 
> 
> 
> 
> 
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] Issue 2635 - methods recategorization

pavel

could you chop it and send it piece by piece to the list so that everybody can 
get a feel about it
and discuss if necessary?
I'm sorry but I like that we act a group and not a bunch of cool individual and 
building a mind-share is important
for me.

Stef
On Jul 6, 2010, at 4:43 PM, Pavel Krivanek wrote:

> Hi,
> 
> I finished the list of changes for the issue
> http://code.google.com/p/pharo/issues/detail?id=2635.
> 
> This issue is the next step after already integrated packages
> reorganization and the goal is to have compact package base a the
> small headless PharoKernel image.
> 
> Most changes are simple naming unification and some classes I skipped
> because they need deeper refactorings.
> 
> I will now check the list once more.
> 
> -- Pavel
> 
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] Alien on Pharo 1.2 on Mac

you do not have access to the alien repository?
can you ask john to gve you access to it?

On Jul 6, 2010, at 3:41 PM, Luc Fabresse wrote:

> Hi all,
> 
> We provide a usable version of Alien to Pharo 1.2 (all tests green on OSX).
> We committed the corrected package on the Ocean squeaksource repository : 
> http://squeaksource.com/Ocean
> (Alien-Core-LucFabresse.64.mcz)
> 
> We didn't look in details to the method 
> SystemDictionary>>recreateSpecialObjectsArray introduced by Alien-Core-63.
> It is now unsed because Smalltalk points to a SmalltalkImage.
> This need to be checked before possibly removal.
> 
> Another point would be to update the metacello configuration 
> ConfigurationOfAlien.
> 
> Luc and Noury
> 
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] Markup Builder in Smalltalk

There is an interest! Please submit/publish it...
Now What is the exact API I found cNode: a bit a bad name. What does it mesn 
childrenNode:

newBldr := XMLBuilder new xmlPreprocessor.
newBldr mbAttr: #(‘a=”6″‘ ‘b=”7″‘); test: ‘welcome to builders’

why new and xmlPreprocessor

mbAttr: sucks also!

Could you shine a bit the API to be reader friendly?

Stef

On Jul 6, 2010, at 12:32 PM, Sudhakar Krishnamachari wrote:

> More or less exactly the same..except the syntax.. but includes the CDATA, 
> Comments, plainText, preproc etc..
> 
> instead of tag: with: .. I went off to..
> 
> {theTag}: theText cNode: [] 
> 
> mbAttr: taking a collection of assocs or strings.. for the attrib.
> 
> 
> tabs are integrated with valueStringTrimmed dummping it without tabs/crlf..
> 
> will see if I can check in this too as an alternative to see means of merging 
> the frameworks for best use..
> *
> 
> Just check "XMLWriter-tbn.5" which can be found in 
> "http://squeaksource.com/PharoGoodies/";
> 
> 
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] Markup Builder in Smalltalk

what I often wanted is to be able to generate valid xml without having to load 
seaside.
Just getting the canvas. So may be lighter solution is interesting.

On Jul 6, 2010, at 11:20 AM, Lukas Renggli wrote:

> Seaside provides that kind of functionality.
> 
> Lukas
> 
> 2010/7/6 Sudhakar Krishnamachari :
>> Is there any general interest in Markup Builder...a la Groovy..?
>> 
>> http://skrishnamachari.wordpress.com/2010/07/06/markupbuilder-in-smalltalk/
>> 
>> 
>> 
>> ___
>> Pharo-project mailing list
>> Pharo-project@lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>> 
> 
> 
> 
> -- 
> Lukas Renggli
> www.lukas-renggli.ch
> 
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] Release Core?


On Jul 6, 2010, at 9:48 AM, Mariano Martinez Peck wrote:

> 
> 
> 2010/7/6 Adrian Lienhard 
> (moving this thread to pharo-dev)
> 
> Context: green tests for Pharo 1.1 (currently at RC4).
> 
> Thanks Mariano, I went through your list of tests.
> 
> In summary, what needs to be done:
> - Fixes for Nile
> - Fix one failing Shout test
> - Adaptation/fixes of external packages: method wrappers, sound, morphic 
> examples
> 
> In detail:
> 
> Needs fixing
> ---
> SHParserST80Test>>#testNumbers
> 
> See 
> http://forum.world.st/Problem-with-number-parsing-in-Shout-help-needed-td2276474.html#a2276474
> 
> Nicolas Cieller explains there the reason. I hadn't time to analize it, thus 
> (and I am completly newbie with that).
> If someone can directly commit to Shout I would appreaciate it. 
> 
>  
> NSMultiByteBinaryOrTextStreamTest>>#testFileOut
> NSSmartRefStreamTest>>#testGlobal
> NSMCPseudoFileStreamTest>>#testFileOut
> NSMCPseudoFileStreamTest>>#testFileOutFileIn
> NSRWBinaryOrTextStreamTest>>#testFileOut
> NSRWBinaryOrTextStreamTest>>#testFileOutFileIn
> ReleaseTest>>#testUndeclared
> 
> Undeclared classes and variables (these external packages need to be adapted 
> or should not be loaded)
> -
> WatchMorph references ColorPickerMorph
> AbstractSound references FillInTheBlank
> EnvelopeEditorMorph, MidiInputMorph, and ScorePlayerMorph reference 
> PopUpChoiceMorph
> KeyboardMorphForInput, MidiInputMorph, and ScorePlayerMorph reference 
> SimpleSwitchMorph
> ArchiveViewer references StandardFileMenu
> ObjectAsMethodWrapper has undeclared variable named selector and wrappedClass
> 
> 
> uf  what do we do with this stuff?

I can have a look. This is why we must change the way we deal with externally 
managed by maintained packages.
We should try to get a special metacello configuration for pharo (pharo-core + 
packages) and that we work with pahro and
not core when we fixe stuff..

Stef


> 
>  
> Fixed, see attached cs (we had that already in 1.0 but apparently it was lost 
> for 1.1)
> ---
> WeakSetInspectorTest>>#testSymbolTableM6812
> 
> 
> 
> Great. Maybe we can integrate it in 1.0 together with 2547 (explained later)
>  
> 
> 
> Workes for me (when running each test alone)(?)
> 
> Most of them.
> testOneGigAllocation and
> testPositionPastEndIsAtEnd
> 
> fail always for me.  
> 
>  
> ---
> ObjectAsOneTimeMethodWrapperTest>>#testInstallOnClassCategory
> MCInitializationTest>>#testWorkingCopy
> WeakRegistryTest>>#testFinalization
> FileStreamTest>>#testPositionPastEndIsAtEnd
> 
> This was fixes in 1.2 by the ticket 2547. Maybe we can integrate it in 1.1 
> also?
> 
>  
> AllocationTest>>#testOneGigAllocation
> 
> Cheers,
> Adrian
> 
> 
> On Jul 5, 2010, at 22:06 , Mariano Martinez Peck wrote:
> 
> > On Mon, Jul 5, 2010 at 8:00 PM, Adrian Lienhard 
> > wrote:
> >
> >> I updated the download page.
> >>
> >>
> > thanks
> >
> >
> >> Cheers,
> >> Adrian
> >>
> >> BTW, what is the state of the tests? Last time I run them, there were a lot
> >> of failures...
> >>
> >>
> > much better. I fixed a lot of Nile with your suggestion and further
> > problems/fixes.
> >
> > My results so far are these:
> >
> > 9764 run, 9697 passes, 53 expected failures, 8 failures, 6 errors, 0
> > unexpected passes
> > Failures:
> > AllocationTest>>#testOneGigAllocation
> > NSMultiByteBinaryOrTextStreamTest>>#testFileOut
> > SHParserST80Test>>#testNumbers
> > ReleaseTest>>#testUndeclared
> > FileStreamTest>>#testPositionPastEndIsAtEnd
> > WeakRegistryTest>>#testFinalization
> > MCInitializationTest>>#testWorkingCopy
> > ObjectAsOneTimeMethodWrapperTest>>#testInstallOnClassCategory
> >
> > Errors:
> > WeakSetInspectorTest>>#testSymbolTableM6812
> > NSSmartRefStreamTest>>#testGlobal
> > NSMCPseudoFileStreamTest>>#testFileOut
> > NSMCPseudoFileStreamTest>>#testFileOutFileIn
> > NSRWBinaryOrTextStreamTest>>#testFileOut
> > NSRWBinaryOrTextStreamTest>>#testFileOutFileIn
> >
> >
> >
> >
> >
> >> ___
> >> http://www.adrian-lienhard.ch/
> >>
> >> On Jul 5, 2010, at 18:26 , Stéphane Ducasse wrote:
> >>
> >>> Yes
> >>>
>  I have just created the image RC4. It is in
> >> https://gforge.inria.fr/frs/download.php/27254/Pharo-1.1-11409-rc4dev10.07.2.zip
> 
>  Adrian, do you think we should update the link of 1.1 from the website
> >> to this one?
> 
>  Cheers
> 
>  Mariano
> >>>
> >>
> >>
> 
> 
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
> 
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] python documentation rocks

Hi,
> 
> Python 2.7 has just been released, documentation is up to date. 
> http://docs.python.org/
> 
> That's so great. I hope we will have a process for Pharo's documentation. Is 
> it possible to automatically generate a changelog for Pharo 1.1 ?

Yes. Scriptloader logStream (may be this is broken)

Now we can also as lukas mentioned use the code web site y entering date we can 
generate a list of fixed items.
The problems is that we are not enough, even if this is getting better. And we 
should have started 5 years ago.

Stef

> Cheers
> 
> Laurent
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] [update 1.2] #12037


On Jul 6, 2010, at 9:49 AM, Marcus Denker wrote:

> 12037
> -
> 
> Issue 2590:   Remove PreferenceBrowser package

kind of a dream.
Soon Preference :)

> Issue 2645:   Remove System Package
> 
> 
> --
> Marcus Denker  -- http://www.marcusdenker.de
> INRIA Lille -- Nord Europe. Team RMoD.
> 
> 
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] I updated the how to contribute web page

this is a good idea.
I should do a pass on hernan feedback
and the help is also a good idea.

Stef

On Jul 6, 2010, at 9:48 AM, laurent laffont wrote:

> Hi,
> 
> I've seen http://book.pharo-project.org/book/Contribute
> 
> Should we Cut / Paste from google project's wiki ?  (So we have only one 
> source of documentation, that can be later integrated to HelpSystem).
> 
> Cheers,
> 
> Laurent Laffont
> 
> http://pharocasts.blogspot.com/
> http://magaloma.blogspot.com/
> 
> 
> On Tue, Jul 6, 2010 at 12:21 AM, Stéphane Ducasse  
> wrote:
> thanks hernan.
> I will not have the time to edit the changes but this is important that we 
> keep this information upto date and that
> people can understand it.
> 
> Stef
> 
> On Jul 5, 2010, at 4:34 PM, Hernán Morales Durand wrote:
> 
> > Ok,
> >
> > 
> > Here: "First and foremost, you must be aware that the Pharo project
> > only accepts code published under the MIT license. By publishing your
> > code in the SqueakSource Pharo or PharoInbox repositories, you are
> > agreeing to this condition. With that out of the way, here are the
> > steps to submit your contributions. "
> >
> > Please provide a link which explain the implications of code published
> > under the MIT license. Or better, a little comparison table between
> > different licensing schemes.
> >
> > 
> > Here: "If your change is directly related to a Mantis report, add the
> > label "Type-Mantis" and add the Mantis ticket number in front of the
> > subject. Else choose another appropriate label "
> >
> > Please clarify or link to. Manits is the bugs.squeak.org right? It
> > should be named by what it is, and not by the tool which is used for
> > bug tracking (if they change their tool 10 times, you must update the
> > page 10 times)
> >
> > 
> > Here: "Announce your contribution by sending a mail to the mailing
> > list and herewith ask to have somebody review your change. This person
> > should change the state of the issue to "Verified". "
> >
> > Provide a link to the mailing list. Note "herewith" is most used and
> > understood as a legal term.
> >
> > 
> > Here: "For complex changes use a slice since there is a much better
> > merging support. "
> >
> > What is a complex change? (please include this information in the page too)
> >
> > 
> > "Prepare a changeset with your changes. File it out. Important: Put
> > your Full name instead of your initials, it will help up to contact
> > you as it is often necessary. Do not use space and only alphabetical
> > characters. "
> >
> > 1) This is killing more than 50% of the habitants of the world :) What
> > happens with contributors without latin alphabet? how they setup their
> > system? (that should be included)
> >
> > 2) What is the problem with using space? If it is a limitation imposed
> > by a tool then the tool should be responsible of trimming all blanks,
> > not the users.
> >
> > 3) How do you distinguish between two John Smith? And how do you
> > contact contributors? (I've never wrote my e-mail or gmail user name
> > in a Pharo image).
> >
> > 4) Some brief explanation on how to create a changeset would be nice.
> >
> > 
> > Finally, this information should be in all images. Better, provide a
> > wizard to guide this process, it sounds like a nice excercise to do a
> > standard window flow with Morphic.
> >
> > Cheers,
> >
> > Hernán
> >
> > 2010/7/5 stephane ducasse :
> >> please comment :)
> >> http://code.google.com/p/pharo/wiki/HowToContribute
> >>
> >> Stef
> >>
> >> ___
> >> Pharo-project mailing list
> >> Pharo-project@lists.gforge.inria.fr
> >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
> >>
> >
> > ___
> > Pharo-project mailing list
> > Pharo-project@lists.gforge.inria.fr
> > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
> 
> 
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
> 
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] Markup Builder in Smalltalk (XMLWriter)

Good may be we should publish with the XMLParser repository?

On Jul 6, 2010, at 12:19 PM, Torsten Bergmann wrote:

> Just check "XMLWriter-tbn.5" which can be found in 
> "http://squeaksource.com/PharoGoodies/";
> 
> --
> |writer|
> writer := XMLTagWriter xml.
> writer comment: 'A new xml file'.
> writer tag: 'package' with: [ 
>   writer cData: 'name' with: 'XMLWriter'.
> ].
> writer contents
> 
> returns
> 
> 
> 
> 
>
> 
> --
> 
> You can also access the stream (writer stream). 
> Indenting is not yet working fully but at least 
> it should give you idea. Check out the test cases for 
> more. 
> 
> I once saw such an XMLWriter written by Ernest Micklei
> in VAST (credits for the idea) and rebuilt it in Pharo.
> 
> Bye
> T.
> -- 
> GMX DSL: Internet-, Telefon- und Handy-Flat ab 19,99 EUR/mtl.  
> Bis zu 150 EUR Startguthaben inklusive! http://portal.gmx.net/de/go/dsl
> 
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] DateAndTime>>asUnixTime should ignore timezones?

thanks a lot.

Stef

On Jul 6, 2010, at 12:31 PM, Nick Ager wrote:

> Hi Stef
> 
> did you run the tests after your fixes?
> Because I tried to integrate another fixes related to date = string as 
> proposed in Squeak by chris
> but a lot of date related tests break. and we should be cautious.
> 
> 
> I checked for senders of asUnixTime in the image and there weren't any. Just 
> to be on the safe side I've run all the tests in KernelTests-Chronology; all 
> green.
> 
> I've updated the issue (#2644) to include a test and have attached a change 
> set which includes the change to asUnixTime and an associated test.
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] feedup of selecting doit or typing " above and below expressions in comments?


On Jul 6, 2010, at 2:59 PM, Torsten Bergmann wrote:

> Henry wrote:
>> Personally, being used to VisualWorks, I always get bitten by having to 
>> >select the entire selector for implementors/senders... :)
> 
> +1

enter a bug entry to describe what should be done.

> Another thing that is related to the above and to the different browsers:
> 
> In Core: When I select a method I can choose "Senders of..." 
> and "Implementors of..." to either search for senders/implementors
> of the selected method AND the messages sent into the selected 
> method.
> 
> In Pharo: with OB I can just do "senders" and "implementors"
>  which looks for the senders/implementors of the selected method
>  One is NOT able to search for senders/implementors of 
>  the messages sent within the selected method.
>  Here I have to select the entire selector which is
>  time consuming as described above.

enter a bug entry.


> So Pharo with OB is (compared to core) really a step backwards here.

I imagine that the enh I did also to get Cmd-M on class name browsing the class 
and Cmd-B on 
selectors do an implementors should also be pushed in OB.



> -- 
> GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
> Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01
> 
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

[Pharo-project] [update 1.2] #12038

2010-07-06 Thread Marcus Denker

12038
-

Issue 2648: LanguageEnvironment>>setupSqueaklandSpecifics
Issue 2647: Consistency by providing uppercase menu items in Tools menus
Issue 2649: World tasklist navigation
Issue 2644: DateAndTime>>asUnixTime should ignore timezones?

--
Marcus Denker  -- http://www.marcusdenker.de
INRIA Lille -- Nord Europe. Team RMoD.


___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] Cleaning WriteBarrier (as used in Magma)

2010-07-06 Thread Chris Muller

Thanks, I will look for your updated WriteBarrier package to include
with the next Magma.  I have just copied my own latest WriteBarrier to
the MagmaTester project of squeaksource.

---
Name: WriteBarrier-cmm.27
Author: cmm
Time: 19 June 2010, 4:41:13.886 pm
UUID: 84945d10-b0eb-419b-a6bc-2de227aac87a
Ancestors: WriteBarrier-pmm.26

Removed PseudoContext extension for compatibility with Squeak 4.2+.
--

WriteBarrier unfortunately doesn't work in either of Pharo or Squeak
4.1+.  I am tempted to remove it from the suite altogether, but to do
so would break backward compatibility with 3.9 who may be using
WriteBarrier, because the implementation requires the handler
(MaTransaction) to inherit from the WriteBarrier class itself..  :-(

Thanks,
  Chris

On Tue, Jul 6, 2010 at 4:44 AM, Torsten Bergmann  wrote:
> Hi Avi,
>
> how is life at Twitter ;)
>
> Would it be possible that you add me as a developer on
>
> http://www.squeaksource.com/WriteBarrier
>
> so I can clean up underscore assignment in the package.
>
> WriteBarrier is used in Magma (see ConfigurationOfMagma)
> which is installable right from a workspace in the
> upcoming Pharo 1.1 release. Currently this fails since
> by default underscore assignment is not allowed in Pharo.
>
> Thanks
> Torsten
> --
> GMX DSL: Internet-, Telefon- und Handy-Flat ab 19,99 EUR/mtl.
> Bis zu 150 EUR Startguthaben inklusive! http://portal.gmx.net/de/go/dsl
>
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] PluginBasedJPEGReadWriter anomaly

Well, I get the same result when loading any JPEG (Windows VM 4.0.2).
Easiest to just drag a JPEG image into the Pharo window and choose "open 
graphic in window".

Distinctive top-left pixel (actually transparent now I investigate further) 
along with bad edge.

To compare, change
PluginBasedJPEGReadWriter>>understandsImageFormat

to return false (will then use original JPEGReadWriter).

Regards, Gary

  - Original Message - 
  From: Eliot Miranda 
  To: Pharo-project@lists.gforge.inria.fr 
  Cc: Gary Chambers 
  Sent: Tuesday, July 06, 2010 6:23 PM
  Subject: Re: [Pharo-project] PluginBasedJPEGReadWriter anomaly


  Hi Gary,


  2010/7/6 Gary Chambers 

Hi all.
Iv'e noticed a slight anomaly with the PluginBasedJPEGReadWriter when 
reading jpeg files (at least on Windows platforms).
The upper left pixel appears to be white and the whole left-hand column of 
pixels have anomalous values.


  COuld you help me reproduce this case exactly?  We had a crash a few weeks 
ago in te JPEG plugin but have not been able to find the data that reproduced 
it.  Looks like you have a case which causes the plugin to behave incorrectly.  
So how do I run the plygin case and the non-plugin case side-by-side?


  TIA
  Eliot


Attached, for reference, are screenshots when using the plugin, the 
original Smalltalk implementation and Windows picture viewer.

Regards, Gary


___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] PluginBasedJPEGReadWriter anomaly

2010-07-06 Thread Eliot Miranda

Hi Gary,

2010/7/6 Gary Chambers 

>  Hi all.
> Iv'e noticed a slight anomaly with the PluginBasedJPEGReadWriter when
> reading jpeg files (at least on Windows platforms).
> The upper left pixel appears to be white and the whole left-hand column of
> pixels have anomalous values.
>

COuld you help me reproduce this case exactly?  We had a crash a few weeks
ago in te JPEG plugin but have not been able to find the data that
reproduced it.  Looks like you have a case which causes the plugin to behave
incorrectly.  So how do I run the plygin case and the non-plugin case
side-by-side?

TIA
Eliot


>
> Attached, for reference, are screenshots when using the plugin, the
> original Smalltalk implementation and Windows picture viewer.
>
> Regards, Gary
>
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] should we move pharo to use webclient?

2010-07-06 Thread Germán Arduino

Yes!

I used WebClient to experiment but also to a (little) commercial project and
it works very well.

As Sven said the code is quite readable/understandable/malleable and I would
add, easy to extend.

+1 to this idea of add it to Pharo.

Germán.


2010/7/6 Stéphane Ducasse 

> to replace the old code?
>
> Stef
>
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

[Pharo-project] Pharo on OLPC XO kid notebook

2010-07-06 Thread Hilaire Fernandes

OLPC moto is based from day one on the use of dynamic language to design 
the content coming with their notebook.


It is to write content but also to allow kids to examine source code, 
edit it and test it ; as we are doing continuously in Smalltalk.
They even think about a source-code key in the keyboard to 
instantaneously open a source code browser exposing the code of a 
running application.


Now that Pharo 1.1 is in good sigh and as we are not ashame any more to 
show how Smalltalk looks like we could also produce a release of Pharo 
for OLPC XO Sugar environment. It is definitely a good opportunity to 
bring an interesting tool to neutral mind (kids). In the other hand, it 
will definitely help to bring awareness about Pharo.  For example, 
without any action of my part, DrGeoII was downloaded about 180'000 
times in one year for XO.


Any takers?

Hilaire

PS: I have a couple of XO machines for testing purpose.


___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

[Pharo-project] World keyboard navigation for tasklist

New issue http://code.google.com/p/pharo/issues/detail?id=2649

Regards, Gary
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] Issue 2647 fixed for 1.2 - consistent menu items with uppercase for all tools

Having look around at things recently, at least the "from triplets" ones 
deliberately capitalise.
Worth having things done right in the first instance (and forced 
capitalisation removed) though (for translation etc.).


Regards, Gary

- Original Message - 
From: "Torsten Bergmann" 

To: 
Sent: Tuesday, July 06, 2010 4:35 PM
Subject: [Pharo-project] Issue 2647 fixed for 1.2 - consistent menu items 
with uppercase for all tools




It is a change that affects the way people are
used to the system - but I think we should integrate it
to align with already cleaned up menus and known host platforms.

 "do it" -> "Do it"
 ...
and all tool menu items starting with uppercase.
Also the buttons I was able to find.

Ready to be harvested for 1.2:

http://code.google.com/p/pharo/issues/detail?id=2647

Bye
T.
--
GMX DSL: Internet-, Telefon- und Handy-Flat ab 19,99 EUR/mtl.
Bis zu 150 EUR Startguthaben inklusive! http://portal.gmx.net/de/go/dsl

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project 



___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

[Pharo-project] Issue 2647 fixed for 1.2 - consistent menu items with uppercase for all tools

It is a change that affects the way people are
used to the system - but I think we should integrate it
to align with already cleaned up menus and known host platforms.

  "do it" -> "Do it"
  ...
and all tool menu items starting with uppercase.
Also the buttons I was able to find.

Ready to be harvested for 1.2:

http://code.google.com/p/pharo/issues/detail?id=2647

Bye
T.
-- 
GMX DSL: Internet-, Telefon- und Handy-Flat ab 19,99 EUR/mtl.  
Bis zu 150 EUR Startguthaben inklusive! http://portal.gmx.net/de/go/dsl

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] Cleaning WriteBarrier (as used in Magma)

2010-07-06 Thread Miguel Enrique Cobá Martínez

El mar, 06-07-2010 a las 11:44 +0200, Torsten Bergmann escribió:
> Hi Avi,
> 
> how is life at Twitter ;)
> 
> Would it be possible that you add me as a developer on 
> 
> http://www.squeaksource.com/WriteBarrier
> 
> so I can clean up underscore assignment in the package.
> 
> WriteBarrier is used in Magma (see ConfigurationOfMagma)
> which is installable right from a workspace in the
> upcoming Pharo 1.1 release. Currently this fails since
> by default underscore assignment is not allowed in Pharo.
> 
> Thanks
> Torsten

Maybe that email isn't monitored currently by Avi.
In his page he states that 
b...@avibryant.com
is the email for contact
You can also reach them in twitter
http://twitter.com/avibryant

Cheers

-- 
Miguel Cobá
http://miguel.leugim.com.mx


___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] [BetaTesting] [ANN] Pharo-1.1-11406-rc3dev10.07.1

2010-07-06 Thread Alexandre Bergel

Thanks David!

Alexandre


On 6 Jul 2010, at 15:52, Johan Fabry wrote:

> 
> It seems to work OK in rc4. Opens normally and I can browse without problems. 
> Thanks David! :-)
> 
> On 06 Jul 2010, at 09:00, David Röthlisberger wrote:
> 
>> I fixed O2 to make it work in latest Pharo.
>> Please test.
>> 
>> Cheers,
>> David
> 
> --
> Johan Fabry   
> jfa...@dcc.uchile.cl - http://dcc.uchile.cl/~jfabry
> PLEIAD Lab - Computer Science Department (DCC) - University of Chile
> 
> 
> 
> 
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

-- 
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel  http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.






___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

[Pharo-project] Issue 2635 - methods recategorization

Hi,

I finished the list of changes for the issue
http://code.google.com/p/pharo/issues/detail?id=2635.

This issue is the next step after already integrated packages
reorganization and the goal is to have compact package base a the
small headless PharoKernel image.

Most changes are simple naming unification and some classes I skipped
because they need deeper refactorings.

I will now check the list once more.

-- Pavel

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] [BetaTesting] [ANN] Pharo-1.1-11406-rc3dev10.07.1

2010-07-06 Thread Johan Fabry


It seems to work OK in rc4. Opens normally and I can browse without problems. 
Thanks David! :-)

On 06 Jul 2010, at 09:00, David Röthlisberger wrote:

> I fixed O2 to make it work in latest Pharo.
> Please test.
> 
> Cheers,
> David

--
Johan Fabry   
jfa...@dcc.uchile.cl - http://dcc.uchile.cl/~jfabry
PLEIAD Lab - Computer Science Department (DCC) - University of Chile




___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

[Pharo-project] Alien on Pharo 1.2 on Mac

2010-07-06 Thread Luc Fabresse

Hi all,

We provide a usable version of Alien to Pharo 1.2 (all tests green on OSX).
We committed the corrected package on the Ocean squeaksource repository :
http://squeaksource.com/Ocean
(Alien-Core-LucFabresse.64.mcz)

We didn't look in details to the method
SystemDictionary>>recreateSpecialObjectsArray introduced by Alien-Core-63.
It is now unsed because Smalltalk points to a SmalltalkImage.
This need to be checked before possibly removal.

Another point would be to update the metacello configuration
ConfigurationOfAlien.

Luc and Noury
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] [SPAM] should we move pharo to use webclient?

+1

Regards, Gary

- Original Message - 
From: "Lukas Renggli" 

To: 
Sent: Tuesday, July 06, 2010 2:06 PM
Subject: Re: [Pharo-project] [SPAM] should we move pharo to use webclient?

What do others, like Lukas and other Seaside people think of it ?

I like it, it should be the default in the image.

Lukas

--
Lukas Renggli
www.lukas-renggli.ch

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] [SPAM] should we move pharo to use webclient?

> What do others, like Lukas and other Seaside people think of it ?

I like it, it should be the default in the image.

Lukas

-- 
Lukas Renggli
www.lukas-renggli.ch

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] [SPAM] should we move pharo to use webclient?

2010-07-06 Thread Sven Van Caekenberghe

Yes!!

It now loads without patches into Pharo 1.1 rc2
I used its client and server part, seaside adaptor, it all works.

The code is quite readable/understandable/malleable.

I did not yet test the WebClient-HTTP package which patches HTTPSocket to 
replace the old code,
which is obviously important (it then gets used by MC and the rest of 
Smalltalk).

The unit tests also have to be double checked.

What do others, like Lukas and other Seaside people think of it ?

The basic point it: it can only be better than the older code.
But on the other hand, maybe the leap could be even bigger still ?
Having a facade for a pluggable http client is one step.

Having a good basic HTTP client and server is very important.

Sven

On 06 Jul 2010, at 09:30, Stéphane Ducasse wrote:

> to replace the old code?
> 
> Stef
> 
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] [BetaTesting] [ANN] Pharo-1.1-11406-rc3dev10.07.1

2010-07-06 Thread David Röthlisberger


I fixed O2 to make it work in latest Pharo.
Please test.

Cheers,
David

> I vote for fixing O2!
> On 05 Jul 2010, at 11:16, Alexandre Bergel wrote:
>
>> It is not clear what we (or at least I) should do.
>> Maintaining two browsers is clearly not an option.
>> Cheers,
>> Alexandre
>>
>>
>> On 5 Jul 2010, at 16:53, Johan Fabry wrote:
>>
>>> BTW it's even worse than initially thought: no classes are shown when I click on 
a category, and doing a find class yields a DNU. So the browser is basically broken.

>>>
>>> On 05 Jul 2010, at 10:39, Alexandre Bergel wrote:
>>>
 I can have a look at it within the next few days (I am currently in 
half-holidays).

 Cheers,
 Alexandre


 On 2 Jul 2010, at 22:27, Mariano Martinez Peck wrote:

>
> 2010/7/2 Johan Fabry 
>
> This RC has problems with 02, I get the below 3 deprecated warnings when 
opening a new browser. Who do I notify?

>
>
> To the O2 "mainteiners". Alexandre Bergel and David Röthlisberger as I am 
aware. I cc'ed them.

>
> Cheers
>
> Mariano
>
> The method Collection asSortedArray has been deprecated.
> Use asArray sort
> The method Collection asSortedArray has been deprecated.
> Use asArray sort
> The method Boolean and:and:and:and: has been deprecated.
> Use and: instead
>
> On 01 Jul 2010, at 18:29, Mariano Martinez Peck wrote:
>
>> Hi folks. I am glad to announce the Pharo 1.1 RC3. It has not too much 
changes in compare to RC2. The main change is the menu structure. I also updated to 
newest version of external packages.

>> Here is the image:
>>
>> 
https://gforge.inria.fr/frs/download.php/27241/Pharo-1.1-11406-rc3dev10.07.1.zip
>>
>> We would really appreaciate feedback and help to fix the failing tests.
>> Cheers
>>
>> Mariano
>> ___
>> Pharo-project mailing list
>> Pharo-project@lists.gforge.inria.fr
>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
> --
> Johan Fabry   jfa...@dcc.uchile.cl - http://dcc.uchile.cl/~jfabry
> PLEIAD Lab - Computer Science Department (DCC) - University of Chile
>
>
>
>
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>
 --
 _,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
 Alexandre Bergel  http://www.bergel.eu
 ^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.





___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

[Pharo-project] feedup of selecting doit or typing " above and below expressions in comments?

Henry wrote:
> Personally, being used to VisualWorks, I always get bitten by having to 
> >select the entire selector for implementors/senders... :)

+1

Another thing that is related to the above and to the different browsers:

In Core: When I select a method I can choose "Senders of..." 
 and "Implementors of..." to either search for senders/implementors
 of the selected method AND the messages sent into the selected 
 method.

In Pharo: with OB I can just do "senders" and "implementors"
  which looks for the senders/implementors of the selected method
  One is NOT able to search for senders/implementors of 
  the messages sent within the selected method.
  Here I have to select the entire selector which is
  time consuming as described above.

So Pharo with OB is (compared to core) really a step backwards here.
-- 
GRATIS für alle GMX-Mitglieder: Die maxdome Movie-FLAT!
Jetzt freischalten unter http://portal.gmx.net/de/go/maxdome01

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] feedup of selecting doit or typing " above and below expressions in comments?

one step at a time :)
first the complete line

Stef

On Jul 6, 2010, at 2:30 PM, Henrik Johansen wrote:

> On Jul 6, 2010, at 1:37 16PM, stephane ducasse wrote:
> 
>> with this little change we can execute simply run in the following line just 
>> by having the mouse on the line and pressing doit even if there are comments 
>> around
>>  
>>  "self run"
>> 
>> We should stop to turn around the system all the system but fix it to make 
>> us more productive.
>> 
>> 
> Personally, being used to VisualWorks, I always get bitten by having to 
> select the entire selector for implementors/senders... :)
> 
> Cheers,
> Henry
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] Changes not logged

yes there is bug entry for some weeks now.
And it would be nice to fix it.

On Jul 6, 2010, at 2:34 PM, Lukas Renggli wrote:

> I noticed that "World > Tools > Recover lost changes ..." does not log
> any longer method removals. Also class definitions, class removals,
> and do-its are missing in the .changes file. I think this is since
> Pharo1.1rc3, but maybe earlier. Did anybody else notice that too?
> 
> Lukas
> 
> -- 
> Lukas Renggli
> www.lukas-renggli.ch
> 
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project


___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] should we move pharo to use webclient?

2010-07-06 Thread Adrian Lienhard

Yes, that would be great!

I've not extensively used WebClient so far but from some experimentation it 
seems to work well and it provides the interface I am expecting. Comparing with 
the old implementation it can only be better ;)

Adrian

On Jul 6, 2010, at 09:30 , Stéphane Ducasse wrote:

> to replace the old code?
> 
> Stef
> 
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

[Pharo-project] Changes not logged

I noticed that "World > Tools > Recover lost changes ..." does not log
any longer method removals. Also class definitions, class removals,
and do-its are missing in the .changes file. I think this is since
Pharo1.1rc3, but maybe earlier. Did anybody else notice that too?

Lukas

-- 
Lukas Renggli
www.lukas-renggli.ch

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] feedup of selecting doit or typing " above and below expressions in comments?

2010-07-06 Thread Henrik Johansen

On Jul 6, 2010, at 1:37 16PM, stephane ducasse wrote:

> with this little change we can execute simply run in the following line just 
> by having the mouse on the line and pressing doit even if there are comments 
> around
>   
>   "self run"
> 
> We should stop to turn around the system all the system but fix it to make us 
> more productive.
> 
> 
Personally, being used to VisualWorks, I always get bitten by having to select 
the entire selector for implementors/senders... :)

Cheers,
Henry
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

[Pharo-project] Fwd: [smalltalk-research] FYI: Smalltalk/Seaside developer



Begin forwarded message:

> From: Geert Claes 
> Date: July 6, 2010 10:11:32 AM GMT+02:00
> To: Smalltalk Research 
> Subject: [smalltalk-research] FYI: Smalltalk/Seaside developer
> Reply-To: smalltalk-resea...@googlegroups.com
> 
> Boris Popov on the Seaside group on LinkedIn wrote:
> 
>> We are looking for another Smalltalk/Seaside developer to join our team at 
>> DeepCove Labs http://goo.gl/LyXE


___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

[Pharo-project] feedup of selecting doit or typing " above and below expressions in comments?

2010-07-06 Thread stephane ducasse

with this little change we can execute simply run in the following line just 
by having the mouse on the line and pressing doit even if there are comments 
around

"self run"

We should stop to turn around the system all the system but fix it to make us 
more productive.



ParagraphEditor-evaluateSelection.st
Description: Binary data
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

[Pharo-project] should we move pharo to use webclient?

to replace the old code?

Stef

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

[Pharo-project] Markup Builder in Smalltalk

More or less exactly the same..except the syntax.. but includes the
CDATA, Comments, plainText, preproc etc..

instead of tag: with: .. I went off to..

{theTag}: theText cNode: []

mbAttr: taking a collection of assocs or strings.. for the attrib.

tabs are integrated with valueStringTrimmed dummping it without tabs/crlf..

will see if I can check in this too as an alternative to see means of
merging the frameworks for best use..
*

Just check "XMLWriter-tbn.5" which can be found in
"http://squeaksource.com/PharoGoodies/";

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] DateAndTime>>asUnixTime should ignore timezones?

2010-07-06 Thread Nick Ager

Hi Stef

did you run the tests after your fixes?
> Because I tried to integrate another fixes related to date = string as
> proposed in Squeak by chris
> but a lot of date related tests break. and we should be cautious.
>
>
I checked for senders of asUnixTime in the image and there weren't any. Just
to be on the safe side I've run all the tests in KernelTests-Chronology; all
green.

I've updated the issue
(#2644)
to include a test and have attached a change set which includes the change
to asUnixTime and an associated test.
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

[Pharo-project] Markup Builder in Smalltalk (XMLWriter)

Just check "XMLWriter-tbn.5" which can be found in 
"http://squeaksource.com/PharoGoodies/";

--
|writer|
writer := XMLTagWriter xml.
writer comment: 'A new xml file'.
writer tag: 'package' with: [ 
writer cData: 'name' with: 'XMLWriter'.
].
writer contents

returns






--

You can also access the stream (writer stream). 
Indenting is not yet working fully but at least 
it should give you idea. Check out the test cases for 
more. 

I once saw such an XMLWriter written by Ernest Micklei
in VAST (credits for the idea) and rebuilt it in Pharo.

Bye
T.
-- 
GMX DSL: Internet-, Telefon- und Handy-Flat ab 19,99 EUR/mtl.  
Bis zu 150 EUR Startguthaben inklusive! http://portal.gmx.net/de/go/dsl

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

[Pharo-project] OB contextual menu item 'method containing' broken: is it useful?

2010-07-06 Thread Simon Denier

In 1.1 RC4 (and before), when opening the contextual menu in the source pane, 
there is an option for 'method containing' among the search actions.

It's not clear what is is supposed to do. Is it the OB implementation of the 
'method strings with it' action, which is also available?

Anyway, it is broken as it raises a DNU #allMethodsNoDoitsSelect:

--
 Simon




___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

[Pharo-project] Cleaning WriteBarrier (as used in Magma)

Hi Avi,

how is life at Twitter ;)

Would it be possible that you add me as a developer on 

http://www.squeaksource.com/WriteBarrier

so I can clean up underscore assignment in the package.

WriteBarrier is used in Magma (see ConfigurationOfMagma)
which is installable right from a workspace in the
upcoming Pharo 1.1 release. Currently this fails since
by default underscore assignment is not allowed in Pharo.

Thanks
Torsten
-- 
GMX DSL: Internet-, Telefon- und Handy-Flat ab 19,99 EUR/mtl.  
Bis zu 150 EUR Startguthaben inklusive! http://portal.gmx.net/de/go/dsl

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

[Pharo-project] Markup Builder in Smalltalk

I may perhaps be unaware of the XML/SGML builder generation from
Seaside, love to be pointed out to.., The Html generation of
Seaside uses explicit construct of classes ( WA**Tags) to do so..
Builders in dynamic manner
use doesNotUnderstand: construct to generate the stream..

The strength in this approach is a lighter construction.. just one
object creation for the entire sgml stream
creation..

Extensibility too therefore is available by default.. any tag/
attribute can be streamed without any extension
to creating a new class/ method..

The offside though is, it is streaming so no handling the DOM / tree
for manipulations..

Infact I feel it can be a good alternative mode to current seaside
markup streaming for the Html streaming ( for static content) too..but
that is specialization
of its use.. and not as yet worked out for handling the callbacks and
all special abilities of Seaside html streaming.

*
Seaside provides that kind of functionality.

Lukas

2010/7/6 Sudhakar Krishnamachari http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project>>:
>* Is there any general interest in Markup Builder...a la Groovy..?
*>*
*>* http://skrishnamachari.wordpress.com/2010/07/06/markupbuilder-in-smalltalk/
*>*
*>*
*>*
*>* ___
*>* Pharo-project mailing list
*>* Pharo-project at lists.gforge.inria.fr

*>* http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
*>*
*

--
Lukas Renggli
www.lukas-renggli.ch
___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

Re: [Pharo-project] Markup Builder in Smalltalk

Seaside provides that kind of functionality.

Lukas

2010/7/6 Sudhakar Krishnamachari :
> Is there any general interest in Markup Builder...a la Groovy..?
>
> http://skrishnamachari.wordpress.com/2010/07/06/markupbuilder-in-smalltalk/
>
>
>
> ___
> Pharo-project mailing list
> Pharo-project@lists.gforge.inria.fr
> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project
>



-- 
Lukas Renggli
www.lukas-renggli.ch

___
Pharo-project mailing list
Pharo-project@lists.gforge.inria.fr
http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

[Pharo-project] Markup Builder in Smalltalk