Comments for Nekohayo ! http://jeff.ecchi.ca/blog La vie personnelle du chat Sun, 09 Jun 2013 01:59:08 +0000 hourly 1 http://wordpress.org/?v=3.5.1 Comment on Status update — new Pitivi timeline, GSoC projects, etc by antistress http://jeff.ecchi.ca/blog/2013/06/08/status-update-new-pitivi-timeline-gsoc-projects-etc/#comment-23696 antistress Sun, 09 Jun 2013 01:59:08 +0000 http://jeff.ecchi.ca/blog/?p=2418#comment-23696 “Mathieu Duponchelle killed our goocanvas-based timeline and redid the whole thing with Clutter. In two weeks” & “Mathieu is now working full time on fixing bugs everywhere in the stack. We hope to have something showable (beta) for GUADEC” : Wow :-)

]]> Comment on Status update — new Pitivi timeline, GSoC projects, etc by Mathieu Duponchelle http://jeff.ecchi.ca/blog/2013/06/08/status-update-new-pitivi-timeline-gsoc-projects-etc/#comment-23695 Mathieu Duponchelle Sat, 08 Jun 2013 23:52:08 +0000 http://jeff.ecchi.ca/blog/?p=2418#comment-23695 It is :) Clutter is a great library !

]]> Comment on Status update — new Pitivi timeline, GSoC projects, etc by Alex http://jeff.ecchi.ca/blog/2013/06/08/status-update-new-pitivi-timeline-gsoc-projects-etc/#comment-23693 Alex Sat, 08 Jun 2013 21:54:52 +0000 http://jeff.ecchi.ca/blog/?p=2418#comment-23693 That timeline looks pretty darn sweet!

]]> Comment on No more stuck rendering dialogs! by nekohayo http://jeff.ecchi.ca/blog/2013/04/28/no-more-stuck-render-dialogs/#comment-23653 nekohayo Wed, 01 May 2013 13:53:20 +0000 http://jeff.ecchi.ca/blog/?p=2405#comment-23653 Hmmm… partly because

  • I’m not sure where to point to (distro bug tracker? Pitivi’s bug tracker?)
  • Every distro has a different bugtracker, and they’re usually where bug reports go to die
  • I don’t know how to interface with bugtrackers, generally speaking
  • At some point if the user can’t be bothered to copy-paste an error (which in itself is not sufficient: you’ll need bug reproduction instructions, debug logs or backtraces, etc.) then what’s the point?
  • Pointing to a wiki/website page URL is not really future-proof, might as well just say “Visit the Pitivi website for bug reporting instructions” at that point…

So yeah, the thought has crossed my mind but I’m not sure how to handle it (and I want to keep the implementation relatively simple too :)

]]> Comment on No more stuck rendering dialogs! by mdgeorge http://jeff.ecchi.ca/blog/2013/04/28/no-more-stuck-render-dialogs/#comment-23650 mdgeorge Tue, 30 Apr 2013 17:55:15 +0000 http://jeff.ecchi.ca/blog/?p=2405#comment-23650 The detailed error message is useful for two things: the user can copy/paste to file a bug report, and the user can google for help. How about instead of making them do all that work, instead just have two big helpful buttons that do these things: “File report” and “Find help” or something like that? I would probably still include the expander in case there’s something I didn’t think of, but if you’re going to go halfway and give the error to the user, why not go whole hog and help them use it effectively?

]]> Comment on No more stuck rendering dialogs! by nekohayo http://jeff.ecchi.ca/blog/2013/04/28/no-more-stuck-render-dialogs/#comment-23648 nekohayo Mon, 29 Apr 2013 15:45:39 +0000 http://jeff.ecchi.ca/blog/?p=2405#comment-23648 I tried implementing the use of the “sad-face” icon in a simple way, but the problem is that GTK Image’s new_from_icon_name makes it impossible for me to know if loading the icon failed or not (because it will display a “broken image” icon instead, and the return value is always True)… and I suppose I can’t assume that this “sad face” icon would always be present on users’ computers (especially outside gnome). So I have three choices:

  • Keep it as it is, with the default GTK error icon. We could argue that it’s a theme issue and that sad face icon should become the default error icon for GTK with gnome…?
  • Try loading the sad face icon, but if it fails, it fails (no fallback to the normal error icon)
  • Implement something rather complicated and ugly for this specific case – not even sure that’s possible
]]> Comment on No more stuck rendering dialogs! by Frederik Elwert http://jeff.ecchi.ca/blog/2013/04/28/no-more-stuck-render-dialogs/#comment-23647 Frederik Elwert Mon, 29 Apr 2013 14:36:42 +0000 http://jeff.ecchi.ca/blog/?p=2405#comment-23647 Yes, that is indeed better!

I would, however, second two suggestions:
+1 for the reformulation suggested by tim, and +1 for the sad smiley suggested by Ulisse. Both make it yet a little less scary.

]]> Comment on No more stuck rendering dialogs! by nekohayo http://jeff.ecchi.ca/blog/2013/04/28/no-more-stuck-render-dialogs/#comment-23646 nekohayo Mon, 29 Apr 2013 14:17:52 +0000 http://jeff.ecchi.ca/blog/?p=2405#comment-23646 Fair point! I think your first suggestion sounds interesting to me (a little bit less formal without mocking).

]]> Comment on No more stuck rendering dialogs! by Tim http://jeff.ecchi.ca/blog/2013/04/28/no-more-stuck-render-dialogs/#comment-23645 Tim Mon, 29 Apr 2013 12:49:52 +0000 http://jeff.ecchi.ca/blog/?p=2405#comment-23645 How about “Sorry, but something didn’t work right” or “Something unexpected happened”. “Has gone terribly wrong” might sound a bit alarming for a novice user (who might not understand that it’s not to be taken entirely seriously and their data isn’t affected).

]]> Comment on No more stuck rendering dialogs! by nekohayo http://jeff.ecchi.ca/blog/2013/04/28/no-more-stuck-render-dialogs/#comment-23644 nekohayo Mon, 29 Apr 2013 12:24:24 +0000 http://jeff.ecchi.ca/blog/?p=2405#comment-23644 I updated the blog post above with the screenshot of a revised implementation that provides a slightly less ugly and demoralizing text for users… let me know if that’s indeed better.

]]>