[9.3] Text coloring for PPx projects?

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Stephen Chu - 28 Sep 2004 15:16 GMT

When I create a new PPx project from the supplied stationeries and set
the "Generate Browser Data From:" to Compiler. Most of the system data
types like OSStatus and CFStringRef are not colored in the editor. Is
this a bug?

If I change the setting to Language Parser, those symbols are then
colored as functions instead of class/enum.

I am having a really tough time getting used to these new "behaviors."
And it makes looking up symbol definition extremely frustrating.

Reply to this Message

MW Ron - 28 Sep 2004 20:11 GMT

>When I create a new PPx project from the supplied stationeries and set
>the "Generate Browser Data From:" to Compiler. Most of the system data
>types like OSStatus and CFStringRef are not colored in the editor. Is
>this a bug?

No but they should be once you compile the source with that information
included.

>If I change the setting to Language Parser, those symbols are then
>colored as functions instead of class/enum.

Report this as a bug.

>I am having a really tough time getting used to these new "behaviors."
>And it makes looking up symbol definition extremely frustrating.

We are working on these and appreciate all feedback so we can tweak
things.

Ron

Signature

Metrowerks Community Forum is a free online resource for developers
to discuss CodeWarrior topics with other users and Metrowerks' staff
-- http://www.metrowerks.com/community --

Ron Liechty - MWRon@metrowerks.com - http://www.metrowerks.com

Reply to this Message

Stephen Chu - 28 Sep 2004 21:40 GMT

> >When I create a new PPx project from the supplied stationeries and set
> >the "Generate Browser Data From:" to Compiler. Most of the system data
[quoted text clipped - 3 lines]
> No but they should be once you compile the source with that information
> included.

Err. Forgot to mention that I did compile everything and still have this
problem.

> >If I change the setting to Language Parser, those symbols are then
> >colored as functions instead of class/enum.
>
> Report this as a bug.

Guess that makes it 2 bugs. :)

> >I am having a really tough time getting used to these new "behaviors."
> >And it makes looking up symbol definition extremely frustrating.
>
> We are working on these and appreciate all feedback so we can tweak
> things.

Will do. But it would be a lot easier if Metrowerks had a online bug
form instead of some email text template that I have to repeatedly
select text and type in new ones.

Reply to this Message

Stephen Chu - 28 Sep 2004 21:44 GMT

> Will do. But it would be a lot easier if Metrowerks had a online bug
> form instead of some email text template that I have to repeatedly
> select text and type in new ones.

Never mind. I find the FormMaker app. :)

Reply to this Message

James W. Walker - 29 Sep 2004 03:59 GMT

> > No but they should be once you compile the source with that information
> > included.
>
> Err. Forgot to mention that I did compile everything and still have this
> problem.

If you use a precompiled header that is not built by your project, then
you won't get the syntax coloring for things in that header.

Reply to this Message

Stephen Chu - 29 Sep 2004 14:13 GMT

> > > No but they should be once you compile the source with that information
> > > included.
[quoted text clipped - 4 lines]
> If you use a precompiled header that is not built by your project, then
> you won't get the syntax coloring for things in that header.

Ah. That's why. Is this new? For I've never noticed this before. But I
didn't notice a lot of other obvious facts in life either...

Guess the old PowerPlant stationeries have their own precompiled
headers. So I used to have all the symbols colored properly.

Reply to this Message

Stephen Chu - 29 Sep 2004 15:14 GMT

OK. I tried to add precompiled header into the project by copying the
needed files from MacHeader Mach-O folder and adding them to my project.
Now I get compile errors on MoreFilesX files. It's complaining 'true'
and 'false' not being defined. I know I can just switch on force C++
compilation. But I am really curious on why using the pre-built
precompiled headers doesn't require me to do that?

Reply to this Message

MW Ron - 29 Sep 2004 17:35 GMT

>> > > No but they should be once you compile the source with that information
>> > > included.
[quoted text clipped - 11 lines]
>compilation. But I am really curious on why using the pre-built
>precompiled headers doesn't require me to do that?

because they are in MacTypes.h and enumerated You must not be including
it.

Ron

Signature

Reply to this Message

Stephen Chu - 29 Sep 2004 18:55 GMT

> >> > > No but they should be once you compile the source with that
> >> > > information
[quoted text clipped - 15 lines]
> because they are in MacTypes.h and enumerated You must not be including
> it.

Actually, I find out that the project stationery uses different
pre-compiled headers for C++ and plain C files.

Reply to this Message

MW Ron - 29 Sep 2004 17:30 GMT

>> > No but they should be once you compile the source with that information
>> > included.
[quoted text clipped - 4 lines]
>If you use a precompiled header that is not built by your project, then
>you won't get the syntax coloring for things in that header.

That isn't true anymore with the language parser, but it is true with
the compiler parser.

Ron

Signature

Reply to this Message

Stephen Chu - 29 Sep 2004 19:03 GMT

> >> > No but they should be once you compile the source with that information
> >> > included.
[quoted text clipped - 7 lines]
> That isn't true anymore with the language parser, but it is true with
> the compiler parser.

I couldn't care less about the language parser in its current form. It
seldom finds the symbols I want. And it often mistakens the type of most
symbols it finds like thinking CFStringRef is a function.

So to me the limitation of requiring the pre-compiled headers to be in
the current project to have the text coloring and other symbol lookup
features to work is really bad. It basically makes the provided or
shared pre-compiled headers useless to me.

Reply to this Message

MW Ron - 29 Sep 2004 19:45 GMT

>> >> > No but they should be once you compile the source with that
>> >> > information
[quoted text clipped - 12 lines]
>seldom finds the symbols I want. And it often mistakens the type of most
>symbols it finds like thinking CFStringRef is a function.

report it as a bug so we can fix it.

>So to me the limitation of requiring the pre-compiled headers to be in
>the current project to have the text coloring and other symbol lookup
>features to work is really bad. It basically makes the provided or
>shared pre-compiled headers useless to me.

Well that is the way it has always been, this is nothing new or buggy.

If you want colorization, you could go to the Find Library and CarbonLib
and add that to the colorization. That will give you quite a bit.

Java has a way to build a dictionary so code completion works great for
Java. But I don't think you'll find that we are that much worse than
anyone else, in C++ especially given the shortness of time. Cocoa is
coming but we still need reports.

Ron

Signature

Reply to this Message

Stephen Chu - 29 Sep 2004 20:39 GMT

> >I couldn't care less about the language parser in its current form. It
> >seldom finds the symbols I want. And it often mistakens the type of most
> >symbols it finds like thinking CFStringRef is a function.
>
> report it as a bug so we can fix it.

Did it already.

> >So to me the limitation of requiring the pre-compiled headers to be in
> >the current project to have the text coloring and other symbol lookup
> >features to work is really bad. It basically makes the provided or
> >shared pre-compiled headers useless to me.
>
> Well that is the way it has always been, this is nothing new or buggy.

The limitation is not documented as far as I can tell. And even the
stationeries come with the product have majority of the symbols missing
the proper color, I called it a bug.

> If you want colorization, you could go to the Find Library and CarbonLib
> and add that to the colorization. That will give you quite a bit.

Hun? How do you "add that to the colorization?"

> Java has a way to build a dictionary so code completion works great for
> Java. But I don't think you'll find that we are that much worse than
> anyone else, in C++ especially given the shortness of time. Cocoa is
> coming but we still need reports.

Well. I don't use code completion. Nor do I use Java or Cocoa. So I
really can't compare them. All I know is the browser data doesn't do
what I think and the documentation claims to do.

Frankly, I don't mind adding my own precompiled headers to the project.
It gives me more coffee breaks when rebuilding the project. But the
stationeries should be setup so they have their own precompiled headers
like the old PowerPlant ones.

Reply to this Message

MW Ron - 29 Sep 2004 22:03 GMT

>> report it as a bug so we can fix it.
>
>Did it already.

Thanks !!

>The limitation is not documented as far as I can tell. And even the
>stationeries come with the product have majority of the symbols missing
>the proper color, I called it a bug.

I'm not sure what you mean by this, I don't recall this, is it in your
bug report. Since the stationery usually uses the language parser.

By the way, while I'm thinking of it, did you trash your
~/library/preferneces/Metrowerks preferences sometimes those get
corrupted and affect this. (do so before launching CodeWarrior or you
just get the corrupted ones restored on exit.)

>> If you want colorization, you could go to the Find Library and CarbonLib
>> and add that to the colorization. That will give you quite a bit.
>
>Hun? How do you "add that to the colorization?"

In the Global preferences.... you can add keywords or a whole file,
simply add the CarbonLib file it just has the keywords for Carbon
Functions.

>> Java has a way to build a dictionary so code completion works great for
>> Java. But I don't think you'll find that we are that much worse than
[quoted text clipped - 4 lines]
>really can't compare them. All I know is the browser data doesn't do
>what I think and the documentation claims to do.

But it does.... I need to look more into this I guess.

Ron

Signature

Reply to this Message

Mac Forum / Programming / CodeWarrior / September 2004

[9.3] Text coloring for PPx projects?