Just a quick thought.
1. Each plugin's owner can store the source code in code.google.com
2. Too bad that code.google.com can not provide a live show about the
plugin's look-and-feel, so we can setup a plugins' "sandbox" on
web2py.com, nightly checkout plugins' source code, then user can visit
a l
We really need a better way to post plugins and keep track of features/
versions than web2py.com/plugins.
On 14 Lug, 18:03, Thadeus Burgess wrote:
> I have this code implemented in plugin_category.py let me just find it
> =/
>
> Ah yes, here it is
>
> http://code.google.com/p/blogitizor/sourc
I have this code implemented in plugin_category.py let me just find it
=/
Ah yes, here it is
http://code.google.com/p/blogitizor/source/browse/src/modules/plugin_category.py
You can see example usage in blogitizor.
--
Thadeus
On Tue, Jul 13, 2010 at 4:19 PM, sociotech wrote:
> You mig
You might want to check out Massimo's code for Modified Preorder Tree
Traversal, which is an extremely efficient way of storing tree
structures in a database:
http://groups.google.com/group/web2py/browse_thread/thread/70efddab62dfe73
On Jul 13, 11:59 am, "topher.baron" wrote:
> I'm looking forwa
I'm looking forward to it.
On Jul 13, 1:12 pm, Vasile Ermicioi wrote:
> I am developing a solution for my needs, something similar to nested sets,
> if you could wait a few days I think I will be able to share it
5 matches
Mail list logo