U++ forum: Welcome to the forum

Re: More Xmlize functions [message #25414 is a reply to message #25413]

Mon, 22 February 2010 12:41

koldo
Messages: 3435
Registered: August 2008

Senior Veteran

luzr wrote on Mon, 22 February 2010 12:26

koldo wrote on Mon, 22 February 2010 04:25

luzr wrote on Mon, 22 February 2010 09:16

koldo wrote on Mon, 22 February 2010 03:02

Hello all

Xmlize functions are a nice way to get serialization using instead of a raw binary file, a XML file.

Advantages are:

- If you change your classes design, .xml data saved is read properly so your old .xml files are useful.

- They integrate very well with code

- Serialization file is a readable .xml file

Now Xmlize.c /.h supports many classes. However some classes and types are not included yet:

- int16
- byte
- Date
- Time
- DropList
- DropTime
- DropDate
- EditDouble
- Option

I have included new files Xmlize2.c / .h to support these types and classes.

If you want to use them just insert Xmlize2.c int your files and #include Xmlize2.h.

Of course they could be integrated in Core Xmlize.c /.h files Smile

Are you sure about implementing the time/date this way?

Maybe we should rather use XmlRpc format? (You can see that in XmlRpc package).

Mirek

Hello Mirek

I thought XmlRpc protocol was not related with serialization.

Anyway if we do not have to use Xmlize it would be better to label it as deprecated. I have spent some hours in it until now.

If it is worthwhile to use it, please indicate me your way to implement time/date.

Ops, nope. What I was saying that perhaps text format used in XmlRpc to represent the date with single attribute is better than to implement it with several.

See:

http://en.wikipedia.org/wiki/XML-RPC

they use

<dateTime.iso8601>19980717T14:08:55</dateTime.iso8601>

of course, in Xmlize, this might be something like

<id value="19980717T14:08:55">

Mirek

Sorry for the misunderstanding Smile

It makes sense. I will change it.

Best regards
Iñaki

Report message to a moderator