Hi Chuck,
Thank you for the notes on this, and the shell script!
Kevin
On Sat, 21 Jun 2014, Charles Hallenbeck wrote:
Kevin,
My archlinux distro provides a js24 package that works with edbrowse
3.5.1, as does Fedora and a growing list of other distros. Debian's
release does not yet work with edbrowse however. The team here mostly
worked with the mozjs24 from Mozilla until the supported packages came
along. I don't recall having difficulties compiling the Mozilla release,
but the others can be more helpful, I'm sjre.
Chuck
On Sat, 21 Jun 2014, Kevin Carhart wrote:
Hi all
Wow, compiling the mozjs-24 has way more to it than in the past. I'm finally
trying to do this. Lots of weird errors so far. Has anyone had difficulties
with the python requirements? What do they need all of this python for? Oh
well.. I guess I was spoiled by using old versions for a long time.
If I want to try out things like parentNodes and attachEvent(), is 3.5.1 the
earliest version where these are found? In other words, I have to go to
mozjs-24 to get these js features? Or could I decouple these two things, give
edbrowse a slightly older js but still be able to use the latest edbrowse?
I'm on a 32-bit CentOS. I haven't been able to find mozjs-24 in package form,
either from yum or hunting around the rpm search engines so I have to compile.
I don't really know how out of date I am. Is 32-bit still OK or is it very
ill-advised? ... if you happen to know.
thank you!
Kevin
On Wed, 7 May 2014, Karl Dahlke wrote:
Hello - I am Kevin - I appreciate being able to lurk on the list
Please continue to read and post, it is quite helpful,
and perhaps you will join the development team if you find time.
You may want to get and use 3.5.1,
even though that is not an official version release yet.
A lot of changes there; the required change of supporting mozjs 24, but also
new features.
One is attachEvent(), which you aluded to in your post.
This is plain js, not jquery, but jquery may well use this feature
to atttach events to actions.
So pages that would attach a javascript function to a click or a load
will now do something whereas they did nothing before.
parentNode is also new;
I try to connect each node to its parent when created.
This is relevat to your description of the document tree,
and yes web js uses and expects and even modifies this tree all over the
place;
we have to support it!
If I am doing the parentnode properly, it would not be too hard
to add in the reverse logic to build the child node links.
Then write the functions to add new nodes
into the tree dynamically.
This is all moving forward, I think,
in the right direction, but slowly,
as it's just a couple of volunteers with some spare time.
Let me know if you can get, build, and use the latest,
and if you have further thoughts on design and development.
Karl Dahlke
_______________________________________________
Edbrowse-dev mailing list
[email protected]
http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
--------
Kevin Carhart * 415 225 5306 * The Ten Ninety Nihilists
_______________________________________________
Edbrowse-dev mailing list
[email protected]
http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
--
Chuck in Ghent, northeast of Hudson on the Hudson.
--------
Kevin Carhart * 415 225 5306 * The Ten Ninety Nihilists
_______________________________________________
Edbrowse-dev mailing list
[email protected]
http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
