Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion Groups
General
GeneralPortable MacsHardwareNetworking
Applications
Mac ApplicationsEudoraFirefox / MozillaInternet ExplorerOutlook ExpressMS OfficeEntourageExcelPowerPointWordVirtual PCMedia PlayerOther MS Products
Programming
Mac ProgrammingCodeWarriorPerl
Country Specific
Australian Mac GroupUK Mac Group

Mac Forum / Programming / CodeWarrior / January 2004



Tip: Looking for answers? Try searching our database.

PowerPlant & Interface Builder

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
Jonathan Hoyle - 15 Jan 2004 21:38 GMT
I haven't kept up with the PowerPlant side of things, so I figure I'd
ask here...

Will PowerPlant be updated so that it interfaces with Interface
Builder's .nib files?  I know Metrowerks always had their own GUI
generating procedure for PowerPlant, but it seems that Apple is pretty
much defining Interface Builder as THE standard GUI creator.  And
since ProjectBuilder already uses it, and I know CodeWarrior can as
well, a next logical step might be to re-implement PowerPlant to work
with .nibs ainstead of ppob's.

I know that this would be a major architectural change, but remember
too that there would be a whole lot less code to write for PowerPlant
as well, since so much of the behavioral code for these objects can be
removed (as it is handled by the OS).  PP becomes a thinner C++ layer
overtop of standard .nib controls, rather than the more involved
interfacing with resources that it currently does.

Not having a  lot of experience with PP, I can say that I would be
much more inclined to use PP if I knew it was supported by a dynamic
GUI generator sanctioned by Apple.  Currently I use RealBasic to
easily create my GUI's, and write my real C++ code in CodeWarrior
shared libraries (works for both Windows & Mac).

If Metrowerks doesn't plan to do integrate PowerPlant with Interface
Builder, I would recommend for you to create a new framework which
does, since I would worry about PowerPlant's long-term viability in a
world of rapid GUI generators.

Thanks for listening.

Jonathan Hoyle
Gene Codes Corporation
MW Ron - 16 Jan 2004 22:01 GMT
>I haven't kept up with the PowerPlant side of things, so I figure I'd
>ask here...
[quoted text clipped - 24 lines]
>does, since I would worry about PowerPlant's long-term viability in a
>world of rapid GUI generators.

Thanks for the constructive advice.  I was waiting to see if others
pipped in or not before replying.  Currently you can use a utility
(provided with CodeWarrior) to change the NIB files to XML that PPx can
use.   I really don't have much I can say because of the limits of the
SEC other than I don't think you have said anything that hasn't been
discussed internally.

Ron

Signature

Metrowerks, maker of CodeWarrior   -  "Software Starts Here"  
Ron Liechty - MWRon@metrowerks.com - <http://www.metrowerks.com>

Jonathan Hoyle - 19 Jan 2004 20:41 GMT
> Thanks for the constructive advice.  I was waiting to see if others
> pipped in or not before replying.  Currently you can use a utility
[quoted text clipped - 4 lines]
>
> Ron

Thanks, Ron.  I can certainly understand if you cannot discuss it
further than you have.  That it has already been discussed internally
is sufficient for me, as I just did not want Metrowerks to miss
considering the option.  I imagine there are a number of internal
reasons why and why not make such a jump, and a decision of that
magnitude would obviously not be taken lightly.

As for the .nib to XML approach, it doesn't not give you the dynamic
nature that Interface Builder or RealBasic give you, which is its
richest reward.

Thanks for your time.

Jonathan Hoyle
Gene Codes Corporation
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.