Forum > Software Development

Things individual people want to be doing on Noggit.

(1/7) > >>

schlumpf:
Please use this thread on synchronizing what you want to change in Noggit, which ideas are good etc.

Please implement the following construct to use settings somewhen soon. ("assigned" to Mjollna.)

--- Code: ---class application
{
  // ...
public:
  QVariant setting (const QString& key) const
  {
    return _settings.get (key);
  }
 
  void setting (const QString& key, const QVariant& value)
  {
    emit setting_about_to_change (key, setting (key));
    _settings.set (key, value);
    emit setting_changed (key, value);
  }

signals:
  void setting_about_to_change (const QString& key, const QVariant& value);
  void setting_changed (const QString& key, const QVariant& value);
};

// examples on how to use:

class foo_bar : public QObject
{
  Q_OBJECT

public:
  foo_bar (QObject* parent)
  : QObject (parent)
  {
    connect ( app()
            , SIGNAL (setting_changed (const QString& key, const QVariant& value))
            , SLOT (setting_changed (const QString& key, const QVariant& value))
            );
  }
public slots:
  void setting_changed (const QString& key, const QVariant& value)
  {
    if (key == "paths/game")
    {
      LogDebug << "game path changed to: " << value.toString().toStdString() << std::endl;
    }
  }
};

class settings_dialog : public QWidget
{
  // ...
  settings_dialog( ...)
  {
    connect (antialiasing_box, SIGNAL (valueChanged (int)), SLOT (set_antialiasing (int)));
    connect (app(), SIGNAL (setting_changed (const QString&, const QVariant&)), SLOT (setting_changed (const QString&, const QVariant&)));
  }

  void set_antialiasing (int value)
  {
    app().setting ("antialiasing", value);
  }

  void setting_changed (const QString& key, const QVariant& value)
  {
    if (key == "antialiasing")
    {
      antialiasing_box.setValue (value.toInt());
    }
  }
};

--- End code ---

Mjollna:
Hi there :)

So here's what I have in mind :

- First priority imho is having a nice Qt UI. Right now there are lots of menus and such to re-do, so that the program can be used again.
For the settings window and having settings changes saved, etc., as Schlumpf said I'm doing it.

- Then, there are the bugs on the bugtracker ( bugtraker/index.php ). Among them, the ground doodads thing ( bugtraker/index.php?do=details&task_id=103 ) and the mcal problem ( bugtraker/index.php?do=details&task_id=50 ) seem, to me, the most important ones, but again, it's just my opinion on the subject.
There's also that rendering problem of the terrain when using very small raising brush which seems quite problematic ( viewtopic.php?f=66&t=1047&start=15 ).

- Lots of things are almost implemented in the code, ctrl+f todo if you're out of ideas. There's also always things to make nicer/cleaner.

- Then for new things... As I said on the Adt Converter topic, having LK features fully implemented would be awesome : mccv, mh2o... And that would prepare for a possible 4.x handling.

phucko1:
Well, a rotate by degrees would be nice :P Aswell as a copy rotation from first selected to second selected :P

Mjollna:
I actually have a question...
If I create an irc chan for people who want to contribute to Noggit dev, would you (Steff, Glararan, other people ?) join ?

It's so much easier to have a common place to chat all together...

-----[edit]

Well, created it, so if some people want to join :
Quakenet, #Noggit
Should be permanent in a few hours.

Steff:
Firs thin is to get all the stuff running again. Then Gui :)

Navigation

[0] Message Index

[#] Next page