You dont have a clue do you? Here is a case study for you, one among many: www.blitzbasic.com/Community/posts.php?topic=51868
You're right. Although I don't see how that helps your arguement. The negative vibe is going, already from the second post. You can't blame BRL for not commenting on a thread that's already stacked against them, nor for not giving in to your poor attempt at a primadonna-like ultimatum. I would have waited for the GUI lib if I wasn't kept in the dark for weeks and weeks at a time. I was kept in the dark so I went and made my own and now have absolutely no need to give them money - because they kept me in the dark.
I fail to see your point. If your large commercial project was being detained because of something you could do in less than a week, I don't see why you would want to wait in the first place.Additionally it's a very grandiose assertation that you would have done such and such under this and that circumstanes. It so nice when you aren't actually challenged on it, because it's an entirely fictional setting.
I think thats a very common thing.
Well, you're entitled to your opinion. If it's accurate, I think that's a good thing. The more people develop rigid cross platform system friendly GUI's the better. Not everyone subscribe to the psuedo communist idea that one size fits all occasions infallibly. The more competition the better is how I see it. Finally flameduck, who elected you the great arse kisser of BRL?
How do you mean? Oh I get it, because I disagree with your point of view, it must be because I'm kissing someone elses arse. That's a brilliant argument right there, if I ever saw it. I would like to see more information, not more promises and I think this is the key.
Marks last worklog is what? Three weeks old? What good would it do, what value could it possibly have, and in what way would it assist your project in moving forward if Mark posted The GUI module is *still* almost there! Unfortunately, there are a few platform inconsistencies to iron out. I want the beast to behave as similarly as possible across all platforms, and that's proving a little, erm, tedious.
from now on, until release? All I would want would be a single paragraph update, say once a week, saying how things had gone that week and letting me know if anything had arisen that would put the release date back at all.
Could you give an example of what such an update might contain? A week really isn't that long, considering you're only two full-time employees working on it. I imagine most of the posts would be like:"This week we worked on some of the DirectX bugs you reported. Since DirectX is a horrible API, which seems to fail at random, for obscure and arcane purposes know only to the DirectX wizards at Microsoft (who've stopped answering mail and returning phone calls) it might take longer than expected. All release dates should be considered pushed back another month."
or maybe:
"This week was spent trying to figure out why users where reporting DrawText was killing their framerate. After much head scratching we discovered that it was a flaw inherent in certain nVidia drivers. We've sent off a report to nVidia, who are going to ignore us, because we aren't EA."
In short: Information that doesn't nessecarilly contribute in a meaningful way to the advancement of my project.