Stuff Michael Meeks is doing

Dear Sir / Madam,
	Recently I had the pleasure of obtaining one of your fruit
yoghurts, in the square configuration with an aluminized plastic top.
I eagerly set to peeling the preservative skin from it's expected
adhesive grip to the material below. Imagine my surprise to discover
whilst engaged upon this task what appeared to be some sort of rivet
like contraption twixt sheet and body welding them inseparably. As one
can well imagine this severely impeded my peeling progress, which
clearly must proceed with caution owing to the well documented bad
luck that plagues those who rip such unblemished coverings.
	So; having peeled many a pot I have never been so appalled with
this blasphemous neologism of non-uniform extra methods of adhesion.
Indeed despite scrupulous care my lid became multiply perforated,
condemning me to who knows what horrors! I have taken to hiding
beneath my bed in disgrace, whence my mother brings me periodic
refreshment.
	Hard as it is to write in such confines, I beg to be informed
as to whether this is all part of a fiendish German plot to cripple
this great Nations fortuity ? and indeed whether anything can be done
about my sorry predicament ?!
	Yours Faithfully,

Dear Sir / Madam,
	The other day I was thrilled to receive the most enormous
cylindrical tin of Roses chocolates, with your bold emblem stamped in
imperial red on its rind. Indeed, the smell that arose to my eager
nostrils as I wrenched the lid from its fixing was delicious, the
aroma assaulting my nostrils as of a chocolate smorgasboard, exciting
and fresh as if for the first time.
	However, in this instance it was different. After sating my
initial desire I held aloft a cursory morsel twixt finger and thumb
and, after a moments uffish thought, a horrifying realization hit me.
My worst fears were quickly confirmed by a rummage in the receptacle:
there are No chocolates with a black wrapping. There were many
beautiful chocolates with a white wrapping, some yellow, some green
but no black! Suddenly the sweet taste in my mouth turned to wax, and
a sickening feeling struck me.
	How can we as a forward looking, vibrant, pivotal community of
communities move forward in tackling the obscene and institutional
racism in our society if we can't get this simple thing right ? How
can the police force be beaten to its senses, the teachers re-educated
and the imperialist walls demolished if we cannot even achieve some
sort of racial balance in our chocolate wrappers !?
	Yours disgustedly,

(setq kill-emacs-query-functions
      '(lambda nil
         (y-or-n-p "Are you sure you want to quit? ")))

	GtkWidget *widget;
	widget = bonobo_widget_new_control ("file:/home/me/myimage.jpeg", NULL);

 "GNOME is an open, free, and productive desktop environment that sparks
  innovation and excitement among users and developers worldwide.
  Microsoft Windows is not."
                             -- Sun Microsystems

• a [n] = b [n++];
• a = (a = 1) + 2;
• a = b [a++] = c;
• a = b = a++;
• a [i++] = i;

• Lets totaly re-think the user interface',
• 'A slightly different mental picture'
• 'It would seem that this idea might work better in several layers or "clusters" and that it would fit just dandily onto .dxf objects and into a 3d dome that rotated about the user
• Community "whiteboard": a pre-code experiement

* Rational
	For the last week and a bit I have been re-writing the UI
handler code, the fruits of my labours have been growing in CVS. But
first, a summary of some of the problems I dimly remember with the
old UI handler:
        a) Huge IDL interface, massive stubs / skel contribution
        b) No status bar support
        c) Doesn't allow menu / toolbar editing a-la MS Office
        d) No  cmd / widget separation for menus / toolbars
        e) No Help Menu support
        f) Leaks memory around the place
        g) Out of order merging may be bad.
        h) Non expandable
        i) Nasty placeholders
        j) Broken paths with translations
	k) Broken position double accounting
	l) No K/B accelerator merging
        And probably some more I havn't discovered yet. Still, the old
UI handler contained a large corpus of useful code, it was mostly
frustrated by its API and structure.
* Nice Features
	So; the new UI handler fixes most of the above and adds a lot
of nice features people had requested, eg. Placeholders that can
(optionaly) add separators at top and bottom when they are occupied.
Also there is proto global keybinding support so many different
components can merge keybindings into the same app.
	Another nice feature is the cmd / widget separation that Jody
suggested to me. In fact, this makes it easy to make the whole thing
editable. Either way, lets say we have an operation with id = 'Bold'.
We have a toggle menu item and 2 toggle toolbar items with id == 'Bold'.
Then when we toggle any of these all of them update their state.
	Another type of command is the 'Verb', all menu items and many
single press toolbar items are implemented via verbs such as 'Open',
'Close', 'SaveAs' etc. This essentialy means that anything that can be
done by the menu system can be automated via the CORBA API with no
need to write idl. It also means that advanced features can be exposed
as verbs an ( in future ) the user could add new commands into their
menus and toolbars with a GUI ( much like office does ).
* How it works
	The master model of the UI is stored in an XML tree internaly.
As new toolbars and menus are merged into the UI the model is updated,
signals are emitted on nodes 'overridden', 'reinstated', 'removed'.
The merging code is separated into bonobo-ui-xml.[ch].
	As the trees are merged dirty bits are set on nodes that have
been altered. After the merge this information is used to re-build
those parts of the UI that need it.
	Currently there is no dtd for the xml, however the source is
rather trivial, and there are plenty of examples in my test case
bonobo/test-app. I will be writing one ASAP.
	The tree can be queried and manipulated via a CORBA API, in
addition to this controls can be inserted into the API.
* State of play
	The UI handler is rapidly moving towards a stage where we can
feasibly do a switch to it from the old code. I am however writing a
compatibility API since this shouldn't be too tough and will make the
transition far easier and sweeter. I have tagged CVS with
'BEFORE_NEW_UI_HANDLER' but this is simply to enable me to do some
more destructive pruning of unused features in the old UI handler.

	Bonobo_PersistStream stream = some_moniker_fn ("file:/demo/a.jpeg", "IDL:Bonobo/PersistStream:1.0");

	Bonobo_Embeddable stream = some_moniker_fn ("file:/demo/a.jpeg", "IDL:Bonobo/Embeddable:1.0");

	if (0)
		return *(&_ORBIT_retval);

• They wanted the Qudos of having sold their property to support the needy in the Church, but they didn't want to have to part with all of it.
• They deliberately lied to the apostles, telling them that they had given them all the money raised from the sale. [ clearly here the money is not important, Peter says 'was it not yours before you sold it ?' ]
• They clearly did not believe that God actualy knew their every word before they spoke it and the thoughts of their hearts.
• They deliberately decieved their brothers, clearly cocking a snook at God's law.
• They refused to trust that God could supply their every need and that it was only of what God had given them that they were giving.

MyCorbaStruct MyObject_MyMethod (MyObject *_obj,
                                 CORBA_Environment *ev);

'* const' clean modules:
        glib, gtk+, gdk-pixbuf, pango, bonobo, glade, eog, 
Used in:
        gnumeric  - 357
        gnome-vfs  - 33 only meta-keys ( seemingly added by Darin )
        gnome-libs - 32 lots of argv
        ORBit      - 14 misc.
        gnome-core - 13 mostly argv.
        libole2    -  3 an accident.
        beast      -  3
        guppi3     -  2
        gnome-games - 2
        gnome-print - 1