[web2py] Re: plugin_wiki suggestions
yes of course. Unfortunately that throws an error that heading is undefined. What is defined in meta-code or other models is not available.
[web2py] Re: plugin_wiki suggestions
Massimo,
Regarding the problem with the reserved SQL words, I entered it as an
issue on cube2py (issue 6).
Regards, D
On Feb 9, 3:17 pm, Massimo Di Pierro
wrote:
> It is in google code, inside the example app:
>
> http://code.google.com/p/cube2py/
>
> On Feb 9, 8:36 am, blackthorne wrote:
>
> > Would you consider the idea of putting plugin_wiki source code in a
> > (git?) repository for versioning?
>
> > On Feb 7, 2:26 pm, Massimo Di Pierro
> > wrote:
>
> > > If you are in mode 3 (code allowed) you can do ``{{=response.title}}
> > > ``:template
>
> > > On Feb 7, 12:29 am, Plumo wrote:
>
> > > > I also made this change to set the page title.
>
> > > > How can I access the page title from within a wiki page?
> > > > response.title is empty
>
>
Re: [web2py] Re: plugin_wiki suggestions
The WATCH THE VIDEO link is broken at Google Code.
I guess it should link to this one: http://vimeo.com/13485916
Regards!
On Wed, Feb 9, 2011 at 4:17 PM, Massimo Di Pierro <
massimo.dipie...@gmail.com> wrote:
> It is in google code, inside the example app:
>
> http://code.google.com/p/cube2py/
>
>
>
> On Feb 9, 8:36 am, blackthorne wrote:
> > Would you consider the idea of putting plugin_wiki source code in a
> > (git?) repository for versioning?
> >
> > On Feb 7, 2:26 pm, Massimo Di Pierro
> > wrote:
> >
> >
> >
> >
> >
> >
> >
> > > If you are in mode 3 (code allowed) you can do ``{{=response.title}}
> > > ``:template
> >
> > > On Feb 7, 12:29 am, Plumo wrote:
> >
> > > > I also made this change to set the page title.
> >
> > > > How can I access the page title from within a wiki page?
> > > > response.title is empty
>
[web2py] Re: plugin_wiki suggestions
It is in google code, inside the example app:
http://code.google.com/p/cube2py/
On Feb 9, 8:36 am, blackthorne wrote:
> Would you consider the idea of putting plugin_wiki source code in a
> (git?) repository for versioning?
>
> On Feb 7, 2:26 pm, Massimo Di Pierro
> wrote:
>
>
>
>
>
>
>
> > If you are in mode 3 (code allowed) you can do ``{{=response.title}}
> > ``:template
>
> > On Feb 7, 12:29 am, Plumo wrote:
>
> > > I also made this change to set the page title.
>
> > > How can I access the page title from within a wiki page?
> > > response.title is empty
[web2py] Re: plugin_wiki suggestions
Would you consider the idea of putting plugin_wiki source code in a
(git?) repository for versioning?
On Feb 7, 2:26 pm, Massimo Di Pierro
wrote:
> If you are in mode 3 (code allowed) you can do ``{{=response.title}}
> ``:template
>
> On Feb 7, 12:29 am, Plumo wrote:
>
>
>
> > I also made this change to set the page title.
>
> > How can I access the page title from within a wiki page?
> > response.title is empty
[web2py] Re: plugin_wiki suggestions
If you just want to print the variable 'heading' that you've defined,
put this in your page:
``
{{
=header
}}
``:template
On Feb 9, 12:53 am, Plumo wrote:
> OK I assume there is not.
>
> I placed the following in meta-code:
>
> heading = 'abc'
>
> But the wiki pages throw an error that heading is undefined.
>
> I also tried:
>
> {{
>
> heading = 'abc'
>
> }}
>
> and:
>
> ``
>
> {{
>
> heading = 'abc'
>
> }}
>
> ``:template
>
> but heading is still undefined.
>
> The editor level is set to 3. Is there anything else that needs to be done
> to activate meta-code?
Re: [web2py] Re: plugin_wiki suggestions
OK I assume there is not.
I placed the following in meta-code:
heading = 'abc'
But the wiki pages throw an error that heading is undefined.
I also tried:
{{
heading = 'abc'
}}
and:
``
{{
heading = 'abc'
}}
``:template
but heading is still undefined.
The editor level is set to 3. Is there anything else that needs to be done
to activate meta-code?
Re: [web2py] Re: plugin_wiki suggestions
that would require an additional database request and replicating the logic from controllers/plugin_wiki.py - is there no way to reuse the data from the controller?
Re: [web2py] Re: plugin_wiki suggestions
You can do that in meta-code page, create a wiki page called meta-code, this code will be executed before the execution of any page. 2011/2/7 Plumo > yes mode 3, but as mentioned response.title is empty (None). > > Where do I need to define response.title for the plugin to use it? I tried > models/menu.py and controllers/plugin_wiki.py without success. > views/layout.html is able to use response.title. >
[web2py] Re: plugin_wiki suggestions
yes mode 3, but as mentioned response.title is empty (None). Where do I need to define response.title for the plugin to use it? I tried models/menu.py and controllers/plugin_wiki.py without success. views/layout.html is able to use response.title.
[web2py] Re: plugin_wiki suggestions
If you are in mode 3 (code allowed) you can do ``{{=response.title}}
``:template
On Feb 7, 12:29 am, Plumo wrote:
> I also made this change to set the page title.
>
> How can I access the page title from within a wiki page?
> response.title is empty
Re: [web2py] Re: plugin_wiki suggestions
I also made this change to set the page title. How can I access the page title from within a wiki page? response.title is empty
Re: [web2py] Re: plugin_wiki suggestions
Sorry, I am so stupid... I forgotten about anchors Thanks again 2010/8/4 mdipierro > Yes you can: > > [[my reference #id1]] > > [[id1]] referenced material > > On Aug 3, 11:56 pm, Bruno Rocha wrote: > > Useful suggestion: > > > > markmin currently does not allow the creation of references to links, > this > > is very useful when the written material might be used for printing as > > well. thus present a list of links referenced in the footnote. > > > > with markdown, we can do: > > This is [an example] [id] reference-style link. > > Then, anywhere in the document, you define your link label like this, on > a > > line by Itself: > > [Id]:http://example.com/"Optional Title Here" > > > > 2010/8/1 mdipierro > > > > > > > > > Not yet. You can post here for now. Not sure it needs a new place. > > > > > If you have comments please send them asap since I am about to make > > > some changes and write a book chapter about it tomorrow. > > > > > On 1 Ago, 04:55, Bruno Rocha wrote: > > > > Sorry again, I am creating a new thread about plugin_wiki. > > > > > > I wonder if there is any public place where we can write suggestions, > > > > criticisms, and send questions exclusively about plugin_wiki, markmin > and > > > > cube2py? > > > > > > -- > > > > > >http://rochacbruno.com.br > > > > -- > > > > http://rochacbruno.com.br > -- http://rochacbruno.com.br
[web2py] Re: plugin_wiki suggestions
Please check the cube2py on google code.
I did not fix the problem with the error but now template=None should
not appear anymore.
On Aug 3, 10:48 pm, Bruno Rocha wrote:
> Thanks Massimo,
>
> template function is very well, but raises an error ticket when passing
> 'None' in http:.../template=None, as you can see in file attached.
>
> 2010/8/3 mdipierro
>
>
>
> > And I did send you the markmin2latex.py the book chap13 I posted is
> > pure markmin2latex output without any manual edit.
>
> > On Aug 3, 7:46 am, Bruno Rocha wrote:
> > > Thanks, Massimo
>
> > > I have no doubt, I will keep the markmin as markup language for my site,
> > I
> > > did a comparison and I write much faster with markmin than with LaTeX,
> > > markdown, html Or Another.
>
> > > I'll do everything possible to contribute on issues that I have
> > knowledge. if
> > > I get some success will send a patch.
>
> > > I suggested using the page title as by questions of SEO,
> > > concatenating site name + pageTitle:
> > > My Wiki Site | My Page Title Considering that
> > plugin_wiki
> > > can be used as a CMS platform (as in my case).
>
> > > {{=thanks*10}}
>
> > > 2010/8/3 mdipierro
>
> > > > I never though somebody sould have more than 1000 revisions. Let's
> > > > think about a good solution. The one you propose may be ok.
>
> > > > On Aug 2, 3:54 pm, Bruno Rocha wrote:
> > > > > - Page History
> > > > > page history does not works on GAE,
> > > >http://web2pybrasil.appspot.com/init/plugin_wiki/page_history/homeFails
> > > > > and raises a ticket
>
> > > > > There is a limit to history entries per page?
>
> > > > > I mean, if I edit a page too many times this will create too many
> > entries
> > > > in
> > > > > plugin_wiki_page_history
> > > > > I think it needs a limit, may be 20 entries per page like a FIFO
>
> > > > > 2010/8/1 Bruno Rocha
>
> > > > > > I am developing and writing a lot with plugin_wiki (cube2py). I
> > already
> > > > > > have some suggestions, observations and have also found some bugs.
> > > > > > As I'm finding more issues, I will posting here in this thread. If
> > > > someone
> > > > > > else has something to add, enjoy the thread.
>
> > > > > > I am working now on this page :
> > > > > >http://web2pybrasil.appspot.com/cursoweb2py/
>
> > > > > > *
> > > > > > *
> > > > > > *Bugs I Found:*
>
> > > > > > -* **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.
> > > > > > however, as the same widget generates the form for adding a
> > comment,
> > > > and
> > > > > > also generates a list of comments to display, it is not possible to
> > > > display
> > > > > > existing comments to a user who is not logged.
> > > > > > I suggest dividing into two widgets, one to generate the form of
> > > > insertion,
> > > > > > and this would be protected. And another to generate a list of
> > existing
> > > > > > comments, and this would free reading. this last could be used in
> > > > another
> > > > > > place eg: to show recent comments for a page.
>
> > > > > > -* 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
>
> > > > > > *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
>
> > > > > > - *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.
>
> > > > > > - *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
>
> > > > > > - *Categories:*
> > > > > > wiki or any other type of page created with plugin_wiki, IMHO, will
> > > > need
> > > > > > some kind of category management. it is not difficult to implement
> > as
> > > > > > standard, without having to create custom widgets, as I had to do.
>
> > > > > > - *Search: *
> > > > > > I created a custom widget that performs
[web2py] Re: plugin_wiki suggestions
Yes you can: [[my reference #id1]] [[id1]] referenced material On Aug 3, 11:56 pm, Bruno Rocha wrote: > Useful suggestion: > > markmin currently does not allow the creation of references to links, this > is very useful when the written material might be used for printing as > well. thus present a list of links referenced in the footnote. > > with markdown, we can do: > This is [an example] [id] reference-style link. > Then, anywhere in the document, you define your link label like this, on a > line by Itself: > [Id]:http://example.com/"Optional Title Here" > > 2010/8/1 mdipierro > > > > > Not yet. You can post here for now. Not sure it needs a new place. > > > If you have comments please send them asap since I am about to make > > some changes and write a book chapter about it tomorrow. > > > On 1 Ago, 04:55, Bruno Rocha wrote: > > > Sorry again, I am creating a new thread about plugin_wiki. > > > > I wonder if there is any public place where we can write suggestions, > > > criticisms, and send questions exclusively about plugin_wiki, markmin and > > > cube2py? > > > > -- > > > >http://rochacbruno.com.br > > -- > > http://rochacbruno.com.br
Re: [web2py] Re: plugin_wiki suggestions
Useful suggestion: markmin currently does not allow the creation of references to links, this is very useful when the written material might be used for printing as well. thus present a list of links referenced in the footnote. with markdown, we can do: This is [an example] [id] reference-style link. Then, anywhere in the document, you define your link label like this, on a line by Itself: [Id]: http://example.com/ "Optional Title Here" 2010/8/1 mdipierro > Not yet. You can post here for now. Not sure it needs a new place. > > If you have comments please send them asap since I am about to make > some changes and write a book chapter about it tomorrow. > > On 1 Ago, 04:55, Bruno Rocha wrote: > > Sorry again, I am creating a new thread about plugin_wiki. > > > > I wonder if there is any public place where we can write suggestions, > > criticisms, and send questions exclusively about plugin_wiki, markmin and > > cube2py? > > > > -- > > > > http://rochacbruno.com.br > -- http://rochacbruno.com.br
[web2py] Re: plugin_wiki suggestions
And I did send you the markmin2latex.py the book chap13 I posted is
pure markmin2latex output without any manual edit.
On Aug 3, 7:46 am, Bruno Rocha wrote:
> Thanks, Massimo
>
> I have no doubt, I will keep the markmin as markup language for my site, I
> did a comparison and I write much faster with markmin than with LaTeX,
> markdown, html Or Another.
>
> I'll do everything possible to contribute on issues that I have knowledge. if
> I get some success will send a patch.
>
> I suggested using the page title as by questions of SEO,
> concatenating site name + pageTitle:
> My Wiki Site | My Page Title Considering that plugin_wiki
> can be used as a CMS platform (as in my case).
>
> {{=thanks*10}}
>
> 2010/8/3 mdipierro
>
>
>
> > I never though somebody sould have more than 1000 revisions. Let's
> > think about a good solution. The one you propose may be ok.
>
> > On Aug 2, 3:54 pm, Bruno Rocha wrote:
> > > - Page History
> > > page history does not works on GAE,
> >http://web2pybrasil.appspot.com/init/plugin_wiki/page_history/homeFails
> > > and raises a ticket
>
> > > There is a limit to history entries per page?
>
> > > I mean, if I edit a page too many times this will create too many entries
> > in
> > > plugin_wiki_page_history
> > > I think it needs a limit, may be 20 entries per page like a FIFO
>
> > > 2010/8/1 Bruno Rocha
>
> > > > I am developing and writing a lot with plugin_wiki (cube2py). I already
> > > > have some suggestions, observations and have also found some bugs.
> > > > As I'm finding more issues, I will posting here in this thread. If
> > someone
> > > > else has something to add, enjoy the thread.
>
> > > > I am working now on this page :
> > > >http://web2pybrasil.appspot.com/cursoweb2py/
>
> > > > *
> > > > *
> > > > *Bugs I Found:*
>
> > > > -* **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.
> > > > however, as the same widget generates the form for adding a comment,
> > and
> > > > also generates a list of comments to display, it is not possible to
> > display
> > > > existing comments to a user who is not logged.
> > > > I suggest dividing into two widgets, one to generate the form of
> > insertion,
> > > > and this would be protected. And another to generate a list of existing
> > > > comments, and this would free reading. this last could be used in
> > another
> > > > place eg: to show recent comments for a page.
>
> > > > -* 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
>
> > > > *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
>
> > > > - *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.
>
> > > > - *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
>
> > > > - *Categories:*
> > > > wiki or any other type of page created with plugin_wiki, IMHO, will
> > need
> > > > some kind of category management. it is not difficult to implement as
> > > > standard, without having to create custom widgets, as I had to do.
>
> > > > - *Search: *
> > > > I created a custom widget that performs searches in titles, slugs, and
> > body
> > > > of the pages, and it is running on GAE, I believe this should be used
> > as a
> > > > widget placed on the meta-header, or meta-sidebar for example. but
> > could
> > > > be part of the plugin itself, considering that this is a basic need of
> > any
> > > > wiki page.
>
> > > > - *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 [[linktitle
> > > >http://linkurlblank]]
>
> > > > - *Preview and Saving: *
> > > > It is very annoying having to submit the page every time we need to
> > save,
> > > > then to have a preview, the savi
Re: [web2py] Re: plugin_wiki suggestions
Thanks, Massimo
I have no doubt, I will keep the markmin as markup language for my site, I
did a comparison and I write much faster with markmin than with LaTeX,
markdown, html Or Another.
I'll do everything possible to contribute on issues that I have knowledge. if
I get some success will send a patch.
I suggested using the page title as by questions of SEO,
concatenating site name + pageTitle:
My Wiki Site | My Page Title Considering that plugin_wiki
can be used as a CMS platform (as in my case).
{{=thanks*10}}
2010/8/3 mdipierro
> I never though somebody sould have more than 1000 revisions. Let's
> think about a good solution. The one you propose may be ok.
>
> On Aug 2, 3:54 pm, Bruno Rocha wrote:
> > - Page History
> > page history does not works on GAE,
> http://web2pybrasil.appspot.com/init/plugin_wiki/page_history/home Fails
> > and raises a ticket
> >
> > There is a limit to history entries per page?
> >
> > I mean, if I edit a page too many times this will create too many entries
> in
> > plugin_wiki_page_history
> > I think it needs a limit, may be 20 entries per page like a FIFO
> >
> > 2010/8/1 Bruno Rocha
> >
> >
> >
> > > I am developing and writing a lot with plugin_wiki (cube2py). I already
> > > have some suggestions, observations and have also found some bugs.
> > > As I'm finding more issues, I will posting here in this thread. If
> someone
> > > else has something to add, enjoy the thread.
> >
> > > I am working now on this page :
> > >http://web2pybrasil.appspot.com/cursoweb2py/
> >
> > > *
> > > *
> > > *Bugs I Found:*
> >
> > > -* **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.
> > > however, as the same widget generates the form for adding a comment,
> and
> > > also generates a list of comments to display, it is not possible to
> display
> > > existing comments to a user who is not logged.
> > > I suggest dividing into two widgets, one to generate the form of
> insertion,
> > > and this would be protected. And another to generate a list of existing
> > > comments, and this would free reading. this last could be used in
> another
> > > place eg: to show recent comments for a page.
> >
> > > -* 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
> >
> > > *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
> >
> > > - *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.
> >
> > > - *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
> >
> > > - *Categories:*
> > > wiki or any other type of page created with plugin_wiki, IMHO, will
> need
> > > some kind of category management. it is not difficult to implement as
> > > standard, without having to create custom widgets, as I had to do.
> >
> > > - *Search: *
> > > I created a custom widget that performs searches in titles, slugs, and
> body
> > > of the pages, and it is running on GAE, I believe this should be used
> as a
> > > widget placed on the meta-header, or meta-sidebar for example. but
> could
> > > be part of the plugin itself, considering that this is a basic need of
> any
> > > wiki page.
> >
> > > - *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 [[linktitle
> > >http://linkurl blank]]
> >
> > > - *Preview and Saving: *
> > > It is very annoying having to submit the page every time we need to
> save,
> > > then to have a preview, the saving could happen with AJAX and have
> option to
> > > view a Preview window.
> >
> > > - *Lists:*
> > > In ordered and unordered lists creates with - and +, Needs a way to
> create
> > > sublevels with lists, maybe -- and ++
> > > - A Topic
> > > -- Subtopic of A Topic
> > > --- Subtopic of a subtopic of A Topic
> > > -- Another
[web2py] Re: plugin_wiki suggestions
I just did On Aug 3, 6:06 am, Timmie wrote: > Hello, > where can we see these changes? > > Do you intend to upload? > > Thanks.
[web2py] Re: plugin_wiki suggestions
Hello, where can we see these changes? Do you intend to upload? Thanks.
[web2py] Re: plugin_wiki suggestions
I never though somebody sould have more than 1000 revisions. Let's
think about a good solution. The one you propose may be ok.
On Aug 2, 3:54 pm, Bruno Rocha wrote:
> - Page History
> page history does not works on
> GAE,http://web2pybrasil.appspot.com/init/plugin_wiki/page_history/home Fails
> and raises a ticket
>
> There is a limit to history entries per page?
>
> I mean, if I edit a page too many times this will create too many entries in
> plugin_wiki_page_history
> I think it needs a limit, may be 20 entries per page like a FIFO
>
> 2010/8/1 Bruno Rocha
>
>
>
> > I am developing and writing a lot with plugin_wiki (cube2py). I already
> > have some suggestions, observations and have also found some bugs.
> > As I'm finding more issues, I will posting here in this thread. If someone
> > else has something to add, enjoy the thread.
>
> > I am working now on this page :
> >http://web2pybrasil.appspot.com/cursoweb2py/
>
> > *
> > *
> > *Bugs I Found:*
>
> > -* **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.
> > however, as the same widget generates the form for adding a comment, and
> > also generates a list of comments to display, it is not possible to display
> > existing comments to a user who is not logged.
> > I suggest dividing into two widgets, one to generate the form of insertion,
> > and this would be protected. And another to generate a list of existing
> > comments, and this would free reading. this last could be used in another
> > place eg: to show recent comments for a page.
>
> > -* 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
>
> > *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
>
> > - *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.
>
> > - *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
>
> > - *Categories:*
> > wiki or any other type of page created with plugin_wiki, IMHO, will need
> > some kind of category management. it is not difficult to implement as
> > standard, without having to create custom widgets, as I had to do.
>
> > - *Search: *
> > I created a custom widget that performs searches in titles, slugs, and body
> > of the pages, and it is running on GAE, I believe this should be used as a
> > widget placed on the meta-header, or meta-sidebar for example. but could
> > be part of the plugin itself, considering that this is a basic need of any
> > wiki page.
>
> > - *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 [[linktitle
> >http://linkurl blank]]
>
> > - *Preview and Saving: *
> > It is very annoying having to submit the page every time we need to save,
> > then to have a preview, the saving could happen with AJAX and have option to
> > view a Preview window.
>
> > - *Lists:*
> > In ordered and unordered lists creates with - and +, Needs a way to create
> > sublevels with lists, maybe -- and ++
> > - A Topic
> > -- Subtopic of A Topic
> > --- Subtopic of a subtopic of A Topic
> > -- Another subtopic of A Topic
>
> > + A Topic
> > ++ Subtopic of A Topic
> > +++ Subtopic of a subtopic of A Topic
> > ++ Another subtopic of A Topic
>
> > - *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"
>
> > - *Wiki Pages management: *
> > Wiki Pages management "plugin_wiki / index" tends to get a little confusing
> > as the number of existing pages grows, it would be interesting to have
> > pagination, search, categorization.
>
> > - *Meta Pages: *
> > As a developer I use a lot the page meta-code, but as the code grows,
> > things start getting difficult t
[web2py] Re: plugin_wiki suggestions
I am not convinced this is a good idea.
On Aug 2, 2:11 pm, Bruno Rocha wrote:
> Another suggestion:
>
> should be the page.title field of plugin_wiki_page just
> including response.title = page.title to page controller
>
> def page():
> """
> shows a page
> """
> slug = request.args(0) or 'index'
> w = db.plugin_wiki_page
> page = db(w.slug==slug).select().first()
> response.title = page.title
> if not auth.user and (not page or not page.public or not page.active):
> redirect(URL(r=request,c='default',f='user',args='login'))
> elif not plugin_wiki_editor and (not page or not page.public or not
> page.active):
> raise HTTP(404)
> elif page and page.role and not auth.has_membership(page.role):
> raise HTTP(404)
> if request.extension=='load': return plugin_wiki.render(page.body)
> if request.extension!='html': return page.body
> return dict(page=page,slug=slug)
>
> 2010/8/1 Bruno Rocha
>
>
>
> > I am developing and writing a lot with plugin_wiki (cube2py). I already
> > have some suggestions, observations and have also found some bugs.
> > As I'm finding more issues, I will posting here in this thread. If someone
> > else has something to add, enjoy the thread.
>
> > I am working now on this page :
> >http://web2pybrasil.appspot.com/cursoweb2py/
>
> > *
> > *
> > *Bugs I Found:*
>
> > -* **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.
> > however, as the same widget generates the form for adding a comment, and
> > also generates a list of comments to display, it is not possible to display
> > existing comments to a user who is not logged.
> > I suggest dividing into two widgets, one to generate the form of insertion,
> > and this would be protected. And another to generate a list of existing
> > comments, and this would free reading. this last could be used in another
> > place eg: to show recent comments for a page.
>
> > -* 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
>
> > *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
>
> > - *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.
>
> > - *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
>
> > - *Categories:*
> > wiki or any other type of page created with plugin_wiki, IMHO, will need
> > some kind of category management. it is not difficult to implement as
> > standard, without having to create custom widgets, as I had to do.
>
> > - *Search: *
> > I created a custom widget that performs searches in titles, slugs, and body
> > of the pages, and it is running on GAE, I believe this should be used as a
> > widget placed on the meta-header, or meta-sidebar for example. but could
> > be part of the plugin itself, considering that this is a basic need of any
> > wiki page.
>
> > - *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 [[linktitle
> >http://linkurl blank]]
>
> > - *Preview and Saving: *
> > It is very annoying having to submit the page every time we need to save,
> > then to have a preview, the saving could happen with AJAX and have option to
> > view a Preview window.
>
> > - *Lists:*
> > In ordered and unordered lists creates with - and +, Needs a way to create
> > sublevels with lists, maybe -- and ++
> > - A Topic
> > -- Subtopic of A Topic
> > --- Subtopic of a subtopic of A Topic
> > -- Another subtopic of A Topic
>
> > + A Topic
> > ++ Subtopic of A Topic
> > +++ Subtopic of a subtopic of A Topic
> > ++ Another subtopic of A Topic
>
> > - *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 inte
[web2py] Re: plugin_wiki suggestions
fixed too. This was a markmin bug.
On Aug 2, 8:23 am, Bruno Rocha wrote:
> Another BUG in markmin render
>
> paragraph with **bold**, ''italic'' and ``code``.but:
>
> **text** renders as text
>
> **text:** renders as **text:**
>
> the same happens if we put any mark, point or accent as the last in Markup
>
> **text()** renders as **text()**
>
> where should render as text()
>
> 2010/8/2 Bruno Rocha
>
>
>
> > Error on "select" widget, trying to fetch non UTF-8 text records, People
> > wrote a message in portuguese, a lot of accents, [ á, é, ã, ê, í] , to
> > insert with "create"widget no problem, then I can view the records on GAE
> > admin.
>
> > But when I try to select the accentuated records with " select"widget its
> > raise an error:
>
> > the same occurs when I give accentuated totle for a page, inserts ok,
> > select fails.
>
> > Traceback (most recent call last):
>
> > File
> > "/base/data/home/apps/web2pybrasil/4.343788305571582046/applications/init/models/plugin_wiki.py",
> > line 555, in render_widget
> > html = getattr(PluginWikiWidgets,name)(**args)
> > File
> > "/base/data/home/apps/web2pybrasil/4.343788305571582046/applications/init/models/plugin_wiki.py",
> > line 252, in jqgrid
> > columns = [x.strip() for x in db[table].fields if
> > db[table][x.strip()].readable]
> > File
> > "/base/data/home/apps/web2pybrasil/4.343788305571582046/gluon/sql.py", line
> > 1323, in __getitem__
> > return dict.__getitem__(self, str(key))
> > KeyError: 'contato'
>
> > 2010/8/1 Bruno Rocha
>
> >> SlideShow widget also does not runs on GAE.
>
> >> try it;http://web2pybrasil.appspot.com/init/plugin_wiki/page/images
>
> >> the code:
> >>http://web2pybrasil.appspot.com/init/plugin_wiki/page.code/images
>
> >> Given an image saved as BLOB in GAE, how to retrieve this image URL to put
> >> it on Wiki Page body?
>
> >> 2010/8/1 Bruno Rocha
>
> >>> Page Attachments does not works on GAE
>
> >>> 2010/8/1 Bruno Rocha
>
> >>> I am developing and writing a lot with plugin_wiki (cube2py). I already
> have some suggestions, observations and have also found some bugs.
> As I'm finding more issues, I will posting here in this thread. If
> someone else has something to add, enjoy the thread.
>
> I am working now on this page :
> http://web2pybrasil.appspot.com/cursoweb2py/
>
> *
> *
> *Bugs I Found:*
>
> -* **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.
> however, as the same widget generates the form for adding a comment, and
> also generates a list of comments to display, it is not possible to
> display
> existing comments to a user who is not logged.
> I suggest dividing into two widgets, one to generate the form of
> insertion, and this would be protected. And another to generate a list
> of existing comments, and this would free reading. this last could be
> used
> in another place eg: to show recent comments for a page.
>
> -* 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
>
> *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
>
> - *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.
>
> - *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
>
> - *Categories:*
> wiki or any other type of page created with plugin_wiki, IMHO, will need
> some kind of category management. it is not difficult to implement as
> standard, without having to create custom widgets, as I had to do.
>
> - *Search: *
> I created a custom widget that performs searches in titles, slugs, and
> body of the pages, and it is running on GAE, I believe this should be
> used
> as a widget placed on the meta-header, or meta-sidebar for example. but
> could be p
[web2py] Re: plugin_wiki suggestions
``
name: comment
table: [page]
record_id: 1
``:comment
not sure this is a good idea but for now it should work.
On Aug 1, 9:33 am, rochacbruno wrote:
> I mean that THISPAGE should be a shortcut to {{=request.args(0)}}
>
> THISPAGE = '{{=request.args(0)}}'
>
> "
> name: comments
> table: THISPAGE
> record_id: 1
> ":comments
>
> or
>
> "
> {{=THISPAGE}}
> ":template
>
> Sent from my iPhone
>
> On 01/08/2010, at 05:40, qqsaqq wrote:
>
> > Concerning Your THISPAGE idea:
>
> > I think what You mean can be achieved simply by writing
> > [[this page #]]
> > I tried it, works great.
>
> > On Aug 1, 6:54 am, Bruno Rocha wrote:
> >> I am developing and writing a lot with plugin_wiki (cube2py). I already
> >> have
> >> some suggestions, observations and have also found some bugs.
> >> As I'm finding more issues, I will posting here in this thread. If someone
> >> else has something to add, enjoy the thread.
>
> >> I am working now on this page :http://web2pybrasil.appspot.com/cursoweb2py/
>
> >> *
> >> *
> >> *Bugs I Found:*
>
> >> -* **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.
> >> however, as the same widget generates the form for adding a comment, and
> >> also generates a list of comments to display, it is not possible to display
> >> existing comments to a user who is not logged.
> >> I suggest dividing into two widgets, one to generate the form of insertion,
> >> and this would be protected. And another to generate a list of existing
> >> comments, and this would free reading. this last could be used in another
> >> place eg: to show recent comments for a page.
>
> >> -* 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
>
> >> *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
>
> >> - *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.
>
> >> - *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
>
> >> - *Categories:*
> >> wiki or any other type of page created with plugin_wiki, IMHO, will need
> >> some kind of category management. it is not difficult to implement as
> >> standard, without having to create custom widgets, as I had to do.
>
> >> - *Search: *
> >> I created a custom widget that performs searches in titles, slugs, and body
> >> of the pages, and it is running on GAE, I believe this should be used as a
> >> widget placed on the meta-header, or meta-sidebar for example. but could be
> >> part of the plugin itself, considering that this is a basic need of any
> >> wiki
> >> page.
>
> >> - *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://linkurlblank]]
>
> >> - *Preview and Saving: *
> >> It is very annoying having to submit the page every time we need to save,
> >> then to have a preview, the saving could happen with AJAX and have option
> >> to
> >> view a Preview window.
>
> >> - *Lists:*
> >> In ordered and unordered lists creates with - and +, Needs a way to create
> >> sublevels with lists, maybe -- and ++
> >> - A Topic
> >> -- Subtopic of A Topic
> >> --- Subtopic of a subtopic of A Topic
> >> -- Another subtopic of A Topic
>
> >> + A Topic
> >> ++ Subtopic of A Topic
> >> +++ Subtopic of a subtopic of A Topic
> >> ++ Another subtopic of A Topic
>
> >> - *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"
>
> >> - *Wiki Pages management: *
> >> Wiki Pages management "plugin_wiki / index" tends to get a little confusing
> >> as the number of existing pages grows, it would be interesting to have
> >> pagination, sea
[web2py] Re: plugin_wiki suggestions
Done. please check it.
On Aug 1, 2:03 am, Bruno Rocha wrote:
> One more suggestion for today.
>
> It will be great to create new pages from "template", as creating a template
> page with standard texts, widgets and other stuff, we have any way to
> duplicate that page.
>
> actually just creating a way to duplicate certain page will do that work.
>
> {{=thanks}}
>
> 2010/8/1 Bruno Rocha
>
>
>
> > But the ".code" thing, is usefull for editors, so there is a way to ".code"
> > output be available only to logged in editor users?
>
> > its usefull to check the code as in
> >http://web2pybrasil.appspot.com/cursoweb2py/plugin_wiki/page.code/met...
>
> > 2010/8/1 Bruno Rocha
>
> >> I Just found one more thing:
>
> >> take this page by example:
>
> >>http://web2pybrasil.appspot.com/cursoweb2py/plugin_wiki/page/curso-we...
>
> >> now add a ".code" to he action
>
> >>http://web2pybrasil.appspot.com/cursoweb2py/plugin_wiki/page.code/cur...
>
> >> even logged out, you can see the code behind the page, as we pass
> >> parameters to custom widgets, I think this could not happens.
>
> >> but, it is usefull to still have page.load, page.xml, page.json, and
> >> page.rss functions.
>
> >> 2010/8/1 Bruno Rocha
>
> >> I am developing and writing a lot with plugin_wiki (cube2py). I already
> >>> have some suggestions, observations and have also found some bugs.
> >>> As I'm finding more issues, I will posting here in this thread. If
> >>> someone else has something to add, enjoy the thread.
>
> >>> I am working now on this page :
> >>>http://web2pybrasil.appspot.com/cursoweb2py/
>
> >>> *
> >>> *
> >>> *Bugs I Found:*
>
> >>> -* **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.
> >>> however, as the same widget generates the form for adding a comment, and
> >>> also generates a list of comments to display, it is not possible to
> >>> display
> >>> existing comments to a user who is not logged.
> >>> I suggest dividing into two widgets, one to generate the form of
> >>> insertion, and this would be protected. And another to generate a list
> >>> of existing comments, and this would free reading. this last could be used
> >>> in another place eg: to show recent comments for a page.
>
> >>> -* 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
>
> >>> *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
>
> >>> - *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.
>
> >>> - *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
>
> >>> - *Categories:*
> >>> wiki or any other type of page created with plugin_wiki, IMHO, will need
> >>> some kind of category management. it is not difficult to implement as
> >>> standard, without having to create custom widgets, as I had to do.
>
> >>> - *Search: *
> >>> I created a custom widget that performs searches in titles, slugs, and
> >>> body of the pages, and it is running on GAE, I believe this should be
> >>> used
> >>> as a widget placed on the meta-header, or meta-sidebar for example. but
> >>> could be part of the plugin itself, considering that this is a basic need
> >>> of
> >>> any wiki page.
>
> >>> - *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 [[linktitle
> >>>http://linkurl blank]]
>
> >>> - *Preview and Saving: *
> >>> It is very annoying having to submit the page every time we need to
> >>> save, then to have a preview, the saving could happen with AJAX and have
> >>> option to view a Preview window.
>
> >>> - *Lists:*
> >>> In ordered and unordered lists creates with - and +, Needs a way to
> >>> create sublevels with lists, maybe -- and ++
> >>> - A Topic
> >>> -- Subtopic of A Topic
> >>> --- Subtopic of a
[web2py] Re: plugin_wiki suggestions
> -* **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.
Re: [web2py] Re: plugin_wiki suggestions
- Page History
page history does not works on GAE,
http://web2pybrasil.appspot.com/init/plugin_wiki/page_history/home Fails
and raises a ticket
There is a limit to history entries per page?
I mean, if I edit a page too many times this will create too many entries in
plugin_wiki_page_history
I think it needs a limit, may be 20 entries per page like a FIFO
2010/8/1 Bruno Rocha
> I am developing and writing a lot with plugin_wiki (cube2py). I already
> have some suggestions, observations and have also found some bugs.
> As I'm finding more issues, I will posting here in this thread. If someone
> else has something to add, enjoy the thread.
>
> I am working now on this page :
> http://web2pybrasil.appspot.com/cursoweb2py/
>
> *
> *
> *Bugs I Found:*
>
> -* **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.
> however, as the same widget generates the form for adding a comment, and
> also generates a list of comments to display, it is not possible to display
> existing comments to a user who is not logged.
> I suggest dividing into two widgets, one to generate the form of insertion,
> and this would be protected. And another to generate a list of existing
> comments, and this would free reading. this last could be used in another
> place eg: to show recent comments for a page.
>
> -* 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
>
>
> *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
>
> - *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.
>
> - *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
>
> - *Categories:*
> wiki or any other type of page created with plugin_wiki, IMHO, will need
> some kind of category management. it is not difficult to implement as
> standard, without having to create custom widgets, as I had to do.
>
> - *Search: *
> I created a custom widget that performs searches in titles, slugs, and body
> of the pages, and it is running on GAE, I believe this should be used as a
> widget placed on the meta-header, or meta-sidebar for example. but could
> be part of the plugin itself, considering that this is a basic need of any
> wiki page.
>
> - *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 [[linktitle
> http://linkurl blank]]
>
> - *Preview and Saving: *
> It is very annoying having to submit the page every time we need to save,
> then to have a preview, the saving could happen with AJAX and have option to
> view a Preview window.
>
> - *Lists:*
> In ordered and unordered lists creates with - and +, Needs a way to create
> sublevels with lists, maybe -- and ++
> - A Topic
> -- Subtopic of A Topic
> --- Subtopic of a subtopic of A Topic
> -- Another subtopic of A Topic
>
> + A Topic
> ++ Subtopic of A Topic
> +++ Subtopic of a subtopic of A Topic
> ++ Another subtopic of A Topic
>
> - *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"
>
> - *Wiki Pages management: *
> Wiki Pages management "plugin_wiki / index" tends to get a little confusing
> as the number of existing pages grows, it would be interesting to have
> pagination, search, categorization.
>
> - *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.
>
> By Now , that's it. As Im using I will send more thoughts about it.
> I am available for any help or tests you need.
>
> {{=thanks}}
>
> ---
>
Re: [web2py] Re: plugin_wiki suggestions
Another suggestion:
should be the page.title field of plugin_wiki_page just
including response.title = page.title to page controller
def page():
"""
shows a page
"""
slug = request.args(0) or 'index'
w = db.plugin_wiki_page
page = db(w.slug==slug).select().first()
response.title = page.title
if not auth.user and (not page or not page.public or not page.active):
redirect(URL(r=request,c='default',f='user',args='login'))
elif not plugin_wiki_editor and (not page or not page.public or not
page.active):
raise HTTP(404)
elif page and page.role and not auth.has_membership(page.role):
raise HTTP(404)
if request.extension=='load': return plugin_wiki.render(page.body)
if request.extension!='html': return page.body
return dict(page=page,slug=slug)
2010/8/1 Bruno Rocha
> I am developing and writing a lot with plugin_wiki (cube2py). I already
> have some suggestions, observations and have also found some bugs.
> As I'm finding more issues, I will posting here in this thread. If someone
> else has something to add, enjoy the thread.
>
> I am working now on this page :
> http://web2pybrasil.appspot.com/cursoweb2py/
>
> *
> *
> *Bugs I Found:*
>
> -* **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.
> however, as the same widget generates the form for adding a comment, and
> also generates a list of comments to display, it is not possible to display
> existing comments to a user who is not logged.
> I suggest dividing into two widgets, one to generate the form of insertion,
> and this would be protected. And another to generate a list of existing
> comments, and this would free reading. this last could be used in another
> place eg: to show recent comments for a page.
>
> -* 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
>
>
> *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
>
> - *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.
>
> - *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
>
> - *Categories:*
> wiki or any other type of page created with plugin_wiki, IMHO, will need
> some kind of category management. it is not difficult to implement as
> standard, without having to create custom widgets, as I had to do.
>
> - *Search: *
> I created a custom widget that performs searches in titles, slugs, and body
> of the pages, and it is running on GAE, I believe this should be used as a
> widget placed on the meta-header, or meta-sidebar for example. but could
> be part of the plugin itself, considering that this is a basic need of any
> wiki page.
>
> - *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 [[linktitle
> http://linkurl blank]]
>
> - *Preview and Saving: *
> It is very annoying having to submit the page every time we need to save,
> then to have a preview, the saving could happen with AJAX and have option to
> view a Preview window.
>
> - *Lists:*
> In ordered and unordered lists creates with - and +, Needs a way to create
> sublevels with lists, maybe -- and ++
> - A Topic
> -- Subtopic of A Topic
> --- Subtopic of a subtopic of A Topic
> -- Another subtopic of A Topic
>
> + A Topic
> ++ Subtopic of A Topic
> +++ Subtopic of a subtopic of A Topic
> ++ Another subtopic of A Topic
>
> - *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"
>
> - *Wiki Pages management: *
> Wiki Pages management "plugin_wiki / index" tends to get a little confusing
> as the number of existing pages grows, it would be interesting to have
> pagination, search, categorization.
>
> - *Met
Re: [web2py] Re: plugin_wiki suggestions
Another BUG in markmin render
paragraph with **bold**, ''italic'' and ``code``.but:
**text** renders as text
**text:** renders as **text:**
the same happens if we put any mark, point or accent as the last in Markup
**text()** renders as **text()**
where should render as text()
2010/8/2 Bruno Rocha
> Error on "select" widget, trying to fetch non UTF-8 text records, People
> wrote a message in portuguese, a lot of accents, [ á, é, ã, ê, í] , to
> insert with "create"widget no problem, then I can view the records on GAE
> admin.
>
>
> But when I try to select the accentuated records with " select"widget its
> raise an error:
>
>
> the same occurs when I give accentuated totle for a page, inserts ok, select
> fails.
>
>
> Traceback (most recent call last):
>
> File
> "/base/data/home/apps/web2pybrasil/4.343788305571582046/applications/init/models/plugin_wiki.py",
> line 555, in render_widget
> html = getattr(PluginWikiWidgets,name)(**args)
> File
> "/base/data/home/apps/web2pybrasil/4.343788305571582046/applications/init/models/plugin_wiki.py",
> line 252, in jqgrid
> columns = [x.strip() for x in db[table].fields if
> db[table][x.strip()].readable]
> File "/base/data/home/apps/web2pybrasil/4.343788305571582046/gluon/sql.py",
> line 1323, in __getitem__
> return dict.__getitem__(self, str(key))
> KeyError: 'contato'
>
>
>
> 2010/8/1 Bruno Rocha
>
>> SlideShow widget also does not runs on GAE.
>>
>> try it; http://web2pybrasil.appspot.com/init/plugin_wiki/page/images
>>
>> the code:
>> http://web2pybrasil.appspot.com/init/plugin_wiki/page.code/images
>>
>> Given an image saved as BLOB in GAE, how to retrieve this image URL to put
>> it on Wiki Page body?
>>
>>
>> 2010/8/1 Bruno Rocha
>>
>>> Page Attachments does not works on GAE
>>>
>>> 2010/8/1 Bruno Rocha
>>>
>>> I am developing and writing a lot with plugin_wiki (cube2py). I already
have some suggestions, observations and have also found some bugs.
As I'm finding more issues, I will posting here in this thread. If
someone else has something to add, enjoy the thread.
I am working now on this page :
http://web2pybrasil.appspot.com/cursoweb2py/
*
*
*Bugs I Found:*
-* **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.
however, as the same widget generates the form for adding a comment, and
also generates a list of comments to display, it is not possible to display
existing comments to a user who is not logged.
I suggest dividing into two widgets, one to generate the form of
insertion, and this would be protected. And another to generate a list
of existing comments, and this would free reading. this last could be used
in another place eg: to show recent comments for a page.
-* 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
*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
- *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.
- *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
- *Categories:*
wiki or any other type of page created with plugin_wiki, IMHO, will need
some kind of category management. it is not difficult to implement as
standard, without having to create custom widgets, as I had to do.
- *Search: *
I created a custom widget that performs searches in titles, slugs, and
body of the pages, and it is running on GAE, I believe this should be used
as a widget placed on the meta-header, or meta-sidebar for example. but
could be part of the plugin itself, considering that this is a basic need
of
any wiki page.
- *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 interest
Re: [web2py] Re: plugin_wiki suggestions
Error on "select" widget, trying to fetch non UTF-8 text records,
People wrote a message in portuguese, a lot of accents, [ á, é, ã, ê,
í] , to insert with "create"widget no problem, then I can view the
records on GAE admin.
But when I try to select the accentuated records with " select"widget
its raise an error:
the same occurs when I give accentuated totle for a page, inserts ok,
select fails.
Traceback (most recent call last):
File
"/base/data/home/apps/web2pybrasil/4.343788305571582046/applications/init/models/plugin_wiki.py",
line 555, in render_widget
html = getattr(PluginWikiWidgets,name)(**args)
File
"/base/data/home/apps/web2pybrasil/4.343788305571582046/applications/init/models/plugin_wiki.py",
line 252, in jqgrid
columns = [x.strip() for x in db[table].fields if
db[table][x.strip()].readable]
File "/base/data/home/apps/web2pybrasil/4.343788305571582046/gluon/sql.py",
line 1323, in __getitem__
return dict.__getitem__(self, str(key))
KeyError: 'contato'
2010/8/1 Bruno Rocha
> SlideShow widget also does not runs on GAE.
>
> try it; http://web2pybrasil.appspot.com/init/plugin_wiki/page/images
>
> the code:
> http://web2pybrasil.appspot.com/init/plugin_wiki/page.code/images
>
> Given an image saved as BLOB in GAE, how to retrieve this image URL to put
> it on Wiki Page body?
>
>
> 2010/8/1 Bruno Rocha
>
>> Page Attachments does not works on GAE
>>
>> 2010/8/1 Bruno Rocha
>>
>> I am developing and writing a lot with plugin_wiki (cube2py). I already
>>> have some suggestions, observations and have also found some bugs.
>>> As I'm finding more issues, I will posting here in this thread. If
>>> someone else has something to add, enjoy the thread.
>>>
>>> I am working now on this page :
>>> http://web2pybrasil.appspot.com/cursoweb2py/
>>>
>>> *
>>> *
>>> *Bugs I Found:*
>>>
>>> -* **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.
>>> however, as the same widget generates the form for adding a comment, and
>>> also generates a list of comments to display, it is not possible to display
>>> existing comments to a user who is not logged.
>>> I suggest dividing into two widgets, one to generate the form of
>>> insertion, and this would be protected. And another to generate a list
>>> of existing comments, and this would free reading. this last could be used
>>> in another place eg: to show recent comments for a page.
>>>
>>> -* 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
>>>
>>>
>>> *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
>>>
>>> - *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.
>>>
>>> - *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
>>>
>>> - *Categories:*
>>> wiki or any other type of page created with plugin_wiki, IMHO, will need
>>> some kind of category management. it is not difficult to implement as
>>> standard, without having to create custom widgets, as I had to do.
>>>
>>> - *Search: *
>>> I created a custom widget that performs searches in titles, slugs, and
>>> body of the pages, and it is running on GAE, I believe this should be used
>>> as a widget placed on the meta-header, or meta-sidebar for example. but
>>> could be part of the plugin itself, considering that this is a basic need of
>>> any wiki page.
>>>
>>> - *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 [[linktitle
>>> http://linkurl blank]]
>>>
>>> - *Preview and Saving: *
>>> It is very annoying having to submit the page every time we need to
>>> save, then to have a preview, the saving could happen with AJAX and have
>>> option to view a Preview window.
>>>
>>> - *Lists:*
>>> In ordered and unordered lists creates with - and +, Needs a way to
>>> create sublevels with lists, ma
Re: [web2py] Re: plugin_wiki suggestions
SlideShow widget also does not runs on GAE.
try it; http://web2pybrasil.appspot.com/init/plugin_wiki/page/images
the code: http://web2pybrasil.appspot.com/init/plugin_wiki/page.code/images
Given an image saved as BLOB in GAE, how to retrieve this image URL to put
it on Wiki Page body?
2010/8/1 Bruno Rocha
> Page Attachments does not works on GAE
>
> 2010/8/1 Bruno Rocha
>
> I am developing and writing a lot with plugin_wiki (cube2py). I already
>> have some suggestions, observations and have also found some bugs.
>> As I'm finding more issues, I will posting here in this thread. If
>> someone else has something to add, enjoy the thread.
>>
>> I am working now on this page :
>> http://web2pybrasil.appspot.com/cursoweb2py/
>>
>> *
>> *
>> *Bugs I Found:*
>>
>> -* **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.
>> however, as the same widget generates the form for adding a comment, and
>> also generates a list of comments to display, it is not possible to display
>> existing comments to a user who is not logged.
>> I suggest dividing into two widgets, one to generate the form of
>> insertion, and this would be protected. And another to generate a list of
>> existing comments, and this would free reading. this last could be used in
>> another place eg: to show recent comments for a page.
>>
>> -* 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
>>
>>
>> *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
>>
>> - *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.
>>
>> - *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
>>
>> - *Categories:*
>> wiki or any other type of page created with plugin_wiki, IMHO, will need
>> some kind of category management. it is not difficult to implement as
>> standard, without having to create custom widgets, as I had to do.
>>
>> - *Search: *
>> I created a custom widget that performs searches in titles, slugs, and
>> body of the pages, and it is running on GAE, I believe this should be used
>> as a widget placed on the meta-header, or meta-sidebar for example. but
>> could be part of the plugin itself, considering that this is a basic need of
>> any wiki page.
>>
>> - *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 [[linktitle
>> http://linkurl blank]]
>>
>> - *Preview and Saving: *
>> It is very annoying having to submit the page every time we need to save,
>> then to have a preview, the saving could happen with AJAX and have option to
>> view a Preview window.
>>
>> - *Lists:*
>> In ordered and unordered lists creates with - and +, Needs a way to
>> create sublevels with lists, maybe -- and ++
>> - A Topic
>> -- Subtopic of A Topic
>> --- Subtopic of a subtopic of A Topic
>> -- Another subtopic of A Topic
>>
>> + A Topic
>> ++ Subtopic of A Topic
>> +++ Subtopic of a subtopic of A Topic
>> ++ Another subtopic of A Topic
>>
>> - *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"
>>
>> - *Wiki Pages management: *
>> Wiki Pages management "plugin_wiki / index" tends to get a little
>> confusing as the number of existing pages grows, it would be interesting to
>> have pagination, search, categorization.
>>
>> - *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.
>>
>> By Now , that's it. As Im using I will sen
Re: [web2py] Re: plugin_wiki suggestions
Page Attachments does not works on GAE
2010/8/1 Bruno Rocha
> I am developing and writing a lot with plugin_wiki (cube2py). I already
> have some suggestions, observations and have also found some bugs.
> As I'm finding more issues, I will posting here in this thread. If someone
> else has something to add, enjoy the thread.
>
> I am working now on this page :
> http://web2pybrasil.appspot.com/cursoweb2py/
>
> *
> *
> *Bugs I Found:*
>
> -* **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.
> however, as the same widget generates the form for adding a comment, and
> also generates a list of comments to display, it is not possible to display
> existing comments to a user who is not logged.
> I suggest dividing into two widgets, one to generate the form of insertion,
> and this would be protected. And another to generate a list of existing
> comments, and this would free reading. this last could be used in another
> place eg: to show recent comments for a page.
>
> -* 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
>
>
> *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
>
> - *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.
>
> - *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
>
> - *Categories:*
> wiki or any other type of page created with plugin_wiki, IMHO, will need
> some kind of category management. it is not difficult to implement as
> standard, without having to create custom widgets, as I had to do.
>
> - *Search: *
> I created a custom widget that performs searches in titles, slugs, and body
> of the pages, and it is running on GAE, I believe this should be used as a
> widget placed on the meta-header, or meta-sidebar for example. but could
> be part of the plugin itself, considering that this is a basic need of any
> wiki page.
>
> - *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 [[linktitle
> http://linkurl blank]]
>
> - *Preview and Saving: *
> It is very annoying having to submit the page every time we need to save,
> then to have a preview, the saving could happen with AJAX and have option to
> view a Preview window.
>
> - *Lists:*
> In ordered and unordered lists creates with - and +, Needs a way to create
> sublevels with lists, maybe -- and ++
> - A Topic
> -- Subtopic of A Topic
> --- Subtopic of a subtopic of A Topic
> -- Another subtopic of A Topic
>
> + A Topic
> ++ Subtopic of A Topic
> +++ Subtopic of a subtopic of A Topic
> ++ Another subtopic of A Topic
>
> - *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"
>
> - *Wiki Pages management: *
> Wiki Pages management "plugin_wiki / index" tends to get a little confusing
> as the number of existing pages grows, it would be interesting to have
> pagination, search, categorization.
>
> - *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.
>
> By Now , that's it. As Im using I will send more thoughts about it.
> I am available for any help or tests you need.
>
> {{=thanks}}
>
> ---
> rochacbruno.com.br
> @rochacbruno
>
> 2010/8/1 mdipierro
>
> Fornow you can post here.Please send your comments asap because I am
>> about to revise it and write a book chapter about it.
>>
>> On 1 Ago, 04:55, Bruno Rocha wrote:
>> > Sorry again, I am creating a new thread about plugin_wiki.
>> >
>> > I wonder if there
Re: [web2py] Re: plugin_wiki suggestions
I mean that THISPAGE should be a shortcut to {{=request.args(0)}}
THISPAGE = '{{=request.args(0)}}'
"
name: comments
table: THISPAGE
record_id: 1
":comments
or
"
{{=THISPAGE}}
":template
Sent from my iPhone
On 01/08/2010, at 05:40, qqsaqq wrote:
> Concerning Your THISPAGE idea:
>
> I think what You mean can be achieved simply by writing
> [[this page #]]
> I tried it, works great.
>
> On Aug 1, 6:54 am, Bruno Rocha wrote:
>> I am developing and writing a lot with plugin_wiki (cube2py). I already have
>> some suggestions, observations and have also found some bugs.
>> As I'm finding more issues, I will posting here in this thread. If someone
>> else has something to add, enjoy the thread.
>>
>> I am working now on this page :http://web2pybrasil.appspot.com/cursoweb2py/
>>
>> *
>> *
>> *Bugs I Found:*
>>
>> -* **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.
>> however, as the same widget generates the form for adding a comment, and
>> also generates a list of comments to display, it is not possible to display
>> existing comments to a user who is not logged.
>> I suggest dividing into two widgets, one to generate the form of insertion,
>> and this would be protected. And another to generate a list of existing
>> comments, and this would free reading. this last could be used in another
>> place eg: to show recent comments for a page.
>>
>> -* 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
>>
>> *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
>>
>> - *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.
>>
>> - *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
>>
>> - *Categories:*
>> wiki or any other type of page created with plugin_wiki, IMHO, will need
>> some kind of category management. it is not difficult to implement as
>> standard, without having to create custom widgets, as I had to do.
>>
>> - *Search: *
>> I created a custom widget that performs searches in titles, slugs, and body
>> of the pages, and it is running on GAE, I believe this should be used as a
>> widget placed on the meta-header, or meta-sidebar for example. but could be
>> part of the plugin itself, considering that this is a basic need of any wiki
>> page.
>>
>> - *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]]
>>
>> - *Preview and Saving: *
>> It is very annoying having to submit the page every time we need to save,
>> then to have a preview, the saving could happen with AJAX and have option to
>> view a Preview window.
>>
>> - *Lists:*
>> In ordered and unordered lists creates with - and +, Needs a way to create
>> sublevels with lists, maybe -- and ++
>> - A Topic
>> -- Subtopic of A Topic
>> --- Subtopic of a subtopic of A Topic
>> -- Another subtopic of A Topic
>>
>> + A Topic
>> ++ Subtopic of A Topic
>> +++ Subtopic of a subtopic of A Topic
>> ++ Another subtopic of A Topic
>>
>> - *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"
>>
>> - *Wiki Pages management: *
>> Wiki Pages management "plugin_wiki / index" tends to get a little confusing
>> as the number of existing pages grows, it would be interesting to have
>> pagination, search, categorization.
>>
>> - *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
Re: [web2py] Re: plugin_wiki suggestions
No
I was talking about an alias to {{= request.args(0)}} used in :widget and
:template
Sent from my iPhone
On 01/08/2010, at 05:40, qqsaqq wrote:
> Concerning Your THISPAGE idea:
>
> I think what You mean can be achieved simply by writing
> [[this page #]]
> I tried it, works great.
>
> On Aug 1, 6:54 am, Bruno Rocha wrote:
>> I am developing and writing a lot with plugin_wiki (cube2py). I already have
>> some suggestions, observations and have also found some bugs.
>> As I'm finding more issues, I will posting here in this thread. If someone
>> else has something to add, enjoy the thread.
>>
>> I am working now on this page :http://web2pybrasil.appspot.com/cursoweb2py/
>>
>> *
>> *
>> *Bugs I Found:*
>>
>> -* **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.
>> however, as the same widget generates the form for adding a comment, and
>> also generates a list of comments to display, it is not possible to display
>> existing comments to a user who is not logged.
>> I suggest dividing into two widgets, one to generate the form of insertion,
>> and this would be protected. And another to generate a list of existing
>> comments, and this would free reading. this last could be used in another
>> place eg: to show recent comments for a page.
>>
>> -* 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
>>
>> *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
>>
>> - *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.
>>
>> - *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
>>
>> - *Categories:*
>> wiki or any other type of page created with plugin_wiki, IMHO, will need
>> some kind of category management. it is not difficult to implement as
>> standard, without having to create custom widgets, as I had to do.
>>
>> - *Search: *
>> I created a custom widget that performs searches in titles, slugs, and body
>> of the pages, and it is running on GAE, I believe this should be used as a
>> widget placed on the meta-header, or meta-sidebar for example. but could be
>> part of the plugin itself, considering that this is a basic need of any wiki
>> page.
>>
>> - *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]]
>>
>> - *Preview and Saving: *
>> It is very annoying having to submit the page every time we need to save,
>> then to have a preview, the saving could happen with AJAX and have option to
>> view a Preview window.
>>
>> - *Lists:*
>> In ordered and unordered lists creates with - and +, Needs a way to create
>> sublevels with lists, maybe -- and ++
>> - A Topic
>> -- Subtopic of A Topic
>> --- Subtopic of a subtopic of A Topic
>> -- Another subtopic of A Topic
>>
>> + A Topic
>> ++ Subtopic of A Topic
>> +++ Subtopic of a subtopic of A Topic
>> ++ Another subtopic of A Topic
>>
>> - *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"
>>
>> - *Wiki Pages management: *
>> Wiki Pages management "plugin_wiki / index" tends to get a little confusing
>> as the number of existing pages grows, it would be interesting to have
>> pagination, search, categorization.
>>
>> - *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.
>>
>> By Now , that's it. As Im using I will send more thoughts about it.
>> I am ava
[web2py] Re: plugin_wiki suggestions
Concerning Your THISPAGE idea:
You can achieve this simply by writing
[[this page #]]
in the markmin editor.
This will create a Link with the name "this page" and it links to
http://127.0.0.1:8000/cube2py/plugin_wiki/page/home# (mind the # in
the end!)
On Aug 1, 7:22 am, Bruno Rocha wrote:
> But the ".code" thing, is usefull for editors, so there is a way to ".code"
> output be available only to logged in editor users?
>
> its usefull to check the code as
> inhttp://web2pybrasil.appspot.com/cursoweb2py/plugin_wiki/page.code/met...
>
> 2010/8/1 Bruno Rocha
>
>
>
> > I Just found one more thing:
>
> > take this page by example:
>
> >http://web2pybrasil.appspot.com/cursoweb2py/plugin_wiki/page/curso-we...
>
> > now add a ".code" to he action
>
> >http://web2pybrasil.appspot.com/cursoweb2py/plugin_wiki/page.code/cur...
>
> > even logged out, you can see the code behind the page, as we pass
> > parameters to custom widgets, I think this could not happens.
>
> > but, it is usefull to still have page.load, page.xml, page.json, and
> > page.rss functions.
>
> > 2010/8/1 Bruno Rocha
>
> > I am developing and writing a lot with plugin_wiki (cube2py). I already
> >> have some suggestions, observations and have also found some bugs.
> >> As I'm finding more issues, I will posting here in this thread. If
> >> someone else has something to add, enjoy the thread.
>
> >> I am working now on this page :
> >>http://web2pybrasil.appspot.com/cursoweb2py/
>
> >> *
> >> *
> >> *Bugs I Found:*
>
> >> -* **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.
> >> however, as the same widget generates the form for adding a comment, and
> >> also generates a list of comments to display, it is not possible to display
> >> existing comments to a user who is not logged.
> >> I suggest dividing into two widgets, one to generate the form of
> >> insertion, and this would be protected. And another to generate a list of
> >> existing comments, and this would free reading. this last could be used in
> >> another place eg: to show recent comments for a page.
>
> >> -* 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
>
> >> *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
>
> >> - *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.
>
> >> - *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
>
> >> - *Categories:*
> >> wiki or any other type of page created with plugin_wiki, IMHO, will need
> >> some kind of category management. it is not difficult to implement as
> >> standard, without having to create custom widgets, as I had to do.
>
> >> - *Search: *
> >> I created a custom widget that performs searches in titles, slugs, and
> >> body of the pages, and it is running on GAE, I believe this should be used
> >> as a widget placed on the meta-header, or meta-sidebar for example. but
> >> could be part of the plugin itself, considering that this is a basic need
> >> of
> >> any wiki page.
>
> >> - *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 [[linktitle
> >>http://linkurl blank]]
>
> >> - *Preview and Saving: *
> >> It is very annoying having to submit the page every time we need to save,
> >> then to have a preview, the saving could happen with AJAX and have option
> >> to
> >> view a Preview window.
>
> >> - *Lists:*
> >> In ordered and unordered lists creates with - and +, Needs a way to
> >> create sublevels with lists, maybe -- and ++
> >> - A Topic
> >> -- Subtopic of A Topic
> >> --- Subtopic of a subtopic of A Topic
> >> -- Another subtopic of A Topic
>
> >> + A Topic
> >> ++ Subtopic of A Topic
> >> +++ Subtopic of a subtopic of A Topic
> >> ++ Another subtopic of A Topic
>
> >> - *Page auto reference:*
> >> It w
[web2py] Re: plugin_wiki suggestions
Concerning Your THISPAGE idea:
I think what You mean can be achieved simply by writing
[[this page #]]
I tried it, works great.
On Aug 1, 6:54 am, Bruno Rocha wrote:
> I am developing and writing a lot with plugin_wiki (cube2py). I already have
> some suggestions, observations and have also found some bugs.
> As I'm finding more issues, I will posting here in this thread. If someone
> else has something to add, enjoy the thread.
>
> I am working now on this page :http://web2pybrasil.appspot.com/cursoweb2py/
>
> *
> *
> *Bugs I Found:*
>
> -* **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.
> however, as the same widget generates the form for adding a comment, and
> also generates a list of comments to display, it is not possible to display
> existing comments to a user who is not logged.
> I suggest dividing into two widgets, one to generate the form of insertion,
> and this would be protected. And another to generate a list of existing
> comments, and this would free reading. this last could be used in another
> place eg: to show recent comments for a page.
>
> -* 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
>
> *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
>
> - *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.
>
> - *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
>
> - *Categories:*
> wiki or any other type of page created with plugin_wiki, IMHO, will need
> some kind of category management. it is not difficult to implement as
> standard, without having to create custom widgets, as I had to do.
>
> - *Search: *
> I created a custom widget that performs searches in titles, slugs, and body
> of the pages, and it is running on GAE, I believe this should be used as a
> widget placed on the meta-header, or meta-sidebar for example. but could be
> part of the plugin itself, considering that this is a basic need of any wiki
> page.
>
> - *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]]
>
> - *Preview and Saving: *
> It is very annoying having to submit the page every time we need to save,
> then to have a preview, the saving could happen with AJAX and have option to
> view a Preview window.
>
> - *Lists:*
> In ordered and unordered lists creates with - and +, Needs a way to create
> sublevels with lists, maybe -- and ++
> - A Topic
> -- Subtopic of A Topic
> --- Subtopic of a subtopic of A Topic
> -- Another subtopic of A Topic
>
> + A Topic
> ++ Subtopic of A Topic
> +++ Subtopic of a subtopic of A Topic
> ++ Another subtopic of A Topic
>
> - *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"
>
> - *Wiki Pages management: *
> Wiki Pages management "plugin_wiki / index" tends to get a little confusing
> as the number of existing pages grows, it would be interesting to have
> pagination, search, categorization.
>
> - *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.
>
> By Now , that's it. As Im using I will send more thoughts about it.
> I am available for any help or tests you need.
>
> {{=thanks}}
>
> ---
> rochacbruno.com.br
> @rochacbruno
>
> 2010/8/1 mdipierro
>
> > Fornow you can post here.Please send your comments asap because I am
> > about to revise it and write a book chapter about it.
>
> > On 1 Ago, 04:55, Bruno Roch
[web2py] Re: plugin_wiki suggestions
Most of your bug reports/suggestions will be accommodated shortly.
Please continue. ;-)
On Aug 1, 2:03 am, Bruno Rocha wrote:
> One more suggestion for today.
>
> It will be great to create new pages from "template", as creating a template
> page with standard texts, widgets and other stuff, we have any way to
> duplicate that page.
>
> actually just creating a way to duplicate certain page will do that work.
>
> {{=thanks}}
>
> 2010/8/1 Bruno Rocha
>
>
>
> > But the ".code" thing, is usefull for editors, so there is a way to ".code"
> > output be available only to logged in editor users?
>
> > its usefull to check the code as in
> >http://web2pybrasil.appspot.com/cursoweb2py/plugin_wiki/page.code/met...
>
> > 2010/8/1 Bruno Rocha
>
> >> I Just found one more thing:
>
> >> take this page by example:
>
> >>http://web2pybrasil.appspot.com/cursoweb2py/plugin_wiki/page/curso-we...
>
> >> now add a ".code" to he action
>
> >>http://web2pybrasil.appspot.com/cursoweb2py/plugin_wiki/page.code/cur...
>
> >> even logged out, you can see the code behind the page, as we pass
> >> parameters to custom widgets, I think this could not happens.
>
> >> but, it is usefull to still have page.load, page.xml, page.json, and
> >> page.rss functions.
>
> >> 2010/8/1 Bruno Rocha
>
> >> I am developing and writing a lot with plugin_wiki (cube2py). I already
> >>> have some suggestions, observations and have also found some bugs.
> >>> As I'm finding more issues, I will posting here in this thread. If
> >>> someone else has something to add, enjoy the thread.
>
> >>> I am working now on this page :
> >>>http://web2pybrasil.appspot.com/cursoweb2py/
>
> >>> *
> >>> *
> >>> *Bugs I Found:*
>
> >>> -* **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.
> >>> however, as the same widget generates the form for adding a comment, and
> >>> also generates a list of comments to display, it is not possible to
> >>> display
> >>> existing comments to a user who is not logged.
> >>> I suggest dividing into two widgets, one to generate the form of
> >>> insertion, and this would be protected. And another to generate a list
> >>> of existing comments, and this would free reading. this last could be used
> >>> in another place eg: to show recent comments for a page.
>
> >>> -* 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
>
> >>> *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
>
> >>> - *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.
>
> >>> - *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
>
> >>> - *Categories:*
> >>> wiki or any other type of page created with plugin_wiki, IMHO, will need
> >>> some kind of category management. it is not difficult to implement as
> >>> standard, without having to create custom widgets, as I had to do.
>
> >>> - *Search: *
> >>> I created a custom widget that performs searches in titles, slugs, and
> >>> body of the pages, and it is running on GAE, I believe this should be
> >>> used
> >>> as a widget placed on the meta-header, or meta-sidebar for example. but
> >>> could be part of the plugin itself, considering that this is a basic need
> >>> of
> >>> any wiki page.
>
> >>> - *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 [[linktitle
> >>>http://linkurl blank]]
>
> >>> - *Preview and Saving: *
> >>> It is very annoying having to submit the page every time we need to
> >>> save, then to have a preview, the saving could happen with AJAX and have
> >>> option to view a Preview window.
>
> >>> - *Lists:*
> >>> In ordered and unordered lists creates with - and +, Needs a way to
> >>> create sublevels with lists, maybe -- and ++
> >>
Re: [web2py] Re: plugin_wiki suggestions
One more suggestion for today.
It will be great to create new pages from "template", as creating a template
page with standard texts, widgets and other stuff, we have any way to
duplicate that page.
actually just creating a way to duplicate certain page will do that work.
{{=thanks}}
2010/8/1 Bruno Rocha
> But the ".code" thing, is usefull for editors, so there is a way to ".code"
> output be available only to logged in editor users?
>
> its usefull to check the code as in
> http://web2pybrasil.appspot.com/cursoweb2py/plugin_wiki/page.code/meta-code
>
>
> 2010/8/1 Bruno Rocha
>
>> I Just found one more thing:
>>
>> take this page by example:
>>
>> http://web2pybrasil.appspot.com/cursoweb2py/plugin_wiki/page/curso-web2py-002
>>
>> now add a ".code" to he action
>>
>>
>> http://web2pybrasil.appspot.com/cursoweb2py/plugin_wiki/page.code/curso-web2py-002
>>
>> even logged out, you can see the code behind the page, as we pass
>> parameters to custom widgets, I think this could not happens.
>>
>> but, it is usefull to still have page.load, page.xml, page.json, and
>> page.rss functions.
>>
>>
>> 2010/8/1 Bruno Rocha
>>
>> I am developing and writing a lot with plugin_wiki (cube2py). I already
>>> have some suggestions, observations and have also found some bugs.
>>> As I'm finding more issues, I will posting here in this thread. If
>>> someone else has something to add, enjoy the thread.
>>>
>>> I am working now on this page :
>>> http://web2pybrasil.appspot.com/cursoweb2py/
>>>
>>> *
>>> *
>>> *Bugs I Found:*
>>>
>>> -* **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.
>>> however, as the same widget generates the form for adding a comment, and
>>> also generates a list of comments to display, it is not possible to display
>>> existing comments to a user who is not logged.
>>> I suggest dividing into two widgets, one to generate the form of
>>> insertion, and this would be protected. And another to generate a list
>>> of existing comments, and this would free reading. this last could be used
>>> in another place eg: to show recent comments for a page.
>>>
>>> -* 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
>>>
>>>
>>> *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
>>>
>>> - *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.
>>>
>>> - *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
>>>
>>> - *Categories:*
>>> wiki or any other type of page created with plugin_wiki, IMHO, will need
>>> some kind of category management. it is not difficult to implement as
>>> standard, without having to create custom widgets, as I had to do.
>>>
>>> - *Search: *
>>> I created a custom widget that performs searches in titles, slugs, and
>>> body of the pages, and it is running on GAE, I believe this should be used
>>> as a widget placed on the meta-header, or meta-sidebar for example. but
>>> could be part of the plugin itself, considering that this is a basic need of
>>> any wiki page.
>>>
>>> - *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 [[linktitle
>>> http://linkurl blank]]
>>>
>>> - *Preview and Saving: *
>>> It is very annoying having to submit the page every time we need to
>>> save, then to have a preview, the saving could happen with AJAX and have
>>> option to view a Preview window.
>>>
>>> - *Lists:*
>>> In ordered and unordered lists creates with - and +, Needs a way to
>>> create sublevels with lists, maybe -- and ++
>>> - A Topic
>>> -- Subtopic of A Topic
>>> --- Subtopic of a subtopic of A Topic
>>> -- Another subtopic of A Topic
>>>
>>> + A Topic
>>> ++ Subtopic of A Topic
>>> +++ Subtopic of a subtopic of A Topic
>>> ++ Another subtopic of A Topic
>>>
>>> - *Page auto reference:*
>>> It would be
Re: [web2py] Re: plugin_wiki suggestions
But the ".code" thing, is usefull for editors, so there is a way to ".code"
output be available only to logged in editor users?
its usefull to check the code as in
http://web2pybrasil.appspot.com/cursoweb2py/plugin_wiki/page.code/meta-code
2010/8/1 Bruno Rocha
> I Just found one more thing:
>
> take this page by example:
>
> http://web2pybrasil.appspot.com/cursoweb2py/plugin_wiki/page/curso-web2py-002
>
> now add a ".code" to he action
>
>
> http://web2pybrasil.appspot.com/cursoweb2py/plugin_wiki/page.code/curso-web2py-002
>
> even logged out, you can see the code behind the page, as we pass
> parameters to custom widgets, I think this could not happens.
>
> but, it is usefull to still have page.load, page.xml, page.json, and
> page.rss functions.
>
>
> 2010/8/1 Bruno Rocha
>
> I am developing and writing a lot with plugin_wiki (cube2py). I already
>> have some suggestions, observations and have also found some bugs.
>> As I'm finding more issues, I will posting here in this thread. If
>> someone else has something to add, enjoy the thread.
>>
>> I am working now on this page :
>> http://web2pybrasil.appspot.com/cursoweb2py/
>>
>> *
>> *
>> *Bugs I Found:*
>>
>> -* **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.
>> however, as the same widget generates the form for adding a comment, and
>> also generates a list of comments to display, it is not possible to display
>> existing comments to a user who is not logged.
>> I suggest dividing into two widgets, one to generate the form of
>> insertion, and this would be protected. And another to generate a list of
>> existing comments, and this would free reading. this last could be used in
>> another place eg: to show recent comments for a page.
>>
>> -* 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
>>
>>
>> *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
>>
>> - *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.
>>
>> - *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
>>
>> - *Categories:*
>> wiki or any other type of page created with plugin_wiki, IMHO, will need
>> some kind of category management. it is not difficult to implement as
>> standard, without having to create custom widgets, as I had to do.
>>
>> - *Search: *
>> I created a custom widget that performs searches in titles, slugs, and
>> body of the pages, and it is running on GAE, I believe this should be used
>> as a widget placed on the meta-header, or meta-sidebar for example. but
>> could be part of the plugin itself, considering that this is a basic need of
>> any wiki page.
>>
>> - *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 [[linktitle
>> http://linkurl blank]]
>>
>> - *Preview and Saving: *
>> It is very annoying having to submit the page every time we need to save,
>> then to have a preview, the saving could happen with AJAX and have option to
>> view a Preview window.
>>
>> - *Lists:*
>> In ordered and unordered lists creates with - and +, Needs a way to
>> create sublevels with lists, maybe -- and ++
>> - A Topic
>> -- Subtopic of A Topic
>> --- Subtopic of a subtopic of A Topic
>> -- Another subtopic of A Topic
>>
>> + A Topic
>> ++ Subtopic of A Topic
>> +++ Subtopic of a subtopic of A Topic
>> ++ Another subtopic of A Topic
>>
>> - *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"
>>
>> - *Wiki Pages management: *
>> Wiki Pages management "plugin_wiki / index" tends to get a little
>> confusing as the number of existing pages grows, it would be interesting to
>> have pagination
Re: [web2py] Re: plugin_wiki suggestions
I Just found one more thing:
take this page by example:
http://web2pybrasil.appspot.com/cursoweb2py/plugin_wiki/page/curso-web2py-002
now add a ".code" to he action
http://web2pybrasil.appspot.com/cursoweb2py/plugin_wiki/page.code/curso-web2py-002
even logged out, you can see the code behind the page, as we pass parameters
to custom widgets, I think this could not happens.
but, it is usefull to still have page.load, page.xml, page.json, and
page.rss functions.
2010/8/1 Bruno Rocha
> I am developing and writing a lot with plugin_wiki (cube2py). I already
> have some suggestions, observations and have also found some bugs.
> As I'm finding more issues, I will posting here in this thread. If someone
> else has something to add, enjoy the thread.
>
> I am working now on this page :
> http://web2pybrasil.appspot.com/cursoweb2py/
>
> *
> *
> *Bugs I Found:*
>
> -* **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.
> however, as the same widget generates the form for adding a comment, and
> also generates a list of comments to display, it is not possible to display
> existing comments to a user who is not logged.
> I suggest dividing into two widgets, one to generate the form of insertion,
> and this would be protected. And another to generate a list of existing
> comments, and this would free reading. this last could be used in another
> place eg: to show recent comments for a page.
>
> -* 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
>
>
> *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
>
> - *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.
>
> - *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
>
> - *Categories:*
> wiki or any other type of page created with plugin_wiki, IMHO, will need
> some kind of category management. it is not difficult to implement as
> standard, without having to create custom widgets, as I had to do.
>
> - *Search: *
> I created a custom widget that performs searches in titles, slugs, and body
> of the pages, and it is running on GAE, I believe this should be used as a
> widget placed on the meta-header, or meta-sidebar for example. but could
> be part of the plugin itself, considering that this is a basic need of any
> wiki page.
>
> - *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 [[linktitle
> http://linkurl blank]]
>
> - *Preview and Saving: *
> It is very annoying having to submit the page every time we need to save,
> then to have a preview, the saving could happen with AJAX and have option to
> view a Preview window.
>
> - *Lists:*
> In ordered and unordered lists creates with - and +, Needs a way to create
> sublevels with lists, maybe -- and ++
> - A Topic
> -- Subtopic of A Topic
> --- Subtopic of a subtopic of A Topic
> -- Another subtopic of A Topic
>
> + A Topic
> ++ Subtopic of A Topic
> +++ Subtopic of a subtopic of A Topic
> ++ Another subtopic of A Topic
>
> - *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"
>
> - *Wiki Pages management: *
> Wiki Pages management "plugin_wiki / index" tends to get a little confusing
> as the number of existing pages grows, it would be interesting to have
> pagination, search, categorization.
>
> - *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.
>
> By Now , that's it. As Im using I
Re: [web2py] Re: plugin_wiki suggestions
I am developing and writing a lot with plugin_wiki (cube2py). I already have
some suggestions, observations and have also found some bugs.
As I'm finding more issues, I will posting here in this thread. If someone
else has something to add, enjoy the thread.
I am working now on this page : http://web2pybrasil.appspot.com/cursoweb2py/
*
*
*Bugs I Found:*
-* **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.
however, as the same widget generates the form for adding a comment, and
also generates a list of comments to display, it is not possible to display
existing comments to a user who is not logged.
I suggest dividing into two widgets, one to generate the form of insertion,
and this would be protected. And another to generate a list of existing
comments, and this would free reading. this last could be used in another
place eg: to show recent comments for a page.
-* 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
*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
- *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.
- *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
- *Categories:*
wiki or any other type of page created with plugin_wiki, IMHO, will need
some kind of category management. it is not difficult to implement as
standard, without having to create custom widgets, as I had to do.
- *Search: *
I created a custom widget that performs searches in titles, slugs, and body
of the pages, and it is running on GAE, I believe this should be used as a
widget placed on the meta-header, or meta-sidebar for example. but could be
part of the plugin itself, considering that this is a basic need of any wiki
page.
- *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 [[linktitle
http://linkurl blank]]
- *Preview and Saving: *
It is very annoying having to submit the page every time we need to save,
then to have a preview, the saving could happen with AJAX and have option to
view a Preview window.
- *Lists:*
In ordered and unordered lists creates with - and +, Needs a way to create
sublevels with lists, maybe -- and ++
- A Topic
-- Subtopic of A Topic
--- Subtopic of a subtopic of A Topic
-- Another subtopic of A Topic
+ A Topic
++ Subtopic of A Topic
+++ Subtopic of a subtopic of A Topic
++ Another subtopic of A Topic
- *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"
- *Wiki Pages management: *
Wiki Pages management "plugin_wiki / index" tends to get a little confusing
as the number of existing pages grows, it would be interesting to have
pagination, search, categorization.
- *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.
By Now , that's it. As Im using I will send more thoughts about it.
I am available for any help or tests you need.
{{=thanks}}
---
rochacbruno.com.br
@rochacbruno
2010/8/1 mdipierro
> Fornow you can post here.Please send your comments asap because I am
> about to revise it and write a book chapter about it.
>
> On 1 Ago, 04:55, Bruno Rocha wrote:
> > Sorry again, I am creating a new thread about plugin_wiki.
> >
> > I wonder if there is any public place where we can write suggestions,
> > criticisms, and send questions exclusively about plugin_wiki, markmin and
> > cube2py?
> >
> > --
> >
> > http://rochacbruno.com.br
>
--
http://rochacbruno.com.br
[web2py] Re: plugin_wiki suggestions
Fornow you can post here.Please send your comments asap because I am about to revise it and write a book chapter about it. On 1 Ago, 04:55, Bruno Rocha wrote: > Sorry again, I am creating a new thread about plugin_wiki. > > I wonder if there is any public place where we can write suggestions, > criticisms, and send questions exclusively about plugin_wiki, markmin and > cube2py? > > -- > > http://rochacbruno.com.br
[web2py] Re: plugin_wiki suggestions
Not yet. You can post here for now. Not sure it needs a new place. If you have comments please send them asap since I am about to make some changes and write a book chapter about it tomorrow. On 1 Ago, 04:55, Bruno Rocha wrote: > Sorry again, I am creating a new thread about plugin_wiki. > > I wonder if there is any public place where we can write suggestions, > criticisms, and send questions exclusively about plugin_wiki, markmin and > cube2py? > > -- > > http://rochacbruno.com.br
