Hi,
> It's really quiet here, huh? ;-)
>
> I've improved the common model of GUI for dynamic filling and
> description. And "instance_attributes", "operations" and "expression"
> have been rewritten based on the model.
> Additionally the metadata of RA has been exploited for adding
> "instance_attributes" and "operations" objects.
>
> Changeset 11792:65350279a168
>
> Any comment or test will be welcome.Thanks!
I want to try this new feature,
but before that, there is still a build problem.
Pacemaker's crm part handles the data as "xmlNode".
Meanwhile, it seems that mgmt(= pygui?) identify it as "ha_msg".
So, compiler would say like this:
"error: 'xmlNode' has no member named 'values'", or
"warning: passing argument 1 of 'cl_get_string' from incompatible pointer
type".
Is mgmt part also going to be changed its data type from "ha_msg" to
"xmlNode" ?
Thanks,
Junko
_______________________________________________
Pacemaker mailing list
Pacemaker@clusterlabs.org
http://list.clusterlabs.org/mailman/listinfo/pacemaker
> It's really quiet here, huh? ;-)
>
> I've improved the common model of GUI for dynamic filling and
> description. And "instance_attributes", "operations" and "expression"
> have been rewritten based on the model.
> Additionally the metadata of RA has been exploited for adding
> "instance_attributes" and "operations" objects.
>
> Changeset 11792:65350279a168
>
> Any comment or test will be welcome.Thanks!
I want to try this new feature,
but before that, there is still a build problem.
Pacemaker's crm part handles the data as "xmlNode".
Meanwhile, it seems that mgmt(= pygui?) identify it as "ha_msg".
So, compiler would say like this:
"error: 'xmlNode' has no member named 'values'", or
"warning: passing argument 1 of 'cl_get_string' from incompatible pointer
type".
Is mgmt part also going to be changed its data type from "ha_msg" to
"xmlNode" ?
Thanks,
Junko
_______________________________________________
Pacemaker mailing list
Pacemaker@clusterlabs.org
http://list.clusterlabs.org/mailman/listinfo/pacemaker