2) in the gallery it should be written which version of iui the example sites are using
3) wrong link
The visit website button has a wrong link here:
http://www.iui-js.org/powered-by/index.html?id=mref
Von meinem iDingens gesendet...
> 1) I dont find a link to the kitchensink examples (stage or demo site of iui) on the website. I would expect it on the page "demo" (or if not there on the gallery)
good point.
the reason is did this is because it's a mobile web framework, so it might be broken on desktop browser, so no reason to access it from desktop.
But since it actually works on most desktop browser
, and people may come from a mobile device, it would make sense to have a "live demo" link... at least in the demo section , and next to the download button on the homepage
>
> 2) in the gallery it should be written which version of iui the example sites are using
yep, good idea too
> 3) wrong link
>
> The visit website button has a wrong link here:
> http://www.iui-js.org/powered-by/index.html?id=mref
good catch!
>
> Von meinem iDingens gesendet...
>
> --
> You received this message because you are subscribed to the Google Groups "iui-developers" group.
> To post to this group, send email to iui-dev...@googlegroups.com.
> To unsubscribe from this group, send email to iui-developer...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/iui-developers?hl=en.
>
These are both great suggestions. Would someone please add them to the
Issues DB with the label "Component-Website" so they'll be in the
official "to do" list for the website:
http://code.google.com/p/iui/issues/list?q=label:Component-Website
It would also be nice if someone developed a single demo app (single
HTML page) that is a "kitchen sink" demo. A starting point would be
combining a bunch of the apps in the test directory (though some of the
tests have too many purely test cases, that aren't right for a Kitchen
Sink-style demo)
> 3) wrong link
>
> The visit website button has a wrong link here:
>
> http://www.iui-js.org/powered-by/index.html?id=mref
Fixed:
http://www.iui-js.org/powered-by/index.html?id=mref
-- Sean
On 13 avr. 2012, at 01:07 PM, Michael nietzold <niet...@gmail.com> wrote:good point.
> 1) I dont find a link to the kitchensink examples (stage or demo site of iui) on the website. I would expect it on the page "demo" (or if not there on the gallery)
the reason is did this is because it's a mobile web framework, so it might be broken on desktop browser, so no reason to access it from desktop.
But since it actually works on most desktop browser
, and people may come from a mobile device, it would make sense to have a "live demo" link... at least in the demo section , and next to the download button on the homepage
I've set the tags, etc.
-- Sean
Is this what we are talking about?
http://remigrumeau-iui-dev.googlecode.com/git/web-app/test/complete.html
Or are you talking about a contact, notes or photos?
Remi
Yes. That is exactly what I'm talking about. (Except, of course, that
it shouldn't have features that aren't supported in the corresponding
released version of iUI -- like "hidebackbutton", etc.)
-- Sean
Remi
On 16 avr. 2012, at 01:23 AM, Sean Gilligan <se...@msgilligan.com> wrote:
I don't think so. Can you show me where it is in "master"?
-- Sean
Remi
Haha! Well, whaddya'know...
http://code.google.com/p/iui/source/browse/web-app/iui/iui.js#852
I had to check when that code was added and it's been there since 0.12!
Personally, I'd like to deprecate that feature at some point. It's just
too much of a special case feature. We need a general way to change the
toolbar buttons on a view-by-view basis, not a bunch of special case
LOCs (lines-of-code) like that. I definitely don't want to remove it now
because we don't have the more generic way, it's not causing any bugs
and I want to get 0.4 out the door. After we add a more general way of
setting buttons we should probably remove it.
A couple quick, related thoughts:
1) Is there a way to hide the back button with TbBMod?
2) I had an idea for a more generic solution: we could put a classname
somewhere on each view and when that view becomes active, apply that
class to the .toolbar div. Users could then use custom CSS to show/hide
buttons based upon the class. (I'm not sure this a *good* idea, it's
just an idea)
-- Sean
My other objection, btw, is that history.go(-1) is not the right way
implement a "go back" button. If you load the view via bookmark, this
won't work.
Remember, the back button and browser history are two different things.
A better solution would be to use iui.goBack() or for us to create some
special markup that will allow any (button) element to be a backButton
without requiring the use of JavaScript.
-- Sean