Extension talk:WidgetsFramework

Contact the initial development team

Extension:WidgetsFramework had been initially developed by the Seizam team. If you wish to contact us directly there is this contact page. But the best way remains this talk page.

Talk to you soon! --ClementD (talk) 18:19, 16 November 2012 (UTC)

---

Jotform & Wafoo forms plus Video switching in the template

Hi saw your extension and was thinking of trying it. Currently I'm using widgets, but for the reasons you mentioned I may be switching. Was wondering if you thought it was possible to create a widget for embedding jotforms & Wafoo forms into a wiki page. Would like to be able to offer end users the ability to embed these forms. Additionally right now I use templates to switch on the quick from embedded video to another embedded video service. Example in the template: {{#widget: {{{VideoSource}}}| Id= {{{Video id}}} }} using some thing like this I'm able to offer the end user of the template the ability to just name the video service as source and then easily switch from Vimeo to YouTube, etc. Is that possible with this extension? Thanks -- Chris Tharp (the site's acting strange - I was signed in but now it says I'm not)

Any code (as long as it's HTML based) can be integrated. I don't know jotforms & wafoo, but I don't see why not.

Yes, it is possible to mix templates. I just made sure for you : See the page I built for you. Enjoy ;-)

Btw, we now have a wizard in the editor for easier integration. See the demo video.

--ClementD (talk) 22:41, 30 January 2013 (UTC)

So I'm switching from widgets to Widget Framework

Hi So I'm switching from widgets to widgetframework. I'm currently having some more widgets coded, which I'll be happy to send you the code for when they're finished. One of those widgets is the ever popular Disqus comments, which allows for adding comments at the bottom of a page.Should I send it to you via email? And what email should I send it to?

Additionally, I was wondering if I could get the code for the skype widget, which you have on your site, but is not part of the download for the extension. Thanks--Christharp (talk) 17:57, 6 February 2013 (UTC)

That's great news! Hope you'll find the framework easy and flexible. Remember to keep in touch if you need anything. Disqus is indeed a good addition...

To push the code, email is fine, you could also directly commit it on Github, as you wish.

We'll repackage the framework to include the latest widgets ASAP.

--ClementD (talk) 20:31, 6 February 2013 (UTC)

The widget for Disqus is done. We're testing it now. I expect to be emailing it to you within a few hours.--Christharp (talk) 20:35, 7 February 2013 (UTC)

The Disqus comment widget has been emailed to you.Please confirm you received it when you can. Hopefully will have a Google Docs widget in another day or so, at which time I'll email that to you also. --Christharp (talk) 14:28, 8 February 2013 (UTC)

Received, proofread, tested, improved (default url to current page), pushed and archived ! All done. Thanks a lot for contributing. How was the coding ? --ClementD (talk) 18:41, 8 February 2013 (UTC)

More widgets

Hi, just emailed you two more widgets from the Yellpedia.com team: Google Doc and Google Viewer. Hopefully we'll get more people involved in making widgets soon. --Christharp (talk) 18:54, 11 February 2013 (UTC)

Done ! Code is in the repo ! Thanks for contributing. Like you, I hope this will grow... --ClementD (talk) 16:12, 13 February 2013 (UTC)

Need browser/OS detection

In my widget code, can I detect the OS/browser?

My widget displays: - To desktop users: a map in an IFrame - To mobile users: a link to a full-screen map

So I need to detect whether a user is on mobile or not. Can I detect this with WidgetsFramework? If it is not possible yet, would you consider adding this feature?

Reason I need this: Some mobile platforms don't support the <IFrame> HTML element well; and for small screens it makes more sense to show the content full-screen anyway. Thanks a lot! Nicolas1981 (talk) 07:33, 18 April 2013 (UTC)

WidgetsFramework has full access to MW functions, but I don't know any php backend function to recognize the type of client. You should check though. Most of the time recognizing the client is done on the client side with JS/JQuery. Something to explore too. This kind of development is not planned, we're betting on unique cross-platform + responsive developments ATM. Good luck --ClementD (talk) 16:57, 18 April 2013 (UTC)

Experimental?

Hello, this extension looks great. Thank you so much for sharing it. I noticed that the extension is still listed as experimental, but that you are using it in production on your website, Seizam. Is there any chance of changing the status to stable and implementing any "breaking changes" via new versions? ForestForTrees (talk) 15:38, 23 April 2013 (UTC)

Sadly we are not at this stage yet. 2 Reasons :

1. Resources, which are scarce at the moment within the WidgetsFramework developers (Seizam+third party).
2. A huge development is coming to interface with the new [VisualEditor] and [Parsoid] projets (MW 1.21). As this has been foreseen during the initial software design there should not be any breaking change but we'd rather not make promise we cannot keep. On the bright side, it means quicker development to get a widgets API with real time WYSIWYG embedding \o/.

--ClementD (talk) 09:05, 24 April 2013 (UTC)

Incorporating wikitext within a widget

Hello, and thanks again for this very promising widget. My site has been using Extension:widget for years and we are happy with it, except for one thing. Specifically, we would like to design the editable portion of our home page in raw HTML, but still have the flexibility to update our "Announcements" section using simple wikitext.

For example, the entire wikitext of the homepage (currently at tmswiki.org) would be something like:

{Widget:HomePage
|Announcements='''We just redesigned our new homepage!''' 
Since we've redesigned our home page in HTML, we have much more graphical flexibility 
while still being able to edit the announcement section using simple wikitext.

The output of the editable portion of the home page would be relatively complex HTML, generated by the widget.

Would it be possible for relatively inexperienced programmers to implement this in WidgetFramework? We have experience with PHP but only very limited experience with hacking Mediawiki. If so, how would one do it?

Thanks in advance. ForestForTrees (talk) 15:38, 23 April 2013 (UTC)

Declare an HTML parameter called HtmlContent :

$this->HtmlContent = new String('HtmlContent');
$this->addParameter($this->HtmlContent);

Output an HTML parameter :

$this->HtmlContent->getOutput()

Declare a WikiText parameter called Announcements :

$this->Announcements = new Wikitext('Announcements');
$this->Announcements->setParser($this->getParser()); // Remember to pass the parser to the parameter object
$this->addParameter($this->Announcements);

Output a WikiText parameter :

$this->Announcements->getOutput()

Seems easy enough for me but do not hesitate to ask if you need more help. --ClementD (talk) 09:20, 24 April 2013 (UTC)

download link

Hi! The download link is broken. 12:41, 16 May 2013 (UTC)

Fixed. Thx! --ClementD (talk) 13:37, 16 May 2013 (UTC)

Twitter Widget?

Hi, I just installed WidgetsFramework, which is fantastic. However, I am getting no result when trying to use the Twitter widget, with the exception that the "follow" variation seems to work. Normally I'd assume it's a problem on my end, but http://www.seizam.com/Widget:Twitter/en seems to have the same issue. Other widgets are working - is there a problem with using that one? - Mmouse (talk) (Sorry, I messed up the signature during the submission)

You're right, the widget does not work anymore due to change on twitter side. Anyone wants to fix ? --2A01:E35:8BDE:B590:5AB0:35FF:FE7F:B518 06:46, 18 November 2013 (UTC)

Helpful Way to Show PDFs, Word Docs via the GoogleViewer WidgetFramework application

Hi to whomever this may be helpful to,

I generally have used the GoogleVeiwer to view PDFs embedded into a wiki page, but it's generally hard for users to upload PDFs since they must know the complete URL. But the following use of Mediawiki magic words makes it very easy for end users to use (especially if you're using Semantic forms):

Template:

{{GoogleViewer:url={{filepath:{{{variable name for upload}}} }} }}

Semantic form:

{{{field|variable name for upload|uploadable}}}

This method works for PDFs, Word Docs, etc., -- in theory all types of files the GoogleVeiwer allows. Of course you need to set the LocalSettings.php to allow those file types to be uploaded. Christharp (talk) 17:30, 5 April 2014 (UTC)