Dermot Musgrove wrote:
> However I think that buttons should be GtkButton _or_ GnomeStockButton so
> that they can be seen to be different widgets (as they are).
Gnome uses a GtkButton for the stock buttons.
I think it would have been better if there was a GnomeButton widget, which
was similar
Martijn van Beers wrote:
>
> On Sat, Nov 20, 1999 at 12:22:06PM +0100, Arnaud Charlet wrote:
> > > I have to agree with Damon here. The problems in the XML file are
> > > barely a problem.
> >
> > Indeed, and other tools are quite happy when the format *doesn't* change
> > ;-)
>
> Well, don't
Miguel de Icaza wrote:
>
> > > Indeed, and other tools are quite happy when the format *doesn't* change ;-)
> >
> > Well, don't worry. I'm starting my own gui builder where I can do
> > all the things I couldn't in glade.
>
> Sounds like a waste of time. You could have just added a different IO
On Sat, Nov 20, 1999 at 08:10:22AM -0600, Miguel de Icaza wrote:
> > Well, don't worry. I'm starting my own gui builder where I can do
> > all the things I couldn't in glade.
> Sounds like a waste of time. You could have just added a different IO
> backend to Glade.
The xml format is definitely
> > Indeed, and other tools are quite happy when the format *doesn't* change ;-)
>
> Well, don't worry. I'm starting my own gui builder where I can do
> all the things I couldn't in glade.
Sounds like a waste of time. You could have just added a different IO
backend to Glade.
+--
> I have to agree with Damon here. The problems in the XML file are
> barely a problem.
Indeed, and other tools are quite happy when the format *doesn't* change ;-)
Arno
+-+
To unsubscribe from this list, send a message to [EM
On Sat, Nov 20, 1999 at 12:22:06PM +0100, Arnaud Charlet wrote:
> > I have to agree with Damon here. The problems in the XML file are
> > barely a problem.
>
> Indeed, and other tools are quite happy when the format *doesn't* change ;-)
Well, don't worry. I'm starting my own gui builder where
Hi Martijn,
Martijn van Beers wrote:
>
> here goes:
>
> 1) The tag and it's children. I've said this before, this
>shouldn't be in the xml file. None of the information is useful
>for applications that want to work with the interface described in
>the xml file. They are all project
here goes:
1) The tag and it's children. I've said this before, this
shouldn't be in the xml file. None of the information is useful
for applications that want to work with the interface described in
the xml file. They are all project settings belonging in some
.ini like file, along
Maybe a better nesting of the tags would be something like:
instead of the widget -> widget -> child nesting we have now.
James.
--
Email: [EMAIL PROTECTED]
WWW: http://www.daa.com.au/~james/
On Thu, 18 Nov 1999, Damon Chaplin wrote:
> Mar
> > I don't think any of them are major problems, warranting a complete
> > rewrite. I think we should forget about switching to a new SGML format
> > for a while. If in the future it becomes really obvious that we should
> > be doing it a certain way, then we can switch. But I don't think it is
On Thu, Nov 18, 1999 at 09:44:31PM +, Damon Chaplin wrote:
> I don't think any of them are major problems, warranting a complete
> rewrite. I think we should forget about switching to a new SGML format
> for a while. If in the future it becomes really obvious that we should
> be doing it a cer
Martijn van Beers wrote:
>
> here goes:
>
> 1) The tag and it's children. I've said this before, this
>shouldn't be in the xml file. None of the information is useful
>for applications that want to work with the interface described in
>the xml file. They are all project settings bel
On Thu, Nov 18, 1999 at 02:09:12AM +, Dermot Musgrove wrote:
> Martijn van Beers wrote:
> >Putting it in the xml file is like putting the source in that file
> >too, so we don't have too many files. It describes a totally
> >different sort of information, it should not be there.
>
14 matches
Mail list logo
