Hi. I was just wondering if Brian could give us some info on where hes at. Im not pushing him to get it done, i would just like to hear how hes doing. Brian, the work you've done is amazing! Keep up the great work!|
I wonder the same. There hasn't been any news for more than a half year. Is SciStudio dead or still in developement?|
Is there an estimated released date for SciStudio 4?
Some info would be nice.
But anyway, keep up your good work. :D
There is no estimated release date. Just whenever SCI Studio VGA is complete.|
As for how far a long it is, you will have to wait for Brian to report on that.
He usually posts updates when important things get done, he isn't going to report every bug, change, and difference that he makes in it. Only major things like new major features or it being more completed.
Ive been eagerly awaiting this release. Ive probably been checking these pages for a year now waiting.|
I hope Brian will let us know soon....
Thank you Brian!!!!
It's strange that in 8 month's there isn't an update with something intresting to say about the project by Brian. I think is the biggest "no-updates" period I ever seen about this project. I hope all is getting well.|
Good Work Brian!
Brian has updated but in SCI Studio page, not from the main page.|
You can check at:
Robin, the last update on the page IS from 8 months ago. ;)|
Look, do you guys really not have a life to the point where you want to hear "I fixed a bug, although you guys didn't know what the bug was because SCI Studio VGA isn't release yet."
I mean, if there is something important that he has done he would have posted it either here or on his site.
I don't think you guys should be hassling him about it because he is doing this in his spare time, and for no money whatsoever, in other words a hobby, NOT A JOB. He has a life outside of SCI Studio.
Woops! I read February 16th 2004.|
It's time for me to buy new glasses. Sorry Chris.
Chris you're right and I'm agree with you, I don't wanna hassling anyone. I only wonder why in this 8 months there aren't any news. Before the last update the work of Brian seems to proceed well so it's strange this long pause. I only hope that this silence doesn't means that the work on the new version is slowing down.|
Sorry for the misunderstandig I didn't wanna make pressure to anyone I'm only curious about the development ;)
Greetings and good luck to Brian :)
Heh, work on the next version has "slowed down", naturally. As Chris said, it's a hobby, not a job. I appreciate the donations, but I would make more money if I were working at a fast food restaraunt for a week than I've made in the five years of working on SCI Studio. I do SCI Studio for the fun of it, if it were for the money, I wouldn't have done it at all. However, work has to come first. |
People ask me for a Mac version, a Linux version, even an Amiga version. People ask for more docs (does everyone realize how many pages of docs I've already written and included with SCI Studio!? Far more than AGI has, that's for sure... docs for 114 kernel functions, 63 classes, 29 scripts, etc. Where did the template come from? I wrote it line by line, it's huge...). People swear at me and complain why it wasn't released last year! I get complaints when I release other projects that I should have spent the time on SCI Studio. You try working on the same project, and nothing else for five years and a few hundred dollars. Good luck! Unless you're a publisher who wants to invest a paying wage into it, I can't drop everything and finish it right away. The reason progress used to be so fast was because I was often spending 12-18 hours a day working on it, staying up for 24 hours straight. It was crazy. I spent my entire spring break a few years back making the SCI compiler for example. In retrospect, that was stupid. I shouldv'e been outside, enjoying the sun. Working 18 hours programming in a day, staying up for 24 hours, has taken it's toll on me, and I can't do it anymore, unless there's a severe deadline, and it's for work. Besides, computer programming is a lot like acting, or anything else, in the sense where you can be typecasted. I don't want to be known as "The SCI Studio Guy", which is another reason I do other projects. I don't even want to be known simply as "The Sierra Guy". I need to work in other areas.
It was to be a surprise when I got time, so you wouldn't have to wait like this, but I guess to calm you down a bit, I'll tell you in advance. I will be releasing the full source and everything I've done for people to play with soonish, but am busy with work right now, and can't spend the time to even tidy and bundle everything and update the site yet. I plan on continuing the project, but since I don't have as much time as I used to for it, if others want to continue it, they will be able to.
It's great you're releasing the source code. I only hope someone will pick it up. This project has so much potentional. |
Good luck with your other projects Brian! Thanks for everything.
|Nychold||I'm not going to raise hopes and spirits in anyone by saying "I'll pick up the project should Brian drop it", but I'll definately be picking up a copy of the source code whenever Brian gets around to it. I know the last copy of the source code I got wouldn't compile because I didn't have the syntax highlighter, and totally forgot to ask where he got it (hint hint if you're reading this ^_~), but I'd love the chance to try. XD Course, I probably have as much free time as he does, and an aversion to meddling in other people's source, so who knows? Still, you definitely rock for at least releasing the source code. ^^|
|Endroz||The best bet for SCI Studio if Brian really wants to release source code would likely be to make SCI Studio an Open Source project, though. ;)|
SCI Studio already is fully open source and licensed under the GNU GPL (like all the software on his site). You can download the latest source code from http://www.bripro.com/.
The highligher control is included in the zip file. In fact, absolutely everything is included in the source zip. There's even a readme that explains exactly how to compile it. Good luck picking it up ;)
Even though I am getting a little impatient for the release, I'll stick to my guns and say it again.|
Take all the time you need to finish it, no one ever conqured the world using the Beta version. ;)
Till next time stay cool 8)
Then the next step would be to put it on Sourceforge.net and extend the project to more developers. Particulary, we all SHOULD help Brian with his project, instead of asking him all day how's it going on. That way, it'd be completed and working before the sun lights out... ;D
|Nychold||SourceForge is a great place for an organized team of people, but just turning the source code loose to dozens of programmers can actually hinder a project more than it can help it. Imagine, if you will, 20 different programmers who've never met, all with different ideas, different coding styles, different choices in APIs, etc. You'd have a nightmare of a code to walk through and debug. Even with ONE person, it's a hard task to walk through as many lines of code that are already in SCI Studio 3 (I know, I've got it...Borland compiles mine at just over 2.6 MILLION lines of code, though most of that is VCL) without having small bugs and errors. In fact, a lot of the SourceForge projects die quickly because of that fact...too many people can't agree on something, and the project suffers. :'( I think the way SCI Studio is now is not a bad way to go. ;)|
|Endroz||I agree that the way SCI Studio is now is not a bad way to go, but consider what Brian just told us. He's gonna sail toward other seas to not let people "typecast" ;D him as the "SCI Studio guy". A wish which is more than justified by the fact that SCI is pratically a legacy engine, unless someone will be able to expand it with more recent graphic/audio formats and technologies. It is just for the fun of it, I see his point -but- if Brian would take another ten years to complete that, well I guess by that time Sierra will give out the whole SCI engine sources as freeware 'old' stuff already. And that's why I'm saying that Brian needs help. ;)|