<html><head><meta http-equiv="Content-Type" content="text/html; charset=UTF-8"></head><body >The point to be noted is, that if you properly separate functionality (PHP) from user interface (HTML) and user experience (JS), custom themes could live longer in it's current form.<div><br></div><div>Currently Im trying to make some custom themes. To properly theme most aspects of OC, i *must* copy almost an entire app (like files/calender, etc) to my themes directory and rewrite more than 50% of the code to give it another look. Thats awfull, and directly explains why there are no themes available in the current repository other than the rediculously simple responsive-theme. (No offense though)</div><div><br></div><div>I could live with the fact that owncloud requires JS to be enabled in the browser. I only think that to make theming easier for non-programmers this is a step that needs to be taken.</div><div>Seperate things and make functionality rely on id,s in JS. Make the id start with "js-..." So themers know it triggers certain functionality in the js-files.</div><div>The looks of oc could be done with ids/classes, like it is now.</div><div>All the generated/build HTML inside the JS-files should be in seperate templates, which could easily be overridden by themers.</div><div><br></div><div>Im willing to work on this, but I need more opinions on the approach and some sort of approval for this plan.</div><div><br></div><div>Hope to have things cleared up a bit.</div><div><br></div><div>Kind regards,</div><div><br></div><div><br></div><div>Stefan Nagtegaal</div><br><br><br>-------- Oorspronkelijk bericht --------<br>Van: Daniel Molkentin <danimo@owncloud.com> <br>Datum: <br>Aan: owncloud@kde.org <br>Onderwerp: Re: [Owncloud] JS degration and use custom themes <br> <br><br>
<div class="moz-cite-prefix">While I generally agree, Bernhard, I
think this misses the OPs point. <br>
<br>
Stefan, ownCloud is - by it's very nature - a web application.
Creating well-working instant-feedback web applications without
the use of JS simply is not possible. So generally, the
requirement of JS is not a bug, and we will not support browsers
that have JS disabled.<br>
<br>
If however, there are special, valid use case that would make pure
HTML desireble (e.g. for automation), please bring it forward,
although usually this is where the REST or WebDAV-APIs are usually
more useful. So what are your use cases?<br>
<br>
Daniel<br>
<br>
On 03/01/2013 08:29 AM, Bernhard Posselt wrote:<br>
</div>
<blockquote cite="mid:513058E2.5050307@gmail.com" type="cite">
<meta content="text/html; charset=ISO-8859-1" http-equiv="Content-Type">
<div class="moz-cite-prefix">Yes, its your typical jQuery project.
JavaScript is not the problem, the problem is like you said the
often missing seperation between view and logic and that makes
it at least for me incredibly hard to understand the code. <br>
<br>
The solution is to use a proper JS framework like AngularJS
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a moz-do-not-send="true" href="http://angularjs.org/">http://angularjs.org/</a>
but this has been introduced very recently to people. Also we
have too less time for too many bugs, so people dont really have
the time to rewrite stuff.<br>
<br>
Everyone who wants to improve the code/fix bugs is welcome
though. Just contact the people on the IRC/mailinglist if you
need help.<br>
<br>
PS: Disabling JS is not an option.<br>
<br>
On 03/01/2013 08:02 AM, development wrote:<br>
</div>
<blockquote cite="mid:lmr37180oiagbo8mwhs85jdw.1362121352930@email.android.com" type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div>Is it me or is *a lot* of owncloud 5 functionality relying
heavely on Javascript, which do not degrade gracefully in
browser whixh do not support or has disabled the use of
Javascript?</div>
<div>Is this intentionally, or are these bug reports?</div>
<div><br>
</div>
<div>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.</div>
<div>When we could split functionality (through PHP) and user
experience improvements (mostly js), we could support more
browsers and make owncloud much easier to theme.</div>
<div>At the moment if someone would like to override the looks
of a simple form, the JS file from the (core) app is required
to be included and edited inside the theme. In my opinion this
could and should be handled in another way.</div>
<div><br>
</div>
<div>If people would like some examples, Im happy to provide
any..</div>
<div><br>
</div>
<div>Kind regards,</div>
<div><br>
</div>
<div><br>
</div>
<div>Stefan Nagtegaal</div>
<div><br>
</div>
<div><br>
</div>
<div>
<div style="font-size:75%;color:#575757">Verzonden vanaf
Samsung Mobile</div>
</div>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Owncloud mailing list
<a moz-do-not-send="true" class="moz-txt-link-abbreviated" href="mailto:Owncloud@kde.org">Owncloud@kde.org</a>
<a moz-do-not-send="true" class="moz-txt-link-freetext" href="https://mail.kde.org/mailman/listinfo/owncloud">https://mail.kde.org/mailman/listinfo/owncloud</a>
</pre>
</blockquote>
<br>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
Owncloud mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Owncloud@kde.org">Owncloud@kde.org</a>
<a class="moz-txt-link-freetext" href="https://mail.kde.org/mailman/listinfo/owncloud">https://mail.kde.org/mailman/listinfo/owncloud</a>
</pre>
</blockquote>
<br>
<br>
<pre class="moz-signature" cols="72">--
<a class="moz-txt-link-abbreviated" href="http://www.owncloud.com">www.owncloud.com</a> - Your Data, Your Cloud, Your Way!
ownCloud GmbH, GF: Markus Rex, Holger Dyroff
Schloßäckerstrasse 26a, 90443 Nürnberg, HRB 28050 (AG Nürnberg)
</pre>
</body>