U3
-
Jan Rysavy
- ALTAP Staff
- Posts: 5231
- Joined: 08 Dec 2005, 06:34
- Location: Novy Bor, Czech Republic
- Contact:
2 Jan Rysavy:
> It is impossible to implement such layer (including unicode support) and
> adapt existing 200KB of C++ save/load code for this layer in a few
> weeks. We will do it but not now, I'm sorry. Support for Registry must
> stay for our corporate customers.
----------
Ok, but I still do not get what takes so long in here...?!
example solution:
a) write a small simple INI-file parser object (I can share mine if needed) - it loads the Salamander.ini file in to a memory buffer and then it translates its content into the internal Salamander settings object (or if you want to be supercool
use some XML stuff instead)
b) the Registry way will differ only in the fact, that you save/load this ini-file from the Registry 1st, then start the same memory buffer parsing code...
Now the only drawback I can think of will be the resulting increase in size (saving readable ini-data vs. binary ones into the Registry ...), but one can compress the ini-data first and then save binary into the Registry. I also know that RegKeys have some limits in size (KeyNames 255 chars, ValueNames 16383 chars, ValueSizes 1MB), in such case there is a split zip-archive etc...
More to the whole discussion above - I think you all missed one important point - sw security restrictions. If one works in a firm with a strict security restrictions implied, a common user hardly will have the admin rights, so a new sw-installation (like the AS) will be probably denied at all (either by a "soft" company policy like the signing appropriate part of an employment contract only or by a "hard" real computer restriction policy applied). From that point of view the requested Salamander portability is a must.
> It is impossible to implement such layer (including unicode support) and
> adapt existing 200KB of C++ save/load code for this layer in a few
> weeks. We will do it but not now, I'm sorry. Support for Registry must
> stay for our corporate customers.
----------
Ok, but I still do not get what takes so long in here...?!
example solution:
a) write a small simple INI-file parser object (I can share mine if needed) - it loads the Salamander.ini file in to a memory buffer and then it translates its content into the internal Salamander settings object (or if you want to be supercool
use some XML stuff instead)b) the Registry way will differ only in the fact, that you save/load this ini-file from the Registry 1st, then start the same memory buffer parsing code...
Now the only drawback I can think of will be the resulting increase in size (saving readable ini-data vs. binary ones into the Registry ...), but one can compress the ini-data first and then save binary into the Registry. I also know that RegKeys have some limits in size (KeyNames 255 chars, ValueNames 16383 chars, ValueSizes 1MB), in such case there is a split zip-archive etc...
More to the whole discussion above - I think you all missed one important point - sw security restrictions. If one works in a firm with a strict security restrictions implied, a common user hardly will have the admin rights, so a new sw-installation (like the AS) will be probably denied at all (either by a "soft" company policy like the signing appropriate part of an employment contract only or by a "hard" real computer restriction policy applied). From that point of view the requested Salamander portability is a must.
-
Jan Rysavy
- ALTAP Staff
- Posts: 5231
- Joined: 08 Dec 2005, 06:34
- Location: Novy Bor, Czech Republic
- Contact:
We already have code that works with Registry. So what we need is layer that will emulate Registry API and will work with our (nearly untouched) existing code. It should probably use .REG (both Ansi and Unicode versions) as data storage so we can import old (exported) configurations and stay away from the Registry.
Ad security restrictions: good point!
Ad security restrictions: good point!
> We already have code that works with Registry. So what we need is
> layer that will emulate Registry API and will work with our (nearly
> untouched) existing code. It should probably use .REG (both Ansi
> and Unicode versions) as data storage so we can import old
> (exported) configurations and stay away from the Registry
--------------
So vice versa of my example sln., I see, I also tend to do not change/overwrite already working code. So good luck with the layer coding, I am looking forward to it.
BTW I think that Microsoft itself is responsible for a bunch of these Registry problems. As usual they started very well, the introduction of a central settings storage object (the Windows Registry) I see as an advantage e.g. in comparison of the UNIX-like systems, but then came usual MS overhype and they de facto put up Win-developers to use Registry storage for everything (and not only preferably for the more important system wide settings). The result - overbloated fragmented Registry slowing down the whole system...
> layer that will emulate Registry API and will work with our (nearly
> untouched) existing code. It should probably use .REG (both Ansi
> and Unicode versions) as data storage so we can import old
> (exported) configurations and stay away from the Registry
--------------
So vice versa of my example sln., I see, I also tend to do not change/overwrite already working code. So good luck with the layer coding, I am looking forward to it.
BTW I think that Microsoft itself is responsible for a bunch of these Registry problems. As usual they started very well, the introduction of a central settings storage object (the Windows Registry) I see as an advantage e.g. in comparison of the UNIX-like systems, but then came usual MS overhype and they de facto put up Win-developers to use Registry storage for everything (and not only preferably for the more important system wide settings). The result - overbloated fragmented Registry slowing down the whole system...
-
Guest
As in case of Altap Salamander? Coz there is also a demand...Jan Rysavy wrote:Because there is demand?
I don't care how is AS programmed. It is your business (however I do know how it could or should be done). I just wanted you to know that registry-free mode for running from flash disks would be nice. A propos, you could of course use it in marketing wars.
-
Jan Rysavy
- ALTAP Staff
- Posts: 5231
- Joined: 08 Dec 2005, 06:34
- Location: Novy Bor, Czech Republic
- Contact:
-
Guest
Sure, the same applies to your product - it is also much smaller then the whole OS, Office and all that stuff. Hey, it is only a file manager. Not bad, but nothing more. And nothing less of course, I have bought a license so it must have proven itselfJan Rysavy wrote:Are you comparing us with Microsoft? We are really on different budget and resources.Anonymous wrote:As in case of Altap Salamander? Coz there is also a demand...
No need to argue further... really.
-
Guest
-
Guest
Re: How about "Import/Export registry sections as XML"
-
showens
Portable config - me too!
This would be very useful to me.Jan Rysavy wrote:So U3 installer is not requested, just support for storing configuration into the file instead of Registry.Anonymous wrote:3. I don't really need U3, I need a simple portable mode. In fact, I use PortableApps.com on my flash disk, which is OK for me.
Steve Owens
Satisfied AS Customer
-
rasty
AS Portable
Partable is the great opportunity for all the AS users. AS U3 is for U3 addicts: useless to me
I've my own 120Mb-HB-USB small like a 20-cigarets-box where I've all the suit of the portable sw I DO LIKE !!!
Therefore it doesn't matter where I'm .... plug the HD into a USB and all my sw is available there.
And of course AS Portable is the main one I need to manage any PC, LAP or server.
Let me know when AS will be ready, I want it !!
If you need I be also a beta tester
Regards
Paolo
Satisfied AS Customer from rel.1.
I've my own 120Mb-HB-USB small like a 20-cigarets-box where I've all the suit of the portable sw I DO LIKE !!!
Therefore it doesn't matter where I'm .... plug the HD into a USB and all my sw is available there.
And of course AS Portable is the main one I need to manage any PC, LAP or server.
Let me know when AS will be ready, I want it !!
If you need I be also a beta tester
Regards
Paolo
Satisfied AS Customer from rel.1.
There is a very easy way to make AS portable, use Thinstall Studio from VMWare. I tried it with a beta version of Thinstall, and it worked perfectly.
Or, you can try to do this with NSIS (NullSoft Scriptable Install System). At the portableapps.com site you find a nice procedure how to make apps portable. I am not sure if it works with AS.
Or, you can try to do this with NSIS (NullSoft Scriptable Install System). At the portableapps.com site you find a nice procedure how to make apps portable. I am not sure if it works with AS.