[JBoss JIRA] (DEVTOOLS-3) Update/Refresh SWT Documentation
by Leo Ufimtsev (JIRA)
[ https://issues.jboss.org/browse/DEVTOOLS-3?page=com.atlassian.jira.plugin... ]
Leo Ufimtsev updated DEVTOOLS-3:
--------------------------------
Labels: SWT (was: swt)
> Update/Refresh SWT Documentation
> --------------------------------
>
> Key: DEVTOOLS-3
> URL: https://issues.jboss.org/browse/DEVTOOLS-3
> Project: Developer Tools Team (IDE)
> Issue Type: Task
> Reporter: Leo Ufimtsev
> Assignee: Leo Ufimtsev
> Labels: SWT
> Time Spent: 2 hours
> Remaining Estimate: 1 day, 2 hours
>
> During the Eclipse conference, a number of users complained that it is hard to figure out how to get started with SWT, how to contribute etc..
> Current documentation has a lot of sections that are out of date, (e.g win XP screen shots).
> The documentation needs to be consolidated, reduced, simplified, upated and made more clear.
> It might be beneficial to track visitors to documentation page also maybe.. .
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months
[JBoss JIRA] (ERT-527) [GTK3][Webkit2] Implement webkit2 support for browser function (Part 2: Java return a value from callback.) [EBZ#510905]
by Leo Ufimtsev (JIRA)
[ https://issues.jboss.org/browse/ERT-527?page=com.atlassian.jira.plugin.sy... ]
Leo Ufimtsev updated ERT-527:
-----------------------------
Sprint: devex #139 October 2017
> [GTK3][Webkit2] Implement webkit2 support for browser function (Part 2: Java return a value from callback.) [EBZ#510905]
> ------------------------------------------------------------------------------------------------------------------------
>
> Key: ERT-527
> URL: https://issues.jboss.org/browse/ERT-527
> Project: Eclipse Release Train
> Issue Type: Task
> Components: Platform
> Reporter: Friendly Jira Robot
> Labels: SWT, bzira
>
> The mechanism whereby javascript calls java in Part1 (Bug 508217) has a limitation.
> Javascript can reach Java's callback. But the callback on the javaside cannot return a value back to javascript.
> I don't think this functionality is used much, but never the less it is a current limitation.
> (Note, Java can execute javascript via 'execute()' call still).
> The jUnit test case for this scenario is:
> org.eclipse.swt.tests.junit.Test_org_eclipse_swt_browser_Browser.test_BrowserFunction_callback_with_javaReturningInt()
> The api that I used in Part1 allows Javascript to call Java asynchronously.
> I.e, meaning once the callback is executed on the java side, it doesn't return a value:
> https://webkitgtk.org/reference/webkit2gtk/stable/WebKitUserContentManage...
> This is a limitation of the webkit2 api itself. The signal has a void return value and since it is async, the call from javascript to java is not executed right away, but is delayed for a bit.
> One possible (complex) solution might be:
> - Create webkitweb extension (this is tricky..)
> - Manually create a C/Javascript object (webkit1 does this, 'external', might re-use this functionality).
> - Expose Js function/object via JavaSciptCoreApi
> - Suggested by aperezdc/mcatanzaro on freednode#webkitgtk+
> Example:
> https://git.gnome.org/browse/epiphany/tree/embed/web-extension/ephy-web-e...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
6 years, 7 months