2008/5/6 Garth Corral <[EMAIL PROTECTED]>:
>
> Sorry about the previous response.
>
> On May 6, 2008, at 3:11 AM, "Pascal Georges" <[EMAIL PROTECTED]>
> wrote:
>
> >
> > I will commit the change.
> >
> Could you also commit the icon and plist files from the tarball I made?
>
> Thanks in advance.
>
Sent from my iPhone
On May 6, 2008, at 3:11 AM, "Pascal Georges" <[EMAIL PROTECTED]>
wrote:
2008/5/6 Garth Corral <[EMAIL PROTECTED]>:
On May 5, 2008, at 10:40 PM, Garth Corral wrote:
>
> Indeed, I believe that is my fault and you have my sincerest
> apologies. I did add a minsize to t
Sent from my iPhone
On May 6, 2008, at 3:27 AM, "Pascal Georges" <[EMAIL PROTECTED]>
wrote:
>
> I agree with you. I certainly was too quick making some changes in ./
> configure (for config.tcl generation) and comiting the change that
> got rid of "@SHAREDIR@" in config.tcl.conf (but nothi
Sorry about the previous response.
On May 6, 2008, at 3:11 AM, "Pascal Georges" <[EMAIL PROTECTED]>
wrote:
>
> I will commit the change.
>
Could you also commit the icon and plist files from the tarball I made?
Thanks in advance.
Garth
---
2008/5/6 Alexander Wagner <[EMAIL PROTECTED]>:
>
> Actually, placing the engines within the path works on Unix.
> Probalbly searching in $PATH first and then in engines/
> subdir below scid could solve this?
>
If you enter as exec "crafty" -> it will be searched in $PATH, if you enter
"/opt/engin
On May 6, 2008, at 3:11 AM, Pascal Georges wrote:
> The solution is to simply ask PGN window to save/restore its size :
> it used to save its geometry layout, but forgot to restore it. So it
> is sufficient to add
>
> setWinSize $w
>
> instead of any "wm minsize ..."
>
> I will commit the
Pascal Georges wrote:
Hi!
> A couple questions. In looking at the unix makefile, it appears that
> the engines are all installed in $(SHAREDIR)/engines. Since I think
> it unlikely that directory would be a user's path, is there some
> facility for finding that directory by
Garth Corral wrote:
Hi!
>> On May 5, 2008, at 9:00 PM, Alexander Wagner wrote:
>>> Pascal Georges wrote:
>>>
>>> Good Morning!
>>>
>>> [...]
Great. I commited your patches into CVS as 95% of it is ok (and this
will help me to start from that base). So we have time to think
2008/5/6 Marcin Kasperski <[EMAIL PROTECTED]>:
> > Maybe there are things I did not get, but I don't see the point in
> packaging
> > data and exec separately : I have some dependencies between data and
> some
> > features (training, books), and I'd prefer things to come in one simple
> > package.
>
>
> A couple questions. In looking at the unix makefile, it appears that
> the engines are all installed in $(SHAREDIR)/engines. Since I think
> it unlikely that directory would be a user's path, is there some
> facility for finding that directory by default in scid? That is,
> without configu
2008/5/6 Garth Corral <[EMAIL PROTECTED]>:
>
> On May 5, 2008, at 10:40 PM, Garth Corral wrote:
> >
> > Indeed, I believe that is my fault and you have my sincerest
> > apologies. I did add a minsize to the pgn window precisely for the
> > reason that I stated, the window collapsed due to no othe
> Maybe there are things I did not get, but I don't see the point in packaging
> data and exec separately : I have some dependencies between data and some
> features (training, books), and I'd prefer things to come in one simple
> package. I don't think a package about 10 MB is too big.
Pascal, th
On May 5, 2008, at 1:55 AM, Pascal Georges wrote:
>
> This brings up another topic. The scid_app target does not try to
> build any engines nor include them in the bundle. I'm not quite sure
> of the right thing to do here. On one hand, I like to install and
> manage my engines independently, o
On May 5, 2008, at 10:40 PM, Garth Corral wrote:
>
> Indeed, I believe that is my fault and you have my sincerest
> apologies. I did add a minsize to the pgn window precisely for the
> reason that I stated, the window collapsed due to no other UI
> elements. Perhaps I should have set the geometr
On May 5, 2008, at 9:32 PM, Garth Corral wrote:
>
> On May 5, 2008, at 9:00 PM, Alexander Wagner wrote:
>> Pascal Georges wrote:
>>
>> Good Morning!
>>
>> [...]
>>> Great. I commited your patches into CVS as 95% of it is ok (and this
>>> will help me to start from that base). So we have time to th
On May 5, 2008, at 9:00 PM, Alexander Wagner wrote:
> Pascal Georges wrote:
>
> Good Morning!
>
> [...]
>> Great. I commited your patches into CVS as 95% of it is ok (and this
>> will help me to start from that base). So we have time to think about
>> the 5% left : @SHAREDIR@ in config.tcl.conf.
>
Pascal Georges wrote:
Good Morning!
[...]
> Great. I commited your patches into CVS as 95% of it is ok (and this
> will help me to start from that base). So we have time to think about
> the 5% left : @SHAREDIR@ in config.tcl.conf.
> I tested on Windows and I got no problem.
Sorry, I do not
2008/5/5 Alexander Wagner <[EMAIL PROTECTED]>:
> Pascal Georges wrote:
>
> Hi!
>
> > > This means there is no longer a need for config.tcl.conf, as it
> > will not be
> > > generated by autoconf : I will wait until everything is
> > validated, then
> > > simplify those thing
Garth Corral wrote:
Hi!
> In addition to the menu changes, there are a couple of small changes
> around scidShareDir to accommodate installation of an application
> bundle in an arbitrary location; scidShareDir was set to a static
> value of /usr/local/share/scid in the configure script. I h
2008/5/5 Garth Corral <[EMAIL PROTECTED]>:
>
> On May 5, 2008, at 10:43 AM, Pascal Georges wrote:
> > Maybe there are things I did not get, but I don't see the point in
> > packaging data and exec separately : I have some dependencies
> > between data and some features (training, books), and I'd p
Pascal Georges wrote:
Hi!
> > This means there is no longer a need for config.tcl.conf, as it
> will not be
> > generated by autoconf : I will wait until everything is
> validated, then
> > simplify those things.
>
> The point of this file was to make it possible
Pascal Georges wrote:
Hi!
> Point is, if you assume a Unix installation, scid is
> owned by root and not by the user. And thogh bases and
> books are an exception there're still some files with
> scid that are kept "for the site" and not "for the
> user". Usually these ar
On May 5, 2008, at 10:43 AM, Pascal Georges wrote:
> Maybe there are things I did not get, but I don't see the point in
> packaging data and exec separately : I have some dependencies
> between data and some features (training, books), and I'd prefer
> things to come in one simple package. I
2008/5/5 Garth Corral <[EMAIL PROTECTED]>:
>
> On May 5, 2008, at 6:48 AM, Marcin Kasperski wrote:
> >>> The point of this file was to make it possible to build scid
> >>> in Linux "packaged" way, where binaries and data are not
> >>> installed together, but we use sth like /usr/bin/scid (or
> >>>
On May 5, 2008, at 6:48 AM, Marcin Kasperski wrote:
>>> The point of this file was to make it possible to build scid
>>> in Linux "packaged" way, where binaries and data are not
>>> installed together, but we use sth like /usr/bin/scid (or
>>> /usr/games/scid) and /usr/share/scid/data/
>>
>> G
2008/5/5 Marcin Kasperski <[EMAIL PROTECTED]>:
> > > The point of this file was to make it possible to build scid
> > > in Linux "packaged" way, where binaries and data are not
> > > installed together, but we use sth like /usr/bin/scid (or
> > > /usr/games/scid) and /usr/share/scid/data/
> >
> > The point of this file was to make it possible to build scid
> > in Linux "packaged" way, where binaries and data are not
> > installed together, but we use sth like /usr/bin/scid (or
> > /usr/games/scid) and /usr/share/scid/data/
>
> Given that books and bases directories are now user
> co
2008/5/5 Marcin Kasperski <[EMAIL PROTECTED]>:
> > This means there is no longer a need for config.tcl.conf, as it will not
> be
> > generated by autoconf : I will wait until everything is validated, then
> > simplify those things.
>
> The point of this file was to make it possible to build scid
>
> This means there is no longer a need for config.tcl.conf, as it will not be
> generated by autoconf : I will wait until everything is validated, then
> simplify those things.
The point of this file was to make it possible to build scid
in Linux "packaged" way, where binaries and data are not ins
2008/5/5 Garth Corral <[EMAIL PROTECTED]>:
>
> The menu/makefile patch isn't enough to build an application bundle,
> there's also an icon file (scid.icns) that I created from the
> original, and a plist file (Info.plist) that need to be part of the
> bundle. I've included these plus an extra pat
On May 4, 2008, at 10:36 PM, Garth Corral wrote:
>
> If any mac users want to try this out they can (SEE NOTES BELOW
> FIRST):
>
> cd
> curl -O http://www.abode.com/scid/scid-2008050503-osx-menus.tar.bz2
> cvs -d :pserver:[EMAIL PROTECTED]:/cvsroot/scid2
> co -
> d scid scid2 # be sure you'
On May 1, 2008, at 11:33 AM, Garth Corral wrote:
>
> On May 1, 2008, at 10:57 AM, pgeorges wrote:
>> Garth Corral a écrit :
>>> Hi all,
>>>
>>> Work that needs to be done:
>>> 1.) Clean up the patch to catch and problems regressions on windows/
>>> unix. I'm sure there are nits in there as I have
Garth Corral a écrit :
>
> One semi-unrelated note. After making some changes I noticed that a
> subsequent commit to tcl/tools/graphs.tcl occurred that (from what I
> can tell) contains only line ending changes (from \n to \rn). It's
> not my place to say, but this seems bad on a couple of fr
On May 1, 2008, at 1:19 PM, "Benoit St-Pierre" <[EMAIL PROTECTED]>
wrote:
> Hello Garth,
>
> Would it be possible and easy to create and maintain a .dmg for OSX
> users ?
> This would be very interesting to improve Scid user base.
> If it's so easy that even I can do it, I'd certainly do that
Hello Garth,
Would it be possible and easy to create and maintain a .dmg for OSX users ?
This would be very interesting to improve Scid user base.
If it's so easy that even I can do it, I'd certainly do that.
I hope it's a yes,
Best regards,
Benoit
-
On May 1, 2008, at 10:57 AM, pgeorges wrote:
> Garth Corral a écrit :
>> Hi all,
>>
>> Work that needs to be done:
>> 1.) Clean up the patch to catch and problems regressions on windows/
>> unix. I'm sure there are nits in there as I have not extensively
>> tested it on OS X nor unix (I don't hav
On May 1, 2008, at 9:46 AM, Cory Helfrich wrote:
> Hello Garth,
>
>
> On May 1, 2008, at 7:19 PM, Garth Corral wrote:
>> menu bar on top of the display as they expect. Now this will only
>> work when built against the Tcl/Tk libraries shipped with OS X and
>> when installed as an application bund
Garth Corral a écrit :
> Hi all,
>
> Work that needs to be done:
> 1.) Clean up the patch to catch and problems regressions on windows/
> unix. I'm sure there are nits in there as I have not extensively
> tested it on OS X nor unix (I don't have a windows box on which to
> test).
>
>
Hi,
Hello Garth,
On May 1, 2008, at 7:19 PM, Garth Corral wrote:
> menu bar on top of the display as they expect. Now this will only
> work when built against the Tcl/Tk libraries shipped with OS X and
> when installed as an application bundle (e.g. double-clickable
> Scid.app). If users choose to
Hi all,
I apologize if this posting is a bit long but I hope you'll bear with
me.
I have a few questions and comments regarding scid on OS X. First a
bit of background. I'm recently back to trying to use scid on OS X
after a very long time away. I had tried it out back in mid 2002 when
40 matches
Mail list logo