Hi :) It's always a good idea to post to the Users List first because if we can't answer it we can signpost to documentation and / or better lists also we do have people with unexpected skills, talents and experience on this list.
Sorry to hear you didn't get a response from the devs list. If any list has not given a decent response after a day or 2 then post again, preferably as a comment into the same thread as the one you just started but as a new question might not hurt either. Apols and regards from Tom :) >________________________________ > From: Stephen Morris <samor...@netspace.net.au> >To: Tom Davies <tomdavie...@yahoo.co.uk>; "michael.me...@suse.com" ><michael.me...@suse.com> >Cc: LibreOffice Users <users@global.libreoffice.org> >Sent: Monday, 18 March 2013, 20:49 >Subject: Re: [libreoffice-users] Development of Extensions for LibreOffice > >On 03/19/2013 01:56 AM, Tom Davies wrote: >> Hi :) >> Thanks for the answer. I think the question was beyond the scope of the >> Users List and i don't know if anyone got around to pointing the person to >> the devs lists. >Hi Tom, > Michael did point me at the developers list and when I sent my last >mail through I cced the developers list, but as yet I haven't had a >response. Michael has provided me with some more info that should help >with what I am trying to do. > >regards, >Steve > >> >> >> Err, was there a slight typo in the last paragraph? Seems like grep got >> typed as grok? >> "which you can grok for user-visible strings" >> Perhaps would have been more generic as "look for"? >> >> Regards from >> Tom :) >> >> >> >> >> >>> ________________________________ >>> From: Michael Meeks <michael.me...@suse.com> >>> To: Stephen Morris <samor...@netspace.net.au> >>> Cc: LibreOffice Users <users@global.libreoffice.org>; Kohei Yoshida >>> <kyosh...@novell.com>; libreoff...@lists.freedesktop.org >>> Sent: Monday, 18 March 2013, 11:54 >>> Subject: Re: [libreoffice-users] Development of Extensions for LibreOffice >>> >>> Hi Stephen, >>> >>> On Mon, 2013-03-18 at 08:34 +1100, Stephen Morris wrote: >>>> I am having all sorts of problems with the source code in Eclipse. I >>>> have created a new blank C++ project in Eclipse and imported the entire >>>> sc directory into that project. Subsequently I have opened >>>> dpgroupdlg.cxx in the editor (I'm also not sure why Eclipse displays all >>>> directories duplicated) and Eclipse is displaying errors on just about >>>> every statement in that file. >>> Well - that's really Eclipse' problem :-) can you turn off it's bogus >>> error display ? I guess getting help with Eclipse would be a good thing >>> to do. Potentially you don't want to create a project - but just use it >>> to edit the specific files. >>> >>>> I think the first thing I need to do is to find all the include >>>> files and add those directories into the include file path in the >>>> project properties. One of the problems I have is that the statement >>>> "com::sun::star::sheet::DataPilotFieldGroupBy::SECONDS," is producing an >>>> error complaining that symbol SECONDS is not found. >>> This is from an UNO / generated header. It seems highly unlikely that >>> Eclipse is going to do a perfect job of building LibreOffice. As such, I >>> would use it as a syntax-colouring text editor - not in it's all-seeing >>> monster mode ;-) >>> >>>> How I configure eclipse to consider the idl file to be the same as >>>> the hpp file so that these symbols get resolved? >>> I have no idea. You need to edit the code with some sort of source code >>> editor, Elipse is one option. If it can't control it's urges to try to >>> understand the entire (apparently not built) code-base then I'd >>> recommend using something else ;-) >>> >>>> I am also having difficulty determining which dp module equates to >>>> the dialog that gets displayed for variables that are dragged to the >>>> pivot table layout areas, to specify the attributes of those variables. >>>> Is there any documentation anywhere that explains what each module >>>> within the suite actually does and how they relate to what is actually >>>> displayed by Libreoffice for each function it performs? >>> Each module ? each top-level directory has README - patches to improve >>> them appreciated. Sadly there is no further good structural >>> documentation at all. >>> >>> In general - if you want to go from the UI -> the source code, you need >>> to go via the .src files - which you can grok for user-visible strings, >>> and then look for the defined names of those in the .hrc files - which >>> are shared between resources and C++ and hence into the relevant source >>> code and down to a widget. >>> >>> Hope that helps :-) >>> >>> Michael. >>> >>> -- >>> michael.me...@suse.com <><, Pseudo Engineer, itinerant idiot >>> >>> >>> -- >>> For unsubscribe instructions e-mail to: users+h...@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 >>> >>> >>> > > >-- >For unsubscribe instructions e-mail to: users+h...@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 > > > > -- For unsubscribe instructions e-mail to: users+h...@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
