Databases
StackOverflow2013
Postsdbo
POWays to organize Settings in Sublime Text plugin
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POWays to organize Settings in Sublime Text plugin
    primarykey
    data
    text
    <p>Perhaps it is another round of "static vs instance" but I am trying to be devil in details. Note that I am fairly new to Python and plugin development.</p> <p>Some plugins use the following code:</p> <pre><code>s = sublime.load_settings(__name__ + '.sublime-settings') class Settings: def load(self): self.setting1 = s.get('setting1', 'default1') self.setting2 = s.get('setting2', 'default2') ... # Global Scope settings = Settings() settings.load() s.add_on_change(__name__ + '-reload', settings.load) </code></pre> <p>There is nothing particularly wrong with this example except <code>load_settings</code> and <code>add_on_change</code> methods should belong to <code>Settings</code>:</p> <pre><code>class Settings: def __init__(self): self.settings = sublime.load_settings(__name__ + '.sublime-settings') self.settings.add_on_change(__name__ + '-reload', self.setup) self.setup() def setup(): self.setting1 = self.settings.get('setting1', 'default1') self.setting2 = self.settings.get('setting2', 'default2') ... # Global Scope settings = Settings() </code></pre> <p>Now <code>Settings</code> class encapsulates all functionality. But do we really need instances of this class ? I don't think so. That's why <code>static</code> should be used:</p> <pre><code>class Settings: settings = sublime.load_settings(__name__ + '.sublime-settings') @staticmethod def init(): Settings.settings.add_on_change(__name__ + '-reload', Settings.setup) Settings.setup() @staticmethod def setup(): Settings.setting1 = Settings.settings.get('setting1', 'default1') Settings.setting2 = Settings.settings.get('setting2', 'default2') ... # Global Scope Settings.init() </code></pre> <p>The advantages (if any) of the example above are:</p> <ul> <li>class encapsulates <em>all</em> functionality related to settings</li> <li>no need to create instances to access settings</li> </ul> <p>Are there any other "decent" ways to organize Settings ?</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PTQuestion
    1. USMattDMo
    1. USIgor Gilyazov
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. POWays to organize Settings in Sublime Text plugin
      1. This table or related slice is empty.
      1. VTUpMod
    1. COYour argumentation makes absolutely sense. I don’t think there is really a standard way to solve this though, so as long as it works, do what you think is the best way.
      singulars
      1. POWays to organize Settings in Sublime Text plugin
      1. USpoke
    2. COClasses are just instances of their metaclass, so `Settings` _is_ and instance of something. By making everything static you're basically creating a singleton, which is a controversial design -- look it up. By doing so you're also preventing or a least hindering code reuse.
      singulars
      1. POWays to organize Settings in Sublime Text plugin
      1. USmartineau
    3. CO@martineau, note that i am not trying to make every class static ("everything static"). The reason for Settings class to be static is that plugin doesn't really need multiple instances of it.
      singulars
      1. POWays to organize Settings in Sublime Text plugin
      1. USIgor Gilyazov
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload