Skip to content

Test with WebWorks 2.0 changes #993

Closed
tneil opened this Issue Dec 3, 2013 · 16 comments

7 participants

@tneil
Open Source Projects member
tneil commented Dec 3, 2013

Double check the latest bbUI with the WebWorks 2.0 API updates... It may just be as simple as changing the sample to listen for the cordovaready event instead of the webworksready event.

@glasspear
Open Source Projects member

The content menu extension will probably need to be ported to Cordova as well, correct?

@sh2sg
sh2sg commented Dec 4, 2013

Code changes should be minimal I think only need to replace webworksready event and chrome/webworks.js

But what is the benefit of using WebWorks 2.0? Performance improvement? Will it get smoother context menu after changed to WebwWorks 2.0?

One thing I don't like WebWorks 2.0 is, I could be wrong because I didn't try it, the signing/compiling process is completely changed, instead of adding features in config.xml, you have to manually specify each feature/plugin in command line? This could be very tedious.

@tneil
Open Source Projects member
tneil commented Dec 5, 2013

The benefit is for overall cross platform distribution of your application.. You can now create your application and simply use the standard Cordova compiling capability to hit multiple different OS platforms.

@splatterb0y

@tneil:
I guess that a pretty flimsy answer because apps made with bbUI.js won't run on other OS at this moment in time. So we have to develop a different ui for other mobile operating systems or abandon bbUI.js for developing cross platform applications and use shit like jQuery Mobile for BB10.

To me it's not a matter of installing plugins or managing files for webworks. Most of the time is spent creating the gui. So we can't hit multiple diffent OS platforms if we want to delivery the best user experience for BB10 with bbUI.js.

@tneil
Open Source Projects member
tneil commented Dec 7, 2013

Hi Christian,

My answer wasn't meant to be bbUI specific. WebWorks 2.0 and bbUI serve two separate purposes. WebWorks is to align with the cross platform capabilities of Cordova and bbUI is to provide a BlackBerry specific user experience.

@splatterb0y

@tneil
Sorry I did not want to be mean or sound disrespectful in any way. I hope you get my point anyway, you know I am a litte rough when it comes to communication but I'm not rough on purpose.

I try to explain what I try to point out:
Most of the time is spent on creating an UI and if you focus on the BB10 platform you need to use bbUI.js which is not cross platform. So to be really cross platform you either need the developer to use something else then bbUI.js, which in my opinion is bad for the BB10 OR they have to focus on BB10 and they don't have any cross platform capabilities with bbUI.js on other platforms and they need to develop a second UI for other platforms. (Thats the approach I have taken.)

I'm just worried that web developers will abandon bbUI.js for something that is cross platform and the quality of web apps for BB10 will suffer. I support BB from heart and I love to have the opportunity to develop for this great platform. If I spent 90% on the UI and 10% to setup a project with all the plugins it's no problem for me to setup a cordova project beside a regular webworks 1.0 project. So maybe you understand that I would like to have bbUI.js cross platform too. Maybe with a "bb10 design in white" or just the layout with an additional stylesheet for cross platforms so we could have a great bb10 app and bbui.js cross platform which is mostly white or something on other platforms. Developers could reuse the structure of their bbUI.js app and layouts and only need to add some styling to the app instead of developing a completely new UI for other platforms.

I hope you got my point. If not and you want to get some more clarification on this, feel free to drop me a mail or reach out to me on twitter. :)

@johannjacobsohn

To mitigate this problem I've written enyo-bbui which bridges EnyoJS and bbUI.js. Using this lib enyo apps can be written once and deployed with bbUI for Blackberry and (eg.) onyx for other platforms. It has been featured on the enyojs blog and is already quite usable but requires additional testing.

@sh2sg
sh2sg commented Dec 9, 2013

A bbUI app will be benefited by WebWorks 2.0/Cordova because it can be deployed on other platforms? Then how can we use BB10's UI on iOS or Android or WP?

My opinion,
Cordova is good for cross platform, yes.
Cordova + bbUI is good for cross platform, no.

Since here is the bbUI repository, a toolkit that completely follows BB10 system UI guidelines and looks, I don't expect bbUI will be adapted to support iOS or Android or WP looks, make bbUI to be compatible with WebWorks 2.0 does not look necessary to me, unless WebWorks 2.0 does come with some performance improvements.

@andreyavram

bbui.js should work out of the box on any platform. I've already used it on other platforms, but I had to modify the core of it. BB10 jQuery Mobile works on any platform, but is slow as hell...
I don't think bbUI should be restricted to BB phones, because of the same reason that BB chose to port BBM on Android and iOS using the BB native-like UI.
I will surely abandon bbUI.js for other UI frameworks if it won't work cross-platform, it's simply counter productive to recreate and rethink my UI on every platform.

@splatterb0y

@sh2sg: BBM looks the same on all platforms and you can still transfer the layout to other OSes with a different color style or something and it would still be pretty suitable.

@andreyavram
Yes. jQM is crap and the bb10 theme is not even far as good as bbUI.js. I guess the performance will heavily improve with the release of jQm 1.4 but it's still .... crap. I like the way things work in bbUI.js much more. It's cleaner and faster.

@sh2sg
sh2sg commented Dec 9, 2013

@splatterb0y I know it can be used on other platform but it looks a bit strange doesn't it? Every platform has its own UI guidelines and app should respect the guidelines.

What I meant by "using bbUI on other platforms" is referring to switch UI/theme when the app runs on Android or iOS or WP, that means bbUI is like a cross-platform UI toolkit, not just for BB10, but I don't think @tneil has such plan.

@splatterb0y

@sh2sg Thats exactly the point if webworks is cross platform why not bbUI? Why not make it easy for developers to work primarily for bbUI.js and have no problems with rewriting the complete ui.

Since nearly all browser of mobiles os are based on webkit I guess it's not a big problem to support iOS and Android too if you replace all calls to blackberry related functions, which should be aligned with the WebWorks 2.0 release because afaik many API have changed from blackberry to navigator.

@andreyavram

@splatterb0y That's exactly my point of view, also.

@T-M-C
T-M-C commented Dec 11, 2013

+1
bbui crossplattform would be a good thing!

@tneil
Open Source Projects member
tneil commented Dec 12, 2013

Lots of great feedback on this thread that we'll definitely take into consideration.. not making any promises though :o)

@tneil
Open Source Projects member
tneil commented Apr 25, 2014

Ok.. so I've been testing this in the 2.0 branch. The sample has been updated along with the proper plug-ins.

The only thing that is left is getting the context menu to work properly. We already have issue #996 covering this, so I'm going to close this issue.

@tneil tneil closed this Apr 25, 2014
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.