Navigation naming & structure. about webui-aria2 HOT 12 CLOSED

Thanks, I see these changes were implemented 😄!

I would like to assist with this project if you need anything done? Let me know. My email address is public. Large download queues (300+ files) causes browser performance problems. I also found a few other minor issues while reading through the source. Is there a possibility that the web UI will be embedded or distributed with Aria2 daemon in the future?

Regards,
Carl

from webui-aria2.

Thanks for the offer and I would love some assistance with the project :)
You could easily start off by just submitting simple pull requests for pretty much any thing useful. It could even be trivial changes to start off with. And once I have semi regular pull requests I am willing to even share admin access to the repo as its a lot easier to collaborate directly on the git repo and having multiple core commiters is always good and keeps the project alive. And even if anyone is interested in implementing a feature but dont have a clear idea on how to implement it then I would love to help out as a mentor, just add it as an issue.

I talked with the aria2 project maintainer regarding the embedding this in aria2 dameon ( something like rpc for humans :] ) but he said that the aria2 code base and release cycle is changing slowly and it would make it hard to make rapid changes and shipping it early which I now agree but I am looking into having a bundler which bundles the project into one html file and then one could ship the aria2 exe and the bundled html in one useful package.

from webui-aria2.

I can also code in my free time, I think it's a great project and I'd like to see it grow. There's plenty more RPC commands that we could implement, like drag&drop reordering of files in a job, etc. Also, an architecture overview would be great.

from webui-aria2.

I totally agree jakub that a lot of improvements can be made,and really happy that the project is getting some momentum with respect to people helping out which I wasn't really sure initially :)

Current architecture is very rusty and refactoring the core was always on my to do list, currently I would soon (within a week) overhaul the core with probably dividing the core into modules (by using requirejs), use backbone for the view and state handling and changing the current ui to work in smaller resolutions and touch devices.
After that I will probably add a wiki page to explain the architecture (which by then should be very easy to understand). And I will finally force myself to document the code and inacrease the comments rate which I am kinda embarrassed about.

from webui-aria2.

I don't know about backbone, I would rather go for a real object oriented language rather than code in javascript with extensions, but whatever works.

from webui-aria2.

Also, angular.js looks nice.

from webui-aria2.

Let me know if I can assist. I have used Backbone in production, but am more than willing to learn something new. The current code is pretty easy to understand.

Tim Branyen's grunt-bbb may be a good choice for build automation if we do use backbone. It precompiles view templates, minifies & packages JavaScript (using RequireJS), minifies CSS, etc. Grunt (without bbb) can be used for these tasks if we don't use backbone.

I like the dynamic and functional-language bits of JavaScript with Underscore.js and am not really keen for Dart's OO syntax - it looks too much like office work. Maybe CoffeeScript or TypeScript for static typing...

Angular looks great and I would like to learn it. It is a larger, more opinionated framework than Backbone or Spine. Angular dictates file structure and code architecture - a good thing for making sure everything is standard. Backbone is more of an optional utility library for structuring existing architecture. Ember.js also looks nice, but will take longer to grok. Check this comparisson: http://blog.stevensanderson.com/2012/08/01/rich-javascript-applications-the-seven-frameworks-throne-of-js-2012

from webui-aria2.

I totally agree with carl. I choose vanilla js initially because it is incredibly popular and hence it is very easy for someone to contribute. But personally I prefer coffee script, which has a very clean syntax with basic fixes across the language. In the similar way I prefer jade over html and less over css and grunt as the defacto build step for any client side project but all of them require nodejs as a build time dependency, which I was initially hesitant to add. After a second thought I guess we could add nodejs (and npm) as a build dependency to develop on the project and ship compiled packages for normal users to consume, what do you guys think?

And I am willing to learn new frameworks and libraries. I tend to prefer libraries because they are easy to change and refactor whereas frameworks are much harder in this regard. I like backbone and knockout and will probably use either one of them in conjunction with requirejs in my current refactor/rewrite for the core but if you guys have a strong opinion about an alternative way then pitch it in!

from webui-aria2.

Well, I haven't used any of those frameworks, I usually avoid javascript.
But I hear good things about angular, especially that it requires much less
code than backbone. I've seen some samples and they look really neat and
clean so if You care about my opinion, I'd say Angular.js.

On 4 January 2013 17:47, ziahamza [email protected] wrote:

I totally agree with carl. I choose vanilla js initially because it is
incredibly popular and hence it is very easy for someone to contribute. But
personally I prefer coffee script, which has a very clean syntax with basic
fixes across the language. In the similar way I prefer jade over html and
less over css and grunt as the defacto build step for any client side
project but all of them require nodejs as a build time dependency, which I
was initially hesitant to add. After a second thought I guess we could add
nodejs (and npm) as a build dependency to develop on the project and ship
compiled packages for normal users to consume, what do you guys think?

And I am willing to learn new frameworks and libraries. I tend to prefer
libraries because they are easy to change and refactor whereas frameworks
are much harder in this regard. I like backbone and knockout and will
probably use either one of them in conjunction with requirejs in my current
refactor/rewrite for the core but if you guys have a strong opinion about
an alternative way then pitch it in!

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/39#issuecomment-11889806.

from webui-aria2.

Node is a pretty standard dependency afaict for build automation. Especially since native Windows support was added. Let's use it 👍

I am going to dig into Angular and try to have something running by tomorrow or Sunday for feedback. I only know Backbone and would like to learn how the bigger frameworks work.

Vanilla JavaScript is actually really nice after reading Crockford's The Good Parts + JavaScript Web Applications. Its prototypal, functional, and closure patterns are fun to use. JSHint and ES5 strict mode help.

from webui-aria2.

I have pushed in the initial structure for revamping everything with angular, its in angular.html and quite some work is still left for all to integrate. I will be working on this for a while and this time want to do it the right way (tests coming, trying to comment the codebase as I go and from now on add issues for the features first before I start to code them out).

from webui-aria2.

Closing this issue as the naming story would be a lot better with the new version. I have adding a milestone for the next version, add any issues or features that you think should go there (docs missing, drap&drop etc) and if interested then start collobarating on one and add a comment. And I totally like the idea of using issues for Q/A and friendly conversations about the project, sort of the road map discussion even if not technical so that everyone could come in. Closing this one because naming and overall ui structure would be a lot better in the new version.

from webui-aria2.