|
|||||||||
PREV NEXT | FRAMES NO FRAMES |
org.gnome.gtk.AboutDialog
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.AboutDialogActivateLinkMethod
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.Accelerator
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.AccelGroup
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.AccelLabel
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.Accessible
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.Action
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.ActionEntry
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.ActionGroup
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.Widget.addListener(DragTargetListener)
instead.
Widget.addListener(DragOriginListener)
instead.
org.gnome.gtk.Adjustment
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.Alignment
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.pango.Alignment
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.gtk.Allocation
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.Arrow
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.ArrowType
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.AspectFrame
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.atk.AtkObject
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.gtk.AttachOptions
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.pango.AttrColor
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.pango.AttrFloat
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.pango.AttrFontDesc
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.pango.Attribute
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.pango.AttrInt
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.pango.AttrIterator
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.pango.AttrLanguage
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.pango.AttrList
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.pango.AttrShape
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.pango.AttrString
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.pango.AttrType
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.gtk.Bin
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.BindingSet
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gdk.Bitmap
.org.gnome.gtk.Box
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.Button
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.ButtonBox
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.ButtonBoxStyle
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.ButtonsType
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.Calendar
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.CalendarDisplayOptions
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.CellLayout
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.CellLayoutHelper
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.CellRenderer
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.CellRendererAttribute
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.CellRendererCombo
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.CellRendererPixbuf
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.CellRendererProgress
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.CellRendererText
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.CellRendererToggle
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.CellView
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.CheckButton
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.CheckMenuItem
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.Clipboard
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gdk.Color
.org.gnome.pango.Color
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.gtk.ColorButton
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gdk.Colormap
.org.gnome.gtk.ColorSelection
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.ColorSelectionDialog
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.ComboBox
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.ComboBoxEntry
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.Container
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.pango.Context
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.gtk.CornerType
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.pango.Coverage
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.pango.CoverageLevel
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.gtk.Curve
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.DataColumn
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.DataColumnBoolean
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.DataColumnDouble
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.DataColumnIconSize
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.DataColumnInt
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.DataColumnLong
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.DataColumnObject
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.DataColumnPixbuf
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.DataColumnStockItem
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.DataColumnString
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.DataRow
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gdk.Device
.org.gnome.gtk.Dialog
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.DialogFlags
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.pango.Direction
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.gdk.Display
.org.gnome.gdk.DragContext
.DragTargetListener
instead.DragOriginListener
instead.org.gnome.gdk.Drawable
.org.gnome.gtk.DrawingArea
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.Editable
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.EditableHelper
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.pango.EllipsizeMode
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.gtk.Entry
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.EntryCompletion
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gdk.Event
.org.gnome.gdk.EventAny
.org.gnome.gtk.EventBox
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gdk.EventButton
.org.gnome.gdk.EventClient
.org.gnome.gdk.EventConfigure
.org.gnome.gdk.EventCrossing
.org.gnome.gdk.EventDND
.org.gnome.gdk.EventExpose
.org.gnome.gdk.EventFocus
.org.gnome.gdk.EventKey
.org.gnome.gdk.EventMask
.org.gnome.gdk.EventMotion
.org.gnome.gdk.EventNoExpose
.org.gnome.gdk.EventOwnerChange
.org.gnome.gdk.EventProperty
.org.gnome.gdk.EventProximity
.org.gnome.gdk.EventScroll
.org.gnome.gdk.EventSelection
.org.gnome.gdk.EventSetting
.org.gnome.gdk.EventType
.org.gnome.gdk.EventVisibility
.org.gnome.gdk.EventWindowState
.org.gnome.gtk.Expander
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gdk.ExtensionMode
.org.gnome.gtk.FileChooser
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.FileChooserAction
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.FileChooserButton
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.FileChooserDialog
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.FileChooserError
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.FileChooserException
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.FileChooserWidget
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.FileFilter
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.FileFilterFlags
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.FileSelection
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.DragContext.finish(boolean, boolean, int)
org.gnome.gtk.Fixed
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.pango.Font
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.gtk.FontButton
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.pango.FontDescription
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.pango.FontFace
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.pango.FontFamily
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.pango.FontMask
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.pango.FontMetrics
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.gtk.FontSelection
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.FontSelectionDialog
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.Frame
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gdk.Function
.org.gnome.gtk.GammaCurve
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gdk.GC
.org.gnome.gdk.Geometry
.Value
of the given child property (name).
Widget.getDragData(DragContext, Atom, int)
getColumnCount
instead.
Device.getDevices()
instead.
TreeView.getSearchDataColumn()
method.
Window.getWindowAtPointer()
.
org.gnome.pango.GlyphString
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.gtk.Gtk
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.GtkInitException
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.GtkObject
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.GtkStockItem
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.HandleBox
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.HBox
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.HButtonBox
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.Widget.highlight()
.
org.gnome.gtk.HPaned
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.HRuler
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.HScale
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.HScrollBar
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.HSeparator
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.atk.Hyperlink
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.gtk.IconFactory
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.IconInfo
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.IconLookupFlags
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.IconSet
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.IconSize
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.IconTheme
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.IconView
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gdk.Image
.org.gnome.gtk.Image
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.ImageMenuItem
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.ImageType
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.IMContext
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.IMContextSimple
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.IMMulticontext
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.InputDialog
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.Invisible
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.Item
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.ItemFactory
to create a menu.org.gnome.gtk.Justification
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gdk.Keymap
.org.gnome.gtk.KeySnoopMethod
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gdk
.org.gnome.gtk.Label
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.pango.Language
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.atk.Layer
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.gtk.Layout
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.pango.Layout
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.pango.LayoutLine
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.gtk.ListStore
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.Menu
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.MenuBar
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.MenuDirectionType
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.MenuItem
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.MenuShell
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.MenuToolButton
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.MessageDialog
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.MessageType
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.Misc
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.Notebook
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.ObjectDestroyedException
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.atk.ObjectFactory
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.gtk.ObjectFlags
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.ComboBox
in gtk 2.3ComboBoxEvent
instead.ComboBoxListener
instead.org.gnome.gtk.PackType
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.Paned
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gdk.PangoAttrEmbossed
.org.gnome.gdk.PangoAttrStipple
.org.gnome.gdk.Pixbuf
.org.gnome.gdk.PixbufAnimation
.org.gnome.gdk.PixbufAnimationIter
.org.gnome.gdk.PixbufError
.org.gnome.gdk.PixbufFormat
.org.gnome.gdk.PixbufLoader
.org.gnome.gdk.PixbufRotation
.org.gnome.gdk.Pixmap
.org.gnome.gtk.Plug
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gdk.Point
.org.gnome.gtk.PolicyType
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.PositionType
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.Preview
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.PreviewType
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.Progress
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.ProgressBar
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.ProgressBarOrientation
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.RadioAction
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.RadioActionEntry
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.RadioButton
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.RadioMenuItem
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.RadioToolButton
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.Range
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.RcStyle
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.pango.Rectangle
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.gdk.Region
.org.gnome.atk.Registry
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.gtk.ReliefStyle
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.Widget.removeListener(DragTargetListener)
instead.
Widget.removeListener(DragOriginListener)
org.gnome.gtk.ResizeMode
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.atk.Role
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.gtk.Ruler
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.Scale
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.pango.Scale
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.gdk.Screen
.org.gnome.gtk.ScrollBar
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.ScrolledWindow
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gdk.Segment
.org.gnome.gtk.SelectionData
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.SelectionMode
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.Separator
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.SeparatorMenuItem
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.SeparatorToolItem
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.AboutDialog.getArtists()
instead.
AboutDialog.getDocumenters()
instead.
TextView.setPixelsBelowLines(int)
instead.
TreeView.setSearchDataColumn(org.gnu.gtk.DataColumn)
method.
org.gnome.gtk.Settings
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.AboutDialog.getWebsite()
.
org.gnome.gtk.ShadowType
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.SimpleList
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.SizeGroup
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.SizeGroupMode
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.SortType
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gdk.Span
.org.gnome.gtk.SpinButton
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.SpinButtonUpdatePolicy
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.SpinType
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.atk.StateSet
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.gtk.StatusBar
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.pango.Stretch
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.gtk.Style
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.pango.Style
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.pango.TabAlign
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.pango.TabArray
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.gtk.Table
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.TargetEntry
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.TearoffMenuItem
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.TextAppearance
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.TextAttributes
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.TextBuffer
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.TextChildAnchor
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.TextDirection
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.TextIter
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.TextMark
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.TextSearchFlags
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.TextTag
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.TextTagTable
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.TextView
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.ToggleAction
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.ToggleActionEntry
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.ToggleButton
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.ToggleToolButton
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.ToolBar
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.ToolButton
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.ToolItem
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.ToolTips
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.TreeIter
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.TreeModel
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.TreeModelFilter
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.TreeModelFilterVisibleMethod
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.TreeModelSort
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.TreePath
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.TreeRowReference
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.TreeSelection
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.TreeSelectionForEach
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.TreeSortable
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.TreeSortableHelper
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.TreeStore
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.TreeView
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.TreeViewColumn
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.TreeViewColumnSizing
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.TreeViewRowSeparatorMethod
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.UIManager
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.UIManagerItemType
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.pango.Underline
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.Widget.unHighlight()
.
org.gnome.gtk.UpdateType
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.pango.Variant
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.gtk.VBox
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.VButtonBox
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.Viewport
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gdk.Visual
.org.gnome.gtk.VPaned
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.VRuler
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.VScale
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.VScrollBar
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.VSeparator
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.pango.Weight
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.org.gnome.gtk.Widget
,
though be aware that the API may be considerably different.org.gnome.gdk.Window
.org.gnome.gtk.Window
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gdk.WindowAttr
.org.gnome.gtk.WindowGroup
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.WindowPosition
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.gtk.WrapMode
.
You should be aware that there is a considerably different API
in the new library: the architecture is completely different
and most notably internals are no longer exposed to public view.org.gnome.pango.WrapMode
.
As this package was never fully implemented in java-gnome 2.x,
however, any new code written will have a considerably different
public API.
|
|||||||||
PREV NEXT | FRAMES NO FRAMES |