Opened 14 years ago

Closed 14 years ago

#7516 closed enhancement (invalid)

Please separate the dijit impletementation

Reported by: jgnan Owned by:
Priority: lowest Milestone: tbd
Component: Dijit Version: 1.1.1
Keywords: Cc:
Blocked By: Blocking:


Dear dijit team members,

Dijit is a great widget framework in its template mechanism, but not good enough in the front end. Why? I think it is because we compound the implementation logic for different browsers together. This is not a good pratice by looking the corrent dijit components, for this implementation method doesn't make any component have a perfect look at lease one browser. Why not give a seperation on dijit implementation for different browser? Why not do the implementation job for different browser? It surely will waste extra workload and bring up many files, but it'll make a better presentation and performance. By looking the code and the performance in a dijit source file, they're becoming more and more complex and not easy to maintain. Also dijit in this way preventing us using some of the good things in different browser. Please do a seperation on the implementation and let our dijit become more wonderful.

Change History (1)

comment:1 Changed 14 years ago by dante

Resolution: invalid
Status: newclosed

This ticket is entirely to vague to act upon. What exactly are you asking for/wanting to happen. I'm going to mark this as invalid and urge you to voice these opinions through the normal channels: either via mailing list [dojo-contributors], or #dojo (, or the Dojo forums, as this kind of feedback is definitely welcomed and encouraged, but trac is reserved for specific changes and enhancements. You touch on the build system, browser branches, dijit maintenance, and frontend design, but fail to suggest anything concrete -- Would love to hear something more solid. What exactly are you suggesting?

Note: See TracTickets for help on using tickets.