> Am 02.03.2016 um 22:53 schrieb Harry Thijssen :
>
> The MSWindows installer displays a readme file on the screen during
> installation.
>
> The second line in this readme box states:
>
> This is a new MSWindows build of the PSPP master branch as of the date this
> binary was built and incl
I do have some understanding of the packager vs. developer situation, yes,
but didn't know there was a known bug in 0.8.5 that is so serious in
Windows, so the explanation is very appreciated.
Just to be clear, I'm not actually advocating recommending 0.8.5
specifically (I thought that's what the
On Wed, Mar 02, 2016 at 03:42:08PM -0600, Alan Mead wrote:
> On 3/2/2016 1:35 PM, Friedrich Beckmann wrote:
> > Am 02.03.2016 um 20:26 schrieb John Darrington
> > :
> >
> > On Wed, Mar 02, 2016 at 07:52:34PM +0100, Friedrich Beckmann wrote:
> >
> > 2 Then, as a first post-release task, let's repla
On 3/2/2016 3:48 AM, Matej Kovacic wrote:
> I mean this is not a decision for a dice. It is a decision the project
> manager shoud do. There should be no democracy here.
Sorry to be late in responding, I didn't see Friedrich's OP (about using
dice to settle the concern about the labeling of untes
Mark,
Maybe you understand this very well, but I think a better way to think
about this is that the PSPP team releases a release of PSPP (which is
source code) and then platform-specific "packagers" release binaries for
their platform, possibly making decisions along the way. For example,
Friedri
Harry, this is helpful Thanks!
-Alan
On 3/2/2016 3:53 PM, Harry Thijssen wrote:
> Hi
>
> First I don't want to be part of the ongoing discussion.
> Just to inform you:
>
> The MSWindows installer displays a readme file on the screen during
> installation.
>
> The second line in this readme b
Hi
First I don't want to be part of the ongoing discussion.
Just to inform you:
The MSWindows installer displays a readme file on the screen during
installation.
The second line in this readme box states:
*This is a new MSWindows build of the PSPP master branch as of the date
this binary was
On 3/2/2016 1:35 PM, Friedrich Beckmann wrote:
> Am 02.03.2016 um 20:26 schrieb John Darrington :
>
> On Wed, Mar 02, 2016 at 07:52:34PM +0100, Friedrich Beckmann wrote:
>
> 2 Then, as a first post-release task, let's replace the existing splash
> screen with an startup window
> which must be ac
I've attached a screenshot of what I think is a much better solution (to
change the website). I think this simple change would alleviate the need
for any messages in the application (though still wouldn't object to
"(unstable)" or "(development)" in the title bar, just not a long
instructional mess
> Am 02.03.2016 um 20:26 schrieb John Darrington :
>
> On Wed, Mar 02, 2016 at 07:52:34PM +0100, Friedrich Beckmann wrote:
>
> 2 Then, as a first post-release task, let's replace the existing splash
> screen with an startup window
> which must be acknowledged. Then we don't need to have any
On Wed, Mar 02, 2016 at 07:52:34PM +0100, Friedrich Beckmann wrote:
> Am 02.03.2016 um 19:44 schrieb Ben Pfaff :
>>
>> Why can't the user see it at startup?
>>
>> The output window is (at least on the window manager I use) below the
data window, unless
>
> Am 02.03.2016 um 20:00 schrieb Ben Pfaff :
>>> Perhaps PSPPIRE should raise the output window, then.
>>
>> That would then be the first really negative functional impact of this
>> warning that John planned.
>> There are good reasons why the windows are raised as they are today.
>
> What are
+1. I agree with every each point of Matej.
(I have no such eloquence as Winston Churchill had.)
Cheers,
Zoltán
On 2016-03-02 10:48, Matej Kovacic wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
What do you think?
Yes, but is it a really true random number generator behind? What
On Wed, Mar 02, 2016 at 07:52:34PM +0100, Friedrich Beckmann wrote:
>
> > Am 02.03.2016 um 19:44 schrieb Ben Pfaff :
> >>
> >> Why can't the user see it at startup?
> >>
> >> The output window is (at least on the window manager I use) below the data
> >> window, unless
> >> explicitly rai
> Am 02.03.2016 um 19:44 schrieb Ben Pfaff :
>>
>> Why can't the user see it at startup?
>>
>> The output window is (at least on the window manager I use) below the data
>> window, unless
>> explicitly raised. Typically, a user will only raise that window, when she
>> explicity
>> has i
On Wed, Mar 02, 2016 at 06:09:16AM +0100, John Darrington wrote:
> On Tue, Mar 01, 2016 at 03:46:52PM -0800, Ben Pfaff wrote:
> On Tue, Mar 01, 2016 at 06:37:49AM +0100, John Darrington wrote:
> > On Sun, Feb 28, 2016 at 10:00:41AM -0800, Ben Pfaff wrote:
> >
> > I su
Hey Matej,
> Yes, but is it a really true random number generator behind? What kind
> of algorithms are used? Or is it used hardware based RNG? If so, which
> provider?
you may convince yourself...: https://www.youtube.com/watch?v=pyH41QXFbUU
and we could watch it via livestream next saturday at
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
> What do you think?
Yes, but is it a really true random number generator behind? What kind
of algorithms are used? Or is it used hardware based RNG? If so, which
provider?
:-)
I mean this is not a decision for a dice. It is a decision the pr
Hi all,
I have the impression that we are now at a point where any solution will piss
off some people, while at the same time the consequences of any solution will
at maximum be minor for all users (can I do more or less with psppire, with any
of the solutions?). So maybe we should let the dice
On Tue, Mar 01, 2016 at 01:47:22AM -0600, Alan Mead wrote:
On 03/01/2016 01:44 AM, Friedrich Beckmann wrote:
>
>>>"This is a development version. It may contain bugs.???
>
>in the title bar? Would you consider this non-scary?
>What about having just
>
>Friedr
On Tue, Mar 01, 2016 at 05:35:57PM -0500, Mark Hancock wrote:
However, I maintain that the title bar is not the right way to warn people
in an interface. Title bars are for application names and information like
filenames.
You may well have a point here. But I would rei
On Tue, Mar 01, 2016 at 03:46:52PM -0800, Ben Pfaff wrote:
On Tue, Mar 01, 2016 at 06:37:49AM +0100, John Darrington wrote:
> On Sun, Feb 28, 2016 at 10:00:41AM -0800, Ben Pfaff wrote:
>
> I suggest putting it into the output window at startup, once. This
is
>
On Tue, Mar 01, 2016 at 06:37:49AM +0100, John Darrington wrote:
> On Sun, Feb 28, 2016 at 10:00:41AM -0800, Ben Pfaff wrote:
>
> I suggest putting it into the output window at startup, once. This is
> easy to do, it is likely that users will notice, and it is not as
> obnoxio
I agree that this sounds less scary (and even just making it not ALL CAPS
would go a long way).
However, I maintain that the title bar is not the right way to warn people
in an interface. Title bars are for application names and information like
filenames.
Currently, the titlebar looks as follows
On 03/01/2016 01:56 AM, Kailash Gajara wrote:
How do I make this mailman list send me only digest email and not all emails
please?
Kailash
Go here:
https://lists.gnu.org/mailman/listinfo/pspp-users
and find near the bottom where it says "To unsubscribe from Pspp-users,
get a password remi
How do I make this mailman list send me only digest email and not all emails
please?
Kailash
> On Mar 1, 2016, at 1:17 PM, Alan Mead wrote:
>
> On 03/01/2016 01:44 AM, Friedrich Beckmann wrote:
>>
"This is a development version. It may contain bugs.“
>>
>> in the title bar? Would you c
On 03/01/2016 01:44 AM, Friedrich Beckmann wrote:
"This is a development version. It may contain bugs.“
in the title bar? Would you consider this non-scary?
What about having just
Friedrich
No, it doesn't seem scary to me; but I hope we continue to be open to
feedback from users. If a sn
> Am 01.03.2016 um 08:33 schrieb Alan Mead :
>
> On 02/29/2016 11:37 PM, John Darrington wrote:
>>
>> How about we implement Ben's suggestion AND have an abridged version of his
>> words
>> on the title-bar?
>>
>> The abridged version could read: "This is a development version. It may
>> cont
On 02/29/2016 11:37 PM, John Darrington wrote:
The wording seems find to me.
I'm not so sure that is will be as noticable as we would like - it will scroll
off the top of the screen after a large output. And in cases like reported
here:
https://lists.gnu.org/archive/html/pspp-users/2
On Sun, Feb 28, 2016 at 10:00:41AM -0800, Ben Pfaff wrote:
I suggest putting it into the output window at startup, once. This is
easy to do, it is likely that users will notice, and it is not as
obnoxious as some of the other options.
For example:
diff --
Doing it the way Ben suggests would not break the regression tests.
On Mon, Feb 29, 2016 at 07:41:10AM -0600, Alan Mead wrote:
On 2/28/2016 12:00 PM, Ben Pfaff wrote:
> I suggest putting it into the output window at startup, once. This is
> easy to do, it is likely that users will
I still think a lot of this can be avoided through better and clearer
messaging when downloading the software, but it is also a good idea to have
a message like this in the output, one time.
The suggested text had a few grammatical errors, though, so here are some
fixes:
This is a development
On 2/29/2016 10:01 AM, Ben Pfaff wrote:
> I don't see why the regression tests would break. For one thing, we
> don't have regression tests for the GUI, which seems to be mostly what
> we're talking about. Second, it would not be hard to disable this
> message for the regression tests (e.g. with --
On Mon, Feb 29, 2016 at 09:57:53AM -0600, Alan Mead wrote:
> On 2/28/2016 12:44 AM, John Darrington wrote:
> > 1. In the output window after each operation.
> >
> >I don't think that is a good idea for several reasons: a) It would
> >break all of our regression tests;
>
> I was referring t
On 2/28/2016 12:44 AM, John Darrington wrote:
> 1. In the output window after each operation.
>
>I don't think that is a good idea for several reasons: a) It would
>break all of our regression tests;
Ben,
I was referring to this. I assumed that John meant that all the
regression tests wou
On Mon, Feb 29, 2016 at 07:41:10AM -0600, Alan Mead wrote:
> On 2/28/2016 12:00 PM, Ben Pfaff wrote:
> > I suggest putting it into the output window at startup, once. This is
> > easy to do, it is likely that users will notice, and it is not as
> > obnoxious as some of the other options.
> > +
> >
On 2/28/2016 12:00 PM, Ben Pfaff wrote:
> I suggest putting it into the output window at startup, once. This is
> easy to do, it is likely that users will notice, and it is not as
> obnoxious as some of the other options.
> +
> + text_item_submit (
> +text_item_create (TEXT_ITEM_PARAGRAPH,
>
On Sun, Feb 28, 2016 at 07:44:33AM +0100, John Darrington wrote:
> On Sat, Feb 27, 2016 at 02:48:54PM -0800, Ben Pfaff wrote:
>
>
> I think that an appropriately worded notice can make all of this clear.
> For example:
>
> This is a development version of PSPP.
On Sat, Feb 27, 2016 at 02:48:54PM -0800, Ben Pfaff wrote:
I think that an appropriately worded notice can make all of this clear.
For example:
This is a development version of PSPP. Please be alert to the
likely possibility that it contain more bugs t
On Fri, Feb 26, 2016 at 07:03:51PM +0100, John Darrington wrote:
> Alan takes the view that users should not be discouraged to try the latest
> git snapshots,
> whereas the decision to add this notice to those snapshots was taken in order
> to ensure
> that users are fully aware of what they are
I would be ok with this warning. I think there should be one.
- ftr
On 26/02/2016 19:55, Matej Kovacic wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
How would it be if we changed this notice to:
"This version is intended for testing purposes only. Please report
any problems."
Wha
Everybody slept already for one or two nights?
> Am 26.02.2016 um 19:03 schrieb John Darrington :
>
> Let's see if we can come to a compromise here.
>
> Alan takes the view that users should not be discouraged to try the latest
> git snapshots,
> whereas the decision to add this notice to thos
On 2/26/2016 12:03 PM, John Darrington wrote:
> Let's see if we can come to a compromise here.
>
> Alan takes the view that users should not be discouraged to try the latest
> git snapshots,
> whereas the decision to add this notice to those snapshots was taken in order
> to ensure
> that users a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
> How would it be if we changed this notice to:
>
> "This version is intended for testing purposes only. Please report
> any problems."
> What do you think?
I think it is a good idea. Maybe even:
"This development version..." or even "This pre-
44 matches
Mail list logo
