dpup-482beta testing
Reading genuine MSWord docs is usually not a problem for any of these WP programs.. It's the writing where they spring up. Make some changes to the Word doc in abiword -- move some margins, type some new text into it, add a table. Then save it, and open it in MSWord, and compare the results. Sometimes even doing nothing, but re-saving a document changes it.
-
gposil
- Posts: 1300
- Joined: Mon 06 Apr 2009, 10:00
- Location: Stanthorpe (The Granite Belt), QLD, Australia
- Contact:
vtpup,
In your Abiword tests, were you using the same fonts in both, and do you have the MS fonts installed, in my testing, having the MS fonts installed makes a world of difference.
On the epdf viewer problem, that is my fault, wherever I opened it in testing is where it was saved...ooops...i'll have to go through that and make sure the initial opening points are desktop central...
Mick
Oh, and Mick the configure I used for Abiword is below:
Guy
PS. Are there any more outstanding fixes we need to do.
In your Abiword tests, were you using the same fonts in both, and do you have the MS fonts installed, in my testing, having the MS fonts installed makes a world of difference.
On the epdf viewer problem, that is my fault, wherever I opened it in testing is where it was saved...ooops...i'll have to go through that and make sure the initial opening points are desktop central...
Mick
Fixed in beta5 Mick, thanks...and yes the wbar config gui would be a great addition...Run action for a *.jpg file is set to "defaultpaint". Can we change that to "defaultimageviewer" by default? And while on the topic, "defaultimageviewer" is set to "gview", can we change that to "fotox"? (I have Smile )
Another thing, /etc/puppyversion is still the old "476". Barry says it is deprecated, but I still find it useful. To create (ie update) it run..
Oh, and Mick the configure I used for Abiword is below:
Cheers./configure --prefix=/usr --enable-plugins="sdw mswrite kword bmp wmf pdf openwriter"
Guy
PS. Are there any more outstanding fixes we need to do.
[img]http://gposil.netne.net/images/tlp80.gif[/img] [url=http://www.dpup.org][b]Dpup Home[/b][/url]
I used Times New Roman from msttcorefonts in abiword for the test below. It helped with the underline breaking, but nothing else. Notice the difference in column widths in the table, and also the row 4 height. Also notice that the Abiword shows bold text on the second entry, while MSWord doesn't.gposil wrote:vtpup,
In your Abiword tests, were you using the same fonts in both, and do you have the MS fonts installed, in my testing, having the MS fonts installed makes a world of difference.
I also just tried the same document in Open Office with Times New Roman and it exactly agrees with the MSWord interpretation, not Abiword's.
It actually looks like Abiword is misrendering its own document, since column widths were created uniform in width when the doc was written in Abiword, but when opened later showed variation in width.
Oh, well -- this isn't really your problem, as it is an app bug, not dpup's.
- Attachments
-
- TNRDocTest.jpg
- (61.2 KiB) Downloaded 1034 times
Ok thanks for the config options Guy.
The wbar gui is coming along, it should be quite configurable, although a little complex, (so many options
). I added a button to kill wbar if you desire (ty vtpup 
) and I have to handle it with a few different guis,,, way to messy otherwise, I will include a detailed help file, it should not end up bigger than 10k compressed (I hope). Does anyone use wbar on the side? I didn't think so, so top and bottom are it!!
I hope to have an alpha (complete) out over the weekend for testing, so I can't see it being ready until beta 6.
Cheers
The wbar gui is coming along, it should be quite configurable, although a little complex, (so many options
). I added a button to kill wbar if you desire (ty vtpup ) and I have to handle it with a few different guis,,, way to messy otherwise, I will include a detailed help file, it should not end up bigger than 10k compressed (I hope). Does anyone use wbar on the side? I didn't think so, so top and bottom are it!!I hope to have an alpha (complete) out over the weekend for testing, so I can't see it being ready until beta 6.
Cheers
Puppy Linux Blog - contact me for access
Hi Dejan
My script actually deletes and replaces the startup script, so, what I plan to do is delete it, and then it is easily replaced next time if you want it back. So far it is working, just some problems with the /root/.wbar config file which will be ironed out.
So far it is only 18k installed, with not much code left to go in, mostly now bugfixing. I will easy beat 10k compressed
.
Cheers
My script actually deletes and replaces the startup script, so, what I plan to do is delete it, and then it is easily replaced next time if you want it back. So far it is working, just some problems with the /root/.wbar config file which will be ironed out.
So far it is only 18k installed, with not much code left to go in, mostly now bugfixing. I will easy beat 10k compressed
.Cheers
Puppy Linux Blog - contact me for access
-
gposil
- Posts: 1300
- Joined: Mon 06 Apr 2009, 10:00
- Location: Stanthorpe (The Granite Belt), QLD, Australia
- Contact:
Thanks for the work on wbar-config Mick...
New for beta5 will be a remote desktop client, for logging onto other network machines using rdp protocol...screenshot below
New for beta5 will be a remote desktop client, for logging onto other network machines using rdp protocol...screenshot below
- Attachments
-
- rdp.jpg
- rdp
- (46.76 KiB) Downloaded 1027 times
-
- rdp2.jpg
- rdp
- (20.51 KiB) Downloaded 993 times
[img]http://gposil.netne.net/images/tlp80.gif[/img] [url=http://www.dpup.org][b]Dpup Home[/b][/url]
Rightio then,
Have a play with this
Wbar Configuration (or whatever )
It basically works, might seem fiddly with all those series of guis but believe me, if I tried to make it all in one gui it would be one big mess !!
Notes:: Of course this is experimental. Restart from first gui is broken, but I thought I would let it go now because I wouldn't be able to work on it again until Sunday. Help file is incomplete, if any one figures it out .. post! There is a pinstall to back up the original configuration. I've tried to be as verbose as possible, using labels and tooltips. (WOW 4kB
)
Have fun
Pet removed, See newer post
Have a play with this
Wbar Configuration (or whatever
)It basically works, might seem fiddly with all those series of guis but believe me, if I tried to make it all in one gui it would be one big mess
!!Notes:: Of course this is experimental. Restart from first gui is broken, but I thought I would let it go now because I wouldn't be able to work on it again until Sunday. Help file is incomplete, if any one figures it out .. post! There is a pinstall to back up the original configuration. I've tried to be as verbose as possible, using labels and tooltips. (WOW 4kB
)Have fun
Pet removed, See newer post
Last edited by 01micko on Fri 30 Oct 2009, 21:58, edited 1 time in total.
Puppy Linux Blog - contact me for access
Looks great gposil. Just a general question -- I've used TightVNC as a client for non-Microsoft remote stuff from Puppy and Ubuntu. It has a great advantage in working over limited bandwidth connections because it compresses on the fly using jpeg and other methods.
Would it be at all applicable here, or any advantage?
Here's the thread that has the tightvnc .pet I used, and also has X11VNCServer with a script for Puppy. They both worked very well for me.
http://www.murga-linux.com/puppy/viewto ... 29&t=27424
Would it be at all applicable here, or any advantage?
Here's the thread that has the tightvnc .pet I used, and also has X11VNCServer with a script for Puppy. They both worked very well for me.
http://www.murga-linux.com/puppy/viewto ... 29&t=27424
haha!
vtpup! Start the wbar config from the desktop menu and you see the wbar-setup window, click the geometry tab and make sure all the values are full, click apply and presto! A new startup script, with your own configuration...
vtpup! Start the wbar config from the desktop menu and you see the wbar-setup window, click the geometry tab and make sure all the values are full, click apply and presto! A new startup script, with your own configuration...
Puppy Linux Blog - contact me for access
Mick, oh! 
Hey it works Mick, but unfortunately it's too high or too low on my screen. At the bottom it is under the status bar and at the top it's........heh.....over the top.
I tried to put 10 in Margins, thinking that would make a difference . but they're still mostly off-screen.
Also I kept looking for "xdesktop" in the menu after the pet install. Couldn't find it. Then I realized you were referring to the "Desktop" menu category. I now see the graphic red X next to"Desktop", but my brain ignores that as a graphic. So maybe just say "Desktop" or hope for better brains out there.
Dejan:
Thanks already tried that, but Puppy won't allow you to mount an sfs with the same name. I suppose I could have renamed it and then tried, but Mick already solved it for me.
EDIT: I've played around quite a bit with wbar and restarted X a few times. The hidden wbar at the top of the screen no longer happens. Don't know why, maybe changing things and restarting got them in order. It's okay now.
But the problem is still there at the bottom of the screen. Most noticeable if icon size is set to 24. You do need to have the stationary taskbar at the bottom of the screen to see the problem. Not the autohide taskbar, option.
Also, when I first tried wbar with the fresh install, the bar was always present, even when the mouse wasn't over it. But now it disappears unless the mouse is over the bar. I have transparency set to zero for both bar and icons, if that has anything to do with it.....
Edit#2 Yes it was the transparency......okay got that sorted out. But it's backwards in the numbering system. More transparency should be a higher number. Also the default should be no transparency, and the user can increase it at will. Otherwise new folks won't be able to see the icons when booting the LiveCD.
Hey it works Mick, but unfortunately it's too high or too low on my screen. At the bottom it is under the status bar and at the top it's........heh.....over the top.
I tried to put 10 in Margins, thinking that would make a difference . but they're still mostly off-screen.
Also I kept looking for "xdesktop" in the menu after the pet install. Couldn't find it. Then I realized you were referring to the "Desktop" menu category. I now see the graphic red X next to"Desktop", but my brain ignores that as a graphic. So maybe just say "Desktop" or hope for better brains out there.
Dejan:
Thanks already tried that, but Puppy won't allow you to mount an sfs with the same name. I suppose I could have renamed it and then tried, but Mick already solved it for me.
EDIT: I've played around quite a bit with wbar and restarted X a few times. The hidden wbar at the top of the screen no longer happens. Don't know why, maybe changing things and restarting got them in order. It's okay now.
But the problem is still there at the bottom of the screen. Most noticeable if icon size is set to 24. You do need to have the stationary taskbar at the bottom of the screen to see the problem. Not the autohide taskbar, option.
Also, when I first tried wbar with the fresh install, the bar was always present, even when the mouse wasn't over it. But now it disappears unless the mouse is over the bar. I have transparency set to zero for both bar and icons, if that has anything to do with it.....
Edit#2 Yes it was the transparency......okay got that sorted out. But it's backwards in the numbering system. More transparency should be a higher number. Also the default should be no transparency, and the user can increase it at will. Otherwise new folks won't be able to see the icons when booting the LiveCD.
Last edited by vtpup on Fri 30 Oct 2009, 14:38, edited 2 times in total.
-
gposil
- Posts: 1300
- Joined: Mon 06 Apr 2009, 10:00
- Location: Stanthorpe (The Granite Belt), QLD, Australia
- Contact:
vtpup
with regard your question on dpup's Remote Desktop Client, compression and encryption are both settable options along with many more, i'll upload a pet so everyone can update their beta4...
Here it is...http://dpup.org/test/dpup482beta4-2.6.3 ... 3-dpup.pet
with regard your question on dpup's Remote Desktop Client, compression and encryption are both settable options along with many more, i'll upload a pet so everyone can update their beta4...
Here it is...http://dpup.org/test/dpup482beta4-2.6.3 ... 3-dpup.pet
Last edited by gposil on Fri 30 Oct 2009, 14:27, edited 1 time in total.
[img]http://gposil.netne.net/images/tlp80.gif[/img] [url=http://www.dpup.org][b]Dpup Home[/b][/url]
Subject: Unable to load OpenOffice 3.1 sfs (BK) after unloading OpenOffice 2.4 Debian through dpup
Hi,
This is in response to vtpup's help reply on p. 16, 4 days ago (already!).
I did change from xorg to xvesa, without success. Actually I just got a dark screen with xvesa. I had to reboot.
As to removing all the sfs's in the dpup's home dir from another Puppy, I did, and it didn't help. When I rebooted dpup, the cursor was still glued to the middle of the screen, and I couldn't do anything but go back to console mode.
No big deal, mind you, I wasn't too far ahead in building my personal pupsave / customizing my dpup. I simply started over with pfix=ram.
I am reporting this in the hope that some of you with more knowledge will know if this problem intersects with some other one in dpup, and perhaps point you with an additional hint in the direction of the solution.
Thanks again. In co-operation,
Hi,
This is in response to vtpup's help reply on p. 16, 4 days ago (already!).
I did change from xorg to xvesa, without success. Actually I just got a dark screen with xvesa. I had to reboot.
As to removing all the sfs's in the dpup's home dir from another Puppy, I did, and it didn't help. When I rebooted dpup, the cursor was still glued to the middle of the screen, and I couldn't do anything but go back to console mode.
No big deal, mind you, I wasn't too far ahead in building my personal pupsave / customizing my dpup. I simply started over with pfix=ram.
I am reporting this in the hope that some of you with more knowledge will know if this problem intersects with some other one in dpup, and perhaps point you with an additional hint in the direction of the solution.
Thanks again. In co-operation,
musher0
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
~~~~~~~~~~
"You want it darker? We kill the flame." (L. Cohen)
Hi guys,
I could manage to fix my kernel panic error at boot. Sadly this error will affect any Puppy distribution created with Woof.
I discovered the cause of this error, it´s init script in dpup. Although I can update this script with a new version, in a updated dpup release will present the same problem if Woof is not updated. I´m glad that Barry is working in woof, so I should report to him and hope for a definitive fix.
The problem mentioned in a early post (http://www.murga-linux.com/puppy/viewto ... &start=277) is:
When I boot dpup for the first time in MWare I created a pupsave file in one of my partition disk (used to test 214x, dpup, 4.3, etc) at shutdown, but I selected one partition with less of 120 MB, the pupsave was 32 MB and I had other pets here too. Then the free space left was about 50 MB.
Later when I boot dpup the second time, it found the pupsave and then it copied the dpup_482.sfs file in that partition. Here is the problem init script does not have a routine to validate free space before the SFS copy (actually this partitions free space is smaller than the SFS file). Anyway the sfs file was copied without any error or alert and the boot process complete successfully. Everything seems to work fine at this second boot.
Then When Pupp boots the third time, CRASH TIME, I get the kernel panic error because Dpup try to use the dpup_482.sfs found in the same directory of pup_save, BUT this is a damaged SFS produced in the second boot when I didn´t have enough free space in that partition (in fact this SFS files was about 40 MB, the original file is over 80 MB).
Well, I don´t like that "feature" (automate copy of xxx.sfs file to home directory) in new Puppys but I can live with that. And I understand Barry´s decision to include that "feature" to reduce successive boot times and increase performance without any user intervention.
The problem is that there are not enough validation before the SFS copy process and not even a single error or alert when you don´t have enough free space, the process just go on and produces a wrong SFS copy. I consider it a mayor bug for the init script that should be fixed in Woof. The good thing is, it only require a quick check in init then a easy fix could be implemented.
I understand Woof is in development and in a early state now.
Barry all your develop efforts are greatly appreciated, I evolve to a Puppy fanatic and a Barry´s admirer. I see Woof as a visionary base system for the future of Puppy and hope you take the voice of this humble Puppy user to improve Woof init script, I also thing a special Woof development thread should be created to discuss this issues.
Thank you all for the attention pleased,
clarf.
I could manage to fix my kernel panic error at boot. Sadly this error will affect any Puppy distribution created with Woof.
I discovered the cause of this error, it´s init script in dpup. Although I can update this script with a new version, in a updated dpup release will present the same problem if Woof is not updated. I´m glad that Barry is working in woof, so I should report to him and hope for a definitive fix.
The problem mentioned in a early post (http://www.murga-linux.com/puppy/viewto ... &start=277) is:
When I boot dpup for the first time in MWare I created a pupsave file in one of my partition disk (used to test 214x, dpup, 4.3, etc) at shutdown, but I selected one partition with less of 120 MB, the pupsave was 32 MB and I had other pets here too. Then the free space left was about 50 MB.
Later when I boot dpup the second time, it found the pupsave and then it copied the dpup_482.sfs file in that partition. Here is the problem init script does not have a routine to validate free space before the SFS copy (actually this partitions free space is smaller than the SFS file). Anyway the sfs file was copied without any error or alert and the boot process complete successfully. Everything seems to work fine at this second boot.
Then When Pupp boots the third time, CRASH TIME, I get the kernel panic error because Dpup try to use the dpup_482.sfs found in the same directory of pup_save, BUT this is a damaged SFS produced in the second boot when I didn´t have enough free space in that partition (in fact this SFS files was about 40 MB, the original file is over 80 MB).
Well, I don´t like that "feature" (automate copy of xxx.sfs file to home directory) in new Puppys but I can live with that. And I understand Barry´s decision to include that "feature" to reduce successive boot times and increase performance without any user intervention.
The problem is that there are not enough validation before the SFS copy process and not even a single error or alert when you don´t have enough free space, the process just go on and produces a wrong SFS copy. I consider it a mayor bug for the init script that should be fixed in Woof. The good thing is, it only require a quick check in init then a easy fix could be implemented.
I understand Woof is in development and in a early state now.
Barry all your develop efforts are greatly appreciated, I evolve to a Puppy fanatic and a Barry´s admirer. I see Woof as a visionary base system for the future of Puppy and hope you take the voice of this humble Puppy user to improve Woof init script, I also thing a special Woof development thread should be created to discuss this issues.
Thank you all for the attention pleased,
clarf.
So, if I understand correctly:
If on LiveCD boot, Puppy encounters a usable personal savefile on a partition which is nearly full, and has no Puppy sfs file, it will automatically write a new Puppy sfs on that directory, without checking for free space.
Because the newly saved Puppy sfs is larger than available disk space, it is corrupted. This appears as a kernel panic on the next puppy boot.
You would like Puppy to check for free space before automatically saving a copy of the Puppy sfs to disk.
EDIT: I'm surprised by this. I thought you had to explicitly choose to have a Puppy sfs saved on disk, just like the personal savefile. That dialog was always at the end ov a LiveCD session. Has something changed?
If on LiveCD boot, Puppy encounters a usable personal savefile on a partition which is nearly full, and has no Puppy sfs file, it will automatically write a new Puppy sfs on that directory, without checking for free space.
Because the newly saved Puppy sfs is larger than available disk space, it is corrupted. This appears as a kernel panic on the next puppy boot.
You would like Puppy to check for free space before automatically saving a copy of the Puppy sfs to disk.
EDIT: I'm surprised by this. I thought you had to explicitly choose to have a Puppy sfs saved on disk, just like the personal savefile. That dialog was always at the end ov a LiveCD session. Has something changed?