[GNOME] Smoothing serialisation

Tomorrow I'll elaborate on some challenges, but for now I'll summarise the past two weeks

  • spent most of the first week on school stuff.  I'm a Masters student and thesis work doesn't really stop, so unfortunately, I ended up with meetings and some overwhelming stuff

    • I did get a letter to ebassi at the start and got to think about his wonderful response

  • spent the second week

    • designing tests

    • designing interfaces

    • creating tests

    • determining modifications required to pass tests

    • implementing modifications

I pushed them over the past few hours to git. :)

Current state of XML serialisation

  • a GObject can be automatically serialised if all you want is

    • to serialise its public properties.  Depending on how you handle an object's properties, this could be enough, as long as the internal logic isn't hiding anything that wouldn't restore itself when the same properties are again set.  I think this is similar to what json-glib serialisation automatically handles.

    • to serialise types that GValue can transform into strings, including enums, or objects that only contain one of these three.

What's coming this week

  • The interface you'll want to implement to manually handle parts of serialisation (e.g. non-public property data). I've been using thesis code to test this from the start.  I'm sadly not allowed to share my thesis code, but I'll be using general examples in the code I'll commit over the next few days.

Next two weeks

  • Collections, I want to have automatic support for a bunch

    • GList is hard, because its ParamSpec just calls it a gpointer, so I need to figure out how to identify it, but GHashTable gets to be a GHashTable.  

    • Gee's collections seem like they might be easier

  • ask glib people more about serialisation interface requirements for glib.  ebassi briefly mentioned the idea in the last e-mail, so I should get back to him with some more concrete questions.

Stuff to consider

  • Data other than public properties.  Is this desirable?  ebassi's response to my last e-mail the other week made me think it's not that desirable.  Right now I have tests for private properties (that fail) and public and private fields (that fail).  I sort of like the idea of automagically serialising as much as possible.

  • Merging with glib.

Note: I use "serialise" with -ise in my writing, but the code uses "serialize" through out.  

Tomorrow I'll talk about issues I ran into and a couple bugs I filed. :)  #vala and #gnome have been lovely, if a bit peaceful, for help so far.  So has looking at more source code for libraries than I ever expected. :D

Keine Kommentare:

Kommentar veröffentlichen

Dieses Blog durchsuchen


#Technology #GNOME gnome gxml fedora bugs linux vala google #General firefox security gsoc GUADEC android bug xml fedora 18 javascript libxml2 programming web blogger encryption fedora 17 gdom git emacs libgdata memory mozilla open source serialisation upgrade web development API Spain containers design evolution fedora 16 fedora 20 fedora 22 fedup file systems friends future glib gnome shell internet luks music performance phone photos php podman preupgrade tablet testing typescript yum #Microblog Network Manager adb apache art automation bash brno catastrophe css data loss debian debugging deja-dup disaster docker emusic errors ext4 facebook fedora 19 gee gir gitlab gitorious gmail gobject google talk google+ html libxml mail microsoft mtp mysql namespaces nautilus nextcloud owncloud picasaweb pitivi ptp python raspberry pi resizing rpm school selinux signal sms speech dispatcher systemd technology texting time management uoguelph usability video web design youtube #Tech Air Canada C Electron Element Empathy Europe GError GNOME 3 GNOME Files Go Google Play Music Grimes IRC Mac OS X Mario Kart Memento Nintendo Nintendo Switch PEAP Selenium Splatoon UI VPN Xiki accessibility advertising ai albums anaconda anonymity apple ask asus eee top automake autonomous automobiles b43 backup battery berlin bit rot broadcom browsers browsing canada canadian english cars chrome clarity comments communication compiler complaints computer computers configuration console constructive criticism cron cropping customisation dataloss dconf debug symbols design patterns desktop summit development discoverability distribution diy dnf documentation drm duplicity e-mail efficiency email english environment estate experimenting ext3 fedora 11 festival file formats firejail flac flatpak forgottotagit freedom friendship fuse galaxy nexus galton gay rights gdb german germany gimp gio gjs gnome software gnome-control-center google assistant google calendar google chrome google hangouts google reader gqe graphviz growth gtest gtg gtk gvfs gvfs metadata hard drive hard drives hardware help hp humour ide identity instagram installation instant messaging integration intel interactivity introspection jabber java java 13 jobs kernel keyboard language language servers languages law learning lenovo letsencrypt libreoffice librpm life livecd liveusb login lsp macbook maintainership mariadb mario matrix memory leaks messaging mounting mouse netflix new zealand node nodelist numix obama oci ogg oggenc oh the humanity open open standards openoffice optimisation org-mode organisation package management packagekit paint shedding parallelism pdo perl pipelight privacy productivity progress progressive web apps pumpkin pwa pyright quality recursion redhat refactoring repairs report rhythmbox sandboxes scheduling screenshots self-navigating car shell sleep smartphones software software engineering speed sql ssd synergy tabs test tests themes thesis tracker travel triumf turtles tv tweak twist typing university update usb user experience valadoc video editing volunteering vpnc waf warm wayland weather web apps website wifi wiki wireless wishes work xinput xmpp xorg xpath
Powered by Blogger.