Re: [fossil-users] How to embed image in project home page or wiki pages?

[Ron W]

On Tue, Sep 15, 2015 at 9:24 PM, The Tick  wrote:
>
>
> That is one of the features that I was looking for. How to get the URL for
> that to put on the 'home' page is one of my next tasks. I doubt that most
> windows users would explore fossil's interface (and understand it enough)
> to click 'files' then click the weird check-in id to get to the ZIP
> download button. At this point I'm assuming I can just copy that URL and
> duplicate it on my home page.


Yes, you can simply copy that URL to the home page. You will need to update
it each time you make a release.

In theory, it is also possible to craft an URL that would also provide a
zip of the latest with a particular tag, such as "release". Not sure if
this is a good idea, but it would eliminate the need to update the home
page for each release. (Personally, I prefer to
explicitly update my download page for each release.)


> I'll have to explore that. It's just one image to get an idea of the app's
> GUI.


To have a file appear in only one version in the repository:
fossil add path/to/file
fossil commit -m 'comment about file being added' # the ID of this
commit is the version containing the file.
fossil rm path/to/file
fossil commit -m 'Make it so this file only appears in the previous
commit'

You can add more than one file this way. To access the file, it will be
necessary to refer to it using the commit ID of the version containing the
file. (Alternately, you can use the artifact ID of the file.)


> Again, thanks for your help.


You are welcome
___
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 embed image in project home page or wiki pages?

[The Tick]

On 9/15/2015 6:09 PM, Ron W wrote:

On Tue, Sep 15, 2015 at 6:18 PM, The Tick > wrote:

However, if I do that, then the image would be included in the
project download, right? I guess one small image would not be that
big a deal, but it would be good to not foist unnecessary files on
users.


What about your project's "user manual"? Screenshots are often included,
so would be reasonable to include in the source "tarball".


First of all, thanks for your reply.

The app is a Tcl script and associated image files. There is no "User 
Manual". It also requires Tcl with the Tk Img package be installed. If 
someone does not know how to unpack a ZIP and double-click a file, 
well... Adding a windows installer (even NullSoft) would add more 
complexity than I am willing to handle, especially trying to determine 
if Tcl is already installed, downloading ActiveState's version if not, 
etc. I am also assuming Unix users know how to unpack a tarball.


There's an 'INSTALL.txt' that should provide enough information. After 
that I will assume that most people know how to click a mouse.


If the 'INSTALL.txt' is unclear or there are bugs, I'd like the bug 
tracking system to be easy to use. Since there's no "Users Manual", I do 
not need nor want a public "wiki".




FYI, Fossil can automatically create "tarballs" of the files in the
repository for a specified version, which defaults to the latest.


That is one of the features that I was looking for. How to get the URL 
for that to put on the 'home' page is one of my next tasks. I doubt that 
most windows users would explore fossil's interface (and understand it 
enough) to click 'files' then click the weird check-in id to get to the 
ZIP download button. At this point I'm assuming I can just copy that URL 
and duplicate it on my home page.




I suppose a work-around would be to add the image(s) to a specific
version of your project, commit that version, then remove (rm) the
image(s) from the next version and commit that. Then your pages can link
to the image(s) at that specific version of your project, while the
automatically made tarballs would not have it/them.


I'll have to explore that. It's just one image to get an idea of the 
app's GUI.




Also, besides Fossil created tarballs, your project's build procedure
can, possibly should, create release packages. Such packages would
contain only what you choose to put in them. (But, see below.) The
specific version "trick" I described would work for these, as well as
images.


Since there is no build procedure, I want whatever source control system 
or host to supply the simple download Zip/Tar button. Again, thanks for 
your help.

___
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 embed image in project home page or wiki pages?

[Ron W]

On Tue, Sep 15, 2015 at 6:18 PM, The Tick  wrote:
>
> I did run across a way to embed an image that is checked in as part of a
> project:
> http://stackoverflow.com/questions/3982999/fossil-how-to-display-checked-in-image-files-on-wiki-pages
>
> However, if I do that, then the image would be included in the project
> download, right? I guess one small image would not be that big a deal, but
> it would be good to not foist unnecessary files on users.
>

What about your project's "user manual"? Screenshots are often included, so
would be reasonable to include in the source "tarball".

FYI, Fossil can automatically create "tarballs" of the files in the
repository for a specified version, which defaults to the latest.

I suppose a work-around would be to add the image(s) to a specific version
of your project, commit that version, then remove (rm) the image(s) from
the next version and commit that. Then your pages can link to the image(s)
at that specific version of your project, while the automatically made
tarballs would not have it/them.

Also, besides Fossil created tarballs, your project's build procedure can,
possibly should, create release packages. Such packages would contain only
what you choose to put in them. (But, see below.) The specific version
"trick" I described would work for these, as well as images.


> I'd like to put a small screenshot image to illustrate the project's GUI.
> Eventually, I will use Chisel to host this project, so perhaps there's a
> way to host an image file outside of a project's repository? (And, of
> course, to reference the image with an  tag.)
>

As best I can tell, ChiselApp.com doesn't provide for hosting files outside
of a Fossil repository. So, if you need to host files (images, release
packages, other) outside of a Fossil repository, you will need some other
arrangement. Unfortunately, I don't have any recommendations for "general
purpose" image /file hosting. Although photo sharing sites like photobucket
would *technically* work, using one that way might be against the terms of
service.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] How to embed image in project home page or wiki pages?

[The Tick]

This is my first open source project... I think fossil is the easiest 
source control for me to use, but I've got a lot to learn.


I've not found a way to put an image in the home page for a project.

I did run across a way to embed an image that is checked in as part of a 
project: 
http://stackoverflow.com/questions/3982999/fossil-how-to-display-checked-in-image-files-on-wiki-pages


However, if I do that, then the image would be included in the project 
download, right? I guess one small image would not be that big a deal, 
but it would be good to not foist unnecessary files on users.


I'd like to put a small screenshot image to illustrate the project's 
GUI. Eventually, I will use Chisel to host this project, so perhaps 
there's a way to host an image file outside of a project's repository? 
(And, of course, to reference the image with an  tag.)



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