Evtl. solltest du mal ein bisschen mit der Widget Galery rumspielen. Sie kann leider nichts, die relevanten Sachen (Session View etc..) sind leider sehr sehr EMPTY ! Geht wohl leider auch nicht anders, die benötigen nämlich die tolle Business Logik um einen sinnvollen Inhalt darstellen zu können. Dazu muss man dann sowieso Saros starten und eine Session aufbauen, damit man die "tollen" Inhalte sehen kann, im Standalone startup zeigt dir die Gallery kaum was an.
Björn hat das Plugin geschrieben, wo alle benötigten Klassen als Singleton Müll im Pico Container vorlagen, die man sich über SarosPluginContext.initComponent(...) dann holen kann. Guck dir mal Holgers Arbeit an ... Zitat: Elemente der gra schen Ober ache, die sich auf eine aktive Sitzung beziehen, sollten dynamisch beim Starten der Sitzung erzeugt werden. Dies ermoglicht die Entfernung weiterer Klassen aus dem PicoContainer des SarosContexts. Dem kann ich nur zustimmen. Nochmal, du kannst die Business Logik vom GUI trennen, aber nicht das GUI von der Business Logik, irgendwas muss es ja anzeigen. Und ob du die WG standalone startest, oder innerhalb von Saros ... laufzeitmäßig ist es fast egal, da auch im Standalone Modus Saros gestartet werden muss. Mein Fazit: Wir müss(t)en hier Code warten, den sogut wie eh keiner benutzt. Im moment ist die WG eher eine Selbstverherrlichung von Björns selbstgeschriebenen Widgets / Composites ... mehr aber auch leider nicht. Ich aktivier nächste Woche mal wieder den Jenkins Job für die WG. Mal gucken wann die ersten Entwickler von den Fehlermeldungen der CI genervt sind. Just my 2 cents ... Am 23.11.2012 18:43, schrieb Zieris, Franz: > Hi, > >> My conclusion: >> >> Hit the mighty delete button for the whole plugin. It only shows you >> the available wizards. Just playing around with Saros has almost the same >> effect. > I strongly vote against deleting the Widget Gallery. I see its biggest > benefit in the separation of business logic and GUI. If you want to replace > "Using the Widget Gallery" with "Simply use Saros and click around" you're > always in trouble of bringing Saros in the required state to display certain > GUI elements representing that state. If the state you're interested in > requires to set-up a session and execute a number of steps until the required > dialog pops up, you'll get annoyed after the third implement-and-verify cycle. > >> There are no "export" statements in the Saros Plugin >> for the new classes >> so you cannot even use them in the WidgetGallery (OSGI concept). > I talked to Björn Kahlert about this, and he mentioned three ways to handle > this: > (1) Adding more export statements -- very tedious. > (2) Reintegrate the Widget Gallery into the Saros main project -- not > favorable. > (3) Making the Widget Gallery a "Buddy Plug-in" of Saros, so that no export > statements need to be maintained. > > Number (3) is obviously the best option. The required changes would be: > > Into WidgetGallery's Manifest add the line: > Eclipse-RegisterBuddy: de.fu_berlin.inf.dpp > > And in Saros's Manifest: > Eclipse-BuddyPolicy: registered > > Opinions? > > Franz > > > > > -----Original Message----- > From: Stefan Rossbach [mailto:srossb...@arcor.de] > Sent: Tuesday, November 20, 2012 11:51 PM > To: Zieris, Franz > Cc: Kevin Funk; erik.ku...@gmail.com; dpp-devel@lists.sourceforge.net > Subject: Re: [DPP-Devel] Fixing bug 3572488 / Gerrit access > > Hi all, > > I just started to fixing the compile errors and gave up after 5 minutes. > > Problem: > > Writing a dummy IChat implementation (that is actually not the hard part) > > The logic has somewhat changed to send a chat message (fixing this would > require changes > to the Saros plugin again). > > Last but not least: There are no "export" statements in the Saros Plugin > for the new classes > so you cannot even use them in the WidgetGallery (OSGI concept). > > My conclusion: > > Hit the mighty delete button for the whole plugin. It only shows you > the available wizards. Just playing around with Saros has almost the same > effect. > > BR, > Stefan > > Am 16.11.2012 15:42, schrieb Kevin Funk: >> On Friday 16 November 2012, 14:54, Zieris, Franz wrote: >>> Hi Kevin, >>> >>>> The compilation errors are from >>>> 'de.fu_berlin.inf.dpp.ui.widgetGallery', which apparently is not covered >>>> by >>>> CI, right? >>> Yes, you're right. The widgetGallery is a tool for developers, and its code >>> is not relevant for the productive code of Saros. And unlike the JUnit and >>> STF code it is also not a necessary part for ensuring Saros's integrity. >>> Thus, there is no need to import de.fu_berlin.inf.dpp.ui.widgetGallery in >>> your Eclipse workspace. And even if you do so, despite these errors you >>> should be able to run and test your local Saros instances anyway. >>>> Does it make sense to fix the widgetGallery errors first? Or is that sub- >>>> project deprecated anyway? >>> Its deprecation is nothing that has been seriously considered yet, but >>> putting it in second place is some kind of pre-stage of deprecation. As a >>> countermeasure I already did some maintenance in September (see [1]), but >>> as you pointed out, the recent chat-related patches didn't take care of the >>> widgetGallery, thus introducing unrecognized or underrated compilation >>> errors. >>> >>> Too sum things up: Of course you're free to provide a patch for fixing the >>> widgetGallery as well. And if you don't, I'll do it during the next days. >>> However, thanks for bringing the widgetGallery back to my mind! >>> >>> Best Regards, >>> Franz >>> >>> >>> [1] http://saros-build.imp.fu-berlin.de/gerrit/293 >> Feel free to do so. I just tried to rebase the widgetGallery stuff onto the >> new changes in master but failed to do so - it requires a lot of insight in >> the way the new IChat-based stuff works. I cannot come up with a way to >> create >> a ChatControl instance without having a session object. >> >> I'll postpone our changes until that works. As it provides a great way to >> test >> our new feature. >> >> Greets >> ------------------------------------------------------------------------------ LogMeIn Rescue: Anywhere, Anytime Remote support for IT. Free Trial Remotely access PCs and mobile devices and provide instant support Improve your efficiency, and focus on delivering more value-add services Discover what IT Professionals Know. Rescue delivers http://p.sf.net/sfu/logmein_12329d2d _______________________________________________ DPP-Devel mailing list DPP-Devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dpp-devel
