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

feat: #572 Theme replicating the coloring of the WTP XML editor #573

Closed
wants to merge 8 commits into from
Closed

feat: #572 Theme replicating the coloring of the WTP XML editor #573

wants to merge 8 commits into from

Conversation

kevloral
Copy link
Contributor

It is not perfect (some items share the same CSS), but it is close enough.

It is not perfect (some items share the same CSS), but is close enough.
@angelozerr
Copy link
Contributor

Thanks @kevloral !

Could you add a screenshot with a sample just to see the result of your PR please.

@angelozerr
Copy link
Contributor

Perhaps we should find a new name than Tradional? WTP for instance?

I suggest too to add your theme in the extensionpoint https://github.com/eclipse/tm4e/blob/88bb9c8d20b5c0bfb11573766fa709bba38323bf/org.eclipse.tm4e.ui/plugin.xml#L44 in order to TM4E provides this new theme.

@kevloral
Copy link
Contributor Author

Actual WTP XML editor:
image

With the Traditional theme:
image

As you can see, the equals sign color does not match and the the highlighting is different too.

@kevloral
Copy link
Contributor Author

The theme has been renamed (now it is called WTP XML Classic) and has been added to the plugin descriptor.

@sebthom sebthom changed the title #572 Theme replicating the coloring of the WTP XML editor feat: #572 Theme replicating the coloring of the WTP XML editor Jul 28, 2023
@sebthom
Copy link
Member

sebthom commented Jul 28, 2023

@kevloral can you please bump the minor version in the MANIFEST.MF and pom.xml of the UI plugin. This should fix the build error

@kevloral
Copy link
Contributor Author

kevloral commented Jul 28, 2023

Sure, but I do not know the policy you have wrt versioning. Would 0.7.1 be fine? Or should it be 0.8.0?

Edit: I just noticed you said minor version. Ok. 0.8.0 then.

Minor version increased (0.7.0 -> 0.8.0)
Minor version increased (0.7.0 -> 0.8.0)
The feature version must be updated too (0.6.0 -> 0.7.0)
The feature version must be updated too (0.6.0 -> 0.7.0)
@kevloral
Copy link
Contributor Author

Feature (org.eclipse.tm4e.feature) version updated (0.6.0 -> 0.7.0) too.

@kevloral kevloral closed this by deleting the head repository Aug 6, 2023
@mickaelistria
Copy link
Contributor

GitHub says "@kevloral closed this by deleting the head repository". Is this intended?

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

Successfully merging this pull request may close these issues.

4 participants