Open Widget Engine
Home About Business Blog Developers Affiliates
Disclaimer: this page is a blog, stating the opinions and considerations of individuals associated with widgetplus in one way or another, and it's not automatically the opinions of naltabyte as a company, widgetplus as an entity, or any partners of either.
If you want to contribute or comment any of the blog posts, email the editor of that specific topic from this page.



Inroducing XML datatables
8 May, 2008

Editor: Mikael Bergkvist


We have introduced what we call XML datatables under the 'developers' tab, if you check 'data handling'.
XML tables are a form of organized databases with cells, columns and rows, and they look a bit like excel sheets, only they are nothing like that.
We are infact doing a spreadsheet app and it will debute later this spring, but this is not it.

The key difference in comparison with other webcentric and crossdomain solutions you have encountered on the web, is that you can enter and edit data en mass with XML datatables, since they use forms to post the data to the server.
You can thus edit thousands of entries and then post/save all changes at once.
Once you have done that, the data is accessable for any widget/webapps of yours using it.
The data in these XML datatables are accessable crossdomain from anywhere on the web, for any widget or webapp with a widgetplus account.
The information is personal for specific accounts and can't be accessed unless the user has logged in properly.

Now, the difference from a security standpoint is that with SQL, if someone manage to hack the account, assuming we where infact using SQL in some manner, they would get access to all the information related to widgetplus, but with this approach, this isn't the case.
Each table exists as a separate entity, so if one gets hacked, then it ends there.
The other tabels remain unaffected.
Getting access to one doesn't mean that you get access to the others.

Check it out





The calendar again
3 May, 2008

Editor: Mikael Bergkvist


We have updated the calendar again.
This time the difference is much more drastic, because it's way more functional, much more a 'real' program, but also organically grown from the framework itself, and because of this, far easier to code.
You can view source here.

You can edit the entries, add new entries, remove entries, and drag to sort the entries.
It has custom selects and scrollbars, and all kinds of other goodies, and it's all copy & paste easy to add to any webpage.




For those interested, the first calendar remake took almost two hours to plan and complete.
The second update happened through the weekend from April 30th to May 2th.. and time was spent celebrating during that period.
This is what I associate the whole deal with more than anything right now..





Here, there, anywhere
26 April, 2008

Editor: Mikael Bergkvist


Imagine you are at the site my_domain.com and you want to add a widget.
The widget's sourcefile is at other_domain.com so you format the link as such:

<a href="javascript:xin.app(other_domain.com/widget.xml, widget_ID)">Open app</a>.

Someone clicks that link.

That fetches the app sourcefile from other_domain.com, the app is automatically logged in at widgetplus.com and returned to your webpage at my_domain.com, where it appears.

If the user hasn't logged in, the default is the demo account, but if the user has logged in, the widget from other_domain.com has access to the users account, which means that the widget can access and manipulate the users personal data and files/folders.

For the user to be logged in, two variables has to be set, hardcoded or using javascript, at my_domain.com, xin.login and xin.pass.

Or maybe the widget itself does this.

So, the widgets sourcefile can reside at one place, be inserted somewhere else, and access the home account at widgetplus.
- Here, there, anywhere.