davebalmer / jo Goto Github PK

joStack needs to clear out all child nodes from its DOM tree except for the current view, which it does after any CSS transitions defined in the app css.

Currently, uses 800ms fixed timeout, which is "ok" for a default, but joStack should be hook into the transition end event for the views if available.

Please add tags for all the releases so far to the git repo.

(And think about adding a Flattr button to the project so that people can throw some gratitude your way).

The keyword "screen" can't be overwritten on Safari 5.0 or Chrome 6.0 (OSX). So the introduction tutorials run in a standard browser throw an undefined error stating "alert" doesn't exist. Changing the variable name to jScreen solved the issue for me ;)

Hi,
Jo framework's demo has been listed on http://frameworkdemos.com
It's a free service to list all popular frameworks' demos so that users can try them on their mobile devices without looking for links around the internet.

Could you verify it and if possible, update Jo's demo source code at:
https://github.com/ngduc/framework-demos

Please let me know if there is any problem with my setup. Thanks.
Regards,
Duc

This is a weird iOS only thing. Dragging any other element from inside a joScroller works as expected, but an input field cases the main browser document to also drag. Haven't tested in a PhoneGap project yet, expect the same.

Hi,

You framework is really awesome !! However, I see a big issue with your scroller into the Palm WebOS browser (1.4.5 and 2.0 beta).

WebOS overrides the scroll management. So, if you have some iframes or some elements with overflow: scroll, you can scroll in these. I try for another application to do a coverflow with finger motion. But WebOS raises mouse events a mouse click (mousedown is called only when you click...). In WebOS application, the mouse events are correclty called.

I think the only way will be to use the touch events (touchstart, touchmove ....) that Webkit provides.

What do you think ?

Regards

Julien

It was cute for a while, but it's odd looking and doesn't perform well on some platforms.

Since joDoc is now its own separate project, the files here can go bye-bye.

Windows 7 Professional - Service Pack 1

�

Right now, joCard.activate() is only called when a card is first pushed onto a stack, and deactivate() is only called when it's popped. I'd prefer for deactivate() to be called when another card is pushed on top of it, and then activated again when it becomes the top card again. Alternately, there could be new event types that get fired when a card isn't on top anymore. I'm thinking of the difference between deactivate() and cleanup() in webOS.

(I'm basically constructing my Jo app in a webOSish way, where cards stay on the stack, but should have a deactivate() method that is called so that the card can stop any polling or animations that they do while active. I can think of a few workarounds, but they tend to break the stack metaphor and none of them are particularly elegant.)

Supplimental -> Supplemental in README

http://github.com/lakinwecker/jo/commit/04e4634ac95ed45f14e2179a4790b556fe49d7f0

Not everything is chainable and it is not obvious what is and what is not.

For example, the following does not work (returns undefined):

    var navbar = new joNavbar().setStack(stack);
    var stack = new joStackScroller().push( card );

looks like input is oversized.
Check here http://sweetr.ru/clck.html

I'm trying to use jo for webOS app development. I had some problems with misaligned CSS styling. I don't know if I'm the only one, but I found the fix for this problem:

I found that the following styling, on all elements, needs to be added to fix it:

"background-origin: border-box; "

however, it was sufficient to add it to the global, joElement styling (right after the body styling)
PLUS adding it to the styling of "jotoggle > * "

also, jopopup is missing in the global joElement styling list

1. pull up the test.html app
2. click the Login menu item
3. hit ESC quickly
4. observe the new view AND the home view both clear out, leaving a blank screen

joLawn is mentioned in the documentation, but it seems there are no references to it... is it still in the works?

Reported by Dion, will check into it.

Oops. :)

I found that the build scripts, both the shell script and the Windows batch file, omit ui/scrollbar.js and ui/image.js. Is this on purpose?

Need to smarten up the Makefiles to remove the requirement if it's not installed.

For example, I have an object with elements - here I am making exemplars of elements and subscribe for theirs events.
var tabBar = new joTabBar([
{label: ' Account'},
{label: ' Settings'} no settings page yet
]);
var elements = {
'mainPageFooter' : new joFooter(tabBar),
'anotherPageFooter' : new joFooter([someButton, tabBar]),
};

Now if I willpush joCard which contains elements['anotherPageFooter' ] to stack- allwill be ok. But if I will am push joCard with mainPageFooter the joFooter element will be empty.

same problem when using stack.pop() - previous pages have empty joFooter. So last joFooter rendering empty joFooters which created before.

Incorrect use, tsk tsk. Should be clarified in the docs, thanks @kevinmarks!

I've recently updated the docs, but some of them are probably still out of date. Would love getting some feedback if there are any examples that don't work, especially.

Shouldn't it be HTML5?

To reproduce the issue please do the following:

1. Open the page http://joapp.com/live/samples/test.html in Safari on iPhone with iOS6 (on iOS 4.2.1 issue was also reproduced)
2. Choose "Form widgets"
3. Choose input field "Username" (default text - 'jo').
4. When cursor appears in the field and keyboard appears - scroll the page up or down - the field moves but cursor stays.

This would allow you to preform an action when the joStack is done animating( CSS transition) the current screen. I created a new event (animateDoneEvent) in my fork of jo for this purpose.

I use it to re-enable the back button so my IOS users can not click an the back button during a screen transition.

this.stack.animateDoneEvent.subscribe( function(){
console.debug("animate done enable back");
MobileApp.nav.back.enable();
});

Mostly prior to 2.1 and slower devices. Not sure how to get around this, but it would be nice to get a fix in there, or at least build a "native scroller" subclass of joStackScroller which uses an approach similar to jQuery Mobile's "floating toolbars".

joDOM should be used instead of joDom in js/ui/busy.js

the screen width of the demo app on my Android device is wrong.
This helps:
<meta name="viewport" content="user-scalable=no, width=device-width" >

Also trying to push an item in the list does not really work well, I can push and an item gets selected, but it's always the wrong one, and I can't even push the 'done' button..

Jo looks very promising though, I like the concepts!

The refactoring from the old Grrok version isn't working well yet. Considering baking an auto-scroll feature into all joContainer objects and avoiding this extra class.

The scrolling area touch-event hack is necessary on iOS and Android<2.3, but many devices support CSS position: fixed.

In my own testing, web applications have much better performance characteristics for content in the scrolling pane. I've noticed that the web forms kitchen-sink widgets' animations are smoother when compared to the touch-event hacked technique.

This might be a solution to:
#22

Users want to be able to drag & drop items in lists to reorder them, and possibly drag to other lists. This is a pretty big undertaking, definitely could use some help to get it in the features sooner than later.

Flat design theme based on less.js customizations. Should be easy to change colors, rounding, sizing and spacing. Also add a glyph font and remove dependency on images (which don't scale too easily).

Is this supported/planned?
Any pointers?

Testing joScroller vs. native; native is generally smoother. Detect Tizen and use native.

Seeing this in the new Flattery theme. Should be a quick fix.

Im trying to disable a already instantiated joButton:

// function...
this.addButton = new joButton("Add").selectEvent.subscribe(this.pushDetail, this),
// later
this.addButton.disable();

The button looks like a disabled one, but I can click it and the function gets called...

Context: Android HTML5 App using PhoneGap (versions: 1.6.0, 1.8.0 and 2.0.0rc1)
Issue is only reproducible on specific devices. verified issue on HP Touchpad running Cyanogen7, issue also reported on jewel & Samsung Galaxy S2 (GT-I9100).

Hints:
testing on PC browser did not trigger issue.
In a standard US Keyboard '9' and '(' are the same physical key.
Changing the soft keyboard app on android device did not fix issue.

My workaround:
Removed all code from JoFramework setting attribute editablecontent.

Would it be possible to include jsdocs/ within the git repo so makedoc could work ootb?

../joDoc/jodoc --template jodocs/singletemplate.html ... > jodocs/docs/index.html

Maybe even called htdocs/ so it's obvious it's meant to be a live website. I'm interested in creating a simple static nodejs server that could show the docs from localhost:8000.

Received some feedback that it would be nice to be able to have the framework create UI elements in the DOM with different names. Adding a config method which lets you set the tag names for any UI class in the JS.

In Tizen, window.load fires before <script> tags in the document body are actually loaded.

There is an issue with joNavbar that prevent it from being extended (subclassed).

The listener for the back button is a function called back. But in the constructor function, it is replaced by the back property which hold the reference to the joBackButton.

The code works because when adding the event listener, the reference to the function has not be called yet, but this cause issues when extending the joNavbar.

The listener should be named goBack instead of back (or any other name that is not back).

The jo docs currently use frames. This causes great pains for all!

Comments?

Something is blocking touch events on Tizen.

Sometimes takes a second go to cause this. Will contact Chrome team and see if they can reproduce. If you run up against it, downgrade to latest stable release and retest your app.

JoStackScroller.back() actually calls joStack.forward()

Details:
The following code:

joStack.prototype.forward.call(this);

Should be:
joStack.prototype.back.call(this);

"aluminum.css" has become sort of a mess. The files will be changed to have a "jo.css" file, with optional "ios.css", "webos.css", "mozilla.css" files that have tweaks (especially to default transitions). This should make it easier to skin, because the default CSS will have just enough to make the widgets work, with no significant visual styling.

The graphic doesn't stretch correctly, and webOS doesn't (yet) support gradients. Possibly disable the background image entirely in webos.css for now...?