[30 Builds] Day 9

  • Advertisement ( why? )
     

    HTML-Kit Support, 16th Aug 2013 4:19 pm

    TreeHouse build 20130729 posted.

    http://www.htmlkit.com/assistant/

    • Many improvements in "Quick Look" feature so it should be easier to
      use. Open a project window, single-click a local file to quickly view
      its content without explicitly opening it.

    • Documents open a bit faster and the tabs update more smoothly.

    • Ctrl+F12 split-preview window open/close with less flicker than in
      previous builds.

    Chami

    • bill, 18th Aug 2013 6:31 am

      On 8/16/2013 5:19 PM, HTML-Kit Support wrote:

      TreeHouse build 20130729 posted.

      http://www.htmlkit.com/assistant/

      • Many improvements in "Quick Look" feature so it should be
        easier to use. Open a project window, single-click a local file
        to quickly view its content without explicitly opening it.

      • Documents open a bit faster and the tabs update more smoothly.

      • Ctrl+F12 split-preview window open/close with less flicker than
        in previous builds.

      Chami

      This would be a good time to make the "dirty" flag in the tab
      more noticeable - red and/or bold asterisk.
      bill

      • HTML-Kit Support, 18th Aug 2013 1:36 pm

        On 8/18/2013 6:31 AM, bill wrote:

        On 8/16/2013 5:19 PM, HTML-Kit Support wrote:

        TreeHouse build 20130729 posted.

        http://www.htmlkit.com/assistant/

        • Many improvements in "Quick Look" feature so it should be
          easier to use. Open a project window, single-click a local file
          to quickly view its content without explicitly opening it.

        • Documents open a bit faster and the tabs update more smoothly.

        • Ctrl+F12 split-preview window open/close with less flicker than
          in previous builds.

        Chami

        This would be a good time to make the "dirty" flag in the tab more
        noticeable - red and/or bold asterisk.
        bill

        Hey Bill,

        Just curious... since it displays a message if you try to close a
        modified document, what's the scenario that helps with having a more
        visible modified flag on the document tab? I'm not arguing against it,
        just curious how it might help you. Knowing that may also lead to a
        better implementation.

        Chami

        • Dave P, 18th Aug 2013 2:12 pm

          On 8/18/2013 2:36 PM, HTML-Kit Support wrote:

          On 8/18/2013 6:31 AM, bill wrote:

          On 8/16/2013 5:19 PM, HTML-Kit Support wrote:

          TreeHouse build 20130729 posted.

          http://www.htmlkit.com/assistant/

          • Many improvements in "Quick Look" feature so it should be
            easier to use. Open a project window, single-click a local file
            to quickly view its content without explicitly opening it.

          • Documents open a bit faster and the tabs update more smoothly.

          • Ctrl+F12 split-preview window open/close with less flicker than
            in previous builds.

          Chami

          This would be a good time to make the "dirty" flag in the tab more
          noticeable - red and/or bold asterisk.
          bill

          Hey Bill,

          Just curious... since it displays a message if you try to close a
          modified document, what's the scenario that helps with having a more
          visible modified flag on the document tab? I'm not arguing against it,
          just curious how it might help you. Knowing that may also lead to a
          better implementation.

          Chami

          Hi Chami,

          I agree with Bill, for what it's worth. I think making that asterisk
          red would help a lot.

          And... my pet peeve, which is particularly a pain during this
          build-a-day experiment. Is it possible to make the selected user
          interface theme color stick between updates?

          Dave

          Dave Pyles

          • HTML-Kit Support, 18th Aug 2013 2:25 pm

            On 8/18/2013 2:12 PM, Dave Pyles wrote:

            On 8/18/2013 2:36 PM, HTML-Kit Support wrote:

            On 8/18/2013 6:31 AM, bill wrote:

            On 8/16/2013 5:19 PM, HTML-Kit Support wrote:

            TreeHouse build 20130729 posted.

            http://www.htmlkit.com/assistant/

            • Many improvements in "Quick Look" feature so it should be
              easier to use. Open a project window, single-click a local file
              to quickly view its content without explicitly opening it.

            • Documents open a bit faster and the tabs update more smoothly.

            • Ctrl+F12 split-preview window open/close with less flicker than
              in previous builds.

            Chami

            This would be a good time to make the "dirty" flag in the tab more
            noticeable - red and/or bold asterisk.
            bill

            Hey Bill,

            Just curious... since it displays a message if you try to close a
            modified document, what's the scenario that helps with having a more
            visible modified flag on the document tab? I'm not arguing against it,
            just curious how it might help you. Knowing that may also lead to a
            better implementation.

            Chami

            Hi Chami,

            I agree with Bill, for what it's worth. I think making that asterisk
            red would help a lot.

            But why tho? :) I'm sure I sound silly asking this, but how would making
            the modified flag pop out more help daily use? You couldn't accidentally
            close a modified doc without being prompted so I want to know how
            specifically this might help you.

            And... my pet peeve, which is particularly a pain during this
            build-a-day experiment. Is it possible to make the selected user
            interface theme color stick between updates?

            I think the last time I looked at this it was going to need some
            internal changes but I'll take another look and see if there's at least
            something temp that could be done.

            Dave

            Dave Pyles

            Chami

            • Dave P, 18th Aug 2013 8:08 pm

              On 8/18/2013 3:25 PM, HTML-Kit Support wrote:

              On 8/18/2013 2:12 PM, Dave Pyles wrote:

              On 8/18/2013 2:36 PM, HTML-Kit Support wrote:

              On 8/18/2013 6:31 AM, bill wrote:

              On 8/16/2013 5:19 PM, HTML-Kit Support wrote:

              TreeHouse build 20130729 posted.

              http://www.htmlkit.com/assistant/

              • Many improvements in "Quick Look" feature so it should be
                easier to use. Open a project window, single-click a local file
                to quickly view its content without explicitly opening it.

              • Documents open a bit faster and the tabs update more smoothly.

              • Ctrl+F12 split-preview window open/close with less flicker than
                in previous builds.

              Chami

              This would be a good time to make the "dirty" flag in the tab more
              noticeable - red and/or bold asterisk.
              bill

              Hey Bill,

              Just curious... since it displays a message if you try to close a
              modified document, what's the scenario that helps with having a more
              visible modified flag on the document tab? I'm not arguing against it,
              just curious how it might help you. Knowing that may also lead to a
              better implementation.

              Chami

              Hi Chami,

              I agree with Bill, for what it's worth. I think making that asterisk
              red would help a lot.

              But why tho? :) I'm sure I sound silly asking this, but how would making
              the modified flag pop out more help daily use? You couldn't accidentally
              close a modified doc without being prompted so I want to know how
              specifically this might help you.

              Hi Chami,

              If I have multiple tabs open, I like to be able to scan quickly across
              the tabs to make sure everything is saved before I shut the tabs then
              shut down the program. If the asterisk was a more prominent color I
              would be less apt to miss it. On the main project that I still work on,
              I have file names that are all in the same format (same number of
              characters), which means that the tabs are all the same length. Once I
              know the files are all saved i can just position my cursor in one place
              and close each file with a click when it slides into place after the
              previous file closes. It just seems like an intrusion if the "Do you
              want to save this" warning pops up. It's not a critical thing, it's
              just the way I like to work.

              >

              And... my pet peeve, which is particularly a pain during this
              build-a-day experiment. Is it possible to make the selected user
              interface theme color stick between updates?

              I think the last time I looked at this it was going to need some
              internal changes but I'll take another look and see if there's at least
              something temp that could be done.

              it's not a big deal if it would take a lot of work to do. I had asked
              about it before and don't remember hearing back, so i thought I'd
              mention it again.
              >

              Dave

              Dave Pyles

              Chami

              • HTML-Kit Support, 19th Aug 2013 2:11 am

                On 8/18/2013 8:08 PM, Dave Pyles wrote:

                ...

                Hi Chami,

                I agree with Bill, for what it's worth. I think making that asterisk
                red would help a lot.

                But why tho? :) I'm sure I sound silly asking this, but how would making
                the modified flag pop out more help daily use? You couldn't accidentally
                close a modified doc without being prompted so I want to know how
                specifically this might help you.

                Hi Chami,

                If I have multiple tabs open, I like to be able to scan quickly across
                the tabs to make sure everything is saved before I shut the tabs then
                shut down the program. If the asterisk was a more prominent color I
                would be less apt to miss it. On the main project that I still work on,
                I have file names that are all in the same format (same number of
                characters), which means that the tabs are all the same length. Once I
                know the files are all saved i can just position my cursor in one place
                and close each file with a click when it slides into place after the
                previous file closes. It just seems like an intrusion if the "Do you
                want to save this" warning pops up. It's not a critical thing, it's
                just the way I like to work.

                Thank you Dave. That's what I wanted to know. I didn't really want to
                have too many colors on document tabs which is why I was reluctant to
                make the modified indicator red. Having read how you'd use it, I think
                the changes in 20130731 build may do the trick. It keeps regular colors
                when you're editing but changes to red when the mouse is over document tabs.

                And... my pet peeve, which is particularly a pain during this
                build-a-day experiment. Is it possible to make the selected user
                interface theme color stick between updates?

                I think the last time I looked at this it was going to need some
                internal changes but I'll take another look and see if there's at
                least something temp that could be done.

                it's not a big deal if it would take a lot of work to do. I had
                asked about it before and don't remember hearing back, so i thought
                I'd mention it again.

                That's cool. I didn't get to look at this today. Document tab work took
                longer than I expected but I'm happy with the result.

                Thank you for your feedback Dave.

                Dave

                Dave Pyles

                Chami

                Chami

                • HTML-Kit Support, 19th Aug 2013 2:18 am

                  On 8/19/2013 2:11 AM, HTML-Kit Support wrote:

                  On 8/18/2013 8:08 PM, Dave Pyles wrote:

                  ...

                  If I have multiple tabs open, I like to be able to scan quickly
                  across the tabs to make sure everything is saved before I shut the
                  tabs then shut down the program.

                  ...

                  Just a quick addition... the "Save all modified files" option on
                  document tab right click menu may also come in handy in some cases.

                  Chami

                  • Dave P, 19th Aug 2013 8:08 am

                    On 8/19/2013 3:18 AM, HTML-Kit Support wrote:

                    On 8/19/2013 2:11 AM, HTML-Kit Support wrote:

                    On 8/18/2013 8:08 PM, Dave Pyles wrote:

                    ...

                    If I have multiple tabs open, I like to be able to scan quickly
                    across the tabs to make sure everything is saved before I shut the
                    tabs then shut down the program.

                    ...

                    Just a quick addition... the "Save all modified files" option on
                    document tab right click menu may also come in handy in some cases.

                    Chami

                    I'm not sure that I ever checked the document tab context menu before.
                    There's some nice stuff there.

                    Dave

        • Charles, 19th Aug 2013 11:43 am

          Scanning quickly through the messages in this thread, the one reason to
          have an easily seen flag that a file has not been saved is in the cases
          where one or more CSS files are also open and in edit. So many times I
          have made changes to a CSS file only fail to save it so it is applied to
          the HTML document. This can drive one nuts trying to find what is wrong.

          Maybe there are other ways to prevent this problem from happening but
          this is just one reason I see to have a very visible flag.

          Charles

          On 8/18/2013 2:36 PM, HTML-Kit Support wrote:

          On 8/18/2013 6:31 AM, bill wrote:

          On 8/16/2013 5:19 PM, HTML-Kit Support wrote:

          TreeHouse build 20130729 posted.

          http://www.htmlkit.com/assistant/

          • Many improvements in "Quick Look" feature so it should be
            easier to use. Open a project window, single-click a local file
            to quickly view its content without explicitly opening it.

          • Documents open a bit faster and the tabs update more smoothly.

          • Ctrl+F12 split-preview window open/close with less flicker than
            in previous builds.

          Chami

          This would be a good time to make the "dirty" flag in the tab more
          noticeable - red and/or bold asterisk.
          bill

          Hey Bill,

          Just curious... since it displays a message if you try to close a
          modified document, what's the scenario that helps with having a more
          visible modified flag on the document tab? I'm not arguing against it,
          just curious how it might help you. Knowing that may also lead to a
          better implementation.

          Chami

          • HTML-Kit Support, 21st Aug 2013 12:30 pm

            On 8/19/2013 11:43 AM, Charles wrote:

            Scanning quickly through the messages in this thread, the one reason
            to have an easily seen flag that a file has not been saved is in the
            cases where one or more CSS files are also open and in edit. So many
            times I have made changes to a CSS file only fail to save it so it is
            applied to the HTML document. This can drive one nuts trying to find
            what is wrong.

            Maybe there are other ways to prevent this problem from happening
            but this is just one reason I see to have a very visible flag.

            Charles

            Thank you Charles. We all have slightly different workflows and
            preferences so this is helpful.

            Chami