Html vs Interface

ID:87263
 
Dec 11 2009, 4:38 pm

Poll: Html or Interface

Html 11% (3)
Interface 88% (23)

Login to vote.

Well recently I opened up a old source of mine and started looking at it and i noticed that i had alot of browser based content which relyed on htmllib. Now with BYONDs interface should i try to upgrade the source to use Interface instead of html? Or should i go on the saying "If it's not broke don't fix it"?
Dec 11 2009, 5:12 pm
Either-or depending on what your trying to do. Why not use both as they can compliment each other well.

ts

Dec 11 2009, 5:16 pm
Well most of the stuff is pretty basic. Just forms asking for your desc., name and such. Wouldnt it be best to use interface becasuse it doesnt have to create a catch file for each window?
Dec 11 2009, 5:31 pm
Sure. Your going to use HTML when your design requires a feature which the interface does provide or make easy.

One example would be drop down lists. They are possible to do in the interface but it is not exactly easy.

ts
Dec 11 2009, 5:32 pm
If it works and you like it just leave it. Though with Interfaces you have much more freedom. Its more of what fits best in the situation.
Dec 11 2009, 5:43 pm
Alrighty, I understand where both of you are coming from. Personally i like the html better, but i have found the interface to be a bit more functional with stuff such as error prompts and phraseing the input.
Dec 11 2009, 5:51 pm
It depends entirely on what you're doing.

The browser object for interfaces makes the use of HTML lib somewhat pointless now. If you know anything about client/Topic(), you're fairly set on doing anything you need to, especially since they added POST data into internal forms (you still can't world.Export() POST data at the moment).

As an example, Character Creation, since I've already done it with an interface (and did it well, I like to think), I'd be more inclined to try doing it with a browser to simply see if I can improve performance. For instance, at least on my computer, sending data to client/Topic() is a lot quicker than using winget().
Dec 11 2009, 6:04 pm
Interface, I say!
Using the interface is just my preference. Just me since I found it to be simpler.
It's your choice, so whatevers.
If the "if it's not broke don't fix it" is your philosophy, I'd stick with HTML. As long as it works, right?
Dec 11 2009, 6:40 pm
Yea i could stick with it, but i think i can get the same functionality and a better look useing interface. Not to mention much less code. I currently have a CSS file and all my tables are hardcoded in, which each table takes around 20-45 lines of space depending on the use. If i can cut that back to a few image files or just useing labels on the interface no telling how mush smaller the file size could be.