appverse/appverse-web-html5-core

Appverse Web Client Side core module based on HTML5 and Java Script

appverse-web-html5-core's Issues

[Question] How can we improve the Appverse?

Hey guys, I just started using Appverse here in GFT and I got some stuff that probably could be improved.

I know that maybe you already had a kind of roadmap of improvements, but I´m using for few weeks and some stuff that I saw we can improve step by step.

Possible improvements

• Even though we're using Bootstrap, I´m not sure if the way we're using it's correct. Maybe we could create a based styleguide with few components that we can share and import only the necessary things of Bootstrap instead all components.
• Another thing that maybe could be a great is to define a based folder structure to styles and components following directives like SMACSS, BEM, OOCSS or even few pieces of each one. This way we can really improve the project along the time and maybe in the future even use more components made by ourselves then bootstrap stuff.
• Replace Grunt by Gulp. I know that Grunt is an amazing task runner, but by migrating to Gulp we can use convention instead of configuration and also improve our tasks and build process. Webpack is an option as well, but I personally prefer Gulp instead.
• Remove Ionic from the web version. Why are we loading Ionic dependencies if the project is to the web? I totally support PWA, but I don't think that load unnecessary stuff that probably isn't used in all projects is a good approach. Let's try to keep things simple.
• Define useful modules/services that could help us during the development process or even use some opensource solution.

Nice to Have

• Add ES6 support with Babel and Browserify (With polyfills, and even ES7 support like async/await that it's in stage-3 now).
• Change JSHint to ESLint and start using Airbnb code standard.
• Do we really need Lodash?

PS: Have you ever heard about FountainJS?

That's it, let the discussion begin. 🏇 💨

Conflict with angular-translate and appverse-translate

Hello,

We've been using Appverse as bootstrap solution in a client's HTML5 and SPA architecture, and we received internal issues regarding the performance of the translation module (appverse-translation).

The developers tried to upgrade angular-translate by themselves but reported conflicts with the appverse-translate module:

function decorateTranslateDirective($delegate, translateFilter) {

        // Get the original directive and its linking function
        var directive = $delegate[0];
        var originalLinkFunction = directive.link;

In the latest versions of angular-translate handles the directive.link internally in the compile function of itself, so originalLinkFunction becomes undefined.

How this could be fixed so we can upgrade properly the angular-translate module of our applications without conflict with your library?

Thank you,
Arnau.