> An update to the previous post.
They met underway :)
> I found the Problem. After i created the keys PluckerDir and
> PluckerHome in the "Lissi" Registry it start now.
Fixed.
> Just verified, this work. But you should enclose this parameter (and
> maybe some other) in qoute chars '"' to avoid problems with filenames
> with space inside.
OK.
> sorry i forgot: append then the the parameter -s Lissi-Shell to the
> plucker-build call.
See my other posting. I don't think that I should do that.
> And some extra ideas/hints/suggestions:
>
> - You should _not_ set the pluckerdir and pluckerhome with commandline
> parameters. The plucker-build.exe do it itself. Instead set the
> Active (Working) Directory to the Directory the user chose as the
> Plucker Directory. (The user does not need to set the PluckerHome in
> your shell)
OK, allthough I don't like it. Setting it means setting it back again
or leaving the user in a dir he doesn't expect... Oh, well :)
> - By use a Temporary BAT file you get may problems if the user launch
> your shell more than once and call the database creation more than
> once at the same time. I'm not sure how this work with VB, but you
> could use "CreateProces" to call Plucker-build.exe and wait until it
> finish with "Waitforsingleobject".
The batch file shouldn't be a problem, since it deletes itself right
after it started plucker-build.exe It's hard to click that fast _and_
have different URLs :)
I thought about using CreateProcess, but (there's always one) I
planned to offer a switch to keep the batch and have a whole library
of them. That way I don't need to store all settings. If I did it with
CreateProcess, I have to keep the settings in the registry.
> - plucker-build.exe are in the Path (in the Windows Dir) and in the
> Plucker Dir. So you could simple call it without a path or IMHO the
> better option are read the Plucker Directory from the registry and
> use always this path (eg. C:\Programme\Plucker\plucker-build.exe).
You can't rely on having plucker or plucker-build in the $PATH, it's
not done during setup. Perhaps it would be a good idea to add it?
Can you be sure that plucker-build.exe is always in the plucker-path?
I found no such key in the registry.
>
> - Maybe you wan't use a Subkey of HKCU\The Plucker Team\ to store your
> settings. So all Plucker related registry setting are at one place.
> eg. use HKCU\The Plucker Team\Lissi Plucker Frontend\
<small voice> *blush* My own key under "The Plucker Team"?!? </small
voice> OK.
>
> What do you think?
>
> After all i think its a good start and many users would find it useful
> to use a Frontend instated the commandline. Due its size i suggest to
> offer its as an additional install (the way its already done) and not
> include it in the plucker windows distribution.
The size can't be helped unless I cut out the msvbvm60.dll. That would
shrink it to ~300k. I used to have it as a separate download, but
almost a 3rd of all people who downloaded one of my apps complained
that it wasn't included in the setup. Another third didn't know how to
register libs. The other reason I include it is that I usually have
the latest version of all libs at $WORK.
It's a shame the commandline is limited to 80chars. I wonder whether
they think you still punch it to a card?
Lissi
--
Life ain't fair, but the root password helps.
- BOFH
PGP-Fingerprint:
F119 52A9 A520 B1C5 28B7 BDFE 2B72 9E38 479E 31CC
