On 2018-06-29 11:24, Chad Perrin wrote:
Okay, after all that, I feel like distilling this down to its essence
(according to my own opinions, naturally) might be in order.
I feel like we basically have three sane options available:
1. Make some very minor changes to the Fossil source, where it
On Thu, Jun 28, 2018 at 12:14 PM, Chad Perrin wrote:
> On Thu, Jun 28, 2018 at 11:40:01AM -0700, Sam Putman wrote:
> >
> > As a target, I would suggest the emitted html look as much like this
> > as possible:
> >
> > view-source:https://github.com/jvirkki/libbloom/blob/master/bloom.c
> >
> > The
Okay, after all that, I feel like distilling this down to its essence
(according to my own opinions, naturally) might be in order.
I feel like we basically have three sane options available:
1. Make some very minor changes to the Fossil source, where it generates
pretty viewable web pages, to mak
On 2018-06-28 12:49, Chad Perrin wrote:
Server side syntax highlighting is an excellent idea, though I'm not
quite sure at this time how to implement it. The other issue with such
being that fossil would basically need to cache the results of running
a highlight for the liftime of the program up
On Thu, Jun 28, 2018 at 11:40:01AM -0700, Sam Putman wrote:
>
> As a target, I would suggest the emitted html look as much like this
> as possible:
>
> view-source:https://github.com/jvirkki/libbloom/blob/master/bloom.c
>
> The actual code block begins at line 821.
>
> This style of markup is a
On Thu, Jun 28, 2018 at 9:07 AM, Chad Perrin wrote:
> See if this makes sense:
>
> Apply syntax highlighting to a block of code. Organize the code in
> second column TD elements of a table. Organize line numbers in first
> column TD elements of a table.
>
> Thus, you would have HTML for a line
On Thu, Jun 28, 2018 at 12:11:11PM -0500, Lester L. Martin II wrote:
> On 2018-06-28 11:07, Chad Perrin wrote:
> >
> > I think a cleaner approach, though it might take a bit of rewriting for
> > file display, would use an HTML table, possibly assembled by
> > JavaScript.
> > Note that I'm feeling
On 2018-06-28 11:07, Chad Perrin wrote:
On Thu, Jun 28, 2018 at 10:40:19AM -0500, Lester L. Martin II wrote:
I've developed a way to do highlighting with line numbering...
The issues are as follows however:
1. The JS code responsible for the highlighting is external to Fossil
itself.
2. The JS
On Thu, Jun 28, 2018 at 10:40:19AM -0500, Lester L. Martin II wrote:
>
> I've developed a way to do highlighting with line numbering...
> The issues are as follows however:
> 1. The JS code responsible for the highlighting is external to Fossil
> itself.
> 2. The JS code highlights blocks, so if
On 2018-06-28 08:12, Richard Hipp wrote:
Please mail in your CLA when you get a chance.
Sending later today, hopefully regular stamped mail won't take 2 weeks.
I've developed a way to do highlighting with line numbering...
The issues are as follows however:
1. The JS code responsible for the h
On 6/28/18, Lester L. Martin II wrote:
>
> Indeed. The entire code dealing with adding in line numbering would need
> reworking to enable it (and probably updates to CSS as well). I might
> can
> look into getting that working as well. I actually think there would be
> a way that would be simpler
On 2018-06-28 07:11, Richard Hipp wrote:
On 6/28/18, Lester L. Martin II wrote:
This patch changes the way `void artifact_page(void)` renders a files
content.
Formerly a `` was issued for content, whereas now a
`` is issued where $ext is the
file's
extension (example, "blah.lua" extension wou
On 6/28/18, Lester L. Martin II wrote:
> This patch changes the way `void artifact_page(void)` renders a files
> content.
> Formerly a `` was issued for content, whereas now a
> `` is issued where $ext is the file's
> extension (example, "blah.lua" extension would be "lua").
But then the syntax h
On 2018-06-28 00:36, Chad Perrin wrote:
On Wed, Jun 27, 2018 at 11:31:57PM -0500, Lester L. Martin II wrote:
This patch changes the way `void artifact_page(void)` renders a files
content. Formerly a `` was issued for content,
whereas now a `` is issued where
$ext is the file's extension (exampl
On Wed, Jun 27, 2018 at 11:31:57PM -0500, Lester L. Martin II wrote:
> This patch changes the way `void artifact_page(void)` renders a files
> content. Formerly a `` was issued for content,
> whereas now a `` is issued where
> $ext is the file's extension (example, "blah.lua" extension would be
>
15 matches
Mail list logo