July 2010 - Pharo-dev - lists.pharo.org

Re: [Pharo-project] Fwd: [squeak-dev] Re: Debug-it and external calls

by Nicolas Cellier

hemiscient ? 2010/7/20 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> > enough half omniscient are enough :) > > On Jul 20, 2010, at 3:49 AM, Henrik Johansen wrote: > > > > > > > Den 19. juli 2010 kl. 23:04 skrev StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr>: > > > >> should this be integrated into pharo? > >> ifTrue: open a ticket please. > >> > >> Sorry but I'm not omniscient yet even if I work hard on it > >> > >> Stef > > > > That's ok, I am! ;) > > The change to use large frames for methods doing performs was integrated > in Pharo shortly after Igor initially raised the issue. > > I can't remember off-hand if they are part of 1.1 though. > > Darn, guess I'm not omnipotent after all. > > > > Cheers, > > Henry > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 20, 2010

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

by StÃ©phane Ducasse

done :) On Jul 20, 2010, at 7:25 PM, Miguel Enrique CobÃ¡ MartÃnez wrote: > This good summary should go directly to the collaboractive book. > > > El mar, 20-07-2010 a las 14:11 -0300, HernÃ¡n Morales Durand escribiÃ³: >> A XML parser just creates a representation of a XML document according >> to a parsing model. Ideally you should choose a XML parser >> specifically for your needs. You have different parsing models: >> >> -Tree Parser: This is what you will read everywhere as the "DOM parser" >> -Event Parser: This is denoted by S*X and could be >> --SAX Parser: Known as the "Push parser" >> --StAX Parser: Known also too as the "Pull parser" >> -VTD Parser : This is known as "Virtual Token Descriptor" >> >> Now there are several classifications depending of the parser >> characteristics and what you want to do or how. You may be interested >> in: >> >> Making modifications or just processing? >> -For modifications: The parser creates long-lived representations from >> the XML document (necessary for modifications): You should choose DOM >> or VTD >> --Do you *need* to query or modify the objects (parser creates nodes): DOM >> --You do not need the objects (parser creates integers and locations >> caches): VTD >> -For processing: The parser doesn't creates long-lived objects: SAX or StAX. >> >> Type of Access >> -Back-and-forth: Access the data after the parsing is complete: DOM or VTD >> --Massive or very frequent access: Choose DOM >> --Rare or simple access: Choose VTD >> -Sequential: Access the data while you're processing the document: SAX or StAX >> --Processing all tokens: SAX >> --Processing interested tokens (allows skipping forward): StAX >> >> Briefly >> -Streaming applications (very large documents): SAX or StAX >> -Database applications: DOM or VTD >> -Hardware acceleration?: VTD >> >> For the S*X parsers you need to know the XML token types because, for >> example in the case of XMLParser in Pharo/Squeak, you probably would >> subclass SAXHandler and override one or several methods in the content >> category to do your own processing. See GTNCBIBlastParser in >> http://www.squeaksource.com/GenomeTools.html for an example of a SAX >> Parser. >> >> XML token types: >> Start element: <Hit>.... >> End element: ...</Hit> >> Text: <...>Text value</...> >> etc. >> >> For DOM usage examples you may see >> http://community.ofset.org/index.php/Les_bases_de_XML_dans_Squeak (it >> is in french but is a good document) >> >> What we have in Pharo/Squeak >> >> Parsers: >> 1) XMLParser : Supports SAX and DOM. http://www.squeaksource.com/XMLSupport.html >> 2) VWXML Parser : Supports SAX and DOM (AFAIK) >> http://www.squeaksource.com/VWXML.html >> 3) XMLPullParser : Supports StAX. http://www.squeaksource.com/XMLPullParser.html >> >> XML Query tools >> 1) Pastell : Supports X-Path like queries. Requires XMLParser. >> http://www.squeaksource.com/Pastell.html >> 2) XPath library : Supports XPath partially. Requires XMLParser. >> http://www.squeaksource.com/XPath.html >> >> There are several additional tools in SqueakSource but I haven't reviewed yet. >> A VTD parser would be ideal for Smalltalk because it uses integer >> arrays reducing the object allocation overhead in memory. I haven't >> found implementations of a XML VTD parser in Smalltalk as of today. >> Cheers, >> >> HernÃ¡n >> >> 2010/7/20 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >>> could the people with a bit of knowledge try to write a map of all the possible and working solutions? >>> >>> People are telling me that python doc is good so may be we should also consider that arranging knowledge >>> on maps is the first step >>> >>> Please take 15 mins because in 15 min you can get a real impact! >>> >>> >>>> http://www.squeaksource.com/XMLPullParser.html >>>> >>>> If I would going to write a XML parser, I'd go for a VTD parser instead. >>>> Cheers, >>>> >>>> HernÃ¡n >>>> >>>> 2010/7/19 Norbert Hartl <norbert(a)hartl.name>: >>>>> >>>>> On 06.07.2010, at 23:04, jaayer wrote: >>>>> >>>>>> >>>>>> >>>>>> ---- 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(a)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: >>>>>> <?xml version="1.0" encoding="UTF-8"?> >>>>>> <foo xmlns:foo="http://foo" a="one" b="two"> >>>>>> <bar>test<baz /> >>>>>> <foobar>test</foobar> >>>>>> </bar> >>>>>> </foo> >>>>>> >>>>> Could you elaborate on the usage of xmlns? The one you defined does nothing. The foo in the xml is just the element name. I would like to know >>>>> >>>>> - how to define a namespace prefix for an element >>>>> - how to define a default namespace for an element >>>>> >>>>> I think I need another look in the xml parser since last time :) Thanks for putting effort into xml parser. Is there a pull parser available or planned? >>>>> >>>>> thanks, >>>>> >>>>> Norbert >>>>> >>>>> >>>>> _______________________________________________ >>>>> Pharo-project mailing list >>>>> Pharo-project(a)lists.gforge.inria.fr >>>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 20, 2010

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

by StÃ©phane Ducasse

We need more of these :) http://book.pharo-project.org/book/XML Thanks a lot hernan On Jul 20, 2010, at 7:11 PM, HernÃ¡n Morales Durand wrote: > A XML parser just creates a representation of a XML document according > to a parsing model. Ideally you should choose a XML parser > specifically for your needs. You have different parsing models: > > -Tree Parser: This is what you will read everywhere as the "DOM parser" > -Event Parser: This is denoted by S*X and could be > --SAX Parser: Known as the "Push parser" > --StAX Parser: Known also too as the "Pull parser" > -VTD Parser : This is known as "Virtual Token Descriptor" > > Now there are several classifications depending of the parser > characteristics and what you want to do or how. You may be interested > in: > > Making modifications or just processing? > -For modifications: The parser creates long-lived representations from > the XML document (necessary for modifications): You should choose DOM > or VTD > --Do you *need* to query or modify the objects (parser creates nodes): DOM > --You do not need the objects (parser creates integers and locations > caches): VTD > -For processing: The parser doesn't creates long-lived objects: SAX or StAX. > > Type of Access > -Back-and-forth: Access the data after the parsing is complete: DOM or VTD > --Massive or very frequent access: Choose DOM > --Rare or simple access: Choose VTD > -Sequential: Access the data while you're processing the document: SAX or StAX > --Processing all tokens: SAX > --Processing interested tokens (allows skipping forward): StAX > > Briefly > -Streaming applications (very large documents): SAX or StAX > -Database applications: DOM or VTD > -Hardware acceleration?: VTD > > For the S*X parsers you need to know the XML token types because, for > example in the case of XMLParser in Pharo/Squeak, you probably would > subclass SAXHandler and override one or several methods in the content > category to do your own processing. See GTNCBIBlastParser in > http://www.squeaksource.com/GenomeTools.html for an example of a SAX > Parser. > > XML token types: > Start element: <Hit>.... > End element: ...</Hit> > Text: <...>Text value</...> > etc. > > For DOM usage examples you may see > http://community.ofset.org/index.php/Les_bases_de_XML_dans_Squeak (it > is in french but is a good document) > > What we have in Pharo/Squeak > > Parsers: > 1) XMLParser : Supports SAX and DOM. http://www.squeaksource.com/XMLSupport.html > 2) VWXML Parser : Supports SAX and DOM (AFAIK) > http://www.squeaksource.com/VWXML.html > 3) XMLPullParser : Supports StAX. http://www.squeaksource.com/XMLPullParser.html > > XML Query tools > 1) Pastell : Supports X-Path like queries. Requires XMLParser. > http://www.squeaksource.com/Pastell.html > 2) XPath library : Supports XPath partially. Requires XMLParser. > http://www.squeaksource.com/XPath.html > > There are several additional tools in SqueakSource but I haven't reviewed yet. > A VTD parser would be ideal for Smalltalk because it uses integer > arrays reducing the object allocation overhead in memory. I haven't > found implementations of a XML VTD parser in Smalltalk as of today. > Cheers, > > HernÃ¡n > > 2010/7/20 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: >> could the people with a bit of knowledge try to write a map of all the possible and working solutions? >> >> People are telling me that python doc is good so may be we should also consider that arranging knowledge >> on maps is the first step >> >> Please take 15 mins because in 15 min you can get a real impact! >> >> >>> http://www.squeaksource.com/XMLPullParser.html >>> >>> If I would going to write a XML parser, I'd go for a VTD parser instead. >>> Cheers, >>> >>> HernÃ¡n >>> >>> 2010/7/19 Norbert Hartl <norbert(a)hartl.name>: >>>> >>>> On 06.07.2010, at 23:04, jaayer wrote: >>>> >>>>> >>>>> >>>>> ---- 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(a)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: >>>>> <?xml version="1.0" encoding="UTF-8"?> >>>>> <foo xmlns:foo="http://foo" a="one" b="two"> >>>>> <bar>test<baz /> >>>>> <foobar>test</foobar> >>>>> </bar> >>>>> </foo> >>>>> >>>> Could you elaborate on the usage of xmlns? The one you defined does nothing. The foo in the xml is just the element name. I would like to know >>>> >>>> - how to define a namespace prefix for an element >>>> - how to define a default namespace for an element >>>> >>>> I think I need another look in the xml parser since last time :) Thanks for putting effort into xml parser. Is there a pull parser available or planned? >>>> >>>> thanks, >>>> >>>> Norbert >>>> >>>> >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 20, 2010

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

by Miguel Enrique CobÃ¡ MartÃnez

This good summary should go directly to the collaboractive book. El mar, 20-07-2010 a las 14:11 -0300, HernÃ¡n Morales Durand escribiÃ³: > A XML parser just creates a representation of a XML document according > to a parsing model. Ideally you should choose a XML parser > specifically for your needs. You have different parsing models: > > -Tree Parser: This is what you will read everywhere as the "DOM parser" > -Event Parser: This is denoted by S*X and could be > --SAX Parser: Known as the "Push parser" > --StAX Parser: Known also too as the "Pull parser" > -VTD Parser : This is known as "Virtual Token Descriptor" > > Now there are several classifications depending of the parser > characteristics and what you want to do or how. You may be interested > in: > > Making modifications or just processing? > -For modifications: The parser creates long-lived representations from > the XML document (necessary for modifications): You should choose DOM > or VTD > --Do you *need* to query or modify the objects (parser creates nodes): DOM > --You do not need the objects (parser creates integers and locations > caches): VTD > -For processing: The parser doesn't creates long-lived objects: SAX or StAX. > > Type of Access > -Back-and-forth: Access the data after the parsing is complete: DOM or VTD > --Massive or very frequent access: Choose DOM > --Rare or simple access: Choose VTD > -Sequential: Access the data while you're processing the document: SAX or StAX > --Processing all tokens: SAX > --Processing interested tokens (allows skipping forward): StAX > > Briefly > -Streaming applications (very large documents): SAX or StAX > -Database applications: DOM or VTD > -Hardware acceleration?: VTD > > For the S*X parsers you need to know the XML token types because, for > example in the case of XMLParser in Pharo/Squeak, you probably would > subclass SAXHandler and override one or several methods in the content > category to do your own processing. See GTNCBIBlastParser in > http://www.squeaksource.com/GenomeTools.html for an example of a SAX > Parser. > > XML token types: > Start element: <Hit>.... > End element: ...</Hit> > Text: <...>Text value</...> > etc. > > For DOM usage examples you may see > http://community.ofset.org/index.php/Les_bases_de_XML_dans_Squeak (it > is in french but is a good document) > > What we have in Pharo/Squeak > > Parsers: > 1) XMLParser : Supports SAX and DOM. http://www.squeaksource.com/XMLSupport.html > 2) VWXML Parser : Supports SAX and DOM (AFAIK) > http://www.squeaksource.com/VWXML.html > 3) XMLPullParser : Supports StAX. http://www.squeaksource.com/XMLPullParser.html > > XML Query tools > 1) Pastell : Supports X-Path like queries. Requires XMLParser. > http://www.squeaksource.com/Pastell.html > 2) XPath library : Supports XPath partially. Requires XMLParser. > http://www.squeaksource.com/XPath.html > > There are several additional tools in SqueakSource but I haven't reviewed yet. > A VTD parser would be ideal for Smalltalk because it uses integer > arrays reducing the object allocation overhead in memory. I haven't > found implementations of a XML VTD parser in Smalltalk as of today. > Cheers, > > HernÃ¡n > > 2010/7/20 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > > could the people with a bit of knowledge try to write a map of all the possible and working solutions? > > > > People are telling me that python doc is good so may be we should also consider that arranging knowledge > > on maps is the first step > > > > Please take 15 mins because in 15 min you can get a real impact! > > > > > >> http://www.squeaksource.com/XMLPullParser.html > >> > >> If I would going to write a XML parser, I'd go for a VTD parser instead. > >> Cheers, > >> > >> HernÃ¡n > >> > >> 2010/7/19 Norbert Hartl <norbert(a)hartl.name>: > >>> > >>> On 06.07.2010, at 23:04, jaayer wrote: > >>> > >>>> > >>>> > >>>> ---- 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(a)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: > >>>> <?xml version="1.0" encoding="UTF-8"?> > >>>> <foo xmlns:foo="http://foo" a="one" b="two"> > >>>> <bar>test<baz /> > >>>> <foobar>test</foobar> > >>>> </bar> > >>>> </foo> > >>>> > >>> Could you elaborate on the usage of xmlns? The one you defined does nothing. The foo in the xml is just the element name. I would like to know > >>> > >>> - how to define a namespace prefix for an element > >>> - how to define a default namespace for an element > >>> > >>> I think I need another look in the xml parser since last time :) Thanks for putting effort into xml parser. Is there a pull parser available or planned? > >>> > >>> thanks, > >>> > >>> Norbert > >>> > >>> > >>> _______________________________________________ > >>> Pharo-project mailing list > >>> Pharo-project(a)lists.gforge.inria.fr > >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >>> > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Miguel CobÃ¡ http://miguel.leugim.com.mx

July 20, 2010

Re: [Pharo-project] Pharo-project Digest, Vol 27, Issue 118

by Larry Gadallah

On 19 July 2010 12:16, <pharo-project-request(a)lists.gforge.inria.fr> wrote: > Message: 6 > Date: Mon, 19 Jul 2010 21:15:54 +0200 > From: Norbert Hartl <norbert(a)hartl.name> > Subject: Re: [Pharo-project] XML Demarshalling > To: Pharo-project(a)lists.gforge.inria.fr > Message-ID: <6BCBFCA9-367D-4848-8D4C-9EA724017B99(a)hartl.name> > Content-Type: text/plain; charset=us-ascii > > > On 16.07.2010, at 18:46, Larry Gadallah wrote: > >> Hi all: >> >> I am a noob searching for an example of how to demarshall a set of >> simple and complex XML nodes into an object using Pastell or something >> similar. I have found many examples of how to pick out all of the >> elements of a certain type into a collection, but I'm trying to grab >> the data from a mixed collection of (~20) elements that are children >> of a particular element type and unpack them into an object. >> >> Does anyone know of some good examples of how to do this using Pastell >> or something similar? >> > Can you give more detailled information about how the XML maps onto the data model? I mean if you have childr elements will that map to objects that are referenced similar? Do attributes map to variables and such? Or do you want to freely define how the structure of the XML resembles into your objects? > > Norbert Hi Norbert: Alas, I am laboring under the burden of being a newbie to both Pharo and XML. It seems to me that it would be better to be able to dynamically pick up all of the child elements of an element of interest, however, I can't imagine how to define an object that doesn't know it's own contents until run-time. In addition, in my case, some of the child elements are complex (i.e. they also contain children) which complicates the traversal a little bit. I'm assuming for now that I will have to read the source XML, define the instance variables of my object based on them, and simply populate them at run time by traversing the XML tree. If the XML model changes, the object definition will have to change too. Thanks, -- Larry Gadallah, VE6VQ/W7Â Â Â Â Â Â Â Â Â Â Â Â Â lgadallah AT gmail DOT com PGP Sig: 917E DDB7 C911 9EC1 0CD9Â C06B 06C4 835F 0BB8 7336

July 20, 2010

Re: [Pharo-project] about hex

by Levente Uzonyi

On Tue, 20 Jul 2010, Yanni Chiu wrote: > Originally, the NATIVE postgresql driver was (somewhat?) ANSI ST > incompatible. I had it working in VAST. Along the way, the Cryptography > package was added as a dependency to support MD5 passwords. > > If #hex is not ANSI ST, then the postgres native driver is likely unaffected > by changes to #hex, other than its effect on MD5. I can verify this later > today. It's a totally different #hex. The original issue is about Integer >> #hex. PostgresV2 uses ByteArray >> #hex which is in the Cryptography package and is independent of Integer >> #hex. Levente > > -- > Yanni > > > Mariano Martinez Peck wrote: >> >> >> On Tue, Jul 20, 2010 at 2:46 AM, Henrik Johansen >> <henrik.s.johansen(a)veloxit.no <mailto:henrik.s.johansen@veloxit.no>> wrote: >> >> Iirc, it was reintroduced in Pharo in relation to SqueakDBX, might >> want to check with Mariano that changes will be compatible/SqueakDBX >> is updated. >> >> >> Hi Henrik. Indeed, it was included for SqueakDBX. Actually, not for itself, >> but the NATIVE postgresql driver used to depends in the chripto package. >> Then, the MD5 class was put in PharoCore so it didn't depend anymore. But >> the hex was missing. >> Now...if you ask me if this change will affect the postgres native driver, >> I HAVE NO IDEA. The only thing I can do is to run the tests. But for that I >> need a postgres with encrypthion running handly. >> >> Do you know Yanni? >> >> Cheers >> >> Mariano > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 20, 2010

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

by HernÃ¡n Morales Durand

A XML parser just creates a representation of a XML document according to a parsing model. Ideally you should choose a XML parser specifically for your needs. You have different parsing models: -Tree Parser: This is what you will read everywhere as the "DOM parser" -Event Parser: This is denoted by S*X and could be --SAX Parser: Known as the "Push parser" --StAX Parser: Known also too as the "Pull parser" -VTD Parser : This is known as "Virtual Token Descriptor" Now there are several classifications depending of the parser characteristics and what you want to do or how. You may be interested in: Making modifications or just processing? -For modifications: The parser creates long-lived representations from the XML document (necessary for modifications): You should choose DOM or VTD --Do you *need* to query or modify the objects (parser creates nodes): DOM --You do not need the objects (parser creates integers and locations caches): VTD -For processing: The parser doesn't creates long-lived objects: SAX or StAX. Type of Access -Back-and-forth: Access the data after the parsing is complete: DOM or VTD --Massive or very frequent access: Choose DOM --Rare or simple access: Choose VTD -Sequential: Access the data while you're processing the document: SAX or StAX --Processing all tokens: SAX --Processing interested tokens (allows skipping forward): StAX Briefly -Streaming applications (very large documents): SAX or StAX -Database applications: DOM or VTD -Hardware acceleration?: VTD For the S*X parsers you need to know the XML token types because, for example in the case of XMLParser in Pharo/Squeak, you probably would subclass SAXHandler and override one or several methods in the content category to do your own processing. See GTNCBIBlastParser in http://www.squeaksource.com/GenomeTools.html for an example of a SAX Parser. XML token types: Start element: <Hit>.... End element: ...</Hit> Text: <...>Text value</...> etc. For DOM usage examples you may see http://community.ofset.org/index.php/Les_bases_de_XML_dans_Squeak (it is in french but is a good document) What we have in Pharo/Squeak Parsers: 1) XMLParser : Supports SAX and DOM. http://www.squeaksource.com/XMLSupport.html 2) VWXML Parser : Supports SAX and DOM (AFAIK) http://www.squeaksource.com/VWXML.html 3) XMLPullParser : Supports StAX. http://www.squeaksource.com/XMLPullParser.html XML Query tools 1) Pastell : Supports X-Path like queries. Requires XMLParser. http://www.squeaksource.com/Pastell.html 2) XPath library : Supports XPath partially. Requires XMLParser. http://www.squeaksource.com/XPath.html There are several additional tools in SqueakSource but I haven't reviewed yet. A VTD parser would be ideal for Smalltalk because it uses integer arrays reducing the object allocation overhead in memory. I haven't found implementations of a XML VTD parser in Smalltalk as of today. Cheers, HernÃ¡n 2010/7/20 StÃ©phane Ducasse <stephane.ducasse(a)inria.fr>: > could the people with a bit of knowledge try to write a map of all the possible and working solutions? > > People are telling me that python doc is good so may be we should also consider that arranging knowledge > on maps is the first step > > Please take 15 mins because in 15 min you can get a real impact! > > >> http://www.squeaksource.com/XMLPullParser.html >> >> If I would going to write a XML parser, I'd go for a VTD parser instead. >> Cheers, >> >> HernÃ¡n >> >> 2010/7/19 Norbert Hartl <norbert(a)hartl.name>: >>> >>> On 06.07.2010, at 23:04, jaayer wrote: >>> >>>> >>>> >>>> ---- 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(a)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: >>>> <?xml version="1.0" encoding="UTF-8"?> >>>> <foo xmlns:foo="http://foo" a="one" b="two"> >>>> Â Â <bar>test<baz /> >>>> Â Â Â Â <foobar>test</foobar> >>>> Â Â </bar> >>>> </foo> >>>> >>> Could you elaborate on the usage of xmlns? The one you defined does nothing. The foo in the xml is just the element name. I would like to know >>> >>> - how to define a namespace prefix for an element >>> - how to define a default namespace for an element >>> >>> I think I need another look in the xml parser since last time :) Thanks for putting effort into xml parser. Is there a pull parser available or planned? >>> >>> thanks, >>> >>> Norbert >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 20, 2010

Re: [Pharo-project] [ANN] ConfigurationOfMagma for Magma 1.1r1

by Dale Henrichs

First, if you are creating configuration for a project and you have different code that needs to be loaded depending upon the version of Pharo into which it is loaded, then you can add attiributes like #'Pharo1.1' or #'Pharo1.0' to control which packages get loaded into the image. This is a case where the maintainer _is_ involved in updating the application to ensure that it runs on both Pharo1.0 and Pharo1.1 or Pharo1.x. Secondly, not all maintainer can ensure that their project runs on Pharo1.0 and Pharo1.1, etc.. So there is a separate problem of identifying the versions of a project that are _known_ to work in Pharo1.0 or Pharo1.1. When a new Pharo1.x arrives, many projects may not work, but over time, more and more of the projects get ported to Pharo1.x so determining a means to communicate to users which projects are known to work is important. I would say that we haven't completely settled the second issue. As Miguel mentioned, I think it is clear that the following will be part of the process - Copy repositories of configurations (+mcz files) for each new release - Use version attributes for conditionally loading packages in version methods. I think that we're still up in the air (I know that I am) as to the best method for controlling the actual load. Ideally, the solution would not involve editing configurations (tags). Technically, once you copied the configs/mcz files that are known to work to a Pharo1.0 repository, all you need to do is use #repositoryOverrides: to force the load to be done from the Pharo1.0 repository, but we want something that is very simple and doesn't require an extra step and we're still discussing this. Dale Andreas Wacknitz wrote: > Am 20.07.10 16:42, schrieb Miguel Enrique CobÃ¡ MartÃnez: >> El mar, 20-07-2010 a las 10:17 +0200, Mariano Martinez Peck escribiÃÂ³: >>> Hi Miguel. I understand your problem, and we are working on that with >>> Dale and Stef. Having repositories for a specific Pharo version and so >>> on. But we are just starting.... >>> >>> By the moment, you can use what Sean told you, or, just update the >>> configuration, but in a new version. I mean....if you had the version >>> 2.3.4 that was released and working in pharo 1.0, then don't touch it, >>> create a new one, say, 2.4 and that works in 1.1. Of course this is >>> not the perfect solution, but for the moment. But one thing for sure: >>> do not update the SAME version that was working for 1.0. >>> Magma should continue working in 1.0 using the same metacello version. >> Exactly. I will do it this night. >> >> BTW. What will be the solution, copying directories (debian does this >> too. They copy the repository contents and then diverge from them. The >> previous repository only receives bug fixes) but the solution of Dale, >> as I understand it uses tags to identify what version is running on and >> then load only the packages for that version. This solution is a third >> alternative. So by now we have: >> >> - Copy repositories of configurations for each new release >> - Use version attributes for conditionally loading packages in version >> methods. >> - Use tags to mark the pharo release a given version method applies. >> Then metacello searches for the version method with the highest number >> that is tagged with the release number of the image (got from >> SystemVersion) >> >> Cheers > Hi, > > Wouldn't it be good to also ask the maintainer of the offending packages > to change the assignments such that Pharo will be happy without changing > the preference? > > Regards, > Andreas > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 20, 2010

Re: [Pharo-project] Bug with Windows titles not refreshing (in OB)

by Lukas Renggli

I am not sure if this is a bug. I think this is intentionally implemented like this. Lukas 2010/7/20 Mariano Martinez Peck <marianopeck(a)gmail.com>: > Hi, there is a bug with windows titles as they don't refresh and keeps a > previous title. > > Steps to reproduce: > > 1) Search senders of a particular message, for example, doesNotUnderstand: > 2) You will see that the opened windows for senders, has the title "Senders > of '#doesNotUnderstand:" > 3) Now, select one of the senders, for example, ContextPart >> send: > selector to: rcvr with: args super: superFlag > 4) That will open the senders of that message, BUT the windows title still > says "Senders of '#doesNotUnderstand:" Â instead ofÂ "Senders of > '#send:to:with:super:" > > Issue: http://code.google.com/p/pharo/issues/detail?id=2707 > > Cheers > > Mariano > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli www.lukas-renggli.ch

July 20, 2010

Re: [Pharo-project] [ANN 1.1] pre-built 1.1 Release #11411 Core

by Lukas Renggli

I only keep per project the artifacts of the last 10 builds + some manually marked builds (releases). The disk usage stabilized around 3 GB. Lukas On 20 July 2010 18:22, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr> wrote: > apparently ours kills our server :) > the disc got filled up :) > > Stef > > On Jul 20, 2010, at 3:52 PM, Lukas Renggli wrote: > >> Thank you Marcus, my hudson is rebuilding the whole shebang now. >> >> Lukas >> >> On 20 July 2010 15:48, Marcus Denker <marcus.denker(a)inria.fr> wrote: >>> >>> Â Â Â Â https://gforge.inria.fr/frs/download.php/27296/PharoCore-1.1.zip >>> >>> -- >>> Marcus Denker Â -- http://www.marcusdenker.de >>> INRIA Lille -- Nord Europe. Team RMoD. >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)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(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli www.lukas-renggli.ch

July 20, 2010

Re: [Pharo-project] [ANN] ConfigurationOfMagma for Magma 1.1r1

by Miguel Enrique CobÃ¡ MartÃnez

El mar, 20-07-2010 a las 18:33 +0200, Andreas Wacknitz escribiÃ³: > Am 20.07.10 16:42, schrieb Miguel Enrique CobÃ¡ MartÃnez: > > El mar, 20-07-2010 a las 10:17 +0200, Mariano Martinez Peck escribiÃÂ³: > >> Hi Miguel. I understand your problem, and we are working on that with > >> Dale and Stef. Having repositories for a specific Pharo version and so > >> on. But we are just starting.... > >> > >> By the moment, you can use what Sean told you, or, just update the > >> configuration, but in a new version. I mean....if you had the version > >> 2.3.4 that was released and working in pharo 1.0, then don't touch it, > >> create a new one, say, 2.4 and that works in 1.1. Of course this is > >> not the perfect solution, but for the moment. But one thing for sure: > >> do not update the SAME version that was working for 1.0. > >> Magma should continue working in 1.0 using the same metacello version. > > > > Exactly. I will do it this night. > > > > BTW. What will be the solution, copying directories (debian does this > > too. They copy the repository contents and then diverge from them. The > > previous repository only receives bug fixes) but the solution of Dale, > > as I understand it uses tags to identify what version is running on and > > then load only the packages for that version. This solution is a third > > alternative. So by now we have: > > > > - Copy repositories of configurations for each new release > > - Use version attributes for conditionally loading packages in version > > methods. > > - Use tags to mark the pharo release a given version method applies. > > Then metacello searches for the version method with the highest number > > that is tagged with the release number of the image (got from > > SystemVersion) > > > > Cheers > Hi, > > Wouldn't it be good to also ask the maintainer of the offending packages > to change the assignments such that Pharo will be happy without changing > the preference? Chris Muller announced some time ago that he was changing the underscores to := assignments in them Magma codebase. He had concerns about the scripts for automating this because it changed the author timestamps of each method modified and he didn't want to lost those original timestamps. So until he publishes the new code without underscores, we must use the preference when loading the code. Cheers > > Regards, > Andreas > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Miguel CobÃ¡ http://miguel.leugim.com.mx

July 20, 2010

Re: [Pharo-project] [ANN] ConfigurationOfMagma for Magma 1.1r1

by Andreas Wacknitz

Am 20.07.10 16:42, schrieb Miguel Enrique CobÃ¡ MartÃnez: > El mar, 20-07-2010 a las 10:17 +0200, Mariano Martinez Peck escribiÃÂ³: >> Hi Miguel. I understand your problem, and we are working on that with >> Dale and Stef. Having repositories for a specific Pharo version and so >> on. But we are just starting.... >> >> By the moment, you can use what Sean told you, or, just update the >> configuration, but in a new version. I mean....if you had the version >> 2.3.4 that was released and working in pharo 1.0, then don't touch it, >> create a new one, say, 2.4 and that works in 1.1. Of course this is >> not the perfect solution, but for the moment. But one thing for sure: >> do not update the SAME version that was working for 1.0. >> Magma should continue working in 1.0 using the same metacello version. > > Exactly. I will do it this night. > > BTW. What will be the solution, copying directories (debian does this > too. They copy the repository contents and then diverge from them. The > previous repository only receives bug fixes) but the solution of Dale, > as I understand it uses tags to identify what version is running on and > then load only the packages for that version. This solution is a third > alternative. So by now we have: > > - Copy repositories of configurations for each new release > - Use version attributes for conditionally loading packages in version > methods. > - Use tags to mark the pharo release a given version method applies. > Then metacello searches for the version method with the highest number > that is tagged with the release number of the image (got from > SystemVersion) > > Cheers Hi, Wouldn't it be good to also ask the maintainer of the offending packages to change the assignments such that Pharo will be happy without changing the preference? Regards, Andreas

July 20, 2010

Re: [Pharo-project] about hex

by StÃ©phane Ducasse

tx! I was thinking that we could keep old hex as hexDigits Stef On Jul 20, 2010, at 4:42 PM, Yanni Chiu wrote: > Originally, the NATIVE postgresql driver was (somewhat?) ANSI ST incompatible. I had it working in VAST. Along the way, the Cryptography package was added as a dependency to support MD5 passwords. > > If #hex is not ANSI ST, then the postgres native driver is likely unaffected by changes to #hex, other than its effect on MD5. I can verify this later today. > > -- > Yanni > > > Mariano Martinez Peck wrote: >> On Tue, Jul 20, 2010 at 2:46 AM, Henrik Johansen <henrik.s.johansen(a)veloxit.no <mailto:henrik.s.johansen@veloxit.no>> wrote: >> Iirc, it was reintroduced in Pharo in relation to SqueakDBX, might >> want to check with Mariano that changes will be compatible/SqueakDBX >> is updated. >> Hi Henrik. Indeed, it was included for SqueakDBX. Actually, not for itself, but the NATIVE postgresql driver used to depends in the chripto package. Then, the MD5 class was put in PharoCore so it didn't depend anymore. But the hex was missing. >> Now...if you ask me if this change will affect the postgres native driver, I HAVE NO IDEA. The only thing I can do is to run the tests. But for that I need a postgres with encrypthion running handly. >> Do you know Yanni? >> Cheers >> Mariano > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 20, 2010

Re: [Pharo-project] [ANN 1.1] pre-built 1.1 Release #11411 Core

by StÃ©phane Ducasse

apparently ours kills our server :) the disc got filled up :) Stef On Jul 20, 2010, at 3:52 PM, Lukas Renggli wrote: > Thank you Marcus, my hudson is rebuilding the whole shebang now. > > Lukas > > On 20 July 2010 15:48, Marcus Denker <marcus.denker(a)inria.fr> wrote: >> >> https://gforge.inria.fr/frs/download.php/27296/PharoCore-1.1.zip >> >> -- >> Marcus Denker -- http://www.marcusdenker.de >> INRIA Lille -- Nord Europe. Team RMoD. >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)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(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 20, 2010

Re: [Pharo-project] Can TestRunner notify failures and errors while they happen?

by StÃ©phane Ducasse

the idea is that adrian proposed to have a testcase acting as an announcer and the testRunner listening So I would start there. On Jul 20, 2010, at 3:15 PM, Mariano Martinez Peck wrote: > Hi folks. One of my tasks while creating the dev images is to run all the tests and analyze the errors and failures. TestRunner list the results (failures and errors) at the end. I would like it to update show and update the TestRunner UI. Why ? Because if it shows me the errors and failures while they happen, I can take the same image, open it again, and start to analyze them. And I don't have to wait until de endâ¦ > > Can someone help me with this? what do you think ? > > Thanks > > Mariano > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 20, 2010

[Pharo-project] Squeak devices and applications

by Torsten Bergmann

Just read the post from Hilaire about Pharo on OLPC [1]. This leads to the following interesting question: What is the most crazy device Squeak VM is running on? What is the most interesting application where nobody would have expected Squeak/Pharo/Cuis? Feel free to answer by posting screenshots/pictures even if you think the device/app is boring. Would be nice to know and we can collect these to do a little bit of advertising on the Squeak/Pharo web pages... Bye T. [1] http://blog.ofset.org/hilaire/index.php?post/2010/07/20/Pharo-Smalltalk-on-… -- Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail

July 20, 2010

Re: [Pharo-project] How to see failures/erros of the Hudson server?

by Mariano Martinez Peck

this is cool :) thank you very much mariano On Tue, Jul 20, 2010 at 3:49 PM, Lukas Renggli <renggli(a)gmail.com> wrote: > As Nick points out. Additionally, the image with the tests is saves so > you can download and run it. > > Lukas > > 2010/7/20 Nick Ager <nick.ager(a)gmail.com>: > > Failing tests: > > http://hudson.lukas-renggli.ch/job/Pharo/lastCompletedBuild/testReport/ > > > http://hudson.lukas-renggli.ch/job/Pharo/lastCompletedBuild/testReport/Test… > > log: > > http://hudson.lukas-renggli.ch/job/Pier/64/console > > > > 2010/7/20 Mariano Martinez Peck <marianopeck(a)gmail.com> > >> > >> I know we have just started with the Hudson server, but is there a way > to > >> see why a test is failing/error ? For the errors, at least we can see > the > >> PharoDebug.log ? > >> THe other idea we have today (talking with Marcus) is to have RFB > running > >> in the hudson images. So that we can connect and browse it. Of course, > it > >> could be password protected so that not everybody can do it. > >> > >> What do you think? > >> > >> Cheers > >> > >> Mariano > >> > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)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(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 20, 2010

[Pharo-project] Bug with Windows titles not refreshing (in OB)

by Mariano Martinez Peck

Hi, there is a bug with windows titles as they don't refresh and keeps a previous title. Steps to reproduce: 1) Search senders of a particular message, for example, doesNotUnderstand: 2) You will see that the opened windows for senders, has the title "Senders of '#doesNotUnderstand:" 3) Now, select one of the senders, for example, ContextPart >> send: selector to: rcvr with: args super: superFlag 4) That will open the senders of that message, BUT the windows title still says "Senders of '#doesNotUnderstand:" instead of "Senders of '#send:to:with:super:" Issue: http://code.google.com/p/pharo/issues/detail?id=2707 Cheers Mariano

July 20, 2010

Re: [Pharo-project] about hex

by Yanni Chiu

Originally, the NATIVE postgresql driver was (somewhat?) ANSI ST incompatible. I had it working in VAST. Along the way, the Cryptography package was added as a dependency to support MD5 passwords. If #hex is not ANSI ST, then the postgres native driver is likely unaffected by changes to #hex, other than its effect on MD5. I can verify this later today. -- Yanni Mariano Martinez Peck wrote: > > > On Tue, Jul 20, 2010 at 2:46 AM, Henrik Johansen > <henrik.s.johansen(a)veloxit.no <mailto:henrik.s.johansen@veloxit.no>> wrote: > > Iirc, it was reintroduced in Pharo in relation to SqueakDBX, might > want to check with Mariano that changes will be compatible/SqueakDBX > is updated. > > > Hi Henrik. Indeed, it was included for SqueakDBX. Actually, not for > itself, but the NATIVE postgresql driver used to depends in the chripto > package. Then, the MD5 class was put in PharoCore so it didn't depend > anymore. But the hex was missing. > Now...if you ask me if this change will affect the postgres native > driver, I HAVE NO IDEA. The only thing I can do is to run the tests. But > for that I need a postgres with encrypthion running handly. > > Do you know Yanni? > > Cheers > > Mariano

July 20, 2010

Re: [Pharo-project] [ANN] ConfigurationOfMagma for Magma 1.1r1

by Miguel Enrique CobÃ¡ MartÃnez

El mar, 20-07-2010 a las 10:17 +0200, Mariano Martinez Peck escribiÃ³: > Hi Miguel. I understand your problem, and we are working on that with > Dale and Stef. Having repositories for a specific Pharo version and so > on. But we are just starting.... > > By the moment, you can use what Sean told you, or, just update the > configuration, but in a new version. I mean....if you had the version > 2.3.4 that was released and working in pharo 1.0, then don't touch it, > create a new one, say, 2.4 and that works in 1.1. Of course this is > not the perfect solution, but for the moment. But one thing for sure: > do not update the SAME version that was working for 1.0. > Magma should continue working in 1.0 using the same metacello version. Exactly. I will do it this night. BTW. What will be the solution, copying directories (debian does this too. They copy the repository contents and then diverge from them. The previous repository only receives bug fixes) but the solution of Dale, as I understand it uses tags to identify what version is running on and then load only the packages for that version. This solution is a third alternative. So by now we have: - Copy repositories of configurations for each new release - Use version attributes for conditionally loading packages in version methods. - Use tags to mark the pharo release a given version method applies. Then metacello searches for the version method with the highest number that is tagged with the release number of the image (got from SystemVersion) Cheers > > cheers > > mariano > > On Tue, Jul 20, 2010 at 9:26 AM, Sean P. DeNigris > <sean(a)clipperadams.com> wrote: > > For now, you can use the hack that Dale suggested in > http://groups.google.com/group/metacello/browse_thread/thread/a27c95d24974a…. > > > Take a look a ConfigurationOfGemTools>>project. In that > method I created a > > #'pharo1.0Beta' attribute by looking at the SystemVersion > current > > version... > -- > View this message in context: > http://forum.world.st/ANN-ConfigurationOfMagma-for-Magma-1-1r1-tp2242566p22… > Sent from the Pharo Smalltalk mailing list archive at > Nabble.com. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- Miguel CobÃ¡ http://miguel.leugim.com.mx

July 20, 2010

Re: [Pharo-project] [ANN] ConfigurationOfMagma for Magma 1.1r1

by Miguel Enrique CobÃ¡ MartÃnez

El mar, 20-07-2010 a las 08:29 +0200, Torsten Bergmann escribiÃ³: > Hi Mariano, > > why dont you add: > > (Scanner class includesSelector: #allowUnderscoreAsAssignment:) > ifTrue: [Scanner allowUnderscoreAsAssignment: true] Yes, in fact the correct one is through the Preferences or Setting classes. Yesterday was late and I had little time for do it correctly, only reverted it to the previous version. But this is just for this case. We *need* to make a decision for how this will work. There are packages that will be more and more affected by changes between releases and a single method with lots of conditionals will reach the C preprocesor nightmare we now :) This night I will make the changes so that ConfigurationOfMagma work in 1.0, 1.1 and 1.2 Cheers > > > to the #preLoadForPharo ? > > Bye > T. -- Miguel CobÃ¡ http://miguel.leugim.com.mx

July 20, 2010

Re: [Pharo-project] [ANN 1.1] pre-built 1.1 Release #11411 Core

by Lukas Renggli

Thank you Marcus, my hudson is rebuilding the whole shebang now. Lukas On 20 July 2010 15:48, Marcus Denker <marcus.denker(a)inria.fr> wrote: > > Â Â Â Â https://gforge.inria.fr/frs/download.php/27296/PharoCore-1.1.zip > > -- > Marcus Denker Â -- http://www.marcusdenker.de > INRIA Lille -- Nord Europe. Team RMoD. > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli www.lukas-renggli.ch

July 20, 2010

Re: [Pharo-project] How to see failures/erros of the Hudson server?

by Lukas Renggli

As Nick points out. Additionally, the image with the tests is saves so you can download and run it. Lukas 2010/7/20 Nick Ager <nick.ager(a)gmail.com>: > Failing tests: > http://hudson.lukas-renggli.ch/job/Pharo/lastCompletedBuild/testReport/ > http://hudson.lukas-renggli.ch/job/Pharo/lastCompletedBuild/testReport/Test… > log: > http://hudson.lukas-renggli.ch/job/Pier/64/console > > 2010/7/20 Mariano Martinez Peck <marianopeck(a)gmail.com> >> >> I know we have just started with the Hudson server, but is there a way to >> see why a test is failing/error ?Â For the errors, at least we can see the >> PharoDebug.log ? >> THe other idea we have today (talking with Marcus) is to have RFB running >> in the hudson images. So that we can connect and browse it. Of course, it >> could be password protected so that not everybody can do it. >> >> What do you think? >> >> Cheers >> >> Mariano >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > -- Lukas Renggli www.lukas-renggli.ch

July 20, 2010

[Pharo-project] [ANN 1.1] pre-built 1.1 Release #11411 Core

by Marcus Denker

https://gforge.inria.fr/frs/download.php/27296/PharoCore-1.1.zip -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

July 20, 2010

[Pharo-project] [update 1.1] #11411

by Marcus Denker

11411 ----- Issue 2684: Deleting a method is not logged Issue 2694: MC screwing up ancestry -- Marcus Denker -- http://www.marcusdenker.de INRIA Lille -- Nord Europe. Team RMoD.

July 20, 2010

Re: [Pharo-project] How to see failures/erros of the Hudson server?

by Nick Ager

Failing tests: http://hudson.lukas-renggli.ch/job/Pharo/lastCompletedBuild/testReport/ http://hudson.lukas-renggli.ch/job/Pharo/lastCompletedBuild/testReport/Test… log: http://hudson.lukas-renggli.ch/job/Pier/64/console 2010/7/20 Mariano Martinez Peck <marianopeck(a)gmail.com> > I know we have just started with the Hudson server, but is there a way to > see why a test is failing/error ? For the errors, at least we can see the > PharoDebug.log ? > THe other idea we have today (talking with Marcus) is to have RFB running > in the hudson images. So that we can connect and browse it. Of course, it > could be password protected so that not everybody can do it. > > What do you think? > > Cheers > > Mariano > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 20, 2010

[Pharo-project] How to see failures/erros of the Hudson server?

by Mariano Martinez Peck

I know we have just started with the Hudson server, but is there a way to see why a test is failing/error ? For the errors, at least we can see the PharoDebug.log ? THe other idea we have today (talking with Marcus) is to have RFB running in the hudson images. So that we can connect and browse it. Of course, it could be password protected so that not everybody can do it. What do you think? Cheers Mariano

July 20, 2010

[Pharo-project] Can TestRunner notify failures and errors while they happen?

by Mariano Martinez Peck

Hi folks. One of my tasks while creating the dev images is to run all the tests and analyze the errors and failures. TestRunner list the results (failures and errors) at the end. I would like it to update show and update the TestRunner UI. Why ? Because if it shows me the errors and failures while they happen, I can take the same image, open it again, and start to analyze them. And I don't have to wait until de endâ¦ Can someone help me with this? what do you think ? Thanks Mariano

July 20, 2010

Re: [Pharo-project] [SPAM] New Features for Hudson Build Tools

by Sven Van Caekenberghe

Lukas, This is really very impressive stuff. Thanks for setting all this up and sharing it with us. I am learning a lot from it. Sven On 20 Jul 2010, at 10:26, Lukas Renggli wrote: > I've added some new functionality to the Hudson Build Toos for Pharo: > > 1. I've added a script build-oneclick.sh that builds OneClick > distributions. This means that with every successful build there will > be a new OneClick distribution. > > For example, the latest PetitParser OneClick distribution is available > from: http://hudson.lukas-renggli.ch/job/PetitParser/lastSuccessfulBuild/artifact…. > > 2. I've changes build.sh to automatically find and fetch dependent > images. This makes the configuration in Hudson much simpler, as no > images need to be copied around. > > For example, the Hudson configuration of PetitParser looks as follows: > > build.sh -i omnibrowser -s petitparser -o petitparser > build.sh -i petitparser -s testrunner -s petitparser-tests -o > petitparser-tests > build-oneclick.sh -i petitparser -o PetitParser-OneClick -t > PetitParser -c PetitParser -n petitparser > > As usual all the code is available from: > > http://github.com/renggli/builder > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 20, 2010

Re: [Pharo-project] New Features for Hudson Build Tools

by StÃ©phane Ducasse

> I've added some new functionality to the Hudson Build Toos for Pharo: > > 1. I've added a script build-oneclick.sh that builds OneClick > distributions. This means that with every successful build there will > be a new OneClick distribution. EXCELLENT!!!!! > > For example, the latest PetitParser OneClick distribution is available > from: http://hudson.lukas-renggli.ch/job/PetitParser/lastSuccessfulBuild/artifact…. > > 2. I've changes build.sh to automatically find and fetch dependent > images. This makes the configuration in Hudson much simpler, as no > images need to be copied around. > > For example, the Hudson configuration of PetitParser looks as follows: > > build.sh -i omnibrowser -s petitparser -o petitparser > build.sh -i petitparser -s testrunner -s petitparser-tests -o > petitparser-tests > build-oneclick.sh -i petitparser -o PetitParser-OneClick -t > PetitParser -c PetitParser -n petitparser > > As usual all the code is available from: > > http://github.com/renggli/builder > > Lukas > > -- > Lukas Renggli > www.lukas-renggli.ch > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 20, 2010

Re: [Pharo-project] collaboractive book

by Tudor Girba

I am reading, but it will take a while until I can look into this :(. Doru On 20 Jul 2010, at 10:54, Francois Stephany wrote: > I had this error on the Moose website in May. > Doru fixed it... Hopefully he reads this mailing list ;) > > Francois > > On 20/07/10 10:01, Norbert Hartl wrote: >> Hi, >> >> I just looked at the book and this is great. But the search is broken >> >> >> Error: subscript is out of bounds: 8212 >> >> FYI, >> >> >> Norbert >> >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com "The coherence of a trip is given by the clearness of the goal."

July 20, 2010

Re: [Pharo-project] Monticello repository types

by Geert Claes

Nick Ager wrote: > > I use FTP - setup is easy, whereas setting up a private squeaksource > repository is more of an undertaking (I imagine) > Sure, I guess you could also register your project on SqueakSource.com as a "private" project. -- View this message in context: http://forum.world.st/Monticello-repository-types-tp2295053p2295162.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

July 20, 2010

Re: [Pharo-project] Monticello repository types

by Norbert Hartl

On 20.07.2010, at 10:45, Geert Claes wrote: > > > Mariano Martinez Peck wrote: >> >> I know Smallworks company uses FTP for all their repositories. >> > > Fair enough. Are there any protocols that are not (yet) supported (e.g. > WebDav?) A http repository is basically a WebDAV folder. Otherwise it would be hard to upload files. Norbert

July 20, 2010

Re: [Pharo-project] collaboractive book

by Francois Stephany

I had this error on the Moose website in May. Doru fixed it... Hopefully he reads this mailing list ;) Francois On 20/07/10 10:01, Norbert Hartl wrote: > Hi, > > I just looked at the book and this is great. But the search is broken > > > Error: subscript is out of bounds: 8212 > > FYI, > > > Norbert > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 20, 2010

Re: [Pharo-project] Monticello repository types

by Nick Ager

I use FTP - setup is easy, whereas setting up a private squeaksource repository is more of an undertaking (I imagine) On 20 July 2010 09:45, Geert Claes <geert.wl.claes(a)gmail.com> wrote: > > > Mariano Martinez Peck wrote: > > > > I know Smallworks company uses FTP for all their repositories. > > > > Fair enough. Are there any protocols that are not (yet) supported (e.g. > WebDav?) > -- > View this message in context: > http://forum.world.st/Monticello-repository-types-tp2295053p2295122.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 20, 2010

Re: [Pharo-project] Monticello repository types

by Geert Claes

Mariano Martinez Peck wrote: > > I know Smallworks company uses FTP for all their repositories. > Fair enough. Are there any protocols that are not (yet) supported (e.g. WebDav?) -- View this message in context: http://forum.world.st/Monticello-repository-types-tp2295053p2295122.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

July 20, 2010

Re: [Pharo-project] Bug in DateAndTime?

by Max Leske

Might be a few days but I'll try. Max On 19.07.2010, at 14:31, StÃ©phane Ducasse wrote: > > On Jul 19, 2010, at 2:19 PM, Max Leske wrote: > >> Hi Stef >> >> Me and Lukas just resolved the issue. It's not really a bug (although having two hard coded epochs seems a bit silly to me); the problem was in my code and the offset is time zone related. >> This means: my problem is solved and no bug report needs to be opened. >> Maybe at some point somone might consider a refactoring though... :) > > > sure can you propose something and check it with lukas. > We value better code!!!! > > Stef > >> >> Thanks, >> Max >> >> On 19.07.2010, at 13:07, StÃ©phane Ducasse wrote: >> >>> Dear Max >>> >>> Right now I do not know. >>> >>> which version are you using? >>> >>> Stef >>> >>> >>>> Hi. >>>> >>>> Evaluating: >>>> >>>> DateAndTime now asUnixTime >>>> >>>> and then creating a DateAndTime object from the result: >>>> >>>> DateAndTime fromUnixTime: <seconds> >>>> >>>> does not yield an equivalent object. As far as I can tell, this is because the unix epoch is hard coded in two places: >>>> >>>> DateAndTime class>>unixEpoch >>>> "Answer a DateAndTime representing the Unix epoch (1 January 1970, midnight UTC)" >>>> ^ self basicNew >>>> ticks: #(2440588 0 0) offset: Duration zero; >>>> yourself. >>>> >>>> DateAndTime>>fromUnixTime: anInteger >>>> ^ self fromSeconds: anInteger + >>>> 2177452800 "unix epoch constant" >>>> >>>> So in the end I get a difference of 7200 seconds. >>>> >>>> I'll gladly open up a bug but can someone please confirm that this is actually a bug and that I didn't miss something? >>>> >>>> Cheers, >>>> Max >>>> _______________________________________________ >>>> Pharo-project mailing list >>>> Pharo-project(a)lists.gforge.inria.fr >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >>> >>> >>> _______________________________________________ >>> Pharo-project mailing list >>> Pharo-project(a)lists.gforge.inria.fr >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 20, 2010

Re: [Pharo-project] about hex

by Mariano Martinez Peck

On Tue, Jul 20, 2010 at 2:46 AM, Henrik Johansen < henrik.s.johansen(a)veloxit.no> wrote: > Iirc, it was reintroduced in Pharo in relation to SqueakDBX, might want to > check with Mariano that changes will be compatible/SqueakDBX is updated. > > Hi Henrik. Indeed, it was included for SqueakDBX. Actually, not for itself, but the NATIVE postgresql driver used to depends in the chripto package. Then, the MD5 class was put in PharoCore so it didn't depend anymore. But the hex was missing. Now...if you ask me if this change will affect the postgres native driver, I HAVE NO IDEA. The only thing I can do is to run the tests. But for that I need a postgres with encrypthion running handly. Do you know Yanni? Cheers Mariano > Cheers, > Henry > > Den 19. juli 2010 kl. 23:05 skrev StÃ©phane Ducasse < > stephane.ducasse(a)inria.fr>: > > > **Tx** > > http://code.google.com/p/pharo/issues/detail?id=2699 > > > > Stef > > > > > > On Jul 19, 2010, at 10:07 PM, Levente Uzonyi wrote: > > > >> On Mon, 19 Jul 2010, StÃ©phane Ducasse wrote: > >> > >>> Levente > >>> Now what hex should returns? > >> > >> If you mean Integer >> #hex then see here: > >> > http://lists.squeakfoundation.org/pipermail/squeak-dev/2010-July/151957.html > >> > >> > >> Levente > >> > >>> > >>> On Jul 19, 2010, at 9:33 PM, stephane ducasse wrote: > >>> > >>>> If I recall hex was removed because it was used for html related > thing. > >>>> > >>>> Stef > >>>> > >>>> > >>>> > >>>> Looks like the hex method will be changed in Squeak and > >>>> we should keep track using this issue to see if Pharo has > >>>> to follow to keep compatible (also for Cog). > >>>> > >>>> See > >>>> > >>>> > http://lists.squeakfoundation.org/pipermail/squeak-dev/2010-July/151949.html > >>>> > >>>> _______________________________________________ > >>>> Pharo-project mailing list > >>>> Pharo-project(a)lists.gforge.inria.fr > >>>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >>> > >>> > >>> _______________________________________________ > >>> Pharo-project mailing list > >>> Pharo-project(a)lists.gforge.inria.fr > >>> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > >> _______________________________________________ > >> Pharo-project mailing list > >> Pharo-project(a)lists.gforge.inria.fr > >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 20, 2010

[Pharo-project] New Features for Hudson Build Tools

by Lukas Renggli

I've added some new functionality to the Hudson Build Toos for Pharo: 1. I've added a script build-oneclick.sh that builds OneClick distributions. This means that with every successful build there will be a new OneClick distribution. For example, the latest PetitParser OneClick distribution is available from: http://hudson.lukas-renggli.ch/job/PetitParser/lastSuccessfulBuild/artifact…. 2. I've changes build.sh to automatically find and fetch dependent images. This makes the configuration in Hudson much simpler, as no images need to be copied around. For example, the Hudson configuration of PetitParser looks as follows: build.sh -i omnibrowser -s petitparser -o petitparser build.sh -i petitparser -s testrunner -s petitparser-tests -o petitparser-tests build-oneclick.sh -i petitparser -o PetitParser-OneClick -t PetitParser -c PetitParser -n petitparser As usual all the code is available from: http://github.com/renggli/builder Lukas -- Lukas Renggli www.lukas-renggli.ch

July 20, 2010

Re: [Pharo-project] connection to access databases

by Mariano Martinez Peck

On Mon, Jul 19, 2010 at 9:07 PM, StÃ©phane Ducasse <stephane.ducasse(a)inria.fr > wrote: > Thanks eliot. > Who is maintaining ODBC? to commit the changes? > > I think Andreas. > On Jul 19, 2010, at 7:39 PM, Eliot Miranda wrote: > > > moduleName > > "Return the name of the module for this library" > > Smalltalk platformName = 'Win32' ifTrue:[^'odbc32']. > > Smalltalk platformName = 'unix' ifTrue:[^ 'libodbc.so']. > > Smalltalk platformName = 'Mac OS' ifTrue:[^ 'libiodbc.dylib']. > > ^self error: 'Don''t know the ODBC library name' > > > > works for me. Find attached. > > > > On Mon, Jul 19, 2010 at 1:41 AM, Tudor Girba <tudor.girba(a)gmail.com> > wrote: > > Hi, > > > > Thanks for all the pointers. I am now testing on Mac using the Actual > driver: > > http://www.actualtech.com/product_access.php > > > > I managed to get it running, but now I have problems with the ODBC Pharo > implementation because there seems to be no module for Mac: > > > > ODBCLibrary class>>moduleName > > "Return the name of the module for this library" > > SmalltalkImage current platformName = 'Win32' ifTrue: [ ^ 'odbc32' > ]. > > SmalltalkImage current platformName = 'unix' ifTrue: [ ^ > 'libodbc.so' ]. > > ^ self error: 'Don''t know the ODBC library name' > > > > Is there something to be done in this area? > > > > Cheers, > > Doru > > > > > > On 19 Jul 2010, at 01:04, GermÃ¡n Arduino wrote: > > > > Yes, Indeed, I mean, I used a driver to access, but can't remember now > > the brand, but I'm sure I not payed for it :) > > > > May be I used some trial version.... > > > > 2010/7/18 Levente Uzonyi <leves(a)elte.hu>: > > > > On Sun, 18 Jul 2010, GermÃ¡n Arduino wrote: > > > > Not, I'm not talking of propietary software. > > > > I'm talking of one I used when helped Diego with the testing of the > > odbc package. Don't remember now, but may be this > > http://www.unixodbc.org/ ? > > > > ODBC is just an API, if you don't have a driver for yourdatabase, then it > > won't help. > > > > > > Levente > > > > > > About Mac, sorry, never touched a mac in all my life.... > > > > Cheers. > > > > > > 2010/7/18 Levente Uzonyi <leves(a)elte.hu>: > > > > On Sun, 18 Jul 2010, GermÃ¡n Arduino wrote: > > > > Hi Tudor: > > > > Is as Levente says, you must define an ODBC source on a Windows PC > > (Alternatively on Unix you can use ODBC also). > > > > I don't know any free ODBC drivers for Access on un*x. I only know a > > driver > > which costs 4-5 times more than the windows OS itself :). But > > there's a driver for mac which costs only 30 usd if you're interested. > > > > > > Levente > > > > > > Some examples on: http://wiki.squeak.org/squeak/2480 > > > > Cheers. > > GermÃ¡n. > > > > > > 2010/7/18 Levente Uzonyi <leves(a)elte.hu>: > > > > On Sun, 18 Jul 2010, Tudor Girba wrote: > > > > Thanks Mariano! > > > > Indeed, if I load ConfigurationOfFFI first, everything loads well. > > > > I am a complete newbie in this area. Can anyone tell me what I should > > do > > next? > > > > I imagine that I should connect to an Access server. If yes, how would > > I > > do that? > > > > Also, do I need anything else, like a C plugin/library to get the C > > calls > > from ODBCLibrary going? > > > > First you'll need a pc running windows. Then you have to create an ODBC > > Data > > Source for your Access file. Then you'll be able to create a connection > > to > > that datasource from your image. > > > > > > Levente > > > > > > Cheers, > > Doru > > > > > > On 18 Jul 2010, at 09:17, Mariano Martinez Peck wrote: > > > > > > > > On Sun, Jul 18, 2010 at 8:49 AM, Tudor Girba <tudor.girba(a)gmail.com> > > wrote: > > Hi, > > > > I tried loading it, but I get : > > "This package depends on the following classes: > > ExternalLibrary > > ExternalStructure" > > > > Can anyone tell me where to find these from? > > > > This means that you need Metacello ;) > > > > Those classes are from FFI, a pre-requisite for ODBC to work. > > Maybe there is a ConfigurationOfODBC somewhere... > > > > For the moment, I recommend you to install FFI using the > > ConfigurationOfFFI. > > > > Cheers > > > > Mariano > > > > > > Also, are there eternal prerequisites to work with ODBC? > > > > Cheers, > > Doru > > > > > > > > On 18 Jul 2010, at 00:35, Levente Uzonyi wrote: > > > > On Sat, 17 Jul 2010, Tudor Girba wrote: > > > > Hi, > > > > Is there a way to connect to a Microsoft Access database from Pharo? > > > > Yes, with ODBC. > > > > > > Levente > > > > > > I have an mdb file of 300 Mb that I would need to analyze. > > > > Cheers, > > Doru > > > > > > -- > > www.tudorgirba.com > > > > "Next time you see your life passing by, say 'hi' and get to know > > her." > > > > > > > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > -- > > www.tudorgirba.com > > > > "Speaking louder won't make the point worthier." > > > > > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > -- > > www.tudorgirba.com > > > > "When people care, great things can happen." > > > > > > > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > > > > > -- > > ================================================= > > GermÃ¡n S. Arduino <gsa @ arsol.net> Twitter: garduino > > Arduino Software & Web Hosting http://www.arduinosoftware.com > > PasswordsPro http://www.passwordspro.com > > ================================================= > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > -- > > www.tudorgirba.com > > > > "Every thing should have the right to be different." > > > > > > > > > > > > _______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > <ODBCLibrary > class-moduleName.st>_______________________________________________ > > Pharo-project mailing list > > Pharo-project(a)lists.gforge.inria.fr > > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 20, 2010

Re: [Pharo-project] [ANN] ConfigurationOfMagma for Magma 1.1r1

by Mariano Martinez Peck

Hi Miguel. I understand your problem, and we are working on that with Dale and Stef. Having repositories for a specific Pharo version and so on. But we are just starting.... By the moment, you can use what Sean told you, or, just update the configuration, but in a new version. I mean....if you had the version 2.3.4 that was released and working in pharo 1.0, then don't touch it, create a new one, say, 2.4 and that works in 1.1. Of course this is not the perfect solution, but for the moment. But one thing for sure: do not update the SAME version that was working for 1.0. Magma should continue working in 1.0 using the same metacello version. cheers mariano On Tue, Jul 20, 2010 at 9:26 AM, Sean P. DeNigris <sean(a)clipperadams.com>wrote: > > For now, you can use the hack that Dale suggested in > > http://groups.google.com/group/metacello/browse_thread/thread/a27c95d24974a… > . > > > Take a look a ConfigurationOfGemTools>>project. In that method I created > a > > #'pharo1.0Beta' attribute by looking at the SystemVersion current > > version... > -- > View this message in context: > http://forum.world.st/ANN-ConfigurationOfMagma-for-Magma-1-1r1-tp2242566p22… > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 20, 2010

Re: [Pharo-project] [ANN] ConfigurationOfMagma for Magma 1.1r1

by Mariano Martinez Peck

Hi Torsten...I guess you meant Miguel ? On Tue, Jul 20, 2010 at 8:29 AM, Torsten Bergmann <astares(a)gmx.de> wrote: > Hi Mariano, > > why dont you add: > > (Scanner class includesSelector: #allowUnderscoreAsAssignment:) > ifTrue: [Scanner allowUnderscoreAsAssignment: true] > > > to the #preLoadForPharo ? > > 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(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 20, 2010

Re: [Pharo-project] Monticello repository types

by Mariano Martinez Peck

I know Smallworks company uses FTP for all their repositories. On Tue, Jul 20, 2010 at 9:37 AM, Geert Claes <geert.wl.claes(a)gmail.com>wrote: > > I just made a few diagrams trying to explain how Monticello/Metacello works > as part of the collaborActive book > (http://book.pharo-project.org/book/introduction/Repository) and I was > just > wondering if anyone actually uses Monticello repository types like FTP, > SMTP, ... ? Would it make things easier to just keep Directory/Cache and > HTTP and maybe GOODS as standard repository types? > -- > View this message in context: > http://forum.world.st/Monticello-repository-types-tp2295053p2295053.html > Sent from the Pharo Smalltalk mailing list archive at Nabble.com. > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 20, 2010

[Pharo-project] collaboractive book

by Norbert Hartl

Hi, I just looked at the book and this is great. But the search is broken Error: subscript is out of bounds: 8212 FYI, Norbert

July 20, 2010

Re: [Pharo-project] help to update actions done in Pharo 1.1

by Mariano Martinez Peck

On Tue, Jul 20, 2010 at 2:51 AM, Henrik Johansen < henrik.s.johansen(a)veloxit.no> wrote: > > > Den 20. juli 2010 kl. 02:04 skrev Levente Uzonyi <leves(a)elte.hu>: > > > On Mon, 19 Jul 2010, StÃ©phane Ducasse wrote: > > > >> > >> On Jul 19, 2010, at 10:08 PM, Levente Uzonyi wrote: > >> > >>> On Mon, 19 Jul 2010, StÃ©phane Ducasse wrote: > >>> > >>>> Where is the code that we should check to be included in 1.2? > >>> > >>> Basically in Squeak, but I'm sure most of them are in the Pharo > bugtracker. > >> Thanks but > >> well... > >> tell me that this is too boring to report it which I can understand but > not that > >> kind of answer because this is certainly not the case since I'm nearly > the only one > >> to look at squeak fixes. > > > > The code of HashedCollection and subclasses in Pharo and Squeak are too > different now, there are no patches/changesets that can convert one to the > other. So a brave soul has to do it by hand. > > > > > > Levente > > > I've been meaning to for the longest time, but work/other bugs/holiday > keeps getting in my way :( > > If my friends start leaving me alone, I might finally get some time at the > end of this last holiday week though ;) > Henry, do you know if there is a ticket for that? at least we won't forget it ;) > >> > > > Cheers, > Henry > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >

July 20, 2010

[Pharo-project] Monticello repository types

by Geert Claes

I just made a few diagrams trying to explain how Monticello/Metacello works as part of the collaborActive book (http://book.pharo-project.org/book/introduction/Repository) and I was just wondering if anyone actually uses Monticello repository types like FTP, SMTP, ... ? Would it make things easier to just keep Directory/Cache and HTTP and maybe GOODS as standard repository types? -- View this message in context: http://forum.world.st/Monticello-repository-types-tp2295053p2295053.html Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

July 20, 2010

Re: [Pharo-project] [ANN] ConfigurationOfMagma for Magma 1.1r1

by Sean P. DeNigris

For now, you can use the hack that Dale suggested in http://groups.google.com/group/metacello/browse_thread/thread/a27c95d24974a…. > Take a look a ConfigurationOfGemTools>>project. In that method I created a > #'pharo1.0Beta' attribute by looking at the SystemVersion current > version... -- View this message in context: http://forum.world.st/ANN-ConfigurationOfMagma-for-Magma-1-1r1-tp2242566p22… Sent from the Pharo Smalltalk mailing list archive at Nabble.com.

July 20, 2010

Re: [Pharo-project] connection to access databases

by Tudor Girba

Hi Eliot, Thanks for the suggestion. I did check the connection again and it seems that something was wrong with System-wide DSN. Everything seems to work properly with User DSN. Thanks everyone for all the help. Doru On 20 Jul 2010, at 00:13, Eliot Miranda wrote: > Hi Doru, > > On Mon, Jul 19, 2010 at 1:51 PM, Tudor Girba <tudor.girba(a)gmail.com> > wrote: > Thanks Eliot. > > Indeed this allowed me to connect, but now I have problems executing > even simple queries. For example, when executing the following code, > the sqlAllocStmtConnection:statement: fails saying "Could not > coerce arguments": > > connection := ODBCConnection dsn: 'Test' user: '' password: ''. > connection query: 'select * from TABLE' > > Am I doing something wrong, or is it something else? > > difficult to know. I was using ODBC & mysql to test the threaded VM > late last year but I haven't ported this to Snow Leopard. Anyway, I > used Apple's ODBC tools and the mysql tools to check the database > was setup correctly before I used the ODBCConnect code. Apple's > recently released their ODBC tools for SNow Leopard http://reviews.cnet.com/8301-13727_7-10330516-263.html > . So I recommend using the relevant tools to check the DB is > configured correctly before you try and debug ODBCConnect. > > cheers, > Eliot > > > Cheers, > Doru > > > On 19 Jul 2010, at 19:39, Eliot Miranda wrote: > > moduleName > "Return the name of the module for this library" > Smalltalk platformName = 'Win32' ifTrue:[^'odbc32']. > Smalltalk platformName = 'unix' ifTrue:[^ 'libodbc.so']. > Smalltalk platformName = 'Mac OS' ifTrue:[^ 'libiodbc.dylib']. > ^self error: 'Don''t know the ODBC library name' > > works for me. Find attached. > > On Mon, Jul 19, 2010 at 1:41 AM, Tudor Girba <tudor.girba(a)gmail.com> > wrote: > Hi, > > Thanks for all the pointers. I am now testing on Mac using the > Actual driver: > http://www.actualtech.com/product_access.php > > I managed to get it running, but now I have problems with the ODBC > Pharo implementation because there seems to be no module for Mac: > > ODBCLibrary class>>moduleName > "Return the name of the module for this library" > SmalltalkImage current platformName = 'Win32' ifTrue: [ ^ > 'odbc32' ]. > SmalltalkImage current platformName = 'unix' ifTrue: [ ^ > 'libodbc.so' ]. > ^ self error: 'Don''t know the ODBC library name' > > Is there something to be done in this area? > > Cheers, > Doru > > > On 19 Jul 2010, at 01:04, GermÃ¡n Arduino wrote: > > Yes, Indeed, I mean, I used a driver to access, but can't remember now > the brand, but I'm sure I not payed for it :) > > May be I used some trial version.... > > 2010/7/18 Levente Uzonyi <leves(a)elte.hu>: > > On Sun, 18 Jul 2010, GermÃ¡n Arduino wrote: > > Not, I'm not talking of propietary software. > > I'm talking of one I used when helped Diego with the testing of the > odbc package. Don't remember now, but may be this > http://www.unixodbc.org/ ? > > ODBC is just an API, if you don't have a driver for yourdatabase, > then it > won't help. > > > Levente > > > About Mac, sorry, never touched a mac in all my life.... > > Cheers. > > > 2010/7/18 Levente Uzonyi <leves(a)elte.hu>: > > On Sun, 18 Jul 2010, GermÃ¡n Arduino wrote: > > Hi Tudor: > > Is as Levente says, you must define an ODBC source on a Windows PC > (Alternatively on Unix you can use ODBC also). > > I don't know any free ODBC drivers for Access on un*x. I only know a > driver > which costs 4-5 times more than the windows OS itself :). But > there's a driver for mac which costs only 30 usd if you're interested. > > > Levente > > > Some examples on: http://wiki.squeak.org/squeak/2480 > > Cheers. > GermÃ¡n. > > > 2010/7/18 Levente Uzonyi <leves(a)elte.hu>: > > On Sun, 18 Jul 2010, Tudor Girba wrote: > > Thanks Mariano! > > Indeed, if I load ConfigurationOfFFI first, everything loads well. > > I am a complete newbie in this area. Can anyone tell me what I should > do > next? > > I imagine that I should connect to an Access server. If yes, how would > I > do that? > > Also, do I need anything else, like a C plugin/library to get the C > calls > from ODBCLibrary going? > > First you'll need a pc running windows. Then you have to create an > ODBC > Data > Source for your Access file. Then you'll be able to create a > connection > to > that datasource from your image. > > > Levente > > > Cheers, > Doru > > > On 18 Jul 2010, at 09:17, Mariano Martinez Peck wrote: > > > > On Sun, Jul 18, 2010 at 8:49 AM, Tudor Girba <tudor.girba(a)gmail.com> > wrote: > Hi, > > I tried loading it, but I get : > "This package depends on the following classes: > ExternalLibrary > ExternalStructure" > > Can anyone tell me where to find these from? > > This means that you need Metacello ;) > > Those classes are from FFI, a pre-requisite for ODBC to work. > Maybe there is a ConfigurationOfODBC somewhere... > > For the moment, I recommend you to install FFI using the > ConfigurationOfFFI. > > Cheers > > Mariano > > > Also, are there eternal prerequisites to work with ODBC? > > Cheers, > Doru > > > > On 18 Jul 2010, at 00:35, Levente Uzonyi wrote: > > On Sat, 17 Jul 2010, Tudor Girba wrote: > > Hi, > > Is there a way to connect to a Microsoft Access database from Pharo? > > Yes, with ODBC. > > > Levente > > > I have an mdb file of 300 Mb that I would need to analyze. > > Cheers, > Doru > > > -- > www.tudorgirba.com > > "Next time you see your life passing by, say 'hi' and get to know > her." > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > www.tudorgirba.com > > "Speaking louder won't make the point worthier." > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > www.tudorgirba.com > > "When people care, great things can happen." > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > > > -- > ================================================= > GermÃ¡n S. Arduino <gsa @ arsol.net> Twitter: garduino > Arduino Software & Web Hosting http://www.arduinosoftware.com > PasswordsPro http://www.passwordspro.com > ================================================= > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > www.tudorgirba.com > > "Every thing should have the right to be different." > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > <ODBCLibrary class- > moduleName.st>_______________________________________________ > > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > -- > www.tudorgirba.com > > "Every thing has its own flow." > > > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project -- www.tudorgirba.com "One cannot do more than one can do."

July 20, 2010

Re: [Pharo-project] [ANN] ConfigurationOfMagma for Magma 1.1r1

by StÃ©phane Ducasse

We should have a MetacelloRepository for Pharo1.0 and Pharo1.1 and probably metacello should support versions too. Stef On Jul 20, 2010, at 5:59 AM, Miguel Enrique CobÃ¡ MartÃnez wrote: > El sÃ¡b, 10-07-2010 a las 12:14 -0300, GermÃ¡n Arduino escribiÃ³: > >> I saw that exist a preference, but seems not work. >> >> Also a closed issue talking about this topic (1544) but really don't >> understand how to use this in Pharo 1.0. >> >> Any clarification will be appreciated. > > Hola GermÃ¡n, > > just have the time to check this issue. I found the problem. > This configuration was made and tested for PharoCore 1.0 (and maybe > Pharo 1.0 but I always test on Pharo Core images). The version I > published with support for 1.1r1 was > > ConfigurationOfMagma-MiguelCoba.31.mcz from 3 June 2010, 7:40:32 pm. > > Thas was tested, as I said, in PharoCore 1.0. In pharo core 1.0 the > underscores are allowed. > Also, in PharoCore 1.0 the setting is changed in a preference > > Preferences class>>allowUnderScoreAssingment. > > Remember that currently only PharoCore 1.0 is released and stable. 1.1 > is frozen and 1.2 is unstable. > > Now, the configuration was modified in order to work for 1.1 and 1.2. > So the method: > > ConfigurationOfMagma>>preLoadForPharo > "Magma extends EventSensor that was replaced by InputEventSensor in > Pharo and Magma still has underscore code" > > Smalltalk at: #EventSensor put: InputEventSensor. > > got this line added: > > Scanner allowUnderscoreAsAssignment: true. > > But this is correct only for Pharo 1.1 and 1.2. In those versions of > pharo, is the Scanner class the responsible of allowing or not the > underscore in the code. In Pharo 1.0 that method doesn't exist in > Scanner class. So the error you saw. > > So the configuration of magma now loads in 1.1 and 1.2 but is broken on > the stable release. > > fortunately this can be reverted and everything will be ok. But... > > two things: > > - If we modify a stable configuration in order to make it work in a RC > or unstable version of pharo things will probably broke, because of the > many changes of the new version of pharo respect to the old one. > - We must decide about the aproach for handle this. > One proposal suggested to copy all the configurations tested in a > given pharo version to a new repository for the next release. > I proposed to use tags in the version methods that specify what > versions of pharo they apply to (but didn't provide any code for this so > the copy of configuration has more viability :) > > No matter what option is elected as long as is elected soon. Why, > because people understandably want software to run in the newest version > of pharo, but if there isn't a specific configuration for the new > version, they will modify and possibly broke the stable one. > > So people, what should we do? > Dale, can you please give your opinion. We need to decide now. > > P.S. I will revert for now the change in ConfigurationOfMagma so it > works for 1.0 and will be broken for 1.1 and 1.2. > > Thanks > > > >> >> Cheers. >> >> >> El 9 de julio de 2010 20:12, GermÃ¡n Arduino <garduino(a)gmail.com> >> escribiÃ³: >> I checked a bit and saw that such method is on Scanner class >> on PharoCore 1.2, but not on Pharo 1.0. >> >> What I missed? >> >> >> El 9 de julio de 2010 19:46, GermÃ¡n Arduino >> <garduino(a)gmail.com> escribiÃ³: >> >> >> Hi; >> >> Thanks by the useful configuration. >> >> I tried today by first time on a Pharo 1.0 image and >> get a DNU >> >> Scanner class(Object)>> >> doesNotUnderstand: #allowUnderscoreAsAssignment: >> >> I need to install some patch before run the >> installation? >> >> Cheers. >> GermÃ¡n. >> >> >> >> >> El 3 de junio de 2010 21:46, Miguel Enrique CobÃ¡ >> MartÃnez <miguel.coba(a)gmail.com> escribiÃ³: >> >> I'm pleased to announce that the >> ConfigurationOfMagma now includes >> >> >> support for loading version 1.1r1 of Magma. >> >> In a Pharo or PharoCore 1.0 image evaluate: >> >> Gofer it >> squeaksource: 'MetacelloRepository'; >> package: 'ConfigurationOfMagma'; >> load. >> >> To install the Magma Client evaluate: >> >> ConfigurationOfMagma project latestVersion >> load: 'Client' >> >> To install the Magma Server evaluate: >> >> ConfigurationOfMagma project latestVersion >> load: 'Server' >> >> To install the Magma Tester evaluate: >> >> ConfigurationOfMagma project latestVersion >> load: 'Tester' >> >> Then if you want, run the test suite. Evaluate >> in a workspace: >> >> MagmaTestCase allowWriteBarrier: false. >> MagmaTestCase fullSuite maDebug. >> >> >> Enjoy >> -- >> Miguel CobÃ¡ >> http://miguel.leugim.com.mx >> >> >> _______________________________________________ >> Magma mailing list >> Magma(a)lists.squeakfoundation.org >> http://lists.squeakfoundation.org/mailman/listinfo/magma >> >> >> >> >> -- >> ================================================= >> GermÃ¡n S. Arduino <gsa @ arsol.net> Twitter: >> garduino >> Arduino Software & Web Hosting >> http://www.arduinosoftware.com >> PasswordsPro http://www.passwordspro.com >> ================================================= >> >> >> >> >> >> > > -- > Miguel CobÃ¡ > http://miguel.leugim.com.mx > > > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 20, 2010

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

by StÃ©phane Ducasse

could the people with a bit of knowledge try to write a map of all the possible and working solutions? People are telling me that python doc is good so may be we should also consider that arranging knowledge on maps is the first step Please take 15 mins because in 15 min you can get a real impact! > http://www.squeaksource.com/XMLPullParser.html > > If I would going to write a XML parser, I'd go for a VTD parser instead. > Cheers, > > HernÃ¡n > > 2010/7/19 Norbert Hartl <norbert(a)hartl.name>: >> >> On 06.07.2010, at 23:04, jaayer wrote: >> >>> >>> >>> ---- 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(a)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: >>> <?xml version="1.0" encoding="UTF-8"?> >>> <foo xmlns:foo="http://foo" a="one" b="two"> >>> <bar>test<baz /> >>> <foobar>test</foobar> >>> </bar> >>> </foo> >>> >> Could you elaborate on the usage of xmlns? The one you defined does nothing. The foo in the xml is just the element name. I would like to know >> >> - how to define a namespace prefix for an element >> - how to define a default namespace for an element >> >> I think I need another look in the xml parser since last time :) Thanks for putting effort into xml parser. Is there a pull parser available or planned? >> >> thanks, >> >> Norbert >> >> >> _______________________________________________ >> Pharo-project mailing list >> Pharo-project(a)lists.gforge.inria.fr >> http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project >> > > _______________________________________________ > Pharo-project mailing list > Pharo-project(a)lists.gforge.inria.fr > http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project

July 20, 2010