User talk:City-busz

From ArchWiki
Jump to: navigation, search

Chromium spin-offs

Hi, are Opera and Vivaldi really Chromium spin-offs? They weren't according to one of your previous edits... -- Lahwaacz (talk) 12:21, 31 July 2016 (UTC)

This is depending on the definition of spin-off. Both of them have a customized interface, but reuse many UI elements and underlying technologies from Chromium. E.g. both of them are compatible with Chrome extensions. But we could rename the section to something else, e.g. "Browsers derived from Chromium", if you think it fits better.--City-busz (talk) 13:13, 31 July 2016 (UTC)
OK, that will be hard, since Brave seems to (or plans to) also support (at least a subset of) Chrome extensions, so maybe the distinction should be different.
I don't mind if it stays like this or not, it just seemed odd that the categorization changed and the section title didn't.
-- Lahwaacz (talk) 13:38, 31 July 2016 (UTC)
Brave just integrated the 1Password extension. There is no general support for Chrome extensions, and I believe that it never happens, because they use libchromiumcontent trough the Electron platform, which is nothing more than an a wrapper around Chromium's Content module, and extensions are not part of it.--City-busz (talk) 14:45, 31 July 2016 (UTC)

Gtk+ Development: Python

I'm not sure why GTK+/Development#Python was reverted, as the warning messages when running the current version of the example code show:

./gtk_dialog.py:6: PyGTKDeprecationWarning: Using positional arguments with the GObject constructor has been deprecated. Please specify keyword(s) for "parent, flags, message_type, buttons, message_format" or use a class specific constructor. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations
  Hello=Gtk.MessageDialog(None, Gtk.DialogFlags.MODAL, Gtk.MessageType.INFO, Gtk.ButtonsType.OK, "Hello world!")
./gtk_dialog.py:6: PyGTKDeprecationWarning: The keyword(s) "message_format" have been deprecated in favor of "text" respectively. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations
  Hello=Gtk.MessageDialog(None, Gtk.DialogFlags.MODAL, Gtk.MessageType.INFO, Gtk.ButtonsType.OK, "Hello world!")
./gtk_dialog.py:6: PyGTKDeprecationWarning: The "flags" argument for dialog construction is deprecated. Please use initializer keywords: modal=True and/or destroy_with_parent=True. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations
  Hello=Gtk.MessageDialog(None, Gtk.DialogFlags.MODAL, Gtk.MessageType.INFO, Gtk.ButtonsType.OK, "Hello world!")
/home/amel/pyenv/lib/python3.6/site-packages/gi/overrides/Gtk.py:542: PyGTKDeprecationWarning: The keyword(s) "parent" have been deprecated in favor of "transient_for" respectively. See: https://wiki.gnome.org/PyGObject/InitializerDeprecations
  self._init(*args, **new_kwargs)

ILMostro (talk) 16:25, 13 February 2018 (UTC)

Because you replaced the message dialog with an empty window. How did you get these deprecation warnings? I can't see these messages when I run the code.--City-busz (talk) 22:52, 13 February 2018 (UTC)

I was trying to keep the code as simple as possible. I wasn't sure how to get the Message Dialog up using the newer code. I don't see the messages/warnings when running the code using the system-wide python interpreter. You can verify using virtualenv, then

pip install PyGObject

That should install PyGObject version 3.27, which should display the warning. Alternatively, you can run the code using the system-wide PyGObject version (3.26) with -Wd flags.

Deprecations will be in the form of Gtk.PyGTKDeprecationWarning. These warnings are only issued in development releases (odd minor version, 3.9, 3.11, etc...). Stable releases with even minor versions will not show deprecations unless the "-Wd" command line option is specified when running Python.


ILMostro (talk) 04:30, 14 February 2018 (UTC)

I didn't know about the "-Wd" command line option. Now I fixed these deprecations.--City-busz (talk) 08:37, 14 February 2018 (UTC)