cga2000 <[EMAIL PROTECTED]> wrote Tue, Jun 06, 2006: > On Tue, Jun 06, 2006 at 05:33:05AM EDT, Jonas Fonseca wrote: > > > Someone posted a patch for something like this, using the X libraries. > > It never was polished to a degree where it was worth merging, tho'. > > Interesting. Obviously 64k or 16M different colors doesn't make much > difference. None that I can see anyway. I asked the xterm maintainer how > the 256-color palette was chosen but he did not give me much detail. My > personal concern was that the default xterm palette has very few blues. > So if you try to harmonize the contents of an xterm with for instance > the default background of Window Maker (I call it WindowMaker blue) you > don't find an xterm color that is anywhere near. That's when I started > taking an interest in these aspects.
I know next to nothing about how good it works. It has been there since I joined the project. BTW, I have a little script that prints out all the nice colors: http://jonas.nitro.dk/tmp/256.sh ... > > Sorry, that I was not clear. I am talking about using JavaScript for > > browser scripting, not document scripting. > > Ok. I need to add JavaScript to the list of things I must look into. > I'll check and see if there is an online tutorial available somewhere. I see, that Miciah might be putting some API docs of SMJS browser scripting together. Else .js files in contrib/smjs/ should be a help. JavaScript is a fairly simple language where many things works "as expected". > > That is, using JavaScript > > to define hooks that can handle stuff from the goto URL dialog or > > preformat the HTML source. > > Yes, but I do need it for page rendering as well..? Especially those > home pages that have some sort of horizontal menu bar that ends up a > vertical list of links in my setup? That is usually controlled by CSS (another area where ELinks is falling behind). CSS let's you define that the tag <p> which is otherwise a block element (that should start on a new separate line, or paragraph if you will) is instead an inline element, where multiple <p> tags should appear on one line. Bad description, but I hope you get the point. > > I have some (mostly 256 related) at http://jonas.nitro.dk/screenshots/ > > I had looked at these a few weeks back. I took another look while > writing this and now I see things I didn't see back then. I compared > those sites that are still around such as OSTG, OSDN, slashdot.. and > it's obvious I'm not quite there yet.. Well, with slashdot's new design (they went away from table-based design to CSS-powered design) it looks broken in my ELinks too. :( So many difference might be because of changes to the website and ELinks lack of CSS support. Not that it makes it easier for you. > > Screenshots sells, I agree. Although most apps are easily downloaded, > > configured and installed, the first appearance by which you make the > > decision whether to even bother with all that may often be a > > screenshot. And properly more so for something as seemingly > > "out-dated" as a text-mode browser. > > What would be nice is to have the web pages and the screenshots. > Because even if the site still exists six months from now the > contents.. or even the page design.. are going to be different. Thus if > the new user has the html document and the .png .. when he wants to make > sure his configuration is optimal he just needs to point elinks to the > web document and compare with the screenshot. He might need to change > his font to the one that was used when the the screenshot was taken but > otherwise it should be pretty painless? Yes, this would guard against "deceptive" screenshots like the /. screenshot above. > > > I don't know if it's realistic/possible but it might be a good idea > > > to have elinks "test pages" .. you go to the test page and if you're > > > set up right you should see this.. and a link to a screenshot. > > > > It's certainly a new approach to a more visual tutorial and might suit > > ELinks better than the poor introduction we have now. On the other > > hand I wonder if most users of text-mode browser is this "visually > > oriented". But then again, Links2 has this calibration page to help > > you get the basics working and that is of course a great help. > > thanks, "calibration" is pretty much what I had in mind. And it should > remain pretty simple. Just giving the new user the ability to verify > that web pages are rendering correctly. As to a tutorial I don't really > see the need for one. As long as a default configuration is provided the > user can learn the basics of elinks by just using it. Same as any gui > app. Call it tips and tricks or cheat sheet instead of tutorial. But yes, "learning while using" makes the learning experience feel less steep. One thing to put in these test pages would be the bottom table in test/css/styletags.html maybe with a "4ever" appended ... ;) > > BTW, being new to ELinks, you should go over contrib/elinks.fortune, > > there's some good tips and tricks in it. > > practically everything that's in this file, I already use without > thinking. But then it was easy for me to find these tricks just > reviewing the contents of the elinks menus.. because I was looking for > these capabilities in the first place. The fact that they are available > in elinks being possibly the main reason why I switched. If they hadn't > been available I would not be using elinks now. That's good to hear. > actually, there's one thing I hadn't found by myself and that's the > Ctrl-W to bring up a history of links on the 'g' goto dialog.. *and* the > popup list is searchable..! How do I repeat the search? Currently previous menu searches are not added to the search history. Maybe they should. > > I am still mousing my way through mozilla. Well, apart from when I start > > pounding the Tab key to get to some link. :-P > > Mozilla has a very nice "search as you type" feature where - provided > the cursor is not in a data entry field you just need to type the link's > text to select the link. I prefer it to numbered links (I'm pretty sure > there is a mozilla patch that enables this) or elinks' typeahead search > (because you don't need a keyboard actions such as '#' to enable this > mode in mozilla). It's configurable somewhere under Edit->Preference - > you can search any text or just links.. You would use Ctrl+g to repeat > the search and ' (single quote) to start a new search before the timer > expires. With a bit of practice you get to do it without thinking (= no > overhead) because you are reading the links' text so doing it becomes a > second nature. Instead of reading the link aloud or mentally you type > it.. The only problem is with pages that force the cursor to a text > entry field (search usually). That.. I understand, is yet another > JavaScript trick and quite annoying. Fortunately it's limited to the > home pages of commercial sites. Thanks for the moz tricks. Having to press '#' to enter typeahead is pretty much a necessity when so many default keybindings are assigned to "unmodded" keys (not guarded by Ctrl- or Alt-) which again is much nicer for general usage. > > > 3. Because elinks is a text-mode browser I don't have to put up with all > > > the distractions.. click here and there to block all this commercial > > > shockflash stuff .. with mozilla it usually takes a minute or more > > > before I have enough peace and quiet and then I am able to (re)focus and > > > actually start reading. With elinks, I can choose to display a picture > > > when I want/need it. Freedom, you know.. > > > > On the otherhand you don't get to experience the tasty new slashdot > > design. But using the URL passing mechanism you can easily fireup the > > firefox. > > As far as I am concerned the quintessence of web page design is the > standard linux HOWTO. Text preferably all the same size and some pale > blue background to highlight stuff like source code.. shell commands > etc.. ;-) KISS works for me, and is a requirement for documentation. > But seriously I want a computer screen that looks like a computer > screen.. not a lame attempt at copying cheap magazines. Heh, good one. However, on the possitive side, they may occationally serve as a warning sign: "We have no real content so we sauce it up with spiffy layout". -- Jonas Fonseca _______________________________________________ elinks-users mailing list [email protected] http://linuxfromscratch.org/mailman/listinfo/elinks-users
