 | | | | | |
Is there a GUI for legOS like Bricx CC for NQC? If there is, is it easier
to use and do you lose features useing it?
Thanx
scott
| | | | | | | | | | | | | | | |
| |
|
In lugnet.robotics.rcx.legos, Scott Davis writes:
> Is there a GUI for legOS like Bricx CC for NQC? If there is, is it easier
> to use and do you lose features useing it?
It really WOULD be nice if someone created a simplified way of getting up
and running for legOS, even if it didn't actually contain a GUI interface
for programming (though I by no means would discourage someone from
providing THAT as well!) or some minor 'features' were lost in the process.
Consider how basically simple it is to install BricXCC: download nqc, unzip,
download BricXCC, unzip, run. Currently it takes at least a few hours to get
legOS running, and that's if everything goes extremely smoothly. I got it
working once just before my computer died but have had no desire to
reexperience this painful process since then.
Is there anyone who has made a "legOS installation for the time-deprived and
pain-intolerant"? Even just having a setup that would be sufficient for 95%
of prospective users would go a long way to getting more people interested
in using this interesting alternative OS. For starters, a pre-compiled
kernel ready for downloading would be extremely welcome! If anyone really
wants to have a different kernel, they are certainly still welcome to use
the full install to do so. And a single zip file for Win-98 compatible OS's
that contains just what you'd need to compile and download programs to the
brick would be equally desirable. Anyone that wants the source code to
cygwin, pearl, the gcc compiler, etc., can still get it - it's only a click
away. But why *force* everyone to have to do so?
The benefits would be a larger number of people starting to use this, and
possibly some of them getting so hooked that they'd volunteer to continue
improving legOS for everyone else.
--
David Schilling
| | | | | | | | | | | | | | | | | |
| |
|
Hello David,
> For starters, a pre-compiled kernel ready for downloading would be
> extremely welcome
What would it help?
> Anyone that wants the source code to cygwin, pearl, the gcc compiler,
> etc., can still get it - it's only a click away. But why *force* everyone
> to have to do so?
Have you ever tried legOS? First, if you are running legOS from Linux, you
don't need cygwin and that kind of things. They are only needed to resemble
a UNIX enviroment under DOS. And the UNIX system is needed by the GNU
compiler.
You _never_ need the source code for gcc or cygwin, but you need the h8 gnu
toolchain anyway because you have to compile your user programs. Compiling
the legOS kernel is a proof that you correctly installed your toolchain and
the supporting programs. So I don't see a need for a ready compiled legOS
kernel.
Running generic h8 compiled programs on the brick is the fastest possible
way to run a program. The benefits in terms of speed a gigantic. But it is
not usefull for a new-to-c-programming user. LegOS is mindstorms swiss army
knife. Very usefull if you can handle it but it can cut ;).
By the way, I use legOS together with kate, the KDE editor and a makefile.
One can start the make process from inside kate, even download to the RCX.
This comes close to a full featured legOS GUI.
Regards,
Michael
| | | | | | | | | | | | | | | | | | |
| |
|
I didn't want to have to write my programs for LegOS and then type a ton of
commands only to find that I made a mistake. So I downloaded UltraEdit-32 9.
It allows unix type file to be saved
(This will replace the carriage return and line feed combinations to a line
feed only.)
and it allows macros to be run; therefore, all I need to do is write my
programs,
press CTRL + SHIFT + 1 to compile, then press CTRL + SHIFT + 2 and my
program is downloaded. (It helps that I wrote a batch file to help UltraEdit
along)
I think this could almost be concidered as a GUI. What do you think?
Bluey
In lugnet.robotics.rcx.legos, Michael Obenland writes:
> Hello David,
>
> > For starters, a pre-compiled kernel ready for downloading would be
> > extremely welcome
>
> What would it help?
>
> > Anyone that wants the source code to cygwin, pearl, the gcc compiler,
> > etc., can still get it - it's only a click away. But why *force* everyone
> > to have to do so?
>
> Have you ever tried legOS? First, if you are running legOS from Linux, you
> don't need cygwin and that kind of things. They are only needed to resemble
> a UNIX enviroment under DOS. And the UNIX system is needed by the GNU
> compiler.
> You _never_ need the source code for gcc or cygwin, but you need the h8 gnu
> toolchain anyway because you have to compile your user programs. Compiling
> the legOS kernel is a proof that you correctly installed your toolchain and
> the supporting programs. So I don't see a need for a ready compiled legOS
> kernel.
>
> Running generic h8 compiled programs on the brick is the fastest possible
> way to run a program. The benefits in terms of speed a gigantic. But it is
> not usefull for a new-to-c-programming user. LegOS is mindstorms swiss army
> knife. Very usefull if you can handle it but it can cut ;).
>
> By the way, I use legOS together with kate, the KDE editor and a makefile.
> One can start the make process from inside kate, even download to the RCX.
> This comes close to a full featured legOS GUI.
>
> Regards,
>
> Michael
| | | | | | | | | | | | | | | | | | | | |
> So I downloaded UltraEdit-32 9.
> I think this could almost be concidered as a GUI. What do you think?
I'm running legOS from Linux, so I don't know Ultraedit. But if its suitable
for your needs and free it seems to be a good choice.
Regards,
Michael
| | | | | | | | | | | | | | | | | | | |
| |
|
Michael,
What I am hearing here and have heard in the past, along with my own
personal experience, is that developing for legOS under Windows and more
specific cygwin can be or is a pretty difficult task. Compounded on top of
that is if you have very little or no Unix experience then it can be near
"impossible" or seem that way. From your post I see that you primarily if
not entirely develop under Linux which as I review this newsgroup does not
seem be that difficult to develop under or use the development tools and
environment. From our (that is Windows users) experience there is room for
improvement or at least "introductory tools" which allow "beginners" get
started. I do see the benefits and the educational value of using the full
set of tools. But getting to the point of compiling and running application
programs can take some major steps. I can think of two things which would
benefit those just starting with legOS under the Windows environment, a
pre-compiled set of tools for compiling and download application programs,
and a web-compiler.
Both of these have existed in one form or another. DJGPP provided
pre-compiled set of tools that I believe allowed a user to use DOS tools can
compile their application program. The old page for DJGPP is at
http://legos.sourceforge.net/files/windows/djgpp/. I have NO experience
with this method but with the resurgence of interest in easier methods to
compile code I will look at this again. And Markus Noga site listed two web
compilers that worked atleast with much earlier versions of legOS. I would
be interested in seeing one work again.
I must personally testify that the readers of this newsgroup are VERY
helpful in assisting anyone having difficulties with legOS. I will recommend
once again that anyone having difficulty post their issues and problems
here. I will go even further and say that if you give a more detail
explanation about what you are experiencing or having trouble with the more
likely a good answer will be given. And if you try several different things
when errors occur and post what you have tried people can give better advice
to as what might help and what won't.
Ed
Michael Obenland <obenland@t-online.de> wrote in message
news:GxsMFn.6DE@lugnet.com...
> Hello David,
>
> > For starters, a pre-compiled kernel ready for downloading would be
> > extremely welcome
>
> What would it help?
>
> > Anyone that wants the source code to cygwin, pearl, the gcc compiler,
> > etc., can still get it - it's only a click away. But why *force* everyone
> > to have to do so?
>
> Have you ever tried legOS? First, if you are running legOS from Linux, you
> don't need cygwin and that kind of things. They are only needed to • resemble
> a UNIX enviroment under DOS. And the UNIX system is needed by the GNU
> compiler.
> You _never_ need the source code for gcc or cygwin, but you need the h8 • gnu
> toolchain anyway because you have to compile your user programs. Compiling
> the legOS kernel is a proof that you correctly installed your toolchain • and
> the supporting programs. So I don't see a need for a ready compiled legOS
> kernel.
>
> Running generic h8 compiled programs on the brick is the fastest possible
> way to run a program. The benefits in terms of speed a gigantic. But it is
> not usefull for a new-to-c-programming user. LegOS is mindstorms swiss • army
> knife. Very usefull if you can handle it but it can cut ;).
>
> By the way, I use legOS together with kate, the KDE editor and a makefile.
> One can start the make process from inside kate, even download to the RCX.
> This comes close to a full featured legOS GUI.
>
> Regards,
>
> Michael
>
| | | | | | |
