Re: [fossil-users] Version 1.28 release?

[Ramey, Christopher]

On Thu, Jan 9, 2014 at 6:14 AM, Richard Hipp d...@sqlite.org wrote:


 On Thu, Jan 9, 2014 at 10:12 AM, Remigiusz Modrzejewski 
 l...@maxnet.org.pl wrote:


 On Jan 9, 2014, at 16:00 , Martin S. Weber wrote:

  But I want Fossil to follow the latest SQLite alphas, not the latest
 SQLite
  stables.  That's the whole point:  Fossil supports SQLite as a test
  platform.  SQLite stable has already been thoroughly vetted and tested
 and
  there is little point in testing it further.  I want Fossil to run
 with the
  latest SQLite on trunk to smoke out bugs early.
 
  ...but fossil in itself is a pretty awesome piece of software, that's
 expected
  by its users to be stable -- at least for releases.

 I second this view, Fossil is definitely valuable on its own merit.
 As such, its stable versions should not contain alpha-quality code from
 other projects.


 SQLite alphas are more robust that stables of most other software
 projects.


I'd be more concerned about the appearance of using a SQLite alpha in
Fossil. People have to have a great deal of faith in the quality and
stability of their VCS - using anything branded alpha even on the
insistence that it's better than most other stables could have a damaging
effect on Fossil's reputation.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Web UI Abstraction

[Ramey, Christopher]

I've been lurking on this list for awhile now, and I've seen more than a
few posts asking for behavior changes to the web UI. For example, the
recent post from Michai Ramakers about switching to a single-column layout
for the file listings (something I'd certainly like to see done, too.) The
barrier for changes like this is that the majority of the display logic for
those pages is hard-coded in C and compiled in. So if you wanted say, a
single-column layout in the file list, you would not only have to take on
that C code and the HTML it produces, you'd also need to maintain your own
version of Fossil with said changes.

My question is this: Is there any intention (or even interest) in
abstracting out the display logic for the web UI pages so that changes can
be made outside of the compiled code? Is that the ultimate intention of the
JSON API, to make all the web UI pages javascript powered JSON consumers?
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users