open source terminal and scanning
Brian K. White
brian at aljex.com
Tue Oct 26 19:36:38 PDT 2010
Small update.. (...edit: not so small anymore)
Although downloading a tar.gz snapshot from git.aljex.com doesn't work,
cloning the repo via git or http does.
It means you can install this git for windows:
http://code.google.com/p/msysgit/downloads/detail?name=Git-1.7.3.1-preview20101002.exe
And then start, All Programs, Git, Git GUI
Clone existing Repository
Source Location: git://git.aljex.com/AljexClient
Target Directory: AljexClient
And hit "Clone"
And it will create directory AljexClient in your %USERHOME% directory
with the repo mirrored inside.
Still looking into github and code.google.com for proper hosting...
You can also just from an msys command line (one is included with this
same package, or you can use cygwin or linux or any *ix that has git):
"git clone git://git.aljex.com/AljexClient"
And it creates a directory AljexClient in the current directory.
I almost have committing/pushing figured out. Well enough already that
this is usable now without worry of losing work later.
.... a couple hours later...
Ok I also have the same stuff up at both github and google
The github is using git. The above mentioned msysgit is a good windows
client. It installs effortlessly and is immediately useable and includes
both an msys bash prompt in which all the git tools work the same as
they would on linux, and a gui which is a little unclear but I managed
after some farting around in it. The git command examples from github
worked out of the box cut/pasted right into the msysgit bash prompt,
including ssh commands to generate keys.
http://github.com/aljex/AljexClient
The code.google.com is using svn. I had to use tortoisesvn and follow
some directions given by a user in the comments on the getting started
page but it worked within a few minutes and was really easy given that
users comment to crib from. The tortoisesvn installer claimed I needed
to reboot, but I didn't reboot and the stuff worked immediately.
Take your pick. I like the model of git better but I like the ease of
use and learning curve of svn better for now. Considering Mark likes svn
and is willing to use it right off the bat, I suppose I don't mind if we
settle on that site the definitive forward moving source from now on. I
think I agree with Marks assessment about maybe git isn't really worth
the extra work for a small project like this.
I am still checking out the different hosting sites other facilities
like parallel hosting of a wiki for documentation, bugtracker,
discussion forums, but code.google seems to be pretty good on all those
counts.
http://code.google.com/p/aljex-client/
Right off the bat, one problem with using the 3rd party to host the
source is I think I can not legally supply the actually working binary
installer on those sites along with the source, because it includes the
proprietary twainsave.dll and a ts.exe with a valid unlock license
compiled-in. I CAN do that on my own machines and on my own hosting
accounts like www.aljex.com hosted on rackspace. It's all the fault of
the terms of the twainsave.dll license.
Got to get Morena going or find some other solution... It's essentially
a broken package until then. Maybe I can talk to them and get permission
to include a demo version of the dll just so that the package will all
build and run out of the box and then the user can get their own
twainsave license if/when they want, but they can have SOMEthing to test
with immediately.
--
bkw
More information about the Filepro-list
mailing list