Hi Olemis, The real question I make to myself is, in these kinds of editors where's the model ? Or is it that you'd just use client-side templating ?
Ya I just wanted to use a framework to provide a structure. As of now there aren't any models. Since I was learning angularjs I just quoted it :). I might only be using the client side. I intially thought of making the editor into an app and it does the rest of the job. I don't know how the situation might be. And can you suggest some approaches on solving this? I have to submit my proposal at the earliest :) with a well written timeline. If the later case is the target then **ideally** I'd rather use a solution supporting Genshi templates so that it will be possible to reuse existing and have a consistent style in server and client code. In the mean time there's a patch proposed in #195 based on Blueimp's js templates engine. However it's not a straitjacket due to the fact that jQuery-File-Upload may be customized to use custom JS template engines (if there's a good reason to do so ;). I didn't quite get you here. Did you mean to use some stuff like genshi2js? Or another library which can go hand in hand with genshi templates? On Mon, Jul 15, 2013 at 6:46 AM, Olemis Lang <[email protected]> wrote: > On 7/14/13, Ryan Ollos <[email protected]> wrote: > > On Sat, Jul 13, 2013 at 9:31 AM, Anoop Nayak <[email protected]> > wrote: > > > >> Hi, > >> > >> So now what all should I include further in the proposal. And should I > >> use > >> angularjs to make a bit MVC so that it is easily maintainable? > >> > > > > The important aspect is that you evaluate alternatives and provide a > strong > > justification for why you should use a particular library or framework, > and > > what value it brings to the Bloodhound project. In considering whether to > > integrate your plugin into Bloodhound we will look at all aspects, > > including maintainability of your codebase. Adding AngularJs results in > > another framework that Bloodhound developers need to have experience with > > in order to maintain the entire project. We'd like to maintain some > amount > > of uniformity across the project in the frameworks and libraries that are > > utilized. See for example, a discussion about testing libraries that are > > utilized in Bloodhound (1). > > > > Now that this subject is on the table I'll express my opinion based on > some facts . Like I mentioned before we tried AngularJS to build BH > plugin once upon a time. With time it proved to be so heavy and kind > of solving the quadrature of the circle, hence we have adopted another > lightweight MVVM js framework ... > > > Bloodhound and Trac currently utilize jQuery, jQuery UI and a single > jQuery > > UI plugin (jQuery Timepicker addon). We would likely have less hesitation > > to integrate a plugin that utilized jQuery, jQuery UI or a jQuery plugin > > than to integrate another entire framework or library. > > ... smoothly and efficiently integrated with jQuery. > > > Therefore I > > encourage you to consider multiple approaches in the early prototyping > > stage and to raise your findings on the dev list for discussion. > > > > The real question I make to myself is, in these kinds of editors > where's the model ? Or is it that you'd just use client-side > templating ? > > If the later case is the target then **ideally** I'd rather use a > solution supporting Genshi templates so that it will be possible to > reuse existing and have a consistent style in server and client code. > In the mean time there's a patch proposed in #195 based on Blueimp's > js templates engine. However it's not a straitjacket due to the fact > that jQuery-File-Upload may be customized to use custom JS template > engines (if there's a good reason to do so ;). > > .. [1] https://github.com/blueimp/JavaScript-Templates > > -- > Regards, > > Olemis. > -- Anoop
