Re: [users] Where does Linux/Mint OOo Store RGB Color Codes?

2010-12-15 Thread James Greenidge

On 12/13/10 7:28 PM, Daniel Lewis wrote:
If you are using the version of OOo provided by Mint, the preset 
parts of OOo are probably located within the /etc/ folder. That is not 
what you want. You mentioned three locations for the standard.soc 
file, but you did not mention where the third location was. If you 
look at my earlier reply, I mentioned a location: 
/home/.openoffice.org/. What I should have written 
/home/user/.openoffice.org/3/user/config/ as the folder containing 
the file you need. The user in the address is the name of the folder 
which contains all of your personal folders. For example, on my Linux 
box, my user name is dan. So, this file is located at 
/home/dan/.openoffice.org/3/user/config/. Another thing: the period in 
front of openoffice.org is used by Linux to identify a hidden folder 
or file. I'm not sure how you searched for the standard.soc file. Did 
you use the command line or something else. This might help some.


Dan


In the immortal words of Captain J.J. Adams The damned thing's 
invisible!, I have you to thank for locating the files in question -- 
only visible in show hidden files mode! Like who'd ever know that, and 
Why?? Wouldn't it make it a heck of a lot easier (not that mucking 
around with CLI is  anyway!) for the poor green user to transfer their 
personalized defaults and bio between OOo versions by keeping it out in 
the open? No wonder Billy isn't all that bothered that OOo exists! 
Anyway, thanks a mint for your input Dan and Merry Xmas!


Jim


-
To unsubscribe, e-mail: users-unsubscr...@openoffice.org
For additional commands, e-mail: users-h...@openoffice.org



Re: [users] Where does Linux/Mint OOo Store RGB Color Codes?

2010-12-15 Thread James Greenidge

On 12/15/10 7:45 AM, Daniel Lewis wrote:

James Greenidge wrote:
In the immortal words of Captain J.J. Adams The damned thing's 
invisible!, I have you to thank for locating the files in question 
-- only visible in show hidden files mode! Like who'd ever know 
that, and Why?? Wouldn't it make it a heck of a lot easier (not that 
mucking around with CLI is  anyway!) for the poor green user to 
transfer their personalized defaults and bio between OOo versions by 
keeping it out in the open? No wonder Billy isn't all that bothered 
that OOo exists! Anyway, thanks a mint for your input Dan and Merry 
Xmas!


Jim

 I'm sending this off list directly to you. Back around OOo 
version 2.0.0, (I think this was the first one), OOo made its folder  
hidden in the /home/user/ folder hiddenfor Linux. I wondered why at 
the time. But as I have used Linux more and more, I realized that this 
was how Linux distributions did it. Selecting Show hidden files will 
show many hidden folders for programs used by the user. So, its a 
matter of understanding the structure of Linux more than OOo. The 
location of the preset file folder follows the Linux tradition: using 
the /etc/ and /init/ folders. The Linux version from the OOo website 
uses the /opt/ folder to place its preset files. This too follows the 
Linux tradition.
 But this is no different than Windows versions nor Mac OS X. Each 
one has a specific location that if very different from other 
operating systems. I still have problems finding what I want because 
the location is in the .../user/Library/Application Support/. This did 
not make sense to me as a Linux user for several years. When I want to 
delete a program for some reason, I have learned to drag it to the 
Trash. But I have no idea of how many folders I have in the 
Application Support folder containing files that I no longer need. But 
this is a Mac thing. It can be as frustrating as you are finding Mint 
Linux.
 Suggestion: Learn the quirks of Mint Linux, and the frustration 
level will drop tremendously.  Hang in there, things will get better.


Dan



Thanks Dan. The only thing is that one shouldn't be a jedi geek to do 
something this elementary! For me, the larger OOo marketing/public 
relations/customer service question is -- doesn't it behoove OpenOffice 
(or whatever it's cloned into now) to make things easier for novices and 
the totally clueless lay-user to transfer their personal configs and 
defaults between OOo versions? Lay non-geek/techie people using OOo 
Windows with lengthy bio user data and several hundred custom colors who 
want to move on to OOo Mac or OOo Mint or visa versa will think twice 
and head back to Word and MS Office if they can't easily transfer their 
OOo configs to other OOo versions. People on 
http://ubuntuforums.org/forumdisplay.php?f=130 and 
https://answers.launchpad.net/ claim that it should take a good OOo 
programmer less than fifteen minutes to whip up such a cross-platform 
OOo config transfer script. It seems to this callow guy that'd be a good 
way for OOo to reap more users who would otherwise be put off trying to 
stay in the OOo fold -- at least you'd do so if you were really out to 
make a profit.


Merry Xmas All!


-
To unsubscribe, e-mail: users-unsubscr...@openoffice.org
For additional commands, e-mail: users-h...@openoffice.org



Re: [users] Where does Linux/Mint OOo Store RGB Color Codes?

2010-12-13 Thread James Greenidge
Bruce, thank you for your suggestions and we'll take it under serious 
consideration. It's just a shame that users and beta testers have to go 
it alone with complicated ad hoc remedies like this on issues which are 
basic programming knowledge to OOo programmers and writers. But by God, 
isn't there a member of the OOo crew here who can suggest less 
jump-thru-hoops suggestions than this when laypeople and schools and 
companies are changing platforms and wish to take OOo along with them? 
Surely a method to semi-painlessly transfer configs and defaults between 
OOo variants would better grease the way to attract more users!


Exasperated JIm in NYC


On 12/12/10 9:00 PM, Bruce_Martin wrote:

Dear James and all:

My experience is that Oo stores color codes, hatches and gradients all 
in the same place relative to itself.


This alone does not give you the exact path, as that can vary in 
relation to the different platforms.


However there is a simple procedure I use to load, store and migrate 
this data between Fedora, Win XP etc on my network, and carry it 
physically to friend's machines (as I have created a number of custom 
colours and gradients.)


*_Procedure:_*

In whatever installation of Oo you are using...

1)Open a blank Oo Draw file.

2)Draw a rectangle (size is minimally important, as long as it 
fits the page and is big enough to see the fill colour.)


3 )   Right click (PC) on the fill.

4)From the menu that appears, choose area.

5)Then choose the colours tab.

6)Close to the right side of the colour choice window, look for 2 
icons, One usually a blue floppy, (to save as the colour palette), 
the other one above it to load a colour palette.


7)Open either one of these, and you will get the contents of the 
default folder that holds the color palette (usual extension: .SOC) 
The default file name is Standard.SOC, and the size will depend on 
the number of colours it contains at the time. (Mine, with added 
colours is only about 12 Kb.)


8)In the usual manner for navigating, start to navigate - more to 
see where the default folder is located than to actually do anything.


9)If you want to export a colour palette, load it into Oo, then 
save it with the other icon, navigating to your desired new location. 
Then you will end up saving a copy of it in that location, which can 
be a USB stick, and external or network drive or whatever you have.


10)Likewise, using the load icon, you can load a file from any 
other location, then save it as the Standard.SOC file, overwriting 
the one in the default folder and, providing the new file is a 
legitimate SOC, it will be the default colour palette once you close 
and restart Open office - no need to reboot as a rule.


11)All the preceding stuff repeats for Gradients (Default 
Standard.SOG) and Hatches - Default Standard.SOG


12)If the installation were on a MAC, either the HFS or HFS+ file 
system would likely generate the usual mac fork, or that might be done 
by the underlying Java runtime used with the MAC (Tiger and up.)


12a)When exporting from a MAC to a PC environment, it is 
normal to end up with 3 files for each part of the MAC fork: The Data 
Resource is the one you need for the PC, the Resource and other forks 
should be saved aside, so that when you need to re-import the file 
back from the PC world to the MAC world, you simply copy the modified 
PC file back into the folder where the other 2 files were kept, making 
sure the filenames (aside from the extensions) are identical, then, in 
the MAC environment, the re-integration of the 3 files back into the 
MAC fork is normally done automatically when you copy the file back 
into the MAC environment.


On the older MACS, this was done with a PC formatted floppy used in 
the MAC floppy drive, as on either the 1.44Mb PC floppy and the same 
physical floppy, formatted as HFS (MAC) 900 Kb. were actually encoded MFM.


On USB Sticks, the file system should be FAT16, but Likely could work 
with ext2 or ext3, providing the MAC OS is capable of reading those 
systems currently.


In the case of an External HD (USB of IEEE1394/Firewire) the likely 
system would be FAT32.


NAS drives are more complex, as they generally have a firmware OS 
which is network transparent. Personally here my NAS box is the D-Link 
DNS-323 which is a UNIX box.


Since the latest major firmware upgrade flashes  the obligatory 
initial initialise and format the box does on anew drive can be ext2 
or ext3 (latter preferred) but other machines will see this as if it 
were NTFS, or, alternatively this box has built-in SFTP and Torrent 
servers as well as the more normal Windows network protocol. In Linux 
(Fedora 14 x_64) I access this via Samba. The box also has firmware 
RAID capability and scheduled automated download capability.


This box can go well with D-Link's DIR-825, as it likes a Gb. Wired 
connection (CAT 6 cable required).


Happy computing and 

Re: [users] Where does Linux/Mint OOo Store RGB Color Codes?

2010-12-13 Thread Daniel Lewis
  Perhaps this will help: The color table is stored in 
/home/.openoffice.org/3/user/config/ in the standard .soc file. This is 
using the OOo version downloaded from the OOo website. The Mac version 
is home/Library/Application Support/openoffice.org/3/user/config. Again 
it is the standard .soc file.
 Before copying  the standard.soc file from another location, you 
might consider renaming the standard.soc file you want to replace. Then 
copy the desired standard.soc file into the same folder. Close OOo if it 
is running. Open it to see if you now have the color table that you want.
 NOTICE: The locations are accurate. The suggestions are what I 
think, but I have never tried to do this. They may not work even if I 
think they should.


Dan

James Greenidge wrote:
Bruce, thank you for your suggestions and we'll take it under serious 
consideration. It's just a shame that users and beta testers have to 
go it alone with complicated ad hoc remedies like this on issues which 
are basic programming knowledge to OOo programmers and writers. But by 
God, isn't there a member of the OOo crew here who can suggest less 
jump-thru-hoops suggestions than this when laypeople and schools and 
companies are changing platforms and wish to take OOo along with them? 
Surely a method to semi-painlessly transfer configs and defaults 
between OOo variants would better grease the way to attract more users!


Exasperated JIm in NYC


On 12/12/10 9:00 PM, Bruce_Martin wrote:

Dear James and all:

My experience is that Oo stores color codes, hatches and gradients 
all in the same place relative to itself.


This alone does not give you the exact path, as that can vary in 
relation to the different platforms.


However there is a simple procedure I use to load, store and migrate 
this data between Fedora, Win XP etc on my network, and carry it 
physically to friend's machines (as I have created a number of custom 
colours and gradients.)


*_Procedure:_*

In whatever installation of Oo you are using...

1)Open a blank Oo Draw file.

2)Draw a rectangle (size is minimally important, as long as it 
fits the page and is big enough to see the fill colour.)


3 )   Right click (PC) on the fill.

4)From the menu that appears, choose area.

5)Then choose the colours tab.

6)Close to the right side of the colour choice window, look for 2 
icons, One usually a blue floppy, (to save as the colour palette), 
the other one above it to load a colour palette.


7)Open either one of these, and you will get the contents of the 
default folder that holds the color palette (usual extension: .SOC) 
The default file name is Standard.SOC, and the size will depend on 
the number of colours it contains at the time. (Mine, with added 
colours is only about 12 Kb.)


8)In the usual manner for navigating, start to navigate - more to 
see where the default folder is located than to actually do anything.


9)If you want to export a colour palette, load it into Oo, then 
save it with the other icon, navigating to your desired new location. 
Then you will end up saving a copy of it in that location, which can 
be a USB stick, and external or network drive or whatever you have.


10)Likewise, using the load icon, you can load a file from any 
other location, then save it as the Standard.SOC file, overwriting 
the one in the default folder and, providing the new file is a 
legitimate SOC, it will be the default colour palette once you close 
and restart Open office - no need to reboot as a rule.


11)All the preceding stuff repeats for Gradients (Default 
Standard.SOG) and Hatches - Default Standard.SOG


12)If the installation were on a MAC, either the HFS or HFS+ file 
system would likely generate the usual mac fork, or that might be 
done by the underlying Java runtime used with the MAC (Tiger and up.)


12a)When exporting from a MAC to a PC environment, it is 
normal to end up with 3 files for each part of the MAC fork: The Data 
Resource is the one you need for the PC, the Resource and other forks 
should be saved aside, so that when you need to re-import the file 
back from the PC world to the MAC world, you simply copy the modified 
PC file back into the folder where the other 2 files were kept, 
making sure the filenames (aside from the extensions) are identical, 
then, in the MAC environment, the re-integration of the 3 files back 
into the MAC fork is normally done automatically when you copy the 
file back into the MAC environment.


On the older MACS, this was done with a PC formatted floppy used in 
the MAC floppy drive, as on either the 1.44Mb PC floppy and the same 
physical floppy, formatted as HFS (MAC) 900 Kb. were actually encoded 
MFM.


On USB Sticks, the file system should be FAT16, but Likely could work 
with ext2 or ext3, providing the MAC OS is capable of reading those 
systems currently.


In the case of an External HD (USB of IEEE1394/Firewire) the likely 
system would 

Re: [users] Where does Linux/Mint OOo Store RGB Color Codes?

2010-12-13 Thread James Greenidge

On 12/13/10 10:53 AM, Daniel Lewis wrote:
  Perhaps this will help: The color table is stored in 
/home/.openoffice.org/3/user/config/ in the standard .soc file. This 
is using the OOo version downloaded from the OOo website. The Mac 
version is home/Library/Application 
Support/openoffice.org/3/user/config. Again it is the standard .soc file.
 Before copying  the standard.soc file from another location, you 
might consider renaming the standard.soc file you want to replace. 
Then copy the desired standard.soc file into the same folder. Close 
OOo if it is running. Open it to see if you now have the color table 
that you want.
 NOTICE: The locations are accurate. The suggestions are what I 
think, but I have never tried to do this. They may not work even if I 
think they should.


Dan 


Seasons Greetings Dan and thanks, however as far I could find, the 
directory structure of Mint is a morass of branches and duplicated 
folders. A file search for OpenOffice and standard.soc came up readily 
enough in Mac, but in Mint a file search popped up nothing less than 
three separate OpenOffice folders in threads raging from /etc/ to /init/ 
and some were alias dead-ends or plain empty. I'm no hacker and I really 
don't want to play Indiana Jones delving our hard drives just to 
transfer color and address and default info from Mac OOo into Mint OOo. 
I wonder how many perspective users OOo lost because people couldn't 
transfer their personal Mac or PC or Linux Ooo defaults between another. 
Surely there's a simple script that can swing this, and I'd really be 
nice if the brains in the know could lend a hint.


Jim in NYC


-
To unsubscribe, e-mail: users-unsubscr...@openoffice.org
For additional commands, e-mail: users-h...@openoffice.org



Re: [users] Where does Linux/Mint OOo Store RGB Color Codes?

2010-12-13 Thread Daniel Lewis

James Greenidge wrote:

On 12/13/10 10:53 AM, Daniel Lewis wrote:
  Perhaps this will help: The color table is stored in 
/home/.openoffice.org/3/user/config/ in the standard .soc file. This 
is using the OOo version downloaded from the OOo website. The Mac 
version is home/Library/Application 
Support/openoffice.org/3/user/config. Again it is the standard .soc 
file.
 Before copying  the standard.soc file from another location, you 
might consider renaming the standard.soc file you want to replace. 
Then copy the desired standard.soc file into the same folder. Close 
OOo if it is running. Open it to see if you now have the color table 
that you want.
 NOTICE: The locations are accurate. The suggestions are what I 
think, but I have never tried to do this. They may not work even if I 
think they should.


Dan 


Seasons Greetings Dan and thanks, however as far I could find, the 
directory structure of Mint is a morass of branches and duplicated 
folders. A file search for OpenOffice and standard.soc came up readily 
enough in Mac, but in Mint a file search popped up nothing less than 
three separate OpenOffice folders in threads raging from /etc/ to 
/init/ and some were alias dead-ends or plain empty. I'm no hacker and 
I really don't want to play Indiana Jones delving our hard drives just 
to transfer color and address and default info from Mac OOo into Mint 
OOo. I wonder how many perspective users OOo lost because people 
couldn't transfer their personal Mac or PC or Linux Ooo defaults 
between another. Surely there's a simple script that can swing this, 
and I'd really be nice if the brains in the know could lend a hint.


Jim in NYC

 If you are using the version of OOo provided by Mint, the preset 
parts of OOo are probably located within the /etc/ folder. That is not 
what you want. You mentioned three locations for the standard.soc file, 
but you did not mention where the third location was. If you look at my 
earlier reply, I mentioned a location: /home/.openoffice.org/. What I 
should have written /home/user/.openoffice.org/3/user/config/ as the 
folder containing the file you need. The user in the address is the 
name of the folder which contains all of your personal folders. For 
example, on my Linux box, my user name is dan. So, this file is 
located at /home/dan/.openoffice.org/3/user/config/. Another thing: the 
period in front of openoffice.org is used by Linux to identify a hidden 
folder or file. I'm not sure how you searched for the standard.soc file. 
Did you use the command line or something else. This might help some.


Dan



-
To unsubscribe, e-mail: users-unsubscr...@openoffice.org
For additional commands, e-mail: users-h...@openoffice.org



[users] Where does Linux/Mint OOo Store RGB Color Codes?

2010-12-12 Thread James Greenidge

Seasons Greetings:

I'd be happy enough just being pointed to where Linux/Mint OOo stores 
its color code files so I can figure out how to replace it with the one 
from Mac OOo to save my home school the time and tedium of inputting 
over eighty custom non-Sun color codes. Thanks.


Jim


-
To unsubscribe, e-mail: users-unsubscr...@openoffice.org
For additional commands, e-mail: users-h...@openoffice.org



Re: [users] Where does Linux/Mint OOo Store RGB Color Codes?

2010-12-12 Thread Bruce_Martin

Dear James and all:

My experience is that Oo stores color codes, hatches and gradients all 
in the same place relative to itself.


This alone does not give you the exact path, as that can vary in 
relation to the different platforms.


However there is a simple procedure I use to load, store and migrate 
this data between Fedora, Win XP etc on my network, and carry it 
physically to friend's machines (as I have created a number of custom 
colours and gradients.)


*_Procedure:_*

In whatever installation of Oo you are using...

1)Open a blank Oo Draw file.

2)Draw a rectangle (size is minimally important, as long as it fits 
the page and is big enough to see the fill colour.)


3 )   Right click (PC) on the fill.

4)From the menu that appears, choose area.

5)Then choose the colours tab.

6)Close to the right side of the colour choice window, look for 2 
icons, One usually a blue floppy, (to save as the colour palette), the 
other one above it to load a colour palette.


7)Open either one of these, and you will get the contents of the 
default folder that holds the color palette (usual extension: .SOC) The 
default file name is Standard.SOC, and the size will depend on the 
number of colours it contains at the time. (Mine, with added colours is 
only about 12 Kb.)


8)In the usual manner for navigating, start to navigate - more to 
see where the default folder is located than to actually do anything.


9)If you want to export a colour palette, load it into Oo, then save 
it with the other icon, navigating to your desired new location. Then 
you will end up saving a copy of it in that location, which can be a USB 
stick, and external or network drive or whatever you have.


10)Likewise, using the load icon, you can load a file from any other 
location, then save it as the Standard.SOC file, overwriting the one 
in the default folder and, providing the new file is a legitimate SOC, 
it will be the default colour palette once you close and restart Open 
office - no need to reboot as a rule.


11)All the preceding stuff repeats for Gradients (Default 
Standard.SOG) and Hatches - Default Standard.SOG


12)If the installation were on a MAC, either the HFS or HFS+ file 
system would likely generate the usual mac fork, or that might be done 
by the underlying Java runtime used with the MAC (Tiger and up.)


12a)When exporting from a MAC to a PC environment, it is normal 
to end up with 3 files for each part of the MAC fork: The Data Resource 
is the one you need for the PC, the Resource and other forks should be 
saved aside, so that when you need to re-import the file back from the 
PC world to the MAC world, you simply copy the modified PC file back 
into the folder where the other 2 files were kept, making sure the 
filenames (aside from the extensions) are identical, then, in the MAC 
environment, the re-integration of the 3 files back into the MAC fork is 
normally done automatically when you copy the file back into the MAC 
environment.


On the older MACS, this was done with a PC formatted floppy used in the 
MAC floppy drive, as on either the 1.44Mb PC floppy and the same 
physical floppy, formatted as HFS (MAC) 900 Kb. were actually encoded MFM.


On USB Sticks, the file system should be FAT16, but Likely could work 
with ext2 or ext3, providing the MAC OS is capable of reading those 
systems currently.


In the case of an External HD (USB of IEEE1394/Firewire) the likely 
system would be FAT32.


NAS drives are more complex, as they generally have a firmware OS which 
is network transparent. Personally here my NAS box is the D-Link DNS-323 
which is a UNIX box.


Since the latest major firmware upgrade flashes  the obligatory initial 
initialise and format the box does on anew drive can be ext2 or ext3 
(latter preferred) but other machines will see this as if it were NTFS, 
or, alternatively this box has built-in SFTP and Torrent servers as well 
as the more normal Windows network protocol. In Linux (Fedora 14 x_64) I 
access this via Samba. The box also has firmware RAID capability and 
scheduled automated download capability.


This box can go well with D-Link's DIR-825, as it likes a Gb. Wired 
connection (CAT 6 cable required).


Happy computing and learning!

I hope you all find my answer a colourful answer (guffaw).

Bruce M.


On 12/12/2010 19:09, James Greenidge wrote:

Seasons Greetings:

I'd be happy enough just being pointed to where Linux/Mint OOo stores 
its color code files so I can figure out how to replace it with the 
one from Mac OOo to save my home school the time and tedium of 
inputting over eighty custom non-Sun color codes. Thanks.


Jim


-
To unsubscribe, e-mail: users-unsubscr...@openoffice.org
For additional commands, e-mail: users-h...@openoffice.org



--
Best Regards, Bruce Martin