So are you saying the javascript is loading correctly and it is just that you can't get the code to work? I thought you were saying that you couldn't get the code to load in the gadgets by editing shindig.properties.
On Sat, Sep 29, 2012 at 2:14 AM, Christian Fischer <flyinghu...@web.de>wrote: > Hi, > > my custom feature is also in the extras-repository and the pubsub-2 libs > are loaded correctly inside the gadgets. > Altough i cant't get any connection via the gadgets.Hub Instance except > for the openajax sample gadgets - there it works like it should. > -> Are the params inside the gadgets by pubsub-2 mandatory? > -> Are there any domain restrictions? The Sample Gadgets are on localhost, > whereas the other gadgets loaded from other domains like google.com, etc. > > I assume that there isn't a problem loading the libs correctly but there > is a problem with my pubsub-2 use case? > > Thanks, > Christian > > Am 28.09.2012 23:23, schrieb Ryan Baxter: > > My guess would be that maybe that is because it is in shindig-extras and >> not part of the main features project, although I am just guessing. At >> the >> end of the day they all get loaded into the same registry I believe so I >> don't see why this would matter. >> >> On Fri, Sep 28, 2012 at 11:37 AM, Christian Fischer <flyinghu...@web.de >> >wrote: >> >> There's also a property in shindig.properties that lists the core >>> features >>> >>>> everything must have (which is currently core and rpc) >>>> >>>> Hi, thanks for the answers - sorry for the delayed reply, but i'm very >>> busy at the moment. >>> >>> Enabling the features with shindig.proterties works fine for my custom >>> feature :) >>> >>> but i also must enable the pubsub-2 feature for all gadgets. >>> For an unknow reason for me, this doesn't work. >>> I included the pubsub-2 feature in shindig.properties and also as a >>> dependency of my custom feature. >>> -> Why isn't there any gadgets.Hub available? >>> Is this not possible with the dependency or shindig.properties Methods? >>> >>> Thanks a lot and nice Weekend, >>> >>> Christian >>> >>> >>> On Tue, Sep 25, 2012 at 2:46 PM, Henry Saputra <henry.sapu...@gmail.com >>>> >* >>>> *wrote: >>>> >>>> HI Christian, >>>> >>>>> You can either have custom DefaultGadgetSpecFactory.****parse() and >>>>> decorate the ModulePrefs element with your features or have custom >>>>> Processor.process() to add default or additional feature there. >>>>> >>>>> Or you can have custom rewriter early in the flow and add the required >>>>> features via call to Gadget.addFeature before other rewriters process >>>>> the gadget >>>>> >>>>> Hope this helps. >>>>> >>>>> - Henry >>>>> >>>>> On Tue, Sep 25, 2012 at 11:37 AM, Christian Fischer < >>>>> flyinghu...@web.de> >>>>> wrote: >>>>> >>>>> Hi all, >>>>>> >>>>>> i'm using shindig (inside Apache RAVE) for my master-thesis and need >>>>>> to >>>>>> enable a default feature for all gadgets even the gadgets doesn't >>>>>> require >>>>>> this feature. >>>>>> In other words: i must inject a reference to a javascript file into >>>>>> each >>>>>> gadget. >>>>>> >>>>>> What is the best way to acquire this goal with shindig? >>>>>> It is possible to set a feature as "required for all"? Then i only >>>>>> must >>>>>> create a new feature. >>>>>> If not, which source files are responsible for the <script ...> >>>>>> >>>>>> inclusion? >>>>> >>>>> For now, the Code looks a bit confusing to me. >>>>>> >>>>>> Thanks, >>>>>> Christian >>>>>> >>>>>> >
