Bugzilla – Full Text Bug Listing
| Summary: | Unify code of orion/Section and sections in the Editor RHS view | ||
|---|---|---|---|
| Product: | [ECD] Orion | Reporter: | Malgorzata Janczarska <malgorzata.tomczyk> |
| Component: | Client | Assignee: | Malgorzata Janczarska <malgorzata.tomczyk> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | antonm, gheorghe, Silenio_Quarti, simon_kaegi |
| Version: | 4.0 | Flags: | malgorzata.tomczyk:
review?
(simon_kaegi) |
| Target Milestone: | 5.0 M1 | ||
| Hardware: | PC | ||
| OS: | Windows 7 | ||
| Whiteboard: | |||
| Bug Depends on: | 422235 | ||
| Bug Blocks: | |||
|
Description
Malgorzata Janczarska
Bogdan, this is the bug for unifying Sections and editor RHS tables I told you about. I think it would be ideal if we could create a widget that as an alternative has a table or just a div content like in README view. There are a few concepts we could probably want to unify here: 1. Section 2. Explorer, including: * have some common rendering of each explorer item, that will render this table-like view we have now * add actions for explorer in the section header * some common selection 3. orion/dynamicContent * Git pages use dynamic content to load some details dynamically (for instance first display the list of branches and after that render information about last commit for each one) 4. We should add a concept of primary content and secondary content that have common css across Orion RHS is not unified with Section and Explorers in this commit: http://git.eclipse.org/c/orion/org.eclipse.orion.client.git/commit/?id=86c740ead607e9ed57cfd991938e1611a04afe7e There still is work to use this API in Git pages and maybe enhance it. Simon, I need your +1 to add it to maintenance branch together with a fix for bug 422235. This looks like cleanup. Why do we need this in the maintenance branch? > This looks like cleanup. Why do we need this in the maintenance branch?
Because we will be able to adopt those changes in applications build against the maintenance branch and this is meant to simplify the overwritten styles and duplications of code in there.
See bug#422488. (In reply to comment #6) > See bug#422488. I'll fix it, but I don't think it's a stopper for backporting it to maintenance branch. |