eboxy-users Mailing List for eboxy

Hi,

I am not being able to make hwsensors to work
with eboxy 0.4.1 and eboxy-plugins-0.4.0. Nothing is printed.
No error message.

The previous version, eboxy 0.3.9 and eboxy-plugins-0.1.0,
works fine.

My system runs fedora core 1 with lm_sensors 2.8.7 from at-rpms.

Am I missing something?

Thank you.

/Paulo Roma.

_________________________________________________________________
FREE pop-up blocking with the new MSN Toolbar – get it now! 
http://toolbar.msn.click-url.com/go/onm00200415ave/direct/01/

Hi all,

eboxy 0.4.1 has just been released. This is a minor release with a few small 
features added and bugs fixed. Most notably, joystick support has been added, 
and global user actions are now supported.

Here's the full changelog for 0.4.1:

- Added actionhandler objects for responding to an action without a button
  (including globally)
- Added joystick support
- Now prints an error message to the console if a button has no font or image
- Calling click() now sets focus to the button before pressing it
- Fixed bug: calling the click() method on a button when it is not shown (ie,
  on another page) now works
- Fixed bug: click() method now does nothing if button is disabled
- Fixed bug: fullscreen command line option was being ignored
- Fixed bug: pluginobject was missing from eboxy XML DTD

As usual, you can pick up the latest version from the download page:

http://eboxy.sourceforge.net/download.html

Cheers,
Paul

Hi all,

It gives me great pleasure to announce that after nearly a year in the making, 
eboxy 0.4.0 is out! You can download it at the usual location:

  http://eboxy.sourceforge.net/download.html

For those following the pre-releases, there have been no changes to the code 
since 0.4.0-pre3.

There's also an added bonus: I threw together a "remote control" plugin for 
sending actions to eboxy either locally or remotely over a network (using 
UDP). This is available from the plugins page, along with the new MySQL 
plugin and slightly updated versions of all the other plugins.

Enjoy, and don't hesitate to send me your feedback or discuss it on the forum:

http://eboxy.sourceforge.net/forum

Cheers,
Paul

Hi all,

I am planning on releasing eboxy 0.4.0 this coming weekend. I have just made a 
final pre-release version (0.4.0-pre3), so if you have a chance within the 
next day or two could you please try it out and let me know if you have any 
problems, particularly if they are serious (eg. can't compile). 0.4.0 
contains a lot of changes from 0.3.9 and I want to make this as clean a 
release as possible.

The pre3 source can be downloaded here:

  http://www.bluelightning.org/ebox/files/eboxy/eboxy-0.4.0-pre3.tar.bz2

Extra plugins (optional, unchanged since pre1):

  http://www.bluelightning.org/ebox/files/eboxy/eboxy-plugins-0.4.0-pre1.tar.bz2

Just in case you haven't seen the changelog for 0.4.0 yet, here it is:

- Added an "interface plugin" system that allows swapping in and out
  different GUI libraries without needing to recompile, and split out SDL_gui
  specific code into an interface plugin
- Added integer and boolean literals, variables, integer arithmetic, boolean
  operators, and comparison expressions to scripting language
- Added default XML file ~/.eboxy/system.xml - see documentation
- Added configuration file ~/.eboxy/eboxy.conf - see documentation
- Added execwaitcapture script command to capture output of executed program
- Can now change the background of a page in a script
- Added visible property to all widgets
- Item previous/next actions now go to previous/next widget when on a button
  or a togglebutton
- Default keyboard layout is now more sensible (tab/shift+tab for next/
  previous widget, up/down and left/right are now the same)
- Added system.gotopage()
- Added more user actions
- Added minimum version check attribute to XML
- Added configure option --with-plugin-path to specify the path to load
  plugins from (default is $prefix/lib/eboxy/plugins). Generic plugins are
  now loaded from $pluginpath/generic.
- Removed automatic initialisation of audio - this should now be handled by
  plugins that need it
- Page OnLoad and OnShow events are now waited on before continuing
- System OnLoad event now occurs after initialising system-level plugins
- Fixed bug: uncertain return convention resulted in memory leaks and
  possible crashes with plugins. Note that this means existing third party
  plugin code will need to be fixed to conform with the new convention (see
  documentation)
- Fixed bug: dynamically created pages were not persistent over file changes
- Fixed bug: characters not used by the scripting language (eg. semicolon)
  were printed out if found
- Fixed bug: fatal script parsing error would cause eboxy to exit
- Fixed bug: action property missing on togglebutton
- Many code tidy-ups and internal changes
- Documentation has been expanded, updated, and converted to DocBook format

The extra plugins archive also includes a previously unreleased (prior to 
0.4.0-pre1) mysql database plugin.

One note: I have done some build testing with a Knoppix hdinstall (ie, Debian) 
and the build doesn't seem to work very well - the auto* stuff needs to be 
regenerated, and so does the flex scanner for the scripting language due to 
Debian using a newer version of flex than Gentoo does. I don't think I can 
really fix this for 0.4.0, however I will see about fixing it in future 
releases.

Cheers,
Paul

Hi all,

eboxy 0.4.0-pre1 is available for download from the following location:

http://www.bluelightning.org/ebox/files/eboxy/eboxy-0.4.0-pre1.tar.bz2

This is a pre-release version and may contain bugs. If you have the 
opportunity, please download it and try it out and let me know what you think 
(especially if you have any problems). In addition, updated versions of all 
the extra plugins previously released, plus the long-awaited MySQL database 
plugin, can be downloaded here:

http://www.bluelightning.org/ebox/files/eboxy/eboxy-plugins-0.4.0-pre1.tar.bz2

The following is the current changelog for the 0.4.0-pre1 release (since 
0.3.9):

- Added an "interface plugin" system that allows swapping in and out
  different GUI libraries without needing to recompile, and split out SDL_gui
  specific code into an interface plugin
- Added integer and boolean literals, variables, integer arithmetic, boolean
  operators, and comparison expressions to scripting language
- Added default XML file ~/.eboxy/system.xml - see documentation
- Added configuration file ~/.eboxy/eboxy.conf - see documentation
- Removed automatic initialisation of audio - this should now be handled by
  plugins that need it
- Added configure option --with-plugin-path to specify the path to load
  plugins from (default is $prefix/lib/eboxy/plugins)
- Generic plugins are now loaded from $pluginpath/generic
- Added execwaitcapture script command to capture output of executed program
- Can now change the background of a page in a script
- Added visible property to all widgets
- Item previous/next actions now go to previous/next widget when on a button
  or a togglebutton
- Added system.gotopage()
- Added more user actions
- Added minimum version check attribute to XML
- Fixed bug: uncertain return convention resulted in memory leaks and
  possible crashes with plugins. Note that this means existing third party
  plugin code will need to be fixed to conform with the new convention (see
  documentation)
- Fixed bug: dynamically created pages were not persistent over file changes
- Fixed bug: characters not used by the scripting language (eg. semicolon)
  were printed out if found
- Fixed bug: fatal script parsing error would cause eboxy to exit
- Fixed bug: action property missing on togglebutton
- Many code tidy-ups and internal changes
- Documentation has been expanded, updated, and converted to DocBook format

Cheers,
Paul

Hi all,

I've installed phpBB2 and added a forum for eboxy. I've never been really 
satisfied with the Sourceforge forums and I think it would be nice to get 
some discussions going.

Anyway, if you feel like posting about something eboxy related, head on over:

http://eboxy.sourceforge.net/forum

Cheers,
Paul

Hi all,

eboxy 0.3.9 is out - thanks to Nick Adams who assisted in testing and 
debugging. This is mainly a bugfix release and will hopefully be the last one 
before 0.4.0. The most important fix is that you no longer have to perform 
any special steps when installing SDL_gui - just install it as normal and 
eboxy will build fine.

Here is the list of changes since version 0.3.8:

- Added validchars property to textfield (see release notes)
- Fixed bug: now compiles against SDL_gui library without having to link it
  against libstdc++ manually
- Fixed bug: eboxy sometimes froze if an error occurred during starting
- Fixed bug: plugin load failure caused eboxy to segfault
- Fixed bug: memory leak in filebrowser plugin when using pattern
- Fixed bug: default textfield.maxlength was 10 instead of 255

Cheers,
Paul

Hi,

While working with eboxy, and at the same time hacking it, I found the
plugin system was great but still quite hard to configure. Indeed, the way
it currently works, one must install every plugin in the
/usr/local/lib/eboxy/, which roughly means "system-wide" and "one plugin
name per computer".

Why not just allow the eboxy.xml to provide the location to it? Something
like:

 <plugin module="filebrowser" location="./lib/libfilebrowser.so">
   <pluginobject name="filebrowser">
   </pluginobject>
 </plugin>

It would be really convenient, for the user who can reference a particular
version of the plugin, but also for the developer (who can reference the
plugin they want to test without installing it on the system). Making such
"ref" attribute optional wouldn't break compatibility.

It may also be useful to do the same for the interface plugin: let the
eboxy.xml provide (optionnally) the location of the interface library (so
that you may remove the hardcoded path in
[devel-0-4-0]interfacemanager.cpp ;-))


Rodrigo

Hi !

I am currently toying with eboxy, and have a few questions:

- Is there a reason why the joystick support is disabled ? This is
probably going to be my first input device (until I get an irda receiver)
and this is pretty annoying. The code was almost 100% done, so I just
added a few lines to have something working. Just in case, please find the
diff enclosed hereby (I am using the CVS version, check-outed today). It
uses up and down to navigate through the widgets, and any button performs
"accept".

- I noticed a refresh issue with the "accept" action (called on
performAction(), in main.cpp --with the keyboard or the joystick): the
refresh is performed several times (at least two ;-)), which leads to an
annoying "blink" effect. I use the linux framebuffer as backend
(SDL_VIDEODRIVER="fbcon"). Is this a known issue (it does not appear in
the bug tracker though)?

Rodrigo

On Mon, 24 Nov 2003 10:04, Pierre DOUCET wrote:
> I have a bug with my eboxy script: When i use mouse to click on buttons,
> it's ok, eboxy works. But if i use keyboard or Lirc, eboxy crash (Fatal
> signal: Segmentation Fault (SDL Parachute Deployed))  when i use "enter"
> event...

Oops, that's definitely a bug - found and fixed. Thanks for reporting it! A 
patch that fixes the bug is attached. (To apply it, cd into the eboxy source 
directory then run patch < simulateclick.segfault.patch, then run make and 
make install again). This is also fixed in CVS.

BTW, I like the skin you have built. I was especially impressed by the way it 
downloads and displays the weather report. Very cool!

Cheers,
Paul

PS It's usually not considered good manners to send >100k attachments to a 
public mailing list without prior warning. I didn't notice this when I went 
to review the submission - what I should have done was to redirect it to my 
own mailbox rather than allowing it through to the list. My apologies to any 
subscribers who were inconvenienced by the size of the attachment.

hello,

I have a bug with my eboxy script: When i use mouse to click on buttons, it's 
ok, eboxy works. But if i use keyboard or Lirc, eboxy crash (Fatal signal: 
Segmentation Fault (SDL Parachute Deployed))  when i use "enter" event...

Please help me, my divxbox is waiting ;-)

A+

Pierre

Hi all,

eboxy now has a new website. It's a lot more spread out than the old single 
page, and there's a bit more information. Also, the plugins are now listed 
and available for download individually. Check it out:

http://eboxy.sourceforge.net

Cheers,
Paul

Hi,

I have written a wrapper plugin around the xine library for playing movies 
inside eboxy. Currently it's available in CVS only as it's not quite 
finished. Feel free to check it out and let me know how you get on with it.

To check out the latest plugins from CVS, type:

cvs -z3 -d:pserver:ano...@cv...:/cvsroot/eboxy co 
eboxy-plugins

Cheers,
Paul

Hi all,

eboxy 0.3.7 is out. The changes are as follows:

- Improved "dynamic" property, method and event system (mostly internal, but
  has enabled other features in this release, and exposed bugs that have been
  fixed)
- Plugins can now create and add widgets to the page at runtime, as well as
  enumerate all pages, widgets on a page, and properties, methods and events
  of an object
- fontsize property now available at runtime on all font-using widgets
- Added width and height to templates
- Added property system.version to report eboxy version
- Can now refer to widgets on other pages in scripts
- Plugins can now execute arbitrary blocks of script code
- Added alternative syntax to execwait script command to get back return code
- Fixed bug: can now refer to pages by name in scripts
- Fixed bug: setting button font colours to "" now causes them to be ignored
- Fixed bug: colour property values are now returned correctly
- Fixed bug: fragments of reserved words and methods/properties were
  erroneously disallowed as names
- Fixed bug: label.textalign was not working correctly
- Fixed bug: setting button caption to "" caused a crash on exit
- Fixed bug: buttons with no caption initially could never have a caption
- Fixed bug: default keyboard key bindings didn't work on first run
- Fixed bug: eboxy still ran with errors in key config file
- Fixed bug: listbox did not respect bordery when drawing last visible item
- Internal type names have been changed (again) to lower case, to match XML
- Massive code tidy-up

There is also a new set of graphics available along with a new version of the 
eBox skin, and the plugins previously only available from CVS can now be 
downloaded (still some work to be done, but they can be used). You can see 
the new graphics in two new screenshots on the website. Check out the 
"testbench" plugin and XML file to see the new dynamic features in action.

As always, eboxy is available from its website at:
http://www.bluelightning.org/ebox/eboxy

Enjoy :)

Cheers,
Paul

Hi all,

I have been hard at work lately on eboxy. It is now possible, at last, for 
plugins to create widgets at runtime. This, coupled with a new dynamic 
internal property, method and event system (as well as a massive code 
tidy-up) has enabled me to add a few features and exposed a number of bugs 
that have now been fixed.

Here's a list of the things changed in the current CVS version that may 
interest some people:

- Added plugin API functions to create widgets and add widgets to pages at 
runtime
- fontsize property now available at runtime on all font-using widgets
- Added width and height to templates
- Added property system.version to report eboxy version
- Fixed bug: can now refer to pages by name in scripts
- Fixed bug: setting button font colours to "" now causes them to be ignored
- Fixed bug: colour property values are now returned correctly
- Fixed bug: fragments of reserved words and methods/properties were
  erroneously disallowed as names

Please feel free to check out the latest code from CVS 
(http://sourceforge.net/cvs/?group_id=60199) and report any bugs you find.

Cheers,
Paul

Hi all,

I have updated the current download of eboxy 0.3.6. It seems that in the haste 
to release the new version I neglected to update the internal version 
numbers, so plugins will see 0.3.6 as 0.3.5. The version I have just uploaded 
fixes this (and only this - no other changes have been made since the 
original 0.3.6, so most people probably won't be worried about this). Phew!

If you want to get the latest version of eboxy, download it here:
http://www.bluelightning.org/ebox/eboxy/

I have also been writing a status document over the past few months, and it is 
now ready to be viewed. It details some of the shortcomings of eboxy in its 
current form and what might need to be done in order to move forward. If you 
have an interest in eboxy's development I strongly suggest you read it and 
make comments. The document is available from:
http://www.bluelightning.org/ebox/eboxy/eboxy-status-2003-04.html

Cheers,
Paul

Hi all,

The long overdue eboxy 0.3.6 has just been released. It fixes quite a number 
of bugs and adds a few minor features, including several items that I know 
people have asked for. Here's the changelog:

0.3.6 (22 April 2003):
- Added togglebutton widget
- Added setfocus method to all widgets
- Added itemheight, itemborderx, itembordery, selitembackgroundfocus
  properties to listbox
- Added sorting to file browser plugin (thanks to Kimble Young)
- Buttons can now be disabled (added enabled property)
- Added fontfocusedcolor, fontdisabledcolor, fontpressedcolor properties to
  buttons
- Added text digit input (use number keys on a remote to enter alphanumeric
  text)
- Added --nokeyrepeat command line option to disable keyboard key repeat
- Added scriptable method system.performaction() for performing actions from
  scripts
- Key bindings can now include modifiers (eg. alt+q, ctrl+enter etc)
- Fixed bug: filebrowser broke if invalid path specified as root
- Fixed bug: changing interval of a timer while enabled didn't take effect
  until the timer was restarted
- Fixed bug: no error was reported if you tried to call a nonexistent method
  on an object
- Fixed bug: some attributes were missing from listbox templates
- Fixed bug: certain versions of autoconf failed to configure eboxy
- Fixed bug: large file support now enabled at build time (fixes files 2GB
  or larger not showing up in filebrowser)
- Fixed bug: segfault on exit after reload of a page with plugins loaded
- Fixed bug: segfault with no widgets
- Fixed bug: buttons with only an image attribute specified now do not blank
  out when focused or pressed
- Fixed bug: segfault on pluginobject with missing file and attached events

If you have time, please download the new version, try it out and let me know 
how you get on.

Cheers,
Paul Eggleton

Hi all

Over the last few weeks the following changes have made it into CVS. Test=
ing=20
would be appreciated :)

- Added toggle button widgets, or checkboxes if you prefer. These are fai=
rly=20
basic right now but should still be useful.
- A fix to the build process that prevented eboxy from configuring proper=
ly on=20
Gentoo 1.4rc3 and probably other systems (autoconf prints out some=20
meaningless error).
- Large file support. I'm not sure how many people this affects, but one=20
person complained about not being able to see files 2gb+ in size in the f=
ile=20
browser. Should be fixed.
- Added system.performaction()=20
- A few other bugfixes.

I need to get this fully tested so I can do another release. I am still i=
n the=20
process of adding a couple of features people have asked for, and if you'=
ve=20
got something you'd like to see added or fixed, speak up now :)

Cheers,
Paul Eggleton

On Tuesday, February 04, 2003 4:50 PM NZST, Kimble Young wrote:
> Firstly. I don't mind receiving CVS notifications.

OK, I'll keep that in mind.

> Sourceforge doesn't really do a good job of reporting when something
> has been committed (I think it's said 577 commits ever since I first
> came across eboxy :)


Yeah, I think the same applies to everything on the main page. Personally I
think Sourceforge is falling behind in general and it's time they updated
their software. In any case my CVS comments aren't always very descriptive
and even if they were it might be hard to decipher what's actually been
added/changed from a user's perspective.

> The methods work fine for me so I'm curious as to why they were
> commented out. Is there something I should know?  If not, I would find
> the methods very useful and I think so would others.  My thoughts on
> the widget are provide as many functions as possible without, of
> course, introducing redundancies.

There was a reason for not putting these in, and I think that was because it
wasn't fully implemented and I wasn't really sure how far to go, and I was
hoping to be able to make a more generic method that would work with other
types of widgets. Being able to run an action from a script might be a
better way to do it. I'll have a think about it tonight.

> One feature I was hoping for was a text and value system, where the
> user never sees the value but it can be used for things like a full
> pathname where only a filename is shown to the user or for one
> applied use I wanted which was to show info from an MP3 ID3 tag to
> the user but have the value as the real filename. Of course value
> would be totally optional.

Yeah, you're not the only person to ask for this :)

> I'm quite happy to have a crack at this if Paul thinks it fits into
> the eboxy system and hasn't done it already.

I'll see about putting it in this evening.

Cheers,
Paul

Good Afternoon,

Firstly. I don't mind receiving CVS notifications.

Sourceforge doesn't really do a good job of reporting when something has 
been committed (I think it's said 577 commits ever since I first came 
across eboxy :)

Now down to my main point.

I was browsing through the sources for the listbox widget (specifically 
listboxwidget.cpp) looking for a way of being able to script selecting 
different items in a listbox and came across some commented out code to 
do exactly this.  It didn't compile without removing a call to a 
function that doesn't exist in that class file and doesn't even seem to 
be needed.

The methods work fine for me so I'm curious as to why they were 
commented out. Is there something I should know?  If not, I would find 
the methods very useful and I think so would others.  My thoughts on the 
widget are provide as many functions as possible without, of course, 
introducing redundancies.

Diff included at bottom of email, it's probably mangled. I can upload it 
to  sourceforge if need be.



I'd also like to see the listbox widget extend a little more in 
functionality if possible.

One feature I was hoping for was a text and value system, where the user 
never sees the value but it can be used for things like a full pathname 
where only a filename is shown to the user or for one applied use I 
wanted which was to show info from an MP3 ID3 tag to the user but have 
the value as the real filename. Of course value would be totally optional.

I'm quite happy to have a crack at this if Paul thinks it fits into the 
eboxy system and hasn't done it already.


Index: listboxwidget.cpp
===================================================================
RCS file: /cvsroot/eboxy/eboxy/eboxy/listboxwidget.cpp,v
retrieving revision 1.13
diff -r1.13 listboxwidget.cpp
468c468
<   if(strstr("additem|removeitem|removelastitem|clear", method))
---
 > 
if(strstr("additem|removeitem|removelastitem|clear|selectnext|selectprev|sel
ectnextpage|selectprevpage", method))
502c502
< /*  else if(!strcasecmp(method, "selectnext")) {
---
 >   else if(!strcasecmp(method, "selectnext")) {
515c515
<       SelectNext(1);
---
 >       SelectNextPage();
520,521c520,521
<       SelectPrevious(GetVisibleItems());
<   }*/
---
 >       SelectPreviousPage();
 >   }

Hi all,

Tonight I committed two changes to CVS, for those who are interested:

1. File browser sorting - this patch from Kimble Young is now integrated and
appears to work fine. I have modified it slightly so that case is not
observed in sorting. Thanks Kimble!

2. Number-pad input. This allows you to use the number keys on a
remote/keyboard to enter in alphanumeric text, as you can on newer mobile
phones. To use this feature you need to bind the keys/buttons to the
appropriate actions (textinput_digitn, where n is a number from 0 to 9). See
the actions section in the user manual for more info. This feature still
needs a bit of work (case switching, more symbol characters, international
characters). Suggestions welcome.

Cheers,
Paul

PS since I tend to do my changes in the evening (well, it's evening here in
NZ) and at weekends, are people interested in me sending messages to the
list as each change makes it into CVS? Or is that too much noise? Thanks.

On Thursday, January 30, 2003 12:37 PM NZST, Kimble Young wrote:
> I was trying to stat files without their full path.  This was working
> for me, for half the files in the directory and led to a lot of
> confusion.

Ah yes, I fell into exactly the same trap while working on the filebrowser.

> There's a new revision of the patch on the sourceforge site which, I
> say with all confidence, should fix my old patch.  Just remember not
> to patch the patch, apply it against the CVS copy.  Please test it and
> provide feedback, bugs etc.

Will do.

> Paul, sorry I couldn't apply the changes you wanted, hope it's not too
> much hassle for you to add them again.

No problem. What I'll probably do is just compare the patches and see what's
necessary. Shouldn't be too hard to figure out :)

Cheers,
Paul

After extensive debugging of S_ISDIR and much swearing at the computer 
I've come to the realisation that it was my fault and not the computer 
and Linux conspiring against me.

I was trying to stat files without their full path.  This was working 
for me, for half the files in the directory and led to a lot of confusion.

There's a new revision of the patch on the sourceforge site which, I say 
with all confidence, should fix my old patch.  Just remember not to 
patch the patch, apply it against the CVS copy.  Please test it and 
provide feedback, bugs etc.


Paul, sorry I couldn't apply the changes you wanted, hope it's not too 
much hassle for you to add them again.

On Thursday, January 23, 2003 8:34 PM NZST, Kimble Young wrote:
> I've added a patch for the filebrowser plugin.
> It adds two new properties to the filebrowser sort and sortdirection.
> These should allow you to sort by name, size, directory, ctime,mtime
> and atime, additionally you can set the sort direction forward or
> reverse.
>
> Just my little contribution to what is shaping up to be a great
> project.

Much appreciated. I will try merging your patch in tonight, and if all goes
well it should be in CVS very soon :)

Cheers
Paul Eggleton

Hi all,


I've added a patch for the filebrowser plugin.

It adds two new properties to the filebrowser sort and sortdirection.
These should allow you to sort by name, size, directory, ctime,mtime and
atime, additionally you can set the sort direction forward or reverse.

Just my little contribution to what is shaping up to be a great project.



Kimble Young.