Who said that!?You could go with http://frhed.sourceforge.net/ and Visual Studio.No one has to have GCC and Unix-like envirorement to create OSes... Instead you could have PE kernel file and your own bootloader, instead using Grub which takes 32 kilobytes of hard drive and takes one part of RAM.Please do not continue this project in Visual Basic, as it's beginner's language, and try using Win32 C++.Anyways, for everyone which dislike PE files, could use your OS deving IDE. Nice work .I could help you when you would write it into Win32 C++.It may look hard to use C++ for GUIs instead of consoles, but it isn't, when you get enough experience.

OS development is really an advanced subject, whose complexity should not be hidden behind a fancy IDE. Furthermore, the widely accepted UNIX philosophy is "write programs that do one thing and do it well", and not "write a program that does everything".

Regards,glauxosdever

_________________Before implementing any piece of software, make sure you have designed it to be extendable. Backporting new features into old code is not always easy.

I agree with glauxosdever. It is a mistake to constrain OS programmers into using a particular set of tools in a particular way. Anyone who is a good enough programmer to do OS development will surely be able to configure a professional IDE such as Eclipse or XCode in a way that suits them; or they may just stick with a terminal and vi.

(But if you must, Visual Basic is as good a language as any to write it in.)

BTW, if your avatar is an indication of your design tastes you could certainly count me out from using an IDE that you designed.

But it won't be easy for bigginers. And, yes, you could configure an other IDE, but why not using someting already configured ?

Well, making OSDev easy for a beginner isn't going to get them anywhere. They'll get used to using "pre-configured" stuff, which will just become a nightmare in the long-term, because they'll turn to tutorials for the harder things, and how many tutorials do you know actually have a good system design? I think configuring your own IDE isn't hard. Using a terminal, a text editor and a build script isn't hard at all either. A Makefile should be even faster, though I don't use it. No offence here, but by writing an IDE for OSDev you are wasting your own effort and time.

_________________Working on a new Unix clone.You know your OS is advanced when you stop using the Intel programming guide as a reference.

Who said that!?You could go with http://frhed.sourceforge.net/ and Visual Studio.No one has to have GCC and Unix-like envirorement to create OSes... Instead you could have PE kernel file and your own bootloader, instead using Grub which takes 32 kilobytes of hard drive and takes one part of RAM.Please do not continue this project in Visual Basic, as it's beginner's language, and try using Win32 C++.Anyways, for everyone which dislike PE files, could use your OS deving IDE. Nice work .I could help you when you would write it into Win32 C++.It may look hard to use C++ for GUIs instead of consoles, but it isn't, when you get enough experience.

I don't like Visual Basic either, it is a language to get your started. If he wants to develop a fully automated GUI IDE, I would suggest him doing it in C#. C# is very GUI friendly and you can create what ever the thing you want with it. C++ is not an option, you need like 99340 lines of code to just create one simple window. Why do you care about 32 kilobytes??? Coding your own bootloader right from the start is not an option, you need to have some detect assembly knowledge. Maybe after 3rd/4th revision of your OS you could do that and see how much you learned.

I use gEdit, FASM, build script, default terminal (GNOME terminal) and QEMU/Bochs for testing. Sometimes, but rarely, I use VMware and VirtualBox too.BTW, graphics programming in C++ for Windows seems harder than it is; it really is simple if you know how the window manager works with events and controls and such.

_________________Working on a new Unix clone.You know your OS is advanced when you stop using the Intel programming guide as a reference.

Who is online

Users browsing this forum: Yahoo [Bot] and 2 guests

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum