Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove Mylyn and PDE from BIRT product #899

Closed
wimjongman opened this issue Mar 27, 2022 · 5 comments
Closed

Remove Mylyn and PDE from BIRT product #899

wimjongman opened this issue Mar 27, 2022 · 5 comments
Milestone

Comments

@wimjongman
Copy link
Contributor

These two products have not much to do with report designers.

@hvbtup
Copy link
Contributor

hvbtup commented Mar 28, 2022

+1 for removing Mylyn, not 100% sure about PDE.

Developing a plugin (even if it is for BIRT) is so very different from developing reports, that > 99% of the BIRT users will never do this. OTOH if one really needs to develop a plugin for BIRT (I once did and I've started to develop a QR-code plugin in my free time) than the all-in-one developer environment is the natural choice.

@wimjongman
Copy link
Contributor Author

Wouldn't you say that the SDK is the natural choice in that case?

https://github.com/eclipse/birt#create-a-birt-development-environment

@hvbtup
Copy link
Contributor

hvbtup commented Mar 28, 2022

I can only speak for myself here.

When I developed the first plugin ~ 10 years ago, there was a tutorial and it was not too complicated to create a plugin with the All-in-one-designer. I would have been totally helpless with the SDK then.

When I started with the QR-code plugin, last weekend, I did use the SDK - but only because I already have the SDK installed and I didn't want to run 3 Eclipse environments (1=SDK run --> 2=all-in-one for plugin development debug --> 3=all-in-one to test the plugin). Still, the SDK ist too much for my little brain - I didn't know where to start, so I cloned the sample RotatedText plugin as a workaround.

IMHO it was much easier with the All-in-one environment, where basically you could just choose between creating a report/library/template or a plugin. OTOH it is helpful to have the full source code at hand for debugging the plugin.

@wimjongman
Copy link
Contributor Author

Yes, it makes sense. We will keep PDE in then. IIRC PDE was required in the early days because of the error log being there. I have ported that view to Eclipse Platform a couple of years ago.

@wimjongman wimjongman added this to the 4.13 milestone Jan 5, 2023
@wimjongman wimjongman modified the milestones: 4.13, 4.14 Mar 3, 2023
@speckyspooky
Copy link
Contributor

Mylin was removed with PR #1405

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants