Re: [Edbrowse-dev] master

[Adam Thompson <arthompson1990@gmail.com>]

On Tue, Jan 28, 2014 at 12:35:03PM -0500, Karl Dahlke wrote:
> There are many enhancements that would be good to make,
> but probably not bundled with this one.
> Go to 3.5.1 first, then other changes can push the third number again.

My thoughts exactly but thought I'd just check.

> These changes are mostly additions to the DOM, objects that I haven't implemented
> or even simulated,
> and as we all saw, when one of these is missing javascript stops in its tracks.
> That's why edbrowse isn't working on more and more sites.
> We need to have the same objects and methods,
> or stubs for these objects and methods,
> as you might find in a browser.
> It's just grunt-work, and not very easy or satisfying.
> A site doesn't work, set db3, track it down,
> what variable is missing, look it up in a js dom tutorial,
> what does the variable do, implement it or simulate it.
> Then move on to the next broken website, and so on.
> All needs to be done, all good stuff,
> but rather independent of what we're doing now.

Yeah, I guess the big ones are AJAX and friends.

> Some of these changes won't happen until the big rewrite,
> those where js creates brand new thingies that are normally made by html.
> That's backwards in my path today, so we'll just wait on these.

They look a bit messy to implement, but we may find that we have no choice
given the way the web is going. Any specific candidates for such things?

> Anyways that's how I see the road ahead.

Yeah, I was also wondering about  other features.
A couple that spring to mind:
An option (config file or command line)
to increase the max limit on the number of lines (basically switch from a static array to malloc)
same for max line length (not sure about the possibility of this one)

These are mainly motivated by the fact that I sometimes need to edit gygantic
ascii data files and such editing is usually much easier to do in a text editor
rather than other more specialist software.

Cheers,
Adam.