From: Pascal K. <pa...@ku...> - 2010-01-20 20:00:13
|
Hello, You know that I'm, usually, in favor of cleaning the code. That means, of course, removing some useless or unmaintained features, improving some others, only adding some stuff when the back-end is ok and the front-end clean, usable and understandable for a "normal" user. In the last few months and years I gave a big amount of my personal time in such projects (but, I'm not the only one). Now, I will not fight with anybody for such a small feature. But, in my opinion, and according to the strength of the Tikiwiki model which means many features, everything integrated, one big block.......to "just copy" an url seems to me very .....poor..... So, I know, your reply will be "ok for keeping it, but improve it". Yeah, I'm just reaching the end of the lesser magic deployment..... once this is done, I would like to start the deployment of the table smarty plugin, which, for instance is only in the coe experimental branch....I'm involved in quality team.....so I think I have enough. So, to be honest, I will surely not fix this feature. Now about your argument "The goal is not to disappoint you. But imagine that if that feature had been removed in Tiki4 (say we are happy with workaround), you would have saved that time." ==> my target is, basically, not to save time but to improve Tikiwiki....with 0 lines of code, I would save a big big amount of time....but..... ;-) I do not really understand the "UI cost" that this feature represents. Could you explain ? So, if you remove this feature, I will not be disappointed.....just, maybe, somewhere, in a way, sad :-) ...but I'm able to deal with my sadness....... Regards, pkdille 2010/1/20 Jean-Marc Libs <jea...@gm...> > On Wed, Jan 20, 2010 at 2:49 PM, Marc Laporte <ma...@ma...> > wrote: > > 1- So, do we need this feature? > > > > 2- Is workaround not sufficient? (just put URL) > > > > 3- If we think this feature provides value, will it be maintained? > > Who will document, who will extend to other features (if needed) > > > > 4- What can we do so it's less confusing for users? Perhaps move all > > the drop downs to the navigation tab? Instead of having an unexplained > > drop down choice in the blog? > > > > 5- How about if there is a single drop down in navigation tab which > > scans all blogs, all forums, etc and gives a list? and when you pick > > from that list, it fills "Home Page" with hard coded URL or keeps > > value but we'll have just one variable instead of 4? > > * I rather like (5) from a UI point of view. > > * (2) is quite sufficient for me and you, but I feel average users > will not figure it out by themselves. And they should not be expected > to read the doc just for that. > > Yes, I know that right now they do not figure it out by themselves > either, but let's improve, not regress. > > +1 to 5 > > Jyhem > > > ------------------------------------------------------------------------------ > Throughout its 18-year history, RSA Conference consistently attracts the > world's best and brightest in the field, creating opportunities for > Conference > attendees to learn about information security's most important issues > through > interactions with peers, luminaries and emerging and established companies. > http://p.sf.net/sfu/rsaconf-dev2dev > _______________________________________________ > Tikiwiki-devel mailing list > Tik...@li... > https://lists.sourceforge.net/lists/listinfo/tikiwiki-devel > |