SRL Archive - MSI Suggestions

I think the setup should be

MSI/MSI/Core/Items.simba
MSI/MSI/Skills/woodcutting.simba


right now it is

MSI/Core/Items.simba
MSI/Skills/woodcutting.simba


That would make it much neater

MSI/MSI/
Would contain the two folders Skill and Core and maybe Extras.

MSI/ would contain…
ACA, Progress Reports, Debug Logs, Extensions, RunMe.simba, and MSI

I don't really like having a long path to the .simba files, but you're right, it would be neater and more orgainzed. I'm okay with it, we'll see what other people say. :)

From: Coh3n
I don't really like having a long path to the .simba files, but you're right, it would be neater and more orgainzed. I'm okay with it, we'll see what other people say. :)

It's usually upsetting when you have to type the longer path out every time you type, but this will be a one time include, in only one .simba file (the setup file?). Since it's not really a big deal for actual scripting, and will enhance the organization, I think it looks nicer. We'd have to get everyone to commit their stuff before or it will be a pain in the ass to update after the folders are all changed around, I think.

From my point of view (and most likely anyone else that frequently codes MSI) it would be sort of annoying just because it's already sort of annoying navigating around everything when writing code.

From a users perspective though, it would probably be nicer.

From: 3Garrett3
It's usually upsetting when you have to type the longer path out every time you type, but this will be a one time include, in only one .simba file (the setup file?). Since it's not really a big deal for actual scripting, and will enhance the organization, I think it looks nicer. We'd have to get everyone to commit their stuff before or it will be a pain in the ass to update after the folders are all changed around, I think.

Commits are made every day, so people shouldn't hold changes for very long anyway.

From: NCDS
From my point of view (and most likely anyone else that frequently codes MSI) it would be sort of annoying just because it's already sort of annoying navigating around everything when writing code.

From a users perspective though, it would probably be nicer.

I agree. Shortcuts can always be made to go straight to the /Skill or /Core (not in MSI, but on personal computers) for easier navigation.

I disagree, I always hate it when I have to click the SRL folder twice to get where I want to be.. Sure, for organizations sake it would be better, but for the scripters it's a hassle and (imo) unnecessary.

Shortcuts aren't as useful when they're that short btw :p

From: Zyt3x
Shortcuts aren't as useful when they're that short btw :p

What? I'm talking about right-clicking the Core folder and choosing "Create Shortcut".

From: Coh3n
What? I'm talking about right-clicking the Core folder and choosing "Create Shortcut".

Yea, so when you open the first msi folder, you can click the shortcut to take you all the way to core.

From: Coh3n
What? I'm talking about right-clicking the Core folder and choosing "Create Shortcut".

[QUOTE=Camaro';759373]Yea, so when you open the first msi folder, you can click the shortcut to take you all the way to core.[/QUOTE]So how many clicks do we save? 2? :redface:

From: Zyt3x
So how many clicks do we save? 2? :redface:

I always hate it when I have to click the SRL folder twice

So there, you save two clicks in SRL(if you used the shortcut) and in MSI it would be around the same amount of clicks as it is now(if you used the shortcut), except the MSI folder would now be more organized. :)

[QUOTE=Camaro';759393]So there, you save two clicks in SRL(if you used the shortcut) and in MSI it would be around the same amount of clicks as it is now(if you used the shortcut), except the MSI folder would now be more organized. :)[/QUOTE]Yeah, but for the time it takes the brain to process "I have to click the shortcut and [B]not[/B] the msi folder" is the same as clicking the msi folder twice so I don't really save anything :p

Lol this is a pointless argument. :p

I think we should go for organization. We add files to the include all the time and we don't want things getting flustered and unorganized.

Zyt3x, I think you would get used to the new paths, you just may find it inconvenient at first.

From: Coh3n
Lol this is a pointless argument. :p

I think we should go for organization. We add files to the include all the time and we don't want things getting flustered and unorganized.

Zyt3x, I think you would get used to the new paths, you just may find it inconvenient at first.

Alright :)

Committed.