Hey

There's this repo that replicates Android Toasts using HTML5 and Javascript ( no jQuery/zepto) dependency. I think it fits well with Fries.

https://github.com/jadjoubran/Android-Toast

Implementation of the following switches should be included in version 1.0.1:

• Checkboxes
• Radio buttons
• On/off switches

Should be implemented with little to no JavaScript as much as possible.

It must follow the design guidelines as stated here: http://developer.android.com/design/building-blocks/switches.html

I'm sorry if this issue is already out, I couldn't find a topic about it.

The problem is quite simple, the back button makes you leave the application even if you are in a "second" screen (like contacts.html in demo content). Is it "normal" considering the use of stack.js ?

My config : Phonegap 2.7.0 on Android 4.1.2

For those interested, I created a new development branch off of the current master AND themes/holo-light branches, merged the dist, lib and example files and fixed some minor JS errors.

You can check it out here. (@jaunesarmiento In case you'd like to merge holo light and dark themes into one branch too, Ill send you another pull request you can merge. Otherwise, just ditch the PR.)

We have found out that fries uses a svg from Tobias Bieniek which is converted by icomoon. Now Tobias asks for attribution according to CC. This does of course mean if I use fries for my app, I need to give attribution to Tobias. This was not clear to me if I wouldn't have had a conflict between Font Awesome and Fries.

Also I was first misleaded by the font name "icomoon" which is most likely the name just because it was generated by the icomoon app. I almost missed the original author of the SVG files.

It would be great if fries would make more clear that it is necessary to attribute Tobias if the icons are used.

I have a page that I am opening via stack.js which has some tabs in it. I added a back button for the page which would execute window.history.go(-1); to go back to index.html.

The problem is that, the user would have to click so many times on the back button to make it go back within a stack.js page which has tabs, after navigating through them. This is because the back button would be going back through the previously viewed tabs on the page before going back to index.html

I could have directly linked back to index.html but I have dynamically loaded data there which I don't want to lose.

Haven't come up with a fix for this yet, looking for a simple workaround first.

Related to issues #12 and #32.

The issue is that Fries components uses touch events so it really won't work on the browser and non-touch devices. Touch events were used because click events are fired after about 300ms from the moment you tapped a button.

A solution I can think of is to rework the components to mimic Google's Fast Button implementation.

Or use a touch library like hammer.js. Although I'd rather rework the library than introduce a dependency to an external library.

A workaround to this is to do what @aymanfarhat suggested in his comment, is to enable the emulated touch events on Google Chrome. For a more detailed instructions on how to do this, click here.

After using Stack.js data-transition="push", spinners in the action bar can't be executed. I get an "Uncaught TypeError: Cannot read property 'classlist' of undefined spinner.js:43" when I attempt to press on the toggle-spinner.

It causes the scrolling to be slow on my Samsung Galaxy S2, S3 and S4. When I changed the body declaration in base.css to the following, it worked

body {
    /*  position: fixed;
    top: 0;
    right: 0;
    bottom: 0;
    left: 0;*/
    font: 15px/1.6 "Roboto", sans-serif;
    color: #fff;
    background-color: #000;
}

I am implementing a tabbed navigation just like in the Fries sample, it is working fine with Phonegap but the tabs are not working on Chrome(Desktop) neither FF when clicking on them, any ideas what could be the problem? What is odd is that in the demo on the site they're working fine, could be a different version?

Note: there are no errors what so ever on the console. Here is my code if you'd like to take a look https://gist.github.com/aymanfarhat/5729462

Implemented dialogs. This pull request exposes a Dialog class in the fries namespace with the ff methods:

• init() - called when you do new fries.Dialog(options);. Initialises the dialog along with the options object. The dialog is initially hidden. Just call show() when you need to display the dialog.
• show() - Shows the dialog.
• hide() - Hides the dialog.

An example of the options object is as follows:

{
  selector: '#dialog',
  okCallback: function () {
    // this is called when the user presses the "OK" button inside the dialog
    // do something here
    // optionally, you can hide the dialog afterwards
    this.hide(); // "this" refers to the dialog
  },
  cancelCallback: function () {
    // this is called when the user presses the "Cancel" button inside the dialog
    // do something else here
    // usually, you just hide the dialog so:
    this.hide();
  }
}

Notes:

• Currently, the dialog only works with the first DOM element specified in the selector parameter. So if you need to create multiple dialogs, you need to call new fries.Dialog() on each of those elements for now.
• The okCallback and cancelCallback are optional parameters. Although it would seem pointless not to add an okCallback.

After checking back after some while, I noticed that the project website at getfri.es is offline. And two whois searches (.es whois is a bit tricky, thus 2) revealed that the name servers for this domain were changed today (2014/12/02) to *.sedoparking.com. Last but not least, the domain owner was transfered from Fries' author - @jaunesarmiento - to some stranger (at least, as far as related to Fries).

Additionally, when you go to the GitHub project page jaunesarmiento.github.io/fries/, it redirects to jaunesarmiento.me/fries/ - the author's private website. However, this site is also offline.

So, may I ask whether the project is still maintained?

Thanks

Not sure why this was merged at all, but 722f50d replaces jekyll serve by jekyll --server --auto.

Here's what jekyll has to say:

>jekyll --server --auto
       Deprecation: Jekyll now uses subcommands instead of just switches. Run `jekyll --help' to find out more.
       Deprecation: The --server command has been replaced by the 'serve' subcommand.
       Deprecation: The switch '--auto' has been replaced with '--watch'.
jekyll 2.5.1 | Error:  Whoops, we can't understand your command.
jekyll 2.5.1 | Error:  invalid option: --server
jekyll 2.5.1 | Error:  Run your command again with the --help switch to see available options.

Easy fix: revert 722f50d

Tabs wont change it's content when it's clicked. I think it just sets the same -webkit-transform: translateX to all "

Hiatus is up! Time to work on v2.1.0. Any help is welcome.

Here's a list of features and fixes that will be included in v2.1.0:

• [x] Holo Light theme
• [ ] Implement navigation drawer (#49)
• [ ] Implement scrollable tabs (#24)
• [ ] Implement <textarea> form element. Its style should look like the <input> element but grows vertically when text is long. (#8)
• [ ] Fix switches (Issues #86, #66)
• [ ] Fix radio buttons (Issue #86, #66)
• [ ] Fix checkboxes (Issues #85, #86)
• [ ] Fix keyboard overlapping fields of a form (Issue #80)

hi there been messing around with a chrome app if anyone is interested see bellow repository.

https://github.com/gregnietsky/fries-chrome-app

the only issue i have come across so far is the bottom actions trigger the scrollbar i have not investigated this. if i do and find something ill feed back seems to be a padding/margin/height calc issue.

what this app does is well nothing ... it opens up a 380x640 app window loading the example off the fri.es site in a webview.

the icons are from a "todo list" demo if you have suitable suggestions / replacements please advise.

anyone is welcome to do with this as they wish.

the idea is to have a standalone chrome app and droid app with the same UI/operation.