Hey Noe, Hmm now that is a interesting problem, i actually don't think
we have any code to make that work right now? Now that would be a good
question for the shindig-dev mailing list:
Can a gadget with content type="url" use dynamic height, and what
needs to happen to make that work?
The work-around suggestion i can offer is to use the height/width
attributes of the gadget to make sure the initial height is the one
you need :)
On Jun 18, 2008, at 8:23 AM, Neo Anderson wrote:
Thank you, this solved the problem(Including the scripts).
But the dynamic height feature is not working. It is working in HTML
type gadget.
I am using PHP version of the gadgets server. In the case of type
HTML gadgets, some hidden iframes (source refers to rpc_relay.html)
will be included in the gadget (gadget's iframe). So, these iframes
will play a role in making the features to work.
But in type URL gadget, there are no such iframes. Then how the
features will work?
Even in the type of HTML gadget also, features are working when we
access it by http://localhost/, but these features are not working
when I access it by typing http://192.168.0.1/.
Where can I find any article or tutorial regarding this RPC, tokens,
oAuth?
On Tue, Jun 17, 2008 at 9:22 PM, Chris Chabot <[EMAIL PROTECTED]>
wrote:
Hmm it should work really, if i check on the PHP version of shindig
(and they should work the same):
http://shindig.us.chabotc.com/gadgets/js/dynamic-height:settitle.js?v=fecaa74c9a98ecd5c1639191e126f88
that looks like the right libs are in there.. are you using that /
gadges/js/<libs> style url to retrieve them?
On Jun 17, 2008, at 5:46 PM, Neo Anderson wrote:
Please tell me if I am disturbing you,
Thank you very much for your suggestion. I am also doing the same.
I am creating a type="url" gadget and once upon Kevin gave a
response to somebody on the list to use the below scriplet:
$scriptPath = $containerUrl.strip_tags($_GET['libs']);
echo '<script src="'.$scriptPath.'"></script>';
But the libs parameter is: dynamic-height:settitle.js?
v=fecaa74c9a98ecd5c1639191e126f88
But this is not working. I try to include these as in the case of
rpc file. But these files(features js files) will be placed in WEB-
INF folder, which we cannot access.
If I am correct, in type URL gadget also the js files corresponding
to the features selected must be injected as in the case of type
html gadgets.
On Tue, Jun 17, 2008 at 7:50 PM, Chris Chabot <[EMAIL PROTECTED]>
wrote:
if your talking about the gadgets side, you shouldn't be including
rpc.js?c=1 .... that c=1 means you want to get the container code
and not the gadgets code :)
I would suggest taking the simple examples (gadgets/files/container/
sample*.html) and seeing how they work (both on gadget and
container level), and then seeing how that differs from your own
code...
In fact, temporary strip your own code and put in the code from the
sample files ... does it work then? If so make a small modification
to make it closer to your own code ... does it still work? if not
what broke it? When that modification works, make the next one and
repeat this cycle until you have it fully working. Good software
engineering practise to debugging when you have no clue about
what's breaking and a great way to learn what's going on!
On Jun 17, 2008, at 4:15 PM, Neo Anderson wrote:
Yes, I am talking about the gadget, not about the container.
Sorry, I say, "I don't understand" only when you talk about the
topic which I don't know and only when I don't get result after
trying this.
I am not asking about the container. I know that I have to write
code for my container.
In fact, I am a fresher, 22yrs old. I am new to RPC, oAuth etc.And
I learned a lot from you and kevin as you solved most of my
doubts. But I am very much worried when you said that I am
spamming the list.
I want to post my doubts only when I am unable to solve them and
unable to find proper documentation for that.
Anyway If I am disturbing you, Sorry once again. But I am very
much interested about JavaScript. I want to get more knowledge as
you. That is why I am posting all the problems.
On Tue, Jun 17, 2008 at 7:21 PM, Chris Chabot <[EMAIL PROTECTED]>
wrote:
ps it would make it so much more gratifying to help you if you -
understood- the answers you recieved
now i feel like i spend minutes of my time trying to help you on
your way and give you the hints you need to continue ... only to
hear you didn't understand a word i said :)
On Jun 17, 2008, at 3:39 PM, Neo Anderson wrote:
Chris,
You have misunderstood me. Last time also I am not talking about
jQuery. I am talking about makeRequest. Sorry once again.
I don't want to spam the list.
Thank you,
