Bug 50615 - Replace the Dojo Javascript Toolkit/Webframework
Replace the Dojo Javascript Toolkit/Webframework
Status: NEW
Product: UCS
Classification: Unclassified
Component: General
UCS 5.0
Other Mac OS X 10.1
: P5 normal (vote)
: ---
Assigned To: UCS maintainers
UCS maintainers
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2019-12-10 10:53 CET by Michel Smidt
Modified: 2019-12-10 11:40 CET (History)
3 users (show)

See Also:
What kind of report is it?: Feature Request
What type of bug is this?: ---
Who will be affected by this bug?: ---
How will those affected feel about the bug?: ---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Ticket number:
Bug group (optional): Usability
Max CVSS v3 score:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michel Smidt univentionstaff 2019-12-10 10:53:00 CET
In product management, we are repeatedly asked about the Javascript web framework Dojo. Meanwhile, we believe that it would make sense to replace the framework. There are a number of more modern Javascript frameworks that bring the following advantages from our point of view:

1) The usability for users is much better because the use is more fluid and faster.
2) There are better options for responsive designs utilizing different CSS frameworks.
3) Regarding the mobile strategy, progressive web apps are possible out-of-the-box.
4) In addition, the development in the frameworks can take place faster and more efficiently, e.g. because of better encapsulation and seperation of concern.
5 )Finally, the community idea should not be neglected. It would be much easier to involve external developers and also to win frontend developers.
Comment 1 Florian Best univentionstaff 2019-12-10 11:03:28 CET
(In reply to Michel Smidt from comment #0)
> 1) The usability for users is much better because the use is more fluid and
> faster.
Yes, dojo has some lack of performance due to supporting a lot of broken old browsers (IE).

> 2) There are better options for responsive designs utilizing different CSS
> frameworks.
For responsive design we are using bootstrap's CSS classes.
The goal here should be that the Javscript itself is aware about these techniques?
Can you give an example framework which does this and how it does this?

> 3) Regarding the mobile strategy, progressive web apps are possible
> out-of-the-box.
I don't understand this.

> 4) In addition, the development in the frameworks can take place faster and
> more efficiently, e.g. because of better encapsulation and seperation of
> concern.
Can you give an example here?

> 5 )Finally, the community idea should not be neglected. It would be much
> easier to involve external developers and also to win frontend developers.
Where do you have this opinion from? Are there any developer which told you that they would contribute but only if we wouldn't have dojo?