notion-devel — Development discussion about the notion window manager

Re: [Notion-devel] Notion and Firefox fullscreen (Bug 3429909)

[Arnout E. <no...@bz...>]

Many thanks for looking into this, I think we're really close to a proper 
solution here.

On Wed, Jan 18, 2012 at 12:40:17AM +0100, Philipp Hartwig wrote:
> I'm not comfortable with the sf.net tracker so please allow me to make this 
> rather long comment on bug 3429909 [1] via mail. After spending many hours 
> with Notion and Firefox in gdb I now understand what is going on. It all comes 
> down to the following behavior of Firefox:
> 
> Assume that
> a) Firefox is in its internal normal mode and
> b) _NET_WM_STATE_FULLSCREEN is set for the Firefox window.
> Now call first XUnmapWindow and then XMapWindow on the Firefox window.
> 
> Result: Firefox switches to its internal fullscreen mode and requests to be 
> put into fullscreen mode via a _NET_WM_STATE client message. Let me call this 
> behavior (B) for reference below. I don't understand how it is a reasonable 
> behavior.
> 
> You can easily reproduce (B) via the following function in ioncore/netwm.c 
> which can be bound to a key and then applied to Firefox:
> 
> --- SNIP ---
> EXTL_EXPORT_AS(WClientWin, ffdbg)
> void firefox_debug(WClientWin *cwin)
> {
>     CARD32 data[1];
>     int n=0;
>     
> 	data[n++]=atom_net_wm_state_fullscreen;
>     XChangeProperty(ioncore_g.dpy, cwin->win, atom_net_wm_state, 
>                     XA_ATOM, 32, PropModeReplace, (uchar*)data, n);
>     XSelectInput(ioncore_g.dpy, cwin->win,
> 			cwin->event_mask&~(StructureNotifyMask|EnterWindowMask));
>     XUnmapWindow(ioncore_g.dpy, cwin->win);
> 	XMapWindow(ioncore_g.dpy, cwin->win);
>     XSelectInput(ioncore_g.dpy, cwin->win, cwin->event_mask);
> }
> --- SNAP ---
> 
> How does this explain the behavior of Firefox that we are seeing with Notion's 
> and Firefox's fullscreen mode? First let me note that according to its man 
> page, XReparentWindow involves an XUnmapWindow followed by a XMapWindow so it 
> will trigger (B) if conditions a) and b) are satisfied.
> 
> Let cwin be a Firefox window. I write cwin_n and cwin_f to denote wheter cwin 
> is in its internal normal or fullscreen mode, respectively.
> 
> 1a)
> Start with an ordinary cwin_n and call Notion's fullscreen toggle function 
> region_set_fullscreen.
> We soon land in
>     clientwin.c:clientwin_fitrep
> Here we have
>     do_reparent_clientwin => XReparentWindow(.., cwin)
> But note that do_reparent_clientwin is called before netwm_update_state(cwin)
> so that condition b) is not satisfied and (B) is not triggered. No other 
> XUnmapWindow(..., cwin) is called in the course of region_set_fullscreen.
> 
> Conclusion (and observation): We end up with cwin_n in Notion's fullscreen 
> mode (and with _NET_WM_STATE_FULLSCREEN set!).
> 
> 1b) Again call Notion's fullscreen toggle function. As above we get to
>     XReparentWindow(.., cwin)
> and as netwm_update_state(cwin) was not yet called, condition b) is satisfied. 
> So by (B) cwin_n becomes cwin_f and requests to be fullscreened, which we do.
> 
> Conclusion (and observation): We end up with cwin_f in Notion's fullscreen 
> mode.
> 
> 1c) Again call region_set_fullscreen. This time (B) is not triggered because 
> condition a) is not satisfied.
> 
> Conclusion (and observation): We end up with cwin_f in Notion's normal mode.
> 
> [Side note: Another instance of (B) can be observed if, at the end of 1a), you 
> switch away from and then back to the fullscreened cwin_n. Switching away calls 
> an XUnmapWindow, switching back to it calls a XMapWindow and consequently
> cwin_n will become cwin_f.]
> 
> 2a)
> Start with an ordinary cwin_n and press F11. cwin_n changes itself to cwin_f 
> and requests to be fullscreened which we do. Here no surprises happen. We end 
> up with cwin_f in Notion's fullscreen mode with _NET_WM_STATE_FULLSCREEN set.
> 
> 2b) Press F11. cwin_f changes itself to cwin_n and requests to be put into 
> normal mode which we do. But as in 1b) above we call XReparentWindow before we 
> remove _NET_WM_STATE_FULLSCREEN. So (B) is triggered and cwin requests to be 
> fullscreened again. We end up with the situation we started with.
> 
> This concludes my analysis. If we believe that all our problems come from 
> (B) it is not surprising anymore that for example dwm[2] does not suffer from 
> them as it never calls XUnmapWindow. 

Very detailed and convincing.

> And most other window managers seem to use XCB instead of Xlib which also 
> doesn't seem to suffer from (B).

I don't know how XCB handles this

> Isn't (B) a clear bug in Firefox? 

I'm not so sure. _NET_WM_STATE_FULLSCREEN *is* a valid way to tell the 
application you want it to be fullscreened - I guess there should never be
a 'stable' situation where _NET_WM_STATE_FULLSCREEN is on but Firefox is still
in its 'normal' mode. Apparently Firefox, when mapped, notices this 'unstable'
situation and 'fixes' is by going into fullscreen mode, including a (arguably
somewhat superfluous) _NET_WM_STATE client message.

> Also the analysis doesn't seem to indicate any other obvious solution, does 
> it? My main goal was to understand what is going on and why other wm's don't
> have the same problem.

Firefox apparently inspects the _NET_WM_STATE_FULLSCREEN field when it is 
mapped. That does not appear to be fundamentally wrong to me, so perhaps we 
should make sure we update it before mapping the window.

I experimented with this a bit, and noticed netwm_update_state uses the 
WRegion parent to determine whether the window is currently fullscreened.
Indeed, when I update ioncore/clientwin.c to call netwm_update_state after
region_set_parent and before do_reparent_clientwin, the behavior is almost
as intended:

1a) Start with ordinary cwin_n and call Notion's fullscreen toggle function:
the window is fullscreened and Firefox correctly switches to its fullscreen UI

1b) Start with fullscreen cwin_f and call Notion's fullscreen toggle function:
the window returns to normal mode, but Firefox remains in fullscreen UI

2a) Start with ordinary cwin_n and call Firefox's fullscreen toggle function:
the window is fullscreened and Firefox correctly switches to its fullscreen UI

2b) Start with fullscreen cwin_f and call Firefox's fullscreen toggle function:
the window returns to normal mode and Firefox correctly switches to its 
fullscreen UI

The only remaining problematic case is '1b'. This is fairly easily worked 
around manually by triggering Firefox's fullscreen toggle. It's kind of 
strange that Firefox does switch to fullscreen UI based on 
_NET_WM_STATE_FULLSCREEN but not back to normal UI - perhaps this is in order
to better support windowmanagers that never ever set _NET_WM_STATE_FULLSCREEN?

For now I'm proposing the following solution:

diff --git a/ioncore/clientwin.c b/ioncore/clientwin.c
index 6272a14..b8d7ae4 100644
--- a/ioncore/clientwin.c
+++ b/ioncore/clientwin.c
@@ -982,14 +982,24 @@ static bool clientwin_fitrep(WClientWin *cwin, WWindow *np,
     
     if(np!=NULL){
         region_unset_parent((WRegion*)cwin);
-        do_reparent_clientwin(cwin, np->win, geom.x, geom.y);
+
+        /**
+         * update netwm properties before mapping, because some apps check the
+         * netwm state directly when mapped.
+         *
+         * also, update netwm properties after setting the parent, because 
+         * the new state of _NET_WM_STATE_FULLSCREEN is determined based on
+         * the parent of the cwin.
+         */
         region_set_parent((WRegion*)cwin, np);
+        netwm_update_state(cwin);
+
+        do_reparent_clientwin(cwin, np->win, geom.x, geom.y);
         sendconfig_clientwin(cwin);
         
         if(!REGION_IS_FULLSCREEN(cwin))
             cwin->flags&=~CLIENTWIN_FS_RQ;
 
-        netwm_update_state(cwin);
     }
     
As suggested by ebik, we could also do it like this:

diff --git a/ioncore/clientwin.c b/ioncore/clientwin.c
index 6272a14..f9cb150 100644
--- a/ioncore/clientwin.c
+++ b/ioncore/clientwin.c
@@ -982,14 +982,26 @@ static bool clientwin_fitrep(WClientWin *cwin, WWindow *np,
     
     if(np!=NULL){
         region_unset_parent((WRegion*)cwin);
-        do_reparent_clientwin(cwin, np->win, geom.x, geom.y);
+
+        XUnmapWindow(ioncore_g.dpy, np->win);
+        /**
+         * update netwm properties before mapping, because some apps check the
+         * netwm state directly when mapped.
+         *
+         * also, update netwm properties after setting the parent, because 
+         * the new state of _NET_WM_STATE_FULLSCREEN is determined based on
+         * the parent of the cwin.
+         */
         region_set_parent((WRegion*)cwin, np);
+        netwm_update_state(cwin);
+
+        do_reparent_clientwin(cwin, np->win, geom.x, geom.y);
+        XMapWindow(ioncore_g.dpy, np->win);
         sendconfig_clientwin(cwin);
         
         if(!REGION_IS_FULLSCREEN(cwin))
             cwin->flags&=~CLIENTWIN_FS_RQ;
 
-        netwm_update_state(cwin);
     }

Indeed arguably this is neater because this can never cause trouble with 
applications that listen to _NET_WM_STATE_FULLSCREEN state changes interfering
with our reparenting operations, but this seems unlikely anyway and the former
code seems a bit neater.

If no-one objects I'll push the former solution. I have tested it works with
chromium, too :).


Kind regards,

Arnout

Re: [Notion-devel] Notion and Firefox fullscreen (Bug 3429909)

[ebik <eb...@uc...>]

Hi,

Maybe the most 'correct' behavior is unmap, set/reset _NET_WM_*
property, and then map. So any mapped window will have proper value of
the property. There may be always some application, that takes action
on change of the property and assumes that it is mapped, but that is
a bug without any doubts. Is it possible to call XUnMapWindow first,
then change the property and then call XReparentWindow ? Will it help?

On Wed, 18 Jan 2012 00:40:17 +0100
Philipp Hartwig <ph...@ph...> wrote:

> I'm not comfortable with the sf.net tracker so please allow me to
> make this rather long comment on bug 3429909 [1] via mail. After
> spending many hours with Notion and Firefox in gdb I now understand
> what is going on. It all comes down to the following behavior of
> Firefox:
> 
> Assume that
> a) Firefox is in its internal normal mode and
> b) _NET_WM_STATE_FULLSCREEN is set for the Firefox window.
> Now call first XUnmapWindow and then XMapWindow on the Firefox window.
> 
> Result: Firefox switches to its internal fullscreen mode and requests
> to be put into fullscreen mode via a _NET_WM_STATE client message.
> Let me call this behavior (B) for reference below. I don't understand
> how it is a reasonable behavior.
> 
> You can easily reproduce (B) via the following function in
> ioncore/netwm.c which can be bound to a key and then applied to
> Firefox:
> 
> --- SNIP ---
> EXTL_EXPORT_AS(WClientWin, ffdbg)
> void firefox_debug(WClientWin *cwin)
> {
>     CARD32 data[1];
>     int n=0;
>     
> 	data[n++]=atom_net_wm_state_fullscreen;
>     XChangeProperty(ioncore_g.dpy, cwin->win, atom_net_wm_state, 
>                     XA_ATOM, 32, PropModeReplace, (uchar*)data, n);
>     XSelectInput(ioncore_g.dpy, cwin->win,
> 			cwin->event_mask&~(StructureNotifyMask|EnterWindowMask));
>     XUnmapWindow(ioncore_g.dpy, cwin->win);
> 	XMapWindow(ioncore_g.dpy, cwin->win);
>     XSelectInput(ioncore_g.dpy, cwin->win, cwin->event_mask);
> }
> --- SNAP ---
> 
> How does this explain the behavior of Firefox that we are seeing with
> Notion's and Firefox's fullscreen mode? First let me note that
> according to its man page, XReparentWindow involves an XUnmapWindow
> followed by a XMapWindow so it will trigger (B) if conditions a) and
> b) are satisfied.
> 
> Let cwin be a Firefox window. I write cwin_n and cwin_f to denote
> wheter cwin is in its internal normal or fullscreen mode,
> respectively.
> 
> 1a)
> Start with an ordinary cwin_n and call Notion's fullscreen toggle
> function region_set_fullscreen.
> We soon land in
>     clientwin.c:clientwin_fitrep
> Here we have
>     do_reparent_clientwin => XReparentWindow(.., cwin)
> But note that do_reparent_clientwin is called before
> netwm_update_state(cwin) so that condition b) is not satisfied and
> (B) is not triggered. No other XUnmapWindow(..., cwin) is called in
> the course of region_set_fullscreen.
> 
> Conclusion (and observation): We end up with cwin_n in Notion's
> fullscreen mode (and with _NET_WM_STATE_FULLSCREEN set!).
> 
> 1b) Again call Notion's fullscreen toggle function. As above we get to
>     XReparentWindow(.., cwin)
> and as netwm_update_state(cwin) was not yet called, condition b) is
> satisfied. So by (B) cwin_n becomes cwin_f and requests to be
> fullscreened, which we do.
> 
> Conclusion (and observation): We end up with cwin_f in Notion's
> fullscreen mode.
> 
> 1c) Again call region_set_fullscreen. This time (B) is not triggered
> because condition a) is not satisfied.
> 
> Conclusion (and observation): We end up with cwin_f in Notion's
> normal mode.
> 
> [Side note: Another instance of (B) can be observed if, at the end of
> 1a), you switch away from and then back to the fullscreened cwin_n.
> Switching away calls an XUnmapWindow, switching back to it calls a
> XMapWindow and consequently cwin_n will become cwin_f.]
> 
> 2a)
> Start with an ordinary cwin_n and press F11. cwin_n changes itself to
> cwin_f and requests to be fullscreened which we do. Here no surprises
> happen. We end up with cwin_f in Notion's fullscreen mode with
> _NET_WM_STATE_FULLSCREEN set.
> 
> 2b) Press F11. cwin_f changes itself to cwin_n and requests to be put
> into normal mode which we do. But as in 1b) above we call
> XReparentWindow before we remove _NET_WM_STATE_FULLSCREEN. So (B) is
> triggered and cwin requests to be fullscreened again. We end up with
> the situation we started with.
> 
> This concludes my analysis. If we believe that all our problems come
> from (B) it is not surprising anymore that for example dwm[2] does
> not suffer from them as it never calls XUnmapWindow. And most other
> window managers seem to use XCB instead of Xlib which also doesn't
> seem to suffer from (B).
> 
> Isn't (B) a clear bug in Firefox? If so I think that the winprop
> kludge is the way go to. Also the analysis doesn't seem to indicate
> any other obvious solution, does it? My main goal was to understand
> what is going on and why other wm's don't have the same problem.
> 
> Any comments are very welcome. Have I overlooked something?
> 
> Regards,
> Philipp
> 
> [1]
> http://sourceforge.net/tracker/?func=detail&aid=3429909&group_id=314802&atid=1324528
> [2] http://dwm.suckless.org/
> 
> ------------------------------------------------------------------------------
> Keep Your Developer Skills Current with LearnDevNow!
> The most comprehensive online learning library for Microsoft
> developers is just $99.99! Visual Studio, SharePoint, SQL - plus
> HTML5, CSS3, MVC3, Metro Style Apps, more. Free future releases when
> you subscribe now! http://p.sf.net/sfu/learndevnow-d2d
> _______________________________________________
> Notion-devel mailing list
> Not...@li...
> https://lists.sourceforge.net/lists/listinfo/notion-devel
> 



-- 
                                 Tomáš 'ebík' Ebenlendr
                                 Centrum Holdings s.r.o.
                                 PF 2012.04761630996

[Notion-devel] Notion and Firefox fullscreen (Bug 3429909)

[Philipp H. <ph...@ph...>]

I'm not comfortable with the sf.net tracker so please allow me to make this 
rather long comment on bug 3429909 [1] via mail. After spending many hours 
with Notion and Firefox in gdb I now understand what is going on. It all comes 
down to the following behavior of Firefox:

Assume that
a) Firefox is in its internal normal mode and
b) _NET_WM_STATE_FULLSCREEN is set for the Firefox window.
Now call first XUnmapWindow and then XMapWindow on the Firefox window.

Result: Firefox switches to its internal fullscreen mode and requests to be 
put into fullscreen mode via a _NET_WM_STATE client message. Let me call this 
behavior (B) for reference below. I don't understand how it is a reasonable 
behavior.

You can easily reproduce (B) via the following function in ioncore/netwm.c 
which can be bound to a key and then applied to Firefox:

--- SNIP ---
EXTL_EXPORT_AS(WClientWin, ffdbg)
void firefox_debug(WClientWin *cwin)
{
    CARD32 data[1];
    int n=0;
    
	data[n++]=atom_net_wm_state_fullscreen;
    XChangeProperty(ioncore_g.dpy, cwin->win, atom_net_wm_state, 
                    XA_ATOM, 32, PropModeReplace, (uchar*)data, n);
    XSelectInput(ioncore_g.dpy, cwin->win,
			cwin->event_mask&~(StructureNotifyMask|EnterWindowMask));
    XUnmapWindow(ioncore_g.dpy, cwin->win);
	XMapWindow(ioncore_g.dpy, cwin->win);
    XSelectInput(ioncore_g.dpy, cwin->win, cwin->event_mask);
}
--- SNAP ---

How does this explain the behavior of Firefox that we are seeing with Notion's 
and Firefox's fullscreen mode? First let me note that according to its man 
page, XReparentWindow involves an XUnmapWindow followed by a XMapWindow so it 
will trigger (B) if conditions a) and b) are satisfied.

Let cwin be a Firefox window. I write cwin_n and cwin_f to denote wheter cwin 
is in its internal normal or fullscreen mode, respectively.

1a)
Start with an ordinary cwin_n and call Notion's fullscreen toggle function 
region_set_fullscreen.
We soon land in
    clientwin.c:clientwin_fitrep
Here we have
    do_reparent_clientwin => XReparentWindow(.., cwin)
But note that do_reparent_clientwin is called before netwm_update_state(cwin)
so that condition b) is not satisfied and (B) is not triggered. No other 
XUnmapWindow(..., cwin) is called in the course of region_set_fullscreen.

Conclusion (and observation): We end up with cwin_n in Notion's fullscreen 
mode (and with _NET_WM_STATE_FULLSCREEN set!).

1b) Again call Notion's fullscreen toggle function. As above we get to
    XReparentWindow(.., cwin)
and as netwm_update_state(cwin) was not yet called, condition b) is satisfied. 
So by (B) cwin_n becomes cwin_f and requests to be fullscreened, which we do.

Conclusion (and observation): We end up with cwin_f in Notion's fullscreen 
mode.

1c) Again call region_set_fullscreen. This time (B) is not triggered because 
condition a) is not satisfied.

Conclusion (and observation): We end up with cwin_f in Notion's normal mode.

[Side note: Another instance of (B) can be observed if, at the end of 1a), you 
switch away from and then back to the fullscreened cwin_n. Switching away calls 
an XUnmapWindow, switching back to it calls a XMapWindow and consequently
cwin_n will become cwin_f.]

2a)
Start with an ordinary cwin_n and press F11. cwin_n changes itself to cwin_f 
and requests to be fullscreened which we do. Here no surprises happen. We end 
up with cwin_f in Notion's fullscreen mode with _NET_WM_STATE_FULLSCREEN set.

2b) Press F11. cwin_f changes itself to cwin_n and requests to be put into 
normal mode which we do. But as in 1b) above we call XReparentWindow before we 
remove _NET_WM_STATE_FULLSCREEN. So (B) is triggered and cwin requests to be 
fullscreened again. We end up with the situation we started with.

This concludes my analysis. If we believe that all our problems come from 
(B) it is not surprising anymore that for example dwm[2] does not suffer from 
them as it never calls XUnmapWindow. And most other window managers seem to 
use XCB instead of Xlib which also doesn't seem to suffer from (B).

Isn't (B) a clear bug in Firefox? If so I think that the winprop kludge is the 
way go to. Also the analysis doesn't seem to indicate any other obvious 
solution, does it? My main goal was to understand what is going on and why 
other wm's don't have the same problem.

Any comments are very welcome. Have I overlooked something?

Regards,
Philipp

[1] http://sourceforge.net/tracker/?func=detail&aid=3429909&group_id=314802&atid=1324528 
[2] http://dwm.suckless.org/

Re: [Notion-devel] Debian packaging

[Arnout E. <no...@bz...>]

On Tue, Nov 15, 2011 at 01:55:35PM +0100, Philipp Hartwig wrote:
> > If you have amd64:
> > 
> >   https://sourceforge.net/projects/notion/files/
> 
> Thanks, I'm using this right now and it seems to work well. 

Good to hear

> lintian still doesn't seem to like the version number

That should only be a problem the first upload: it's comparing the version
number of the previous 'ion3' package to the version number of this 'notion'
package, which are in different formats.

> wasn't that your motivation for switching from 3-.. to 3+..?

http://www.debian.org/doc/manuals/maint-guide/first.en.html#namever specifies
upstream versions should 'consist only of alphanumerics (0-9A-Za-z), plus (+),
tildes (~), and periods (.)' and start with a digit. Discussed it on 
#debian-mentors, this seems to be the sane way to do it.

> I've requested to be able to participate in the collab-maint repository 
> using [1] but I never heard back from that. But I see you have already 
> merged the patch so it doesn't really matter.

Hmm I don't think I can add you, guess only admins can.


Arnout

Re: [Notion-devel] Debian packaging

[Philipp H. <phi...@un...>]

> If you have amd64:
> 
>   https://sourceforge.net/projects/notion/files/

Thanks, I'm using this right now and it seems to work well. lintian still 
doesn't seem to like the version number, wasn't that your motivation for
switching from 3-.. to 3+..?

I've requested to be able to participate in the collab-maint repository 
using [1] but I never heard back from that. But I see you have already 
merged the patch so it doesn't really matter.

Regards,
Philipp

https://alioth.debian.org/project/request.php?group_id=30755 

Re: [Notion-devel] Debian packaging

[Arnout E. <no...@bz...>]

Hello,

The package appears to be getting into fairly good shape.

If you have amd64:

  https://sourceforge.net/projects/notion/files/

On other architectures, you can clone the packaging repo:

  http://anonscm.debian.org/git/collab-maint/notion.git

and run 'git-buildpackage' to produce a package for your architecture.


If anyone is or knows a DD that might be interested in reviewing and
sponsoring this package that would be great!


Kind regards,

Arnout

On Sun, Oct 30, 2011 at 08:29:35PM +0100, Arnout Engelen wrote:
> Hi,
> 
> The previous ion3 packager for Debian is no longer using it, so he's not 
> interested in maintaining a notion package.
> 
> I've started on porting his ion3 packaging work to create a notion package. 
> This is checked into the 'collaborative maintenance'-infrastructure at Debian:
> 
> Basically you can git clone
> 
>   ssh://<username>@git.debian.org/git/collab-maint/notion.git
> 
> and use 'git-buildpackage' to build the notion package. Currently not 
> lintian-clean and untested. 
> 
> Anyone interested in helping out?
> 
> 
> Kind regards,
> 
> Arnout
> 
> ------------------------------------------------------------------------------
> Get your Android app more play: Bring it to the BlackBerry PlayBook 
> in minutes. BlackBerry App World&#153; now supports Android&#153; Apps 
> for the BlackBerry&reg; PlayBook&#153;. Discover just how easy and simple 
> it is! http://p.sf.net/sfu/android-dev2dev
> _______________________________________________
> Notion-devel mailing list
> Not...@li...
> https://lists.sourceforge.net/lists/listinfo/notion-devel

Re: [Notion-devel] Licensing situation

[Arnout E. <no...@bz...>]

Hi,

Thanks for pointing this out, indeed this allows us to drop the 28-days-clause,
which is nice. 

I'm contacting some of our contributors since the fork, if they're OK with it
(which I expect :) ) I'll make the license change.


Kind regards,

Arnout

On Wed, Nov 09, 2011 at 08:28:36PM +0100, Philipp Hartwig wrote:
> Here's a copy of Tuomo's message with the relaxed license for your 
> convenience and future reference. The license has a valid GPG signature 
> that can be verified with the key with the ID C004251B which is available 
> on the GPG keyservers and can be imported with $ gpg --recv-keys C004251B
> Use for example :set pgp_auto_decode or <check-traditional-pgp> (bound to 
> ESC P by default) in mutt to verify the signature. It seems as if this 
> message was good enough to update the license of the latest Ion3 package in 
> Debian.
> 
> Regards,
> Philipp
> 
> 
> 
> >From tuomov at iki.fi  Wed Sep  2 19:56:56 2009
> From: tuomov at iki.fi (Tuomo Valkonen)
> Date: Wed, 2 Sep 2009 20:56:56 +0300
> Subject: License update
> Message-ID: <200...@mo...>
> 
> Since I probably won't be working on Ion much, and Ion3
> seems very stable anyway, here's an updated license file
> without the 28-day clause. There's also one patch available
> to Ion3 at <http://iki.fi/tuomov/ion/patches.html>, not
> included in the latest release.
> 
> -- 
> Tuomo
> -------------- next part --------------
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
> Copyright (c) Tuomo Valkonen 1999-2009.
> 
> Unless otherwise indicated in components taken from elsewhere, this software
> is licensed under the GNU Lesser General Public License, version 2.1 ("LGPL",
> reproduced below), extended and modified with the following terms:
> 
>   If the name Ion(tm) or other names that can be associated with the Ion
>   project are used to distribute this software, then:
> 
>     - A version that does not significantly differ from one of the
>       copyright holder's releases, must be provided by default.
> 
>     - Significantly altered versions may be provided only if the user
>       explicitly requests for those modifications to be applied, and 
>       is prominently notified that the software is no longer considered 
>       the standard version, and is not supported by the copyright holder.
>       The version string displayed by the program must describe these
>       modifications and the "support void" status.
> 
>   Versions for which the above conditions are not satisfied, must be
>   renamed so that they can not be associated with the Ion project, their
>   executables must be given names that do not conflict with the copyright
>   holder's version, and neither the copyright holder nor the Ion project
>   may be referred to for support.
> 
>   In the text of sections 0-2, 4-12, and 14-16 of the LGPL, "this License" 
>   is to be understood to refer to the LGPL extended with these terms and,
>   where applicable, possible similar terms related to the names of other
>   works forming a whole. Sections 3 and 13 of the LGPL are void. Where
>   contradictory, these additional terms take precedence over the LGPL.
> 
> End of terms.
> 
> 
> Explanations
> 
> Trademarks: With the terms above primarily appealing to copyright law,
> should any of the indicated trademarks be found invalid, does not excuse
> you from the conditions imposed by those terms. The use of these names
> in contexts other than redistribution of this software and modifications,
> is outside the scope of the terms above, and governed by applicable
> trademark or other laws. 
> 
>   With regard to modules and other extensions to Ion(tm), the permission
>   is hereby granted to use "Ion" as part of the name, provided that it
>   occurs in a form suggesting that the work is supported by neither the
>   copyright holder nor the Ion project: "Foo for Ion" instead of "Ion Foo",
>   etc.
> 
> Significant change: Bug fixes are insignificant as additions. Basic changes
> that are needed to install or run the software on a target platform, are 
> insignificant. Additionally, basic/small configuration changes to better 
> integrate the software with the target platform, without obstructing the
> standard behaviour, are insignificant. Everything else is significant, 
> unless expressly declared otherwise by the copyright holder. 
> 
> 
> - ---
> 
> 
>                   GNU LESSER GENERAL PUBLIC LICENSE
>                        Version 2.1, February 1999
> 
>  Copyright (C) 1991, 1999 Free Software Foundation, Inc.
> 	51 Franklin St, Fifth Floor, Boston, MA  02110-1301  USA
>  Everyone is permitted to copy and distribute verbatim copies
>  of this license document, but changing it is not allowed.
> 
> [This is the first released version of the Lesser GPL.  It also counts
>  as the successor of the GNU Library Public License, version 2, hence
>  the version number 2.1.]
> 
>                             Preamble
> 
>   The licenses for most software are designed to take away your
> freedom to share and change it.  By contrast, the GNU General Public
> Licenses are intended to guarantee your freedom to share and change
> free software--to make sure the software is free for all its users.
> 
>   This license, the Lesser General Public License, applies to some
> specially designated software packages--typically libraries--of the
> Free Software Foundation and other authors who decide to use it.  You
> can use it too, but we suggest you first think carefully about whether
> this license or the ordinary General Public License is the better
> strategy to use in any particular case, based on the explanations
> below.
> 
>   When we speak of free software, we are referring to freedom of use,
> not price.  Our General Public Licenses are designed to make sure that
> you have the freedom to distribute copies of free software (and charge
> for this service if you wish); that you receive source code or can get
> it if you want it; that you can change the software and use pieces of
> it in new free programs; and that you are informed that you can do
> these things.
> 
>   To protect your rights, we need to make restrictions that forbid
> distributors to deny you these rights or to ask you to surrender these
> rights.  These restrictions translate to certain responsibilities for
> you if you distribute copies of the library or if you modify it.
> 
>   For example, if you distribute copies of the library, whether gratis
> or for a fee, you must give the recipients all the rights that we gave
> you.  You must make sure that they, too, receive or can get the source
> code.  If you link other code with the library, you must provide
> complete object files to the recipients, so that they can relink them
> with the library after making changes to the library and recompiling
> it.  And you must show them these terms so they know their rights.
> 
>   We protect your rights with a two-step method: (1) we copyright the
> library, and (2) we offer you this license, which gives you legal
> permission to copy, distribute and/or modify the library.
> 
>   To protect each distributor, we want to make it very clear that
> there is no warranty for the free library.  Also, if the library is
> modified by someone else and passed on, the recipients should know
> that what they have is not the original version, so that the original
> author's reputation will not be affected by problems that might be
> introduced by others.
> 
>   Finally, software patents pose a constant threat to the existence of
> any free program.  We wish to make sure that a company cannot
> effectively restrict the users of a free program by obtaining a
> restrictive license from a patent holder.  Therefore, we insist that
> any patent license obtained for a version of the library must be
> consistent with the full freedom of use specified in this license.
> 
>   Most GNU software, including some libraries, is covered by the
> ordinary GNU General Public License.  This license, the GNU Lesser
> General Public License, applies to certain designated libraries, and
> is quite different from the ordinary General Public License.  We use
> this license for certain libraries in order to permit linking those
> libraries into non-free programs.
> 
>   When a program is linked with a library, whether statically or using
> a shared library, the combination of the two is legally speaking a
> combined work, a derivative of the original library.  The ordinary
> General Public License therefore permits such linking only if the
> entire combination fits its criteria of freedom.  The Lesser General
> Public License permits more lax criteria for linking other code with
> the library.
> 
>   We call this license the "Lesser" General Public License because it
> does Less to protect the user's freedom than the ordinary General
> Public License.  It also provides other free software developers Less
> of an advantage over competing non-free programs.  These disadvantages
> are the reason we use the ordinary General Public License for many
> libraries.  However, the Lesser license provides advantages in certain
> special circumstances.
> 
>   For example, on rare occasions, there may be a special need to
> encourage the widest possible use of a certain library, so that it
> becomes a de-facto standard.  To achieve this, non-free programs must
> be allowed to use the library.  A more frequent case is that a free
> library does the same job as widely used non-free libraries.  In this
> case, there is little to gain by limiting the free library to free
> software only, so we use the Lesser General Public License.
> 
>   In other cases, permission to use a particular library in non-free
> programs enables a greater number of people to use a large body of
> free software.  For example, permission to use the GNU C Library in
> non-free programs enables many more people to use the whole GNU
> operating system, as well as its variant, the GNU/Linux operating
> system.
> 
>   Although the Lesser General Public License is Less protective of the
> users' freedom, it does ensure that the user of a program that is
> linked with the Library has the freedom and the wherewithal to run
> that program using a modified version of the Library.
> 
>   The precise terms and conditions for copying, distribution and
> modification follow.  Pay close attention to the difference between a
> "work based on the library" and a "work that uses the library".  The
> former contains code derived from the library, whereas the latter must
> be combined with the library in order to run.
> 
>                   GNU LESSER GENERAL PUBLIC LICENSE
>    TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
> 
>   0. This License Agreement applies to any software library or other
> program which contains a notice placed by the copyright holder or
> other authorized party saying it may be distributed under the terms of
> this Lesser General Public License (also called "this License").
> Each licensee is addressed as "you".
> 
>   A "library" means a collection of software functions and/or data
> prepared so as to be conveniently linked with application programs
> (which use some of those functions and data) to form executables.
> 
>   The "Library", below, refers to any such software library or work
> which has been distributed under these terms.  A "work based on the
> Library" means either the Library or any derivative work under
> copyright law: that is to say, a work containing the Library or a
> portion of it, either verbatim or with modifications and/or translated
> straightforwardly into another language.  (Hereinafter, translation is
> included without limitation in the term "modification".)
> 
>   "Source code" for a work means the preferred form of the work for
> making modifications to it.  For a library, complete source code means
> all the source code for all modules it contains, plus any associated
> interface definition files, plus the scripts used to control
> compilation and installation of the library.
> 
>   Activities other than copying, distribution and modification are not
> covered by this License; they are outside its scope.  The act of
> running a program using the Library is not restricted, and output from
> such a program is covered only if its contents constitute a work based
> on the Library (independent of the use of the Library in a tool for
> writing it).  Whether that is true depends on what the Library does
> and what the program that uses the Library does.
> 
>   1. You may copy and distribute verbatim copies of the Library's
> complete source code as you receive it, in any medium, provided that
> you conspicuously and appropriately publish on each copy an
> appropriate copyright notice and disclaimer of warranty; keep intact
> all the notices that refer to this License and to the absence of any
> warranty; and distribute a copy of this License along with the
> Library.
> 
>   You may charge a fee for the physical act of transferring a copy,
> and you may at your option offer warranty protection in exchange for a
> fee.
> 
>   2. You may modify your copy or copies of the Library or any portion
> of it, thus forming a work based on the Library, and copy and
> distribute such modifications or work under the terms of Section 1
> above, provided that you also meet all of these conditions:
> 
>     a) The modified work must itself be a software library.
> 
>     b) You must cause the files modified to carry prominent notices
>     stating that you changed the files and the date of any change.
> 
>     c) You must cause the whole of the work to be licensed at no
>     charge to all third parties under the terms of this License.
> 
>     d) If a facility in the modified Library refers to a function or a
>     table of data to be supplied by an application program that uses
>     the facility, other than as an argument passed when the facility
>     is invoked, then you must make a good faith effort to ensure that,
>     in the event an application does not supply such function or
>     table, the facility still operates, and performs whatever part of
>     its purpose remains meaningful.
> 
>     (For example, a function in a library to compute square roots has
>     a purpose that is entirely well-defined independent of the
>     application.  Therefore, Subsection 2d requires that any
>     application-supplied function or table used by this function must
>     be optional: if the application does not supply it, the square
>     root function must still compute square roots.)
> 
> These requirements apply to the modified work as a whole.  If
> identifiable sections of that work are not derived from the Library,
> and can be reasonably considered independent and separate works in
> themselves, then this License, and its terms, do not apply to those
> sections when you distribute them as separate works.  But when you
> distribute the same sections as part of a whole which is a work based
> on the Library, the distribution of the whole must be on the terms of
> this License, whose permissions for other licensees extend to the
> entire whole, and thus to each and every part regardless of who wrote
> it.
> 
> Thus, it is not the intent of this section to claim rights or contest
> your rights to work written entirely by you; rather, the intent is to
> exercise the right to control the distribution of derivative or
> collective works based on the Library.
> 
> In addition, mere aggregation of another work not based on the Library
> with the Library (or with a work based on the Library) on a volume of
> a storage or distribution medium does not bring the other work under
> the scope of this License.
> 
>   3. You may opt to apply the terms of the ordinary GNU General Public
> License instead of this License to a given copy of the Library.  To do
> this, you must alter all the notices that refer to this License, so
> that they refer to the ordinary GNU General Public License, version 2,
> instead of to this License.  (If a newer version than version 2 of the
> ordinary GNU General Public License has appeared, then you can specify
> that version instead if you wish.)  Do not make any other change in
> these notices.
> 
>   Once this change is made in a given copy, it is irreversible for
> that copy, so the ordinary GNU General Public License applies to all
> subsequent copies and derivative works made from that copy.
> 
>   This option is useful when you wish to copy part of the code of
> the Library into a program that is not a library.
> 
>   4. You may copy and distribute the Library (or a portion or
> derivative of it, under Section 2) in object code or executable form
> under the terms of Sections 1 and 2 above provided that you accompany
> it with the complete corresponding machine-readable source code, which
> must be distributed under the terms of Sections 1 and 2 above on a
> medium customarily used for software interchange.
> 
>   If distribution of object code is made by offering access to copy
> from a designated place, then offering equivalent access to copy the
> source code from the same place satisfies the requirement to
> distribute the source code, even though third parties are not
> compelled to copy the source along with the object code.
> 
>   5. A program that contains no derivative of any portion of the
> Library, but is designed to work with the Library by being compiled or
> linked with it, is called a "work that uses the Library".  Such a
> work, in isolation, is not a derivative work of the Library, and
> therefore falls outside the scope of this License.
> 
>   However, linking a "work that uses the Library" with the Library
> creates an executable that is a derivative of the Library (because it
> contains portions of the Library), rather than a "work that uses the
> library".  The executable is therefore covered by this License.
> Section 6 states terms for distribution of such executables.
> 
>   When a "work that uses the Library" uses material from a header file
> that is part of the Library, the object code for the work may be a
> derivative work of the Library even though the source code is not.
> Whether this is true is especially significant if the work can be
> linked without the Library, or if the work is itself a library.  The
> threshold for this to be true is not precisely defined by law.
> 
>   If such an object file uses only numerical parameters, data
> structure layouts and accessors, and small macros and small inline
> functions (ten lines or less in length), then the use of the object
> file is unrestricted, regardless of whether it is legally a derivative
> work.  (Executables containing this object code plus portions of the
> Library will still fall under Section 6.)
> 
>   Otherwise, if the work is a derivative of the Library, you may
> distribute the object code for the work under the terms of Section 6.
> Any executables containing that work also fall under Section 6,
> whether or not they are linked directly with the Library itself.
> 
>   6. As an exception to the Sections above, you may also combine or
> link a "work that uses the Library" with the Library to produce a
> work containing portions of the Library, and distribute that work
> under terms of your choice, provided that the terms permit
> modification of the work for the customer's own use and reverse
> engineering for debugging such modifications.
> 
>   You must give prominent notice with each copy of the work that the
> Library is used in it and that the Library and its use are covered by
> this License.  You must supply a copy of this License.  If the work
> during execution displays copyright notices, you must include the
> copyright notice for the Library among them, as well as a reference
> directing the user to the copy of this License.  Also, you must do one
> of these things:
> 
>     a) Accompany the work with the complete corresponding
>     machine-readable source code for the Library including whatever
>     changes were used in the work (which must be distributed under
>     Sections 1 and 2 above); and, if the work is an executable linked
>     with the Library, with the complete machine-readable "work that
>     uses the Library", as object code and/or source code, so that the
>     user can modify the Library and then relink to produce a modified
>     executable containing the modified Library.  (It is understood
>     that the user who changes the contents of definitions files in the
>     Library will not necessarily be able to recompile the application
>     to use the modified definitions.)
> 
>     b) Use a suitable shared library mechanism for linking with the
>     Library.  A suitable mechanism is one that (1) uses at run time a
>     copy of the library already present on the user's computer system,
>     rather than copying library functions into the executable, and (2)
>     will operate properly with a modified version of the library, if
>     the user installs one, as long as the modified version is
>     interface-compatible with the version that the work was made with.
> 
>     c) Accompany the work with a written offer, valid for at least
>     three years, to give the same user the materials specified in
>     Subsection 6a, above, for a charge no more than the cost of
>     performing this distribution.
> 
>     d) If distribution of the work is made by offering access to copy
>     from a designated place, offer equivalent access to copy the above
>     specified materials from the same place.
> 
>     e) Verify that the user has already received a copy of these
>     materials or that you have already sent this user a copy.
> 
>   For an executable, the required form of the "work that uses the
> Library" must include any data and utility programs needed for
> reproducing the executable from it.  However, as a special exception,
> the materials to be distributed need not include anything that is
> normally distributed (in either source or binary form) with the major
> components (compiler, kernel, and so on) of the operating system on
> which the executable runs, unless that component itself accompanies
> the executable.
> 
>   It may happen that this requirement contradicts the license
> restrictions of other proprietary libraries that do not normally
> accompany the operating system.  Such a contradiction means you cannot
> use both them and the Library together in an executable that you
> distribute.
> 
>   7. You may place library facilities that are a work based on the
> Library side-by-side in a single library together with other library
> facilities not covered by this License, and distribute such a combined
> library, provided that the separate distribution of the work based on
> the Library and of the other library facilities is otherwise
> permitted, and provided that you do these two things:
> 
>     a) Accompany the combined library with a copy of the same work
>     based on the Library, uncombined with any other library
>     facilities.  This must be distributed under the terms of the
>     Sections above.
> 
>     b) Give prominent notice with the combined library of the fact
>     that part of it is a work based on the Library, and explaining
>     where to find the accompanying uncombined form of the same work.
> 
>   8. You may not copy, modify, sublicense, link with, or distribute
> the Library except as expressly provided under this License.  Any
> attempt otherwise to copy, modify, sublicense, link with, or
> distribute the Library is void, and will automatically terminate your
> rights under this License.  However, parties who have received copies,
> or rights, from you under this License will not have their licenses
> terminated so long as such parties remain in full compliance.
> 
>   9. You are not required to accept this License, since you have not
> signed it.  However, nothing else grants you permission to modify or
> distribute the Library or its derivative works.  These actions are
> prohibited by law if you do not accept this License.  Therefore, by
> modifying or distributing the Library (or any work based on the
> Library), you indicate your acceptance of this License to do so, and
> all its terms and conditions for copying, distributing or modifying
> the Library or works based on it.
> 
>   10. Each time you redistribute the Library (or any work based on the
> Library), the recipient automatically receives a license from the
> original licensor to copy, distribute, link with or modify the Library
> subject to these terms and conditions.  You may not impose any further
> restrictions on the recipients' exercise of the rights granted herein.
> You are not responsible for enforcing compliance by third parties with
> this License.
> 
>   11. If, as a consequence of a court judgment or allegation of patent
> infringement or for any other reason (not limited to patent issues),
> conditions are imposed on you (whether by court order, agreement or
> otherwise) that contradict the conditions of this License, they do not
> excuse you from the conditions of this License.  If you cannot
> distribute so as to satisfy simultaneously your obligations under this
> License and any other pertinent obligations, then as a consequence you
> may not distribute the Library at all.  For example, if a patent
> license would not permit royalty-free redistribution of the Library by
> all those who receive copies directly or indirectly through you, then
> the only way you could satisfy both it and this License would be to
> refrain entirely from distribution of the Library.
> 
> If any portion of this section is held invalid or unenforceable under
> any particular circumstance, the balance of the section is intended to
> apply, and the section as a whole is intended to apply in other
> circumstances.
> 
> It is not the purpose of this section to induce you to infringe any
> patents or other property right claims or to contest validity of any
> such claims; this section has the sole purpose of protecting the
> integrity of the free software distribution system which is
> implemented by public license practices.  Many people have made
> generous contributions to the wide range of software distributed
> through that system in reliance on consistent application of that
> system; it is up to the author/donor to decide if he or she is willing
> to distribute software through any other system and a licensee cannot
> impose that choice.
> 
> This section is intended to make thoroughly clear what is believed to
> be a consequence of the rest of this License.
> 
>   12. If the distribution and/or use of the Library is restricted in
> certain countries either by patents or by copyrighted interfaces, the
> original copyright holder who places the Library under this License
> may add an explicit geographical distribution limitation excluding those
> countries, so that distribution is permitted only in or among
> countries not thus excluded.  In such case, this License incorporates
> the limitation as if written in the body of this License.
> 
>   13. The Free Software Foundation may publish revised and/or new
> versions of the Lesser General Public License from time to time.
> Such new versions will be similar in spirit to the present version,
> but may differ in detail to address new problems or concerns.
> 
> Each version is given a distinguishing version number.  If the Library
> specifies a version number of this License which applies to it and
> "any later version", you have the option of following the terms and
> conditions either of that version or of any later version published by
> the Free Software Foundation.  If the Library does not specify a
> license version number, you may choose any version ever published by
> the Free Software Foundation.
> 
>   14. If you wish to incorporate parts of the Library into other free
> programs whose distribution conditions are incompatible with these,
> write to the author to ask for permission.  For software which is
> copyrighted by the Free Software Foundation, write to the Free
> Software Foundation; we sometimes make exceptions for this.  Our
> decision will be guided by the two goals of preserving the free status
> of all derivatives of our free software and of promoting the sharing
> and reuse of software generally.
> 
>                             NO WARRANTY
> 
>   15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
> WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
> EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
> OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
> KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
> IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
> PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
> LIBRARY IS WITH YOU.  SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
> THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
> 
>   16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
> WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
> AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
> FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
> CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
> LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
> RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
> FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
> SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
> DAMAGES.
> 
>                      END OF TERMS AND CONDITIONS
> 
>            How to Apply These Terms to Your New Libraries
> 
>   If you develop a new library, and you want it to be of the greatest
> possible use to the public, we recommend making it free software that
> everyone can redistribute and change.  You can do so by permitting
> redistribution under these terms (or, alternatively, under the terms
> of the ordinary General Public License).
> 
>   To apply these terms, attach the following notices to the library.
> It is safest to attach them to the start of each source file to most
> effectively convey the exclusion of warranty; and each file should
> have at least the "copyright" line and a pointer to where the full
> notice is found.
> 
> 
>     <one line to give the library's name and a brief idea of what it does.>
>     Copyright (C) <year>  <name of author>
> 
>     This library is free software; you can redistribute it and/or
>     modify it under the terms of the GNU Lesser General Public
>     License as published by the Free Software Foundation; either
>     version 2.1 of the License, or (at your option) any later version.
> 
>     This library is distributed in the hope that it will be useful,
>     but WITHOUT ANY WARRANTY; without even the implied warranty of
>     MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
>     Lesser General Public License for more details.
> 
>     You should have received a copy of the GNU Lesser General Public
>     License along with this library; if not, write to the Free Software
>     Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA  02110-1301  USA
> 
> Also add information on how to contact you by electronic and paper mail.
> 
> You should also get your employer (if you work as a programmer) or
> your school, if any, to sign a "copyright disclaimer" for the library,
> if necessary.  Here is a sample; alter the names:
> 
>   Yoyodyne, Inc., hereby disclaims all copyright interest in the
>   library `Frob' (a library for tweaking knobs) written by James
>   Random Hacker.
> 
>   <signature of Ty Coon>, 1 April 1990
>   Ty Coon, President of Vice
> 
> That's all there is to it!
> 
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.9 (MingW32)
> 
> iEYEARECAAYFAkqesLwACgkQ0AyiHsAEJRufaQCfZH2trAXY83GGTmgcW2Vg1Ac4
> f3AAnRhMzFlmGmoJ0+3H5g1mD0YNW70I
> =iRLJ
> -----END PGP SIGNATURE-----
> 
> 
> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Save $700 by Nov 18
> Register now
> http://p.sf.net/sfu/rsa-sfdev2dev1
> _______________________________________________
> Notion-devel mailing list
> Not...@li...
> https://lists.sourceforge.net/lists/listinfo/notion-devel

Re: [Notion-devel] Licensing situation

[<kev...@gm...>]

Hi Philipp,

I was extremely excited when I saw this message (The first time, when
Tuomo posted it).  Unfortunately while it relaxed the license
modifications somewhat, it still unduly restricts distribution of the
software, so (speaking just for myself) it is still worthwhile to fork
from a version of the software from before the license insanity started.

Kevin Granade


Philipp Hartwig <phi...@un...> writes:

> Here's a copy of Tuomo's message with the relaxed license for your 
> convenience and future reference. The license has a valid GPG signature 
> that can be verified with the key with the ID C004251B which is available 
> on the GPG keyservers and can be imported with $ gpg --recv-keys C004251B
> Use for example :set pgp_auto_decode or <check-traditional-pgp> (bound to 
> ESC P by default) in mutt to verify the signature. It seems as if this 
> message was good enough to update the license of the latest Ion3 package in 
> Debian.
>
> Regards,
> Philipp
>
>
>
>>From tuomov at iki.fi  Wed Sep  2 19:56:56 2009
> From: tuomov at iki.fi (Tuomo Valkonen)
> Date: Wed, 2 Sep 2009 20:56:56 +0300
> Subject: License update
> Message-ID: <200...@mo...>
>
> Since I probably won't be working on Ion much, and Ion3
> seems very stable anyway, here's an updated license file
> without the 28-day clause. There's also one patch available
> to Ion3 at <http://iki.fi/tuomov/ion/patches.html>, not
> included in the latest release.

Re: [Notion-devel] [Notion-general] Panels with notion?

[David G. <dg...@co...>]

On 11/11/11 15:40, Arnout Engelen wrote:
[...]
> Iirc your original proposal was to have some 'default winprops' and then allow
> them to be overridden by individual defwinprop statements. Not sure if you can
> accomplish this with the clientwin_init hook, but by all means give it a try!

Thinking about there's actually use cases for doing things both ways
round (allow the user to specify default winprops which get overridden
by defwinprop, and allow the user to specify additional winprops which
override those set by defwinprop).

Is it currently possible to call the functions on a hook from Lua? I
don't see any obvious code to do so.

-- 
┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ───── http://www.cowlark.com ─────
│
│ "Under communism, man exploits man. Under capitalism, it's just the
│ opposite." --- John Kenneth Galbrith

Re: [Notion-devel] [Notion-general] Panels with notion?

[Arnout E. <no...@bz...>]

On Thu, Nov 10, 2011 at 11:02:16PM +0000, David Given wrote:
> On 06/11/11 14:01, Arnout Engelen wrote:
> > Even better might be to use the existing 'hook' infrastructure
> 
> Is there any difference between doing things at this stage with a 
> clientwin_init hook, rather than adding the new hook after the winprop table
> has been looked up in the Lua side of things? It *should* have the same 
> effect in the long run (winprops set by the hook override winprops set by 
> defwinprop).

Iirc your original proposal was to have some 'default winprops' and then allow
them to be overridden by individual defwinprop statements. Not sure if you can
accomplish this with the clientwin_init hook, but by all means give it a try!


Arnout

Re: [Notion-devel] [Notion-general] Panels with notion?

[David G. <dg...@co...>]

On 06/11/11 14:01, Arnout Engelen wrote:
[...]
> Even better might be to use the existing 'hook' infrastructure: when a client
> window is created, you could then set it to 'float' in a hook that runs after 
> creation and before the winprops are applied.

Sorry about the delay, I've been swamped with stuff...

Ah, I didn't find hooks. That's obviously the way to go.

[...]
> * adding a hook that fires when initializing a client window, before winprops 
>   are applied
[...]
> Does that make sense? How does it compare to the other proposed solution?

This approach does mean changing things on the C side. Is there any
difference between doing things at this stage with a clientwin_init
hook, rather than adding the new hook after the winprop table has been
looked up in the Lua side of things? It *should* have the same effect in
the long run (winprops set by the hook override winprops set by defwinprop).

-- 
┌─── ｄｇ＠ｃｏｗｌａｒｋ．ｃｏｍ ───── http://www.cowlark.com ─────
│
│ "Under communism, man exploits man. Under capitalism, it's just the
│ opposite." --- John Kenneth Galbrith

Re: [Notion-devel] Licensing situation

[Philipp H. <phi...@un...>]

Here's a copy of Tuomo's message with the relaxed license for your 
convenience and future reference. The license has a valid GPG signature 
that can be verified with the key with the ID C004251B which is available 
on the GPG keyservers and can be imported with $ gpg --recv-keys C004251B
Use for example :set pgp_auto_decode or <check-traditional-pgp> (bound to 
ESC P by default) in mutt to verify the signature. It seems as if this 
message was good enough to update the license of the latest Ion3 package in 
Debian.

Regards,
Philipp



>From tuomov at iki.fi  Wed Sep  2 19:56:56 2009
From: tuomov at iki.fi (Tuomo Valkonen)
Date: Wed, 2 Sep 2009 20:56:56 +0300
Subject: License update
Message-ID: <200...@mo...>

Since I probably won't be working on Ion much, and Ion3
seems very stable anyway, here's an updated license file
without the 28-day clause. There's also one patch available
to Ion3 at <http://iki.fi/tuomov/ion/patches.html>, not
included in the latest release.

-- 
Tuomo
-------------- next part --------------
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


Copyright (c) Tuomo Valkonen 1999-2009.

Unless otherwise indicated in components taken from elsewhere, this software
is licensed under the GNU Lesser General Public License, version 2.1 ("LGPL",
reproduced below), extended and modified with the following terms:

  If the name Ion(tm) or other names that can be associated with the Ion
  project are used to distribute this software, then:

    - A version that does not significantly differ from one of the
      copyright holder's releases, must be provided by default.

    - Significantly altered versions may be provided only if the user
      explicitly requests for those modifications to be applied, and 
      is prominently notified that the software is no longer considered 
      the standard version, and is not supported by the copyright holder.
      The version string displayed by the program must describe these
      modifications and the "support void" status.

  Versions for which the above conditions are not satisfied, must be
  renamed so that they can not be associated with the Ion project, their
  executables must be given names that do not conflict with the copyright
  holder's version, and neither the copyright holder nor the Ion project
  may be referred to for support.

  In the text of sections 0-2, 4-12, and 14-16 of the LGPL, "this License" 
  is to be understood to refer to the LGPL extended with these terms and,
  where applicable, possible similar terms related to the names of other
  works forming a whole. Sections 3 and 13 of the LGPL are void. Where
  contradictory, these additional terms take precedence over the LGPL.

End of terms.


Explanations

Trademarks: With the terms above primarily appealing to copyright law,
should any of the indicated trademarks be found invalid, does not excuse
you from the conditions imposed by those terms. The use of these names
in contexts other than redistribution of this software and modifications,
is outside the scope of the terms above, and governed by applicable
trademark or other laws. 

  With regard to modules and other extensions to Ion(tm), the permission
  is hereby granted to use "Ion" as part of the name, provided that it
  occurs in a form suggesting that the work is supported by neither the
  copyright holder nor the Ion project: "Foo for Ion" instead of "Ion Foo",
  etc.

Significant change: Bug fixes are insignificant as additions. Basic changes
that are needed to install or run the software on a target platform, are 
insignificant. Additionally, basic/small configuration changes to better 
integrate the software with the target platform, without obstructing the
standard behaviour, are insignificant. Everything else is significant, 
unless expressly declared otherwise by the copyright holder. 


- ---


                  GNU LESSER GENERAL PUBLIC LICENSE
                       Version 2.1, February 1999

 Copyright (C) 1991, 1999 Free Software Foundation, Inc.
	51 Franklin St, Fifth Floor, Boston, MA  02110-1301  USA
 Everyone is permitted to copy and distribute verbatim copies
 of this license document, but changing it is not allowed.

[This is the first released version of the Lesser GPL.  It also counts
 as the successor of the GNU Library Public License, version 2, hence
 the version number 2.1.]

                            Preamble

  The licenses for most software are designed to take away your
freedom to share and change it.  By contrast, the GNU General Public
Licenses are intended to guarantee your freedom to share and change
free software--to make sure the software is free for all its users.

  This license, the Lesser General Public License, applies to some
specially designated software packages--typically libraries--of the
Free Software Foundation and other authors who decide to use it.  You
can use it too, but we suggest you first think carefully about whether
this license or the ordinary General Public License is the better
strategy to use in any particular case, based on the explanations
below.

  When we speak of free software, we are referring to freedom of use,
not price.  Our General Public Licenses are designed to make sure that
you have the freedom to distribute copies of free software (and charge
for this service if you wish); that you receive source code or can get
it if you want it; that you can change the software and use pieces of
it in new free programs; and that you are informed that you can do
these things.

  To protect your rights, we need to make restrictions that forbid
distributors to deny you these rights or to ask you to surrender these
rights.  These restrictions translate to certain responsibilities for
you if you distribute copies of the library or if you modify it.

  For example, if you distribute copies of the library, whether gratis
or for a fee, you must give the recipients all the rights that we gave
you.  You must make sure that they, too, receive or can get the source
code.  If you link other code with the library, you must provide
complete object files to the recipients, so that they can relink them
with the library after making changes to the library and recompiling
it.  And you must show them these terms so they know their rights.

  We protect your rights with a two-step method: (1) we copyright the
library, and (2) we offer you this license, which gives you legal
permission to copy, distribute and/or modify the library.

  To protect each distributor, we want to make it very clear that
there is no warranty for the free library.  Also, if the library is
modified by someone else and passed on, the recipients should know
that what they have is not the original version, so that the original
author's reputation will not be affected by problems that might be
introduced by others.

  Finally, software patents pose a constant threat to the existence of
any free program.  We wish to make sure that a company cannot
effectively restrict the users of a free program by obtaining a
restrictive license from a patent holder.  Therefore, we insist that
any patent license obtained for a version of the library must be
consistent with the full freedom of use specified in this license.

  Most GNU software, including some libraries, is covered by the
ordinary GNU General Public License.  This license, the GNU Lesser
General Public License, applies to certain designated libraries, and
is quite different from the ordinary General Public License.  We use
this license for certain libraries in order to permit linking those
libraries into non-free programs.

  When a program is linked with a library, whether statically or using
a shared library, the combination of the two is legally speaking a
combined work, a derivative of the original library.  The ordinary
General Public License therefore permits such linking only if the
entire combination fits its criteria of freedom.  The Lesser General
Public License permits more lax criteria for linking other code with
the library.

  We call this license the "Lesser" General Public License because it
does Less to protect the user's freedom than the ordinary General
Public License.  It also provides other free software developers Less
of an advantage over competing non-free programs.  These disadvantages
are the reason we use the ordinary General Public License for many
libraries.  However, the Lesser license provides advantages in certain
special circumstances.

  For example, on rare occasions, there may be a special need to
encourage the widest possible use of a certain library, so that it
becomes a de-facto standard.  To achieve this, non-free programs must
be allowed to use the library.  A more frequent case is that a free
library does the same job as widely used non-free libraries.  In this
case, there is little to gain by limiting the free library to free
software only, so we use the Lesser General Public License.

  In other cases, permission to use a particular library in non-free
programs enables a greater number of people to use a large body of
free software.  For example, permission to use the GNU C Library in
non-free programs enables many more people to use the whole GNU
operating system, as well as its variant, the GNU/Linux operating
system.

  Although the Lesser General Public License is Less protective of the
users' freedom, it does ensure that the user of a program that is
linked with the Library has the freedom and the wherewithal to run
that program using a modified version of the Library.

  The precise terms and conditions for copying, distribution and
modification follow.  Pay close attention to the difference between a
"work based on the library" and a "work that uses the library".  The
former contains code derived from the library, whereas the latter must
be combined with the library in order to run.

                  GNU LESSER GENERAL PUBLIC LICENSE
   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

  0. This License Agreement applies to any software library or other
program which contains a notice placed by the copyright holder or
other authorized party saying it may be distributed under the terms of
this Lesser General Public License (also called "this License").
Each licensee is addressed as "you".

  A "library" means a collection of software functions and/or data
prepared so as to be conveniently linked with application programs
(which use some of those functions and data) to form executables.

  The "Library", below, refers to any such software library or work
which has been distributed under these terms.  A "work based on the
Library" means either the Library or any derivative work under
copyright law: that is to say, a work containing the Library or a
portion of it, either verbatim or with modifications and/or translated
straightforwardly into another language.  (Hereinafter, translation is
included without limitation in the term "modification".)

  "Source code" for a work means the preferred form of the work for
making modifications to it.  For a library, complete source code means
all the source code for all modules it contains, plus any associated
interface definition files, plus the scripts used to control
compilation and installation of the library.

  Activities other than copying, distribution and modification are not
covered by this License; they are outside its scope.  The act of
running a program using the Library is not restricted, and output from
such a program is covered only if its contents constitute a work based
on the Library (independent of the use of the Library in a tool for
writing it).  Whether that is true depends on what the Library does
and what the program that uses the Library does.

  1. You may copy and distribute verbatim copies of the Library's
complete source code as you receive it, in any medium, provided that
you conspicuously and appropriately publish on each copy an
appropriate copyright notice and disclaimer of warranty; keep intact
all the notices that refer to this License and to the absence of any
warranty; and distribute a copy of this License along with the
Library.

  You may charge a fee for the physical act of transferring a copy,
and you may at your option offer warranty protection in exchange for a
fee.

  2. You may modify your copy or copies of the Library or any portion
of it, thus forming a work based on the Library, and copy and
distribute such modifications or work under the terms of Section 1
above, provided that you also meet all of these conditions:

    a) The modified work must itself be a software library.

    b) You must cause the files modified to carry prominent notices
    stating that you changed the files and the date of any change.

    c) You must cause the whole of the work to be licensed at no
    charge to all third parties under the terms of this License.

    d) If a facility in the modified Library refers to a function or a
    table of data to be supplied by an application program that uses
    the facility, other than as an argument passed when the facility
    is invoked, then you must make a good faith effort to ensure that,
    in the event an application does not supply such function or
    table, the facility still operates, and performs whatever part of
    its purpose remains meaningful.

    (For example, a function in a library to compute square roots has
    a purpose that is entirely well-defined independent of the
    application.  Therefore, Subsection 2d requires that any
    application-supplied function or table used by this function must
    be optional: if the application does not supply it, the square
    root function must still compute square roots.)

These requirements apply to the modified work as a whole.  If
identifiable sections of that work are not derived from the Library,
and can be reasonably considered independent and separate works in
themselves, then this License, and its terms, do not apply to those
sections when you distribute them as separate works.  But when you
distribute the same sections as part of a whole which is a work based
on the Library, the distribution of the whole must be on the terms of
this License, whose permissions for other licensees extend to the
entire whole, and thus to each and every part regardless of who wrote
it.

Thus, it is not the intent of this section to claim rights or contest
your rights to work written entirely by you; rather, the intent is to
exercise the right to control the distribution of derivative or
collective works based on the Library.

In addition, mere aggregation of another work not based on the Library
with the Library (or with a work based on the Library) on a volume of
a storage or distribution medium does not bring the other work under
the scope of this License.

  3. You may opt to apply the terms of the ordinary GNU General Public
License instead of this License to a given copy of the Library.  To do
this, you must alter all the notices that refer to this License, so
that they refer to the ordinary GNU General Public License, version 2,
instead of to this License.  (If a newer version than version 2 of the
ordinary GNU General Public License has appeared, then you can specify
that version instead if you wish.)  Do not make any other change in
these notices.

  Once this change is made in a given copy, it is irreversible for
that copy, so the ordinary GNU General Public License applies to all
subsequent copies and derivative works made from that copy.

  This option is useful when you wish to copy part of the code of
the Library into a program that is not a library.

  4. You may copy and distribute the Library (or a portion or
derivative of it, under Section 2) in object code or executable form
under the terms of Sections 1 and 2 above provided that you accompany
it with the complete corresponding machine-readable source code, which
must be distributed under the terms of Sections 1 and 2 above on a
medium customarily used for software interchange.

  If distribution of object code is made by offering access to copy
from a designated place, then offering equivalent access to copy the
source code from the same place satisfies the requirement to
distribute the source code, even though third parties are not
compelled to copy the source along with the object code.

  5. A program that contains no derivative of any portion of the
Library, but is designed to work with the Library by being compiled or
linked with it, is called a "work that uses the Library".  Such a
work, in isolation, is not a derivative work of the Library, and
therefore falls outside the scope of this License.

  However, linking a "work that uses the Library" with the Library
creates an executable that is a derivative of the Library (because it
contains portions of the Library), rather than a "work that uses the
library".  The executable is therefore covered by this License.
Section 6 states terms for distribution of such executables.

  When a "work that uses the Library" uses material from a header file
that is part of the Library, the object code for the work may be a
derivative work of the Library even though the source code is not.
Whether this is true is especially significant if the work can be
linked without the Library, or if the work is itself a library.  The
threshold for this to be true is not precisely defined by law.

  If such an object file uses only numerical parameters, data
structure layouts and accessors, and small macros and small inline
functions (ten lines or less in length), then the use of the object
file is unrestricted, regardless of whether it is legally a derivative
work.  (Executables containing this object code plus portions of the
Library will still fall under Section 6.)

  Otherwise, if the work is a derivative of the Library, you may
distribute the object code for the work under the terms of Section 6.
Any executables containing that work also fall under Section 6,
whether or not they are linked directly with the Library itself.

  6. As an exception to the Sections above, you may also combine or
link a "work that uses the Library" with the Library to produce a
work containing portions of the Library, and distribute that work
under terms of your choice, provided that the terms permit
modification of the work for the customer's own use and reverse
engineering for debugging such modifications.

  You must give prominent notice with each copy of the work that the
Library is used in it and that the Library and its use are covered by
this License.  You must supply a copy of this License.  If the work
during execution displays copyright notices, you must include the
copyright notice for the Library among them, as well as a reference
directing the user to the copy of this License.  Also, you must do one
of these things:

    a) Accompany the work with the complete corresponding
    machine-readable source code for the Library including whatever
    changes were used in the work (which must be distributed under
    Sections 1 and 2 above); and, if the work is an executable linked
    with the Library, with the complete machine-readable "work that
    uses the Library", as object code and/or source code, so that the
    user can modify the Library and then relink to produce a modified
    executable containing the modified Library.  (It is understood
    that the user who changes the contents of definitions files in the
    Library will not necessarily be able to recompile the application
    to use the modified definitions.)

    b) Use a suitable shared library mechanism for linking with the
    Library.  A suitable mechanism is one that (1) uses at run time a
    copy of the library already present on the user's computer system,
    rather than copying library functions into the executable, and (2)
    will operate properly with a modified version of the library, if
    the user installs one, as long as the modified version is
    interface-compatible with the version that the work was made with.

    c) Accompany the work with a written offer, valid for at least
    three years, to give the same user the materials specified in
    Subsection 6a, above, for a charge no more than the cost of
    performing this distribution.

    d) If distribution of the work is made by offering access to copy
    from a designated place, offer equivalent access to copy the above
    specified materials from the same place.

    e) Verify that the user has already received a copy of these
    materials or that you have already sent this user a copy.

  For an executable, the required form of the "work that uses the
Library" must include any data and utility programs needed for
reproducing the executable from it.  However, as a special exception,
the materials to be distributed need not include anything that is
normally distributed (in either source or binary form) with the major
components (compiler, kernel, and so on) of the operating system on
which the executable runs, unless that component itself accompanies
the executable.

  It may happen that this requirement contradicts the license
restrictions of other proprietary libraries that do not normally
accompany the operating system.  Such a contradiction means you cannot
use both them and the Library together in an executable that you
distribute.

  7. You may place library facilities that are a work based on the
Library side-by-side in a single library together with other library
facilities not covered by this License, and distribute such a combined
library, provided that the separate distribution of the work based on
the Library and of the other library facilities is otherwise
permitted, and provided that you do these two things:

    a) Accompany the combined library with a copy of the same work
    based on the Library, uncombined with any other library
    facilities.  This must be distributed under the terms of the
    Sections above.

    b) Give prominent notice with the combined library of the fact
    that part of it is a work based on the Library, and explaining
    where to find the accompanying uncombined form of the same work.

  8. You may not copy, modify, sublicense, link with, or distribute
the Library except as expressly provided under this License.  Any
attempt otherwise to copy, modify, sublicense, link with, or
distribute the Library is void, and will automatically terminate your
rights under this License.  However, parties who have received copies,
or rights, from you under this License will not have their licenses
terminated so long as such parties remain in full compliance.

  9. You are not required to accept this License, since you have not
signed it.  However, nothing else grants you permission to modify or
distribute the Library or its derivative works.  These actions are
prohibited by law if you do not accept this License.  Therefore, by
modifying or distributing the Library (or any work based on the
Library), you indicate your acceptance of this License to do so, and
all its terms and conditions for copying, distributing or modifying
the Library or works based on it.

  10. Each time you redistribute the Library (or any work based on the
Library), the recipient automatically receives a license from the
original licensor to copy, distribute, link with or modify the Library
subject to these terms and conditions.  You may not impose any further
restrictions on the recipients' exercise of the rights granted herein.
You are not responsible for enforcing compliance by third parties with
this License.

  11. If, as a consequence of a court judgment or allegation of patent
infringement or for any other reason (not limited to patent issues),
conditions are imposed on you (whether by court order, agreement or
otherwise) that contradict the conditions of this License, they do not
excuse you from the conditions of this License.  If you cannot
distribute so as to satisfy simultaneously your obligations under this
License and any other pertinent obligations, then as a consequence you
may not distribute the Library at all.  For example, if a patent
license would not permit royalty-free redistribution of the Library by
all those who receive copies directly or indirectly through you, then
the only way you could satisfy both it and this License would be to
refrain entirely from distribution of the Library.

If any portion of this section is held invalid or unenforceable under
any particular circumstance, the balance of the section is intended to
apply, and the section as a whole is intended to apply in other
circumstances.

It is not the purpose of this section to induce you to infringe any
patents or other property right claims or to contest validity of any
such claims; this section has the sole purpose of protecting the
integrity of the free software distribution system which is
implemented by public license practices.  Many people have made
generous contributions to the wide range of software distributed
through that system in reliance on consistent application of that
system; it is up to the author/donor to decide if he or she is willing
to distribute software through any other system and a licensee cannot
impose that choice.

This section is intended to make thoroughly clear what is believed to
be a consequence of the rest of this License.

  12. If the distribution and/or use of the Library is restricted in
certain countries either by patents or by copyrighted interfaces, the
original copyright holder who places the Library under this License
may add an explicit geographical distribution limitation excluding those
countries, so that distribution is permitted only in or among
countries not thus excluded.  In such case, this License incorporates
the limitation as if written in the body of this License.

  13. The Free Software Foundation may publish revised and/or new
versions of the Lesser General Public License from time to time.
Such new versions will be similar in spirit to the present version,
but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number.  If the Library
specifies a version number of this License which applies to it and
"any later version", you have the option of following the terms and
conditions either of that version or of any later version published by
the Free Software Foundation.  If the Library does not specify a
license version number, you may choose any version ever published by
the Free Software Foundation.

  14. If you wish to incorporate parts of the Library into other free
programs whose distribution conditions are incompatible with these,
write to the author to ask for permission.  For software which is
copyrighted by the Free Software Foundation, write to the Free
Software Foundation; we sometimes make exceptions for this.  Our
decision will be guided by the two goals of preserving the free status
of all derivatives of our free software and of promoting the sharing
and reuse of software generally.

                            NO WARRANTY

  15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
LIBRARY IS WITH YOU.  SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

  16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
DAMAGES.

                     END OF TERMS AND CONDITIONS

           How to Apply These Terms to Your New Libraries

  If you develop a new library, and you want it to be of the greatest
possible use to the public, we recommend making it free software that
everyone can redistribute and change.  You can do so by permitting
redistribution under these terms (or, alternatively, under the terms
of the ordinary General Public License).

  To apply these terms, attach the following notices to the library.
It is safest to attach them to the start of each source file to most
effectively convey the exclusion of warranty; and each file should
have at least the "copyright" line and a pointer to where the full
notice is found.


    <one line to give the library's name and a brief idea of what it does.>
    Copyright (C) <year>  <name of author>

    This library is free software; you can redistribute it and/or
    modify it under the terms of the GNU Lesser General Public
    License as published by the Free Software Foundation; either
    version 2.1 of the License, or (at your option) any later version.

    This library is distributed in the hope that it will be useful,
    but WITHOUT ANY WARRANTY; without even the implied warranty of
    MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.  See the GNU
    Lesser General Public License for more details.

    You should have received a copy of the GNU Lesser General Public
    License along with this library; if not, write to the Free Software
    Foundation, Inc., 51 Franklin St, Fifth Floor, Boston, MA  02110-1301  USA

Also add information on how to contact you by electronic and paper mail.

You should also get your employer (if you work as a programmer) or
your school, if any, to sign a "copyright disclaimer" for the library,
if necessary.  Here is a sample; alter the names:

  Yoyodyne, Inc., hereby disclaims all copyright interest in the
  library `Frob' (a library for tweaking knobs) written by James
  Random Hacker.

  <signature of Ty Coon>, 1 April 1990
  Ty Coon, President of Vice

That's all there is to it!


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (MingW32)

iEYEARECAAYFAkqesLwACgkQ0AyiHsAEJRufaQCfZH2trAXY83GGTmgcW2Vg1Ac4
f3AAnRhMzFlmGmoJ0+3H5g1mD0YNW70I
=iRLJ
-----END PGP SIGNATURE-----

Re: [Notion-devel] Licensing situation

[Philipp H. <phi...@un...>]

Hi,

Ion3 was relicensed at some point under a slightly more permissive license. 
Most notably it does not force distributions to display a warning if the 
provided version is out of date.

The updated license can be found under
https://lists.berlios.de/pipermail/ion-general/2009-September/001730.html

Any reason why we can not just use this license for notion?

Regards,
Philipp

Re: [Notion-devel] [Notion-general] Panels with notion?

[Arnout E. <no...@bz...>]

(moved to '-devel' as this is about changing/extending the way notion works)

On Fri, Oct 21, 2011 at 11:34:28AM +0100, David Given wrote:
> Possibly rather than try to change the defwinprop behaviour, it would be
> better to do this via new behaviour? Maybe something as simple as:
> 
> add_winprop_hook(
> 	function(prop, cwin, id)
> 		-- make all windows float unless specified otherwise
> 		if not prop.float then
> 			prop.float = true
> 		end
> 	end
> )
> 		
> These then get run (in order) after ioncore.getwinprop() has scanned the
> defwinprop list. This should satisfy Principle of Least Surprise while
> at the same time being more flexible.

Even better might be to use the existing 'hook' infrastructure: when a client
window is created, you could then set it to 'float' in a hook that runs after 
creation and before the winprops are applied.

Some winprops are applied directly in clientwin_get_winprops, others are just 
placed into cwin->proptab for later evaluation. 

This would mean:
* adding a hook that fires when initializing a client window, before winprops 
  are applied
* change 'cwin->proptab=tab' to merge the new values into a possibly-
  preexisting proptab instead of overwriting it.
* make 'proptab' available via lua

Then the client code could look something like:

ioncore.get_hook('clientwin_init_hook'):add(
  function(cwin)
    cwin.proptab = { float = true }
    end
)

Does that make sense? How does it compare to the other proposed solution?


Kind regards,

Arnout

Re: [Notion-devel] Debian packaging

[Matthieu M. <Mat...@gr...>]

Philipp Hartwig <phi...@un...> writes:

> Personally I had never even heard of pwm3 to this day. The man page says 
> that it is identical to Ion3 with the only difference lying in the default 
> configuration file.

PWM was Tuomo's first baby. It is said to be the first window-manager
including the "tab" features, but wasn't a tiling window-manager. Then,
Tuomo worked on ion (tiling mode), and then the floating windows were
added to ion (IIRC, with ion2), so ion became a superset of PWM. I think
including the PWM binary in the distribution was essentially a way to
emphasize the beauty and generality of ion, saying "hey, look, PWM can
be implemented on top of ion by just tweaking the config!".

I don't think it is technically relevant to keep it today.

-- 
Matthieu Moy
http://www-verimag.imag.fr/~moy/

[Notion-devel] Dropping support for PWM

[Arnout E. <no...@bz...>]

(cross-posted between -general and -devel because I guess it touches both)

Hi,

Ion3 used to include a windowmanager called 'pwm3'. 

As far as I understand pwm3 is basically 99.9% ion3 but with some other default
settings.

Does anyone use this or find it useful? If we can't find anyone, I propose we
drop this from Notion entirely. If someone can write some docs on how Notion 
can be configured to behave pwm-like we could add that to the wiki.


Kind regards,

Arnout

Re: [Notion-devel] Debian packaging

[Philipp H. <phi...@un...>]

> Actually the diff between the two debian folders is rather small. It should 
> be straightforward to just merge it with the changes you have already done.

I've done this but my message with the patch is awaiting moderator approval 
because apparently it was too big. (Just so that nobody else bothers to 
redo the work.)

Re: [Notion-devel] Debian packaging

[Philipp H. <phi...@un...>]

> Actually the diff between the two debian folders is rather small. It should 
> be straightforward to just merge it with the changes you have already done.

I've done this, see the attached patch. (The patch 
debian/patches/101_ion-3-20090526.diff has appararently already been 
applied to notion.)

This looks pretty good:

-------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------------------
$ fakeroot dpkg-buildpackage -uc -b > /dev/null
 dpkg-source --before-build notion
 debian/rules clean
No patch removed
 debian/rules build
obj.c: In function ‘comp_fun’:
obj.c:130:14: warning: ISO C forbids conversion of function pointer to object pointer type [-pedantic]
obj.c:131:14: warning: ISO C forbids conversion of function pointer to object pointer type [-pedantic]
obj.c: In function ‘lookup_dynfun’:
obj.c:192:20: warning: ISO C forbids conversion of function pointer to object pointer type [-pedantic]
obj.c:192:41: warning: ISO C forbids conversion of function pointer to object pointer type [-pedantic]
obj.c:196:20: warning: ISO C forbids conversion of function pointer to object pointer type [-pedantic]
obj.c:196:40: warning: ISO C forbids conversion of function pointer to object pointer type [-pedantic]
rb.c: In function ‘rb_inserti’:
rb.c:613:48: warning: cast to pointer from integer of different size [-Wint-to-pointer-cast]
modules.c: In function ‘get_module_fptr’:
modules.c:104:12: warning: ISO C forbids conversion of object pointer to function pointer type [-pedantic]
ion-statusd.c: In function ‘statusd_getloadavg’:
ion-statusd.c:304:5: warning: implicit declaration of function ‘getloadavg’ [-Wimplicit-function-declaration]
 debian/rules binary
dpkg-gencontrol: warning: package notion-dev: unused substitution variable ${Notion:ApiVersion}
 dpkg-genchanges -b >../notion_3-2011102900-1_amd64.changes
dpkg-genchanges: warning: the current version (3-2011102900-1) is earlier than the previous one (20080825-1)
dpkg-genchanges: binary-only upload - not including any source code
 dpkg-source --after-build notion
-------------------------------------------------------------------------------------------------------------
-------------------------------------------------------------------------------------------------------------

Here's what Lintian has to say about the package:

W: notion: latest-debian-changelog-entry-without-new-version
W: notion: binary-without-manpage usr/sbin/install-notion-cfg
W: notion: binary-without-manpage usr/bin/pwm3plus

The second trivial patch removes a postinst error. With this I'm able to 
install the package.

Regards,
Philipp

Re: [Notion-devel] Debian packaging

[Philipp H. <phi...@un...>]

> > I think this would be a better place to start. 
> 
> Obviously

Actually the diff between the two debian folders is rather small. It should 
be straightforward to just merge it with the changes you have already done.

> > What's the policy on pwm3? Is this supposed to be renamed to pwm3plus 
> > everywere?
> 
> Do we want to keep pwm at all? Or do we want to drop it entirely?

Personally I had never even heard of pwm3 to this day. The man page says 
that it is identical to Ion3 with the only difference lying in the default 
configuration file. I certainly don't see a reason to ship a separate 
binary file for that but that's just my personal opinion.
There is a discussion about the same question here:
http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=261076

Maybe dropping pwm3 but documenting the configuration necessary to achieve 
its behavior with notion is the right thing to do?

> > Lintian and others don't seem to be too happy about your choice of version 
> > number because they consider it to be older than the Ion3 versions (the 
> > leading 3 is the problem). Maybe just drop it?
> 
> I'm not sure - using *just* the date as the version would get us into trouble
> when we ever want a 'Notion 4' (a major rewrite or something). Having seperate
> packages for those (like 'ion2' and 'ion3' previously) would be something I'd 
> probably like to avoid. OTOH if it really warrants a new major version number
> perhaps it should allow users to have both installed alongside each other. What
> do you think?

How about just dropping the Ion3 history from the changelog and write 
"Inital release. Based on the Ion3 package, version 20090110-3, by Ben 
Hutchings." or something like that. This would give us complete liberty in 
the version numbers. Are you against version numbers like 3.0? I would 
leave the name at notion for the moment, we would then still have the 
option of releasing a notion4 package with all files renamed to notion4 if 
that looks like the reasonable thing to do at some point in the future.

Regards,
Philipp

Re: [Notion-devel] Debian packaging

[Josef 'J. S. <je...@jo...>]

On Mon, Oct 31, 2011 at 01:52:46PM +0100, Arnout Engelen wrote:
> On Mon, Oct 31, 2011 at 11:35:04AM +0100, Philipp Hartwig wrote:
> > are you aware that there is a newer Debian package available from
> > http://snapshot.debian.org/package/ion3/20090110-3/
> 
> No, I wasn't, thanks!
> 
> > I think this would be a better place to start. 
> 
> Obviously
> 
> > it doesn't seem to have the checks on whether the version being installed is
> > up-to-date which Tuomo was requiring at some point (look at template and 
> > notion.postinst in your tree).
> 
> Indeed we don't need those anymore
> 
> > What's the policy on pwm3? Is this supposed to be renamed to pwm3plus 
> > everywere?
> 
> Do we want to keep pwm at all? Or do we want to drop it entirely?

FWIW, I knew that there was something in there called pwm, but I never used
it/looked into it.  I suspect many others did the same.

> > Lintian and others don't seem to be too happy about your choice of version 
> > number because they consider it to be older than the Ion3 versions (the 
> > leading 3 is the problem). Maybe just drop it?
> 
> I'm not sure - using *just* the date as the version would get us into trouble
> when we ever want a 'Notion 4' (a major rewrite or something). Having seperate
> packages for those (like 'ion2' and 'ion3' previously) would be something I'd 
> probably like to avoid. OTOH if it really warrants a new major version number
> perhaps it should allow users to have both installed alongside each other. What
> do you think?

I noticed the odd looking version number too.  I'd be for notion$X-$Y, where
$X is the major number (= 3 at the moment) and $Y is some sort of minor
version number (either a counter or a timestamp).

Jeff.

-- 
Keyboard not found!
Press F1 to enter Setup

Re: [Notion-devel] Debian packaging

[Arnout E. <no...@bz...>]

On Mon, Oct 31, 2011 at 11:35:04AM +0100, Philipp Hartwig wrote:
> are you aware that there is a newer Debian package available from
> http://snapshot.debian.org/package/ion3/20090110-3/

No, I wasn't, thanks!

> I think this would be a better place to start. 

Obviously

> it doesn't seem to have the checks on whether the version being installed is
> up-to-date which Tuomo was requiring at some point (look at template and 
> notion.postinst in your tree).

Indeed we don't need those anymore

> What's the policy on pwm3? Is this supposed to be renamed to pwm3plus 
> everywere?

Do we want to keep pwm at all? Or do we want to drop it entirely?

> Lintian and others don't seem to be too happy about your choice of version 
> number because they consider it to be older than the Ion3 versions (the 
> leading 3 is the problem). Maybe just drop it?

I'm not sure - using *just* the date as the version would get us into trouble
when we ever want a 'Notion 4' (a major rewrite or something). Having seperate
packages for those (like 'ion2' and 'ion3' previously) would be something I'd 
probably like to avoid. OTOH if it really warrants a new major version number
perhaps it should allow users to have both installed alongside each other. What
do you think?


Kind regards,

Arnout

Re: [Notion-devel] Debian packaging

[Olof J. <ol...@et...>]

On 2011-10-30 20:29 +0100, Arnout Engelen wrote:
> Basically you can git clone
> 
>   ssh://<username>@git.debian.org/git/collab-maint/notion.git

Or git://git.debian.org/git/collab-maint/notion.git if you don't have
an alioth account.

> and use 'git-buildpackage' to build the notion package. Currently not 
> lintian-clean and untested. 
> 
> Anyone interested in helping out?

I'd be happy to help out if you need any assistance. I think the
lintian error can be solved easily, since the package no longer uses
debconf. Just remove the template file (debian/notion.templates), the
po directory and comment out line 127 (dh_installdebconf -a) of
debian/rules.

There's also a problem with undocumented build-dependencies (xinerama
and xrandr).

-- 
 --------------------------------------------------------------- 
|                                                Olof Johansson |
|                                             http://stdlib.se/ |
 --------------------------------------------------------------- 

Re: [Notion-devel] Debian packaging

[Philipp H. <phi...@un...>]

Hi,

are you aware that there is a newer Debian package available from
http://snapshot.debian.org/package/ion3/20090110-3/

(Unpack and patch it with
$ dpkg-source -x dpkg-source -x ion3_20090110-3.dsc
in a folder containing the three files.)

I think this would be a better place to start. It uses newer versions of 
debhelper etc., getting rid of some deprecation warnings, and it doesn't 
seem to have the checks on whether the version being installed is 
up-to-date which Tuomo was requiring at some point (look at template and 
notion.postinst in your tree).

What's the policy on pwm3? Is this supposed to be renamed to pwm3plus 
everywere?

Lintian and others don't seem to be too happy about your choice of version 
number because they consider it to be older than the Ion3 versions (the 
leading 3 is the problem). Maybe just drop it?

Regards,
Philipp

[Notion-devel] Debian packaging

[Arnout E. <no...@bz...>]

Hi,

The previous ion3 packager for Debian is no longer using it, so he's not 
interested in maintaining a notion package.

I've started on porting his ion3 packaging work to create a notion package. 
This is checked into the 'collaborative maintenance'-infrastructure at Debian:

Basically you can git clone

  ssh://<username>@git.debian.org/git/collab-maint/notion.git

and use 'git-buildpackage' to build the notion package. Currently not 
lintian-clean and untested. 

Anyone interested in helping out?


Kind regards,

Arnout

[Notion-devel] Roadmap for the next Notion release

[Arnout E. <no...@bz...>]

Hi,

With our first release out of the door, it's time to start planning the next 
one. What is your wishlist? A start:

* Bugfixes, documentation improvements based on any questions/bugreports
* Support for Windows (cygwin) and FreeBSD 
* Further improve multihead behavior (disappearing/re-appearing monitors are 
not handled well yet - I'd still like feedback on how we'd expect this to work
from the users' perspective)
* Improved support for EWMH hints
* Enabling more scripts/modules in the default configuration to give a better
out-of-the-box experience

(I'd like to try and "release early, release often", so we might not manage 
all of these in the next release, but it's still good to have some kind of 
focus :) )


Kind regards,

Arnout