Op 1 mrt. 2013, om 12:42 heeft Diederik de Haas <didi.deb...@cknow.org> het volgende geschreven:
> On Friday 01 March 2013 08:02:32 development wrote: >> There is quite some HTML generated through the js-files. I can not see why >> this would be required to be in the JS, and not could be handled through >> PHP. When we could split functionality (through PHP) and user experience >> improvements (mostly js) > > I hope they'll listen to your recommendations. Not that I'm interested in > creating themes (or have the skills for it), but it would make owncloud > better! > > Keep up the good work :) > > Diederik Indeed, it would.. The major advantage of it would be that is will be more widely adopted by bigger firms and organizations. The community around OwnCloud will grow, once it is easier to white label things. White labeling relies heavily on theming. When the community grows, OwnCloud will get more people aboard that will have understanding of it's code and so, OwnCloud will benefit from that. Apart from all that, things will become *much* easier to understand once we split out design (HTML) vs functionality (PHP core and JS). As a sidenote: I'm not bashing on OwnCloud. Not at all. I think it has a tremendous potential to become something _really_ big, I absolutely *love* the functionality, but the overall implementation and separation of code vs design could be much, much better.. I've quite some experience with the open source project Drupal, of which I designed the default theme. We struggled with the same problems there, and I have seen that when we did actually separated the code there was an enormous hit on developers/designers and users which adopted and contributed back to Drupal. I'm willing to put a lot of time in making things better, but unfortunately I can not do such a major overhaul on my own. Kind regards, Stefan _______________________________________________ Owncloud mailing list Owncloud@kde.org https://mail.kde.org/mailman/listinfo/owncloud
