[JBoss JIRA] (JBIDE-18813) Convert JBoss Central to an HTML5 page
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18813?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-18813.
---------------------------------
Resolution: Done
The bulk of the work is now done. Marking as resolved. New tickets can be opened for the bugs we find
> Convert JBoss Central to an HTML5 page
> --------------------------------------
>
> Key: JBIDE-18813
> URL: https://issues.jboss.org/browse/JBIDE-18813
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: central
> Affects Versions: 4.3.0.Alpha1
> Reporter: Fred Bricon
> Assignee: Fred Bricon
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Beta1
>
> Attachments: Central Design Concept A.bmml, Central Design Concept A.bmml, Central Design Concept A.bmml, Central Design Concept A.png, Central Design Concept B.bmml, Central Design Concept B.bmml, Central Design Concept B.png, Central design concept E.bmml, Central design concept E.png, Design concept C - Search centric layout.bmml, Design concept C - Search centric layout.png, Design Concept D - categories across top.bmml, Design Concept D - categories across top.bmml, Design Concept D - categories across top.png, JBoss Access Panel Concept.bmml, JBoss Access Panel Concept.png, JBoss Central User Stories and Flows.gliffy, JBossCentral_DesignC_HighFidelity_InitialState.png, JBossCentral_DesignC_HighFidelity_SearchState.png, JBossCentral_DesignC_HighFidelity_SmallScreen_InitialState.png, JBossCentral_DesignC_HighFidelity_SmallScreen_SearchState.png, JBossCentral_DesignC_HighFidelity_SmallScreen_StarterHover.png, JBossCentral_DesignC_HighFidelity_StarterHover.png, Screen Shot 2015-01-16 at 4.38.58 PM.png
>
>
> Central Page requires new capabilities :
> - needs more customization (display content depending on user preferences)
> - needs to scale with JBDS-IS, Fuse content
> - access to more examples, with filtering capabilities
> Given that the existing page is pretty hard to maintain and suffers from scalability/UI bugs, we're heading towards an HTML5 approach :
> - use an embedded SWT Browser widget (or Java FX), depending on the platform compatibility
> - webpage and its content could be served remotely (as zip), and downloaded locally for offline use. this would give us more flexibility to update the content.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 3 months
[JBoss JIRA] (JBIDE-19924) For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Birt]
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19924?page=com.atlassian.jira.plugi... ]
Snjezana Peco closed JBIDE-19924.
---------------------------------
Resolution: Done
> For JBIDE 4.3.0.Beta1: Code Freeze + Branch [Birt]
> --------------------------------------------------
>
> Key: JBIDE-19924
> URL: https://issues.jboss.org/browse/JBIDE-19924
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: birt
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Priority: Blocker
> Labels: task
> Fix For: 4.3.0.Beta1
>
>
> For JBIDE 4.3.0.Beta1 [Birt]: Please perform the following tasks:
> 0. If nothing has changed in your component since the creation of the 4.2.x branch (eg., Portal, Freemarker), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.3.0.Beta1
> [Unresolved JIRAs with fixVersion = 4.3.0.Beta1, 9.0.0.Beta1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%2...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0, or from 1.2.2 to 1.2.100.
> *NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
> {code}
> mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.3.0.Beta1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Beta1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Beta1;
> {code}
> mvn clean verify -Dtpc.version=4.50.0.Beta1-SNAPSHOT # (if the TP is still a SNAPSHOT)
> or
> mvn clean verify -Dtpc.version=4.50.0.Beta1 # (if the TP is already released)
> {code}
> 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch;
> {code}
> git checkout master
> git pull origin master
> git checkout -b jbosstools-4.3.0.Beta1x
> git push origin jbosstools-4.3.0.Beta1x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
> {code}
> git checkout master
> git pull origin master
> {code}
> 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.3.0.Beta2-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.3.0.Beta2-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.3.0.Beta1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.3.0.Beta1x{color}* branch, and
> * *{color:orange}4.3.0.Beta2-SNAPSHOT{color}* in your *{color:orange}master{color}* bran
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Birt task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 3 months