From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from QMTA11.westchester.pa.mail.comcast.net (qmta11.westchester.pa.mail.comcast.net [IPv6:2001:558:fe14:44:76:96:59:211]) by hurricane.the-brannons.com (Postfix) with ESMTP id B38597863A for ; Sat, 1 Mar 2014 06:01:17 -0800 (PST) Received: from omta24.westchester.pa.mail.comcast.net ([76.96.62.76]) by QMTA11.westchester.pa.mail.comcast.net with comcast id YDcl1n0061ei1Bg5BE07TH; Sat, 01 Mar 2014 14:00:07 +0000 Received: from eklhad ([107.5.36.150]) by omta24.westchester.pa.mail.comcast.net with comcast id YE061n00Y3EMmQj3kE06Mj; Sat, 01 Mar 2014 14:00:07 +0000 To: Edbrowse-dev@lists.the-brannons.com From: Karl Dahlke User-Agent: edbrowse/3.5.1 Date: Sat, 01 Mar 2014 09:00:07 -0500 Message-ID: <20140201090007.eklhad@comcast.net> Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=comcast.net; s=q20121106; t=1393682407; bh=M7mvJQZBeIxTlMFujROqLJzb2BpNexqAD8nupaTPYc0=; h=Received:Received:To:From:Reply-to:Subject:Date:Message-ID: Mime-Version:Content-Type; b=YwdEY4Xy8sptJwIat0jcpUcb9Xy/F80QyPe0zKNWV7W9QNcOVbCX0uv/Gc1SqzdJI oyN5xzK8h2MoVjh7ULnqOTgIX4fMfUjDXKvudo4EHP94J90zPZXJs88WJy2bujbUq/ twYS4ru+QJM7gRM+qrEUqGZkUKsJ8NSx7CoUznHoyDm9ZRh/YNuks7xI+LMNBQ39fd gkieeQ/usJa8xGkaflXW8eYXLzDXwr9YznUY9lKVsMTxuFstpmeb9Mg8Gdka3zYIFE QIaDu5HuFEqMcWrb0dvK942QLzpUaoMtF98YP1xO5PLDw01oweyGCaMRysSm2W5ImO 6bJbAVtoKKdDg== Subject: [Edbrowse-dev] tag list X-BeenThere: edbrowse-dev@lists.the-brannons.com X-Mailman-Version: 2.1.17 Precedence: list Reply-To: Karl Dahlke List-Id: Edbrowse Development List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 01 Mar 2014 14:01:18 -0000 Well the tags are built in a growing linked list as the page is parsed, but at the end of parse I plop them all into an array, so it is easy to grab tag 243 (example), just index the array, because the text in your buffer actually has encoded tag 243 {go to this link} You don't see tag code 243 but it's there, and it is accessed when you go to that link. If we want tags to continue to grow after page parse, new tags because of javascript creating html structures etc, then we want something with the dynamic power of a linked list or a tree but also an easy way to index like an array. Not sure if C++ list has this much power, or vector, but in C there wasn't anything, which is why I made the compromise I did. Anyways we might be able to forget the array and stay with the c++ list, and use its power to move forward. Create tags whenever javascript tells us to, and they can have parent links inside them to define the tree structure of forms and tables and so on. Karl Dahlke