GVariant based API instead of GValue based
Bug #675870 reported by
Mikkel Kamstrup Erlandsen
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
dee |
Fix Released
|
Medium
|
Mikkel Kamstrup Erlandsen |
Bug Description
The 0.4 series uses GValue as generic container for data both internally and in the API.
This should be switched over to GVariant instead. This has numerous benefits:
* We can have a single row setter dee_model_set_row (model, iter, variant)
* More advanced getters dee_row_unpack (model, iter, column, signature, va_list)
* We guarantee that all values are serializable (a GValue can hold any GObject)
* Better/cleaner integration with GDBus and GSettings
* The data container itself is refcounted (GValue is not)
Related branches
lp://staging/~unity-team/dee/gdbus
- Neil J. Patel (community): Approve
- Diff: 0 lines
Changed in dee: | |
milestone: | none → 0.5.0 |
Changed in dee: | |
assignee: | nobody → Mikkel Kamstrup Erlandsen (kamstrup) |
importance: | Undecided → Medium |
status: | New → Triaged |
summary: |
- GVariant based API instead og GValue based + GVariant based API instead of GValue based |
Changed in dee: | |
status: | Triaged → Fix Released |
To post a comment you must log in.