"Lissi" == [EMAIL PROTECTED] <[EMAIL PROTECTED]> writes:
>> You could add a new Section in the PluckerHomes (check the
>> HKCU\Software\The Plucker Team\ Registry) plucker.ini file. Maybe
>> [Lissi-Shell] and set the keys close_on_exit=1 and close_on_error=1
>> (only supported by the next release). Then this messages disapear.
Lissi> Oh, ok, that's a good reason to expect the latest version :)
Lissi> Still, editing those keys wouldn't be in the scope of a frontend, or
Lissi> would it? IMNSHO the frontend should mind its own business, and not
Lissi> mess with the original app beyond calling it.
Well it depend in the point of view. Lets say plucker's API allow
other programs to store settings with a name. So later this other app
could call the stored settings by a name. I would not say that this
are a mess with the original app.
Keep in mind that the [Lissi-Shell] section are not change any other
thinks in plucker, it is only used if your frontend call it.
The same mechanism are used by the "right-click Frontend" thats
included in the setup (right click in the explorer on a *.html and
select "convert to Plucker"). Its a Frontend (a simple, but..) and the
settings it use are stored in the main plucker ini in the
[CONTEXT_DEFAULT] section.
>> Ahhhgg 1.5 MB, please could you also provide the EXE only for updates
>> :-)
Lissi> http://www.lissi.dusnet.de/PluckerFrontendUpdate.zip
Ahhh, thats a fine small download :-)
>> As i understand you are writing a frontend for the plucker-build
>> command and Krayzel write one for the Predefined Databases (controlled
>> by the Shortcuts in the Plucker Program Group). Is this right?
Lissi> So I understood. But wouldn't it be nice to do it all in one GUI?
Sure if this possible. But i just see that Krayzel use Delphi, so its
maybe difficult :-)
And the other mail:
"Lissi" == [EMAIL PROTECTED] <[EMAIL PROTECTED]> writes:
>> - 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)
Lissi> OK, allthough I don't like it. Setting it means setting it back again
Lissi> or leaving the user in a dir he doesn't expect... Oh, well :)
Never Mind was the user want, the _only_ right value for the
PluckerHome are the Directory were Plucker are installed :-)
You could set a different PluckerHome but then you also need take care
that a plucker.ini with the right settings are there (include the base
settings for the image converter tools).
About the PluckerDir: That the one the user should set. plucker-build
set this to the working Directory so you do not *need* to set this on
the command line (so could could save space here). If the user select
a PluckerDir (eg. C:\Test\Testing) you could add this in the BAT:
C:\
CD\
CD Test\Testing
plucker-build.exe ......
>> - 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).
Lissi> You can't rely on having plucker or plucker-build in the $PATH, it's
Lissi> not done during setup. Perhaps it would be a good idea to add it?
It's done by put a copy of plucker-build.exe in the Windows directory.
So you could access from every place without messing with the PATH
setting. I do not wan't to modify the PATH because the are also a
length limit :-(
The best you could do are access the Registry key
Software\The Plucker Team\Plucker\Path
to read the Plucker Directory and the call:
<PLUCKERDIR>\plucker-build.exe
>> - 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\
Lissi> <small voice> *blush* My own key under "The Plucker Team"?!? </small
voice>> OK.
:-)
Lissi> It's a shame the commandline is limited to 80chars. I wonder
Lissi> whether they think you still punch it to a card?
Well not the command line are limited to 80 chars, only the DOS Box
are limited to that (and there also enough other bugs here :-( ).
As i started with the Windows distribution of Plucker i also used a
BAT file to call the tools similar as you do it. But after receiving a
lot of bug report (because every Windows has its own bug in the DOS
box) i give up this :-(
cu,
Dirk
--
Permanent URLs to the latest Version () of the Plucker Windows installer
- For the Webpage: http://www.dirk-heiser.de/plucker
- Direct Download: http://www.dirk-heiser.de/plucker/plucker.exe [2.79MB]
