meteoric124 / meteoric Goto Github PK

This is a good idea while there are still small user base.

Hi @JoeyAndres ,
When we use only one side menu (right or left) other side tap and pull must be disable to prevent white extra partial space.
See below Images:

Please say for extra detail needs.

$ionicHistory delegate.

Hi,

i'm trying to use this meteoric branch at the moment, and after getting around some other issues I'm working on, I noticed that the content always "slides in" from the right on the first load of any page, no matter if it's a subpage or the index page of the whole app.

See it here: http://jandres-ionic.meteor.com/ - just press reload and see the content slide in from the right.

I think that's probably to transition nicely between pages, but is it possible to disable this somehow for the first load?

A workaround would be fine for now, or maybe any information about where this is coming from in the code exactly.

Thanks and best wishes!

Currently, ionScroll can scroll in one axis at a time. This is due to the default of iscroll (backend of ionScroll).

Hi @JoeyAndres,
I dive in meteoric and try to create demo application based on your component to find bugs and report here and for more clear refer to codes. This is my demo app repository:
https://github.com/cyclops24/meteoric24-demo

My first issue that I find in meteoric is when I use simple collection each in template it's worked well and show in web mode but run on real android device (with android 4.2.1) show me a white view without side menu icon or template each result.
Show this issue in two image below.

Good result on web:

Bad result on mobile device:

As you see in above images header title text and side menu and also each content not visible in mobile this is my template code:

<template name="index">

    {{#contentFor "headerTitle"}}
        <h1 class="title">App Title</h1>
        <button class="button button-clear pull-right" data-ion-menu-toggle="right">
            {{> ionIcon icon='navicon'}}
        </button>
    {{/contentFor}}

    {{#ionView}}
        {{#ionContent}}
            <div class="padding">
                <ul>
                    {{# each messages }}
                        <li>{{title}}</li>
                    {{/each}}
                </ul>
            </div>
        {{/ionContent}}
    {{/ionView}}

</template>

(full source available in my demo repository)

Due to the removal of all non-ionic controllers, ionSlideBox was broken. Utilize the ionic controllers and make this work again.

Integrate ionic's controllers/utils/views libraries. utils/views are framework independent (they don't care if you are in angular), controller's on the other hand need some code change. All of these are essential so we only have to reinvent the platform dependent parts. #32

Current side menu is too primitive. Although snapper js was modified to be more consistent, there are still many unimplemented features. Especially wrt to 1.2.4

Hi @JoeyAndres,
I try to use {{>ionNavBackButton}} with empty text and try to use like this:
{{>ionNavBackButton text=""}}
But this component add default value for text property (Back) but I think it's not good because many times I need back button without text (only icon).
I found and see this default value set on this file I come here to suggest this to you.

Hi @JoeyAndres ,
I test your demo all things worked well but Side Menu not working for me. (Side Menu worked well for me on meteoric demo version)
I try using firefox and chromium.

See scrollController.js in v1.2.4 tag of ionic repo. It contains _setRefresher which is called when pulling the top of the list. Would be nice to implement this.

Do investigation in what context this is used.

Hi @JoeyAndres ,
First excuse me if I post many issue. I see that transition on route change (page change animation) not working now.
You can compare this and this.

With ionic 1.1.1, we need to update ionRadio so that it works well with also 1.1.1 styling.

Hi,
First thanks for maintaining this awesome package and continue mobile development with blaze.
I want to switch to your version but saw that you are using another version of ionic-scss package.
I suggest that update GUIDE.md and add new notes about your version setup.

Thanks again @JoeyAndres.

Hi @JoeyAndres ,
I have same issue with this stackoverflow question when use ionic in meteor.
In the past when I used ionic alone I didn't have this issue.

When app runs on the real device some text blurred and unclear line above stackoverflow question image.
Can you any idea about this?

Hi @JoeyAndres ,
Form elements OK on web but when I test in on device radio element view is buggy.
See below image for more info:

This is annoying as hell. Why not just "class".

Abstract away from contentFor

Atm, METEORIC.PLATFORM are in utility.js, which should be in its own folder.

FlowRouter is now the recommended router by MDG and IronRouter has limited support going forward. Therefore, it would be awesome if you could integrate in support for FlowRouter. It looks like there is already a port to FlowRouter https://github.com/txs/meteor-wecare-ionic-flow/ and this was previously discussed meteoric#199

I'd be willing to donate a small $ amount to make it happen and have you support it going forward. You could probably combine efforts with @txs.

Hi @JoeyAndres,
I success to pass _id through route parameter for below route:

this.route('category', {path: '/category/:_id', controller: 'CategoryController'});

This is my html:

{{#each categories}}
                {{#ionItem path="category" class="item-icon-left item-icon-right" }}
                    {{#ionItemContent}}
                        {{> ionIcon icon="ios-arrow-left"}}
                        {{../title}}
                        <p>{{../description}}</p>
                        {{> ionIcon icon="ios-checkmark" class="balanced"}}
                        <span class="badge badge-assertive">0</span>
                    {{/ionItemContent}}
                {{/ionItem}}
            {{/each}}

But who to pass title parameter for below route:

this.route('category', {path: '/category/:_id/:title', controller: 'CategoryController'});

I guess now meteoric only support _id (this specific name) because I didn't say in ionItem (I specify only path {{#ionItem path="category"}}) but meteoric automatically pass _id to route, but how we can pass other route parameter. Is it possible with ionItem?

Hi @JoeyAndres ,
I update last version of demo and run on my android device and I has new issue. On the index route when I tap and pull list vertically left SideMenu opened for me. This bug happens in this version and all things OK on previous version.

A bunch of helper function for Cucumber so that developers can implement their own "acceptance testing" faster.

Hi @JoeyAndres ,
When I build your demo app and run it on a real android device spinner freeze and no animation available.
I talked about this page:
http://jandres-ionic.meteor.com/spinner

Right now it is literally "single page". EVERYTHING is loaded in a single page. This is abusing mdg's server.

Utilize caching to speed things up.

I find myself using () => {} for a noop function. This should be abstracted away to reduce thinking time, especially for new developers.

Hi,
Do you have any plan to upgrade meteor-ionic to ionic2 ?
ionic 2 has beautiful material design and many other new things.

Hi @JoeyAndres ,
I test demo app on a android device and go to loading page but spinner animation and icons not shown for me after that I test online version and see that issue also there.

Hi, sorry, but i'm curious: Why did you get rid of "ionIcon"? Is there an alternative we should be using?

Hi @JoeyAndres,
Backdrop not working after update.

iontab is clunky as hell. Js errors pop here and there.

Add a meteoric/meteor-ionic migration guide in the documentation website.

Make it on par or better than http://ionicframework.com/docs/api/directive/ionContent/

This will probably contain multiple subtask since many things are below this thing.

Hi @JoeyAndres ,
I used Side Menu in all of my project one other issue that exist in meteoric version (and ok on ionic version) is when you tap and pull page to a side and pull more than side menu width an extra space occur between content and side menu and a small horizontal scroll shown below side menu. See below image for more info:

Hi @JoeyAndres,
I found two extra scroll.
One in content of all page like this:

And another in SideMenu like this:

Hi @JoeyAndres ,
1- Please go to this page: http://jandres-ionic.meteor.com/tabs/one from demo index.
2- Then back
3- This causes below error: (on firebug or developer console)

Exception from Tracker afterFlush function:
d7eb804a9c0226fcaecc891d990c8f7533514e97.js?meteor_js_resource=true:5 TypeError: Cannot read property 'enable' of null
    at Object.R.enable (d7eb804a9c0226fcaecc891d990c8f7533514e97.js?meteor_js_resource=true:193)
    at null.<anonymous> (d7eb804a9c0226fcaecc891d990c8f7533514e97.js?meteor_js_resource=true:191)
    at d7eb804a9c0226fcaecc891d990c8f7533514e97.js?meteor_js_resource=true:93
    at Function.e._withTemplateInstanceFunc (d7eb804a9c0226fcaecc891d990c8f7533514e97.js?meteor_js_resource=true:94)
    at d7eb804a9c0226fcaecc891d990c8f7533514e97.js?meteor_js_resource=true:93
    at Object.d._withCurrentView (d7eb804a9c0226fcaecc891d990c8f7533514e97.js?meteor_js_resource=true:93)
    at l (d7eb804a9c0226fcaecc891d990c8f7533514e97.js?meteor_js_resource=true:93)
    at t.Computation._compute (d7eb804a9c0226fcaecc891d990c8f7533514e97.js?meteor_js_resource=true:33)
    at new t.Computation (d7eb804a9c0226fcaecc891d990c8f7533514e97.js?meteor_js_resource=true:33)
    at Object.t.autorun (d7eb804a9c0226fcaecc891d990c8f7533514e97.js?meteor_js_resource=true:33)

I test another code and if layout doesn't have sideMenu this error happens. For example with a layout like this:

<template name="simpleLayout">
    {{#ionBody}}
        {{#ionView}}
            {{> yield}}
        {{/ionView}}
    {{/ionBody}}
</template>

Might be related to #26 issue in the backlog, or just some unnecessary js processing.

ionic have events.js. By a quick glance it seems to coalesce all events in one place, making it easier to utilize by other developers. Investigate and implement this.