[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Renaissance menus on OS X ?

From: Helge Hess
Subject: Re: Renaissance menus on OS X ?
Date: Fri, 03 Jan 2003 17:19:00 +0100
User-agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.3a) Gecko/20021212

Nicola Pero wrote:
...as with so any things in the post-NeXT world :-) o.k., that makes sense
now. I think what would be a good thing to have, however, would be a "base"
set of gsmarkup files which do the same as a "new project" in Interface
builder does - i.e. come with all the standard menus attached so you just
add your own at the end. Alterting the example so that the gsmarkup
file was loaded before application main rather than in a delegate might
also be advantageous if you really wnat people to do it at that point, as I
suspect that an awfull lot of code is written by taking an example and
modifying it.

Yes.  Good idea!

I've been thinking about adding a 'template' application.

Hm, I'm not sure what you mean. Anyway, "standard components" can be easily build using "WO reusable components". Those can even have parameters, eg:

  <var:embed component="DefaultMenu" title="NSApp.name"/>

Think of it like using a .nib as a view in another .nib.

I added a new <image> tag for this, and documented it.

Something like

<image name="GNUstep" />

I would suggest using "<img src=.../>" and adding a NSURL subclass for resources (eg gsresource://mainbundle/GNUstep.gif). The src would need to be relative to the document (gsresource://mainbundle/MyPage.gsmodel) and we could use "img src="GNUstep.gif".
Easy todo with NSURL.

<window class="MyWindow" title="Hello" width="200" height="4000">
  <!-- some views here -->

then the system when decoding the <window> tag could plainly simply
allocate it of class MyWindow (assuming it exists and it is a subclass of
NSWindow) instead of simply NSWindow.

"class" should be used for CSS ;-) But besides that, yes, IMHO this would be correct (MyWindow class used in a window "mapping" context).


reply via email to

[Prev in Thread] Current Thread [Next in Thread]