How do I copy intellicode templates from one system to another?  I can't
find where these are stored.

Thanks, Joe

> How do I copy intellicode templates from one system to another?  I can't
> find where these are stored.

Joe,
not sure what you mean, however, these tricks will be useful, regardless
what you want to clone
from one system to another:

a) in the registry, the VXIDE settings are stored under
current user /-> Software -> Alaska Software -> Visual Xbase++
You could just export this to a *.reg fiel and reimport it
on the otehr machine, provided your path etc setting sare same.

b) Have a look in the c:\alaska\xppw32\bin
(or wherever you installed your VX-FileS) directory
and look for all what has changed (new date / time)
in that directory and the typinfo subdirectory.
In your case, especialy the file Templates.ini
might be of interest.

HTH and all the best,
Kai

Kai Froeb wrote:

> not sure what you mean, however, these tricks will be useful, regardless
> what you want to clone
> from one system to another:
>
> a) in the registry, the VXIDE settings are stored under
> current user /-> Software -> Alaska Software -> Visual Xbase++

IMO, the IDE should have a function to export/import all settings without
having the need to fiddle around with regedit.

There are a lot of developers that need to move their devlopment
environment to the notebook and back to their desktop pc.

Thomas

Xbase++ FAQ : www.software-braun.de/xbfaq/xbfaq.htm
Any general statement is like a cheque drawn on a bank.  Its value depends
on what is there to meet it.				      --Ezra Pound

Thomas,

 the way the ide currently stores information is not final.

 We feel that a lot of informations currently stored in the
 registry for simplicity reasons should be stored in a
 transparent on the harddisk.

 regards,
 Steffen F. Pirsig,
 www.alaska-research.com

"Thomas Braun" <spam@software-braun.de> wrote in message
news:6$A1wEyzDHA.1972@S15147418...
> Kai Froeb wrote:
>
> > not sure what you mean, however, these tricks will be useful, regardless
> > what you want to clone
> > from one system to another:
> >
> > a) in the registry, the VXIDE settings are stored under
> > current user /-> Software -> Alaska Software -> Visual Xbase++
>
> IMO, the IDE should have a function to export/import all settings without
> having the need to fiddle around with regedit.
>
> There are a lot of developers that need to move their devlopment
> environment to the notebook and back to their desktop pc.
>
> Thomas
> --
> Xbase++ FAQ : www.software-braun.de/xbfaq/xbfaq.htm
> Any general statement is like a cheque drawn on a bank.  Its value depends
> on what is there to meet it.       --Ezra Pound

>IMO, the IDE should have a function to export/import all settings without
>having the need to fiddle around with regedit.
>
>There are a lot of developers that need to move their devlopment
>environment to the notebook and back to their desktop pc.

Add my vote for that.  Nothing should be in the Registry.  I regularly
move stuff to the notebook for a visit to a client's site where work
is done, changes made.  Then it must be moved back to the desktop when
I get home.


Regards - cj


Clayton Jones   www.cjcom.net 
 Top-Down Library for Xbase++
 X-DBU Database Utility   
 X-MEMO Memo Field Replacement

Same to me, so you have my vote too.
Klemens

"Clayton Jones" <topdown@cjcom.net> schrieb im Newsbeitrag
news:t1llvvs0kv7917bnf8vge9gahj1krd70iu@4ax.com...
>
> >IMO, the IDE should have a function to export/import all settings without
> >having the need to fiddle around with regedit.
> >
> >There are a lot of developers that need to move their devlopment
> >environment to the notebook and back to their desktop pc.
>
> Add my vote for that.  Nothing should be in the Registry.  I regularly
> move stuff to the notebook for a visit to a client's site where work
> is done, changes made.  Then it must be moved back to the desktop when
> I get home.
>
>
> Regards - cj
>
>
> Clayton Jones   www.cjcom.net
>  Top-Down Library for Xbase++
>  X-DBU Database Utility
>  X-MEMO Memo Field Replacement

I agree. I prefer ini file to registry.
Regards.
CL

We also agree.
The solution won't be a ini file. We will make it
with xml. But you are right, we allready regretted started with
this registry B***S***.

Regards
   Andreas Herdt
   [Alaska Research & Development]

Christian Laborde wrote:

> I agree. I prefer ini file to registry.
> Regards.
> CL
>

Andreas,

> But you are right, we allready regretted started with
> this registry B***S***.

Spoken like a true programmer 

Regards,

Phil Ide

***************************************
* Xbase++ FAQ, Libraries and Sources: *
* goto: http://www.idep.org.uk/xbase  *
***************************************

I program, therefore I exist.

Andreas Herdt wrote:

> The solution won't be a ini file. We will make it
> with xml.

Call me conservative , but a simple solution like an .ini file would do
at least for me 

Thomas

Xbase++ FAQ : www.software-braun.de/xbfaq/xbfaq.htm
I don't always know what I'm talking about, but I'm always pretty much
convinced that I'm right.
		-- musician Mojo Nixon

Thomas, Oskar
My advise would be:
  Get used to it - it will be good for you! 
Garry

Thomas Braun wrote:
> Andreas Herdt wrote:
> 
> 
>>The solution won't be a ini file. We will make it
>>with xml.
> 
> 
> Call me conservative , but a simple solution like an .ini file would do
> at least for me 
> 
> Thomas

Hi,
>The solution won't be a ini file ...
... within a separate settings-directory
i agree too.

Oskar Eschenbach
 LANDO-Software
"Andreas Herdt" <andreas.herdt@alaska-research.com> schrieb im Newsbeitrag
news:sIBLLuR1DHA.3616@S15147418...
> We also agree.
> The solution won't be a ini file. We will make it
> with xml. But you are right, we allready regretted started with
> this registry B***S***.
>
> Regards
>    Andreas Herdt
>    [Alaska Research & Development]
>
> Christian Laborde wrote:
>
> > I agree. I prefer ini file to registry.
> > Regards.
> > CL
> >
>