Re: [fossil-users] Internal hyperlinks, content-type and stuff

2010-05-19 Thread Eric


> I'm thinking Eric intended these links:
>
> http://www.fossil-scm.org/index.html/doc/tip/www/embeddeddoc.wiki
http://www.fossil-scm.org/index.html/doc/tip/www/branching.wiki
>
> Instead of:

>
> Regards,
>Donald
>
>

Well, what I intended was:

http://www.fossil-scm.org/fossil/doc/tip/www/embeddeddoc.wiki
http://www.fossil-scm.org/fossil/doc/tip/www/branching.wiki

but Donald's work too.

Sorry, I'm usually more careful than that :(

Eric



-- 


___
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] Internal hyperlinks, content-type and stuff

2010-05-19 Thread Eric

> On Wed, May 19, 2010 at 5:06 PM, Michal Suchanek
> wrote:
>
>> On 19 May 2010 20:27, Eric  wrote:
>> It looks like images magically get the correct doctype when accessed
>> through the doc/ urls so it's necessary to check them into the repo as
>> managed files and access them that way, wiki attachments won't work.
>>
>
> I think this is a bug.
>
> --
> -
> D. Richard Hipp
> d...@sqlite.org

Probably, but the link could be something like

http://www.fossil-scm.org/fossil/raw?name=ec8f7980c85f6bfc00e858a6ba9a7f2184c84127&m=text/plain

or, to be relative, just

raw?name=ec8f7980c85f6bfc00e858a6ba9a7f2184c84127&m=text/plain

(but I don't think the latter works from an embedded doc page).

You can get the "name" (actually the artifact ID) by clicking on the
attachment name on the wiki page, and use the proper mime-type for "m".

Maybe a more friendly-looking alternative would be good, perhaps some
attachxxx URL.

Eric



___
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] Internal hyperlinks, content-type and stuff

2010-05-19 Thread Richard Hipp
On Wed, May 19, 2010 at 5:06 PM, Michal Suchanek wrote:

> On 19 May 2010 20:27, Eric  wrote:
> It looks like images magically get the correct doctype when accessed
> through the doc/ urls so it's necessary to check them into the repo as
> managed files and access them that way, wiki attachments won't work.
>

I think this is a bug.

-- 
-
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


Re: [fossil-users] Internal hyperlinks, content-type and stuff

2010-05-19 Thread Michal Suchanek
On 19 May 2010 20:27, Eric  wrote:
>
>> Hello
>>
>> I considered to use fossil for my project but the curernt release is
>> unusable for me.
>>
>> I could not find any way for fossil to store non-text files and serve
>> them over http with the correct content-type, either inferred by some
>> magic or specified manually.
>>
>> As I would like to use illustrations/diagrams/pictures in the
>> documentation which I hoped to store in the included wiki there is no
>> way to do that with fossil.
>>
>> A somewhat different issue is easy linking to wiki attachments and/or
>> SCM objects in the docs. Since the artifacts are technically immutable
>> just linking to the artifact directly should suffice in most cases as
>> the link should not change over time but it would be nicer if there
>> was a way to generate links relative to the repository location so
>> that the links work also when the repository is moved to another
>> location.
>>
>> Another question is how to reliably link to a particular version vs
>> latest version of a file which is managed by fossil.
>>
>> As the wiki formatting page does not answer these question I suspect
>> fossil only relies on direct links so far.
>>
>> Is there something I am missing here?
>>
>> Thanks
>
> basically you need to follow the embedded documentation link on the home
> page to get some information about this
>
> http://www.fossil-scm.org/doc/tip/www/embeddeddoc.wiki
>
> Also if you look at
>
> http://www.fossil-scm.org/doc/tip/www/branching.wiki

It would be

http://www.fossil-scm.org/index.html/doc/tip/www/embeddeddoc.wiki
http://www.fossil-scm.org/index.html/doc/tip/www/branching.wiki

>
> you will see that it contains pictures. They are GIFs in the same
> directory and are linked with a relative link such as
>
> 
>
> The fossil code that handles this is in src/doc.c if you are interested
> and can read C (or even if you can't)
>

Indeed, the first has some general info that helps with referencing
different versions of files and the later has some images.

However, the doc on embedded docs does not detail use of pictures.

The later page is included in the source tarball in www directory so I
guess that's a good example.

It looks like images magically get the correct doctype when accessed
through the doc/ urls so it's necessary to check them into the repo as
managed files and access them that way, wiki attachments won't work.

Thanks

Michal
___
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] Internal hyperlinks, content-type and stuff

2010-05-19 Thread Eric

> Hello
>
> I considered to use fossil for my project but the curernt release is
> unusable for me.
>
> I could not find any way for fossil to store non-text files and serve
> them over http with the correct content-type, either inferred by some
> magic or specified manually.
>
> As I would like to use illustrations/diagrams/pictures in the
> documentation which I hoped to store in the included wiki there is no
> way to do that with fossil.
>
> A somewhat different issue is easy linking to wiki attachments and/or
> SCM objects in the docs. Since the artifacts are technically immutable
> just linking to the artifact directly should suffice in most cases as
> the link should not change over time but it would be nicer if there
> was a way to generate links relative to the repository location so
> that the links work also when the repository is moved to another
> location.
>
> Another question is how to reliably link to a particular version vs
> latest version of a file which is managed by fossil.
>
> As the wiki formatting page does not answer these question I suspect
> fossil only relies on direct links so far.
>
> Is there something I am missing here?
>
> Thanks

basically you need to follow the embedded documentation link on the home
page to get some information about this

http://www.fossil-scm.org/doc/tip/www/embeddeddoc.wiki

Also if you look at

http://www.fossil-scm.org/doc/tip/www/branching.wiki

you will see that it contains pictures. They are GIFs in the same
directory and are linked with a relative link such as



The fossil code that handles this is in src/doc.c if you are interested
and can read C (or even if you can't)

HTH

Eric

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