I posted the resulting patch against 2.1-pre28 (which I also updated to earlier today - nothing seems to have broken) at http://www.contrib.andrew.cmu.edu/user/edanaher/links/ . The patch has everything I've done in it; it's all fairly inter-related, so it would be a pain to pull it into separate patches. There's also a linksrc; this is the configuration file, which needs to be in ~/.links in order to work (that's currently hardcoded, one of the many things I don't like about it).
I'll probably start re-doing everything soon, working from a stock 2.1-pre28, doing my best to write code that doesn't break text mode and shouldn't break in general. Another issue is the whole UI thing; I personally like just writing a config file, and being able to re-read the config file while the browser is running. This then conflicts with changing settings with a GUI, which normally writes to a file which is not edited. I'm not sure what the Right Way to do both of these is; for the moment, I'm pretty much just ignoring GUI's for editing settings. On 4/16/07, Edward Rosten <[EMAIL PROTECTED]> wrote: > > > On Mon, 16 Apr 2007, Evan Danaher wrote: > > > Executive Summary: > > > > Links is cool. I've added some features. I want to submit them back. > > I am also possibly interested in making Javascript better, and/or > > adding in some semblence of DOM and/or CSS support. > > > > Details: > > > > I'm expecting this to be rather long, hence the summary above. > > > > About a month ago, I finally got fed up with Firefox using huge > > amounts of memory, and occasionally taking several seconds to scroll > > when other processes were using CPU. So I decided to look for a > > lighter browser. I found that Links, which I had used a bit in text > > mode, also had a GUI version, which looked remarkably usable. Even > > better, it has a fairly small, well-organized source base that I can > > work on. > > > > I thus began adding features to Links, gradually moving it towards my > > ideal browser. I've been using it as my primary browser for the past > > couple weeks, so I've fixed a couple things that annoy me. > > > > Most notably, I merged in some tabs code from links-hacked, and added > > a FVWM-style configuration file that allows for easy rebinding of keys > > and eventually mouse buttons. > > > > I've also added a couple smaller features: > > > > - URL abbreviations (e.g., wp:hello goes to > > http://en.wikipedia.org/wiki/Special:Search?search=hello";), set up in > > a general fashion using the configuration file. > > Does that have a GUI config box? If not, I can help you with that. I > figured out how to add those for the URL blocking. If you want to know, > look in block.c, or just ask. I'd be happy to share all of the insights I > had. > > > - forward: now going back can be undone; acts just like other browsers > > (though I'm thinking it'd be nice to get some sort of tree structure > > working. > > Can you post a patch for that? Also I agree re: tree structures. > Interestingly, the list boxes can support general tree structures. > > > > I have a decent list of other features I'd like, including a > > customizable status line, a good UI for browser spoofing on certain > > web sites (likely through the configuration file), an open with... > > menu, something along the lines of Konqueror's "Access keys" to make > > keyboard navigation easier, better font support, and gestures. Some > > of these are harder than others, and I have no idea how many I'll get > > done, but so far I've done a good job of occasionally sitting down and > > working on stuff. > > Mouse gestures are pretty straightforward, I've used these before. There's > a library called libstroke (not updated in ages, v.0.5 but it seems 100% > complete) which is very solid and works like a charm. It's not > particularly intelligent and can take a fair amount of training, but it > was good enough for me to use a commandline proficiently from a tablet PC > (ie lots of characters required). Again, I'll answer any questions you > have on this. > > > -Ed > > > > > - "Session Saver": on closing, save the tabs so that the next session > > can open up in the same state. Currently kind of hack-ish, since it's > > intended for development, but it saves the full state of every tab > > (just like the back history), so I can build a new version, and > > restart links and not lose open pages. > > > > - History deletion: in the CTRL-W history menu, you can use the delete > > key to remove history items, and insert to put them back (until you > > close the window). > > > > > > I'm also hoping to get better Javascript and CSS support; this might > > be better as a project for the summer. I'll see what happens. > > > > Finally, the point of this e-mail is that I'm interested in submitting > > these features back. Unfortunately, I've been working mostly for > > myself, and so some of the code is kind of ugly. Worse, I haven't > > been paying too much attention to text mode, so that's somewhat > > broken. But if you're interested in these features, I can get them > > fixed up and ready for submission. > > _______________________________________________ > > links-list mailing list > > links-list@linuxfromscratch.org > > http://linuxfromscratch.org/mailman/listinfo/links-list > > > _______________________________________________ > links-list mailing list > links-list@linuxfromscratch.org > http://linuxfromscratch.org/mailman/listinfo/links-list > _______________________________________________ links-list mailing list links-list@linuxfromscratch.org http://linuxfromscratch.org/mailman/listinfo/links-list
