[JBoss JIRA] (JBIDE-19192) provide option for disable html preview
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19192?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-19192:
-------------------------------------------
Fix Version/s: 4.3.0.Beta2
(was: 4.3.0.Beta1)
> provide option for disable html preview
> ---------------------------------------
>
> Key: JBIDE-19192
> URL: https://issues.jboss.org/browse/JBIDE-19192
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.2.Final
> Environment: win8.1 64 eclipse luna 4.4.0 jboss 4.2.2
> Reporter: jim harber
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Fix For: 4.3.0.Beta2
>
> Attachments: Clipboard01.png
>
>
> when i use tween.js to create a html page,i create an array,here is the problem:
> var eles = [];
> //push such as 500 elements into eles;
> ..
> then i need call a function to update every element in eles,when these two line:
> requestAnimationFrame(animate);
> TWEEN.update();
> already in the function,i can't see a change in preview and it makes eclipse shutdown,so i put this two line when i finish the other codes,this time preview become normal.
> every time when i type to for(var i=0;i<eles.length;i) eclipse gets stuck. so i wonder is thers any chance i can shutdown living view,i checked preferences panel i didn't find anything.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19259) JSF or HTML5 support choosing issues
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19259?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-19259:
-------------------------------------------
Fix Version/s: 4.3.0.Beta2
(was: 4.3.0.Beta1)
> JSF or HTML5 support choosing issues
> ------------------------------------
>
> Key: JBIDE-19259
> URL: https://issues.jboss.org/browse/JBIDE-19259
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core, xulrunner
> Affects Versions: 4.3.0.Alpha1
> Environment: Fedora 20 GNOME 64 bit, Open JDK 7, Alpha2-v20150212-0919-B9496
> Reporter: Vlado Pakan
> Assignee: Konstantin Marmalyukov
> Fix For: 4.3.0.Beta2
>
>
> # GKT2 + xulrunner loaded + JSF support enabled: HTML5 page not rendered - visual part of VPE should contain similar message as in case HTML5 support is enabled for XHTML page informing users about possibility to enable HTML5 suppport
> # VPE Preference page should contain checkbox with choice: "Always ask" otherwise user will never be able to get dialog asking to choose between JSF and HTML5 support once he will check check box "Do not show this message again"
> # When support is changed page is opened and then Eclipse is restarted it would look better if page won't be opened before Eclipse is restarted. Page should be opened after restart
> # With GTK3 "Visual Editor Browser Engine" group within VPE prefrences page is hidden it would be more user friendly just disable it and add some label why it's disabled?.The same way as selecting of GTK for BrowserSim/CordovaSim works.
> # Confusing scenario #1:
> ## Set HTML5 support
> ## Open .xhtml page and say "Stay with HTML5"
> ## Open .html page
> ## Restart Eclipse
> ## Close .html page
> ## ERROR: Dialog asking to choose between HTML5 or JSF support is displayed. It's confusing to ask this when page is closed.
> # Confusing scenario #2:
> ## Set HTML5 support
> ## Open .xhtml page and say "Stay with HTML5"
> ## Restart Eclipse
> ## ERROR: Dialog asking to choose between HTML5 or JSF support is displayed before workspace window appears. This dialog should be displayed once worspace is visible and user actually can see page he is going to open.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19360) JSF or HTML5 Support: don't show dialog for the first opened page
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19360?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-19360:
-------------------------------------------
Fix Version/s: 4.3.0.Beta2
(was: 4.3.0.Beta1)
> JSF or HTML5 Support: don't show dialog for the first opened page
> -----------------------------------------------------------------
>
> Key: JBIDE-19360
> URL: https://issues.jboss.org/browse/JBIDE-19360
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: visual-page-editor-core
> Affects Versions: 4.3.0.Alpha1
> Reporter: Konstantin Marmalyukov
> Assignee: Konstantin Marmalyukov
> Fix For: 4.3.0.Beta2
>
>
> Confusing scenario #2:
> * Set HTML5 support
> * Open .xhtml page and say "Stay with HTML5"
> * Restart Eclipse
> ERROR: Dialog asking to choose between HTML5 or JSF support is displayed before workspace window appears. This dialog should be displayed once worspace is visible and user actually can see page he is going to open.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19452) extension point for editors to tell html5 preview which html content to render
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19452?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-19452:
-------------------------------------------
Fix Version/s: 4.3.x
(was: 4.3.0.Beta1)
> extension point for editors to tell html5 preview which html content to render
> ------------------------------------------------------------------------------
>
> Key: JBIDE-19452
> URL: https://issues.jboss.org/browse/JBIDE-19452
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Reporter: Max Rydahl Andersen
> Assignee: Konstantin Marmalyukov
> Fix For: 4.3.x
>
>
> html preview seem to figure out that text from structured editor is the actual document in the editor.
> But when you have something like the Visual JSF Page Editor or Mylyn wiki text editor where the html content is actually not in the main document but something generated html preview does not work.
> it would be great if html5 preview would have an extension point where one can install a handler for a specific editor what html should be shown in the preview.
> end result: when opening mylyn wiki text editor it should show what corresponds to the Preview tab, not the source tab.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-8874) Support XML documents for XSLT compliant browser
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-8874?page=com.atlassian.jira.plugin... ]
Konstantin Marmalyukov updated JBIDE-8874:
------------------------------------------
Fix Version/s: 4.3.x
(was: 4.3.0.Beta1)
> Support XML documents for XSLT compliant browser
> ------------------------------------------------
>
> Key: JBIDE-8874
> URL: https://issues.jboss.org/browse/JBIDE-8874
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: visual-page-editor-core
> Affects Versions: 3.3.0.M1
> Reporter: Denis Golovin
> Assignee: Konstantin Marmalyukov
> Priority: Minor
> Fix For: 4.3.x
>
> Attachments: screenshot-1.png, screenshot-2.png, screenshot-3.png, screenshot59.png, wecandoit.png, xml-xsl.png
>
>
> Would be good to have support to show documents for XSLT compliant browser like
> {code:title=cdcatalog.xsl|borderStyle=solid}
> <?xml version="1.0" encoding="ISO-8859-1"?>
> <!-- Edited by XMLSpy® -->
> <xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
> <xsl:template match="/">
> <html>
> <body>
> <h2>My CD Collection</h2>
> <table border="1">
> <tr bgcolor="#9acd32">
> <th>Title</th>
> <th>Artist</th>
> </tr>
> <xsl:for-each select="catalog/cd">
> <tr>
> <td><xsl:value-of select="title"/></td>
> <td><xsl:value-of select="artist"/></td>
> </tr>
> </xsl:for-each>
> </table>
> </body>
> </html>
> </xsl:template>
> </xsl:stylesheet>
> {code}
> {code:title=page.xml|borderStyle=solid}
> <?xml version="1.0" encoding="ISO-8859-1"?>
> <?xml-stylesheet type="text/xsl" href="cdcatalog.xsl"?>
> <!-- Edited by XMLSpy® -->
> <catalog>
> <cd>
> <title>Empire Burlesque</title>
> <artist>Bob Dylan</artist>
> <country>USA</country>
> <company>Columbia</company>
> <price>10.90</price>
> <year>1985</year>
> </cd>
> <cd>
> <title>Hide your heart</title>
> <artist>Bonnie Tyler</artist>
> <country>UK</country>
> <company>CBS Records</company>
> <price>9.90</price>
> <year>1988</year>
> </cd>
> <cd>
> <title>Greatest Hits</title>
> <artist>Dolly Parton</artist>
> <country>USA</country>
> <company>RCA</company>
> <price>9.90</price>
> <year>1982</year>
> </cd>
> </catalog>
> {code}
> Visual part of editor would look like:
> !screenshot59.png!
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-18772) Include publish steps in pom files
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-18772:
----------------------------------------
jbosstools-integration-tests job seems to have been successfully updated.
Remaining:
* devstudio.product : requires more specific steps, so pom has to be changed
* jbosstools-browsersim-standalone : doesn't match the generic deployment procedure, so its pom requires some customization
* jbosstools-discovery : requires more specific steps, as generic process isn't covering this case
* jbosstools-integration-stack-tests.aggregate : Needs adoption of a more recent parent pom +needs additional configuration to publish also to snapshot location. see jbosstools-integration-tests/site/pom.xml as reference
* RedDeer_master : Does NOT use JBoss Tools parent, so configuration of the deploy-to-jboss profile from JBT parent pom has to be duplicated to Red Deer before updating the job
> Include publish steps in pom files
> ----------------------------------
>
> Key: JBIDE-18772
> URL: https://issues.jboss.org/browse/JBIDE-18772
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.3.0.Beta1
>
> Attachments: jbds-publish-to-snapshots.png
>
>
> instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses.
> suggestion:
> publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing.
> What this helps with is:
> a) can do changes to publish mechanism without affecting every past builds.
> b) more movable build system
> c) isolated testing possible
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months
[JBoss JIRA] (JBIDE-19835) 'JPA Tools -> Generate Tables from Entities' does not work for Hibernate 4.0
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19835?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-19835:
------------------------------
Fix Version/s: 4.3.0.Beta1
(was: 4.3.0.Beta2)
Sprint: Sprint #4 May 2015
> 'JPA Tools -> Generate Tables from Entities' does not work for Hibernate 4.0
> ----------------------------------------------------------------------------
>
> Key: JBIDE-19835
> URL: https://issues.jboss.org/browse/JBIDE-19835
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Reporter: Koen Aers
> Assignee: Koen Aers
> Fix For: 4.3.0.Beta1
>
>
> This issue is a result of further investigation of JBIDE-19431 and JBIDE-19535. This investigation showed me that the generation of DDL works fine (wether a defined console configuration is used or not) unless version 4.0 of Hibernate is used.
> So for JPA 2.0 (which uses Hibernate 4.0 under the covers) the DDL generation does not work if the console configuration is used, nor when the use of a console configuration is disabled and Hibernate 4.0 is selected in the DDL generation dialog. It works however for Hibernate 3.5, 3.6 and 4.3.
> For a JPA 1.0 project, DDL generation works with the console configuration and when console configuration is disabled and Hibernate 3.5, 3.6 or 4.3 are selected in the DDL generation dialog.
> For JPA 2.1, only Hibernate 4.3 is a compatible Hibernate version and DDL generation works in this case both with and without using the console configuration.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 10 months