|
Elexis API documentationVersion 2.1.6 as of December 11 2011 | |||||||||
PREV NEXT | FRAMES NO FRAMES |
Deprecated Interfaces | |
---|---|
ch.elexis.util.IKonsExtension
use IRangeRenderer and SSDRange |
Deprecated Classes | |
---|---|
ch.elexis.actions.AbstractDataLoaderJob
Die Funktionalität der BackgroundJobs kann seit Eclipse 3.0 von Eclipse-Jobs und Joblisteners übernommen werden. Neuer Code sollte direkt mit Eclipse Jobs arbeiten. |
|
ch.elexis.actions.BackgroundJob
Seit Eclipse 3.0 gibt es direkt im Job-API die Möglichkeit, einen IJobChangeListener einzusetzen, um Über die Beendigung eines Hintergrundprozesses informiert zu werden. Neuer Code sollte lieber diese Technik verwenden anstelle der BackgroundJobs. |
|
ch.elexis.views.BBSView
|
|
ch.elexis.agenda.data.Import_Agenda
|
|
ch.elexis.actions.JobPool
Neuer Code sollte das Eclipse Job API verwenden |
|
ch.elexis.util.KGDrucker
|
|
ch.elexis.matchers.KontaktMatcher
use ch.elexis.exchange.KontaktMatcher |
|
ch.elexis.actions.LazyTreeLoader
|
|
ch.elexis.util.PluginCleaner
do not use |
|
ch.elexis.text.model.Samdas
use SimpleStructuredDocument |
|
ch.elexis.text.model.Samdas.Analyse
|
|
ch.elexis.text.model.Samdas.ECG
|
|
ch.elexis.text.model.Samdas.Finding
|
|
ch.elexis.text.model.Samdas.Image
|
|
ch.elexis.actions.Synchronizer
|
|
ch.elexis.data.Transaction
we don't need this really |
|
ch.elexis.actions.TreeLoader
|
Deprecated Methods | |
---|---|
ch.elexis.data.Konsultation.addXRef(String, String, int, String)
|
|
com.sun.star.comp.beans.OOoBean.clearDocument(boolean)
There is currently no way to dismiss changes, except for loading of the unchanged initial document. Furthermore it is unclear how derived classes handle this and what exactly their state is (e.g. what members make up their state). Calling this method on a derived class requires knowledge about their implementation. Therefore a deriving class should declare their own clearDocument if needed. Clients should call the clearDocument of the deriving class or OOoBean.clear()
which discards the currently displayed document. |
|
ch.rgw.tools.StringTool.flatten(Hashtable, int, Object)
compressmode is always ZIP now. |
|
ch.rgw.tools.StringTool.fold(byte[], int, Object)
|
|
ch.elexis.data.Fall.getArbeitgeber()
|
|
ch.elexis.data.Fall.getArbeitgeberName()
|
|
ch.elexis.data.Fall.getBillingSystemAttribute(String, String)
use getBillingSystemConstant |
|
ch.elexis.core.util.Extensions.getClasses(List Use #getClasses(List instead |
|
ch.elexis.util.Extensions.getClasses(List Use #getClasses(List instead |
|
ch.elexis.importers.HL7.OBX.getDate()
better use obr date for date of sample |
|
ch.elexis.data.Konsultation.getDiagnosen()
Use Konsultation.getReasons() instead |
|
ch.elexis.data.Verrechnet.getEffPreis()
|
|
ch.elexis.data.Patient.getFaelle()
use getCustomerRelations() |
|
ch.elexis.data.Konsultation.getFall()
use getCustomerRelation |
|
ch.elexis.data.Konsultation.getGewinn()
|
|
ch.elexis.data.Konsultation.getMandant()
use getResponsible |
|
com.swtdesigner.ResourceManager.getPluginImage(Object, String)
Use ResourceManager.getPluginImage(String, String) instead. |
|
com.swtdesigner.ResourceManager.getPluginImageDescriptor(Object, String)
Use ResourceManager.getPluginImageDescriptor(String, String) instead. |
|
ch.rgw.tools.StringTool.getStringBounds(String, Graphics)
this ist a dependency to Swing |
|
ch.elexis.data.Konsultation.getUmsatz()
not accurate. use getLeistungen() |
|
ch.elexis.data.Fall.getVersNummer()
user getRequiredString instead |
|
ch.elexis.core.data.IPersistentObject.isDeleted()
use state() |
|
ch.elexis.data.Leistungsblock.isEmpty()
|
|
com.sun.star.comp.beans.OOoBean.isMenuBarVisible()
Clients should use the service com.sun.star.frame.LayoutManager, which can be obtained from a frame, to control toolbars. See also OOoBean.setAllBarsVisible(boolean) . |
|
com.sun.star.comp.beans.OOoBean.isOOoConnected()
This method is not useful in a multithreaded environment. Then all threads accessing the instance would have to be synchronized in order to make is method work. It is better to call OOoBean's methods and be prepared to catch a NoConnectionException. |
|
com.sun.star.comp.beans.OOoBean.isStandardBarVisible()
Clients should use the service com.sun.star.frame.LayoutManager, which can be obtained from a frame, to control toolbars. See also OOoBean.setAllBarsVisible(boolean) . |
|
com.sun.star.comp.beans.OOoBean.isStatusBarVisible()
Clients should use the service com.sun.star.frame.LayoutManager, which can be obtained from a frame, to control toolbars. See also OOoBean.setAllBarsVisible(boolean) . |
|
com.sun.star.comp.beans.OOoBean.isToolBarVisible()
Clients should use the service com.sun.star.frame.LayoutManager, which can be obtained from a frame, to control toolbars. See also OOoBean.setAllBarsVisible(boolean) . |
|
ch.elexis.importers.ExcelWrapper.load(String, int)
use load(InputStream) instead |
|
com.sun.star.comp.beans.OOoBean.paint(Graphics)
|
|
com.sun.star.comp.beans.OOoBean.readExternal(ObjectInput)
|
|
com.sun.star.comp.beans.OOoBean.releaseSystemWindow()
When Component.removeNotify of the parent window of the actual office window is called, then the actions are performed for which this method needed to be called previously. |
|
ch.elexis.data.Konsultation.removeXRef(String, String)
|
|
ch.rgw.crypt.SAT.sendRequest(String, String)
|
|
com.sun.star.comp.beans.OOoBean.setAllBarsVisible(boolean)
Clients should use the service com.sun.star.frame.LayoutManager, which can be obtained from a frame, to control toolbars. For example: com.sun.star.beans.XPropertySet xPropSet = (com.sun.star.beans.XPropertySet) UnoRuntime.queryInterface( com.sun.star.beans.XPropertySet.class, aFrame); com.sun.star.frame.XLayoutManager xLayoutManager = (com.sun.star.frame.XLayoutManager) UnoRuntime.queryInterface( com.sun.star.frame.XLayoutManager.class, xPropSet.getPropertyValue("LayoutManager")); xLayoutManager.showElement("private:resource/menubar/menubar"); |
|
com.sun.star.comp.beans.OOoBean.setMenuBarVisible(boolean)
Clients should use the service com.sun.star.frame.LayoutManager, which can be obtained from a frame, to control toolbars. See also OOoBean.setAllBarsVisible(boolean) . |
|
ch.elexis.data.Verrechnet.setPreis(Money)
use setTP and setFactor |
|
com.sun.star.comp.beans.OOoBean.setStandardBarVisible(boolean)
Clients should use the service com.sun.star.frame.LayoutManager, which can be obtained from a frame, to control toolbars. See also OOoBean.setAllBarsVisible(boolean) . |
|
com.sun.star.comp.beans.OOoBean.setStatusBarVisible(boolean)
Clients should use the service com.sun.star.frame.LayoutManager, which can be obtained from a frame, to control toolbars. See also OOoBean.setAllBarsVisible(boolean) . |
|
com.tiff.common.ui.datepicker.DatePickerCombo.setText(String)
use setDate(date) instead |
|
com.sun.star.comp.beans.OOoBean.setToolBarVisible(boolean)
Clients should use the service com.sun.star.frame.LayoutManager, which can be obtained from a frame, to control toolbars. See also OOoBean.setAllBarsVisible(boolean) . |
|
ch.rgw.tools.StringTool.split(String, String)
obsoleted by java 1.4x 's String.split method. |
|
com.sun.star.comp.beans.OOoBean.writeExternal(ObjectOutput)
|
Deprecated Constructors | |
---|---|
de.ralfebert.rcputils.menus.ContextMenu(StructuredViewer, IWorkbenchPartSite, boolean)
|
|
com.sun.star.comp.beans.OOoBean(OfficeConnection)
Clients could use the getOOoConnection to obtain an OfficeConnection and use it as argument in a constructor for another OOoBean instance. Calling the dispose method of the OfficeConnection or the OOoBean's stopOOoConnection method would make all instances of OOoBean stop working. |
|
Elexis API documentationVersion 2.1.6 as of December 11 2011 | |||||||||
PREV NEXT | FRAMES NO FRAMES |