Hi everyone...

K-meleon was not able to  find your tool bar settings..Your selected skin might be missing or corrupt.PLease check your skin settings in the GUI apeareance section of k-meleon preferences.

This message appeares after i compressed Klassic folder in k-meleon\skins\Klassic
and took out the uncompressed folder...

Nevertheless the browser starts and works allmost normal after you click on the OK button...

It looks to me that after you compress the skin folder the browser can not find the path toward the skins folder anymore...

Is there any way where i can go and manually set the path so that k-meleon will recognize the new commpresed skin???

Thank you all

Quote
Badajoz Relu
It looks to me that after you compress the skin folder the browser can not find the path toward the skins folder anymore...

Is there any way where i can go and manually set the path so that k-meleon will recognize the new commpresed skin???

No, K-Meleon cannot read skin files out of a ZIP archive, it must be folder.

What Microsoft calls a "ZIP-compressed folder" is actually a file. I guess you confused that for file system compression which is available on NTFS drives...

Quote
kko

Quote
Badajoz Relu
It looks to me that after you compress the skin folder the browser can not find the path toward the skins folder anymore...

Is there any way where i can go and manually set the path so that k-meleon will recognize the new commpresed skin???

No, K-Meleon cannot read skin files out of a ZIP archive, it must be folder.

What Microsoft calls a "ZIP-compressed folder" is actually a file. I guess you confused that for file system compression which is available on NTFS drives...

h
I have`nt got confused..

What i am actually trying to do is to reduce the K-meleon`s size ....

that`s how i started compresing files an stuff..So far my K-meleon is around 8,70 Mb now but i am still working on it...I might be able to slimm it down to 5 MB...
An other quick question would be...

in folder k-meleon\chrome we got the file embed.jar which is about 1.60 Mb
if you transform it in embed.7z you will end up with a 260Kb file ,,,But then again...K-meleon will not work...

Any ideias...Is there any way around it,,??

cheers..

Yes, but you must first unzip the jar file, and compress it again choosing zip type instead of 7z type. You will must change the extension to jar.

In fact jar files are zip files, but with no compress, that's why you will win much place by zipping it. But the thing you win with size, the thing you loose is speed.

A+

---

Mozilla/5.0 (x11; U; Linux x86_64; fr-FR; rv:38.0) Gecko/20100101 Ubuntu/12.04 K-Meleon/76.0

---

Web: http://jujuland.pagesperso-orange.fr/
Mail : alain [dot] aupeix [at] wanadoo [dot] fr

---

Ubuntu 12.04 - Gramps 3.4.9 - Harbour 3.2.0 - Hwgui 2.20-3 - K-Meleon 76.0 rc

---

Quote
Badajoz Relu

What i am actually trying to do is to reduce the K-meleon`s size ....

that`s how i started compresing files an stuff..So far my K-meleon is around 8,70 Mb now but i am still working on it...I might be able to slimm it down to 5 MB...

1.) a.) Dll&Exe. You can use upx (that was used by alain to make last portable K-Meleon, not all dll files can stand it). That will create smaller dll and exe for You.

b.) Chrome. Unpack all jars one after the other (use: unzip here -> unpacks to locale, skin, content) and repack to jar like alain described using high compression. It will reduce e.g. embed.jar to ca 500 kb. Work in extra folder to reduce work.

c.) Skin. You can use a smaller throbber (i attached a smaller one). You can perhaps go without menuitems.cfg and the pictures of menu.bmp that are referenced in it. You can certainly use a much smaller or no back.bmp.

I am not sure (kko may remember, new 1.5 or next version may support another smaller picture format for BMP in skin).

2.) K-Meleon can read zip (but only uses this to read chrome).
7z is another format. K-Meleon cannot read it.



Edited 2 time(s). Last edit at 01/06/2009 09:57PM by guenter.

Min1.1 by rmn has about 56 kb and is AFAIK the smallest skin. Even as installer it has half the size of Klassic.



Edited 1 time(s). Last edit at 01/06/2009 10:32PM by guenter.

Quote
JujuLand
Yes, but you must first unzip the jar file, and compress it again choosing zip type instead of 7z type. You will must change the extension to jar.

In fact jar files are zip files, but with no compress, that's why you will win much place by zipping it. But the thing you win with size, the thing you loose is speed.

A+

Thanks a lot man...I will give it a shot ,and i will be back to keep ya posted

Quote
JujuLand
Yes, but you must first unzip the jar file, and compress it again choosing zip type instead of 7z type. You will must change the extension to jar.

In fact jar files are zip files, but with no compress, that's why you will win much place by zipping it. But the thing you win with size, the thing you loose is speed.

A+

A+...

You`re a legend mate...

I will give it a shot and i will be back with more questions...

PS: Sorry to be a pain in the ...err neck

Umm,,,

Guys, is not workin....

It happens the same as before..
It does not matter what extension i use to compress chrome,After compression The browser starts but when i type a web adress in the adress bar K-meleon will not load it,..

Thank you..

You unpack one level more shallow / not so deep. Then it works normally.

Example: put embed.jar to a new folder.
Use unzip here function.

You get subfolders: console2, embed, flasbloch, kmprefs, mtypes.

Now select all and repack to embed.jar using zip.

BTW. If it unpacks to embed. Repacking changes its structure to embed.jar/embed/console,embed... and that is one level deeper than it was.

The subfolder embed contains the needed parts of a browser chrome.
The subfolder embed comes from the name of the unpacked jar

---

en-Us.jar the same.
You get subfolders: console2, embed, kmprefs, mtypes.
go back into en-US.jar.

---

Others may unpack to content, classic (a skin), locale or a combination of them. Repack to the original name + jar.

If You unpacked to deep go into the folder and zip from there.

Guys,,,

I tried it...No use ..IS NOT working..

I am using K-Meleon 1.5.2 on a windows server 2000..

It is obvious that the moment you change the extension of the files,K-meleon is not able to recognize the path toward the folder...

I had the same problem when I slimmed down Opera@Usb down to 3.87Mb..BUT there you could just go in the profile.ini and manually set the path toward the folder and opera would just accept it...

SO MY BIG QUESTION IS :Is it possibile to do the same thing in K-meleon??
Normally it should be...

There must be a place where all the paths to the folders and stuff are setted...
After all K-meleon does not take it`s settings out of the blue..


Does anyone knows where i could find those settings???


Cheers!!

Maybe paths are in embed.manifest

Quote
Gorilla no baka
Guys,,,

I tried it...No use ..IS NOT working..

I am using K-Meleon 1.5.2 on a windows server 2000..

I attached the first part of a deflated en-US chrome to Your post and the rest is attached here.

The file format is 7z. Unpack both archives until You have manifest and jar files and copy all manifests and jars to Your chrome folder.

p.s. I much recommend this 7zip for future work with chrome.

K-Meleon will stay bigger than Opera.



Edited 3 time(s). Last edit at 01/08/2009 02:23PM by guenter.

The advantage of a portable K-Meleon 1.5.x over Opera or any other browser is that its USB version do not write on HDD provided You use the right settings and the xpcom_core.dll that I attached to this post (desgas2 prepared that for portables, thx & credit 4 him!).


p.s. On new USB the size is not the problem - take 5 $ and get a bigger stick.
Size was a problem when affordable USB sticks were 16 MB or so.
On USB You may still want to use deflated chrome jars - because unpacking in RAM might be faster than the read operation.



Edited 1 time(s). Last edit at 01/08/2009 02:43PM by guenter.

Thank you guys...

I will give it a shot as soon as my night shift will be over..

I do have and work with 7.zip an UPX..
They're quite good for compression especiallyUPX..
That's how i managed to get Opera@USB down to 3.87 MB..
Say...Would not be easyer just to download the source code and compile it
to a smaller K-meleon..??
I probably would be able to modify the network protocol as well
in order to remove the pipeline request limit (Is still hardcoded to maximum 8 requests right??)

Thank you...

network.http.pipelining.maxrequests = 4 (by default)

K-Meleon in Spanish

Not small enough yet? :O

1.) You may want to try a ME Version if the main concern is size.
Have a look at the latest CCF ME by Hao or the K-Meleon-NX by Fred.

Much of K-Meleon is modular. Versions with less functions are possible.
That can e.g. reduce the number of kplugins. ME can have almost no chrome ...

2.) The bulk of K-Meleon install is the GRE - You will have to recompile Mozilla Sources and K-Meleon with param for low size.

3.) network.http.pipelining.maxrequests is a Pref that can be set.

Quote
Gorilla no baka
remove the pipeline request limit (Is still hardcoded to maximum 8 requests right??)

It is recommended to set it to 8.

4.) More info about speed tweaks.



Edited 1 time(s). Last edit at 01/09/2009 11:09AM by guenter.

Quote
guenter
Not small enough yet? :O

1.) You may want to try a ME Version if the main concern is size.
Have a look at the latest CCF ME by Hao or the K-Meleon-NX by Fred.

Much of K-Meleon is modular. Versions with less functions are possible.
That can e.g. reduce the number of kplugins. ME can have almost no chrome ...

2.) The bulk of K-Meleon install is the GRE - You will have to recompile Mozilla

Sources and K-Meleon with param for low size.

3.) network.http.pipelining.maxrequests is a Pref that can be set.

Quote
Gorilla no baka
remove the pipeline request limit (Is still hardcoded to maximum 8 requests right??)

It is recommended to set it to 8.

4.) More info about speed tweaks.

Thank you for the tweak list ..I am familiar with them from my Firefox experience

About the "It is recommended to set it to 8. "

I know that...Everyone knows that But since I am a very curious person.....

Here is a part of the code source from the network protocol Take a look at the 12 #define NS_HTTP_MAX_PIPELINED_REQUESTS 8 Line...

That is why it would not matter if you sett the limit to more than 8 pipelining connections requests...


________________________________________________________________________________
83 // http default buffer geometry
84 #define NS_HTTP_SEGMENT_SIZE 4096
85 #define NS_HTTP_SEGMENT_COUNT 16 // 64k maximum
86 #define NS_HTTP_MAX_ODA_SIZE (NS_HTTP_SEGMENT_SIZE * 4) // 16k
87
88 // http version codes
89 #define NS_HTTP_VERSION_UNKNOWN 0
90 #define NS_HTTP_VERSION_0_9 9
91 #define NS_HTTP_VERSION_1_0 10
92 #define NS_HTTP_VERSION_1_1 11
93
94 typedef PRUint8 nsHttpVersion;
95
96 //-----------------------------------------------------------------------------
97 // http connection capabilities
98 //-----------------------------------------------------------------------------
99
100 #define NS_HTTP_ALLOW_KEEPALIVE (1<<0)
101 #define NS_HTTP_ALLOW_PIPELINING (1<<1)
102
103 // a transaction with this caps flag will continue to own the connection,
104 // preventing it from being reclaimed, even after the transaction completes.
105 #define NS_HTTP_STICKY_CONNECTION (1<<2)
106
107 //-----------------------------------------------------------------------------
108 // some default values
109 //-----------------------------------------------------------------------------
110
111 // hard upper limit on the number of requests that can be pipelined
112 #define NS_HTTP_MAX_PIPELINED_REQUESTS 8
113
114 #define NS_HTTP_DEFAULT_PORT 80
115 #define NS_HTTPS_DEFAULT_PORT 443
116
117 #define NS_HTTP_HEADER_SEPS ", \t"
118

12 #define NS_HTTP_MAX_PIPELINED_REQUESTS 9999999999 (This is a joke of course )


Now can anyone tell me where are the next settings stored ????
Definatelly they are not stored in a .dll

I took a look at the source code and it does not contain any

#include "dll.h"
#include <windows.h>

So where are they stored..??

C'mon...I am only a beginer in C++ so if I can see that..Any of the programers here can do..



Thanks for your help guys...

Quote
Gorilla no baka

Thank you for the tweak list ..I am familiar with them from my Firefox experience


Here is a part of the code source from the network protocol Take a look at the 12 #define NS_HTTP_MAX_PIPELINED_REQUESTS 8 Line...


Now can anyone tell me where are the next settings stored ????
Definatelly they are not stored in a .dll
So where are they stored..??

C'mon...I am only a beginer in C++ so if I can see that..Any of the programers here can do..

1.) Sorry i did not know that You knew it was applicable for K-Meleon and every Gecko.

2.) I did not know it was hard coded. Thx for info.


Found this about #define NS_HTTP_MAX_PIPELINED_REQUESTS more than 8 at works only if the server can handle it. Several can not which leads to a broken page.

But do not know whether that is true.
AFAIK 8 is part of HTTP/1.1, the newest protocol.
He probably means Servers using the older protocols fail.

3.) My best guess. necko.dll.

Look & resource hack with hex editor or compile?
But IMHO it is not worth the investment of time - if it is in the protocol.

Else component responsible for prefs.

4.) I am a lamer - I cannot program at all.



Edited 1 time(s). Last edit at 01/09/2009 01:25PM by guenter.

Quote
guenter

Quote
Gorilla no baka

Thank you for the tweak list ..I am familiar with them from my Firefox experience


Here is a part of the code source from the network protocol Take a look at the 12 #define NS_HTTP_MAX_PIPELINED_REQUESTS 8 Line...


Now can anyone tell me where are the next settings stored ????
Definatelly they are not stored in a .dll
So where are they stored..??

C'mon...I am only a beginer in C++ so if I can see that..Any of the programers here can do..

1.) Sorry i did not know that You knew it was applicable for K-Meleon and every Gecko.

2.) I did not know it was hard coded. Thx for info.


Found this about #define NS_HTTP_MAX_PIPELINED_REQUESTS more than 8 at works only if the server can handle it. Several can not which leads to a broken page.

But do not know whether that is true.
AFAIK 8 is part of HTTP/1.1, the newest protocol.
He probably means Servers using the older protocols fail.

3.) My best guess. necko.dll.

Look & resource hack with hex editor or compile?
But IMHO it is not worth the investment of time - if it is in the protocol.

Else component responsible for prefs.

4.) I am a lamer - I cannot program at all.

I do not think that are many serve around using the old protocol

Anyway i am not a programer either i am just learning..
But i am sure there are guys here who CAN program and stuff,,

I just do not know them...

Do you think some of them might want to answer,,>??