Dashboard - ...

[kaystrobach]

Hi Devs,

i have currently a pending question on the extjs licensing manager.

Are the examples covered with the extJS dual license?
What license do the following 2 demos have?
http://www.sencha.com/deploy/dev/exampl ... ortal.html
http://www.sencha.com/deploy/dev/exampl ... /view.html

If they are covered by the extjs dual license i will try to create a dashboard with some widgets and an rss viewer for tine20.org.

Best regards
Kay

[Balazs]

Hi Kay,

as far as I know are all sencha products (at least all that were ExtJS) under a dual licence. So it should be fine to use it.

If you decide to spend some time in dashboard and RSS feeder, I would like offer to work together with you in defining the requirements and the final look & feel!

Björn

[kaystrobach]

The answere:

Kay,

Yes, they are included in our GPL license.

~ Adam

My idea was to use the portalpanel object from extjs and some panels in it. (Without the sidebar)
http://www.sencha.com/deploy/dev/exampl ... ortal.html

Aditionally i would like to see, if UWA widgets would work:
http://dev.netvibes.com/doc/uwa/documentation

Basically i would like to use netvibes/igoogle as base for visual and usability questions.
The base question is, if it's good to provide a feed reader AND a dashboard, as many people read rss feeds on the dashboard ...
I don't think, that the first release the chance to change the column count.

API:
* UWA
* API to register widgets from Applikation

Widgets
* Mail (Show messages in inbox) -> is there a way to open a mail in a new window?
* rss (select feed from reader)
* kalender (show upcoming events / filter / today / ressources
* tasks

[nelius]

Hi Kay,

I like the idea of having a dashboard


Here my technical notes:
* The portal stuff is already in our js builds
* RSS Reader -> Should also become part of Fmail
* Security Considerations Should be the first think to be done:
-> dealing with external js code -> widgets in external iframes?
-> message bus?
* The UWA approach is to have a widget in one file (including all css/js)
-> this might lead to problems with versioning etc.

[kaystrobach]

I like the idea of having a dashboard


Here my technical notes:
* The portal stuff is already in our js builds
* RSS Reader -> Should also become part of Fmail

I've seen that
Nice idea to include it in Felamimail -> but i would like to seperate both.

* Security Considerations Should be the first think to be done:
-> dealing with external js code -> widgets in external iframes?
-> message bus?

I think there 2 types of widgets
1. internal ones -> complete api access
2. external ones installed from admin -> uwa
3. external ones installed by user -> i would deny that by default or architecture

* The UWA approach is to have a widget in one file (including all css/js)
-> this might lead to problems with versioning etc.

correct, but most widget plattforms extract the .widget archive to render it.
That can be done here as well be storing it in a folder with a unique id.
After extraction we have single files. If we store the default widgets already extracted there is no problem with versioning.

The first step should be to create the dashboard with the settings panels and an easy way to add widgets of type 1.
If that is working UWA should be next.

[Balazs]

How will the dashboard page be integrated into the rest of Tine 2.0?

I think it would be a reasonable substitute for our "Start-Menu". So people can configure their start-page individually. This would on the other hand mean to include the functionallity from the menu into the dashboard...

What do you think?

[kaystrobach]

i thought to integrate it as normal tab for consistency

but it's a cool idea to replace the tine20.org button with the dashboard. let me think a night about that.

[kaystrobach]

UWA sample implementation:

http://h6e.net/wiki/wordpress/plugins/uwa
http://wordpress.org/extend/plugins/uwa-widgets/