myDSL Extensions (deprecated) :: Request for .ucis
I did create a user.tar.gz, very much like the one in Robert's openoffice.uci. But I realise now that I might have done it somewhat wrong. I will check it out. I did create a user.tar.gz where I incorporated the .openoffice1.9.82/ folder initially created by the app. I realised know that my changing the name of the program (and thereby also the /opt/openoffice-folder) from openoffice1.9.82 to openoffice2 might cause the hidden folder in /home/dsl to be renamed. So, while my user.tar.gz contained a /home/dsl/.openoffice1.9.82 folder, the app will probably try and create a /home/dsl/.openoffice2 folder? This could be the reason why it takes somewhat more time to boot the first time... I will check this out!
Davide: I do use openoffice.uci on an older laptop, 56MB RAM. It is a Compac Presario 1210 or something like that. It works but it is slow. On my office-computer though, Dell Optiplex 270 with 512 MB RAM, it rocks!!!
I don't know about abiword and gimp ucis. I haven't seen any yet, but I hope there will be made some! The ordinary abiword.dsl and gimp.dsl doesn't work for me on the old laptop (I have a frugal install and the larger dsls eat up too much RAM).
And thanks for the congrats I am not sure if I am really a fast learner, but I love it that you can learn so many new things while using DSL!!!
-rJust for the record: the somewhat long initial start-time for my openoffice2.uci had nothing to do with my giving the directory in user.tar.gz a different name from the app. I tried changing it to /home/dsl/.openoffice2 in user.tar.gz, just to see that two directories were made in /home/dsl when the app was first booted, one /home/dsl/.openoffice2 and one /home/dsl/.openoffice.org1.9.82 (which was the initial name of the app). So my previous attempt (closely following the instructions from the docs!) was right. The somewhat longer time it takes for the app to start the first time must have a different reason. I guess it is like the mysterious Mr. 'Guest' said earlier in this thread:
Quote
Disk buffering is used by the operating system to kind-of predict what files you access from the hard disk or compressed image devices (like the uci) are used often. A copy of these will reside in the memory as long as the memory is free.
