In article <20100107142516.GE30054(a)digital-scurf.org&gt;, Daniel Silverstone <dsilvers(a)netsurf-browser.org&gt; wrote: Having a meet up for committee stuff or development planning may be useful. -- Michael Drake (tlsa) http://www.netsurf-browser.org/

On Thu, 07 Jan 2010 23:25:42 +0000, John-Mark Bell wrote: Sounds like a good idea. Has it been decided to drop RISC OS support then, or is this a case of anybody who wants to work on the RISC OS interface has until the show to get treeview working otherwise it gets axed? Chris

On 8 Jan, John-Mark Bell wrote in message <1262994399.1688.221.camel@duiker>: I would be inclined to agree, I'm afraid. The couple of weeks I freed up in November were swallowed up with Wakefield Show work which arrived without warning almost the day after I posted here and came with a tight deadline. That took me up to the regular monthly writing stuff again, and since that was done I've had no time due to non-RISC OS things. I doubt it's news to anyone here (myself included), but there seems little willingness amongst the remaining RISC OS community to actually *do* anything about this. Someone (who I assume was firmly grasping the wrong end of the stick) congratulated me last week on sorting out the NetSurf problem, which gave me the opportunity to suggest that those present could help me get started by taking some of the other RISC OS tasks that could be done in Ovation (so no programming skills required) out of my to-do pile. I don't think I need to describe the response I've had to that suggestion so far. So while I would obviously prefer support for the RISC OS build to continue, I wouldn't suggest that it is allowed to adversely affect other developments. If it becomes pragmatic to drop support in April, then that is the way to go IMHO. It's a shame, but if there are not enough people left now to do everything that needs to be done for the RISC OS platform, that isn't going to change at any time soon. -- Steve Fryatt - Leeds, England http://www.stevefryatt.org.uk/

Hello On 14.01.10, you wrote: I read this """" NetSurf 2.5 is likely to be the last release for RISC OS. It is unlikely that RISC OS development builds will function for much longer after this, either. """" But i guess RiscOS have also SDL so a SDL Port is too easy possible ? I think with enhanced SDL Port, Netsurf can be a easy everywhere browser because no handy or Pocket device is able to run Cairo, Pango and GTK+. Also there is no other browser that is so easy portable as the Netsurf SDL Version. http://www.mail-archive.com/netsurf-users@netsurf-browser.org/msg02500.html Regards

Hello On 14.01.10, you wrote: most time use during surfing extrem selden GUI, important s that the browser show all pages, play videos, let download files, let show and save pictures and type text and let search a page. A spell checker for the textfields is also welcome. The bookmark menu that is standard i dont like, because when have more entries need much scroll time and there is no search function. I think the way of handle bookmark as a page in NetSurf best, there can also in search requester type some letters to find the links.all not work in bookmark menu. same can the page history add as a page in Netsurf.Here can too search.I think this more usable as the hieracrchy list in gui. because when visit lots pages, the best way to find is always a search stringfield.But the GUI listviews menus, do not allow search. and all this can work with SDL Version and it is usable in same way on handy without touchscreen or maybe on a television (when a television Developer maybe NetSurf use) the feature of URL completion i dislike because on browsers(firefox safari ) it happen often that it freeze during type.so i have it switch off, because in 99.9 it make more disadvanatage and the links it suggest are wrong. Regards

Hello On 14.01.10, you wrote: SDL is not too bad, if you want a GUI toolkit, do you know Agar ? Agar run with opengl and also with SDL.Agar is port to Amiga OS and it can maybe too port to RISCOS.But i think change of the framebuffer is then lots work. """"" http://libagar.org/ Agar is a modern open-source, cross-platform toolkit for graphical applications implemented in C, C++, Perl and Ada (with bindings to other languages in development). Designed for ease of integration, it follows the philosophy of building the GUI around the application and not the other way around. Unlike most other GUI toolkits, Agar takes maximum advantage of hardware graphics acceleration when it is available via OpenGL, but it also supports traditional framebuffer interfaces such as SDL direct video. The Agar API is entirely thread-safe when Agar is compiled with optional threads support. """" On amigaos 68k SDL there is not much code add, to get this features working. http://aminet.net/package/comm/www/NetSurf-68k there is not too much miss.What SDL version need is correct working scrollbar and textfields that show cursor and allow move the cursor with mouse or cursor key, a history page that is create as a HTML page and a string gadget to search in a page. All is i think 100* less work as write a complete backend and must alone maintain this.MOS have done a backend that amigaos68k too can with not too much work use, but because the MOS dev seem give up(do since now not the much work to update to new plotter interface), Artur use the maintened SDL Version and compile and enhance, because every newer NetSurf Version can show more pages correct even if the SDL is not so good as the MOS MUI GUI. the window can code resizable in all SDL and SDL 1.3 can support multiple windows too.but for tabs 1 window is enough.see here for code how resize a SDL window.but i dont know how must this done in netsurf and because most pages are width 1024 i need not resize. http://www.gamedev.net/community/forums/topic.asp?topic_id=428022 but ok, thats my last post, i want only information, if there is less develop power on a system, a actual SDL version is maybe better than stay on old Version. Regards

Hello On 14.01.10, you wrote: maybe i can add it to SDL easy, with some help here ? I see in Amiga OS4 Version the flag IDCMP_NEWSIZE is active, but i dont see the codeplace where it tell netsurf that the window size is change. When a message from SDL is recieve that the window is resize the x and y size of window is return, but i dont know how can i tell NetSurf that the window size is change and should rerender the display ? Regards

Hello On 15.01.10, you wrote: The Amiga OS4 Version use a own OS specific backend and no SDL, so it go the prefered way, and it should be possible.But i dont see how. first you tell no resizing as disadvantage of the SDL Version then you tell SDL should not support this.I cant understand that. If somebody not want the feature there can of course a define to switch it off. Regards

Hello On 15.01.10, you wrote: I think it is too difficult and need lots time for me.I need only look in the amigaos Folder and the filesize and how often Chris add code to SVN.I guess he work more than 500 hours on it yet. So when i have maybe 10 hours/month time to code on netsurf, then 500 hours are reach in 5 years.I dont have the patience to do a 5 year project.And when not have enough time. then the train is loose. luckily the SDL Netsurf miss not too much features so it can use without much work. I think btw write of a XUL backend for Firefox (which is btw availaible for the common used AOS GUI System MUI)can do in less work and firefox can show more pages(java frames).So when there is Netsurf in future not working with SDL, i try better to get this working. On amigaos there are no browsers that have CSS, but there are browsers with some limit java script and working frames.ome pages NetSurf can show better some pages can work with amiga browsers, (but they look ugly) A great reason to use Netsurf or help on code is when it is easy and fast compileable and keep upto date. and thats now possible with SDL. Luckily i need not resize window, i also do not resize window when i use firefox on windows, because when i make a win smaller than 1024 i need scroll. I have only a AMD64 3000+ (with real 1,8 GHZ)X86 CPU, here compile firefox or OWB because of C++ over 50 minutes i think.And when port it, and change headers,then much need recompile. netsurf compile in only 45 sec and here make much more fun to keep it upto date, than on this C++ monsters where need wait long time after every change. And when the Netsurf come out with Cache i like test too. Regards

Hello On 15.01.10, you wrote: where is a windows Version binary of NetSurf ? Regards

Something like: http://source.netsurf-browser.org/branches/MarkieB/windows/ it seems... François.

On Sat, 16 Jan 2010 10:54:57 +0200 Bernd Roesch <nospamname(a)gmx.de&gt; wrote: Just install MinGW and build with that. I believe it can be built under Windows or Linux using it. B.

In article <yam11702.960.283422120(a)mail.gmx.net&gt;, Bernd Roesch <nospamname(a)gmx.de&gt; wrote: I think you have missed the point of the framebuffer front end. It is intended for use on fixed-sized framebuffers (e.g. the Linux framebuffer, or the ABLE framebuffer) and would be used fullscreen, as the only program running on the system. In addition to the Linux and ABLE framebuffer implementations there is also an SDL framebuffer implementation. This was created to simplify the process of developing NetSurf's framebuffer front end. If it's useful to anyone as more than a debug and testing aid, then that's a bonus. It doesn't matter that SDL can support window size changes. The point is there is no NetSurf front end targeting SDL, only a front end targeting simple framebuffers that happens to have an implementation in SDL. So, since the framebuffer front end is designed as a straightforward front end for fixed-size framebuffers, it does not matter whether SDL can support window resizing -- the functionality is simply not provided though the framebuffer front end. -- Michael Drake (tlsa) http://www.netsurf-browser.org/

On Thu, 7 Jan 2010 23:28:14 +0000 Steve Fryatt <lists(a)stevefryatt.org.uk&gt; wrote: The typesetting is often right somewhere, and always wrong somewhere else. I think it's been the exhibitor badges and our entry on the website for the past few years, rather than the printed guide. B.

On Fri, 8 Jan 2010 00:02:02 +0000 Steve Fryatt <lists(a)stevefryatt.org.uk&gt; wrote: Nod; knowing who to contact when errors are uncovered is certainly useful! Thanks. B.