6 Jan
2011
6 Jan
'11
10:31 p.m.
---- On Thu, 06 Jan 2011 08:33:36 -0800 Stéphane Ducasse wrote ----
Hi
may be you should let us pharo dev guys know what is the best?
May be loading a more recent version is more adequate.
Stef
Perhaps you could postpone the integration until Pharo 1.3? Honestly, I am not really sure
if it should be in the core at all, as it adds another megabyte to the image and nothing
in the image depends on it. The real reason why you're considering including it is
that people keep going onto the Pharo lists asking if a Pharo XML parser exists and where
it can be found, because they don't already know of XMLSupport's existence. Rather
than stuffing every popular package into the core image, the long term solution should be
to find a way to enable people to search for Pharo packages. Maybe the Squeak Source
rewrite being planned will be more Google friendly, and you'll be able to put a search
box on the pharo-project.org homepage with a prompt to "Search for Pharo
projects" and people will be able to find whatever they need :)
As for the differences between older and newer packages, there are many, some of which
aren't backwards compatible. For example, the writer API was redone to be block-based
like Seaside's HTML generation API. The #contentString methods return the combined
string content of all descendant elements rather than only of the first child string node.
You can check the changelog at squeaksource.com/XMLSupport for more information. I have
unfortunately been busy lately and unable to work on Pharo-related projects.
On Jan 6, 2011, at 4:59 PM, jaayer wrote:
============ Forwarded message ============
From : jaayer
To : "Alexandre Bergel"
Date : Thu, 06 Jan 2011 07:27:20 -0800
Subject : Re: [Moose-dev] xmlsupport conflict in pharo 1.2
============ Forwarded message ============
---- On Wed, 05 Jan 2011 09:39:31 -0800 Alexandre Bergel wrote ----
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
I had a quick look at it.
In Pharo 1.2, the XML-Parser parkage is clean (i.e.,not dirty). Loading XMLSupport turns
the package dirty. The user is asked whether he is ready to lose his changes. I cannot
determine why the packages turned dirty.
Executing:
Gofer new
squeaksource: 'XMLSupport';
package: 'ConfigurationOfXMLSupport';
load.
(Smalltalk at: #ConfigurationOfXMLSupport) perform: #loadDefault.
in a fresh image raises the popup. Without canceling or accepting, open a Monticello
browser, you will see the package dirty.
Jaaryer, can you have a look at it? There is something weird with the configuration. I
sincerely hope we will have a better tool for managing configuration. I am currently
working on it, but it is still too early for releasing it.
Cheers,
Alexandre
Is the package in Pharo 1.2 the most recent version? Reading the discussion from last
month, it appeared they were opting for an older version. The only Pharo 1.2 image I can
find on the website is a barren core without XMLSupport in it.
Regardless, if you load any of the recent XMLSupport packages and run the test suite, it
will dirty the XML-Tests-Parser package. To understand why, just browse the
XMLParserElementFactoryTest class or read its comment; it generates a number of
"dummy" subclasses of XMLElement for testing purposes in its #setUp message and
removes those classes from the system in its #tearDown message. I have known about this
for weeks but did not consider it to be a problem as other packages ("Tests",
for example) always seem to have an asterisk beside them in the Monticello browser and
nothing seems break as a result. I can easily change this to make those classes static
(always present) rather than dynamically generated/removed, if this is a problem.
On 5 Jan 2011, at 11:41, Tudor Girba wrote:
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev Hi,
XMLSupport is present in the latest Pharo 1.2. Loading a new version generates an
exception apparently, so I removed for the moment XMLSupport from the default
ConfigurationOfMoose.
I think we should only load this conditionally. Or do you have another solution?
Cheers,
Doru
--
www.tudorgirba.com
"Every thing should have the right to be different."
_______________________________________________
Moose-dev mailing list
Moose-dev(a)iam.unibe.ch
https://www.iam.unibe.ch/mailman/listinfo/moose-dev
--
_,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:
Alexandre Bergel http://www.bergel.eu
^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;._,.;:~^~:;.