Hi Andreas,
We have not started working on the project yet. We are still in scoping
stages and I am trying to finalize the milestones that we will have to
achieve. I think starting with support of importing and exporting the
macros would be a good as we will gain a understanding of the existing code
base (as we have never contributed before).
Let me know your thoughts on this. Suggestions are welcome.
Thanks,
Aman
On Tue, Feb 17, 2015 at 12:12 AM, Andreas Beeker <[email protected]>
wrote:
> Hi Aman,
>
> > Support for
> > Importing/exporting/creating macros from java will make the tool a lot
> more
> > maintainable and reduce operation load as well.
> Importing and exporting seems to be not so complicated, i.e. in xlsx it's
> a .bin file, which needs to be imported and linked.
> But creating needs an implementation of OVBA [1] - is creating really
> necessary, or can you live with importing a predefined binary from Office?
>
> How far is your implementation? How do you cope with that issue up till
> now?
>
> I only had a quickview over OVBA, but it looks like, there is no
> compilation necessary, just a bit of source (de-)compression.
>
> Apart of that, I inline here my private response to you, as I think, this
> still applies: "...
>
> > Why does POI does not support Macros? Any specific reasons?
> Although I could guess, that would probably be not the reason ... if a
> feature is not strongly demanded, it usually
> drops from the interest list and for new features, either its in the
> interest of one of the committers to develop it
> or we get a ready-to-merge patch
>
> > What are the high level milestones that need to be done in case someone
> wants this to be implemented?
> Afaik we don't work with milestones - I guess the support within XSSF is
> much easier, so I would start there.
>
> > We are a group (3-4) of developers who want to contribute to open source
> and this is a problem we face at work.
> > ... but macros are kind of black box from the code (over a period of
> years have becoming non maintainable for us).
> Sounds good - when you say it's a black box from the code, that means you
> can't simply safe a xlsx with macros,
> compare and add the necessary parts with POI?
> I.e. do you want to create a specific vbaproject.bin for every file or can
> use a predefined (pre-exported from Office)?
>
> ..."
>
> Best wishes,
> Andi
>
>
> [1] https://msdn.microsoft.com/en-us/library/cc313094(v=office.12).aspx
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>
