Hi, i cannot find anymore OPAX under XML-Parser. After the long discussion about the future of OPAX i guess that at the end OPAX has been move, but where? I cannot see any package related to OPAX into the XML-Support repo. Where i can find the last version of the OPAX packages that have been moved from XML-Parser?
Cheers,
Fabrizio
---- On Sat, 27 Nov 2010 03:35:18 -0800 Fabrizio Perin wrote ----
Hi, i cannot find anymore OPAX under XML-Parser. After the long discussion about the future of OPAX i guess that at the end OPAX has been move, but where? I cannot see any package related to OPAX into the XML-Support repo. Where i can find the last version of the OPAX packages that have been moved from XML-Parser?
Cheers,
Fabrizio _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi Fabrizio. I sent a mail to Tudo a few days ago outlining my intentions but have not heard back. I suppose I should have contacted you too, as you are also a maintainer of Opax.
The plan was to move Opax and other non-essential components out of XML-Support so we can have a lean core into which add-ons can be optionally loaded and without which the useful, standalone components can be used. The XML-Writer classes are now a separate package (XML-Writer) residing in a separate repository and can be used without XML-Parser. The same is true of two collection classes used by XML-Parser and XML-Writer. The XML-Parser tests are in a separate package, but still reside in the same repository.
Opax was extracted into two packages, one for the core and another for the tests, and a Metacello ConfigurationOfOpax was created for it. I attached all three packages and mailed them to Tudor. I will forward the email to you.
Opax should live at http://www.squeaksource.com/OPAX. The Metacello ConfigurationOfXMLSupport package has already (since v.36) been told to look there for it. To load in Opax through XML-Support, you will (once the extracted packages and configuration are uploaded to the Opax repository) just need to evaluate ConfigurationOfXMLSupport lastVersion load: 'Opax'. I plan on also creating an "AddOns" package group that will load Pastell, Opax and other additions automatically.
Hi,
The version from the OPAX repository is slightly older than the one from XMLSupport, but the only difference are some comments.
In any case, Fabrizio, please take a look at the XMLDOMParser and the XMLPluggableElementFactory. They will probably do exactly what you want. Perhaps it would be interesting to move some traversal methods from Opax to the XMLElement.
Here is the example from Jaayer: doc := (XMLDOMParser on: aStringOrStream) nodeFactory: (XMLPluggableElementFactory new handleElement: 'user' withClass: MyUserElement; handleElement: 'report' withClass: MyReportElement; handleElement: 'report' namespaceURI: 'urn:specialReport' withClass: MySpecialReportElement); parseDocument.
Cheers, Doru
On 27 Nov 2010, at 14:38, jaayer wrote:
---- On Sat, 27 Nov 2010 03:35:18 -0800 Fabrizio Perin wrote ----
Hi, i cannot find anymore OPAX under XML-Parser. After the long discussion about the future of OPAX i guess that at the end OPAX has been move, but where? I cannot see any package related to OPAX into the XML-Support repo. Where i can find the last version of the OPAX packages that have been moved from XML-Parser?
Cheers,
Fabrizio _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi Fabrizio. I sent a mail to Tudo a few days ago outlining my intentions but have not heard back. I suppose I should have contacted you too, as you are also a maintainer of Opax.
The plan was to move Opax and other non-essential components out of XML-Support so we can have a lean core into which add-ons can be optionally loaded and without which the useful, standalone components can be used. The XML-Writer classes are now a separate package (XML-Writer) residing in a separate repository and can be used without XML-Parser. The same is true of two collection classes used by XML-Parser and XML-Writer. The XML-Parser tests are in a separate package, but still reside in the same repository.
Opax was extracted into two packages, one for the core and another for the tests, and a Metacello ConfigurationOfOpax was created for it. I attached all three packages and mailed them to Tudor. I will forward the email to you.
Opax should live at http://www.squeaksource.com/OPAX. The Metacello ConfigurationOfXMLSupport package has already (since v.36) been told to look there for it. To load in Opax through XML-Support, you will (once the extracted packages and configuration are uploaded to the Opax repository) just need to evaluate ConfigurationOfXMLSupport lastVersion load: 'Opax'. I plan on also creating an "AddOns" package group that will load Pastell, Opax and other additions automatically.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"It's not what we do that matters most, it's how we do it."
---- On Sat, 27 Nov 2010 13:52:51 -0800 Tudor Girba wrote ----
Hi,
The version from the OPAX repository is slightly older than the one from XMLSupport, but the only difference are some comments.
Do either of you plan on maintaining Opax separately? There is presently a project reference to Opax in ConfigurationOfXMLSupport that expects a ConfigurationOfOpax package in http://www.squeaksource.com/OPAX. You can merge the core and tests back into a single package, dispense with the Metacello configuration, and I can change the project reference to Opax in ConfigurationOfXMLSupport to be a package reference instead.
In any case, Fabrizio, please take a look at the XMLDOMParser and the XMLPluggableElementFactory. They will probably do exactly what you want. Perhaps it would be interesting to move some traversal methods from Opax to the XMLElement.
Here is the example from Jaayer: doc := (XMLDOMParser on: aStringOrStream) nodeFactory: (XMLPluggableElementFactory new handleElement: 'user' withClass: MyUserElement; handleElement: 'report' withClass: MyReportElement; handleElement: 'report' namespaceURI: 'urn:specialReport' withClass: MySpecialReportElement); parseDocument.
Cheers, Doru
On 27 Nov 2010, at 14:38, jaayer wrote:
---- On Sat, 27 Nov 2010 03:35:18 -0800 Fabrizio Perin wrote ----
Hi, i cannot find anymore OPAX under XML-Parser. After the long discussion about the future of OPAX i guess that at the end OPAX has been move, but where? I cannot see any package related to OPAX into the XML-Support repo. Where i can find the last version of the OPAX packages that have been moved from XML-Parser?
Cheers,
Fabrizio _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi Fabrizio. I sent a mail to Tudo a few days ago outlining my intentions but have not heard back. I suppose I should have contacted you too, as you are also a maintainer of Opax.
The plan was to move Opax and other non-essential components out of XML-Support so we can have a lean core into which add-ons can be optionally loaded and without which the useful, standalone components can be used. The XML-Writer classes are now a separate package (XML-Writer) residing in a separate repository and can be used without XML-Parser. The same is true of two collection classes used by XML-Parser and XML-Writer. The XML-Parser tests are in a separate package, but still reside in the same repository.
Opax was extracted into two packages, one for the core and another for the tests, and a Metacello ConfigurationOfOpax was created for it. I attached all three packages and mailed them to Tudor. I will forward the email to you.
Opax should live at http://www.squeaksource.com/OPAX. The Metacello ConfigurationOfXMLSupport package has already (since v.36) been told to look there for it. To load in Opax through XML-Support, you will (once the extracted packages and configuration are uploaded to the Opax repository) just need to evaluate ConfigurationOfXMLSupport lastVersion load: 'Opax'. I plan on also creating an "AddOns" package group that will load Pastell, Opax and other additions automatically.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"It's not what we do that matters most, it's how we do it."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
As I said, at this moment, your Factory implementation is better. The only current reason to use Opax is compatibility, and perhaps a couple of traversal methods.
So, just directly reference the package, because I do not expect much movement in Opax soon.
Doru
On 28 Nov 2010, at 02:31, jaayer wrote:
---- On Sat, 27 Nov 2010 13:52:51 -0800 Tudor Girba wrote ----
Hi,
The version from the OPAX repository is slightly older than the one from XMLSupport, but the only difference are some comments.
Do either of you plan on maintaining Opax separately? There is presently a project reference to Opax in ConfigurationOfXMLSupport that expects a ConfigurationOfOpax package in http://www.squeaksource.com/OPAX. You can merge the core and tests back into a single package, dispense with the Metacello configuration, and I can change the project reference to Opax in ConfigurationOfXMLSupport to be a package reference instead.
In any case, Fabrizio, please take a look at the XMLDOMParser and the XMLPluggableElementFactory. They will probably do exactly what you want. Perhaps it would be interesting to move some traversal methods from Opax to the XMLElement.
Here is the example from Jaayer: doc := (XMLDOMParser on: aStringOrStream) nodeFactory: (XMLPluggableElementFactory new handleElement: 'user' withClass: MyUserElement; handleElement: 'report' withClass: MyReportElement; handleElement: 'report' namespaceURI: 'urn:specialReport' withClass: MySpecialReportElement); parseDocument.
Cheers, Doru
On 27 Nov 2010, at 14:38, jaayer wrote:
---- On Sat, 27 Nov 2010 03:35:18 -0800 Fabrizio Perin wrote ----
Hi, i cannot find anymore OPAX under XML-Parser. After the long discussion about the future of OPAX i guess that at the end OPAX has been move, but where? I cannot see any package related to OPAX into the XML-Support repo. Where i can find the last version of the OPAX packages that have been moved from XML-Parser?
Cheers,
Fabrizio _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi Fabrizio. I sent a mail to Tudo a few days ago outlining my intentions but have not heard back. I suppose I should have contacted you too, as you are also a maintainer of Opax.
The plan was to move Opax and other non-essential components out of XML-Support so we can have a lean core into which add-ons can be optionally loaded and without which the useful, standalone components can be used. The XML-Writer classes are now a separate package (XML-Writer) residing in a separate repository and can be used without XML-Parser. The same is true of two collection classes used by XML-Parser and XML-Writer. The XML-Parser tests are in a separate package, but still reside in the same repository.
Opax was extracted into two packages, one for the core and another for the tests, and a Metacello ConfigurationOfOpax was created for it. I attached all three packages and mailed them to Tudor. I will forward the email to you.
Opax should live at http://www.squeaksource.com/OPAX. The Metacello ConfigurationOfXMLSupport package has already (since v.36) been told to look there for it. To load in Opax through XML-Support, you will (once the extracted packages and configuration are uploaded to the Opax repository) just need to evaluate ConfigurationOfXMLSupport lastVersion load: 'Opax'. I plan on also creating an "AddOns" package group that will load Pastell, Opax and other additions automatically.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"It's not what we do that matters most, it's how we do it."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Live like you mean it."
---- On Sat, 27 Nov 2010 23:59:28 -0800 Tudor Girba wrote ----
As I said, at this moment, your Factory implementation is better. The only current reason to use Opax is compatibility, and perhaps a couple of traversal methods.
So, just directly reference the package, because I do not expect much movement in Opax soon.
Done.
Doru
On 28 Nov 2010, at 02:31, jaayer wrote:
---- On Sat, 27 Nov 2010 13:52:51 -0800 Tudor Girba wrote ----
Hi,
The version from the OPAX repository is slightly older than the one from XMLSupport, but the only difference are some comments.
Do either of you plan on maintaining Opax separately? There is presently a project reference to Opax in ConfigurationOfXMLSupport that expects a ConfigurationOfOpax package in http://www.squeaksource.com/OPAX. You can merge the core and tests back into a single package, dispense with the Metacello configuration, and I can change the project reference to Opax in ConfigurationOfXMLSupport to be a package reference instead.
In any case, Fabrizio, please take a look at the XMLDOMParser and the XMLPluggableElementFactory. They will probably do exactly what you want. Perhaps it would be interesting to move some traversal methods from Opax to the XMLElement.
Here is the example from Jaayer: doc := (XMLDOMParser on: aStringOrStream) nodeFactory: (XMLPluggableElementFactory new handleElement: 'user' withClass: MyUserElement; handleElement: 'report' withClass: MyReportElement; handleElement: 'report' namespaceURI: 'urn:specialReport' withClass: MySpecialReportElement); parseDocument.
Cheers, Doru
On 27 Nov 2010, at 14:38, jaayer wrote:
---- On Sat, 27 Nov 2010 03:35:18 -0800 Fabrizio Perin wrote ----
Hi, i cannot find anymore OPAX under XML-Parser. After the long discussion about the future of OPAX i guess that at the end OPAX has been move, but where? I cannot see any package related to OPAX into the XML-Support repo. Where i can find the last version of the OPAX packages that have been moved from XML-Parser?
Cheers,
Fabrizio _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi Fabrizio. I sent a mail to Tudo a few days ago outlining my intentions but have not heard back. I suppose I should have contacted you too, as you are also a maintainer of Opax.
The plan was to move Opax and other non-essential components out of XML-Support so we can have a lean core into which add-ons can be optionally loaded and without which the useful, standalone components can be used. The XML-Writer classes are now a separate package (XML-Writer) residing in a separate repository and can be used without XML-Parser. The same is true of two collection classes used by XML-Parser and XML-Writer. The XML-Parser tests are in a separate package, but still reside in the same repository.
Opax was extracted into two packages, one for the core and another for the tests, and a Metacello ConfigurationOfOpax was created for it. I attached all three packages and mailed them to Tudor. I will forward the email to you.
Opax should live at http://www.squeaksource.com/OPAX. The Metacello ConfigurationOfXMLSupport package has already (since v.36) been told to look there for it. To load in Opax through XML-Support, you will (once the extracted packages and configuration are uploaded to the Opax repository) just need to evaluate ConfigurationOfXMLSupport lastVersion load: 'Opax'. I plan on also creating an "AddOns" package group that will load Pastell, Opax and other additions automatically.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"It's not what we do that matters most, it's how we do it."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Live like you mean it."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi, thanks a lot for the answers and the information provided on the overall discussion. As Doru also said there will probably no movement on OPAX in the next period. Also i agree with Doru that a ConfigurationOfOPAX it is probably not necessary. I will try to move some of the stuff implemented in OPAX to the XMLPluggableElementFactory. Anyway with the version 1.0.6 of XMLSupport i can still work with all my stuff i will figure out if it will be necessary move on the newest version.
Cheers,
Fabrizio
On 28 Nov 2010, at 19:48, jaayer wrote:
---- On Sat, 27 Nov 2010 23:59:28 -0800 Tudor Girba wrote ----
As I said, at this moment, your Factory implementation is better. The only current reason to use Opax is compatibility, and perhaps a couple of traversal methods.
So, just directly reference the package, because I do not expect much movement in Opax soon.
Done.
Doru
On 28 Nov 2010, at 02:31, jaayer wrote:
---- On Sat, 27 Nov 2010 13:52:51 -0800 Tudor Girba wrote ----
Hi,
The version from the OPAX repository is slightly older than the one from XMLSupport, but the only difference are some comments.
Do either of you plan on maintaining Opax separately? There is presently a project reference to Opax in ConfigurationOfXMLSupport that expects a ConfigurationOfOpax package in http://www.squeaksource.com/OPAX. You can merge the core and tests back into a single package, dispense with the Metacello configuration, and I can change the project reference to Opax in ConfigurationOfXMLSupport to be a package reference instead.
In any case, Fabrizio, please take a look at the XMLDOMParser and the XMLPluggableElementFactory. They will probably do exactly what you want. Perhaps it would be interesting to move some traversal methods from Opax to the XMLElement.
Here is the example from Jaayer: doc := (XMLDOMParser on: aStringOrStream) nodeFactory: (XMLPluggableElementFactory new handleElement: 'user' withClass: MyUserElement; handleElement: 'report' withClass: MyReportElement; handleElement: 'report' namespaceURI: 'urn:specialReport' withClass: MySpecialReportElement); parseDocument.
Cheers, Doru
On 27 Nov 2010, at 14:38, jaayer wrote:
---- On Sat, 27 Nov 2010 03:35:18 -0800 Fabrizio Perin wrote ----
Hi, i cannot find anymore OPAX under XML-Parser. After the long discussion about the future of OPAX i guess that at the end OPAX has been move, but where? I cannot see any package related to OPAX into the XML-Support repo. Where i can find the last version of the OPAX packages that have been moved from XML-Parser?
Cheers,
Fabrizio _______________________________________________ Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Hi Fabrizio. I sent a mail to Tudo a few days ago outlining my intentions but have not heard back. I suppose I should have contacted you too, as you are also a maintainer of Opax.
The plan was to move Opax and other non-essential components out of XML-Support so we can have a lean core into which add-ons can be optionally loaded and without which the useful, standalone components can be used. The XML-Writer classes are now a separate package (XML-Writer) residing in a separate repository and can be used without XML-Parser. The same is true of two collection classes used by XML-Parser and XML-Writer. The XML-Parser tests are in a separate package, but still reside in the same repository.
Opax was extracted into two packages, one for the core and another for the tests, and a Metacello ConfigurationOfOpax was created for it. I attached all three packages and mailed them to Tudor. I will forward the email to you.
Opax should live at http://www.squeaksource.com/OPAX. The Metacello ConfigurationOfXMLSupport package has already (since v.36) been told to look there for it. To load in Opax through XML-Support, you will (once the extracted packages and configuration are uploaded to the Opax repository) just need to evaluate ConfigurationOfXMLSupport lastVersion load: 'Opax'. I plan on also creating an "AddOns" package group that will load Pastell, Opax and other additions automatically.
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"It's not what we do that matters most, it's how we do it."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-- www.tudorgirba.com
"Live like you mean it."
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
Moose-dev mailing list Moose-dev@iam.unibe.ch https://www.iam.unibe.ch/mailman/listinfo/moose-dev
-
Fabrizio Perin -
jaayer -
Tudor Girba