Hi Juergen,

Thank you very much for the promptly reply. Please find my comments inline.

On Fri, Mar 29, 2013 at 12:29 AM, Juergen Schmidt <jogischm...@gmail.com>wrote:

> Hi Ishan,
>
> first of all welcome at Apache and thank you for interest in this proposed
> GSoC project.
>
>
> Am Donnerstag, 28. März 2013 um 18:02 schrieb Ishan Thilina:
>
> > Hi,
> >
> > I am a student from the Faculty of Engineering, Universtiy of Moratuwa,
> Sri
> > Lanka who is currently in my 4th year (final year) majoring in Computer
> > Science and Engineering. I was a GSoC participant in 2012 for Creative
> > Commons and was able to successfully complete the assigned project[1].
> >
> > The projects aim was to port an existing Java LibreOffice extension to
> > Python. So I have an understanding about the OpenOffice API and I've been
> > exposed to extensions development using both Java and Python for
> > LibreOffice.
> >
> >
>
> sounds good so far
> >
> > I saw the idea of creating an OpenOffice Extension Plugin for Eclipse
> from
> > [2]. Although I don't have prior experience on writing plugins for
> Eclipse,
> > I think with proper guidance I achieve the goals of this project.
> >
> >
>
> The Eclipse  community is very big and there is a lot documentation
> available. I am also no Eclipse expert but I will do my best to give you
> the necessary guidance and advice.
>

Yes, I too agree to the fact that learning how to write eclipse plugins
should be done my my self. What I meant by "proper guidance" is mostly the
design decisions that will be involved in the plugin development process.

I will start learning about eclipse plugins development as soon as possible
so that I can get a clear understanding about the difficulty of the project
it self and submit a strong proposal.


> I mentored a similar project years ago but it is not directly comparable
> with what we have for NetBeans already and license is not compatible with
> the Apache license.
> Anyway what I have it mind goes in the direction of the NetBeans plugin. I
> recommend that you take a look on it and try it out.
>

Yes, I have already used the NetBeans plugin. I used for my work in GSoC
2012, So I'm familiar with its functionality.


> The idea is to provide some further tooling for developers who prefer
> Eclipse over NetBeans and potentially bring in more ideas ;-)
> Or support the same kind of wizard for different languages, eg. Java,
> Python and maybe c++.
> But the initial project should focus on the first basic steps of course.
>
> For example setting up working extension projects in Eclipse and think in
> a second step how it can convert in a plugin with wizards...,
> >
> > What will be your selection criteria for a GSoC student? Are there any
> > other things that I need to be aware of this project?
> >
> >
>
> I wrote it the description already and it depends how many students are
> interested in this project. I am open to work with interested people and in
> the end it is up to them to move the project forward and to a success.


So I guess the way to start working on the project is to first take a look
at on how to write Eclipse plugins. But this could take some time. Also I
think by looking at the NetBeans plugin, we'd be able to get a proper idea
on how to   *package an extension package (oxt), deploy it from Eclipse
into the office and how to remote debug the extension in the office* (one
of your ideas in the jira issue).

Any other particular guidelines on what I should be focusing with in this
period?


> >
> > You can access my LinkedIn profile from [3]. It'll list many of my
> project
> > work and achievements.
> >
> >
>
> I will take a closer look on it later...
>
> Kind regards
> Juergen
> >
> >
> > [1]. http://code.creativecommons.org/viewgit/cc.libreoffice.git/
> > [2]. https://issues.apache.org/jira/browse/COMDEV-77
> > [3]. www.linkedin.com/pub/ishan-somasiri/25/bab/951
> >
> >
> > --
> > Thank you..!
> > ---------------------------------------------------------------------
> > 071-6372089
> >
> > Ishan's info: www.ishans.info
> > මගේ සටහන්: www.siblog.ishans.info
> > Ishan's way: www.blog.ishans.info
> > ---------------------------------------------------------------------
> >
> >
>
>
>

Reply via email to