TOPIC:

Hi,

Thanks for this great tool, I wonder if it would be possible to create a Portable version?
regards,
Johan

Thanks Sir,
No portable plan for now (sorry)
CodeTyphon is a large Programming studio
only the source after installation has size 1.6 Gbytes
after build BigIDE has about 2.5-3.5 Gbytes
with 86 Pages and 1009 Visual Components
so, we can't pack our "monster"

Cop, if you want portable edition for windows, then look for "cameyo" - it's a tool similar to thinstall, but free.
With it you could create portable version of CT.
All you need are:
- launch cameyo and let it scan your system;
- install CT;
- remove unnecessary things (demos, etc); *optional
- let cameyo pack your installation.

Having this done you will pocess portable package of CT for windows, working in XP,vista,seven (I'm not sure 'bout 8).
Cameyo archives all files into ONE executable (which launches VERY fast), so there's no need in additional setup, editing configs or so.

Will check this out, but never heard of this before looks promising.

In my opinion, "portable" means all the config files are in the program folder and the whole program can be copied to another computer without the loss of the config files. It is nothing to do with the size and you do not need to "pack".

I have installed the CT and it works well for me, thanks for providing this wonderful software. But the Lazarus uses the system folder %APPDATA% to store it's config file which means that when I copy the whole CT to another computer, I would loss all the config files. So is there any possible to move the config files from the system folder to CT installed folder and let the Lazarus load the config files from installed folder and then the CT would become portable ?

if prefer like if codetyphon can installed in another drive like USB Hard drive,
and all setting could be backup or restore if we want to use in different computer

A quasi portable solution did the XAMPP people find:
The installation directory has to be \XAMPP\
but the drive letter does not matter.

The same approach (without breaking the current way of working) would be possible to be applied for CodeTyphon, by just omitting the drive letter, and start all fixed path in the different scripts just with
\codetyphon and not with c:\codetyphon

And the settings Dir is already settable in the command line:
startlazarus.exe --primary-config-path=F:\laz\config01

In windows exist simlinks like in linux

CREATE PORTABLE USB
1) Install CT in c:\codetyphon
2) Move c:\codetyphon to USB
3) Move %appdata%\lazarus32 to USB

USE PORTABLE CT
3) Create junction USB:\codetyphon -> c:\codetyphon
4) Create junction USB:\lazarus32 -> %appdata%\lazarus32

It is all ?

do you test it ?
may be with full tutorial

FAT32 does NOT have symlinks feature, so you'll need to have your pen drive formatted as NTFS, which definitely will result in sllower access time and will slow down both read and write...
Anyway you could try it out

4aiman wrote: FAT32 does NOT have symlinks feature, so you'll need to have your pen drive formatted as NTFS, which definitely will result in sllower access time and will slow down both read and write...
Anyway you could try it out

It is only half true

If you have USB (f:\) formated FAT32 and system (c:\) formated NTFS is posible create junction
I tested and it works OK

As for now, let us forget about differences between symlinks and junction points

And then... why "half true"?
You wouldn't argue if I say that this is working only because NTFS make your PC think that FAT32 drive is the part of NTFS volume, would you?

And furthermore, mklink is win vista+ feature, so XP users have only junction points.

In XP to create junction is linkd.exe
It is part of Windows Server 2003 Resource Kit Tools

I always use Junction , Codetyphon files are on E: disk but Codetyphon think it is c:\Codetyphon , and it works OK

I know how one could do that and where to get Win Server 2003 RKT.
And I've never argued with you in the point where "it works OK" - just want to warn those who still have FAT32 on their HDDs, to show that symlinks aren't exactly junction points and to say that XP users have to use junction points (which you repeated as well)

But thanks anyway.
And I'm sure you'll be thanked million times for the above link too