i was just thinking...

perhaps a new client layout would be cool. the main reason is because i was thinking that perhaps status bars would be cool. Most people who are coming on here to use this are wanting health systems etc, and HP, MP bars and what not would be cool. Also, i think a bigger space for status variables is needed, then people could display character stats, gold (gold in bank), experience bar? attribute points. I guess i could come up with a few designs if asked

You can make your own.....

||||||||
|||||---
|||-----
||||||--
|||||||-
|||||---

erm,
()))))--
()))))))
()))----
()------
(-------

[---------]
[-------""]
[----"""""]
[-""""""""]

Or something like that....
Maybe have a font with a uni width...

Good ideas, and we really do need more space.

Computer Whizz wrote:You can make your own.....

||||||||
|||||---
|||-----
||||||--
|||||||-
|||||---

erm,
()))))--
()))))))
()))----
()------
(-------

[---------]
[-------""]
[----"""""]
[-""""""""]

Or something like that....
Maybe have a font with a uni width...

Well - I do agree that bars would be helpful - just like the one's in kazaa and some such programs - although they use VC++....

You know - when Alex changes the RTF to HTML, then you'll be able to just resize two images to make a good bar scale thingy anyway ....

HTML??? WTF?

There's been loads of talk over it Ste - he wants to change the textbox to HTML instead of RTF....

Thing is it's quite hard...

i knew there was talk but i didnt think it was gunna be a serious (and/or definate) change. man, that sucks

What do you mean it sucks?
It's much better since you can do some things alot easier...

Plus it's only the output - ad not ASL itself.

eek, i just don't like the thought of HTML in a C++ application, especially something like quest.

Where the hell did you get C++ from?

From what i've read, C++ is what Quest is written in
Of course, I'm still learning and I'm pretty new, so i may be wrong

AFAIK Quest is a Visual Basic (6) Application.

Al (MaDbRiT)

VB5 actually, but close enough

Knew you hadn't gone .NET yet Alex... but guilty of simply *assuming* you'd be using VB6 sp6 (the last 'pre .NET issue) which is what I have here. Never really looked closely enough obviously

Al (MaDbRiT)

You should get VB6 Alex
Can't you get an upgrade version really cheaply?

There would be no point whatsoever. There is hardly any difference between VB5 and VB6.

And I suppose learning VB .NET would be a waste of time, so sticking with VB5 is the best option?

VB.NET would require massive changes to the code. That would take a very long time. And then Quest would require the .NET runtime, which would add, oh, around 30mb to the download

All that for no advantage whatsoever...

So VB5 it is.

so is it only the Qnet server that is written in C++? i thought you said it was, and didn't know VB (when i was gunna make that personal stand alone client).

Anyway. I still think the client layout needs to be changed.

QuestNet Server is written in VB as well - that way it uses much of the same code as Quest itself.

Didn't think of this earlier: wouldn't VB5 still require the VB Runtime Files?

Didn't think of this earlier: wouldn't VB5 still require the VB Runtime Files?

Yes, VB5 & 6 still require VB run time files, but the thing is that Quest with VB5 runtimes included is like 3.5Mb whereas if Alex moved to VB.net the VB.net runtime files alone are over 21Mb in size... so Quest would swell in size by a factor of 6 or 7 times...

Actually most PC's already have the VB5 run times on them courtesy of other apps by now - but that's not relevant to this discussion.

There's no real world gain in performance (actually VB.net seems consistently and noticeably slower on my development machine). it would be a huge amount of work for Alex to change the code (.net is quite a bit different to VB 'classic' as we call it here) and the download would become pretty intolerable in size on a dial up...

So to echo "Alex VB5 it is"

Al (MaDbRiT)

I guess so. And having tried VB .NET for about a month before my computer stuffed up, I know that so much has changed. Microsoft obvisouly think that they've made things easier, and in someways they probably have (like the form resizing), but in most ways they've made it real hard for VB6 programmers to learn it.