Changes to Allegiance's UI

Pos_21 · Post by **Pos_21** » Wed Sep 27, 2006 5:26 pm

Can we convince AU to run batch files?

If so, we could include one to copy a person's backups (from, say, /./artwork/backup/) over the existing files.

I don't know if this would be any more plausable than a 'don't touch' list however.

terrenblade · Post by **terrenblade** » Wed Sep 27, 2006 6:59 pm

Cast my vote with baxter on this one, everything he hates I also would hate. And I'm too lazy to type it my self.

Post by **BlackViper** » Wed Sep 27, 2006 7:23 pm

NM TE, I cheated and hit the edit button so I could read the color code.

I agree. I will edit this when I get home for exactly what I use and like.

Batch file idea. That would probably the the simpliest way for an individual to then redo their own custom install. We post up a basic batch file that includes all of the changed file names. Then each user could comment out the file list per his own custom installation and restore what they want after the upgrade. Of course everyone would have to create a "UIbackup" folder (as a name example) and make sure to keep a current copy of the .mdl files they like in there. Then after the update, batch/copy over their old files.

Post by **Tigereye** » Wed Sep 27, 2006 7:33 pm

Unfortunately BV that's not an option with some of the changes we are pushing.

The biggest "breaker" will be changing the status text below your target while in cockpit view.

That single line of text is going to be replaced by 3 lines of scrolling status so it isn't constantly overwritten. This change requires new controls to be added to the .mdl files (which is why we need to push new MDLs) and codechanges to pump 3 lines of text to these new controls instead of 1.

If someone were to install the R3 exe but not install the updated .mdl file, they will crash every time they attempt to join a game.

Users will NEED these new status controls in their mdl files, so we will be overwriting everyone's mdl files with these new controls. By then, all mod makers will have had time to update their installers so their other customizations can be re-applied on top.

In short: we can't let users choose which files to update and which ones they can't. All of the current mods aren't whole files as much as they are changes made to files.

Everyone's free to change the defaults we push, but if you use any old files without the new status lines you WILL crash.

--TE

Bard · Post by **Bard** » Wed Sep 27, 2006 7:58 pm

Ok hang on a second guys.We have Teamspeak. It's beneficial and advertised.We have the academy keymappings. Also beneficial and a good starting point for custom keyboard layouts.We have various UI interfaces done custom as mods, to suit anyone who has a personal preference.We have the ability to record custom sound files for in game sounds and replace the existing ones with alternates (see sector overload/boundary file)Why alter the AU files to include this at all?

Why not just advertise the UI features and allow everyone their own choice? Not everyone uses CortUI. If the advantages and disadvantages of doing so are clearly stated and easily located, noone is in the dark. Change the dialog.mdl strictly as needed for R3. Is there any reason not to leave everything else optional? The whole problem seems like it's the wrong approach to a simple problem.

Just set a simple standard and allow easily obtainable alternative options.

Dogbones · Post by **Dogbones** » Wed Sep 27, 2006 8:31 pm

Bard that is one of the options. Pushing the new mdls via AU is just one way of getting them to you, and that method is problematic.

What seems to be a more likely method is an R3 installer that includes the required new mdl files. After it is installed you can update to what ever custom mdls you want. Although even that is not quite so simple, so it likely we'd need to reinstall all of the mdl files not just the ones we need to chnage. But you would still be able to reapply custom mdl files (updated to include whatever changes we need so it doesn't crash).

We are just hashing things out here in the forum.

Bard · Post by **Bard** » Wed Sep 27, 2006 8:51 pm

I kinda figured, but maybe it'd be wise to clamp down on some of the "omg the sky is falling" and start comparing the most practical solution to the simplest possible solution instead of giving immediate weight to whoever is deciding to be vocal about the upcoming popular opinion/controversy of the day? (no offense to anyone who's posted here so far, it just feels like the issue is being muddled a lot by opinion, especially in the absence of factual data)

What exactly is R3 going to change in the dialog.mdl file?

How do the R3 changes in and of themselves, as they were planned before the UI addition was considered, affect custom UI's?

Dogbones · Post by **Dogbones** » Wed Sep 27, 2006 9:03 pm

Bard wrote:QUOTE (Bard @ Sep 27 2006, 04:51 PM) instead of giving immediate weight to whoever is deciding to be vocal about the upcoming popular opinion/controversy of the day?

Umm.... are you new here /ninja.gif" style="vertical-align:middle" emoid=":ninja:" border="0" alt="ninja.gif" />

But I agree 100%, I'd actually be inclined to flush 90+% of the posts and keep on topic.

What features of CortUI would you guys like to see as part of the base Alleg everyone gets when they install it?

Bard · Post by **Bard** » Wed Sep 27, 2006 9:10 pm

Dogbones wrote:QUOTE (Dogbones @ Sep 27 2006, 03:03 PM) Umm.... are you new here /ninja.gif" style="vertical-align:middle" emoid=":ninja:" border="0" alt="ninja.gif" />

Can you tell? *wink*

Honestly, I'd say none of them, but that's really the part that stymies me...why it's being suggested that the CortUI features be implemented as standard in the first place. What's the reasoning behind it?

If we're going to debate change issues and register opinions on them, it's probably wise to drill down to the root causes of said changes.

I see people bitching about screen real estate in various software and hardware UI mods. I can't see adding extra chat lines as a default when it's available as an option and some people already seem to think that the current amount is too much.

I love that F3 shows ship information in CortUI, but other people hate it.

Basically, why is this thread here at all?

Zapper · Post by **Zapper** » Wed Sep 27, 2006 9:12 pm

The only GUI modification i want in Cort's GUI is the F7 minimap ripcord option when launching from a base.

The other stuff was not a useful modification... but more a visual distraction.
Ofcause this will change when the resolution standard will get higher and even then the modification will change and conflict or challenge the visual setup of the GUI.

The Cort' gui modification is not a "need" to have mod. But a "nice" to have mod and should be the option of the individual.

I would rather have a on/off checkbox configuration of the diff. option's then a Yes/No solution.
This could easily be implemented in the System setup config written in the Registry.

The future HighRes version will prolly mess the config up...(we/I have to test it)
Zap