Re: [fossil-users] Compiling fossil under windows

2010-04-14 Thread Rene de Zwart 

Op Zo, 11 april, 2010 12:59, schreef D. Richard Hipp:
>
> On Apr 11, 2010, at 6:46 AM, Rene de Zwart wrote:
>
>>
>> Having had my way with fossil compiling under windows. I was looking
>> for
>> new challenges by compiling with other free compilers.
>> I tried digital mars c compiler. Which promptly said
>>  "unistd.h is for unix systems" (The smart little bugger :-)
>>
>> Do I correctly infer from this that native windows compilers are not
>> tested/used/supported?
>
>
> Correct.
>
> I don't own a windows machine. The windows binaries on the website are
> generated by cross-compiling off of Linux.  I do have the capability
> of running windows under VMWare (for testing), but I don't bring
> VMWare up that often and do not have any compilers installed there.
>
> D. Richard Hipp
> d...@hwaci.com
>
>
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
Richard,

In my latest experiment I installed on my arch linux machine wine.
Then under wine I installed msys, digital mars c compiler, zlib , fossil
and compiled fossil with dmc under wine. I started fossil under wine and
started firefox (under linux). I can see the windows fossil on
localhost:8080


-- 
Rene de Zwart

___
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] Compiling fossil under windows

2010-04-13 Thread Rene de Zwart 

Op Zo, 11 april, 2010 12:59, schreef D. Richard Hipp:
>
> On Apr 11, 2010, at 6:46 AM, Rene de Zwart wrote:
>
>>
>> Having had my way with fossil compiling under windows. I was looking
>> for
>> new challenges by compiling with other free compilers.
>> I tried digital mars c compiler. Which promptly said
>>  "unistd.h is for unix systems" (The smart little bugger :-)
>>
>> Do I correctly infer from this that native windows compilers are not
>> tested/used/supported?
>
>
> Correct.
>
> I don't own a windows machine. The windows binaries on the website are
> generated by cross-compiling off of Linux.  I do have the capability
> of running windows under VMWare (for testing), but I don't bring
> VMWare up that often and do not have any compilers installed there.
>
> D. Richard Hipp
> d...@hwaci.com
>
>
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
I have done compilations with
1) digitalmars c 8.42n (DMC)
2) borland bcc55
3) Microsoft express 2008 (MSVC)

Borland doesn't have support for long long type so it isn't usable

Microsoft and dmc lack unistd.h in various degrrees.
Which is fixable with what you find on the internet.
dirent.h is an other one also fixable via the internet.
Microsoft is the pain in the ass because gnumake isn't capable of
producing the fossil.exe. With a bit of fiddling around fossil.exe was
produced.

both fossils by dmc en msvc allow me to clone, open, diff, changes, ui and
server.

So seem you can use native compilers for fossil compiling.

I still want to look in the open watcom compiler.

-- 
Rene de Zwart

___
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] Compiling fossil under windows

2010-04-11 Thread Rene de Zwart 

Op Zo, 11 april, 2010 12:59, schreef D. Richard Hipp:
>
> On Apr 11, 2010, at 6:46 AM, Rene de Zwart wrote:
>
>>
>> Having had my way with fossil compiling under windows. I was looking
>> for
>> new challenges by compiling with other free compilers.
>> I tried digital mars c compiler. Which promptly said
>>  "unistd.h is for unix systems" (The smart little bugger :-)
>>
>> Do I correctly infer from this that native windows compilers are not
>> tested/used/supported?
>
>
> Correct.
>
> I don't own a windows machine. The windows binaries on the website are
> generated by cross-compiling off of Linux.  I do have the capability
> of running windows under VMWare (for testing), but I don't bring
> VMWare up that often and do not have any compilers installed there.
>
> D. Richard Hipp
> d...@hwaci.com
>
>
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
Richard,

I had success compiling fossil with Digital Mars Compiler.
This compiler identifies itself with __DMC__
so basically everwhere
  if __MINGW32__ or if!__min...@__
stands has to change to
   if __MINGW32__ || __DMC__ or if !__MINGW32__ && !__DMC__
there are a few quirks
dmc doesn't have

-) close-, open- and read-dir but a public header fixes that in construct,
add and vfile
-)  strncasecmp and strcasecmp a simple  -Dstrncasecmp=memicmp
-Dstrcasecmp=stricmp
-) winsock inclusing is different
I had to do
  #if defined(__MINGW32__)
  #  include/* for Sleep once server works again */
  #  include   /* socket operations */
  #  define sleep Sleep/* windows does not have sleep, but   
Sleep */
  #  include 
  #elif defined(__DMC__)
typedef int socklen_t;
  #  include   /* socket operations */
  #else
in cgi.c http_socket.c
it seems that winsock2.h includes windows.h

if it is of importance to you i can send the diffs


-- 
Rene de Zwart

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

[fossil-users] Compiling fossil under windows

2010-04-11 Thread Rene de Zwart 

Having had my way with fossil compiling under windows. I was looking for
new challenges by compiling with other free compilers.
I tried digital mars c compiler. Which promptly said
  "unistd.h is for unix systems" (The smart little bugger :-)

Do I correctly infer from this that native windows compilers are not
tested/used/supported?


-- 
Rene de Zwart

___
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] can this be done in fossil: hyperlinking to subdir of fossil repo

2010-04-06 Thread Rene de Zwart 

Op Di, 6 april, 2010 23:03, schreef Stephan Beal:
> On Tue, Apr 6, 2010 at 9:10 PM, verizon  wrote:
>
>> From advice I got previously here is how I can access a PDF that is in
>> the
>> repository with a relative link (works both locally and in a server)
>>
>> [http:doc/tip/Ethernet/DOCS/npincomplete.pdf | Code Description (pdf) ]
>>
>
> That won't work in this case because...
>
> The document i need to serve is a demo PHP page, which must be served by
> the
> underlying web server. It uses JavaScript which requires a web server to
> be
> able to POST messages to (it's an RPC framework, so it's all about passing
> messages to/from the web server).
>
> i was hoping i could link non-fossil'd subdirs without using absolute URLs
> (including domain), but i haven't found a way to do it. They would be
> useful
> because my public website is mirrored on my system, so i could simplify
> local testing before updating the public server. But no big deal, in any
> case.
>
> --
> - stephan beal
> http://wanderinghorse.net/home/stephan/
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>

Its is a bit odd to run 2 http servers (well maybe not that odd)
1) run fossil ui on port 8080
2) run apache (xampp) on port 80 for the php pages.
   use a link or a path to get de directory into the pages that apache
will serve. you could do [http://localhost/fossil/demo/my.php|php
demo].
It is the basic theme you could improve with virtual hosts so that your
development  system uses the same naming (of course you have to edit your
local hostfile )

-- 
Rene de Zwart

___
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] SSL support, prebuilt binaries, Windows

2010-03-30 Thread Rene de Zwart 

Op Di, 30 maart, 2010 23:11, schreef Dan:
> don't know if its to do with versions, but i had to change it to
>
> LIB += -leay32 -lssl32
>
> and that built fine, but i don't really know how to test the end result
> - since i don't have any use for ssl :)
>
> Daniel
If I do that then fossil.exe exits with cannot find leay32.dll
-- 
Rene de Zwart

___
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] SSL support, prebuilt binaries, Windows

2010-03-30 Thread Rene de Zwart 

Op Di, 30 maart, 2010 17:52, schreef Bjorn Toft Madsen:
> I managed a successful build of fossil on Windows, through the kind
> help of other list members.
>
> The only outstanding issue is some undefined references when
> FOSSIL_ENABLE_SSL=1:
change
  ifdef FOSSIL_ENABLE_SSL
  LIB += -lcrypto -lssl
  endif
to
  ifdef FOSSIL_ENABLE_SSL
  LIB = -lssl -lcrypto -lgdi32 -lmingwex -lz -lws2_32
  endif

and it works (for me :-)



-- 
Rene de Zwart

___
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] Repository in a single file

2010-01-25 Thread Rene de Zwart 

Op Ma, 25 januari, 2010 08:18, schreef Paul Serice:
> On Sun, 2010-01-24 at 18:29 -0500, D. Richard Hipp wrote:
>> On Jan 24, 2010, at 5:42 PM, Paul Serice wrote:
>> > Just search for "Berkeley DB usage leading to respository
>> > corruption and data loss" on the Wikipedia page for Subversion.
>>
>> That's why subversion switched to SQLite, isn't it?
>
> They switched to pile-of-files as the default.  They still have the
> option to create Berkeley DB repositories.  From their INSTALL file,
> they use SQLite only internally which is probably a good thing because
> they've given Berkeley DB quite a black eye; whether it's deserved or
> not, I do not know.
At the end of the day sqlite is a pile of tables. It still has to manage
the "enitities" (artefacts, users,tickets, check-ins,...). But it
convenient hides the details from vision.
Sqlite has a good(I assume here I can neither prove or disprove) track
record for well maintaining its "entities"

I'm quit sure that file systems have a very good track record for
maintaining files. It is just those pesky little humans who screw up the
file systems :-)

It's storage and every storage organization form has its pros and cons.

What (I think) Richard is saying that Sqlite is just a convenient storage
module that has nothing to do with fossil's scm algorithm. It is just a
storage method he has chosen(not surprisingly him being the maker) . With
the consequence that there is one file for a scm project.

Would he have chosen Berkley DB then the storage would be different and
you loose the convenience of one file.

Other storage implementations bring more dependencies (think oracle,
mysql, postgres, Hsqldb, ) or would require to build storage
capabilities e.g. an other sqlite.

It is interesting to see that Linus for  git has build his own storage
capabilities. From
http://www.software-configuration.com/articles/git-fast_version_control_system.html
-
A third matter that occasionally concerns people is the GIT storage model.
Each created item is retained in an individual file. In an attempt to use
space efficiently, these individual files are saved in a collective format
known as a pack. As history is created, it is stored in single files;
therefore packing into collective pack form is required periodically. This
is done automatically on occasion by the GIT system. However, using the
git-go command will enable you to process this manually whenever you
choose. This would prove useful to you if you have recently worked on a
large collection and wanted it efficiently stored as soon as possible,
prior to the automatic packing.
--------
So git is just a pile of files and storage concerns are everywhere

--
Rene de Zwart

___
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] Repository in a single file

2010-01-25 Thread Rene de Zwart 

Op Ma, 25 januari, 2010 08:18, schreef Paul Serice:
> On Sun, 2010-01-24 at 18:29 -0500, D. Richard Hipp wrote:
>> On Jan 24, 2010, at 5:42 PM, Paul Serice wrote:
[snip
>> Usually the whole drive goes out, rather than changing a single
>> byte.
>
> Well, your drive goes out, and you don't have a remote clone so you
> reach for your DVD backup which verified ok, but now when you restore,
> cpio warns about a checksum not matching.
>
So making a backup doesn't mean you can restore!
You have to check for that to. And slowly we come to the old question
"who is checking the checks" (endless recursion)
It is a question how important it is and how much certainty you want to
archive. which we have done upfront off course (yeah and pigs fly :-)
>
[snip]
> Nice.
>
>
> Thank You,
> Paul Serice
>
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>


-- 
Rene de Zwart

___
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] Noob windows build problems

2010-01-22 Thread Rene de Zwart 

Op Vr, 22 januari, 2010 16:11, schreef Simon Horton:
> Thanks for the help, I used the gnuwin32.sf.net zlib packages and now
> have successfully compiled fossil. I know this is all very obvious to
> many of you, but I thought I would write up the detailed steps I took
> to get fossil compiled on windows:-
>
> 1.  Install MinGW (http://www.mingw.org/)
>   - http://sourceforge.net/projects/mingw/files/  (click on the
> download now button - MinGW-5.1.6.exe for me)
>   - Run and answer:
>- Download and Install
>- Current Package
>  - install options
>   - MiGW base tools
>   - g++ compiler
>   - install to C:\MinGW
>   - Add C:\MinGW\bin  to Path system variable (under environmental
> variables in the control panel).
> 2. Install MSYS
>   - I followed information on this wiki page:
> http://www.mingw.org/wiki/msys
>   - http://downloads.sourceforge.net/mingw/MSYS-1.0.11.exe
>   - just follow all of the defaults
>   - http://downloads.sourceforge.net/mingw/msysDTK-1.0.1.exe
>   - Install to C:\msys\1.0
This one isn't necessary unless you want to toy with msys. You have the
order wrong first mingw than msys.
A good replacement installer for mingw is at
 http://www.tdragon.net/recentgcc/
>   -
> http://sourceforge.net/projects/mingw/files/MSYS%20Base%20System/msys-1.0.11/msysCORE-1.0.11-bin.tar.gz/download
>   - Extract to C:\MinGW
>   - Set Environment variable HOME to C:\msys\1.0\home (under
> environmental variables in the control panel).
>
> 3. Download zlib  (from 
> http://gnuwin32.sourceforge.net/packages.html )
>   - http://gnuwin32.sourceforge.net/downlinks/zlib-bin-zip.php
>   - Extract to C:\MinGW
>   - http://gnuwin32.sourceforge.net/downlinks/zlib-lib-zip.php
>   - Extract to C:\MinGW
> 4. Download fossil source code (to c:/fossil-src in this example)
> 5. Compile fossil
>   - open MSYS link from desktop
>   - cd /c/fossil-src
>make -f Makefile.w32
>
> Now I have a new fossil.exe in c:\fossil-src
>
> /Simon Horton.
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>


-- 
Rene de Zwart

___
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] Noob windows build problems

2010-01-22 Thread Rene de Zwart 
rc/../manifest >>VERSION.h
> ./makeheaders  add_.c:add.h allrepo_.c:allrepo.h bag_.c:bag.h
> blob_.c:blob.h
> bra
> nch_.c:branch.h browse_.c:browse.h captcha_.c:captcha.h cgi_.c:cgi.h
> checkin_.c:
> checkin.h checkout_.c:checkout.h clearsign_.c:clearsign.h clone_.c:clone.h
> comfo
> rmat_.c:comformat.h configure_.c:configure.h construct_.c:construct.h
> content_.c
> :content.h db_.c:db.h delta_.c:delta.h deltacmd_.c:deltacmd.h
> descendants_.c:des
> cendants.h diff_.c:diff.h diffcmd_.c:diffcmd.h doc_.c:doc.h
> encode_.c:encode.h f
> ile_.c:file.h finfo_.c:finfo.h http_.c:http.h http_socket_.c:http_socket.h
> http_
> transport_.c:http_transport.h info_.c:info.h login_.c:login.h
> main_.c:main.h
> man
> ifest_.c:manifest.h md5_.c:md5.h merge_.c:merge.h merge3_.c:merge3.h
> name_.c:nam
> e.h pivot_.c:pivot.h pqueue_.c:pqueue.h printf_.c:printf.h
> rebuild_.c:rebuild.h
> report_.c:report.h rss_.c:rss.h rstats_.c:rstats.h schema_.c:schema.h
> search_.c:
> search.h setup_.c:setup.h sha1_.c:sha1.h shun_.c:shun.h skins_.c:skins.h
> stat_.c
> :stat.h style_.c:style.h sync_.c:sync.h tag_.c:tag.h th_main_.c:th_main.h
> timeli
> ne_.c:timeline.h tkt_.c:tkt.h tktsetup_.c:tktsetup.h undo_.c:undo.h
> update_.c:up
> date.h url_.c:url.h user_.c:user.h verify_.c:verify.h vfile_.c:vfile.h
> wiki_.c:w
> iki.h wikiformat_.c:wikiformat.h winhttp_.c:winhttp.h xfer_.c:xfer.h
> zip_.c:zip.
> h ./src/sqlite3.h ./src/th.h VERSION.h
> touch headers
> gcc -Os -Wall -DFOSSIL_I18N=0 -L/mingw/lib -I/mingw/include  -I. -I./src
> -o
> add.
> o -c add_.c
> gcc -Os -Wall -DFOSSIL_I18N=0 -L/mingw/lib -I/mingw/include  -I. -I./src
> -o
> allr
> epo.o -c allrepo_.c
> gcc -Os -Wall -DFOSSIL_I18N=0 -L/mingw/lib -I/mingw/include  -I. -I./src
> -o
> bag.
> o -c bag_.c
> gcc -Os -Wall -DFOSSIL_I18N=0 -L/mingw/lib -I/mingw/include  -I. -I./src
> -o
> blob
> .o -c blob_.c
> blob_.c:28:18: zlib.h: No such file or directory
> blob_.c: In function `blob_compress':
> blob_.c:725: warning: implicit declaration of function `compress'
> blob_.c: In function `blob_compress2':
> blob_.c:755: error: `z_stream' undeclared (first use in this function)
> blob_.c:755: error: (Each undeclared identifier is reported only once
> blob_.c:755: error: for each function it appears in.)
> blob_.c:755: error: syntax error before "stream"
> blob_.c:764: error: `stream' undeclared (first use in this function)
> blob_.c:764: error: `alloc_func' undeclared (first use in this function)
> blob_.c:764: error: syntax error before numeric constant
> blob_.c:765: error: `free_func' undeclared (first use in this function)
> blob_.c:765: error: syntax error before numeric constant
> blob_.c:769: warning: implicit declaration of function `deflateInit'
> blob_.c:772: warning: implicit declaration of function `deflate'
> blob_.c:776: error: `Z_FINISH' undeclared (first use in this function)
> blob_.c:778: warning: implicit declaration of function `deflateEnd'
> blob_.c: In function `blob_uncompress':
> blob_.c:818: warning: implicit declaration of function `uncompress'
> blob_.c:820: error: `Z_OK' undeclared (first use in this function)
> make: *** [blob.o] Error 1
>
>
> /Simon Horton
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
The easy thing to do is to download from gnuwin32.sf.net the zlib packages.
binary and developer and install them in your mingw tree.

-- 
Rene de Zwart

___
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] Please contribute Fossil "skins" or "themes"

2009-12-19 Thread Rene de Zwart 
Op Za, 19 december, 2009 22:28, schreef D. Richard Hipp:
> Earlier today, I checked in a version of Fossil that has the ability
> to host multiple "themes" or "skins" for the web interface and that
> allows users (with Admin privilege) to switch between skins with a
> simple mouse click.
>
> However, the current implementation contains only two built-in skins:
> The old default and a new "black" theme which is very similar to the
> default.  It would be good, I think to have 6 to 10 different themes
> that show a wide variety of possible looks.  Therefore, I am calling
> on the user community to submit themes for consideration.
>
> To create a new theme or skin, edit the CSS, header, and footer to
> obtain the look you want.  Then run the following command:
>
>  fossil configuration export skin outputfile.txt
>
> And post the outputfile.txt here.  Thanks for contributing.
>
> D. Richard Hipp
> d...@hwaci.com
>
>
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>


-- 
Rene de Zwart-- The "skin" configuration exported from
-- repository "/home/renez/src/myclone.fossil"
-- on 2009-12-20 03:54:14
REPLACE INTO config VALUES('css','/* General settings for the entire page */
body {
  margin: 0ex 1ex;
  padding: 0px;
  background-color: white;
  font-family: sans-serif;
}

/* The project logo in the upper left-hand corner of each page */
div.logo {
  display: table-cell;
  text-align: center;
  vertical-align: bottom;
  font-weight: bold;
  color: #558195;
}

/* The page title centered at the top of each page */
div.title {
  display: table-cell;
  font-size: 2em;
  font-weight: bold;
  text-align: left;
  padding: 0 0 0 1em;
  color: #558195;
  vertical-align: bottom;
  width: 100%;
}

/* The login status message in the top right-hand corner */
div.status {
  display: table-cell;
  text-align: right;
  vertical-align: bottom;
  color: #558195;
  font-size: 0.8em;
  font-weight: bold;
}

/* The header across the top of the page */
div.header {
  display: table;
  width: 100%;
}

/* The main menu bar that appears at the top of the page beneath
** the header */
div.mainmenu {
  padding: 5px 10px 5px 10px;
  font-size: 0.9em;
  font-weight: bold;
  text-align: center;
  letter-spacing: 1px;
  background-color: #558195;
  color: white;
}

/* The submenu bar that *sometimes* appears below the main menu */
div.submenu {
  padding: 3px 10px 3px 0px;
  font-size: 0.9em;
  text-align: center;
  background-color: #456878;
  color: white;
}
div.mainmenu a, div.mainmenu a:visited, div.submenu a, div.submenu a:visited {
  padding: 3px 10px 3px 10px;
  color: white;
  text-decoration: none;
}
div.mainmenu a:hover, div.submenu a:hover {
  color: #558195;
  background-color: white;
}

/* All page content from the bottom of the menu or submenu down to
** the footer */
div.content {
  padding: 0ex 1ex 0ex 2ex;
}

/* Some pages have section dividers */
div.section {
  margin-bottom: 0px;
  margin-top: 1em;
  padding: 1px 1px 1px 1px;
  font-size: 1.2em;
  font-weight: bold;
  background-color: #558195;
  color: white;
}

/* The "Date" that occurs on the left hand side of timelines */
div.divider {
  background: #a1c4d4;
  border: 2px #558195 solid;
  font-size: 1em; font-weight: normal;
  padding: .25em;
  margin: .2em 0 .2em 0;
  float: left;
  clear: left;
}

/* The footer at the very bottom of the page */
div.footer {
  font-size: 0.8em;
  margin-top: 12px;
  padding: 5px 10px 5px 10px;
  text-align: right;
  background-color: #558195;
  color: white;
}

/* Make the links in the footer less ugly... */
div.footer a { color: white; }
div.footer a:link { color: white; }
div.footer a:visited { color: white; }
div.footer a:hover { background-color: white; color: #558195; }

/*  blocks */
pre.verbatim {
   background-color: #f5f5f5;
   padding: 0.5em;
}

/* The label/value pairs on (for example) the ci page */
table.label-value th {
  vertical-align: top;
  text-align: right;
  padding: 0.2ex 2ex;
}

/* For marking important UI elements which shouldn''t be
   lightly dismissed. I mainly use it to mark "not yet
   implemented" parts of a page. Whether or not to have
   a ''border'' attribute set is arguable. */
.achtung {
  color: #ff;
  background: #00;
  border: 1px solid #ff;
}

div.miniform {
font-size: smaller;
margin: 8px;
}



#nav, #nav ul {
float: left;
width: 100%;
list-style: none;
line-height: 1;
background: white;
font-family: sans-serif;
font-weight: bold;
padding: 0;
border: solid #558195;
border-width: 1px 0;
margin: 0 0 1em 0;
}

#nav a {
display: block;

Re: [fossil-users] cross compilling fossil

2009-12-01 Thread Rene de Zwart 
daniel,

I'm just being curious :-) Did you succeed in cross-compiling linux on
windows?

-- 
Rene de Zwart

___
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] Wiki Formatting?

2009-11-29 Thread Rene de Zwart 

Op Za, 28 november, 2009 22:56, schreef Joshua Paine:
> On Sat, 2009-11-28 at 13:18 -0800, Michael wrote:
>>  And, as I recall, there
>>  have been some posts here that show how you can add your
>>  own markup right into your own repositories, if that is
>>  your wish.
>
> Someone showed how to integrate TinyMCE, which edits and produces HTML.
> (Like many programmers, there's hardly any tool I like less, but I'm
> happy for whomever it helps.) I didn't see anything that would make it
> possible to use Markdown or Textile or any other wiki format which is
> edited in plain text and produces HTML for viewing only. I've considered
> using a JavaScript Markdown implementation in my Fossil header to render
> Markdown text stored in the wiki to HTML on the fly, but I think the
> fossil wiki markup would conflict.


I did the TinyMCE integration and worked with it I have got two problems
with it
1) It is difficult to integrate the link attribute
2) You have problems with the  and the 
So tinyMCE or whatever similar you come up with is nice eye-candy
almost fantastic for a "dummy" user but not very practical for the reasons
I mentioned above.
I found it easer to start up my trusty html editor and write my
documentation there.

Because of the link attribute and references to tickets, checkins,...*
an implementation of Textile, Markdown,creole, * isn't just a plugin
system. It needs to connect to fossil so we are talking an implementation.

Basically my (maybe THE) criticism is that there are very few advantages
to use wiki formatting and writing substantial amounts of html in a
textarea isn't, H, Nice.

I understand that reimplementing wiki syntax will break all wiki pages.
Doing it later make more pages break.

Richard you are the "benevolent dictator" so say NO or YES and let put
this discussion to an end (and the bike shredding :-)

(Maybe you should say NO because the bike shredding starts all over with
Textile, Markdown, creole,...* :-)

-- 
Rene de Zwart

___
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] Adding your own pages to fossil

2009-11-28 Thread Rene de Zwart 

Op Za, 28 november, 2009 04:50, schreef Stephan Beal:
> On Fri, Nov 27, 2009 at 1:22 PM, Rene de Zwart  wrote:
>
>> If you do this it is obviously not fossil anymore! Its a nice way to
>> build
>> a small application with a database and built in scm and wiki. with zero
>> administration on windows and linux
>>
>
> Almost two years ago (651 days, says the fossil repo) i actually started
> on
> an app framework for C based around fossil's model - a CGI app which uses
> some built-in database:
>
> http://fossil.wanderinghorse.net/repos/cgi3/
>
> The idea was that client apps could use this lib build full-fledged apps,
> with this lib handling the CGI, db, and output buffering parts (necessary
> for separating headers/body during page generation).
>
> i never got very far with it (once i realized how much work it was gonna
> be
> to handle the CGI input properly), but the basics are there.
>
> The idea still comes back to haunt me every now and then, though, and i
> haven't ruled out making it halfway usable. The fact is, though, that i
> don't aspire to write my apps as CGI apps in C. There are higher-level
> languages for that type of work. But it's still a cool idea, for the
> idea's
> sake.
Your dream came true( and better) you have fossil.
Just as an exercise I made an ajax implementation and let  it be
served from fossil. You have a choice put the javascript in a webpage e.g.
in the fossil executable or serve it from the fossil repository.

In either case you can distribute your application via the web e.g. have
your latest fossil executable available for download and clone the repo.
Source code included. Whoa freedom to the max!
-- 
Rene de Zwart

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

[fossil-users] Adding your own pages to fossil

2009-11-27 Thread Rene de Zwart 
It occurred to me that fossil can be seen as a frame work where you can
serve your own pages. That it has already a permission system and a
database is a big plus.
So i made a hello world page. See the instructions below.

If you do this it is obviously not fossil anymore! Its a nice way to build
a small application with a database and built in scm and wiki. with zero
administration on windows and linux






--instructions

I assume your in fossil directory and al the pages you make are in
custom/pages with extension _c that's Underscore followed by the letter c

mkdir -p custom/pages
--file custom/pages/hello._c
#include "config.h"
#include "hello.h"
/*
** WEBPAGE: hello
*/
void page_hello(void){

  style_header("Hello World");
@ Hello World
  style_footer();
}

---eof hello._c

---file custom/custom.mk

cdir := custom
cpage:= $(cdir)/pages

cbase:=$(basename $(notdir $(wildcard $(cpage)/*._c)))

TRANS_SRC += $(addsuffix .c,$(cbase))
TRANS_H :=$(join $(addsuffix .c:,$(cbase)),$(addsuffix .h,$(cbase)))
OBJ += $(addsuffix .o,$(cbase))

%.c : $(cpage)/%._c
./translate $< > $*.c

%.o : %.c %.h $(SRCDIR)/config.erve
$(XTCC)  -o $*.o -c $*.c


eof custom/custom.mk
edit src/main.mk
line 271 ( ./makeheaders  add_.c:add.h allrepo_.c:allrepo.h ) and add at
eof line $(TRANS_H)

line 229 (all:  $(APPNAME) and add above the line
include custom/custom.mk

make and start fossil as a server and goto
http:/localhost:8080/hello

I advice you to not use the name hello._c but to use a prefix e.g.
cust_hello._c to not clash with fossil names.
The same is true for the c function instead of page_hello use cust_hello.
and also the WEBPAGE: use custom/hello so your url becomes
http://localhost:8080/custom/hello

-- 
Rene de Zwart

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

[fossil-users] cross compilling fossil

2009-11-22 Thread Rene de Zwart 

I have been looking  at cross compiling fossil and have a bit less
intrusive instructions because the Makefile already have a provision for
cross-compiling.

1) Install mingw32-gcc on arch you type Pacman -S mingw32-gcc
2) download zlib unpack and
   CC=i486-mingw32-gcc ./configure
   i486-mingw32-ranlib libz.a
3) Become root and cp libz.a, zconf.h and zlib.h to the mingw dirs mine
   cp libz.a /usr/i486-ming32/lib
   cp zconf.h zlib.h /usr/486-mingw32/include
   exit from root
   You kan remove the zlib source it is not needed anymore.
4) edit Makefile and Makefile.w32
   a) add a line "TARGETCC=gcc"
   b) Change gcc in every TCC= line to $(TARGETCC)

5) if you want to create windows binary do
   make -f Makefile.w32 TARGETCC=i486-mingw32-gcc

6) if you have installed wine and want to a have wine binary
   make TARGETCC=winegcc

Perhaps the under 4 mentioned changes can be added to the Makefiles by
someone with checkin capabilities?

-- 
Rene de Zwart

___
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] Noob Win32 build issues

2009-11-12 Thread Rene de Zwart 
Clark,

What you assume is that fossil can be build in a cross compile environment.
It isn't setup to do that. It has two compile environments
  1) Ms Windows with mingw see below
  2) Unix environments (And probably not all of them)
I had fun in getting the cross compile working but there has never been
any  intention to support this.

So the right answer to your question is
 "you cannot compile fossil for windows under (Arch) Linux with out
additional work".

If you want to build your own windows fossil binary see
http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg00592.html

Thanks for the Wow :-)
Rene

> Wow.  I really appreciate you taking the time to reply with such detailed
> info, Rene.
>
> It seems like a really big departure from the info on the Fossil website,
> and from the Makefile.w32 provided in the source.  I have little
> experience with C compilers, and the like, and I guess I was hoping for a
> simpler solution, like "you just need libthisor that", or "add
> /path/to/some/dir to your path".
>
> Though I'd like to have some of the changes since the last (September)
> release, I think I'll just stick with the precompiled Win32 binaries from
> fossil-scm.org.  And now I see a new one was posted yesterday, so maybe
> that'll do the job for me.
>
> Thanks again.
>
>  -Clark
>
>
>
> - Original Message 
> From: Rene de Zwart 
> To: fossil-users@lists.fossil-scm.org
> Sent: Thu, November 12, 2009 3:07:01 PM
> Subject: Re: [fossil-users] Noob Win32 build issues
>
>> Hello,
>>
>> I'm trying to build the Win32 executable from source, and I'm running
>> into
>> some issues.
>>
>> Fossil:
>> server-code:  bdb6c83a1308a2cd3809b9c482fb4f3819f3d0b9
>> checkout: 107f38dd014ae469dcac1f3e1c4fb230ffdc7d71 2009-10-27
>> 20:15:30
>> UTC
>> parent:   3275d9c63ce62cb1e21f20a0a8c8be5ca1aa19a8 2009-10-21
>> 15:43:23
>> UTC
>> tags: trunk
>>
>> This is on Ubuntu 9.04 Server, gcc v4.3.3, the latest mingw32 as
>> packaged
>> by Ubuntu (sorry, I don't know how to get mingw's version).
>>
>> The Linux build goes just file, and I'm using the generated binary
>> there.
>>
>> But when I try to do the Win32 build, I run into trouble.  My guess is
>> something's missing in my environment.  Any suggestions?
>>
>> Thanks!
>>
>>  -Clark
>>
>> cla...@cdc-linux:~/build/fossil$ make -f Makefile.w32 >~/make.txt
>> In file included from ./src/config.h:33,
>>  from add_.c:27:
>> /mingw/include/ctype.h: In function ‘isalnum’:
>> /mingw/include/ctype.h:154: error: ‘_impmb_cur_max_dll’
>> undeclared
>> (first use in this function)
>> /mingw/include/ctype.h:154: error: (Each undeclared identifier is
>> reported
>> only once
>> /mingw/include/ctype.h:154: error: for each function it appears in.)
>> /mingw/include/ctype.h: In function ‘isalpha’:
>> /mingw/include/ctype.h:155: error: ‘_impmb_cur_max_dll’
>> undeclared
>> (first use in this function)
>> /mingw/include/ctype.h: In function ‘iscntrl’:
>> /mingw/include/ctype.h:156: error: ‘_impmb_cur_max_dll’
>> undeclared
>> (first use in this function)
>> /mingw/include/ctype.h: In function ‘isdigit’:
>> /mingw/include/ctype.h:157: error: ‘_impmb_cur_max_dll’
>> undeclared
>> (first use in this function)
>> /mingw/include/ctype.h: In function ‘isgraph’:
>> /mingw/include/ctype.h:158: error: ‘_impmb_cur_max_dll’
>> undeclared
>> (first use in this function)
>> /mingw/include/ctype.h: In function ‘islower’:
>> /mingw/include/ctype.h:159: error: ‘_impmb_cur_max_dll’
>> undeclared
>> (first use in this function)
>> /mingw/include/ctype.h: In function ‘isprint’:
>> /mingw/include/ctype.h:160: error: ‘_impmb_cur_max_dll’
>> undeclared
>> (first use in this function)
>> /mingw/include/ctype.h: In function ‘ispunct’:
>> /mingw/include/ctype.h:161: error: ‘_impmb_cur_max_dll’
>> undeclared
>> (first use in this function)
>> /mingw/include/ctype.h: In function ‘isspace’:
>> /mingw/include/ctype.h:162: error: ‘_impmb_cur_max_dll’
>> undeclared
>> (first use in this function)
>> /mingw/include/ctype.h: In function ‘isupper’:
>> /mingw/include/ctype.h:163: error: ‘

Re: [fossil-users] Noob Win32 build issues

2009-11-12 Thread Rene de Zwart 
> Hello,
>
> I'm trying to build the Win32 executable from source, and I'm running into
> some issues.
>
> Fossil:
> server-code:  bdb6c83a1308a2cd3809b9c482fb4f3819f3d0b9
> checkout: 107f38dd014ae469dcac1f3e1c4fb230ffdc7d71 2009-10-27 20:15:30
> UTC
> parent:   3275d9c63ce62cb1e21f20a0a8c8be5ca1aa19a8 2009-10-21 15:43:23
> UTC
> tags: trunk
>
> This is on Ubuntu 9.04 Server, gcc v4.3.3, the latest mingw32 as packaged
> by Ubuntu (sorry, I don't know how to get mingw's version).
>
> The Linux build goes just file, and I'm using the generated binary there.
>
> But when I try to do the Win32 build, I run into trouble.  My guess is
> something's missing in my environment.  Any suggestions?
>
> Thanks!
>
>  -Clark
>
> cla...@cdc-linux:~/build/fossil$ make -f Makefile.w32 >~/make.txt
> In file included from ./src/config.h:33,
>  from add_.c:27:
> /mingw/include/ctype.h: In function ‘isalnum’:
> /mingw/include/ctype.h:154: error: ‘_impmb_cur_max_dll’ undeclared
> (first use in this function)
> /mingw/include/ctype.h:154: error: (Each undeclared identifier is reported
> only once
> /mingw/include/ctype.h:154: error: for each function it appears in.)
> /mingw/include/ctype.h: In function ‘isalpha’:
> /mingw/include/ctype.h:155: error: ‘_impmb_cur_max_dll’ undeclared
> (first use in this function)
> /mingw/include/ctype.h: In function ‘iscntrl’:
> /mingw/include/ctype.h:156: error: ‘_impmb_cur_max_dll’ undeclared
> (first use in this function)
> /mingw/include/ctype.h: In function ‘isdigit’:
> /mingw/include/ctype.h:157: error: ‘_impmb_cur_max_dll’ undeclared
> (first use in this function)
> /mingw/include/ctype.h: In function ‘isgraph’:
> /mingw/include/ctype.h:158: error: ‘_impmb_cur_max_dll’ undeclared
> (first use in this function)
> /mingw/include/ctype.h: In function ‘islower’:
> /mingw/include/ctype.h:159: error: ‘_impmb_cur_max_dll’ undeclared
> (first use in this function)
> /mingw/include/ctype.h: In function ‘isprint’:
> /mingw/include/ctype.h:160: error: ‘_impmb_cur_max_dll’ undeclared
> (first use in this function)
> /mingw/include/ctype.h: In function ‘ispunct’:
> /mingw/include/ctype.h:161: error: ‘_impmb_cur_max_dll’ undeclared
> (first use in this function)
> /mingw/include/ctype.h: In function ‘isspace’:
> /mingw/include/ctype.h:162: error: ‘_impmb_cur_max_dll’ undeclared
> (first use in this function)
> /mingw/include/ctype.h: In function ‘isupper’:
> /mingw/include/ctype.h:163: error: ‘_impmb_cur_max_dll’ undeclared
> (first use in this function)
> /mingw/include/ctype.h: In function ‘isxdigit’:
> /mingw/include/ctype.h:164: error: ‘_impmb_cur_max_dll’ undeclared
> (first use in this function)
> /mingw/include/ctype.h: In function ‘isblank’:
> /mingw/include/ctype.h:169: error: ‘_impmb_cur_max_dll’ undeclared
> (first use in this function)
> make: *** [add.o] Error 1
> cla...@cdc-linux:~/build/fossil$
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
>
if your lucky you can do mingw make -f makefile.w32.
But I guess your are not!
determing how the mingw compiler is called for me under arch it is
   i486-mingw32-gcc
determing libs for mingw mine /usr/i486-mingw32/lib
determing incs for mingw mine /usr/i486-mingw32/include
download zlib-1.2.3.tar.gz
mkdir mingw
cd mingw
tar -xvf zlib-1.2.3.tar.gz
cd zlib-1.2.3
CC=i486-mingw32-gcc ./configure
i486-mingw32-ranlib libz.a
cd ..
mkdir fossil
cd fossil
fossil co your-fossil-rep or unzip the src you downloaded
make (yes unix you need unix translate)
rm *.o
vi Makefile.win32
change gcc into i486-mingw32-gcc
change the TCC line from
TCC = i486-mingw32-gcc -Os -Wall -DFOSSIL_I18N=0 -L/mingw/lib
-I/mingw/include
to
TCC = i486-mingw32-gcc -Os -Wall -DFOSSIL_I18N=0 -L/usr/i486-mingw/lib
-I/usr/i486-mingw/include -L../zlib-1.2.3 -I../zlib-1.2.3

save it

make -f Makefile.w32

Have fun,
Rene

___
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] Different layout for fossil

2009-11-05 Thread Rene de Zwart 
>> > Some time ago Richard ask for input on different layout for fossil.
> I
>> made
>> > an attempt for a different layout.. It works in firefox. But in ie6
> it
>> is
>> > not yet perfect. Have a look at it. It is based  on suckerfish  css
>> menu.
>> >
>> > Have fun Rene___
>> > fossil-users mailing list
>> > fossil-users@lists.fossil-scm.org
>> >
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>> >
>> I made it work on windows ie6 and ie7.
>> Corrected the login not from localhost
>> removed the events
>> extended the admin user menu.
>>
>> the header is attached.
>> You (sh)(c)ould change the footer to just 
>>
>> Rene
>
> Pretty neat.
I changed it a bit.
1) defined th1 variable tinymce defaulting to 0 (OFF)
2) if tinymce is true then only load tinymce when current_page is either
tktnew, tktedit, wikiedit or wikiappend
3) Made admin defaults menu (Got bitten and couldn't
   restore the defaults :-)
4) added a footer which only init timymce when name exists.
   which depende on 1 and 2  above
5) moved the fossil logo into the menu. hoover over the logo displays
   fossil version
   fossil build date
   fossil page title
   fossil project name
   fossil login name (if defined)
   fossil page name (if defined)

6 ) some css changes.

Have fun Rene

header
Description: Binary data


footer
Description: Binary data
___
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] Different layout for fossil

2009-11-03 Thread Rene de Zwart 
> Some time ago Richard ask for input on different layout for fossil. I made
> an attempt for a different layout.. It works in firefox. But in ie6 it is
> not yet perfect. Have a look at it. It is based  on suckerfish  css menu.
>
> Have fun Rene___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
I made it work on windows ie6 and ie7.
Corrected the login not from localhost
removed the events
extended the admin user menu.

the header is attached.
You (sh)(c)ould change the footer to just 

Rene

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

[fossil-users] Different layout for fossil

2009-11-03 Thread Rene de Zwart 
Some time ago Richard ask for input on different layout for fossil. I made
an attempt for a different layout.. It works in firefox. But in ie6 it is
not yet perfect. Have a look at it. It is based  on suckerfish  css menu.

Have fun Rene

header
Description: Binary data
___
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] Fossil and tinymce integration

2009-10-29 Thread Rene de Zwart 
>
> On 29 Oct 2009, at 14:13, Rene de Zwart wrote:
>
>> Twylite wrote
>>> Rene de Zwart wrote:
>>>> I just finished integrating tiny mce.
>>>> To start with the downside -;( 'You need to make tinyMce part of the
>>>> Repository!'
>>>>
>>> Please no!  TinyMCE is a bloated monstrosity and produces _horrible_
>>> HTML.  We're struggling to migrate an intranet system from Drupal to
>>> PmWiki on account of the terrible markup produced by TinyMCE.
>>>
>>> If some sort of edit helper is required, please consider MarkItUp
>>> (http://markitup.jaysalvat.com/home/) rather than a WYSIWYG.
>>> MarkItUp
>>> is built on jQuery, which provides the side benefit of giving
>>> Fossil and
>>> excellent JavaScript library for UI enhancement, AJAX features, etc.
>
> I agree with Twylite about TinyMCE generating horrible markup,
> although it does generate code that survives HTML email bodies - the
> most degrading place for CSS as email clients are restrictive and
> inconsistent. I reckon a limited feature WYSIWYG editor would be the
> best idea as it might not be programmers or people familiar with
> markup editing documentation or submitting tickets - users of software
> shouldn't need to learn syntax in order to contribute and communicate
> effectively. In addition to this, having an editor that could get out
> of the way for folk who can write markup would also be a good idea.
>
> Just my £0.02. Your thoughts?
>
> ~ James
Well if you agree with him then you probably want this :-).

mkdir markitup
mkdir markitup/javascript
fossil new markitup.fsl
fossil ui markitup.fsl {configure the project)
download markitup and jquery
unzip in markitup/javascript, cd latest, mv * .., rmdir latest
copy jquery-js to javascript/jquery.js
cd markitup
fossil open ../markitup.fsl
fossil add javascript
fossil commit -m "added markitup an jquery to the project"
fossil ui
select admin/headers add after the  put
  
  

  
  
  

and save
select admin/footer add above the first line


  var m = document.getElementsByTagName('textarea')
  var l = m.length
  var n
 var mySettings = {
nameSpace:   "html", // Useful to prevent multi-instances CSS
conflict
onShiftEnter:{keepDefault:false, replaceWith:'<br />\n'},
onCtrlEnter: {keepDefault:false, openWith:'\n<p>',
closeWith:'</p>\n'},
onTab:   {keepDefault:false, openWith:' '},
markupSet:  [
{name:'Heading 1', key:'1', openWith:'<h1(!(
class="[![Class]!]")!)>', closeWith:'</h1>', placeHolder:'Your
title here...' },
{name:'Heading 2', key:'2', openWith:'<h2(!(
class="[![Class]!]")!)>', closeWith:'</h2>', placeHolder:'Your
title here...' },
{name:'Heading 3', key:'3', openWith:'<h3(!(
class="[![Class]!]")!)>', closeWith:'</h3>', placeHolder:'Your
title here...' },
{name:'Heading 4', key:'4', openWith:'<h4(!(
class="[![Class]!]")!)>', closeWith:'</h4>', placeHolder:'Your
title here...' },
{name:'Heading 5', key:'5', openWith:'<h5(!(
class="[![Class]!]")!)>', closeWith:'</h5>', placeHolder:'Your
title here...' },
{name:'Heading 6', key:'6', openWith:'<h6(!(
class="[![Class]!]")!)>', closeWith:'</h6>', placeHolder:'Your
title here...' },
{name:'Paragraph', openWith:'<p(!( class="[![Class]!]")!)>',
closeWith:'</p>'  },
{separator:'---' },
{name:'Bold', key:'B', openWith:'<strong>', closeWith:'</strong>' },
{name:'Italic', key:'I', openWith:'<em>', closeWith:'</em>'  },
{name:'Stroke through', key:'S', openWith:'<del>',
closeWith:'</del>' },
{separator:'---' },
{name:'Ul', openWith:'<ul>\n', closeWith:'</ul>\n' },
{name:'Ol', openWith:'<ol>\n', closeWith:'</ol>\n' },
{name:'Li', openWith:'<li>', closeWith:'</li>' },
{separator:'---' },
{name:'Picture', key:'P', replaceWith:'<img
src="[![Source:!:<a  rel="nofollow" href="http://]!]"">http://]!]"</a>; alt="[![Alternative text]!]" />' },
{name:'Link', key:'L', openWith:'<a href="[![Link:!:<a  rel="nofollow" href="http://]!]"">http://]!]"</a>;(!(
title="[![Title]!]")!)>', closeWith:'</a>', placeHolder:'Your text
to link...' },
{separator:'---' },
{name:'Clean', replaceWith:function(h) { return
h.selection.replace(/<(.*?)>/g, "") } },
{name:'Preview', call:'preview', className:'preview' }
]
}
  for(var i=0 ;i < l;i++){
n = m[i].name
if( 'comment' == n || 'cmappnd' == n || "w"  == n){
m[i].id = n
$(document).ready(function() {
  $("#" + n).markItUp(mySettings);
});
}
  }
 

and save and DONE.

Congratulations you have markit in fossil for ticket and wiki.

Rene

___
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] Fossil and tinymce integration

2009-10-29 Thread Rene de Zwart 
Twylite wrote
> Rene de Zwart wrote:
>> I just finished integrating tiny mce.
>> To start with the downside -;( 'You need to make tinyMce part of the
>> Repository!'
>>
> Please no!  TinyMCE is a bloated monstrosity and produces _horrible_
> HTML.  We're struggling to migrate an intranet system from Drupal to
> PmWiki on account of the terrible markup produced by TinyMCE.
>
> If some sort of edit helper is required, please consider MarkItUp
> (http://markitup.jaysalvat.com/home/) rather than a WYSIWYG.  MarkItUp
> is built on jQuery, which provides the side benefit of giving Fossil and
> excellent JavaScript library for UI enhancement, AJAX features, etc.

Well if you  prefer xyz AND!! it has the same kind of interfacing as
tinyMCE (e.g. recognizing text areas by name. Because the text areas
doesn't have ids in fossil.) than the drill is exactly the same.

What I did doesn't need to alter fossil. In this way one can test out
support for wysiwyg html editing and decide if it is worth all the
trouble.

It does add the xyz javascript library to every page. But that doesn't
means that fossil is using it. That would require modifying every page.
Which is a major undertaking and creating a dependency on xyz.

BTW I did a bit of testing and I found 3 areas which allow html
elements comment,cmappnd (in ticket) and element w (in wikiedit) so it
makes more sense to test for
('comment' == n || 'cmappnd' == n || "w" == n)
then for
('header' != n && 'footer' != n && 'css' != n)

Rene

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

[fossil-users] Fossil and tinymce integration

2009-10-29 Thread Rene de Zwart 
I just finished integrating tiny mce.
To start with the downside -;( 'You need to make tinyMce part of the
Repository!'

for those interested I can send you the fossil repository 600K 7zip
compressed or follow the receipe

mkdir tiny
mkdir tiny/javascript
fossil new tinymce.fsl
fossil ui tinymce.fsl {configure the project)
download tinymce
unzip in tiny/javascript
cd tiny
fossil open ../tinymce/fsl
fossil add javascript
fossil commit -m "added timymce to the project"
fossil ui
select admin/headers add after the 
   
   

and save
select admin/footer add above the first line

 
  var m = document.getElementsByTagName('textarea')
  var l = m.length
  var n
  for(var i=0 ;i < l;i++){
n = m[i].name
if( 'header' != n && 'footer' != n && 'css' != n){
tinyMCE.init({ mode : 'exact' , elements : n, theme: 'advanced'
,width : '90%' } );
}
  }
 

and save and DONE.
If you clone the repository then the clone repository has the same
capabilities.

Does it make sense to add this to the wiki?

Have fun,

Rene

___
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] extending creole link to include tickets, wiki and checkins

2009-10-18 Thread Rene de Zwart 
>> Robert thanks for the clarification. Is there a planning when the creole
>> parser will be part of the trunk?
>
> No. The creole parser is my own little folly, not part of the main fossil
> development, it is unlikely to be merged with the trunk.
>
> Best Wishes
> --
> Robert
If I want to use the creole parser in my projects what do I need to do then?

___
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] extending creole link to include tickets, wiki and checkins

2009-10-18 Thread Rene de Zwart 
> I'm not sure I understand your request.
>
> The creole parser uses the same link code as the fossil parser. If you use
>
> [[8ae201d843|Link to Ticket]]
>
> A link to the ticket will appear.  The same with check in and other
> artifacts. Any artifact id
> prefix will be converted to an appropriate link. For wiki pages you
> just need to type the name
> of the page. The only confusion would be if a wiki page had the same
> name as an artifact Id,
> which seems unlikely.
>
> If you could explain more fully where the confusion arises and under what
> circumstances the warning message would appear, I will be happy to
> consider
> your suggestion further.
>
>
> --
> Robert

My mistake. It wasn't clear to me that it worked like that.
All the better its already in there.

I liked the creole wiki syntax and it allows a good subset of display
formatting. I say display because that is the primary goal of HTML.

If you want to go to print a thing like
asciiDoc http://www.methods.co.nz/asciidoc/
might be more appropriated. The down side is to incorporate that you need
python and that goes beyond the aims of fossil.

The printed documentation goes beyond fossil, it just wants to have a wiki.
If one wants more documentation for your project then use a text base format
like xml (docbook, Open Office, abiword) or text like asciiDoc or TeX.
Add those files to your project and provide a makefile to produce your
favorite output format e.g. PDF, (X)HTML, RTF, manpage, .

Robert thanks for the clarification. Is there a planning when the creole
parser will be part of the trunk?


Rene

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

[fossil-users] extending creole link to include tickets, wiki and checkins

2009-10-18 Thread Rene de Zwart 
Would it be feasible and of value to amend the creole link command to look
up tickets, check-ins and wiki?  By way of

[[fossil:TYPE:id|title]]

and TYPE being
1) tkt  ticket
2) ci   check-in
3) wiki wikipage

it is a bit verbose and not exportable to other creole parsers but it
plays nice to the link idea.
And it prevents the confusion when someone types in a wiki page
  The system will respond with "Are you sure [y/n]? : "


Rene

___
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] making fossil with mingw32

2009-10-13 Thread Rene de Zwart 
I just tested building it on a "virgin" xp system

download the mingw installer from mingw.org and execute.
downlaod msys installer from mingw and execute.
download and unzip libz binaries and development packages from
gnuwin32.sf.net.
I copied them in c:\MinGW
download fossil binary. i copied fossil.exe to c:\MinGW\bin

open msys and type
   fossil clone http://www.fossil-scm.org/ myclone.fossil
   mkdir fossil
   cd fossil
   fossil open ../myclone.fossil
   make -f Makefile.win32
   ./fossil rebuild
   cp fossil.exe /c/MinGW/bin

Upgrading to the latest
   open msys
   cd fossil
   fossil update
   make -f Makefile.win32
   ./fossil rebuild
   cp fossil.exe /c/MinGW/bin


Rene

___
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] making fossil with mingw32

2009-10-13 Thread Rene de Zwart 
> Recipe to build fossil using MinGW is present at
> http://fossil-scm.org/index.html/finfo?name=win32.txt
>
> This works for me (note a small patch to install zlib):
> - Install MinGW-5.1.4 (with g++ & make)
> - Install MSYS-1.0.11
> - Run following commands in MSYS:
> # Get zlib source & unpack
> wget http://www.zlib.net/zlib-1.2.3.tar.bz2
> mkdir -p /usr/src
> tar -xjvf zlib-1.2.3.tar.bz2 -C /usr/src
> # Download and prepare zlib
> wget http://gd.tuwien.ac.at/gnu/mingw/zlib-1.2.3-mingwPORT.tar.bz2
> tar -xjvf zlib-1.2.3-mingwPORT.tar.bz2
> - Apply following patch to zlib-1.2.3/mingwPORT/mingwPORT.sh:
> ---  patch -t $PATCHFLAGS < ${CURDIR}/mingwPORT.patch
> +++  patch -d /usr/src -t $PATCHFLAGS < ${CURDIR}/mingwPORT.patch
> - Run following commands in MSYS:
> # Build zlib - answer various questions asked
> cd zlib-1.2.3/mingwPORT/
> ./mingwPORT.sh
> # Build fossil
> cd C:/temp
> fossil clone http://fossil-scm.org fossil.fsl
> fossil open fossil.fsl trunk
> make -f Makefile.w32
> strip fossil.exe
>
> - Altu
>
>
use gnuwin32.sf.net to get missing packages
download
http://kent.dl.sourceforge.net/project/gnuwin32/zlib/1.2.3/zlib-1.2.3-lib.zip
unzip in c:\mingw

all I had to do to compile under mingw was
  make -f makefile.win32 SRC=./src (I'm guessing here. it could be SRC=.
but you need to something with SRC=)

Rene

___
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] Some questions about fossil [importing cvs]

2009-10-08 Thread Rene de Zwart 
> Rene de Zwart wrote:
>>> Andreas Kupries wrote:
>>>> See file
>>>>c2f_fossil.tcl
>
>>> #!/bin/sh
>>  echo fossil $* >> /your/log/file
>> rc=`__fossil $*`
>> echo $rc >> /your/log/file
>> echo $rc
>
> Right, the result of the command can be of interest too.
> And the $? variable should hold the exit status of the app after the call.
>
> Note. We assumed a basic bourne sh here. If the shell is a bash we can use
>
>   rc=$(__fossil $*)
>
> instead of the backticks. More readable, nestable, better structured.
>
> --
> Sincerely,
>  Andreas Kupries 
>  Developer @<http://www.activestate.com/>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
there is one slight problem ;-)

fossil get feed with
fossil test-import-manifest 1255003794 By renez: example repostory -f
2 example/first

instead of
fossil test-import-manifest 1255003794 "By renez: example repostory"
-f 2 example/first

I suppose there is a newline between user: and Comment. It is in
c2f_fossil.tcl. I see no parsing of the comment in checkin.c.
Does the cvs commiter get named in fossil? I get the impression that every
thing is filed under the user who does the conversion.

But it is insightful. How on earth did you figured these things out?

Rene

___
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] Some questions about fossil [importing cvs]

2009-10-08 Thread Rene de Zwart 
> Andreas Kupries wrote:
>
>> See file
>>  c2f_fossil.tcl
>>
>> That contains the code exec'ing fossil.
>> Look for the 'Do ...' calls.
>>
>> cvs2fossil basically imports the files first, by revision, using some
>> test-
>> commands to setup the delta-chain. Then it uses some more test- commands
>> to
>> import the changesets, i.e. sets of file revisions.
>
> Another trick useful in such circumstances:
>
>   mv fossil __fossil
>
>   echo <<"eof"
>   #!/bin/sh
echo fossil $* >> /your/log/file
rc=`__fossil $*`
echo $rc >> /your/log/file
echo $rc
>   "eof" > fossil
>
> Essentially create a shell script wrapper around the application which
> logs the
> invokations and their arguments.
>
> --
> Sincerely,
>  Andreas Kupries 
>  Developer @
> ___
> 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] Some questions about fossil [importing cvs]

2009-10-07 Thread Rene de Zwart 
I wonder what the sequence is for importing cvs files into fossil. I tried
to get it from cvs2fossil but got lost.

first you need to get a commit identifier?
assume the following cvs-repository 'example'
first.c with rev 1.1 1.2 1.3 1.4
second.c with rev 1.1 1.2 1.3 1.4 and only one user user1

commit 1 first.c rev 1.1

commit 2 first.c rev 1.2 second.c rev 1.1

commit 3 first.c rev 1.3 second.c rev 1.2

commit 4  second.c rev 1.3

commit 5 first.c rev 1.4 second.c 1.4

cvs2fossil does
create repository 'example' with user1?
then
first.c rev 1.1 1.2 1.3 1.4
and then
second.c rev 1.1 1.2 1.3 1.4

which test-? are used to accomplish this?

Rene
>
> On Oct 7, 2009, at 12:01 PM, Ramon Ribó wrote:
>
>>   1- If someone wants to create a new cvs2fossil, what command can be
>> used to commit a
>> file with an ancient date?
>
> Use undocumented flags to commit:
>
>  --date-override 2009-10-06T12:34:56
>  --user-override userid
>
>>
>>   2- How to revert a file to a different version but saving with a
>> different name?
>
> You can use the web interface to download any version of any file you
> want.  Your web browser will normally let you choose the name.
>
>  From the command-line, you can try using the "test-content-get"
> command:
>
>  fossil test-content-get SHA1-hash-of-file output-filename
>
>
>> ___
>> fossil-users mailing list
>> fossil-users@lists.fossil-scm.org
>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
> D. Richard Hipp
> d...@hwaci.com
>
>
>
> ___
> 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] Possible extensions

2009-10-06 Thread Rene de Zwart 
> p...@planet.nl wrote:
>> Just wanted to know the opinion of the people on this list on two
>> possible extensions.
>>
>> [1] wysiwig wiki
>> There is the fossil wiki language + html and I noticed there is creole
>> branch. Wouldn't it be good for usability if there was a TinyMCE-like
>> option? TinyMCE is not as tiny as the name suggests, but I came across
>> this:
>> http://www.peej.co.uk/projects/wysiwyg.html
>> 
>> which I think is tiny enough (~20K) to be used as a base. Anybody
>> working on something like this?
>
> Someone has actually already done this as a proof-of-concept, it's just
> that you have to include the TinyMCE code in your repository, which is
> less than ideal.
>
> http://thread.gmane.org/gmane.comp.version-control.fossil-scm.user/752
>
> IMHO it would be good to have some seperate "container", as there are
> for tickets and wiki pages, for pieces of javascript code that add
> functionality to the web interface. There was some discussion about this
> a while ago. (I guess the question is, where does the current stuff like
> the site-wide CSS go, and can/should that be extended?)
>
> (The other bit is of course hacking whatever to output fossil markup
> instead of HTML)
>
> I'm currently looking into making a version of wiky -
> http://goessner.net/articles/wiky/ - that works with multiple markup
> languages, including fossil wiki syntax; I personally don't like the
> WYSIWYG model for wikis too much, but I agree it should be an option,
> and I'll face the same integration challenges you will.
>
I made the proof of concept but after thinking more about it I think:
1) Fossil  is to be self contained not depending on external libraries.
2) Changing to a creole parser would make entering descriptions much better.
3) Facilitate the possibility to start an external tool for edits of
complicated docs. Alternative is to edit in a external tool and copy the
source into the textarea.

Most external tools will not show the wiki formatting and might get
confused by <> and/or other wiki formatting.

2 cents Rene


So this is only feassible for html documents


___
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] Fossil space efficiency vs. CVS

2009-08-16 Thread Rene de Zwart 
On Tue, Aug 11, 2009 at 2:53 PM, D. Richard Hipp  wrote:

> We are in the process of converting a 10-year-old project from CVS to
> fossil.  The original CVS tree consist of 957 separate files totalling
> 322,265,419 bytes.  The first cut of the fossil repository is
> 33,091,584 bytes and after cloning (which results in better delta
> compression) reduced to 23,604,224 bytes.

In hindsight that isn't surprising
tags/branch names, log messages, author and dates are spelled out in full
in all the 957 files.
to give an exaggerated example
  An update of all the 957 files with a 1KB log message
  means 957KB growth of CVS (and rewriting 957 files).
  While in fossil it is a much smaller growth.

  For tagging a release 957 files need to be rewritten
  In fossil 957 records are added

It isn't only de compressed delta also the more efficient database
structure of fossil versus CVS which saves space and time.

Rene





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

[fossil-users] dot files fossil-db

2009-07-15 Thread Rene de Zwart 
I wanted to document the fossil (server) database and made graphviz dot file.

I lost interest but maybe it is of value to someone else.

Rene

fossil-db.dot
Description: MS-Word document
<>___
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] adding tinyMCE to fossil

2009-03-24 Thread Rene de Zwart 
> On Tue, Mar 24, 2009 at 11:29 PM, Rene de Zwart 
> wrote:
>> tinyMCE.init({
>>        theme : "advanced",
>>        mode : "textareas"
>> });
>
> This is great! Do you know if tinyMCE is configurable enough for us to
> easily hack it to output fossil-compatible markup?
>
> --
> - stephan beal
> http://wanderinghorse.net/home/stephan/
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
I'm not sure what you mean by fossil-compatible markup.
TinyMce does HTML formatting. I suppose you mean:
   1.  Blank lines are paragraph breaks
No but nothing keeps you from making 'real' paragraphs in HTML
   2. Bullets are "*" surrounded by two spaces at the beginning of the line.
No but nothing keeps you from making 'real' bullets (even nested)in HTML
   3. Enumeration items are a number surrounded by two space at
  the beginning of a line.
No but nothing keeps you from making 'real' Enumeration (even nested)in HTML
   4. Indented paragraphs begin with a tab or two spaces.
No but nothing keeps you from making 'real' paragraphs (even nested)in HTML
   5. Hyperlinks are contained with square brackets: "[target]"
No it doesn't understand but won't object again for external links you
could use real HTML
   6. Most ordinary HTML works.
And that is the beauty you get WYSIWYG editor and fossil (your browser!)
will display it correctly. And the need for doing a preview is almost
gone!
   7.  and .
maybe or else >verbatim< or 


Renez



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

[fossil-users] adding tinyMCE to fossil

2009-03-24 Thread Rene de Zwart 
Hi,

Just to make good on my comment of combining tinyMCE and fossil (a proof
of concept).

1) download
http://surfnet.dl.sourceforge.net/sourceforge/tinymce/tinymce_3_2_2_1.zip
2) unpack to ~/
3) goto the www directory of the fossil checkout
4) ln -s ~/javascript .
5) Admin--> edit header
 Just above  add


tinyMCE.init({
theme : "advanced",
mode : "textareas"
});

6) save (and you get a mess because of th1 and its a valid html header!!)
7) tickets --> New and see a full blow javascript editor :-)

Off course I 'misused' the chkout feature and if one wants to do this for
real fossil has to allow loading of external js from a fixed directory or
a configuration setting $jsurl? What fun that would give you could include
the tabber library and make tabbed  forms or include jscookmenu

Rene

___
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] Please help improve the "look" of fossil.

2009-03-23 Thread Rene de Zwart 
>
> A recurring complaint about fossil is that, it lacks aesthetic
> appeal.  This is perhaps reflective of the unusual tastes of the lead
> programmer, who prefers minimalist and utilitarian "shaker"-style
> designs over the art-deco/eye-candy/bubble-gum appearance that is so
> popular on the web these days.  Nevertheless, we are *very* open to
> improving the look of the fossil program itself and the fossil website
> and eager to accept contributions in this area.
>
> If you have any graphic or artistic talent and can contribute, please
> do so.  Working code is appreciated, but not required.  If you can
> submit a mock-up screenshot of a new look with a few paragraphs of
> description, someone else can be persuaded to do the actual
> implementation.
>
> Here are some specific contributions what will be appreciated:
>
> (1)  A "logo" image for the fossil project
> (2)  Better CSS for the pages generated by fossil
> (3)  Ideas on how to better structure the display of information in
> fossil
> (4)  A redesign of the main fossil website
>
> Thanks you for considering this request.
>
> D. Richard Hipp
> d...@hwaci.com
>
>
>
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
For what it is worth, I'm pleased with the simplicity. You gave a lot of
freedom with the ability to change, so easy, the css and html, headers en
footers. I think I even can get tinyMCE in the ticket page editing box

Being a cvstrac user I would like to see the Milestones and the checkins
against a ticket. I would like to have an option to commit against a
ticket via ?-t ticket?| ?--ticket ticket?. But that would need a table
ticketCheckin(ticket integer,checkin integer, UNIQUE(ticket,checkin))).
But I digress and the ticketing stuff is on the todo list.

I think that form follows function very well in fossil!

Rene de Zwart.


___
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] cvs2fossil "fossil tag branch" is discontinued

2009-02-23 Thread Rene de Zwart 
> Rene de Zwart wrote:
>> Andreas,
>>
>> I changed c2f_fossil.tcl (changed tag branch to branch new)
>
> Was that all which was needed ?
> I.e. has 'branch new' the exact same syntax as 'tag branch' ?
> Only then a 1:1 replacement is possible. Otherwise more code
> changes will be needed to adapt to the changed syntax.
>
I guess it is the same!

>> I tried the option -passes ImportFiles:ImportFinal with the old
>> Statefile
>> no dice.
>
> Hm. What errors did you see ?
>
after a few files I get:
couldn't open "E:/cvs2fossil/cvs2fossil_wspc_4y2oHUEz7c/rpatch":
permission denied
>> I had to redo the whole import.
>
> First think in the situation we are in is to save the statefile before
> retrying
> the passes, so that you have a fixed state you can re-try from multiple
> times,
> i.e. copy saved state to working state, then re-try.
>
> And then basically go backwards through the passes to see from where a
> restart
> is possible and ok. For the passes where a restart showed to be not
> possible we
> will have to preserve error messages and logs to see what is going wrong
> there.
>
>  > It takes a lot of time (+8 hours)
>
> What cvs repo are you working with
+1800 files
+12 branches
+14 authors
>
>> especially the breakcycle
>
> Topological sorting and complex processing of changesets for conflicts,
> yeah.
>
>  > and import branches take a lot of time.
>
> 'Import branches' I would have expected to take less time than 'Import
> files'.
> As the latter has to stash any and all revisions into the database and the
> 'import branches' then 'just' does the changesets and their connections.
>
maybe the change to "branch new"

>> I have no ideas how to speed up the process.
>
> I actually sped up a few of the phases by rewriting them, this should
> actually
> all be in the fossil history of cvs2fossil. However the import phases ...
> To
> make them faster I fear I believe that I would need support from fossil
> for
> bulk loading things ... Actually drh already made fossil faster in that
> area
> IIRC, by capping the length of delta-chains for revisions of the files.
>
> Another possibility for making the import area faster would be to have C
> package implementing these parts of fossil. Then the import would 'just'
> be
> invoking Tcl commands, instead of 'exec'ing the fossil application over
> and
> over again.
a libfossil.so ?
 I know I brought up the subject of speed, but that is caused by the fact
that my attempts with cvs2fossil fail to produce a working repository.
It breaks
 first on tag branch
 second on importing branches
 third on redoing the passes

It doesn't matter, to me, if it takes 48 hours for the conversion as long
as it produces a working repository.

I'm not sure if my cvs repository is a mess. I'm doing a bad job of using
cvs2fossil, problems with cvs2fossil or all of the above.
Unfortunately I'm not at liberty to offer you my cvs repository to see for
your self.
>
>  > Is there any documentation on
>> the "cvs normalization process"?
>
> No, not really.
>
>  > I looked at cvs2subversion but other than
>> the program I could not find info about the  inner workings.
>
> cvs2svn actually has some docs about the problems they encountered with
> cvs and
> how that affected their code and the general architecture. I did not copy
> the
> relevant files into cvs2fossil because the whole of cvs2svn is GPL and I
> did
> not wish to taint the cvs2fossil code base. I worked of cvs2svn, using it
> as
> spiritual guide but the code of cvs2fossil is completely new. The
> architecture
> with the phases is similar tough, and the phases also match quite closely.
>
>  > (how to
>> determine what constitutes a check-in, branche merge etc)
>
>> probably a case of "goto the source Luke" ;-)
>
> Unfortunately yes


___
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] cvs2fossil "fossil tag branch" is discontinued

2009-02-23 Thread Rene de Zwart 
> Rene de Zwart wrote:
>> I'm doing an cvs2fossil import and get
>>
>> e:\mingw\bin\fossil.EXE: the "fossil tag branch" command is discontinued
>> Use the "fossil branch new" command instead.
>> while executing
>> "exec e:/mingw/bin/fossil.EXE tag branch sym-kpn
>> 3eacc87848c4af36bec8e493c392870e5f5fbfe"
>>
>>
>> anyway to adjust and start from state "branch"?
>
> I am not sure what you are asking here.
>
> First, we will certainly have to update cvs2fossil to use the new command.
>
> Second, you are hoping to re-run only the last phase of the import ?
>
> Yes, that is possible, although I am not remembering the option for that
> right
> now. ... cvs2fossil should have a -H, -h, --help option ... Alternative,
> the
> option processor is in a single file, if you are willing to source-dive.
>
> Andreas.
> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>

Andreas,

I changed c2f_fossil.tcl (changed tag branch to branch new)
I tried the option -passes ImportFiles:ImportFinal with the old Statefile
no dice.
I had to redo the whole import. It takes a lot of time (+8 hours)
especially the breakcycle and import branches take a lot of time.

I have no ideas how to speed up the process. Is there any documentation on
the "cvs normalization process"? I looked at cvs2subversion but other than
the program I could not find info about the  inner workings. (how to
determine what constitutes a check-in, branche merge etc)

probably a case of "goto the source Luke" ;-)

Rene

Rene

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

[fossil-users] cvs2fossil "fossil tag branch" is discontinued

2009-02-20 Thread Rene de Zwart 
I'm doing an cvs2fossil import and get

e:\mingw\bin\fossil.EXE: the "fossil tag branch" command is discontinued
Use the "fossil branch new" command instead.
while executing
"exec e:/mingw/bin/fossil.EXE tag branch sym-kpn
3eacc87848c4af36bec8e493c392870e5f5fbfe"


anyway to adjust and start from state "branch"?

Rene

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

[fossil-users] Compiling under mingw

2009-02-17 Thread Rene de Zwart 
fossil :  version [bc857ecd92] 2009-02-13 20:30:30 UTC

If I want to compile fossil under mingw if have to do either
a) edit makefile.w32 to change SRCDIR from ../src to ./src
b) make -f Makefile.w32 SRCDIR=./src

Do I do something wrong?

Regards Rene

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