Automatically exported from code.google.com/p/openmobster
zied-ellouze / openmobster Goto Github PK
View Code? Open in Web Editor NEWAutomatically exported from code.google.com/p/openmobster
Automatically exported from code.google.com/p/openmobster
Port the device side stack to the Android Operating System.
Versions to support: 1.5+
Original issue reported on code.google.com by [email protected]
on 20 Jan 2010 at 10:28
The Dev Mode CloudManager is installed via a link to its location in the local
maven repo,
This creates a chicken and egg problem for sample apps where maven repo is not
loaded by a build from source.
Having this packaged solves the problem and the missing artifacts will be
downloaded from the internet.
In any case, for long term development use, the maven repo formed from a build
of source code using:
mvn -DskipTests -Pbuild-all install
is the cleanest way to set your development environment
Original issue reported on code.google.com by [email protected]
on 25 Feb 2011 at 2:04
Some improvements
* Add the ability to trigger a Cloud Push for demonstrating the Push feature
* On the Channel side, may be disable the Mock bean generator
* Make it less ugly looking ;)
Original issue reported on code.google.com by [email protected]
on 10 Apr 2010 at 3:14
When the App is launched, if the Push Daemon is disabled,
The App should perform a Channel sync in the background. This will
automatically synchronize the state of the App with that on the Cloud.
If Push is active, all this will already be synchronized in the background,
so this step is unnecessary.
Also, add a callback to components in the MVC framework to deal with the
case when new data needs to be displayed
Original issue reported on code.google.com by [email protected]
on 22 Apr 2010 at 4:56
While testing socket connections on the real BlackBerry 8330
* noticed that on the CDMA phone sometimes a fair bit of data traffic over
a single NetSession (in this case single two way socket), causes data
corruption. The failover mechanism used to care of sudden network failures
handles this issue
* but it would be nice if such socket anomalies can be handles without failure
* In theory this should not happen and socket communication should stay kosher
* but for some reason due to bugs in TCP/IP implementations on the device
side, this situation is possible
* See here for details:
http://supportforums.blackberry.com/t5/Java-Development/Socket-Write-strange-pro
blem/td-p/55843
Original issue reported on code.google.com by [email protected]
on 16 Apr 2010 at 2:14
A remotely accessible Device Management Module integrated with the Cloud
Console.
Possible Functions:
* Remote Lock
* Remote Wipe
* Activation/Deactivation with the Cloud, etc
Original issue reported on code.google.com by [email protected]
on 1 Mar 2011 at 8:37
This will help with diagonosing device side errors. Users should be able to
dump the OpenMobster Error Log right from the device via the CloudManager app
Original issue reported on code.google.com by [email protected]
on 16 Apr 2010 at 2:19
The 'port' field should be pre-populated with the default Cloud Server Port of
1502
Original issue reported on code.google.com by [email protected]
on 19 Nov 2010 at 4:58
"Activation" click from the List is fine. "Activation" click from the Menu is
the problem
Only applies to the development mode CloudManager App
Original issue reported on code.google.com by [email protected]
on 19 Nov 2010 at 4:56
If the Push Daemon dies for whatever reason, it should auto recover.
Right now the user can either soft turnoff the device or use the manual
start/stop feature under the CloudManager
Original issue reported on code.google.com by [email protected]
on 22 Apr 2010 at 5:04
Inside the Cloudmanager it must show which type of push setting is
currently active
Original issue reported on code.google.com by [email protected]
on 16 Apr 2010 at 3:46
The default setup is a single shared runtime packaged with the CloudManager App.
All Cloud Apps installed on the device use this shared runtime.
However, if there is only a single App involved like someone distributing
throgh the App store, there needs to be plumbing such that the App + Cloud
runtime are packaged and deployed as a single app.
One side effect: Use this deployment option only when there is only one Cloud
App being distributed. If more than one app needs to use the Cloud runtime,
this option should not be used
Original issue reported on code.google.com by [email protected]
on 27 Jan 2011 at 6:51
This so that its clear it means the AppStore that hosts the Corporate Apps
installed on the OpenMobster system.
Not some universal, carrier, or vendor-specific appstore
Original issue reported on code.google.com by [email protected]
on 16 Apr 2010 at 3:49
[deleted issue]
Update the AppCreator such that the user can choose to create an App with the
Cloud runtime included.
Note:There shouldn't be multiple apps installed with this setup which can
result in multiple instances of the shared Cloud runtime.
See this thread for details:
http://groups.google.com/group/openmobster-users/browse_thread/thread/514e2998bb
d8a00f
Original issue reported on code.google.com by [email protected]
on 19 Nov 2010 at 5:02
APN for Push
Original issue reported on code.google.com by [email protected]
on 13 Mar 2011 at 3:05
Implement DeviceManagement Callback for devices to notify device management
meta data.
Original issue reported on code.google.com by [email protected]
on 7 Mar 2011 at 8:25
AppCreator is lagging in producing the project template.
It still carries traces of the deprecated BlackBerry platform
Original issue reported on code.google.com by [email protected]
on 11 Feb 2011 at 7:45
Enhance the MVC framework so that Cloud Push can be handled at the
App-level if necessary. At this time the notification is at the system level
Original issue reported on code.google.com by [email protected]
on 22 Apr 2010 at 4:57
Blackberry Eclipse JDE plugin has issues with developing Blackberry Apps
that consume 3rd party libraries.
A Moblet is a Blackberry App that integrates with the OpenMobster Cloud
using OpenMobster Cloud libraries.
This process for using the 3rd party libraries needs to be simplified for
the Moblet Developer.
Original issue reported on code.google.com by [email protected]
on 7 Feb 2010 at 4:38
Under Push Settings, show the status of the PushListener, so that user can
find out if the daemon that receives push updates from the server is
active. If not, they can recycle the daemon so that it does become actively
listening
Original issue reported on code.google.com by [email protected]
on 10 Apr 2010 at 3:48
Integrate the camera hardware with services in the Cloud.
Original issue reported on code.google.com by [email protected]
on 13 Feb 2011 at 5:06
This should not be required to be specified by the App Developer
If its specified, then it will be used to override the default "Startup"
bootstrapping command provided by the MVC Framework
Original issue reported on code.google.com by [email protected]
on 11 Apr 2010 at 3:30
maven build issue
Original issue reported on code.google.com by [email protected]
on 2 May 2010 at 1:33
Ability to scale with multiple openmobster nodes
Original issue reported on code.google.com by [email protected]
on 13 Mar 2011 at 3:07
Port the Mobile Cloud device side stack to the iPhone OS
Original issue reported on code.google.com by [email protected]
on 20 Jan 2010 at 10:30
add a couple of methods
byte[] getBinary and void setBinary(byte[])
for binary data like attachments, photos, etc
Original issue reported on code.google.com by [email protected]
on 7 Feb 2011 at 11:12
usually when parsing of moblet-app.xml file fails, it shows an empty string.
This should result in a better Error Dialog that exits the App instead of
having it run in a failed state
Original issue reported on code.google.com by [email protected]
on 2 Sep 2010 at 4:19
Sometimes if the RemoteCommand takes a while, the waiting dialog sticks
around for longer than user would feel comfortable. There needs to be
reasonable timeout to improve user experience.
Usually the issue occurs during socket timeouts. On Blackberry's the
default socket timeout is 2 minutes, which is quite high for the user to
wait on a RemoteCommand to report an error
Original issue reported on code.google.com by [email protected]
on 10 Apr 2010 at 3:51
On the Blackberry device, the MobileCloud module is installed as a system
module.
This is the runtime that all Moblet Apps rely on. If this is in a crashed
state for whatever reason (should rarely happen), a device re-boot is required.
This can be annoying. There needs to be an easy way from the CloudManager
to start this module.
Not sure if the BlackBerry OS allows this, but will have to research it further
Original issue reported on code.google.com by [email protected]
on 22 Apr 2010 at 5:08
Create an Activation Wizard to help with registration with the Cloud before
using Cloud services.
This is similar to the Android Cloud Manager APp except this one for now will
only have Activation functionality.
Due to the non-shared nature of the iPhone runtime, other features are
non-applicable.
Non-shared runtime is a huge PITA and IMO makes the iphone handicapped as an
Enterprise device
Original issue reported on code.google.com by [email protected]
on 28 Feb 2011 at 7:15
AppCreator produces a maven skeleton for every platform supported (Android and
BlackBerry) at this moment.
There needs to be a way for the developer to pick the platform of their
interest from the command line or as an option during project generation.
Original issue reported on code.google.com by [email protected]
on 18 Sep 2010 at 10:23
This will require integration with Apple's Push Service.
This should include Sync Push as well as Cloud-to-component push
Original issue reported on code.google.com by [email protected]
on 17 Feb 2011 at 3:15
This usually helps with efficiency during the development phase. The dev mode
cloud manager is very slim and does not have any way to reset channels.
The actual deploy time CloudManager is full featured, so this issue is not that
big a deal. If a channel seems stuck, it can be manually booted with the Cloud
Original issue reported on code.google.com by [email protected]
on 2 Sep 2010 at 4:24
The CloudManager should provide the user the ability to start and stop the
Push Daemon.
Original issue reported on code.google.com by [email protected]
on 22 Apr 2010 at 4:51
Log4J configuration needs to become more robust on the Cloud Side with
options of setting levels at atleast the package level
Also would be nice to have a single place to configure it
This comes out of the box when deployed in a JBoss instance (Production mode)
But this is also necessary in a standalone/development mode instance for
debugging purposes
Original issue reported on code.google.com by [email protected]
on 16 Apr 2010 at 2:18
To make sure the PushDaemon stays active in the most efficient manner.
The keepalive packets should be sent as late as possible but before the
socket times out.
While testing on actual Blackberry 8330 device, it was detected that this
window is 55 seconds even though the OS spec allows for a 2 minute timeout.
It is most likely a bug, but our Push Daemon should handle it regardless.
Hence, the PushDaemon configuration should be more dynamic and adjust the
keepalive interval dynamically based on device specific information
Original issue reported on code.google.com by [email protected]
on 22 Apr 2010 at 5:02
So that apps can be architected using HTML/Javascript, make the RPC service
available via Javascript
Original issue reported on code.google.com by [email protected]
on 20 Feb 2011 at 7:53
Add a sample that shows how to use the incoming method invocation information
on the SyncChannel to push 'MobileBeans' to specific devices/users.
See here for details:
http://groups.google.com/group/openmobster-users/browse_thread/thread/30c08b4fbc
afb74e/cdc67cca0b3b9521#cdc67cca0b3b9521
Original issue reported on code.google.com by [email protected]
on 24 Nov 2010 at 12:20
When the device back button is clicked, it exits the App. It should go back
if its not the Home screen
Original issue reported on code.google.com by [email protected]
on 10 Apr 2010 at 3:45
Clearly show if everything is running in ssl or non-ssl mode
Original issue reported on code.google.com by [email protected]
on 16 Apr 2010 at 3:47
The feature allows Push command initiated from the Cloud resulting in
invocation of a registered component on the device
Some applications:
* ask for current location of the connected device
* send cloud state updates (not sync updates). Sync updates are built-in to the
Sync component
* device management commands like remote wipe, remote lock, etc
Original issue reported on code.google.com by [email protected]
on 23 Feb 2011 at 11:39
the dev mode cloud manager has its configuration supplied in this
activation.properties file, so developer does not have to do a manual
activation during development phase.
One side effect is, the cloud server ip needs to be changed otherwise, device
cannot connect to the cloud.
Unfortunately localhost or 127.0.0.1 will not work since on the device, this
address points to itself, and not the computer where the emulator is running.
Original issue reported on code.google.com by [email protected]
on 2 Sep 2010 at 4:28
The Maven files need to be modified to support the new sdk layout.
tools should be platform-tools, etc
Original issue reported on code.google.com by [email protected]
on 18 Feb 2011 at 8:39
As an optional configuration, ability to store local sync channel data in an
encrypted format.
The default would be no encrytion for performance reasons
Original issue reported on code.google.com by [email protected]
on 13 Mar 2011 at 3:10
Update Readme docs/Appropriate Wiki docs to include getting started with iPhone
Original issue reported on code.google.com by [email protected]
on 28 Feb 2011 at 7:13
So far everything is tested on 4.3.0 and 4.5.0 simulator environment.
Next release should include a fully tested codebase on an actual BlackBerry
device
Original issue reported on code.google.com by [email protected]
on 10 Apr 2010 at 3:34
The RPC module supports synchronous invocations only. This needs the
asynchronous mode of operation as well
Original issue reported on code.google.com by [email protected]
on 20 Jan 2010 at 10:23
The DevMode CloudManager connects to the Cloud using a confiured IP of
192.168.1.102.
This can be changed using the "Change Cloud IP" option in the Menu.
Just the failure message is non-descriptive...It needs to point to this option
or bring up the dialog upon failure
Original issue reported on code.google.com by [email protected]
on 25 Feb 2011 at 2:11
So that Apps can be architected using HTML/Javascript, make the Sync beans
available via Javascript
Original issue reported on code.google.com by [email protected]
on 20 Feb 2011 at 7:51
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.