> -* **Comments Widget*
> I noticed that the comments widget is restricted to logged in users, the
> code that generates the widget has requires_login (), this is great for
> protecting users not logged in to write.
FIXED
> -* Searches with crud.search and jqgrid on GAE*
> I got error using crud.search and jqgrid widgets, as GAE does not allow to
> perform LIKE, StartsWIth, EndsWith, Contains, etc, while do not have any
> workarround, I think that options should be disabled When it is detected
> that is working in GAE
DO NOT KNOW HOW TO. ANY ADVICE?
> *Suggestions:*( Too many things. Sorry )
?
> - *Widget_Builder:*
> Binds the code generated by widget builder direct to the page content
> editor, I think it is not hard to do with JavaScript, preventing the
> copy-paste when using widget builder
DO NOT KNOW HOW TO. ANY ADVICE?
> - *Widget* *Messages customization*
> Include the total capacity for customize the output messages in the
> standard widgets. "load_action" and "load_url" eg uses AJAX and display the
> message "loading", it would be nice to have how to pass as a parameter, a
> new message to be displayed, it is usefull for translating.
Now loading has a T('loading...')
> - *Blank lines, white space:*
> Markdown for example set spaces by using two blank spaces at the end of each
> line to make a break, I'm developing a lot with plugin_wiki and had to
> create a function just to give me white space and blank lines.
> ``{{=br(2)}}``:template
I think this should be managed by CSS I am not happy with page editors
adding spaces. In which situation do you need them?
> - *Link Targets:*
> I do not think there is a specific reason not to open external links in a
> wiki page, wikipedia does, it would be interesting to receive the parameter
> "target" by default in the marking of a [[link]] as
> [[linktitlehttp://linkurl blank]]
ok with trunk web2py you can now do
[[link http:... popup]]
'popup' maps into target="_blank"
>
> - *Page auto reference:*
> It would be interesting to have a variable that works as ALIAS to reference
> the page itself, when I need to reference the current page into a widget I
> use {{= request.args(0)}} would be more interesting to use something like
> "THISPAGE"
I added [page] request.args(0), [id] request.args(1) and [application]
request.application, and [client] for request.client
>
> - *Meta Pages: *
> As a developer I use a lot the page meta-code, but as the code grows, things
> start getting difficult to administer, would have the option to create more
> pages like meta-code, for example meta-code- xxx, meta-code-something,
> meta-code-anynameigive, and they have the same operation of the meta-code.
This would be easy to do but my feeling is, if you have lots of code
edit a model via admin.
Not sure we should encourage large meta-code
> - *Wiki Pages management: *
> - *Preview and Saving: *
> - *Lists:*
> - *Categories:*
> - *Search: *
This is a bit complex, will happen but not overnight.
If you can submit a patch I may take it.
