applait / finder Goto Github PK

Forgot to turn off debug mode in 1.1. Now everything is getting logged in the console. And the app can feel to be slow. Need to push out an early release with debugMode turned off.

In the "About" view, add a "Preferences" section that will have an option to search through hidden files.

This will be a checkbox. The value of it will be persisted through localStorage. Default value should be disabled. The value should be checked on startup.

This option will change the value of Applait.Finder.checkhidden.

We have several blocks of repeating code which came in from the 2 PRs made to solve #5. They are in js/ui/home.js and js/ui/actions.js and toggle the disabled state of the search interaction elements.

These blocks should ideally move to functions and those functions should be called from event listeners.

Curently, :disabled has opacity: 0.3. It looks too light.

Increase it to opacity: 0.75.

Now that #5 is solved, we need a way to tell the user that those buttons and text inputs are disabled. Add slight CSS changes for the :disabled pseudo property to make that happen.

As of now we have a :focus declaration for buttons, but that does not work well with touch screens.

Need to apply the same animation to buttons when they are tapped on touchscreens. This would mean using touch events. instead of just click events, and using JavaScript instead of CSS :focus to detect those events and use a class to do the animation.

Essentially, the :focus events need to be there, but we also need better touch events for buttons.

As of now we say that Finder is supported only on Firefox OS 1.3+. The reason is, pre-1.3 did not have support for the standard display: flex. We have to use -moz vendor prefixes to make sure the current layout works in Firefox 1.1+.

Any place in the CSS where we are using flexbox need to be supplemented with the vendor prefixes. After that we can say that Finder is supported on Firefox OS 1.1+.

As noted in applait/finderjs#2, we need to hide files if they belong to a hidden folder. So, include updated version of FinderJS as soon as that issue is patched upstream.

Give it to meeeeeeeee.............

Sometimes searching for a query which can include hidden files shows the search count to be double or near double of the actual number of results.

This can be an issue with FinderJS not returning proper filematchcount when hidden files are enabled.

Change all the click bindings to touch bindings.

In home view, the searchresult item template uses data-goto on each child item to detect click. That was a quick patch to make sure it works, but it is not a good solution. As of now, in index.html it looks like:

<!-- searchresult item -->
<template id="tmpl-searchresult-item">
    <div id="searchresult-item-{i}" class="searchresult-item" data-index="{i}" data-goto="#/detail/{i}">
        <button data-goto="#/detail/{i}">
            <i class="icon-{icontype}"></i>
        </button>
        <h3 data-goto="#/detail/{i}">{name}</h3>
        <button data-goto="#/detail/{i}">
            <i class="icon-right-open"></i>
        </button>
    </div>
</template>

Ideally, only .searchresult-item elements should have the data-goto attribute. That should work whenever a single .searchresult-item item is tapped.

In the "About" view, add a "Preferences" section that will have an option to enable debugMode.

This will be a checkbox. The value of it will be persisted through localStorage. Default value should be disabled. The value should be checked on startup.

This option will change the value of Applait.Finder.debugmode.

Version 1.5 of the logo.

In the "About" view, add a "Preferences" section that will have an option to make searches case-sensitive.

This will be a checkbox. The value of it will be persisted through localStorage. Default value should be disabled. The value should be checked on startup.

This option will change the value of Applait.Finder.casesensitive.

We forgot to disable reset button and search form and search button when search is going on. As a result, if anyone hits the reset button while a search is being continued, it will result in broken UX.

These elements should be disabled on api.finder.on("searchBegin", fn) and enabled on either of:

• api.finder.on("searchComplete", fn)
• api.finder.on("searchCancelled", fn)
• api.finder.on("empty", fn)
• api.finder.on("error", fn)

Include a "Rate us in the Firefox Marketplace" link in the About view, linking it to Finder's page on Firefox Marketplace.