[fossil-users] pending-review items.

[Andy Bradford]

Hello,

Should these two pending-review items be included in 1.27:

http://www.fossil-scm.org/index.html/info/8ad0a8796a
http://www.fossil-scm.org/index.html/info/bdbf144ed3

Thanks,

Andy
-- 
TAI64 timestamp: 4000522e9141


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Problem with Mac OS X downloads

[David Mason]

On 9 September 2013 10:07, Warren Young  wrote:
> On 9/9/2013 07:03, Richard Hipp wrote:
>> I'd like to provide universal binaries for Mac, but (alas) I
>> don't know how to do that.
>
> $ ./configure --disable-dependency-tracking \
> CFLAGS='-arch x86_64 -arch i386'
>
> You can add "-arch ppc" and "-arch ppc64" if you want *truly* universal
> binaries.

I'd argue that i386 (and maybe ppc) is plenty.  My understanding is
that most _64 processors actually perform pretty well with 32-bit
code.

But the other (and larger) problem I had was with the library update.
The provided binary wanted libiconv version 8, when I only had 7.
Maybe you have to compile on a Snow Leopard system?

../Dave
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] How to allow script tag in Fossil Wiki

[Stephan Beal]

On Mon, Sep 9, 2013 at 4:26 PM, Samuel Debionne <
samuel.debio...@ujf-grenoble.fr> wrote:

>   
> 
> 
> 
>   
>

Correct - fossil elides all tags which are not listed here:

http://fossil-scm.org/index.html/wiki_rules

and it strips all but "a few benign" attributes. At the time that was
written, "data-" was not yet standardized and not in common usage.
(Sidebar: the HTML4 standard is ambiguous on how exactly browsers should
parse that: the wording allows a browser to "ignore" such attributes but
does not specify whether "ignore" means "skip while parsing" or "parse but
apply no meaning to," but everyone seems to expect/rely on the latter
behaviour.) Perhaps Richard could be convinced that "data-" is necessary
for modern JS usage. Then again, because data- is basically there solely
for the sake of JS, one could argue that the risk of cross-site-scripting
problems is higher with those tags. (That said: i have no opinion on the
topic - i'm an utter idiot when it comes to XSS and similar topics.)



> Meanwhile, I have been following your dev of the JSON API as this is
> probably the right solution in the long term (to have fossil as
> library/web service). But in the short term is this kind of hack worth
> considering (I have a prototype implemented for Fossil Wiki markup) ?
>

Personally, i wouldn't bother, but people do all sorts of things i wouldn't
ever bother trying to do ;). If you JUST want a Wiki, an AJAX/JSON-only
solution is currently realistic. Longer term (but not this year) libfossil
should be able to offer potential solution for you. The plan is to move the
wiki parsing into a higher-level API, such that the client can plug in
their own renderers/filters for specified wiki text types (wikis have a
mime-type field which we can use to dispatch to the proper renderer). But
the networking components are still a very long way down the TODO list.

-- 
- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] How to allow script tag in Fossil Wiki

[Samuel Debionne]

Hello Stephan,
Lately I have been working on integrating Bootstrap (from Twitter) to
modernize the look & feel and add a responsive design to my Fossil web
interfaces. For that, I hacked the markup generated by fossil, mainly
adding a few class attributes - these modifications could probably be
written in javascript. The main thing I'm really missing is a way to
inject raw html within the wiki markups, html that would not be parsed,
because the parser is a bit to restrictive and may remove some
markup/attributes considered armfuls or unknowns. A concrete example :





  


With the current implementation the div markup and the data-target,
data-slide-to attributes are stripped from the rendered output.

Meanwhile, I have been following your dev of the JSON API as this is
probably the right solution in the long term (to have fossil as
library/web service). But in the short term is this kind of hack worth
considering (I have a prototype implemented for Fossil Wiki markup) ?

Regards,
Samuel

Le 30/08/2013 16:31, Stephan Beal a écrit :
> On Fri, Aug 30, 2013 at 3:58 PM, Samuel Debionne
>  > wrote:
> 
> Too bad. Would that mean that if I submit a patch that would make it an
> extra option with an "extra warning" it has no chance to be accepted ?
> 
> 
> That would be Richard's decision. i wouldn't be against it. My own use
> of the wiki nowadays mostly uses the JSON API to store/fetch
> GoogleCode-formatted wiki pages and render them on the client using
> JavaScript. Example:
> 
> http://fossil.wanderinghorse.net/wikis/cson/?page=cson
> 
> That's a fossil repository who's sole purpose is to hold the wiki pages
> for that project (the sources are another repo), and it's only rendered
> using the custom (wiki-only) front-end.
> 
> -- 
> - stephan beal
> http://wanderinghorse.net/home/stephan/
> http://gplus.to/sgbeal
> 
> 
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
> 

<>___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Problem with Mac OS X downloads

[Warren Young]

On 9/9/2013 07:03, Richard Hipp wrote:


I'd like to provide universal binaries for Mac, but (alas) I
don't know how to do that.


Something like:

$ ./configure --disable-dependency-tracking \
CFLAGS='-arch x86_64 -arch i386'

The --disable-dependency-tracking bit is necessary because you don't 
want *.o from one architecture to fool make(1) into believing it doesn't 
have to rebuild the *.o for the other arch.


This doubles build time, of course.

You can add "-arch ppc" and "-arch ppc64" if you want *truly* universal 
binaries.

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] Problem with Mac OS X downloads

[Richard Hipp]

On Sun, Sep 8, 2013 at 9:48 PM, David Mason  wrote:

>
> I can and have built from the tar file and will provide it for my
> class, but it would seem desirable for the downloadable file to be the
> most widely executable possible.
>
> ../Dave
>

Thanks.  I'd like to provide universal binaries for Mac, but (alas) I don't
know how to do that.  Do you have suggestions on how I might compile Fossil
to on Mac to make it usable by the most Mac users?  We are getting ready to
do a new "release".

Cool that you are using Fossil in your class.  CPS313 is it?

-- 
D. Richard Hipp
d...@sqlite.org
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users