January 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-12388) look into if usage dialog can become modeless and still be in front of the main window

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12388?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12388: ------------------------------------- Fix Version/s: 4.2.x (was: 4.0.x) > look into if usage dialog can become modeless and still be in front of the main window > -------------------------------------------------------------------------------------- > > Key: JBIDE-12388 > URL: https://issues.jboss.org/browse/JBIDE-12388 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: usage > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.2.x > > > would be interesting to see if usage dialog could be made modeless instead of modal to avoid blocking startups, especially during testing. > Previously we did not attemp this because the modeless dialog acted differently across OS's (mac and linux in particular) - maybe Juno SWT changes fixed this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12388) look into if usage dialog can become modeless and still be in front of the main window

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12388?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12388: ------------------------------------- Assignee: (was: Andre Dietisheim) > look into if usage dialog can become modeless and still be in front of the main window > -------------------------------------------------------------------------------------- > > Key: JBIDE-12388 > URL: https://issues.jboss.org/browse/JBIDE-12388 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: usage > Reporter: Max Rydahl Andersen > Priority: Critical > Fix For: 4.2.x > > > would be interesting to see if usage dialog could be made modeless instead of modal to avoid blocking startups, especially during testing. > Previously we did not attemp this because the modeless dialog acted differently across OS's (mac and linux in particular) - maybe Juno SWT changes fixed this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-12388) look into if usage dialog can become modeless and still be in front of the main window

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12388?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-12388: ------------------------------------- Priority: Major (was: Critical) > look into if usage dialog can become modeless and still be in front of the main window > -------------------------------------------------------------------------------------- > > Key: JBIDE-12388 > URL: https://issues.jboss.org/browse/JBIDE-12388 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: usage > Reporter: Max Rydahl Andersen > Fix For: 4.2.x > > > would be interesting to see if usage dialog could be made modeless instead of modal to avoid blocking startups, especially during testing. > Previously we did not attemp this because the modeless dialog acted differently across OS's (mac and linux in particular) - maybe Juno SWT changes fixed this. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-7062) usage report should track eclipse sessions

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-7062?page=com.atlassian.jira.plugin... ] Andre Dietisheim updated JBIDE-7062: ------------------------------------ Assignee: (was: Andre Dietisheim) > usage report should track eclipse sessions > ------------------------------------------ > > Key: JBIDE-7062 > URL: https://issues.jboss.org/browse/JBIDE-7062 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: usage > Affects Versions: 3.2.0.M2 > Reporter: Andre Dietisheim > Fix For: LATER > > > There are 2 levels of uniqueness: > - session (aka work session in Eclipse) -> reported as "page view" / "unique page view" > - Eclipse instance -> reported as "New Visitor" / "Returning Visitor" > Eclipse instances are trackable by querying the stats for 'Visitor Type' and the value 'New Visitor'/'Returning Visitor'. My plugin currently counts visits and GA recognizes this and reports accordingly. > It would be nice to have a match towards the sessions, too. Unfortunately I'm still not 100% sure how this stuff works. There are cookies for this (utmb, utmc) but no spec that details the values. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16333) Report 32/64-bit Eclipse/Java

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-16333: ---------------------------------------- Summary: Report 32/64-bit Eclipse/Java Key: JBIDE-16333 URL: https://issues.jboss.org/browse/JBIDE-16333 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: usage Affects Versions: 4.1.1.Final Reporter: Andre Dietisheim Fix For: 4.2.x On Mac there are limitations to use VPE (see mail thread started by Burr Sutter on 18/12/2013 "Eclipse on Mac OS X Mavericks") : {quote} Yes, that's our limitation on mac currently: a) you want VPE => you have to use 32bit eclipse => you have to use java 1.6 b) you don't need VPE => you can use 64bit eclipse => you can use java 1.7 {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-443) Simple guide to show app signing and deploying for iOS and Android

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-443?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-443: ------------------------------------------ If time permits, Hybrid Mobile Tools is to be added to the Getting Started Guide tutorial for the 8.0 release. I will keep this feedback in mind and aim to incorporate it as possible. [Explaining Android and iOS application structureor how to use them is beyond the scope of the JBDS User Guide, which is limited to the functionality of JBDS tooling.] > Simple guide to show app signing and deploying for iOS and Android > ------------------------------------------------------------------ > > Key: TOOLSDOC-443 > URL: https://issues.jboss.org/browse/TOOLSDOC-443 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: User Guide - Hybrid Mobile Tools > Reporter: Tadeas Kriz > Assignee: Michelle Murray > > The documentation shows how to export "Mobile Application" in chapter 8.3.7. It says "ready-to-sign applications", but I'd be good to show, what can the user then do with the exported application, as readers of this guide might not be aware of how native packages work. > When export is made for iOS, the output is a single .app package. For Android, it's an .apk archive. It should be made clear to user what those packages are and possibly link to official documentation on given topic if it exists. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-443) Simple guide to show app signing and deploying for iOS and Android

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-443?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-443: ------------------------------------- Affects Version/s: 4.1.1 > Simple guide to show app signing and deploying for iOS and Android > ------------------------------------------------------------------ > > Key: TOOLSDOC-443 > URL: https://issues.jboss.org/browse/TOOLSDOC-443 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: User Guide - Hybrid Mobile Tools > Affects Versions: 4.1.1 > Reporter: Tadeas Kriz > Assignee: Michelle Murray > > The documentation shows how to export "Mobile Application" in chapter 8.3.7. It says "ready-to-sign applications", but I'd be good to show, what can the user then do with the exported application, as readers of this guide might not be aware of how native packages work. > When export is made for iOS, the output is a single .app package. For Android, it's an .apk archive. It should be made clear to user what those packages are and possibly link to official documentation on given topic if it exists. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-443) Simple guide to show app signing and deploying for iOS and Android

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-443?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-443: ------------------------------------- Fix Version/s: 4.2.0 > Simple guide to show app signing and deploying for iOS and Android > ------------------------------------------------------------------ > > Key: TOOLSDOC-443 > URL: https://issues.jboss.org/browse/TOOLSDOC-443 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: User Guide - Hybrid Mobile Tools > Affects Versions: 4.1.1 > Reporter: Tadeas Kriz > Assignee: Michelle Murray > Fix For: 4.2.0 > > > The documentation shows how to export "Mobile Application" in chapter 8.3.7. It says "ready-to-sign applications", but I'd be good to show, what can the user then do with the exported application, as readers of this guide might not be aware of how native packages work. > When export is made for iOS, the output is a single .app package. For Android, it's an .apk archive. It should be made clear to user what those packages are and possibly link to official documentation on given topic if it exists. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-441) Typo in 8.2.2. unordered list

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-441?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-441: ------------------------------------- Component/s: User Guide - Hybrid Mobile Tools (was: User Guide) > Typo in 8.2.2. unordered list > ----------------------------- > > Key: TOOLSDOC-441 > URL: https://issues.jboss.org/browse/TOOLSDOC-441 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: User Guide - Hybrid Mobile Tools > Affects Versions: 4.1.1 > Environment: Build Name: 22443, User Guide-7.1 > Build Date: 11-12-2013 15:10:49 > Topic ID: 24051-567464 [Latest] > Reporter: Tadeas Kriz > Assignee: Michelle Murray > Priority: Trivial > Fix For: 4.1.2 > > > Title: About Hybrid Mobile Tools > Describe the issue: > In the unordered list, fourth item, there is "Android and iOS *SKDs*" (the bold is only to show what's wrong) > Suggestions for improvement: > It should say "Android and iOS *SDKs*" (the bold is only to show what exactly should change) > Additional information: -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-442) Confusing order of chapters

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-442?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-442: ------------------------------------------ [~tkriz], thanks for the feedback. Valid point - will determine how best to fix and update doc for 7.1.1 release. Need to make sure requirements are specified before informing how to install so perhaps should just take the instruction parts out of 8.2.4 and 8.2.5 and put these into 8.2.6, would be better than linking. Will need to look more closely at it. > Confusing order of chapters > --------------------------- > > Key: TOOLSDOC-442 > URL: https://issues.jboss.org/browse/TOOLSDOC-442 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: User Guide, User Guide - Hybrid Mobile Tools > Environment: Build Name: 22443, User Guide-7.1 > Build Date: 11-12-2013 15:10:49 > Topic ID: 24053-567457 [Latest] > Reporter: Tadeas Kriz > Assignee: Michelle Murray > Priority: Critical > > Title: Install Hybrid Mobile Tools and CordovaSim > Describe the issue: > The 8.2 chapter's current sub-chapter order is confusing. There are example screens shown in chapter 8.2.4. and 8.2.5., which the user can't find until he installs the Hybrid Mobile Tools by following the chapter 8.2.6. > Suggestions for improvement: > I recommend the order to be 8.2.1., 8.2.2., 8.2.3., 8.2.6., 8.2.4., 8.2.5. > Also, it'd be wise to link the 8.2.4. and 8.2.5. chapters from the 8.2.6. > Additional information: -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 3 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues January 2014