For my dictionary extensions, I used the "externally hosted" option.
Since I can have my offerings placed onto one of my domains, I can use
that option.
So it links to the externally hosted file, instead of the hosting on the
LO server system.
I wonder when this file extension stripping will get fixed. When I
tried to deal with the CMS editing for some of the pages for a project,
I uploaded some files and the filenames were modified. It replaced or
removed the underline "_" character in the file names. I did not like
that. But this stripping of the file extension type is a worse action
to my feeling.
Hopefully it will be fixed soon. Otherwise, some people might need some
other way to do it. For me, I would offer anyone who wants to have a
place to host their .oxt files till the system works. I could create an
FTP account for them to upload their files to - limited folder size though.
If you want to have me place you files on one of my domains, I would.
You can contact me off this list about options you could use, including
an FTP accessible folder off one of my domains.
.
On 11/20/2011 11:19 AM, Michael Bauer wrote:
Yes I do. I've already emailed Andreas Mantke about this but I'll
gladly sum up my main points again. Please take this as constructive
criticism, I certainly want this project to succeed :)
The process is fiendishly complicated and rather cryptic. Now, I
apologise for being slightly vague, having only one extension I did
not go through the process more than once and I wasn't making notes,
so this is from memory.
1) The window where one uploads the extensions is crackers. Mine is a
spellchecker, something.oxt. I selected the file and moved one. But in
the process of uploading, the .oxt was stripped and in some *other*
window where I was asked for a name (I think) it neither stated (nor
did it occur to me) that I have to add the .oxt onto the filename
again. Why? If I'm uploading xxxx.oxt, then the system should
recognise this. Also, I suspect that most people already have given
their desired name to their extensions, so the option of renaming
seems rather superfluous.
At no point was there a warning either that my extension was
unworkable due to a lack of .oxt. Fortunately someone spotted this
when testing and we fixed it... but that's slightly mad.
2) Too many obscure windows. In the process, I'm asked to name and
version my extension several times but on neither occassion was it
obvious to me what actually went where in the end. For some reasons -
and I don't seem to be able to change that though I'Ve certainly tried
- mine is now called
Current Release
An Dearbhair Beag - Scottish Gaelic Spellchecker an-dearbhair
and the Version is
an-dearbhair
I certainly didn't want the current release to be that long or the
version to be text... but I still can't figure how to amend those
bits. Maybe I'm just more used to it but the OO extension site was a
lot easier to handle.
If you want to check out the mess I managed to create, see
http://extensions.libreoffice.org/extension-center/an-dearbhair-beag-scottish-gaelic-spellchecker
Salude e trigu,
Michael
20/11/2011 16:03, sgrìobh webmaster for Kracked Press Productions:
Any ideas about what is going on?
Any ideas on how a user can get the listed software?
Should we allow an extension/template be listed if there is no file
to test out?
--
Unsubscribe instructions: E-mail to website+help@global.libreoffice.org
Problems? http://www.libreoffice.org/get-help/mailing-lists/how-to-unsubscribe/
Posting guidelines + more: http://wiki.documentfoundation.org/Netiquette
List archive: http://listarchives.libreoffice.org/global/website/
All messages sent to this list will be publicly archived and cannot be deleted
Context
Privacy Policy |
Impressum (Legal Info) |
Copyright information: Unless otherwise specified, all text and images
on this website are licensed under the
Creative Commons Attribution-Share Alike 3.0 License.
This does not include the source code of LibreOffice, which is
licensed under the Mozilla Public License (
MPLv2).
"LibreOffice" and "The Document Foundation" are
registered trademarks of their corresponding registered owners or are
in actual use as trademarks in one or more countries. Their respective
logos and icons are also subject to international copyright laws. Use
thereof is explained in our
trademark policy.