On Sat, 08 Oct 2011 11:54:23 +0200, Gilles
wrote:
>Yes, users should be aware that Fossil refuses to handle files that
>contain some characters that are valid in Windows but might not be in
>other OS's.
Actually, this is a non-issue, since Fossil won't add a file that
contains characters it doesn
On Fri, 07 Oct 2011 23:53:11 +0200, Ingo Koch
wrote:
>WinFossil works if you give it time enough to do its job. ;-)
Thanks for the infos.
Actually, I use C: for system + applications, and use D: for data
files and files I don't care about (eg. installers), so I put the
repository at the root of
On 07.10.2011 01:09, Gilles wrote:
> On Thu, 6 Oct 2011 11:01:43 -0400, Tomek Kott
> wrote:
>> Yep, it should. It's worked for me for all of the repo's I've tried.
> So I guess WinFossil doesn't work when the repo is opened at the root
> of a partition that contains a lot of directories because it
On Thu, 6 Oct 2011 11:17:06 -0400, Richard Hipp
wrote:
>Fossil is fairly strict about the format of filenames - to try to avoid
>cross-platform issues and globbing issues.
>http://www.fossil-scm.org/fossil/artifact/79bed8df57b?ln=425
Thanks for the tip.
__
On Thu, 6 Oct 2011 11:01:43 -0400, Tomek Kott
wrote:
> Yep, it should. It's worked for me for all of the repo's I've tried.
So I guess WinFossil doesn't work when the repo is opened at the root
of a partition that contains a lot of directories because it will go
through each one looking for files
On Thu, 6 Oct 2011 18:20:12 +0200
Stephan Beal wrote:
> > Last time I checked GPB was implemented in the form of a C++
> > library.
> Many C++ APIs can be used from C code, actually, as long as their C+
> +-only functionality can be hidden behind an intermediary C-style API.
My point is that we'l
On Thu, Oct 6, 2011 at 6:20 PM, Stephan Beal wrote:
> Diffs and whatnot are a whole other problem altogether, because there are
> no clients other than fossil itself which handles fossil-format diffs.
>
That's not true - fossil interacts with many graphical diff programs.
> So those are also w
On Thu, Oct 6, 2011 at 5:59 PM, Konstantin Khomoutov <
flatw...@users.sourceforge.net> wrote:
> Last time I checked GPB was implemented in the form of a C++ library.
>
Many C++ APIs can be used from C code, actually, as long as their C++-only
functionality can be hidden behind an intermediary C-s
On Thu, 6 Oct 2011 11:31:16 -0400
Erlis Vidal wrote:
> Take a look to protocol buffers. The implementation is not restricted
> only to java, c++, python. Other people are adding more languages...
> this gives you kind of "portability"
Last time I checked GPB was implemented in the form of a C++
Take a look to protocol buffers. The implementation is not restricted only
to java, c++, python. Other people are adding more languages... this gives
you kind of "portability"
-Erlis
On Thu, Oct 6, 2011 at 11:19 AM, Stephan Beal wrote:
> On Thu, Oct 6, 2011 at 4:47 PM, Erlis Vidal wrote:
>
>>
On Thu, Oct 6, 2011 at 4:47 PM, Erlis Vidal wrote:
> Do you know about "protocol buffers". I'm asking because I didn't know
> about them since recently.
>
>
> http://google-opensource.blogspot.com/2008/07/protocol-buffers-googles-data.html
>
Never heard of them. Thanks for the link :).
> Could
On Thu, Oct 6, 2011 at 11:11 AM, Stephan Beal wrote:
> On Thu, Oct 6, 2011 at 4:30 PM, Tomek Kott wrote:
>
>> As for the illegal characters, I guess I haven't ran across that one. You
>> should probably submit a bug for that one with Ingo. Fossil itself allows
>> that kind of name, right?
>>
>
>
On Thu, Oct 6, 2011 at 4:30 PM, Tomek Kott wrote:
> As for the illegal characters, I guess I haven't ran across that one. You
> should probably submit a bug for that one with Ingo. Fossil itself allows
> that kind of name, right?
>
i'm fairly certain (but not entirely) that that error comes from
On Thu, Oct 6, 2011 at 10:55 AM, Gilles wrote:
> On Thu, 6 Oct 2011 10:30:46 -0400, Tomek Kott
> wrote:
> >So the checkout issue I'm not sure about, because that's how I started
> using
> >winfossil as well. I have two thoughts. By default, WinFossil looks for
> >'.fsl' type extensions. This mig
On Thu, 6 Oct 2011 10:30:46 -0400, Tomek Kott
wrote:
>So the checkout issue I'm not sure about, because that's how I started using
>winfossil as well. I have two thoughts. By default, WinFossil looks for
>'.fsl' type extensions. This might be somehow screwing things up because it
>can't match what
On Thu, Oct 6, 2011 at 9:04 AM, Stephan Beal wrote:
> There are some (a small few) features which we can't provide over JSON
> without some major workarounds and/or caveats. Namely binary data (which
> JSON cannot natively support), which means committing binary files this way
> will not be imple
So the checkout issue I'm not sure about, because that's how I started using
winfossil as well. I have two thoughts. By default, WinFossil looks for
'.fsl' type extensions. This might be somehow screwing things up because it
can't match what it expects the fossil repo to be named vs. what it is
nam
On Thu, 06 Oct 2011 16:09:45 +0200, Gilles
wrote:
>If I choose "C:\" instead, it seems to scan the whole drive, which
>takes for ever and freezes the UI.
Also, it chokes when using some non-standard characters:
"filename contains illegal characters: ... OS Cda [or] Mp3.ico"
On Thu, 6 Oct 2011 09:50:26 -0400, Tomek Kott
wrote:
> what issues did you have with it?
Maybe it's just that I didn't use it properly:
Starting with a repo I opened with the CLI and is located at the root
of the partition where I keep all the documents I work on (source
code, HTML pages, etc.).
Ooops, pressed send a little early. Meant to finish "filed bug reports".
On Thu, Oct 6, 2011 at 9:50 AM, Tomek Kott wrote:
>
> I tried WinFossil, but had issues with it.
>>
>> Understanding that WinFossil isn't a finished solution yet, what issues
> did you have with it? I've used it frequently
> I tried WinFossil, but had issues with it.
>
> Understanding that WinFossil isn't a finished solution yet, what issues did
you have with it? I've used it frequently for
commit/update/diff/checkout/sync/create/ui and those functions have all
worked. I think Ingo would love more feedback, and I he
On Thu, 6 Oct 2011 15:04:48 +0200, Stephan Beal
wrote:
>The "most important" functionality is working already (see the doc link). i
>unfortunately can't give a timetable - i hack on it as the
>time/energy/desire allow for. If you're well-versed in C, i'd be happy to
>have another developer or 3 wo
On Thu, Oct 6, 2011 at 1:56 PM, Gilles wrote:
> I tried WinFossil, but had issues with it.
>
It's not WinFossil's fault - because fossil has no well-defined standards
for output format, it is a futile exercise to create a UI around it. One of
the niches the JSON API hopes to fill is as a communi
On Thu, 6 Oct 2011 12:10:15 +0200, Stephan Beal
wrote:
>Fossil is a standalone application, not a C library of functionality.
Thanks for the infos.
I think there's a market for Fossil because it's so easy to install
and use, so that anyone who needs to keep different versions of a file
would hav
On Thu, Oct 6, 2011 at 12:02 PM, Gilles wrote:
> Thanks for the info. Out of curiosity, what do you mean by "monolithic
> design", and why is it a problem to write a GUI?
Fossil is a standalone application, not a C library of functionality. That
means that in order to write a UI the only possib
On Thu, 6 Oct 2011 09:05:06 +0200, Stephan Beal
wrote:
>Nope. Fossil's monolithic design doesn't lend itself well to creating GUIs.
>We're in the process of providing a solution, though - the JSON API allows
>alternate GUIs/shells to be written for fossil, but it is not yet
>feature-complete.
Tha
On Thu, Oct 6, 2011 at 3:01 AM, Gilles wrote:
> Is there another client I should know about, free or commercial?
>
Nope. Fossil's monolithic design doesn't lend itself well to creating GUIs.
We're in the process of providing a solution, though - the JSON API allows
alternate GUIs/shells to be wr
Hello
I'd like to use a fat GUI client instead of the CLI or the web UI, so
checked out GUI clients for Windows.
Since I can't stand Java, I didn't try jurassic-fossil.
Apparently, the only alternative for Windows is Ingo Koch's WinFossil.
http://repository.mobile-developers.de/cgi-bin/ikoch/sh
28 matches
Mail list logo
