Recent changes to feature-requests

#12 Expose data source context to user

Matthieu Labas — Sat, 11 May 2019 16:55:27 -0000

status: open --> closed
assigned_to: Matthieu Labas
Group: v4.3.0 --> v4.3.3

#12 Expose data source context to user

Matthieu Labas — Mon, 06 May 2019 12:38:53 -0000

OK, I think I get it: the entity reading the XML file is not aware about the XML structure and needs to know the offset and length.
I will add your patch in the next version, hopefully this week.
Thanks!

#12 Expose data source context to user

Alexander Goomenyuk — Wed, 01 May 2019 11:50:32 -0000

Thanks for reply!

Here is real life example:
There are two exchangeable units: a flange board and add-on equipment.
There is EEPROM on add-on equipment which stores some parameters of attached add-on in XML format. The add-on is attached to flange board. The firmware running on that board reads EEPROM, extracts XML file and parse it. Two XML-tags are searched for during the parsing. First tag defines begining of configuration parameters and second tag specifies the name of configuration parameters file. Firmware creates that configuration parameter file and extracts content of XML file embraced between those two tags. Then the host is notified to read parameter file out.

One needs to know exact location (file offset or buffer offset) of begining and end of second tag in order to extract the content and copy it to another location.

<config><filename><rest>...</rest></filename></config>

filename content

<rest>...</rest>

#12 Expose data source context to user

Matthieu Labas — Wed, 01 May 2019 10:38:12 -0000

Hi Alexander,

I'm not sure I understand what is your need. Could you give me an example (if possible) so I can see if there are some other ways around?

Thank you for the patch anyway, adding those information might be interesting anyway!

Regards,
Matthieu

Expose data source context to user

Alexander Goomenyuk — Mon, 29 Apr 2019 11:50:19 -0000

In some cases content of XML file embedded into some flags must be extracted and stored separately of XML content.

In this case, it is useful to know exact location beginning and end of text of interest.

In the attched patch I added two fields to SAX_Data structure:
1. DataSourceType type
2. void *src

Expose data source context to user

Alexander Goomenyuk — Mon, 29 Apr 2019 11:50:19 -0000

Ticket 12 has been modified: Expose data source context to user
Edited By: Matthieu Labas (matthieu-labas)
Status updated: u'open' => u'closed'
_milestone updated: u'v4.3.0' => u'v4.3.3'
Owner updated: None => u'matthieu-labas'

#9 Ease node creation

Matthieu Labas — Sat, 05 Jan 2019 11:12:24 -0000

status: open --> closed
Group: v4.3.0 --> v4.2.8

#11 Print XML to a char buffer.

Matthieu Labas — Thu, 17 May 2018 13:25:22 -0000

Need to resolve #10 before, to ease buffer allocation.

#11 Print XML to a char buffer.

Matthieu Labas — Thu, 17 May 2018 13:23:54 -0000

assigned_to: Matthieu Labas

Print XML to a char buffer.

Matthieu Labas — Thu, 17 May 2018 13:23:15 -0000

Currently, XMLDoc_print() can only output the XML to a FILE*. It would be interesting to output it to a char* also, just like parsing can be performed on a FILE* or a char*.