SRL Archive - General

I think that to increase ease of use (making MSI easy to use) Script Records should have attributes.

These would not necessarily break v1, (I'm not picturing it right now), but I'm hoping we dont have to.

If we do, that's fine. Here's what I had in mind:

Type
  TScript = record;
    Location: integer;
    Address: string;
    SName: string;

    //Start list of attributes here.
    ObjsAvailable: TIntegerArray;

I don't understand at all…

Ok, this is part of the coding style that just learnt it uni, so I'll get back to it, no worries :)

For the TScriptRecord don't worry about it, I'll take care of it and post and afterwords we'll just make sure everything adds up :) Code away as usual and I'll start by making sure all the old 'attributes' get on there and that the system gets well implemented.

Afterward it'll probably just be ctrl + R - all and we'll have MSI v2, as soon as we've added all the planned features in.

~RM

I'm confused too…


"Script records should have attributes"

From Wikipedia:
"In computing, an attribute is a specification that defines a property of an object, element, or file."

procedure DeclarePlayers;
var
  i: integer;
begin
  with Players[0] do
  begin
    Username := 'Sir R. Magician';
    Password := '$RL43v3R';
    Pin := '1234';
  end;

  for i := 0 to High(Players) do
  begin
    with Players[i] do
    begin
      {$IFDEF MSI_LSW}
      SetLength(RocksArray, 3);
      RocksArray := [ORE_COAL, ORE_MITH, ORE_ADDY];
      {$ENDIF}

      {$IFDEF RM_Cook}
      SetLength(Processes, 4);
      Processes := [COLLECT_WHEAT, COOK_FLOUR, COOK_MIX, COOK_BAKE];
      {$ENDIF}
    end;
  end;
end;

Now that's just stupid.. Using Defines means to change objectives / scripts you have to manually change the code..

From: Zyt3x
Now that's just stupid.. Using Defines means to change objectives / scripts you have to manually change the code..

No…

Who's dev here? Rather than call stupid go read up on attributes.

xml attributes are the best to look at to get the picture here.
:google:

From: Sir R. M8gic1an
No…

Who's dev here? Rather than call stupid go read up on attributes.

xml attributes are the best to look at to get the picture here.
:google:

Even though you're an admin, your action tells me otherwise… I'm sorry for saying this, but lately your actions has made me look at you as nothing more than a JR Member….

Back on topic: I don't see how this will make it easier for users. Making them change code in order to make MSI do something else is not the right way to go IMO

Well I'll explain this when I'm done coding it, I don't know what else you could expect

~RM

From: Sir R. M8gic1an
Well I'll explain this when I'm done coding it, I don't know what else you could expect

~RM

Great :)
I'll just wait until you're done updating OP then.

From: Zyt3x
Back on topic: I don't see how this will make it easier for users. Making them change code in order to make MSI do something else is not the right way to go IMO

I agree with this. I think you explain this more, RM, because we're clearly not understanding it correctly. Like what are the advantages, what does it mean for the rest of the include?

I'm not sure how what you're saying will make it any easier to setup MSI. I mean, I'm not even sure how much easier we can make it than it is right now. :unsure:

I just realized there's a post missing here, my bad Zytex.

~RM

This seems like an appropriate thread to bring this up (going off the title). I've been using MSI a lot lately using my army, and one thing that really annoys me is the form. I think the layout is poor, and it's very time consuming to setup multiple players, especially if you want them all using the same script (the latter is a simple fix, but I thought'd I'd mention it anyway).

Yeah, the form looks great, but when it comes down to it, it's not that user friendly. Not to mention the lack of space we have for expansion. There are a lot of suggestions for features/options to add to the form, and for some of them, we simply don't have the space, unless we were to use popups upon button clicking. You guys may think I'm crazy, but I propose we rewrite the form. Not as soon as possible, but slowly over time, just to see how things go. I may open a git repository if people are interested in following.

Why do something like this? Simple.

1. Makes it easier for the end user to setup.
2. We can still make it look nice without using bitmaps for everything.
3. Using the default form components allows for easy expansion of options/features.
4. Any mistakes that were made with this form can be corrected with the new one.
5. The form will most likely be 1000x faster/smoother since we won't have 100 bitmaps slowing it down.
6. Most of the functionality code can be used from the other form, so we wouldn't be completely rewriting everything.
7. Gives us the opportunity to properly implement all the suggestions that were given here.
8. Last but not least, MSI is meant to be a learning ground for other scripters. I don't know if anyone's taken a look at the code for the form, but there's no way anyone can learn from half the code that's there. It's messy, unorganized, and undocumented.

So yeah, this popped into my head a couple days ago when I was setting up my army. Don't be afraid to tell me I'm an idiot, I can take it. ;)

E: We could just simply reorganize the current form, but wouldn't solve all the problems.

I agree Coh3n. The form is really tiny, and the code is really messy. I'd say a complete re-write would be the best

I would support a re-write. I could use a bit more form experience.

Or just don't use a form… I hate forms. :(

From: Wizzup?
Or just don't use a form… I hate forms. :(

It's much more user-friendly though, and that's something we'd want with the new users coming to SRL

From: Wizzup?
Or just don't use a form… I hate forms. :(

Plus, you can always just set USE_FORM = False; ;)

From: Wizzup?
Or just don't use a form… I hate forms. :(

I know. :p

But think about it from a new user's point of view. Would you rather use a nice GUI to set everything up, or have to learn how to properly setup the code side of it?

I'm surprised you guys agreed so easily. I thought for sure someone would debate it. I'll setup a repository and create a new thread in the SL section. :)

E: http://villavu.com/forum/showthread.php?p=784142#post784142

From: Wizzup?
Or just don't use a form… I hate forms. :(

You know we have to be more of an Ubuntu than a Gentoo, there just isn't enough people.

From: Boreas
You know we have to be more of an Ubuntu than a Gentoo, there just isn't enough people.

Probably. I just wanted to say focus on stability first. :D