public inbox for frysk-cvs@sourceware.org
help / color / mirror / Atom feed
From: ajocksch@sourceware.org
To: frysk-cvs@sourceware.org
Subject: frysk-gui/frysk/gui/srcwin ChangeLog InlineVie ...
Date: Wed, 16 Nov 2005 23:42:00 -0000 [thread overview]
Message-ID: <20051116234207.13823.qmail@sourceware.org> (raw)
CVSROOT: /cvs/frysk
Module name: frysk-gui
Changes by: ajocksch@sourceware.org 2005-11-16 23:42:07
Modified files:
frysk/gui/srcwin: ChangeLog InlineViewer.java SourceBuffer.java
SourceViewWidget.java
frysk/gui/srcwin/dom: DOMFunction.java DOMInlineInstance.java
Log message:
2005-11-16 Adam Jocksch <ajocksch@redhat.com>
* InlineBuffer.java: Added.
* InlineViewer.java (InlineViewer): Now takes StackLevel and
DOMInlineInstance.
(toggleChild): Commented out for now.
(moveDown): Ditto.
(setSubScopeAtCurrentLine): Ditto.
(drawMargin): Corrected bug where r,g, and b for a color were all being
populated by the r component.
* SourceBuffer.java (SourceBuffer): Created constructor that just
initializes, but doesn't load data.
(getInlineInstance): Added.
(init): Removed section that loads data.
(loadFile): Changed to protected, extracted out loadLines function.
(loadLines): Refactored out of loadFile.
(createTags): Changed to protected.
* SourceViewWidget.java (SourceViewWidget): Added constructor that takes
an already existing SourceBuffer.
(toggleChild): Refactored to use new InlineViewer constructor.
(drawMargin): Executable marks not drawn on lines where the is expanded
inline code.
* dom/DOMFunction.java (getLines): No longer throws exception, now
actually works as expected.
* dom/DOMInlineInstance.java (DOMInlineInstance): Removed constructor
that doesn't take an Element since it wasn't being used.
(getDeclaration): Now actually browses the tree to find the proper
DOMFunction object.
Patches:
http://sourceware.org/cgi-bin/cvsweb.cgi/frysk-gui/frysk/gui/srcwin/ChangeLog.diff?cvsroot=frysk&r1=1.117&r2=1.118
http://sourceware.org/cgi-bin/cvsweb.cgi/frysk-gui/frysk/gui/srcwin/InlineViewer.java.diff?cvsroot=frysk&r1=1.17&r2=1.18
http://sourceware.org/cgi-bin/cvsweb.cgi/frysk-gui/frysk/gui/srcwin/SourceBuffer.java.diff?cvsroot=frysk&r1=1.28&r2=1.29
http://sourceware.org/cgi-bin/cvsweb.cgi/frysk-gui/frysk/gui/srcwin/SourceViewWidget.java.diff?cvsroot=frysk&r1=1.33&r2=1.34
http://sourceware.org/cgi-bin/cvsweb.cgi/frysk-gui/frysk/gui/srcwin/dom/DOMFunction.java.diff?cvsroot=frysk&r1=1.3&r2=1.4
http://sourceware.org/cgi-bin/cvsweb.cgi/frysk-gui/frysk/gui/srcwin/dom/DOMInlineInstance.java.diff?cvsroot=frysk&r1=1.5&r2=1.6
next reply other threads:[~2005-11-16 23:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-16 23:42 ajocksch [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-01-20 16:20 ajocksch
2005-12-21 16:36 ajocksch
2005-12-21 16:07 ajocksch
2005-12-12 19:48 ajocksch
2005-12-08 20:22 ajocksch
2005-11-24 22:05 ajocksch
2005-11-21 18:06 ajocksch
2005-10-28 19:29 ajocksch
2005-10-19 22:40 ajocksch
2005-10-05 19:38 ajocksch
2005-10-04 15:09 ajocksch
2005-10-03 20:49 ajocksch
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=20051116234207.13823.qmail@sourceware.org \
--to=ajocksch@sourceware.org \
--cc=frysk-cvs@sourceware.org \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).