Notes for developers

johnraff · 2016-03-15 08:15:08

I thought it might not hurt to have a thread here to post changes, additions etc which might be of interest to BL developers, to save them from having to watch multiple threads all the time. I'll post changes to packages here, but other devs feel free to post other stuff you think we (and users) should be aware of.

johnraff · 2016-03-15 08:30:53

bunsen-common recent added functions

There is now a new file /usr/lib/bunsen/bunsen-common/yad-includes which lets you simplify the code for simple yad popups in scripts. Some variables yad_common_args and yad_popup_args are set and functions yad_question yad_info and yad_error are available. See the comments in the file for more info. You can include this file the same way as bl-include.cfg, something like:

BL_COMMON_LIBDIR='/usr/lib/bunsen/bunsen-common'
if ! . "$BL_COMMON_LIBDIR/yad-includes" 2> /dev/null; then
    echo $"Error: Failed to locate yad-includes in $BL_COMMON_LIBDIR" >&2
    exit 1
fi

or if you wanted both:

for i in bl-include.cfg yad-includes
do
    if ! . "$BL_COMMON_LIBDIR/$i" 2> /dev/null; then
        echo $"Error: Failed to locate $i in $BL_COMMON_LIBDIR" >&2
        exit 1
    fi
done

There are also some new package handling functions in bl-include.cfg
Nothing all that fancy, but see allInstalled checkVersion and checkOrigin (They are now used in bl-welcome.)

Of course users can source these files the same way in their own scripts.

Horizon_Brave · 2016-03-15 14:20:45

Great idea for a stickied post... Serves as a "running configuration" to the distro. Referencing github for the changelog can get messy at times. Are you going to go back and post changes that you've made in the past?

Last edited by Horizon_Brave (2016-03-15 14:24:34)

damo · 2016-03-15 15:22:35

Horizon_Brave wrote:

... Are you going to go back and post changes that you've made in the past?

I hope not - he won't have time for doing anything else!

nobody · 2016-03-15 16:26:47

So https://bunsenlabs.org/gitlog.html is not good enough?

Horizon_Brave · 2016-03-15 17:17:19

damo wrote:

Horizon_Brave wrote:
... Are you going to go back and post changes that you've made in the past?
I hope not - he won't have time for doing anything else!

Sounds like the life of a true programmer to me!

johnraff · 2016-03-15 23:33:09

twoion wrote:

So https://bunsenlabs.org/gitlog.html is not good enough?

Just had a look at that, and I'd say: no it's too cluttered, being auto-generated the important/usefull stuff is buried in detail.

hhh · 2016-03-16 03:01:45

Sir Attenborough wrote:

We can now destroy, or we can cherish.
The choice... is ours.

johnraff · 2016-03-18 07:42:09

Forgot to mention, in bl-include.cfg there's also now a function declareDependencies which will check any commands you give it, and exit with a message if any are missing from the user's system. If you're already using bl-include.cfg in a script you can add a check for any non-standard commands your script uses, like:

declareDependencies curl xclip

hhh · 2016-03-18 07:47:20

hhh wrote:

Sir Attenborough wrote:
We can now destroy, or we can cherish.
The choice... is ours.

Hmm. A great quote, but not particularly relevant to this thread. Cross-post, I think.

My apologies.

johnraff · 2016-03-19 01:45:23

From here.

twoion wrote:

The BL main website now works completely without JavaScript by way of a <noscript> thumbnail gallery for non-JS-browsers.

johnraff · 2016-04-07 02:45:00

johnraff wrote:

twoion wrote:
So https://bunsenlabs.org/gitlog.html is not good enough?
Just had a look at that, and I'd say: no it's too cluttered, being auto-generated the important/usefull stuff is buried in detail.

I might have sounded a bit too dismissive there: it's also a handy reference, but I was thinking of this thread as a bit more curated...

#1 2016-03-15 08:15:08

Notes for developers

#2 2016-03-15 08:30:53

Re: Notes for developers

#3 2016-03-15 14:20:45

Re: Notes for developers

#4 2016-03-15 15:22:35

Re: Notes for developers

#5 2016-03-15 16:26:47

Re: Notes for developers

#6 2016-03-15 17:17:19

Re: Notes for developers

#7 2016-03-15 23:33:09

Re: Notes for developers

#8 2016-03-16 03:01:45

Re: Notes for developers

#9 2016-03-18 07:42:09

Re: Notes for developers

#10 2016-03-18 07:47:20

Re: Notes for developers

#11 2016-03-19 01:45:23

Re: Notes for developers

#12 2016-04-07 02:45:00

Re: Notes for developers

Board footer