On Sunday 22 November 2009, John Ralls wrote:
> Both valid points, thanks. I think that the appearance of
> "MacOSX/2.2.9/Readme" is a helpful cue to anyone who's spent much time with
> computers, even if it doesn't actually create a hierarchy on the file
> system. Both that and MacOSX/2.3.7/Readme
On Nov 22, 2009, at 12:04 PM, Christian Stimming wrote:
> Two minor points to keep in mind when comparing a Wiki page to a plain HTML
> file:
>
> Am Donnerstag, 19. November 2009 schrieb John Ralls:
>> The wiki page would become the primary; converting it to html is easily
>> done by opening it
Two minor points to keep in mind when comparing a Wiki page to a plain HTML
file:
Am Donnerstag, 19. November 2009 schrieb John Ralls:
> The wiki page would become the primary; converting it to html is easily
> done by opening it in the browser and saving it (or downloading it via
> curl).
The
On Nov 19, 2009, at 1:53 PM, Geert Janssens wrote:
> Personally I think it would be better in the long run if the files were
> referring to the release they are written for, so for example:
> MacOSX/Readme/2.2.9
> and
> MacOSX/Readme/2.3.7
>
> I don't have experience with the SF file manager (I
On Thursday 19 November 2009, John Ralls wrote:
>
> The wiki page would become the primary; converting it to html is easily
> done by opening it in the browser and saving it (or downloading it via
> curl). Not a significant change in effort, really. It has the advantage
> that it could be easily up
On Nov 19, 2009, at 8:04 AM, Geert Janssens wrote:
> On Thursday 19 November 2009, John Ralls wrote:
>> On Nov 19, 2009, at 5:31 AM, Derek Atkins wrote:
>>> Fair enough. I'm just trying to think of how to make it available in a
>>> way that's NOT a link off to a SF page. Maybe a link to the wik
On Thursday 19 November 2009, John Ralls wrote:
> On Nov 19, 2009, at 5:31 AM, Derek Atkins wrote:
> > Fair enough. I'm just trying to think of how to make it available in a
> > way that's NOT a link off to a SF page. Maybe a link to the wiki?
>
> I thought that Geert had set it up to be a hosted
On Nov 19, 2009, at 5:31 AM, Derek Atkins wrote:
>
> Fair enough. I'm just trying to think of how to make it available in a
> way that's NOT a link off to a SF page. Maybe a link to the wiki?
I thought that Geert had set it up to be a hosted file (he mentioned
osx_readme.phtml being missing
John Ralls writes:
> On Nov 18, 2009, at 9:32 AM, Derek Atkins wrote:
>
>> John,
>>
>>
>> How about if you put it into the installer itself so that it pops up
>> when they attempt to install it?
>>
>
> There is no installer. You download the dmg (which is a disk image, like an
> iso), mount i
On Nov 18, 2009, at 9:32 AM, Derek Atkins wrote:
> John,
>
>
> How about if you put it into the installer itself so that it pops up
> when they attempt to install it?
>
There is no installer. You download the dmg (which is a disk image, like an
iso), mount it (most browsers will do that auto
Am Mittwoch, 18. November 2009 schrieb Derek Atkins:
> John,
>
> John Ralls writes:
> > I can live with any of those options as long as the result is easy for
> > the impatient new user to find and read the file.
> >
> > Yes, it's true that the file is "additional release notes", but users
> > ge
John,
John Ralls writes:
> I can live with any of those options as long as the result is easy for
> the impatient new user to find and read the file.
>
> Yes, it's true that the file is "additional release notes", but users
> generally don't read release notes, and I want the users to read this
On Nov 16, 2009, at 5:19 AM, Geert Janssens wrote:
...
Question 2. Where to fetch the Mac OS X Readme file ?
This file is currently hosted on sourceforge and the www.gnucash.org
website
links to it there. However, due to the sourceforge website works, it
will
first show a download page (wi
Zitat von Geert Janssens :
Question 2. Where to fetch the Mac OS X Readme file ?
Different solutions I see:
* Leave it as is, just live with the redirect.
* Setup a "Release notes" section in wiki, store all release relevant
information (release notes, changelog, readmes) there and link there. A
Zitat von Geert Janssens :
Question 3. Release timing
While setting up the download block on the front page, I presumed that a new
stable release is always made available for the three major platforms at the
same time. That's what the block also indicates: it states in big
letters what
the cu
John Ralls writes:
> On Nov 14, 2009, at 7:35 PM, Derek Atkins wrote:
>
>>
>> Why do we have separate per-release Readme files? I can understand a
>> different readme for 2.2 vs. 2.3, and a CHANGELOG per release, but
>> why a
>> full separate readme per package? That seems overkill to me.
>>
>
On Nov 14, 2009, at 7:35 PM, Derek Atkins wrote:
Why do we have separate per-release Readme files? I can understand a
different readme for 2.2 vs. 2.3, and a CHANGELOG per release, but
why a
full separate readme per package? That seems overkill to me.
Because Gnucash on OSX is neither
Geert Janssens writes:
> On Friday 13 November 2009, John Ralls wrote:
>> I got the same results.
>>
>> Interestingly, if I copy the contents of your page into a file and
>> display the file in Firefox, I don't get the redirect screen either.
>> That suggests that it's neither cookie magic (since
John,
John Ralls writes:
> The magic link is:
> http://downloads.sourceforge.net/sourceforge/gnucash/Gnucash%20OSX%20Readme.html
>
> That will magically find the best (or user's default, if he's got a
> sourceforge account and has it set up) mirror and doesn't flash the
> mirror screen. It works
"Stephen R. Besch" writes:
> Small suggestions:
>
> 1) List Linux download first. Putting Windows first and prominent
> suggests that this is a windows development effort with a port to
> linux, rather than the other way around.
Sure. Linux, Mac, Windows.
> 2) Add svn address (http://svn.gnuca
On Friday 13 November 2009, John Ralls wrote:
> I got the same results.
>
> Interestingly, if I copy the contents of your page into a file and
> display the file in Firefox, I don't get the redirect screen either.
> That suggests that it's neither cookie magic (since the only cookies
> it can see w
On Friday 13 November 2009, t...@filmchicago.org wrote:
> The php option you could try is to have the link initially link to a local
> page which would then redirect the user with the php function:
>
> header('Location: http://filelink');
> exit;
> ?>
>
> Note that the header function must be used
On Nov 13, 2009, at 1:38 AM, Geert Janssens wrote:
On Thursday 12 November 2009, Geert Janssens wrote:
Sourceforge is working again, so I tested these new links.
They work fine, but there is some weirdness going on with the mirror
screen.
When I click on a link on my new download page, I
int® Now Network from my BlackBerry®
-Original Message-
From: Geert Janssens
Date: Fri, 13 Nov 2009 16:34:28
To:
Subject: Re: Website download section
On Friday 13 November 2009, t...@filmchicago.org wrote:
> For the readme have you tried seeing what happens if you have the link open
Message-
From: Geert Janssens
Date: Fri, 13 Nov 2009 16:34:28
To:
Subject: Re: Website download section
On Friday 13 November 2009, t...@filmchicago.org wrote:
> For the readme have you tried seeing what happens if you have the link open
> in a new window?
>
> It will probably be
to open it right-click->Open in new window, yes. It made no
difference indeed.
Geert
> --Original Message--
> From: Geert Janssens
> Sender: gnucash-devel-boun...@gnucash.org
> To: gnucash-devel@gnucash.org
> Subject: Re: Website download section
> Sent: Nov 13,
ucash-devel@gnucash.org
Subject: Re: Website download section
Sent: Nov 13, 2009 7:43 AM
On Friday 13 November 2009, Tim M wrote:
> Geert, I do see what you are saying about the links.
>
> However, to be honest I don't think the download links should be bypassing
> the download
On Friday 13 November 2009, Tim M wrote:
> Geert, I do see what you are saying about the links.
>
> However, to be honest I don't think the download links should be bypassing
> the download screen of Sourceforge anyway, especially for the binaries and
> source code. The HTML Readme is a tiny file
Geert, I do see what you are saying about the links.
However, to be honest I don't think the download links should be bypassing
the download screen of Sourceforge anyway, especially for the binaries and
source code. The HTML Readme is a tiny file on the other hand, so IMO it's
not a big deal if i
On Thursday 12 November 2009, Geert Janssens wrote:
> On Thursday 12 November 2009, John Ralls wrote:
> > The magic link is:
> > http://downloads.sourceforge.net/sourceforge/gnucash/Gnucash%20OSX%20Read
> >me .html
> >
> > That will magically find the best (or user's default, if he's got a
> > sour
On Thursday 12 November 2009, Christian Stimming wrote:
> Am Donnerstag, 12. November 2009 schrieb Geert Janssens:
>
> > * The original site had links to a USA and a European sourcecode-only
> > "mirror" (for the lack of a better word). I have added those to the
> > source code section on the down
On Thursday 12 November 2009, John Ralls wrote:
>
> The magic link is:
> http://downloads.sourceforge.net/sourceforge/gnucash/Gnucash%20OSX%20Readme
>.html
>
> That will magically find the best (or user's default, if he's got a
> sourceforge account and has it set up) mirror and doesn't flash the
>
Am Donnerstag, 12. November 2009 schrieb Geert Janssens:
> To see the intermediate result, surf to:
> http://www.kobaltwit.be/gnucash/index.phtml
Looks very good!
> * Added a new page for downloading. (...)
> - direct one-click links to the installers we have available,
> - information on how
On Nov 12, 2009, at 8:54 AM, Geert Janssens wrote:
Apparently I can do this if I put a direct link to one of the
download mirrors
instead of the main download server. It seems the main download
server is
configured to redirect to a mirror at all times. It's this
redirection that
shows the
On Thursday 12 November 2009, Geert Janssens wrote:
>
>
> What I have not done yet:
> * Fix the release news items
I have made some changes to the 2.3.7 news item:
* include a very visible warning box
* added a similar box to inform users about the latest stable release. The
icons from both these
On Thursday 12 November 2009, Stephen R. Besch wrote:
> Small suggestions:
>
> 1) List Linux download first. Putting Windows first and prominent
> suggests that this is a windows development effort with a port to linux,
> rather than the other way around.
>
Yes, I did have the same impression. Howe
On Nov 12, 2009, at 7:18 AM, Geert Janssens wrote:
I have made some progress with my proposals.
To see the intermediate result, surf to:
http://www.kobaltwit.be/gnucash/index.phtml
(Just ignore the php safe mode warnings. They are caused by my hosting
provider but not relevant for the changes
Small suggestions:
1) List Linux download first. Putting Windows first and prominent
suggests that this is a windows development effort with a port to linux,
rather than the other way around.
2) Add svn address (http://svn.gnucash.org/repo/gnucash/trunk) to the
getting GnuCash part of the ne
Looks nice!
Sent on the Sprint® Now Network from my BlackBerry®
-Original Message-
From: Geert Janssens
Date: Thu, 12 Nov 2009 16:18:51
To:
Subject: Website download section
I have made some progress with my proposals.
To see the intermediate result, surf to:
http://www.kobaltwit.be
39 matches
Mail list logo
