Clarion 7 Accessory Deployment Demo [January 03, 2009]

[NewsArchive]

SoftVelocity Clarion Third-Party Developers,

We have released an enhanced experimental "Clarion Accessory Deployment" demo. This demo supports automatic "Clarion 7" Template Registration and Unregistration. It also demonstrates how to deploy to "Clarion 6" and "Clarion 7" from the same setup.exe.

Please download and install the following experimental Examples package (the download is login protected)

http://lindersoft.com/sb6_Examples.exe

Note: we have renamed the "Clarion Template Deployment.sb6" to "Clarion Accessory Deployment Demo.sb6" in the new #2465 Examples package. To use the new "Clarion Accessory Deployment Demo.sb6", you need at least SetupBuilder 6.9 Build 2454!

- accessory1.jpg screenshot. The same folder tree can be used for C6 and C7 accessory deployment.

- accessory2.gif screenshot. This SetupScript source code is used to handle the different folder structure "standards" for Clarion 6 and Clarion 7.

Please open, compile and run "Clarion Template Deployment.sb6". The installer will install a "SB_TEST.TPL" test template to the appropriate Clarion template folder and register it. It will install a DING.WAV test file to the appropriate Examples folder and a SB6.htm test file to the Documents folder. If you run Uninst_Clarion Accessory.exe, the uninstall application will remove all files and unregister the template from C7.

---------
Clarion 7
---------

Support for the Clarion 7 "Accessory" folder structure:
<ROOT>\accessory\bin
<ROOT>\accessory\images
<ROOT>\accessory\lib
<ROOT>\accessory\libsrc\win
<ROOT>\accessory\resources
<ROOT>\accessory\template\win

By default, examples are installed to the "SoftVelocity\Clarion7\accessory\<product>" subdirectory of CSIDL_COMMON_DOCUMENTS.

By default, help and online documentation files are installed to the "SoftVelocity\Clarion7\accessory\<product>\Docs" subdirectory of
CSIDL_COMMON_DOCUMENTS.

The EXAMPLESFOLDER dialog allows users to change the examples/documents folder location.

The uninstall .exe and .log are created in <ROOT>\accessory\template.

If "Examples" is a subdirectory of CSIDL_COMMON_DOCUMENTS and the Windows OS is less than Vista then give write-access to the example folder.

---------
Clarion 6
---------
Support for the Clarion 6 "3rdparty" folder structure:
<ROOT>\3rdparty\bin
<ROOT>\3rdparty\docs
<ROOT>\3rdparty\examples
<ROOT>\3rdparty\images
<ROOT>\3rdparty\lib
<ROOT>\3rdparty\libsrc
<ROOT>\3rdparty\rsc
<ROOT>\3rdparty\template

By default, examples are installed to the "<ROOT>\3rdparty\examples" subdirectory. The EXAMPLESFOLDER dialog allows users to change the examples folder location.

The uninstall .exe and .log are created in %_SB_INSTALLDIR%.

Please let me know what you think.

Thanks,
Friedrich

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

SetupBuilder "point. click. ship"
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Thanks Friedrich!

Saved for later testing.

--
Russell B. Eggen
www.radfusion.com
Skype Clarion chat: http://tinyurl.com/2273lm

[NewsArchive]

ff is the culprit ..... 33 :)

--

Thank you - Merci

Cordialement - Best Regards
Jean-Pierre GUTSATZ

DMC - Data Management Center - A tool to let you Migrate Import Export
Transfer all your Data very easily
www.dmc-fr.com
Certified by Microsoft : "Works with Vista" & "Works with Windows Server
2008"

[NewsArchive]

Quick question, don't want to start a long thread. Should examples end with
a folder of "Examples" since Documents ends with a folder of "Docs" (and
they are in the same tree)?

Thanks,

Bill Roe
www.valutilities.com

[NewsArchive]

Hi Bill,

Hmm, very good question! I am a little brain dead right now.... I have to
give it some thoughts.

Friedrich

[NewsArchive]

Bill,

I am not sure at all but it seems that only examples go there so no need

Now that path _I feel_ is way too long
C:\Users\Public\Documents\SoftVelocity\Clarion7\ac cessory\CoolAppDemo

softvelicity (useless i'd say)
clarion
accessory (useless i'd say)

I would suggest cleaning it out a bit as after all Clarion 7 is the ONLY one
from SV today and when Net comes out they can easily change to something
else they prefer, no ?
what is accessory for _here_ ?
examples maybe IF there is something else to install in here ....
C:\Users\Public\Documents\Clarion7\YourAppNameGoes Here

makes it way easier to type when needed and easier too to save as closer to
root .....

my 0.000000000000000000000000000000000000000000001 cent
:)

anyway till ..... feel free to test as you prefer
juts put images in images and not under appname

docs till ... I would also say root/accessory/documents/YourAppname etc
......

"docs" or "documents" ..... I'd eventually prefer "documents" as it makes it
less "friendly buddy chappy style maybe ...but ....

again till ... you choose ...

--

Thank you - Merci

Cordialement - Best Regards
Jean-Pierre GUTSATZ

DMC - Data Management Center - A tool to let you Migrate Import Export
Transfer all your Data very easily
www.dmc-fr.com
Certified by Microsoft : "Works with Vista" & "Works with Windows Server
2008"

[NewsArchive]

Hi Friedrich,

> By default, examples are installed to the
> "SoftVelocity\Clarion7\accessory\<product>"
> subdirectory of CSIDL_COMMON_DOCUMENTS.

I have opted to use <vendor>\<product> for this. I think either would work
fine. I like to keep my products under the vendor name, but I don't think
it should make any difference.

> By default, help and online documentation files are installed to the
> "SoftVelocity\Clarion7\accessory\<product>\Docs" subdirectory of
> CSIDL_COMMON_DOCUMENTS.

Since documentation does not require write access it was suggested (I think
by Bruce Johnson at some point) to put docs into
Program_Files\Softvelocity\Clarion7\accessory. I have done that in my
installs under accessory\documents\Icetips\<product> as I realized there
wasn't any reason really to put them into COMMON_DOCUMENTS...

> The uninstall .exe and .log are created in <ROOT>\accessory\template.

Hmm.... Why in "template" I have changed my installers based on your idea
to use "uninstall" folder under accessory.

> If "Examples" is a subdirectory of CSIDL_COMMON_DOCUMENTS and the Windows OS
> is less than Vista then give write-access to the example folder.

I'm doing this regardless of OS. Any problems doing this under Vista also?

> The uninstall .exe and .log are created in %_SB_INSTALLDIR%.

I'm installing it into a "uninstall" folder for both C7 and previous
versions.

Best regards,

--
Arnór Baldvinsson - Icetips Creative, Inc.
Port Angeles, Washington
www.icetips.com - www.buildautomator.com

Icetips product subscriptions at http://www.icetips.com/subscribe.php

[NewsArchive]

Hi Arnór,

>> By default, examples are installed to the
>> "SoftVelocity\Clarion7\accessory\<product>"
>> subdirectory of CSIDL_COMMON_DOCUMENTS.
>
> I have opted to use <vendor>\<product> for this. I think either would
> work fine. I like to keep my products under the vendor name, but I don't
> think it should make any difference.

I'll add a "universal" identifier to the project. So you can use your
<productname> or <vendorname> or <vendorname>\<productname>, etc.

>> By default, help and online documentation files are installed to the
>> "SoftVelocity\Clarion7\accessory\<product>\Docs" subdirectory of
>> CSIDL_COMMON_DOCUMENTS.
>
> Since documentation does not require write access it was suggested (I
> think by Bruce Johnson at some point) to put docs into
> Program_Files\Softvelocity\Clarion7\accessory. I have done that in my
> installs under accessory\documents\Icetips\<product> as I realized there
> wasn't any reason really to put them into COMMON_DOCUMENTS...

Yes, perhaps Bruce's suggestion is better.

If others do not mind, I'll change the documentation path to:

<ROOT>\accessory\documents

>> The uninstall .exe and .log are created in <ROOT>\accessory\template.
>
> Hmm.... Why in "template" I have changed my installers based on your
> idea to use "uninstall" folder under accessory.

Argh! Should read "uninstall". It's correctly handled in the project, but
incorrect in the notes.

>> If "Examples" is a subdirectory of CSIDL_COMMON_DOCUMENTS and the Windows
>> OS is less than Vista then give write-access to the example folder.
>
> I'm doing this regardless of OS. Any problems doing this under Vista
> also?

Should not be a problem.

>> The uninstall .exe and .log are created in %_SB_INSTALLDIR%.
>
> I'm installing it into a "uninstall" folder for both C7 and previous
> versions.

Good idea. I'll change it!

Friedrich

[NewsArchive]

Friedrich,

Another vote for Bruce's path for documents under "accessory" or whatever
.....
way easier there indeed

Excellent idea the uninstaller in it's own "accesssory" or whatever
/uninstaller

makes all cleaner

and moreover you are doing all our work : way too much MERCI :)

--

Thank you - Merci

Cordialement - Best Regards
Jean-Pierre GUTSATZ

DMC - Data Management Center - A tool to let you Migrate Import Export
Transfer all your Data very easily
www.dmc-fr.com
Certified by Microsoft : "Works with Vista" & "Works with Windows Server
2008"

[NewsArchive]

Hi Friedrich,

> I'll add a "universal" identifier to the project. So you can use your
> <productname> or <vendorname> or <vendorname>\<productname>, etc.

Since I have a few products it makes sense to _me_ to keep it under
icetips\productname. But I don't see a problem with someone to just use the
product name.

>> installs under accessory\documents\Icetips\<product> as I realized there
>> wasn't any reason really to put them into COMMON_DOCUMENTS...
>
> Yes, perhaps Bruce's suggestion is better.
>
> If others do not mind, I'll change the documentation path to:
>
> <ROOT>\accessory\documents

I don't want to start wars over this<g> It's just that we have always had
Clarion\Docs and 3rdParty\Docs it makes sense to _me_ to have
accessory\documentation or something like that for the docs. I don't see a
reason to mix them in with other stuff.

> Argh! Should read "uninstall". It's correctly handled in the project, but
> incorrect in the notes.

Sounds good:)

>> I'm doing this regardless of OS. Any problems doing this under Vista
>> also?
>
> Should not be a problem.

Excellent!

Best regards,

--
Arnór Baldvinsson - Icetips Creative, Inc.
Port Angeles, Washington
www.icetips.com - www.buildautomator.com

Icetips product subscriptions at http://www.icetips.com/subscribe.php

[NewsArchive]

>> I'll add a "universal" identifier to the project. So you can use your
>> <productname> or <vendorname> or <vendorname>\<productname>, etc.
>
> Since I have a few products it makes sense to _me_ to keep it under
> icetips\productname. But I don't see a problem with someone to just use the
> product name.

I like Friedrich's "universal" identifier idea too.

This is one of those areas where I figure there will be significant
differences of opinion on which way to go, so making either way a part of
the standard here will be a good thing IMHO.

From the EUD (End User Developer) perspective, even if they don't know (at
first) which way a developer is installing, at least they won't have to dig
all over the hard drive to find it.

This WOULD be a good thing for each developer to be sure to include in
their docs (prominent and right up front) and even a MESSAGE at the end of
the install advising the location might be a good thing.

If it was done inside the installer, all that you'd need to do is reference
the path where SB installed it and it would be clear as to exactly where
that was.


>> If others do not mind, I'll change the documentation path to:
>> <ROOT>\accessory\documents
>
> I don't want to start wars over this<g> It's just that we have always had
> Clarion\Docs and 3rdParty\Docs it makes sense to _me_ to have
> accessory\documentation or something like that for the docs. I don't see a
> reason to mix them in with other stuff.

I agree 100% here.

The docs are read only, so the location under Program Files is no big deal
and for those coming to Clarion 7 from older versions (most of us for now),
the docs will be in the general neighborhood of where they were before.

:-)

Charles


--
-------------------------------------------------------------------------------------------------------
Charles Edmonds
www.ezchangelog.com - "Free ChangeLog software to manage your projects!"
www.setupcast.com - "A revolutionary new publishing system for software
developers - enhanced for SetupBuilder users!"
www.pagesnip.com - "Print and Save the Web, just the way you want it!"
www.clarionproseries.com - "Serious imaging tools for Clarion Developers"
www.ezround.com - "Round Corner HTML tables with matching Banners, Buttons
and Forms!"
www.lansrad.com - "Intelligent Solutions for Universal Problems"
www.fotokiss.com - "World's Best Auction Photo Editor"
-------------------------------------------------------------------------------------------------------

[NewsArchive]

Hi Charles,

> From the EUD (End User Developer) perspective, even if they don't know (at
> first) which way a developer is installing, at least they won't have to dig
> all over the hard drive to find it.

Yep.

> This WOULD be a good thing for each developer to be sure to include in
> their docs (prominent and right up front) and even a MESSAGE at the end of
> the install advising the location might be a good thing.

I put it in a readme kind of dialog that shows at the end of the install.
Just a short information about what demos are included and where they are.
But telling someone to go to COMMON_DOCUMENTS - where the heck is that???
I'm wondering if there is a way to update the RTF in there to show the value
of the %CSIDL_COMMON_DOCUMENTS% (or other variables) when the install runs.

FRIEDRICH!!!<g>


> The docs are read only, so the location under Program Files is no big deal
> and for those coming to Clarion 7 from older versions (most of us for now),
> the docs will be in the general neighborhood of where they were before.

Exactly:)

Best regards,

--
Arnór Baldvinsson - Icetips Creative, Inc.
Port Angeles, Washington
www.icetips.com - www.buildautomator.com

Icetips product subscriptions at http://www.icetips.com/subscribe.php

[NewsArchive]

> I put it in a readme kind of dialog that shows at the end of the install.
> Just a short information about what demos are included and where they are.
> But telling someone to go to COMMON_DOCUMENTS - where the heck is that???
> I'm wondering if there is a way to update the RTF in there to show the value
> of the %CSIDL_COMMON_DOCUMENTS% (or other variables) when the install runs.

Just check the SetupBuilder source code of the Enhanced WebUpdate Client
included with your copy of SetupCast!

You'll see exactly how to do it.

Does that help?

Charles


--
-------------------------------------------------------------------------------------------------------
Charles Edmonds
www.ezchangelog.com - "Free ChangeLog software to manage your projects!"
www.setupcast.com - "A revolutionary new publishing system for software
developers - enhanced for SetupBuilder users!"
www.pagesnip.com - "Print and Save the Web, just the way you want it!"
www.clarionproseries.com - "Serious imaging tools for Clarion Developers"
www.ezround.com - "Round Corner HTML tables with matching Banners, Buttons
and Forms!"
www.lansrad.com - "Intelligent Solutions for Universal Problems"
www.fotokiss.com - "World's Best Auction Photo Editor"
-------------------------------------------------------------------------------------------------------

[NewsArchive]

Hi Charles,

> Just check the SetupBuilder source code of the Enhanced WebUpdate Client
> included with your copy of SetupCast!

DOH! I _knew_ I had read about this somewhere!<g>

Best regards,

--
Arnór Baldvinsson - Icetips Creative, Inc.
Port Angeles, Washington
www.icetips.com - www.buildautomator.com

Icetips product subscriptions at http://www.icetips.com/subscribe.php

[NewsArchive]

Arnor,

Anyway a message in SB with
%INSTALL_EXAMPLE_PATH% if that is the variable you use will be translated to
user and he will "see" the real path on _his_ machine :)


--

Thank you - Merci

Cordialement - Best Regards
Jean-Pierre GUTSATZ

DMC - Data Management Center - A tool to let you Migrate Import Export
Transfer all your Data very easily
www.dmc-fr.com
Certified by Microsoft : "Works with Vista" & "Works with Windows Server
2008"

[NewsArchive]

> Anyway a message in SB with
> %INSTALL_EXAMPLE_PATH% if that is the variable you use will be translated to
> user and he will "see" the real path on _his_ machine :)

Right and with the code from Enhanced SetupBuilder Web update Client he can
use that same variable to merge the data value into the RTF he displays to
the client!

:-)

Charles


--
-------------------------------------------------------------------------------------------------------
Charles Edmonds
www.ezchangelog.com - "Free ChangeLog software to manage your projects!"
www.setupcast.com - "A revolutionary new publishing system for software
developers - enhanced for SetupBuilder users!"
www.pagesnip.com - "Print and Save the Web, just the way you want it!"
www.clarionproseries.com - "Serious imaging tools for Clarion Developers"
www.ezround.com - "Round Corner HTML tables with matching Banners, Buttons
and Forms!"
www.lansrad.com - "Intelligent Solutions for Universal Problems"
www.fotokiss.com - "World's Best Auction Photo Editor"
-------------------------------------------------------------------------------------------------------

[NewsArchive]

Hi Arnór,

> Since documentation does not require write access it was suggested (I
> think by Bruce Johnson at some point) to put docs into
> Program_Files\Softvelocity\Clarion7\accessory. I have done that in my
> installs under accessory\documents\Icetips\<product> as I realized there
> wasn't any reason really to put them into COMMON_DOCUMENTS...

I gave it again some thoughts this night and now I remember why I suggested
to not install it under the Program Files root.

Some HTML Help files (*.chm) that contain references to another Help file,
create an index file (*.chw) in the folder that contains the Help. Without
the index file, some Help topics will not be available. So in this case,
developers have to build the .chw and deploy it along with their help
because under "Program Files" (read-only) users don't have permission to
create files in the folder where the Help file is located.

But I think most (if not even all?) Clarion 3rd-party HTML Help files do not
create a .chw.

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

SetupBuilder "point. click. ship"
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

Hi Friedrich,

> But I think most (if not even all?) Clarion 3rd-party HTML Help files do not
> create a .chw.

I don't recall ever hearing about it<g>

Best regards,

--
Arnór Baldvinsson - Icetips Creative, Inc.
Port Angeles, Washington
www.icetips.com - www.buildautomator.com

Icetips product subscriptions at http://www.icetips.com/subscribe.php

[NewsArchive]

I have enhanced the "Clarion Accessory Deployment" demo. I'll post it when
we have a final decision for the "Examples" and "Documentations" locations
(or if you are interested in the new .sb6 project).

Four SetupBuilder "compiler variables" have full control over the folder
logic now. In other words, you only have to modify the variable values to
follow different deployment strategies. You don't need to modify the
SetupScript source code at all.

1. See "missioncontrol1.gif" screenshot.

[3P_VENDOR_NAME] holds the name of the 3rd-party vendor.

For example: Lindersoft

[3P_PRODUCT_NAME] holds the name of the 3rd-party product.

For example: LSZip

[3P_C7_SAMPLES_BASE] holds the default "base" location for C7 example files.

For example:
%_CSIDL_COMMON_DOCUMENTS%\SoftVelocity\Clarion\7\a ccessory\samples

To support examples deployment to the "\SoftVelocity\Clarion7\accessory",
just change this variable to:

%_CSIDL_COMMON_DOCUMENTS%\SoftVelocity\Clarion7\ac cessory and you are done.

The compiler will do all the "dirty work" for you.

[3P_SUBFOLDER_LAYOUT] holds the subfolder layout format for "Examples" and
"Documentations".

Supported formats are:

1 = <CompanyName>\<ProductName>
2 = <CompanyName> <ProductName>
3 = <ProductName>


2. See "missioncontrol2.gif" screenshot.

Of course, you can access the variables through the "Compiler Variables"
Visualizer.

Friedrich

--
Friedrich Linder
Lindersoft
www.lindersoft.com
+1.954.252.3910

SetupBuilder "point. click. ship"
Create Windows Vista ready installations in minutes

-- Official Comodo Code Signing and SSL Certificate Partner

[NewsArchive]

You are MAGIC for us all Friedrich

MERCI :)

--

Thank you - Merci

Cordialement - Best Regards
Jean-Pierre GUTSATZ

DMC - Data Management Center - A tool to let you Migrate Import Export
Transfer all your Data very easily
www.dmc-fr.com
Certified by Microsoft : "Works with Vista" & "Works with Windows Server
2008"

[NewsArchive]

Friedrich,

I hope you mean "documents" not "Documentations"? :)

Regards,
Kelly E Major

[NewsArchive]

Hi Kelly,

>
> I hope you mean "documents" not "Documentations"? :)
>

YES :)

Friedrich