Hello!
Piotr Sipika has written on Friday, 4 July, at 20:43:
>On 07/03/2014 04:22 PM, Andrej N. Gritsenko wrote:
>> What is the current state of this work? I believe it is the time to
>> make a release for LXPanel so we need some progress into this plugin as
>> well.
>I'm 95% done migrating the plugin to the new API.
>The only thing missing is saving configuration to the panel config file
>-- I need to look over other plugins' source to figure out how and when
>their configuration gets written to the file (would appreciate some help
>with that - a point in the right direction - if you have a bit of time).
This is pretty simple in fact - after your configuration dialog is
closed (it can be handled connecting to the "response" signal of the
dialog widget) or some value is changed (that if you prefer to apply your
changes immediately so you would connect to individual dialog's widgets
signals to catch changes) you can call either config_group_set_int() API
or config_group_set_string() one to save new value into the config. The
pointer to config for the plugin instance is given as a parameter on the
instance creation so it may be remembered in the private data to use for
that purpose.
>I don't want to hold back the release, so my plan is to do the following
>by the end of this weekend:
>1) fix configuration persistence
>2) fix the 'refresh' logic in the details screen
>3) [possibly] move initial forecast retrieval from main thread
Do not force yourself, please, we don't have any deadline yet and I
don't think all other plugins will be migrated to new API in next few
days anyway. And using separate thread for all retrievals is the most
desired thing anyway, we'll rather wait you to finish that. :)
>I just pushed some changes to github[1]. If you have any other comments,
>or suggestions, please do let me know.
Please, inspect LXPanelPluginInit description in the plugin.h header
file - the config callback should never run configuration dialog but just
compose it, you know you can handle different responces anyway, just
connect to the "response" signal and use g_signal_stop_emission_by_name()
API if you want to keep dialog still open after responce.
>I'll provide details for completed functionality Sunday night (US
>Eastern Time).
>Sorry for the silence for the past 3 months -- real-life is keeping me
>on my toes.
Thank you very much for your work! There is nothing to be sorry for,
we all are just volunteers here. :)
With best regards,
Andriy.
------------------------------------------------------------------------------
Open source business process management suite built on Java and Eclipse
Turn processes into business applications with Bonita BPM Community Edition
Quickly connect people, data, and systems into organized workflows
Winner of BOSSIE, CODIE, OW2 and Gartner awards
http://p.sf.net/sfu/Bonitasoft
_______________________________________________
Lxde-list mailing list
Lxde-list@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/lxde-list
