Dave Lawton wrote on 5 Jul:
> You need to 'Login', then you will find a 'Create Ticket'
> button has been added on the LHS.
Maybe this useful info could be added to Netsurf's own help page --
http://www.netsurf-browser.org/documentation/info -- which tells you
how to report a bug. (Is this page wiki-editable or is it only the
Netsurf team who can do it? A link direct to the relevant point in
Sourceforge would be welcome.)
I've just finished floundering my way through the Sourceforge process
before discovering this thread on the mailinglist. Am still unsure
whether my report got posted on Sourceforge or not or twice. Its
"Preview" button didn't give any reassurance.
And, while on the subject of Sourceforge, does its print really need
to be so tiny, given the acres of white space? And does the print
need to be grey rather than black? (Is this grey a current fashion
among website designers or is it my eyesight?!? If grey, I presume it
is controlled by something in CSS.)
--
Jim Nagel www.archivemag.co.uk
>> before emailing large files (>1Mb), please ask me for FTP details
See you at Kenilworth? www.mug.riscos.org/show13 July 13
Friday, 5 July 2013
Re: Sourceforge
On Fri, Jul 05, 2013 at 12:52:51PM +0100, Peter Young wrote:
> Presumably this means that people without a Sourceforge account can't
> submit bug reports any more, which is a pity,
At least we get identifying marks and a way to contact the author with every
bug report now though.
D.
--
Daniel Silverstone http://www.netsurf-browser.org/
PGP mail accepted and encouraged. Key Id: 3CCE BABE 206C 3B69
> Presumably this means that people without a Sourceforge account can't
> submit bug reports any more, which is a pity,
At least we get identifying marks and a way to contact the author with every
bug report now though.
D.
--
Daniel Silverstone http://www.netsurf-browser.org/
PGP mail accepted and encouraged. Key Id: 3CCE BABE 206C 3B69
Re: Sourceforge
On 5 Jul 2013 "Dave Lawton" <lists@etcsystems.co.uk> wrote:
> On Fri, 5 July, 2013 12:03 pm, Peter Young wrote:
>> On 5 Jul 2013 Richard Porter <ricp@minijem.plus.com> wrote:
>>
>>> What's happened to Sourceforge? It's virtually unusable now. The
>>> help
>>> page tells me to click on "Submit new" but it's nowhere to be found
>>> on
>>> the bugs page.
>>
>> I don't know if you're seeing the same thing as I am, but the URL
>> https://sourceforge.net/tracker/?func=add&group_id=51719&atid=464312
>> used to take you to the "add a bug" page (Can't remember what the
>> correct name is), but it now takes you to the list of bugs instead.
>> This has, as you say, no obvious way of adding a bug.
>>
>> I did try this URL in Windows Firefox, and the same thing happens
>> there.
>>
>> Is there a way we can help the developers by reporting bugs now?
>>
>> With best wishes,
>>
>> Peter.
>>
> Hi,
> You need to 'Login', then you will find a 'Create Ticket'
> button has been added on the LHS.
So there is! I did try logging in to see if it made a difference, but
didn't notice the "Create ticket".
Presumably this means that people without a Sourceforge account can't
submit bug reports any more, which is a pity,
At least they now have "Save" instead of that awful "Add artifact"!
With best wishes,
Peter.
--
Peter Young (zfc Ta) and family
Prestbury, Cheltenham, Glos. GL52, England
http://pnyoung.orpheusweb.co.uk
pnyoung@ormail.co.uk
> On Fri, 5 July, 2013 12:03 pm, Peter Young wrote:
>> On 5 Jul 2013 Richard Porter <ricp@minijem.plus.com> wrote:
>>
>>> What's happened to Sourceforge? It's virtually unusable now. The
>>> help
>>> page tells me to click on "Submit new" but it's nowhere to be found
>>> on
>>> the bugs page.
>>
>> I don't know if you're seeing the same thing as I am, but the URL
>> https://sourceforge.net/tracker/?func=add&group_id=51719&atid=464312
>> used to take you to the "add a bug" page (Can't remember what the
>> correct name is), but it now takes you to the list of bugs instead.
>> This has, as you say, no obvious way of adding a bug.
>>
>> I did try this URL in Windows Firefox, and the same thing happens
>> there.
>>
>> Is there a way we can help the developers by reporting bugs now?
>>
>> With best wishes,
>>
>> Peter.
>>
> Hi,
> You need to 'Login', then you will find a 'Create Ticket'
> button has been added on the LHS.
So there is! I did try logging in to see if it made a difference, but
didn't notice the "Create ticket".
Presumably this means that people without a Sourceforge account can't
submit bug reports any more, which is a pity,
At least they now have "Save" instead of that awful "Add artifact"!
With best wishes,
Peter.
--
Peter Young (zfc Ta) and family
Prestbury, Cheltenham, Glos. GL52, England
http://pnyoung.orpheusweb.co.uk
pnyoung@ormail.co.uk
Re: Sourceforge
On Fri, 5 July, 2013 12:03 pm, Peter Young wrote:
> On 5 Jul 2013 Richard Porter <ricp@minijem.plus.com> wrote:
>
>> What's happened to Sourceforge? It's virtually unusable now. The
>> help
>> page tells me to click on "Submit new" but it's nowhere to be found
>> on
>> the bugs page.
>
> I don't know if you're seeing the same thing as I am, but the URL
> https://sourceforge.net/tracker/?func=add&group_id=51719&atid=464312
> used to take you to the "add a bug" page (Can't remember what the
> correct name is), but it now takes you to the list of bugs instead.
> This has, as you say, no obvious way of adding a bug.
>
> I did try this URL in Windows Firefox, and the same thing happens
> there.
>
> Is there a way we can help the developers by reporting bugs now?
>
> With best wishes,
>
> Peter.
>
Hi,
You need to 'Login', then you will find a 'Create Ticket'
button has been added on the LHS.
HTH
--
Regards,
Dave Lawton
HTML emails are just a security risk, and nobody needs that.
> On 5 Jul 2013 Richard Porter <ricp@minijem.plus.com> wrote:
>
>> What's happened to Sourceforge? It's virtually unusable now. The
>> help
>> page tells me to click on "Submit new" but it's nowhere to be found
>> on
>> the bugs page.
>
> I don't know if you're seeing the same thing as I am, but the URL
> https://sourceforge.net/tracker/?func=add&group_id=51719&atid=464312
> used to take you to the "add a bug" page (Can't remember what the
> correct name is), but it now takes you to the list of bugs instead.
> This has, as you say, no obvious way of adding a bug.
>
> I did try this URL in Windows Firefox, and the same thing happens
> there.
>
> Is there a way we can help the developers by reporting bugs now?
>
> With best wishes,
>
> Peter.
>
Hi,
You need to 'Login', then you will find a 'Create Ticket'
button has been added on the LHS.
HTH
--
Regards,
Dave Lawton
HTML emails are just a security risk, and nobody needs that.
Re: Sourceforge
On 5 Jul 2013 Richard Porter <ricp@minijem.plus.com> wrote:
> What's happened to Sourceforge? It's virtually unusable now. The help
> page tells me to click on "Submit new" but it's nowhere to be found on
> the bugs page.
I don't know if you're seeing the same thing as I am, but the URL
https://sourceforge.net/tracker/?func=add&group_id=51719&atid=464312
used to take you to the "add a bug" page (Can't remember what the
correct name is), but it now takes you to the list of bugs instead.
This has, as you say, no obvious way of adding a bug.
I did try this URL in Windows Firefox, and the same thing happens
there.
Is there a way we can help the developers by reporting bugs now?
With best wishes,
Peter.
--
Peter Young (zfc Ta) and family
Prestbury, Cheltenham, Glos. GL52, England
http://pnyoung.orpheusweb.co.uk
pnyoung@ormail.co.uk
> What's happened to Sourceforge? It's virtually unusable now. The help
> page tells me to click on "Submit new" but it's nowhere to be found on
> the bugs page.
I don't know if you're seeing the same thing as I am, but the URL
https://sourceforge.net/tracker/?func=add&group_id=51719&atid=464312
used to take you to the "add a bug" page (Can't remember what the
correct name is), but it now takes you to the list of bugs instead.
This has, as you say, no obvious way of adding a bug.
I did try this URL in Windows Firefox, and the same thing happens
there.
Is there a way we can help the developers by reporting bugs now?
With best wishes,
Peter.
--
Peter Young (zfc Ta) and family
Prestbury, Cheltenham, Glos. GL52, England
http://pnyoung.orpheusweb.co.uk
pnyoung@ormail.co.uk
Sourceforge
What's happened to Sourceforge? It's virtually unusable now. The help
page tells me to click on "Submit new" but it's nowhere to be found on
the bugs page.
--
Richard Porter http://www.minijem.plus.com/
mailto:ricp@minijem.plus.com
I don't want a "user experience" - I just want stuff that works.
page tells me to click on "Submit new" but it's nowhere to be found on
the bugs page.
--
Richard Porter http://www.minijem.plus.com/
mailto:ricp@minijem.plus.com
I don't want a "user experience" - I just want stuff that works.
Monday, 1 July 2013
New treeview
Since the old treeview was inefficient, a bit flaky, and difficult to
maintain, we've been planning to replace it for some time.
I have a treeview rewrite in progress which is quite advanced, and I've
just pushed what I have done so far. Currently this is a new generic
treeview module, a partial new global history module, and a hack in the
old treeview for testing the new one.
To see the new treeview in action, either set temp_treeview_test:1 in the
Chocies file, or pass --temp_treeview_test=1 when you execute NetSurf.
With this option set, the global history treeview test can be found in the
hotlist/bookmarks/favourites window. You can have the old and new global
history treeviews open side-by-side.
Any feedback welcome.
A few more notes follow.
Performance
-----------
On a 600MHz XScale, the new global history treeview builds much faster
with my current 326kB of URL file.
New treeview:
(2.440000) desktop/global_history.c global_history_init 657: Loading
global history
(2.600000) desktop/global_history.c global_history_init 709: Loaded
global history
Old treeview:
(2.690000) desktop/history_global_core.c history_global_initialise 281:
Building history tree
(4.020000) desktop/history_global_core.c history_global_initialise 288:
History tree built
That's 0.16s vs. 1.33s. The new one is probably fast enough that we could
get away with making the global history treeview when the global history
window is opened, rather than generating on startup.
RISC OS treeview drags
----------------------
Seems that the RISC OS front end doesn't pass the mouse coordinate to the
core during drags in the treeview window, which is making the drag
behaviour there a bit peculiar.
Treeview behaviour
------------------
Single click on the expand/contract arrow toggles its expansion.
Single click on text/icon selects it.
Double click on a directory toggles its expansion.
Double click on an entry will "launch" it.*
Drag from an empty area starts a selection.
Drag from text/icon region will start a move drag.
Drag from anywhere in a selection will start a move drag.
First mouse button creates new selection.
Second mouse button modifies a selection.
Keyboard shortcuts for select all, clear selection, and delete selection
are implemented.
* Global history doesn't implement the launch callback msg yet.
Global history TODO
-------------------
- Need to implement launch message handling
- Need to implement node deletion message handling (so the delete actually
affects URLdb)
- Need to make browser window update the new global history code as you
visit pages.
What next
---------
1. Get some feedback.
2. Address feedback.
3. Finish new global history.
4. Change global history to use new treeview, removing temp test option.
5. Implement bookmarks, ssl cert chain viewer and cookie manager
with new treeview. Need to add various features to the treeview,
such as read-only mode, node movement drags, etc.
Up to and including step 5, there will be no changes in the front ends...
the old tree stuff will be wrapper layers for the new stuff.
6. Change front ends to use new treeview stuff directly.
Somewhere before step 6, I intend to change the interface for the using
the new treeview features a bit (core_window stuff).
Cheers,
--
Michael Drake (tlsa) http://www.netsurf-browser.org/
maintain, we've been planning to replace it for some time.
I have a treeview rewrite in progress which is quite advanced, and I've
just pushed what I have done so far. Currently this is a new generic
treeview module, a partial new global history module, and a hack in the
old treeview for testing the new one.
To see the new treeview in action, either set temp_treeview_test:1 in the
Chocies file, or pass --temp_treeview_test=1 when you execute NetSurf.
With this option set, the global history treeview test can be found in the
hotlist/bookmarks/favourites window. You can have the old and new global
history treeviews open side-by-side.
Any feedback welcome.
A few more notes follow.
Performance
-----------
On a 600MHz XScale, the new global history treeview builds much faster
with my current 326kB of URL file.
New treeview:
(2.440000) desktop/global_history.c global_history_init 657: Loading
global history
(2.600000) desktop/global_history.c global_history_init 709: Loaded
global history
Old treeview:
(2.690000) desktop/history_global_core.c history_global_initialise 281:
Building history tree
(4.020000) desktop/history_global_core.c history_global_initialise 288:
History tree built
That's 0.16s vs. 1.33s. The new one is probably fast enough that we could
get away with making the global history treeview when the global history
window is opened, rather than generating on startup.
RISC OS treeview drags
----------------------
Seems that the RISC OS front end doesn't pass the mouse coordinate to the
core during drags in the treeview window, which is making the drag
behaviour there a bit peculiar.
Treeview behaviour
------------------
Single click on the expand/contract arrow toggles its expansion.
Single click on text/icon selects it.
Double click on a directory toggles its expansion.
Double click on an entry will "launch" it.*
Drag from an empty area starts a selection.
Drag from text/icon region will start a move drag.
Drag from anywhere in a selection will start a move drag.
First mouse button creates new selection.
Second mouse button modifies a selection.
Keyboard shortcuts for select all, clear selection, and delete selection
are implemented.
* Global history doesn't implement the launch callback msg yet.
Global history TODO
-------------------
- Need to implement launch message handling
- Need to implement node deletion message handling (so the delete actually
affects URLdb)
- Need to make browser window update the new global history code as you
visit pages.
What next
---------
1. Get some feedback.
2. Address feedback.
3. Finish new global history.
4. Change global history to use new treeview, removing temp test option.
5. Implement bookmarks, ssl cert chain viewer and cookie manager
with new treeview. Need to add various features to the treeview,
such as read-only mode, node movement drags, etc.
Up to and including step 5, there will be no changes in the front ends...
the old tree stuff will be wrapper layers for the new stuff.
6. Change front ends to use new treeview stuff directly.
Somewhere before step 6, I intend to change the interface for the using
the new treeview features a bit (core_window stuff).
Cheers,
--
Michael Drake (tlsa) http://www.netsurf-browser.org/
Subscribe to:
Posts (Atom)