www.digitalmars.com         C & C++   DMDScript  

digitalmars.D.announce - dxml 0.3.0 released

reply Jonathan M Davis <newsgroup.d jmdavisprog.com> writes:
Well, since I'm going to be talking about dxml at dconf, and it's likely
that I'll be talking about stuff that was not in the 0.2.* releases, it
seemed like I should get a new release out before dconf. So, here it is.

dxml 0.3.0 has now been released.

I won't repeat everything that's in the changelog, but the biggest changes
are that writer support has now been added, and it's now possible to
configure how the parser handles non-standard entity references.

Please report any bugs that you find via github.

Changelog: http://jmdavisprog.com/changelog/dxml/0.3.0.html
Documentation: http://jmdavisprog.com/docs/dxml/0.3.0/
Github: https://github.com/jmdavis/dxml/tree/v0.3.0
Dub: http://code.dlang.org/packages/dxml

- Jonathan M Davis
Apr 19
next sibling parent reply Suliman <evermind live.ru> writes:
Am I right remember that this lib is planed to be included as 
std.xml replacement?
Apr 19
next sibling parent "H. S. Teoh" <hsteoh quickfur.ath.cx> writes:
On Thu, Apr 19, 2018 at 05:21:15PM +0000, Suliman via Digitalmars-d-announce
wrote:
 Am I right remember that this lib is planed to be included as std.xml
 replacement?
Yes. I'm really looking forward to that. T -- A linguistics professor was lecturing to his class one day. "In English," he said, "A double negative forms a positive. In some languages, though, such as Russian, a double negative is still a negative. However, there is no language wherein a double positive can form a negative." A voice from the back of the room piped up, "Yeah, yeah."
Apr 19
prev sibling parent Jonathan M Davis <newsgroup.d jmdavisprog.com> writes:
On Thursday, April 19, 2018 17:21:15 Suliman via Digitalmars-d-announce 
wrote:
 Am I right remember that this lib is planed to be included as
 std.xml replacement?
It is a potential candidate to replace std.xml. It is currently the plan that once I feel that it's complete enough and battle-tested enough, I will submit it to the Phobos review process, after which it may or may not end up in Phobos. That will depend entirely on how that process goes. The only other potential candidate that I'm aware of was a GSoC project that stalled after the student disappeared (presumably, he got busy with school again and never got back to it), and it shows no sign of ever being completed. - Jonathan M Davis
Apr 19
prev sibling next sibling parent reply aberba <karabutaworld gmail.com> writes:
On Thursday, 19 April 2018 at 14:40:58 UTC, Jonathan M Davis 
wrote:
 Well, since I'm going to be talking about dxml at dconf, and 
 it's likely that I'll be talking about stuff that was not in 
 the 0.2.* releases, it seemed like I should get a new release 
 out before dconf. So, here it is.

 dxml 0.3.0 has now been released.

 I won't repeat everything that's in the changelog, but the 
 biggest changes are that writer support has now been added, and 
 it's now possible to configure how the parser handles 
 non-standard entity references.

 Please report any bugs that you find via github.

 Changelog: http://jmdavisprog.com/changelog/dxml/0.3.0.html
 Documentation: http://jmdavisprog.com/docs/dxml/0.3.0/
 Github: https://github.com/jmdavis/dxml/tree/v0.3.0
 Dub: http://code.dlang.org/packages/dxml

 - Jonathan M Davis
I understand XML is more powerful for some stuff... however XML libs naming conventions generally seem verbose (thanks Microsoft)...I've never used XML beyound HTML though. I started with JSON and has always been JSON.
Apr 19
parent Mengu <mengukagan gmail.com> writes:
On Thursday, 19 April 2018 at 22:38:50 UTC, aberba wrote:
 On Thursday, 19 April 2018 at 14:40:58 UTC, Jonathan M Davis 
 wrote:
 Well, since I'm going to be talking about dxml at dconf, and 
 it's likely that I'll be talking about stuff that was not in 
 the 0.2.* releases, it seemed like I should get a new release 
 out before dconf. So, here it is.

 dxml 0.3.0 has now been released.

 I won't repeat everything that's in the changelog, but the 
 biggest changes are that writer support has now been added, 
 and it's now possible to configure how the parser handles 
 non-standard entity references.

 Please report any bugs that you find via github.

 Changelog: http://jmdavisprog.com/changelog/dxml/0.3.0.html
 Documentation: http://jmdavisprog.com/docs/dxml/0.3.0/
 Github: https://github.com/jmdavis/dxml/tree/v0.3.0
 Dub: http://code.dlang.org/packages/dxml

 - Jonathan M Davis
I understand XML is more powerful for some stuff... however XML libs naming conventions generally seem verbose (thanks Microsoft)...I've never used XML beyound HTML though. I started with JSON and has always been JSON.
it's not that xml is any more powerful than anything else out there however unfortunately you don't get to choose that especially when it comes to integrating old apis in sectors such as banking and travel. it was crucial that we had an xml speaking module in phobos. thank you very much jonathan.
Apr 22
prev sibling next sibling parent reply Jesse Phillips <Jesse.K.Phillips+D gmail.com> writes:
On Thursday, 19 April 2018 at 14:40:58 UTC, Jonathan M Davis 
wrote:

 I won't repeat everything that's in the changelog, but the 
 biggest changes are that writer support has now been added, and 
 it's now possible to configure how the parser handles 
 non-standard entity references.
In reference to http://jmdavisprog.com/docs/dxml/0.3.0/dxml_writer.html#.XMLWriter.writeText "XMLWritingException if the given text is not legal in the text portion of an XML document." Is this to say that the text must be encoded (dxml.util.encodeText) prior to calling this or it will throw if the text contains "<"? This should be clearer in the documentation.
Apr 19
parent reply Jonathan M Davis <newsgroup.d jmdavisprog.com> writes:
On Thursday, April 19, 2018 23:00:03 Jesse Phillips via Digitalmars-d-
announce wrote:
 On Thursday, 19 April 2018 at 14:40:58 UTC, Jonathan M Davis

 wrote:
 I won't repeat everything that's in the changelog, but the
 biggest changes are that writer support has now been added, and
 it's now possible to configure how the parser handles
 non-standard entity references.
In reference to http://jmdavisprog.com/docs/dxml/0.3.0/dxml_writer.html#.XMLWriter.writeTe xt "XMLWritingException if the given text is not legal in the text portion of an XML document." Is this to say that the text must be encoded (dxml.util.encodeText) prior to calling this or it will throw if the text contains "<"? This should be clearer in the documentation.
Yes. I would have thought that that was clear. It throws if any of the characters or sequence of characters in the argument aren't legal in the text portion of an XML document. Those characters that can be legally present in encoded form but not in their literal form can be encoded first with encodeText. I'll try to make the documentation clearer. - Jonathan M Davis
Apr 19
parent reply Jesse Phillips <Jesse.K.Phillips+D gmail.com> writes:
On Friday, 20 April 2018 at 00:46:38 UTC, Jonathan M Davis wrote:

 Yes. I would have thought that that was clear. It throws if any 
 of the characters or sequence of characters in the argument 
 aren't legal in the text portion of an XML document. Those 
 characters that can be legally present in encoded form but not 
 in their literal form can be encoded first with encodeText. 
 I'll try to make the documentation clearer.

 - Jonathan M Davis
I think I just feel it is a little hidden under the exception list. A note in the general description about utilizing encodeText on text which needs encoding would be good.
Apr 20
parent Jonathan M Davis <newsgroup.d jmdavisprog.com> writes:
On Friday, April 20, 2018 16:07:06 Jesse Phillips via Digitalmars-d-announce 
wrote:
 On Friday, 20 April 2018 at 00:46:38 UTC, Jonathan M Davis wrote:
 Yes. I would have thought that that was clear. It throws if any
 of the characters or sequence of characters in the argument
 aren't legal in the text portion of an XML document. Those
 characters that can be legally present in encoded form but not
 in their literal form can be encoded first with encodeText.
 I'll try to make the documentation clearer.
I think I just feel it is a little hidden under the exception list. A note in the general description about utilizing encodeText on text which needs encoding would be good.
Well, for better or worse, it now mentions it directly in the Throws section. - Jonathan M Davis
Apr 20
prev sibling parent reply Dejan Lekic <dejan.lekic gmail.com> writes:
On Thursday, 19 April 2018 at 14:40:58 UTC, Jonathan M Davis 
wrote:
 Well, since I'm going to be talking about dxml at dconf, and 
 it's likely that I'll be talking about stuff that was not in 
 the 0.2.* releases, it seemed like I should get a new release 
 out before dconf. So, here it is.

 dxml 0.3.0 has now been released.

 I won't repeat everything that's in the changelog, but the 
 biggest changes are that writer support has now been added, and 
 it's now possible to configure how the parser handles 
 non-standard entity references.

 Please report any bugs that you find via github.

 Changelog: http://jmdavisprog.com/changelog/dxml/0.3.0.html
 Documentation: http://jmdavisprog.com/docs/dxml/0.3.0/
 Github: https://github.com/jmdavis/dxml/tree/v0.3.0
 Dub: http://code.dlang.org/packages/dxml

 - Jonathan M Davis
I am happy to see dxml moving on! Jonathan, are the interfaces in the dom module generated from the IDL code from W3C?
Apr 20
next sibling parent Kagamin <spam here.lot> writes:
On Friday, 20 April 2018 at 08:45:45 UTC, Dejan Lekic wrote:
 Jonathan, are the interfaces in the dom module generated from 
 the IDL code from W3C?
It's not W3C DOM :)
Apr 20
prev sibling parent Jonathan M Davis <newsgroup.d jmdavisprog.com> writes:
On Friday, April 20, 2018 08:45:45 Dejan Lekic via Digitalmars-d-announce 
wrote:
 On Thursday, 19 April 2018 at 14:40:58 UTC, Jonathan M Davis

 wrote:
 Well, since I'm going to be talking about dxml at dconf, and
 it's likely that I'll be talking about stuff that was not in
 the 0.2.* releases, it seemed like I should get a new release
 out before dconf. So, here it is.

 dxml 0.3.0 has now been released.

 I won't repeat everything that's in the changelog, but the
 biggest changes are that writer support has now been added, and
 it's now possible to configure how the parser handles
 non-standard entity references.

 Please report any bugs that you find via github.

 Changelog: http://jmdavisprog.com/changelog/dxml/0.3.0.html
 Documentation: http://jmdavisprog.com/docs/dxml/0.3.0/
 Github: https://github.com/jmdavis/dxml/tree/v0.3.0
 Dub: http://code.dlang.org/packages/dxml

 - Jonathan M Davis
I am happy to see dxml moving on! Jonathan, are the interfaces in the dom module generated from the IDL code from W3C?
No, that's not something that I'm familiar with. I just made up the API based on what made sense to me. I basically took the API that EntityRange.Entity has and morphed it into what made sense for a tree structure. - Jonathan M Davis
Apr 20