maemo.org - Talk
Page 20 of 140 « First 101819 20 212230 Last »
Show 40 post(s) from this thread on one page

maemo.org - Talk (https://talk.maemo.org/index.php)
-   Applications (https://talk.maemo.org/forumdisplay.php?f=41)
-   -   [Announce] Queen BeeCon Widget: Super powerful and customizable Widget Generation Engine - Official Thread (https://talk.maemo.org/showthread.php?t=45388)

Sash 2010-05-27 10:55
Re: [Announce] Queen BeeCon Widget: Customizable and flexible monitoring tool.
 
Quote:
Originally Posted by das_schlumpfie (Post 682197)
hi again, so you knows he has those '1 Ghz' and 'Ideal' widgets?

do those actually alter the kernel settings?

thanks
If you're using the scripts from here:
http://talk.maemo.org/showpost.php?p...postcount=3947

The "snippet_ideal.txt" script will change the kernel to ideal settings.

To have a 1Ghz snippet, you have to follow these instructions first:
Code:
1. Launch xterminal
2. root
3. kernel-config load ideal
4. kernel-config limits 500 1000
5. kernel-config save ideal_1000
and then the "snippet_ideal_1000.txt" script will change the kernel to 1Ghz

No!No!No!Yes! 2010-05-27 14:58
Re: [Announce] Queen BeeCon Widget: Customizable and flexible monitoring tool.
 
Quote:
Originally Posted by No!No!No!Yes! (Post 679452)
Uhm ... no easy way to preserve backward compatibility if I implement this feature with Hildon-Extras extensions.
Especially if exported instances, with extended-fonts functionalities, need to be read by older releases.

Same happens if I change Color (both foreground and background) dialog with extended and more cosmetic one.

Unless it is polite to ask users to check and change fonts/color after import.
:confused::(

BTW, is it possible that HeColorButton is a bit buggy with PR1.2 SDK?
http://wiki.maemo.org/images/7/7f/HeColorButton.png
In scratchbox, if I click on black button frame then color dialogs opens, if I click on orange rectangle nothing happens...

Ciao.

UPDATE:
Also if I compile this:
Code:
                GtkWidget *cmdFontBox = gtk_hbox_new (FALSE, 0);//AP1

                GtkWidget *cmdFontSz;
                if (!g_strcmp0(self->priv->cmdExtFont,"")) {
                        GtkWidget *cmdFontFam = hildon_touch_selector_new_text ();//AP1
                        for(i=0;p_fonts[i]!=NULL;i++) {//AP1
                                int j;
                                for (j=0;j<4;j++) {//AP1
                                        gchar fs[256];//AP1
                                        g_sprintf(fs, "%s %s",p_fonts[i], p_fonts_types[j]);//AP1
                                        hildon_touch_selector_append_text (HILDON_TOUCH_SELECTOR (cmdFontFam), fs);//AP1
                                }//AP1
                        }//AP1
                        hildon_touch_selector_set_active (HILDON_TOUCH_SELECTOR (cmdFontFam), 0, self->priv->cmdFontName);//AP1

                        GtkWidget * cmdFontSelector = hildon_picker_button_new (HILDON_SIZE_AUTO_WIDTH | HILDON_SIZE_THUMB_HEIGHT, HILDON_BUTTON_ARRANGEMENT_VERTICAL);//AP1
                        hildon_button_set_title (HILDON_BUTTON (cmdFontSelector), "Font Face: ");//AP1
                        hildon_button_set_alignment (HILDON_BUTTON (cmdFontSelector), 0, 0.5, 0, 0);//AP1
                        hildon_picker_button_set_selector (HILDON_PICKER_BUTTON (cmdFontSelector), HILDON_TOUCH_SELECTOR (cmdFontFam));//AP1
                        gtk_box_pack_start (GTK_BOX (cmdFontBox), cmdFontSelector, FALSE, FALSE, 0);//AP1

                        cmdFontSz = gtk_hscale_new_with_range ((gdouble)8, (gdouble)72, (gdouble)1);//AP1
                        gtk_range_set_value(GTK_RANGE(cmdFontSz), self->priv->cmdFontSize);//AP1
                        gtk_box_pack_start (GTK_BOX (cmdFontBox), cmdFontSz, TRUE, TRUE, 0);//AP1
                }
                GtkWidget *cmdFontFam = he_font_button_new_with_font (self->priv->cmdExtFont);
                gtk_box_pack_start (GTK_BOX (cmdFontBox), cmdFontFam, TRUE, TRUE, 0);

                gtk_container_add (GTK_CONTAINER (content_area), cmdFontBox);//AP1
Everything goes fine ... if I move the he_font_button before the old font selectors and scales ... H-H dumps

Code:
                GtkWidget *cmdFontBox = gtk_hbox_new (FALSE, 0);//AP1

                GtkWidget *cmdFontSz;
                GtkWidget *cmdFontFam = he_font_button_new_with_font (self->priv->cmdExtFont);
                gtk_box_pack_start (GTK_BOX (cmdFontBox), cmdFontFam, TRUE, TRUE, 0);
                if (!g_strcmp0(self->priv->cmdExtFont,"")) {
                        GtkWidget *cmdFontFam = hildon_touch_selector_new_text ();//AP1
                        for(i=0;p_fonts[i]!=NULL;i++) {//AP1
                                int j;
                                for (j=0;j<4;j++) {//AP1
                                        gchar fs[256];//AP1
                                        g_sprintf(fs, "%s %s",p_fonts[i], p_fonts_types[j]);//AP1
                                        hildon_touch_selector_append_text (HILDON_TOUCH_SELECTOR (cmdFontFam), fs);//AP1
                                }//AP1
                        }//AP1
                        hildon_touch_selector_set_active (HILDON_TOUCH_SELECTOR (cmdFontFam), 0, self->priv->cmdFontName);//AP1

                        GtkWidget * cmdFontSelector = hildon_picker_button_new (HILDON_SIZE_AUTO_WIDTH | HILDON_SIZE_THUMB_HEIGHT, HILDON_BUTTON_ARRANGEMENT_VERTICAL);//AP1
                        hildon_button_set_title (HILDON_BUTTON (cmdFontSelector), "Font Face: ");//AP1
                        hildon_button_set_alignment (HILDON_BUTTON (cmdFontSelector), 0, 0.5, 0, 0);//AP1
                        hildon_picker_button_set_selector (HILDON_PICKER_BUTTON (cmdFontSelector), HILDON_TOUCH_SELECTOR (cmdFontFam));//AP1
                        gtk_box_pack_start (GTK_BOX (cmdFontBox), cmdFontSelector, FALSE, FALSE, 0);//AP1

                        cmdFontSz = gtk_hscale_new_with_range ((gdouble)8, (gdouble)72, (gdouble)1);//AP1
                        gtk_range_set_value(GTK_RANGE(cmdFontSz), self->priv->cmdFontSize);//AP1
                        gtk_box_pack_start (GTK_BOX (cmdFontBox), cmdFontSz, TRUE, TRUE, 0);//AP1
                }

                gtk_container_add (GTK_CONTAINER (content_area), cmdFontBox);//AP1
As a second thought with respect to innovations in font and color settings for command and results labels I implemented the new extended font dialog as proposed by qwerty12.

I believe pros will be much more than cons and side effects will be bearable...:
  • Old font selection and button is deprecated
  • Backward compatibility for instances exported from previous releases is guaranteed and settings upgraded as necessary during import
  • Exported instances from release 0.1.9 onward will have their fonts reset to command="Nokia Sans bold italic 12" results="Nokia Sans bold 12" when/if imported in previous releases
Faheem, if you are planning to come up with some bugfixing for the color button issue I'll try to release, into PR1.2 extras-devel repository for preliminary testing, a 0.1.9 working release with enhanced font/color settings within 1 or 2 days.
Otherwise only the font enhancement will be published.

No!No!No!Yes! 2010-05-27 17:20
Re: [Announce] Queen BeeCon Widget: Customizable and flexible monitoring tool.
 
And a crazy idea ... on my mind
DBUS event driven Beecons
:D:cool::eek:

No!No!No!Yes! 2010-05-28 22:49
Re: [Announce] Queen BeeCon Widget: Customizable and flexible monitoring tool.
 
OK ... Queen BeeCon Widget release 0.1.9 is now in extras-devel
Partial Change Log since 0.1.4
Code:
queen-beecon (0.1.9)

    * New: New extended font dialog for command and results labels (Old font selection deprecated; backward compatibility for instances exported from previous releases is guaranteed and settings upgraded as necessary)
    * Changed: Due to new font settings implementation, exported instances from this release onward will have their fonts reset to command="Nokia Sans bold italic 12" results="Nokia Sans bold 12" when imported in previous releases
    * Bugfixing: Some fixing and cleanup in package install/uninstall

queen-beecon (0.1.8-testonly-PR1.2)

    * WARNING This release is for testing purposes only as PR1.2 upgrade brought some instabilities which need forensics!!!
    * New: Implementation of DBUS methods: reset_rearm_timer
    * New: QBW is now integrated into the N900 system backup/restore features according to standard specifications as better described in SDK "Using Backup Application" http://wiki.maemo.org/Documentation/Maemo_5_Developer_Guide/Generic_Platform_Components/Using_Backup_Application#Custom_back-up_locations
    * Changed: Completely revised Timer logic and reset/re-arming for widget periodic auto-update
    * Changed: Visual feedback when Beecons pressed; now rectangle gets drawn as well as cell (better chance of noticing feedback for canvas-less Beecons)
    * Bugfixing: Fixed segmentation fault if dbus get_position method called and dbus_method_monitor turned on

queen-beecon (0.1.7-PR1.1.1)

    * NOTE: Special Build for PR1.1.1
    * New: Implementation of Widget Instance visibility toggle and configuration parameter (for showing or hiding the widget also via DBUS)
    * New: Implementation of following DBUS methods: dbus_method_monitor, show, hide, wakeup, sleep, update_content, update_layout, exec, set_param_string, set_param_int32, set_param_uint32, set_param_double, set_param_boolean, get_param string, set_position, get_position, get_exit_status
    * New: Implementation of following DBUS signals: sig_content_updated
    * Changed: Enhanced DBUS implementation for Widget2Widget & System2Widget Inter Process Communication
    * Changed: Changed default values for some Update Policies in new QBW instances (updOnStartup now defaults to FALSE; updOnDesktop now defaults to FALSE) to prevent bugged Beecons from freezing hildon-home even after restart
    * Respect: To querty12@talk.maemo.org Many, many, many, many, many thanks for supporting QBW IPC implementation

queen-beecon (0.1.6)

    * New: Simple DBUS implementation for Widget2Widget & System2Widget Inter Process Communication
    * New: Added Widget Instance ID in Settings Dialog Title
    * Changed: Compiled Vs. PR1.2

queen-beecon (0.1.5)

    * Changed: Thanks "qwerty12" disabled automatic capitalization for all text entry fields

queen-beecon (0.1.4)

    * New: Implementation of Widget Instance disabling and minimizing on desktop (click on minimized icon on desktop will wakeup and maximize instance)
    * New: Implementation of image/icon scaling function for all images used (Zoom In/Out from 5% to 200% or Fit to Widget Width/Height)
    * Bugfixing: In Advanced Maintenance Dialog Box several bugfixes for Import/Export commands and instances.
See complete Change Log in the WIKI

Usual WARNINGS apply to extras-devel material

Feel free to experiment with all extended features implemented since 0.1.4 and please report bugs and experiences or feature requests here.

Have fun!

gabby131 2010-05-28 23:54
Re: [Announce] Queen BeeCon Widget: Customizable and flexible monitoring tool.
 
so do my saved instances (commands) will still work if i import it to the 1.9 QBW? right?

gkuenning 2010-05-29 00:32
Re: [Announce] Queen BeeCon Widget: Customizable and flexible monitoring tool.
 
Does this mean that if I upgrade QBW, it's now safe to also upgrade to PR1.2?

No!No!No!Yes! 2010-05-29 06:21
Re: [Announce] Queen BeeCon Widget: Customizable and flexible monitoring tool.
 
Quote:
Originally Posted by gabby131 (Post 687059)
so do my saved instances (commands) will still work if i import it to the 1.9 QBW? right?
I dedicated a major effort in trying to guarantee backward compatibility and transparent upgrade of already created instances.
Only limitation, apart from possible lurking bugs, is the one reported in the change log and relevant to ability for older releases to deal with new font parameters for instances exported by >=0.1.9 QBW.

No!No!No!Yes! 2010-05-29 07:56
Re: [Announce] Queen BeeCon Widget: Customizable and flexible monitoring tool.
 
Quote:
Originally Posted by gkuenning (Post 687105)
Does this mean that if I upgrade QBW, it's now safe to also upgrade to PR1.2?
Hi, you won't be able to upgrade QBW PR1.1.1 with current extras-devel v0.1.9 which gets compiled in PR1.2 SDK framework with upgraded modules; you'll face this issue:
Code:
[sbox-FREMANTLE_X86: ~/workspace/queen-beecon] > dpkg -l queen-beecon

Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name                              Version                          Description
+++-=================================-=================================-==================================================================================
ii  queen-beecon                      0.1.5                            Customizable and flexible widget-based multi-instance monitoring and alerting tool

[sbox-FREMANTLE_X86: ~/workspace/queen-beecon] > dpkg -i queen-beecon_0.1.9.1_i386.deb
(Reading database ... 32547 files and directories currently installed.)
Preparing to replace queen-beecon 0.1.5 (using queen-beecon_0.1.9.1_i386.deb) ...
Unpacking replacement queen-beecon ...
dpkg: dependency problems prevent configuration of queen-beecon:
 queen-beecon depends on libhildon1 (>= 2.2.10); however:
  Version of libhildon1 on system is 2.2.3-1+0m5.
dpkg: error processing queen-beecon (--install):
 dependency problems - leaving unconfigured
Errors were encountered while processing:
 queen-beecon

[sbox-FREMANTLE_X86: ~/workspace/queen-beecon] >
If you want to stick a bit more with PR1.1.1 you can try queen-beecon_0.1.9-PR1.1.1_armel.deb package but I will not be able to provide support and maintain this many versions of the package and I'd rather focus on maintenance on PR1.2

Ciao.

Sash 2010-05-29 10:47
Re: [Announce] Queen BeeCon Widget: Customizable and flexible monitoring tool.
 
I've updated to the 0.1.9 QBW and it looks good. The new font section bit works great with a preview included now.

I'll have to test out the DBUS commands.

gabby131 2010-05-29 23:40
Re: [Announce] Queen BeeCon Widget: Customizable and flexible monitoring tool.
 
Quote:
Originally Posted by No!No!No!Yes! (Post 687409)
I dedicated a major effort in trying to guarantee backward compatibility and transparent upgrade of already created instances.
Only limitation, apart from possible lurking bugs, is the one reported in the change log and relevant to ability for older releases to deal with new font parameters for instances exported by >=0.1.9 QBW.
i have upgraded to 1.9 and everything feels okay, the only change is all the fonts revert back to default (as stated on the description changes), the commands still work as usual havent try sudo commands but i will.

im using the same commands on my overclocking.

thanks for this one!

EDIT: the user interface is very friendly in this upgrade. and easy to customize


All times are GMT. The time now is 23:23.
Page 20 of 140 « First 101819 20 212230 Last »
Show 40 post(s) from this thread on one page

vBulletin® Version 3.8.8