Date: prev next · Thread: first prev next last
2011 Archives by date, by thread · List index


On 09/15/2011 08:03 AM, Onyeibo Oku wrote:
Sometime ago, I wrote to this list when I was developing an Extension
for automating some tasks for fellow lecturers using spreadsheets to
compute School Results. I was advocating migration from MS-Office to
LibO for my colleagues because they knew little about spreadsheets and
were using mostly pirated software.

LO over pirated MSO, yes they need to get rid of the pirates.
The adventure, so far, has been intriguing and fraught with challenges.
The solution was not new.  I was porting something I did in 2006 from
VBA to Python for LibO -- an opportunity to test my skills in python for
real.  The new one is better implemented.

On Thursday,September 8, 2011, I formally presented the update to the
Department of Architecture in Enugu State University, Nigeria.  It was
totally welcomed.  That means LibO is staying as far as the department
is concerned.  I have Hanya to thank for this progress.  Please see:
http://user.services.openoffice.org/en/forum/viewtopic.php?f=45&t=43492

I aim to push LibO further than that.  I'm being asked to document the
Extension.  To do that, I need to replace the generic icons I used in my
demo/beta toolbar with something unique.  The adventure is now on *phase
two*.

Questions:
Why is LibO requiring magenta (0xFF00FF) to interpret transparency for
toolbar icons? The wiki states that it (imageidentifier) is deprecated
yet all attempts to use the 'images' configuration branch fail.  With
'images' branch, transparencies in PNG are supported.  Why can't I get
this to work?  Anybody interested in seeing a sample of my addon.xcu file???

Is there a way to ensure macro privacy/invisibility even for extensions
installed by users (not administrators)?.  This is one area VBA still
beats LibO.  In Excel the macros a wrapped up in the .XLS file and can
be password protected (However, tools exist to extract the password ...
hehehe).  In libO, one only needs to know the installation paths to see
everything.


IS the computers going to be attached to an in-house network/file-server? If so, is there a way to have the installation folder on a network drive with READ-ONLY unless you have the password to the folder? I know that you can edit some of the paths. OR, is there a way, with Windows systems, to password protect as READ-ONLY for a folder unless you sign in as an administrator? I know that you use to be able to HIDE files and folders by changing the attributes for them. If there hidden or read-only, then that could solve some problems here.
I am still activating a macro listener manually after loading the target
document.  Attempts to do this via events throw errors. The event is
passing an argument I cannot decode yet. Yeah, I know ... someone needs
to read the developers guide again.  Any ideas are welcome though.

Why does the toolbar icons show in Linux and disappear in LibO 3.4
(Windows).  Is there something different in 3.4 specs?
I have seen, in the LO Extension test site that there are some listed with a versions for 3.3.x and 3.4.x, so it looks like there may be some specification changes. I know that LO is slowly removing JAVA from their code and replacing it with Python [I believe] so there may be some issues there, or not.



--
For unsubscribe instructions e-mail to: users+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/users/
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.