While others are talking about Dekoh, I figured I’d make it interesting and discuss Xindesk. I just received a tip from Mikael Bergkvist, and he sent me an invite to check it out.
I did check it out, and it appears ready for primetime. It has a few things that I saw that were needing of a quick fix, but for the most part - Xindesk is a winner. I think I said it late last year, that this would be the year of the webtop or webOS. This one is getting a lot closer to that reality. The item that their main site seems to be pushing is the mobile issue.
Here is a quote (blog post actually, but it is well written to what it is and what services they are providing) directly from their blog:
So, whats different about XINDESK in comparison to other webtops/webos out there?
Well, lets start at the top shall we?
1) Xindesk is serverside, and all it’s applications are server applications by default, accessing all server features, including all the good stuff like SQL, the filesystem, and the email accounts.
It has an really easy to grasp API which can easily be extended and all it’s functions can be set either public or private with a single command.
2) Xindesk serverside development is in javascript, and the serverside javascript manipulates the serverside html in the exact same way DHTML manipulates html on the clientside.
We repeat, it’s serverside DHTML.
All DHTML techniques used on the clientside can be used the same way on the server!
This is not a trick nor a workaround - this is how it works.
All DOM metods work, and therefor the html can be manipulated extensivly before being served to the browser, AND inbetween pageloads.
That means that the server does some work AFTER the browser has recieved all the full content of the page, and BEFORE a new request is being made from the client.
If this is unclear somehow, please read it again.
3) Variables are persistent across pageloads, further strenghtening the connection to DHML to the point where there’s virtually no difference.
4) The Ajax interface is default.
It’s not something the developer need to code him/herself, or even do anything about - it just happens and it just works.
5) It’s fast, which is something many beta testers can testify to.
(We have passed 7400 beta testers as of yesterday.)
6) It’s modular, so applications created to function on the desktop may also be accessed in many other ways, even as webservices, returning XML only.
So by this it’s perfectly clear that as a developer you can build very big and very advanced datadriven webapplications very quickly, and plug in/out of any of the other pre-existing applications/frameworks on the XINDESK to extend the application(s) further, or allow others to do the same.
This blog, for example, was built in it’s entirety in a weekend, and a buzy one at that, with no real effort involved, by a single developer, and it also appear as an application on the demo desktop, from where it can be managed, and it’s file manager is the same file manager that XINDESK itself uses by default.
You can read about that here.
Technically Speaking, I have been a Goowy fan for some time now, but I do believe that Xindesk will be doing quite well also. Don’t forget to see some of the latest unpublished items on GMAFB and help to FRIGGIN’ BREAK them to the published side.
Sphere It