edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Kevin Carhart <kevin@carhart.net>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] about compiling 3.5.1
Date: Sat, 21 Jun 2014 02:43:31 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LRH.2.03.1406210233240.18275@carhart.net> (raw)
In-Reply-To: <20140407185427.eklhad@comcast.net>



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
> Edbrowse-dev@lists.the-brannons.com
> http://lists.the-brannons.com/mailman/listinfo/edbrowse-dev
>

--------
Kevin Carhart * 415 225 5306 * The Ten Ninety Nihilists

  parent reply	other threads:[~2014-06-21  9:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-07 22:54 [Edbrowse-dev] jQuery Karl Dahlke
2014-05-09  0:57 ` Kevin Carhart
2014-06-21  9:43 ` Kevin Carhart [this message]
2014-06-21  9:58   ` [Edbrowse-dev] about compiling 3.5.1 Charles Hallenbeck
2014-06-21 22:15     ` Kevin Carhart
2014-06-21 23:03   ` Chris Brannon
2014-06-22 16:41   ` Adam Thompson
2014-06-22 23:39     ` Kevin Carhart
2014-06-24 14:02       ` Adam Thompson
2014-06-25  1:48         ` Kevin Carhart
2014-06-25 18:34           ` Adam Thompson
2014-06-25 23:44             ` Kevin Carhart
2014-06-26  9:53               ` Kevin Carhart
2014-06-24 14:09 Karl Dahlke
2014-06-24 18:11 ` Chris Brannon
2014-06-25 18:40   ` Adam Thompson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LRH.2.03.1406210233240.18275@carhart.net \
    --to=kevin@carhart.net \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=eklhad@comcast.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).