Author Topic: Elog -weblog (Read 8109 times)

xjqian · « **on:** February 12, 2005, 10:35:19 pm »

Thanks for fpp's heads up. I copied his original message below from the Software megapost

Quote

A touch of the exotic, from Switzerland : ELOG

Not as well know as their cheese, chocolate, gold bars, Victorinox knives and luxury watches, but nice and useful too, and free :-)

Read up on ELOG here : http://midas.psi.ch/elog/

It's a versatile, 'batteries-included' weblog app (no separate web server or database needed) that can be turned into almost anything (blog, forum, note-taking, database etc.). Very simple to configure. Can replicate or synchronize between ELOG servers, & much more.

To try it out: grab the tar.gz archive on the site above (no IPK yet, sorry) and follow the Linux install instructions except for the "make" part.

Then get the ready-made binaries for the Z here :
http://fredp.lautre.net/Z/

Copy them to the 'bin' directory under your ELOG installation and off you go...

fpp, Thanks a lot for the updates on the arm ipk. However, I had some problems with the latest 2.5.6 arm ipk you built
* it's hungry on memory. When I opened http://localhost.localdomain:8080/<mylogbook>, soon the memory usage go crazy. system reminds me "the available work space is low, please close applications ..." . I created a 16M swap in my sd to see how bad it is. It used up all of the 16M! On 2.5.3, I only encounter this when several applications (opera+justreader+qkonsole+sysinfo) were running simultaneously.
* On 2.5.3 I used to be able to display chinese character display using charset=Big5 or GBK in the [global] setting. But on 2.5.6 I can't display chinese characters at all. No problem with the 2.5.6-2 windows version on my xp

edit1: maybe it's just the way elog 2.5.6 is. I need to report he problems to the author?
edit2: i'm trying to compile the elog on my z, by using zgcc or dev_img.
edit3: i would probably try the debain package soon

xjqian · « **Reply #1 on:** February 13, 2005, 02:12:06 am »

sorry about the fuss. there's no problem with the 2.5.6 arm ipk at all. It does use more memory than 2.5.3, but not that bad. I forgot to clear the "fast load" since i just restored the stock rom. and the chinese display issue is solved. thanks.

fpp · « **Reply #2 on:** February 13, 2005, 06:09:20 am »

Thanks for the feedback xjqian ! I did notice the new elogd binary was quite a bit larger than the previous one (maybe due to the regexp code being linked in now). Glad it works though. I guess I'll put back the link to the older version on my page so people can choose between newer and less greedy

EDIT: done.

fpp · « **Reply #3 on:** February 14, 2005, 10:48:05 am »

There, I just knew it : 2.5.7 came out today :-)

Fixes a remote shell exploit in previous versions, no less...

I'll compile the new binaries and put them up later today.

fpp · « **Reply #4 on:** February 14, 2005, 03:47:08 pm »

Elog 2.5.7 arm binaries are now available at :

http://fredp.lautre.net/Z/

xjqian · « **Reply #5 on:** February 15, 2005, 12:36:32 am »

2.5.7 worked great. memory footprint almost the same as 2.5.6. Took about 45Mb to use with opera on my 6k, but not bad. Thanks

homeridian · « **Reply #6 on:** February 15, 2005, 04:29:24 am »

Hi,

I started using elog and really like it, but the memory footprint is a little bit alarming: Could this be a bug or does such a program really need these amounts of memory?

As a solution: Is it possible to use the former version 2.5.3 on the Zaurus and 2.5.7 on the desktop with the same logbooks that I synchronize with unison?

Thanks for introducing (and compiling) that program!

Carsten

ensign · « **Reply #7 on:** February 16, 2005, 02:23:33 pm »

Hi,
Can anybody show me how to get the 'Theme' effect as shown on the elog website? Where can i download themes. I don't think I have even got the default one.

EDIT - found them thanks.

THanks,
Mawuli

fpp · « **Reply #8 on:** February 16, 2005, 03:57:32 pm »

Quote

Hi,
I started using elog and really like it, but the memory footprint is a little bit alarming: Could this be a bug or does such a program really need these amounts of memory?

Dunno - I'll have a word with the author about this, seems like a recent development.

Quote

As a solution: Is it possible to use the former version 2.5.3 on the Zaurus and 2.5.7 on the desktop with the same logbooks that I synchronize with unison?

I think it should work: there hasn't been a change in data file formats in a long while, so if your logbook definition(s) are not concerned by the few bugfixes between 5.3 and 5.7, or use some very recent feature, you should be OK.

Glad you people find Elog interesting and useful. It looks deceptively simplistic on the outside, but is incredibly versatile when you start digging some...

News:

Author Topic: Elog -weblog (Read 8109 times)