@Thomas
Aha got it. As for proper bug-report we lately discuss it on aw.net (check plz
that thread, troll-free, so worth to check) and currently seems goint nowhere with making proper and good bug report. Hope soon we can understand the roots and make a proper report.
I also install it on SFS, and do some tests:
-- seems its now reacts faster, and even scrolls a bit faster
-- new ASL requester are good
-- trying to type "
file:///work:" , and it start to show my content, but then, just stick for a while and then crashes with pointing on the bsdsocket.library. I do tests without actual network connection, so maybe TW trying to send/recv somthing , and when can't fail to load even
file:///work:. Through, with previous beta it opens without crashes.
Also i trying just for fun, run TW from SFS, while system partiiong are FFS (so font files and fontconfig are on FFS), and its take i think .. about 10 minutes to generate font config ! While if i have SFS as system partition it generates more or less fast. Maybe worth to add to the readme something like "don't use FFS at all if you want to use TW normally, first run will take ages !". Of course preferable will be just get rid off of fontconfig at all (as Joerg do with his Ra-OWB back in past), but i think its hard and annoing work ..
Quote:
and I'm not sure that RAM-handler supports the necessary file system features (In fact, I'm quite sure it doesn't)
It is worth to add necessary features to ram-handler ? I mean there is no stop-factors to doing so, just need update ram-handler more ?
Quote:
Update: Please report bugs here
I put some report already.
Also seems bookmarking works now.
Curently, the most annoing moments its slownes of startup and whole scroll/redrawing/responses. On pegasos2 it takes about 15 seconds for start till usable "about page" from SFS. In compare with 3.5 beta, which starts if i remember right just in few seconds (about 5 maximum) on the same setup.
Edited by kas1e on 2012/3/28 15:00:32