>> JP Larsson, we believe that by making the UI more usable would lead >> to more users on freenet, that's why there is an effort (of 2) to do >> this. There is a proposal here: http://freenet.makdisse.com/ And the >> work is being done here: >> https://github.com/Thynix/Winterface/tree/velocity-dev What I thought >> is that you could sum efforts with Steve (operhiem) to implement the >> template files that I will create into the backend. > > To provide context: the current web interface of Freenet (FProxy) grew > gradually over many years into something that is difficult to maintain > or modify. There is no separation between the backend and frontend > components - HTML is generated element-by-element in the Java code that > also performs actions and gathers data. I think I remember at least one > developer intending to contribute to the web interface, seeing the code, > and giving up. > > Winterface is a web interface plugin for Freenet that was started by a > GSoC student. Paulo and I have forked it to continue work. Our goal is > to separate page templates and Java code. It makes it much more friendly > for web developers to change the interface around, and gives a much > nicer layer of separation for backend developers as well. I hope that > Winterface will be able to eventually replace FProxy, and make Fred > itself less concerned with user interface. > > It seems like Paulo has been making progress on templates while I've > been too busy to keep up on the backend. Page templates expect objects > from the backend with certain names and attribute getters in order to > display things. Localization keys are one example. > > One thing that is somewhat unsettling to me is that the templates can > test conditions and render different things depending on them. It will > require careful usage to keep that logic limited to things relevant to > display. > > Paulo has been kind enough to document assumptions the template makes > about what the backend will provide, as done here. [2] If you'd like > more information about the templating engine this is using, the Velocity > user guide [3] may be helpful.
Thanks! I’d be happy to work on the new interface. As you mentioned that the backend needs more work, maybe I could have a look at that. How is the actual development done, should I fork your repository on GitHub and take it from there or have you got a different kind of workflow? JP _______________________________________________ Devl mailing list [email protected] https://emu.freenetproject.org/cgi-bin/mailman/listinfo/devl
