jasig / umobile-app-phonegap Goto Github PK

Documentation located at: https://wiki.jasig.org/display/UPC/uMobile+PhoneGap+Exploration

• Overview of project & code.
• Overview of build

Provide up to date screenshots, instructions and verify the setup process.

Hi,

It seems that if you set something different than mockLogin and you try to run the uMobile on a browser it never initialize.

After some investigations I saw this : https://github.com/Jasig/umobile-app-phonegap/blob/master/src/js/src/app.js#L329

The problem is that deviceready is only available on phonegap and for some developments purpose it can be helpful to run uMobile on a web browser (without phonegap) with setting different than mockLogin.

May this be changed ?

casLogin appears to be defective. I had to modify my local CAS server to allow callbacks to 'http' urls (which is fine) and with that change , once I login to uMobile as admin/admin, for some reason the JS code doesn't recognize the uid and always returns 'guest' even though CAS shows that I have successfully logged in and validated the ticket:

uMobile.js:

• Looked at CredentialsView in umobile.js and the 'admin' username appears to correctly be saved into the model.

authentication.js;casLogin():

• On the success callback, the 'credentials.attributes.username' returns admin. However, 'data.user' returns 'guest'?

So it looks like there's a mismatch between credentials model/view where the uid isn't saved into local storage, or something like that...

v1.8.4

Update the documentation for the current build. Targets have changed

Version: 2.4 as of this request

In preparing for the 2013 Apereo Conference, some minor adjustments to the theme layer were implemented. This task will captures those minor changes.

A lot of plugins don't work well with regex support. Custom ones may need to be written or we could take a look at require-js which may done some of resource filtering.

Would be beneficial to have a CI tool build the code on commits, something like Travis CI, etc.

Matt might have better recommendations or alternatives.

This would be a good question for the community. What tool should we use? Is this the right approach?

• Move filters to the config directory.
• Move yuidoc.json to docs/yuidoc.json.
• Update grunt build with new file locations.
• Change environment flag from iphone to ios.
• Updated cordova-iphone.js to cordova-ios.js.

This only includes uMobile JS code and not frameworks at this time. Update all HTML accordingly.

In the context of this project, the fluid library should be removed from the current implementation and replaced with the jQuery widget factory or any existing widget factory provided by jQuery mobile. The goal is too simplify the code base for greater adoption. Since fluid is only used for a single widget removing it makes sense. It reduces the amount of technologies a developer needs to understand on the front end to the jQuery ecosystem.

Documentation located at: https://wiki.jasig.org/display/UPC/uMobile+PhoneGap+Exploration

...using ph-pages branch. This is dependent on #8

Then, have the build populate the target directory that would then include production-ready code appropriate for the environment.

The target directory may essentially be the www directory, per android spec.

Would be beneficial to hit android docs and see if there's a standard structure/format/tool/approach to follow.

During preparation for the 2013 Apereo conference we created android and iOS based uMobile icons and screenshots. These icons and screenshots can be used in conjunction with PhoneGap 2.5. The icons and screenshots provided can be used as a starting point for things like splash screens or launcher icons.

Rendering uMobile under local authentication with "admin/admin". The icon urls that are returrned back in the JSON payload are missing from the codebase.

A number of mock html pages are now simply duplicates of calendar or are empty. need to provide appropriate content.

Branch: https://github.com/Jasig/umobile-app-phonegap/tree/UPG-10

Ideas and suggestions we can discuss:

• Build process should support two directories. A source (src) directory where all our uncompressed code lives and a public (www) directory where all our production ready code gets pushed.
• Automate which SessionTracker.js or SessionTrackerMock.js (formally mobile-plugin-android.js & mobile-plugin-web.js ) file gets added to the build. This can be done with config.js files that get imported into our grunt build.
• Automate which cordova-iphone.js or cordova-android.js file gets added to the build. This can be done with config.js files that get imported into our grunt build.
• Build process would ideally cover the following:
  • Linting JavaScript files.
  • Compile css using less framework ( *Not implemented )
  • Execute JavaScript unit tests with Jasmine and PhantomJS on the command-line ( *Not implemented )
  • Collect, optimize and concatenate JavaScript libraries and source files.
  • Copy production-ready resources to www directory.

Right now, only one build is allowed per the getCordova() call.

While i was testing uMobile i found something a bit weird and I couldn't find where it comes from.

https://github.com/jasig/umobile-app-phonegap/blob/master/src/js/src/app.js#L143

I can't find any reference to config.uPortalServerUrl in the uMobile project... and it generates an URL which looks like undefined/path/to/img.png

Then I changed config.uPortalServerUrl to config.uMobileServerUrl, Am I right or did I miss something ? See df9d03d

Redefinning variable is disallowed in strict mode. Be sure to be in fully compliant ES5 environment.
The "use strict" directive is only recognized at the top of a script or function, which makes it sensitive to script concatenation.
So which way to go?

• Never concatenate strict files an nonstrict files.
• Concatenate files by wrapping their bodies in immediatly invocked function expressions
  //file01.js
  (function() {
  "use strict";
  function foo() {
  // ...
  }
  // ...
  })();

//file02.js no strictmode
(function() {
function foo() {
var arg = [];
// ...
}
// ...
})();

The jQuery mobile theme does not fail to load but it fails to apply itself to the view. This might be a bug with the version of the library that we are using. Upgrading may solve this concern.

Setup information has been added to wiki:
https://wiki.jasig.org/display/UPC/Setting+up+uMobile+PhoneGap+for+HTML5-only+Development

Currently, the HTML5 application does not notify the user when an error results from a failed request. The application also does not update the UI in anyway in the event a request for Data fails. It might not be appropriate to notify the user in all cases but we should discuss these scenarios to give the best user experience possible.

This would be a good question for the community. What approach should be taken?

It is possible to precompile templates. This will result in a smaller required runtime library and significant savings from not having to compile the template in the browser. This can be especially important when working with mobile devices. It is also possible to automate the precompiling of templates with node.js and grunt. Precompiling templates can be another grunt task added to our build.

http://handlebarsjs.com/

This would be a good question for the community. Should we take this approach?