I'm pretty sure someone else has brought this up but is there any chance we can have the research sort descending from left to right so that we don't have to click the left and right buttons all the time to compare points to complete and see where we are at on the various research topics?

you know, we don't see the missions after we complete them, why do we see the tech after we research it ? just sayin'

Yes it has been "brought up" in Suggestions & Ideas , which is where it gos . because your suggesting to change how it works now to something better.

The difference between a bug and an improvement is often times perspective. I build custom web pages for a living and I've always had to put the most relevant data up front. I do not consider the sort order a feature that needs improvement but an interface that was done wrong. If the code was written right it should just be a matter reversing the array or changing the order clause in the db select statement. If the underlying code was written wrong was done wrong then its about 1-3 hours of reorganizing html and or correcting the code base to a more modular data object.

Is this a glaring error no, and you would be right to assume that some will consider this a feature upgrade. Having built launched and maintained close to 100 sites in the last 7 years of my programming career i felt this was a bug. You are welcome to disagree.

So , the new claim all artifact box was an bug fix and not an improvement , by your standards.

Actually that would be a feature upgrade because it's additional functionality to make something easier. The sort order i see as a design flaw that needs to be corrected. Bare in mind that I think very highly of Dan's over all design skill. It's certainly far better than mine and his use of JS is elegant. I'm more of a server side programmer myself.

a design that has existed for over a year that you'd want changed should probably be considered a suggestion not an issue

"flaw in design" are not bugs, but well.... flaws
we can't know for sure whether this is a bug or a suggestion w/o knowing the original concept the developer had in mind.
If it is doing what Dan envisioned it should, then this would go into suggestions, as we are suggesting a better design.
If it was designed the "better way" to start with but ended up the way it is now, then it's a bug.

I see the bug scenario as highly unlikely, so I'm gonna guess this is a suggestion, not a issue.

Definition of bugs:
A software bug is the common term used to describe an error, flaw, mistake, failure, or fault in a computer program or system that produces an incorrect or unexpected result, or causes it to behave in unintended ways.
note that the "result" should be "incorrect or unexpected result" or "behave in unintended ways"
so if it was intended/expected, it's not a bug, quality of design(and "intended way") being irrelevant

That is a valid argument, and like i said people will probably consider it a feature. I still view it as a design flaw. If i had done that on a client's project i would have to fix it. Even if it took them a year to notice, and it's not like he will have to do a lot to get it done. I imagine the hardest part will be finding the code responsible and if things were done right it should only take about 30 seconds from there. There is also a quick and dirty solution that can be applied through jquery if he doesn't feel like hunting down the code.

http://tinysort.sjeiti.com/ has a jquery sorter that he can apply to the id's

$(".item > div").tsort("",{attr:"id"});

Placing that in the html being served up by loader.php?page=Research should do the trick
Some browsers (IE versions 6-9 COUGH COUGH) might fight him on that, and he will probably need to add some dual classing to keep if from manipulating other elements. 'item' is a pretty generic term so i assume that is being rendered by loader.php.

But honestly since the numbering there is based on the primary key from the db a 'order by <PRIMARY KEY> desc' or just adding ', <PRIMARY KEY> desc' to the end of the current order by is about all it would take.

Ok the real point that you should post something like this in Suggestions & Ideas is that. Issues and Support needs to be save for when something is not working the want it was programed to like , things not loading , can't claim things , artifacts not working as they should. Suggestions & Ideas is where we post things that we want added/changed to make the game better, where everyone can talk about it(there are a lot that don't read Issues and Support if eveything is working for them).

Here is the last post about this feel free to comment/bump the post
http://galaxylegion.com/forum/viewtopic.php?f=6&t=10214

Fair enough pardon my insolence.

errr... those things u mentioned should go into... support tickets?
this here issue&support forum is more for bugs that affects everyone, for example a typo somewhere or some (new) function not working in general
forum isn't exactly the most reliable at getting things fixed quickly XD

There are some known issues that are browser based that some people don't know about and sometimes it's just a misunderstanding of how the game works , there are even times that it's a facebook error. Things like this in-game support tickets can't fix and and maybe we can't ether , but you tend to get a more timely answer here.

In-game support tickets should be saved for when you know something is wrong, so there not spending all there time looking over false/unneeded tickets and can fix whats really broke and make improvements.