I’d like to know what QSSL plan to do about editors, IDE,…
At the moment there is nothing comfortable to edit source code in QRTP. I see that ped receive new functionnalities in every new package but will it become a real source code editor?
I’d like not to talk about vi, qed, … may be some peoples like these, personnaly I don’t.
Wouldn’t it be more interesting to make a portage of some powerfull editors such as xemacs or anything else?
I tried gxedit but first we need a powerfull cpu to cast off the ‘weight’ of the xphoton layer, and second it seems impossible to use it with localized keyboard (for me, with a french keyboard, only alphabetical keys work).
I’d like to know what QSSL plan to do about editors, IDE,…
At the moment there is nothing comfortable to edit source code in QRTP. I see that ped receive new functionnalities in every new package but will it become a real source code editor?
I’d like not to talk about vi, qed, … may be some peoples like these, personnaly I don’t.
Wouldn’t it be more interesting to make a portage of some powerfull editors such as xemacs or anything else?
I tried gxedit but first we need a powerfull cpu to cast off the ‘weight’ of the xphoton layer, and second it seems impossible to use it with localized keyboard (for me, with a french keyboard, only alphabetical keys work).
Thanks, Alain.
ermm, before we go into a […] contest about the pro’s and con’s of
having an editor with two modes (it beeps or it doesn’t) versus an
operating system with editing capabilities (and lisp interpretation),
there is quite a few good IDE’s out there which compile right out of the
box on RTP. Source Navigator (http://sources.redhat.com/sourcenav/) from
Cygnus (now Redhat) is one of it, and Colin promised a port of KDevelop
“Real Soon Now ™”. Now someone could give Code Crusader
(http://www.newplanetsoftware.com/jcc) a shot and then there should be
enough flavours to please everybody.
From my point of view we do not need ASAP an IDE. We need to build
Asynch library for instance ASAP.
Then many other hot problems which should be solved, many scripts to be
ported to RTP, administration tools and so on. You could try porting w,
or who to RTP.
Emacs is working ok, there is a problem in slow redrawing of menus
sometimes but it is ok. Then if you would like try porting xemacs or
wait for kdevelop. then remember the command line if your best friend,
belive me.
keep it as simple as possible. It is nice.
stefan
Alain Bonnefoy wrote:
Hello,
I’d like to know what QSSL plan to do about editors, IDE,…
At the moment there is nothing comfortable to edit source code in QRTP. I see that ped receive new functionnalities in every new package but will it become a real source code editor?
I’d like not to talk about vi, qed, … may be some peoples like these, personnaly I don’t.
Wouldn’t it be more interesting to make a portage of some powerfull editors such as xemacs or anything else?
I tried gxedit but first we need a powerfull cpu to cast off the ‘weight’ of the xphoton layer, and second it seems impossible to use it with localized keyboard (for me, with a french keyboard, only alphabetical keys work).
I’d like to know what QSSL plan to do about editors, IDE,…
At the moment there is nothing comfortable to edit source code in QRTP. I see that ped receive new functionnalities in every new package but will it become a real source code editor?
I’d like not to talk about vi, qed, … may be some peoples like these, personnaly I don’t.
Wouldn’t it be more interesting to make a portage of some powerfull editors such as xemacs or anything else?
I tried gxedit but first we need a powerfull cpu to cast off the ‘weight’ of the xphoton layer, and second it seems impossible to use it with localized keyboard (for me, with a french keyboard, only alphabetical keys work).
I’d like to know what QSSL plan to do about editors, IDE,…
At the moment there is nothing comfortable to edit source code in QRTP.
I see that ped receive new functionnalities in every new package but will it
become a real source code editor?
I’d like not to talk about vi, qed, … may be some peoples like these,
personnaly I don’t.
Wouldn’t it be more interesting to make a portage of some powerfull
editors such as xemacs or anything else?
I tried gxedit but first we need a powerfull cpu to cast off the
‘weight’ of the xphoton layer, and second it seems impossible to use it with
localized keyboard (for me, with a french keyboard, only alphabetical keys
work).
Thanks, Alain.
ermm, before we go into a […] contest about the pro’s and con’s of
having an editor with two modes (it beeps or it doesn’t) versus an
operating system with editing capabilities (and lisp interpretation),
there is quite a few good IDE’s out there which compile right out of the
box on RTP. Source Navigator (> http://sources.redhat.com/sourcenav/> ) from
Cygnus (now Redhat) is one of it, and Colin promised a port of KDevelop
“Real Soon Now ™”. Now someone could give Code Crusader
(> http://www.newplanetsoftware.com/jcc> ) a shot and then there should be
enough flavours to please everybody.
-Th
Please can you post some instructions and hints on HOW TO compile Source
Navigator or, better, where binaries for QRTP could be found?
I’d like to know what QSSL plan to do about editors, IDE,…
At the moment there is nothing comfortable to edit source code in QRTP.
I see that ped receive new functionnalities in every new package but will it
become a real source code editor?
I’d like not to talk about vi, qed, … may be some peoples like these,
personnaly I don’t.
Wouldn’t it be more interesting to make a portage of some powerfull
editors such as xemacs or anything else?
I tried gxedit but first we need a powerfull cpu to cast off the
‘weight’ of the xphoton layer, and second it seems impossible to use it with
localized keyboard (for me, with a french keyboard, only alphabetical keys
work).
Thanks, Alain.
Install JED off the CD.
I know this will sound very dumb, but I did that, hoped to get something
useful…
(I was running as root)
How do I RUN JED?
Help on JED (in Helpviewer) was very unhelpful at the top level!
Great reference for macros, etc., but how do I get started??
I know this will sound very dumb, but I did that, hoped to get something
useful…
(I was running as root)
How do I RUN JED?
Help on JED (in Helpviewer) was very unhelpful at the top level!
Great reference for macros, etc., but how do I get started??
Ahhhh… the old `root doesn’t have /usr/local/bin in the PATH
problem’…
jed installs into /usr/local/bin … You can probably figure it out from
there.
I know this will sound very dumb, but I did that, hoped to get something
useful…
(I was running as root)
How do I RUN JED?
Help on JED (in Helpviewer) was very unhelpful at the top level!
Great reference for macros, etc., but how do I get started??
Ahhhh… the old `root doesn’t have /usr/local/bin in the PATH
problem’…
jed installs into /usr/local/bin … You can probably figure it out from
there.
I’d like to know what QSSL plan to do about editors, IDE,…
At the moment there is nothing comfortable to edit source code in QRTP.
I see that ped receive new functionnalities in every new package but will it
become a real source code editor?
I’d like not to talk about vi, qed, … may be some peoples like these,
personnaly I don’t.
Wouldn’t it be more interesting to make a portage of some powerfull
editors such as xemacs or anything else?
I tried gxedit but first we need a powerfull cpu to cast off the
‘weight’ of the xphoton layer, and second it seems impossible to use it with
localized keyboard (for me, with a french keyboard, only alphabetical keys
work).
Thanks, Alain.
ermm, before we go into a […] contest about the pro’s and con’s of
having an editor with two modes (it beeps or it doesn’t) versus an
operating system with editing capabilities (and lisp interpretation),
there is quite a few good IDE’s out there which compile right out of the
box on RTP. Source Navigator (> http://sources.redhat.com/sourcenav/> ) from
Cygnus (now Redhat) is one of it, and Colin promised a port of KDevelop
“Real Soon Now ™”. Now someone could give Code Crusader
(> http://www.newplanetsoftware.com/jcc> ) a shot and then there should be
enough flavours to please everybody.
-Th
Please can you post some instructions and hints on HOW TO compile Source
Navigator or, better, where binaries for QRTP could be found?
Thanks.
get config.guess and config.sub for QNXRTP from ftp.gnu.org,
untar/unzip the sourcenav tarball
…/configure
make
make install
I’ll post the binaries eventually to qnxstart.com, just gotta figure
what all should be included and how that RTP packaging thingy works…
I know this will sound very dumb, but I did that, hoped to get something
useful…
(I was running as root)
How do I RUN JED?
Help on JED (in Helpviewer) was very unhelpful at the top level!
Great reference for macros, etc., but how do I get started??
Ahhhh… the old `root doesn’t have /usr/local/bin in the PATH
problem’…
jed installs into /usr/local/bin … You can probably figure it out from
there.
I think that we can accept these style of editor in MS-DOS or maybe vxworks, but in system like qnx with a graphical interface like photon, sorry we can’t!!!
Do you really think that it’s coherent to use phab for a part of a project and go back to vi for the rest of the project.
It seems that there is two completely different entities in QSSL!
Previously, Stefan Parvu wrote in qdn.public.qnxrtp.devtools:
hi,
From my point of view we do not need ASAP an IDE. We need to build
Asynch library for instance ASAP.
Then many other hot problems which should be solved, many scripts to be
ported to RTP, administration tools and so on. You could try porting w,
or who to RTP.
Emacs is working ok, there is a problem in slow redrawing of menus
sometimes but it is ok. Then if you would like try porting xemacs or
wait for kdevelop. then remember the command line if your best friend,
belive me.
keep it as simple as possible. It is nice.
stefan
Alain Bonnefoy wrote:
Hello,
I’d like to know what QSSL plan to do about editors, IDE,…
At the moment there is nothing comfortable to edit source code in QRTP. I see that ped receive new functionnalities in every new package but will it become a real source code editor?
I’d like not to talk about vi, qed, … may be some peoples like these, personnaly I don’t.
Wouldn’t it be more interesting to make a portage of some powerfull editors such as xemacs or anything else?
I tried gxedit but first we need a powerfull cpu to cast off the ‘weight’ of the xphoton layer, and second it seems impossible to use it with localized keyboard (for me, with a french keyboard, only alphabetical keys work).
Thanks, Alain.
when I talked about emacs I talked about a graphical emacs but a PHemacs not Xemacs.
Alain Bonnefoy <alain.bonnefoy@icbt.com> wrote in message
news:Voyager.001011083520.1454114A@val_22055…
Previously, > pete@qnx.com > wrote in qdn.public.qnxrtp.devtools:
Steve Munnings, Corman Technologies <> steve@cormantech.com> > wrote:
Install JED off the CD.
I know this will sound very dumb, but I did that, hoped to get
something
useful…
(I was running as root)
How do I RUN JED?
Help on JED (in Helpviewer) was very unhelpful at the top level!
Great reference for macros, etc., but how do I get started??
Ahhhh… the old `root doesn’t have /usr/local/bin in the PATH
problem’…
jed installs into /usr/local/bin … You can probably figure it out from
there.
I think that we can accept these style of editor in MS-DOS or maybe
vxworks, but in system like qnx with a graphical interface like photon,
sorry we can’t!!!
Do you really think that it’s coherent to use phab for a part of a project
and go back to vi for the rest of the project.
It seems that there is two completely different entities in QSSL!
Hoy, don’t get all over QSSL’s case about this! Some people prefer text
based editing, some like it more graphical.
If QSSL caters to both groups, why is this a problem??
Editors come in all kinds of flavours. I can usually use whatever tool is
handy, but some are stuck on one editor or another, I think it is good of
QSSL to supply this one (I think they supplied it, not someone else)
I think that we can accept these style of editor in MS-DOS or maybe
vxworks, but in system like qnx with a graphical interface like photon,
sorry we can’t!!!
What are you talking about?
When I use PhAb, I don’t even do the makes from inside PhAB… I do them
from inside JED because JED is smart enough to parse the error output
from the build, and load the file that contains an error and position the
cursor on the appropriate line.
JED is smart enough to understand the ctags format so I can ask it to take
me to a particular function in a project without knowing which file that
function is defined in.
It does syntax highlighting, and it can reformat someone elses C code
into the kind of formatting I prefer.
It’s got all it’s help built in, AND it still works from text mode, which
is handy if I’ve screwed up my config files so Photon won’t run, or
I am working on some embedded system that can’t run Photon to begin with.
Do you really think that it’s coherent to use phab for a part of a project
and go back to vi for the rest of the project.
No… not at all, but you’re ignoring the alternative. `vi’ is not the only
choice.
I think that we can accept these style of editor in MS-DOS or maybe
vxworks, but in system like qnx with a graphical interface like photon,
sorry we can’t!!!
What are you talking about?
When I use PhAb, I don’t even do the makes from inside PhAB… I do them
from inside JED because JED is smart enough to parse the error output
from the build, and load the file that contains an error and position the
cursor on the appropriate line.
JED is smart enough to understand the ctags format so I can ask it to take
me to a particular function in a project without knowing which file that
function is defined in.
It does syntax highlighting, and it can reformat someone elses C code
into the kind of formatting I prefer.
It’s got all it’s help built in, AND it still works from text mode, which
is handy if I’ve screwed up my config files so Photon won’t run, or
I am working on some embedded system that can’t run Photon to begin with.
Do you really think that it’s coherent to use phab for a part of a project
and go back to vi for the rest of the project.
No… not at all, but you’re ignoring the alternative. `vi’ is not the only
choice.
I agree that text mode editors must exist. Of course!
I’m just surprised that so few people think a graphic mode editor could interest some developers.
All tasks could be achieve in text mode, mail, news, audio cd, package managing (gloups! bad example), system info,… but almost all these have graphical front end.
About editors, especially on qnx platforms (qnx4 or qrtp), it seems not be an interesting work.
I think that we can accept these style of editor in MS-DOS or maybe
vxworks, but in system like qnx with a graphical interface like photon,
sorry we can’t!!!
What are you talking about?
When I use PhAb, I don’t even do the makes from inside PhAB… I do them
from inside JED because JED is smart enough to parse the error output
from the build, and load the file that contains an error and position the
cursor on the appropriate line.
JED is smart enough to understand the ctags format so I can ask it to take
me to a particular function in a project without knowing which file that
function is defined in.
It does syntax highlighting, and it can reformat someone elses C code
into the kind of formatting I prefer.
It’s got all it’s help built in, AND it still works from text mode, which
is handy if I’ve screwed up my config files so Photon won’t run, or
I am working on some embedded system that can’t run Photon to begin with.
Do you really think that it’s coherent to use phab for a part of a project
and go back to vi for the rest of the project.
No… not at all, but you’re ignoring the alternative. `vi’ is not the only
choice.
I agree that text mode editors must exist. Of course!
I’m just surprised that so few people think a graphic mode editor could interest some developers.
All tasks could be achieve in text mode, mail, news, audio cd, package managing (gloups! bad example), system info,… but almost all these have graphical front end.
About editors, especially on qnx platforms (qnx4 or qrtp), it seems not be an >interesting work.
I’m not convinced … download Igor’s port of
nedit at QNXfree86 at Sourceforge.net. (graphical,
syntax high lighting a.s.o …)
I’d like to know what QSSL plan to do about editors, IDE,…
At the moment there is nothing comfortable to edit source code in
QRTP.
I see that ped receive new functionnalities in every new package but
will it
become a real source code editor?
I’d like not to talk about vi, qed, … may be some peoples like
these,
personnaly I don’t.
Wouldn’t it be more interesting to make a portage of some powerfull
editors such as xemacs or anything else?
I tried gxedit but first we need a powerfull cpu to cast off the
‘weight’ of the xphoton layer, and second it seems impossible to use it
with
localized keyboard (for me, with a french keyboard, only alphabetical
keys
work).
Thanks, Alain.
ermm, before we go into a […] contest about the pro’s and con’s of
having an editor with two modes (it beeps or it doesn’t) versus an
operating system with editing capabilities (and lisp interpretation),
there is quite a few good IDE’s out there which compile right out of
the
box on RTP. Source Navigator (> http://sources.redhat.com/sourcenav/> )
from
Cygnus (now Redhat) is one of it, and Colin promised a port of
KDevelop
“Real Soon Now ™”. Now someone could give Code Crusader
(> http://www.newplanetsoftware.com/jcc> ) a shot and then there should be
enough flavours to please everybody.
-Th
Please can you post some instructions and hints on HOW TO compile Source
Navigator or, better, where binaries for QRTP could be found?
Thanks.
get config.guess and config.sub for QNXRTP from ftp.gnu.org,
untar/unzip the sourcenav tarball
./configure
make
make install
I’ll post the binaries eventually to qnxstart.com, just gotta figure
what all should be included and how that RTP packaging thingy works…
-Th
This doesn’t seem to work for me…
I got the SN452.tar.gz from redhat plus the config scripts from gnu, but the
source doesn’t compile (for me, at least) out of the box…
Which source were you using? Any chance of those binaries?
Thanks in advance,
James
I’d like to know what QSSL plan to do about editors, IDE,…
At the moment there is nothing comfortable to edit source code in
QRTP.
I see that ped receive new functionnalities in every new package but
will it
become a real source code editor?
I’d like not to talk about vi, qed, … may be some peoples like
these,
personnaly I don’t.
Wouldn’t it be more interesting to make a portage of some powerfull
editors such as xemacs or anything else?
I tried gxedit but first we need a powerfull cpu to cast off the
‘weight’ of the xphoton layer, and second it seems impossible to use it
with
localized keyboard (for me, with a french keyboard, only alphabetical
keys
work).
Thanks, Alain.
ermm, before we go into a […] contest about the pro’s and con’s of
having an editor with two modes (it beeps or it doesn’t) versus an
operating system with editing capabilities (and lisp interpretation),
there is quite a few good IDE’s out there which compile right out of
the
box on RTP. Source Navigator (> http://sources.redhat.com/sourcenav/> )
from
Cygnus (now Redhat) is one of it, and Colin promised a port of
KDevelop
“Real Soon Now ™”. Now someone could give Code Crusader
(> http://www.newplanetsoftware.com/jcc> ) a shot and then there should be
enough flavours to please everybody.
-Th
Please can you post some instructions and hints on HOW TO compile Source
Navigator or, better, where binaries for QRTP could be found?
Thanks.
get config.guess and config.sub for QNXRTP from ftp.gnu.org,
untar/unzip the sourcenav tarball
./configure
make
make install
I’ll post the binaries eventually to qnxstart.com, just gotta figure
what all should be included and how that RTP packaging thingy works…
-Th
This doesn’t seem to work for me…
I got the SN452.tar.gz from redhat plus the config scripts from gnu, but the
source doesn’t compile (for me, at least) out of the box…
Which source were you using? Any chance of those binaries?
Thanks in advance,
James
SN452.tgz
Compiled it’s huge, I’ll have to find a place to post it, let me see
what I can do.
(Bug me next week again if I forget
