Put differently, what can’t you do with “fossil ui” that you can do with a
native client?
Drag and drop is the only one I can think of and I suspect that’s a good thing.
-- Steve
On 6 Aug 2018, 9:17 AM +0800, Richard Hipp , wrote:
> On 8/5/18, Gilles wrote:
> > 2. There's no maintained GUI for
On 8/5/18, Gilles wrote:
> 2. There's no maintained GUI for Fossil.
I would argue that running "fossil ui" is your GUI.
--
D. Richard Hipp
d...@sqlite.org
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080
Thanks for the info, but like 90% of deskop users, I run Windows. I gave
up on deskop Linux, even though I give it a try every year or so just to
check it out.
I'm not arguing. It's just that Fossil is such a great SCM application
that I guess it would benefit even more users if it were availa
Re Your point (2)
There may not be a GUI for Windows (I don’t use Windows) but there is is a nice
‘Tortoise-like’ GUI for Fossil on macOS - Snail Fossil.
> On 5 Aug 2018, at 21:14, Gilles wrote:
>
> On 05/08/2018 22:02, Richard Hipp wrote:
>> How does adding an extra component and a bunch of
On 05/08/2018 22:02, Richard Hipp wrote:
How does adding an extra component and a bunch of new interfaces make
a program easier to build? I think that the key to building complex
systems is to keep them as simple as possible. If you can omit a
DLL/shared library and all the maintenance and inte
On 05/08/2018 21:28, Stephan Beal wrote:
Very, very long story very, very short: reimplementing fossil as a
library requires a massive effort.
Too bad. Thanks for the info.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fo
On 8/5/18, Gilles wrote:
>
> I'm only a casual programmer, but I assume it would have made it easier
> to build a GUI by calling functions within the DLL.
How does adding an extra component and a bunch of new interfaces make
a program easier to build? I think that the key to building complex
sys
On Sun, Aug 5, 2018 at 8:56 PM Gilles wrote:
> Hello,
>
> Out of curiosity, why isn't Fossil split into the engine in a DLL and a
> CLI in an EXE, like SQLite?
>
> I'm only a casual programmer, but I assume it would have made it easier
> to build a GUI by calling functions within the DLL.
>
> At
Hello,
Out of curiosity, why isn't Fossil split into the engine in a DLL and a
CLI in an EXE, like SQLite?
I'm only a casual programmer, but I assume it would have made it easier
to build a GUI by calling functions within the DLL.
At this point, it seems like all of the Windows GUI (Fuel,
On 05/08/2018 05:47, Warren Young wrote:
It is not correct to say that Fossil had no output in this case. Its
output was the exit status code, which was zero, meaning there was no
failure.
I understand that it's too late now that some scripts would break if
diff/gdiff returned something like "N
10 matches
Mail list logo