[
https://issues.jboss.org/browse/JBIDE-15457?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-15457:
---------------------------------------------
[~burrsutter] not following what engineering promotion have to do with it. in past we
wanted to promote standalone browsersim but it was shutdown as "not important"
:)
The question here is if there is a need/usecase for running browsersim externally that
outweighs the cost of doing so - and right now I and as far as I can see [~gercan]
don't see such a need.
Thus I would vote for launching the server side parts inside eclipse, but keeping the
dependencies and API clean so it is clear where this running. If it is kept clean a user
can run his own http server to provide the cordova parts which cordovasim could run
against.
CordovaSim and Hybrid tools interaction/source code sharing
-----------------------------------------------------------
Key: JBIDE-15457
URL:
https://issues.jboss.org/browse/JBIDE-15457
Project: Tools (JBoss Tools)
Issue Type: Task
Components: aerogear-hybrid, browsersim
Reporter: Yahor Radtsevich
Assignee: Yahor Radtsevich
Fix For: 4.2.x
Currently CordovaSim application consists of two parts: a Jetty-based server, and a
BrowserSim-based client. The server part generates some content on the fly. For instance,
the server may response with generated {{cordova_plugins.js}} content when it is requested
by the client. Both parts of CordovaSim are executed in their own JVM, which means they do
not have access to the Eclipse API.
Hybrid tools do very similar things, but in static way. For instance, while creating
Android executables, they create {{cordova_plugins.js}} file on disk. Hybrid tools is a
set of Eclipse plugins, so they have access to the Eclipse API.
Obviously CordovaSim and Hybrid tools have some code in their sources that could be
shared. For the example above, both of them need a method to generate content of
{{cordova_plugins.js}}. There are several approaches to implement it:
1. Create two different implementations for CordovaSim and Hybrid tools and synchronize
them when needed (currently we do this). This approach creates code duplication problems.
2. Create an Eclipse API-independent plugin, so both CordovaSim and Hybrid tools could
set it as a dependency. This approach imposes some restriction on the independent plugin
(useful Eclipse API and libs cannot be used).
3. Move the server part of CordovaSim to the Eclipse JVM, so it could use Eclipse API and
any Hybrid tools API. With this approach we loose the ability to create standalone
CordovaSim in the future.
--
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