It's trully possible.
Hello Carl,
> has anyone direct experience of using Wordpress, SquareSpace or
> similar solution alongside Web2py?
>
> These solutions appeal for their maturity and I'd like to use one to
> do the "donkey" work and fall back to Web2py to do my site's specific
> functionality.
I also wondering about the possibility to use WordPress alongwith Web2Py...
Let me say that, if possible, I'd like to stay solely in the Web2py arena, but
I do not see mature CMS with decent support...
KpaxCMS does not look alive and Instant Press seems to be cared only by Martin
M. which is either busy with other stuff or not sufficiently interested to push
it on. (I've submitted bug report about IP not styling bullets and, so far,
nothing happened.)
This situation makes me reluctant to embrace IP as web2py-based CMS/blog on
which to further build additional add-ons/plugins.
Otoh, I'm not enthusiastic to re-invent the whole CMS...
Maybe having CMS/blog is not most important need for most of web2py users, but
here it's real need for it.
Have you investigate more about using WordPress & Web2py or found some other
interesting solution?
Sincerely,
Gour
--
When your intelligence has passed out of the dense forest
of delusion, you shall become indifferent to all that has
been heard and all that is to be heard.
http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810
I've been in the same situation - I use Plone as a CMS (a 300lb gorilla
beside web2py, and overly complex to develop against at my scale), and
use web2py behind it for RDBMS tasks.
What sort of CMS functionality do you need OOTB, and what sort of
functionality do you envisage developing?
--
Regards,
PhilK
'a bell is a cup...until it is struck'
Due to the fact of web2py's Single step deployment , many
not-so-technical users will want to adopt it . If theres a stable ,
active CMS , developed using Web2py , it will change the future of
both python and web2py in web development.
PHP Based solutions are very hard for normal to Super user for setup /
installation / deployment. For web2py we can do just one click
install.
> Due to the fact of web2py's Single step deployment , many
> not-so-technical users will want to adopt it . If theres a stable ,
> active CMS , developed using Web2py , it will change the future of
> both python and web2py in web development.
I fully agree...before jumping to Web2py I was looking at Zine (
http://zine.pocoo.org/code), but web2py-based blog/CMS could have much greater
impact considering all the known web2py pros...
Sincerely,
Gour
--
One who is not connected with the Supreme can have neither
transcendental intelligence nor a steady mind, without which
there is no possibility of peace. And how can there be any
happiness without peace?
On 04/11/2011 06:06, Phyo Arkar wrote:
> We really need a CMS/Blog that the developer really cares ., It have a
> lot of potential to become top CMS/Blog.
>
I agree, in principle, but we need to define our terms here. If by
CMS/Blog we're referring to something like Wordpress, then that is
realistic. The first step would probably be to define some sort of
spec., as "CMS/Blog" can mean very different things to different people.
However, I think it would be too ambitious to try to replicate something
like Plone - not a blogging tool, and hardly a lightweight CMS either -
so from my PoV there will continue to be a need to mesh Plone and web2py
together.
> I agree, in principle, but we need to define our terms here. If by
> CMS/Blog we're referring to something like Wordpress, then that is
> realistic. The first step would probably be to define some sort of
> spec., as "CMS/Blog" can mean very different things to different
> people.
Having decent support/docs/more_devs/.. for InstantPress would be, imho, good
starting point...
Sincerely,
Gour
--
A person who has given up all desires for sense gratification,
who lives free from desires, who has given up all sense of
proprietorship and is devoid of false ego — he alone can
attain real peace.
Can Instant Press developer define goals and roadmaps so that we know
what to work on and submit patches or allow some of us Developer
access?
Or should we fork it if hes busy to manage this project ?
Regards,
Phyo
Lets start with Main feature of WordPress , A blog , Layout/Theme
management , Posting news , Tagging , comments (Instant-press should
have to features)
Make those features works well stable and robust.
Add more features later.
Any takers?
On 11/4/11, Philip Kilner <phil....@gmail.com> wrote:
On 04/11/2011 12:39, Phyo Arkar wrote:
> Plone itself is a beast of its own, even tho web2py is a lot easier
> than Zope and can create something that beats Plone , alot easier
> than doing it with zope, we should not try to go that way.
>
There are things that Zope & Plone do with acquisition, the ZODB and its
catalog that are hugely powerful. Having said that, the reputation for a
"Z-shaped learning curve" is well deserved.
Again, we need to define our terms - trying to beat Plone in terms of
its enterprise (that word again!) CMS features would be plain daft, and
doomed to failure with the resources available, but trying to beat Plone
in terms of agility and accessibility to developers is a task that
web2py is well positioned for.
> perhaps we should make a list of desired features.
I believe that WordPress is quite etablished as Blog engine and CMS
platform, so making Instant Press as "Python's WordPress" would be
cool, iow, stable blog/CMS + support for easy styling/theming along
with solid framework to write plugins...
I'd be more than satisfied and would try to contribute to make it
happen!
Sincerely,
Gour
--
Massimo Di Pierro
<massimo....@gmail.com> wrote:
i
Dear Massiomo,
> perhaps we should make a list of desired features.
After I put some more thought into it, I've arrived at the conclusion that,
imho, Concrete5 (http://www.concrete5.org/) is, philosophically closer to
web2py than Wordpress, so it would be nice if you can check it out briefly.
Here are some of the C5 features:
- in-context (inline) editing
- easy styling (very easy to convert HTML/CSS/JS design into C5 theme)
- pages are based on theme/template and bunch of blocks (can we call 'em
widgets) which can be freely moved around the pre-defined slots (based on the
theme)
- based on MBC framework using jQuery, DA (ADOdb), Zend...
- advanced permission system
- sensible defaults with the ability for user to override (almost) everything
- lot of add-ons available
So, C5 is primarily CMS and not blog like WP, although there are few blogs
written as add-ons.
Having something like that based on web2py would bring horde of new users
(dunno if web2py devs are ready to embrace 'em) to web2py 'cause there is
simply no such beast available on the planet Earth combining such features
(e.g. easy designing of layout, inline editing, blocks...) with the well-known
advantages of web2py.
However, it might be that such project is more suitable for Web3py...it would
be pity if it should be rewritten.
Sincerely,
Gour
--
In this endeavor there is no loss or diminution,
and a little advancement on this path can protect
one from the most dangerous type of fear.
* Not-so-elegant code, derived from the fact that's php-based
* Structure and data too much mixed up, due to the will to make
everything configurable from the admin panel.
* Excessive setup time. Many times 3rd-part modules (sometimes even
needed to add missing important features to the core) tend to conflict
or miss something -> many times there is need to develop a custom
site-specific module in order to simplify things.
* Lack of enterpriseness in 3rd-part modules: they are not "verified"
that much, and sometimes bad things happen, even with stuff that used to
work and must have continued to do so.
So, I recently started doing some experiments to see "how hard would it
be" to rewrite Drupal web2py-based and with some improvements.
At the moment, I have a simple app that, along with
garbage/experiments/stuff does pretty much this:
* CRUD for different content-types (each content type may be treated in
different ways / define extra fields / ..; some examples may be
"article", "page", "ecommerce product", ...).
* Commenting. It is handled in a component-like way, although I haven't
written a proper component yet, I'm using a similar way to attach
comments + comment form to "entities", that might be not only "content".
* Regions + blocks. In a way similar to what Drupal does, the
layout.html defines some regions (sidebars, footer, before/after
content, before/after page, ...) in which some "blocks" may be placed,
then blocks are shown independently from the controller (and only in the
html views, since they wouldn't make much sense, for example, in a json
or xml representation).
* Configuration stored in INI files (and maybe in database too, I have
to decide that).
* Some rudimental support (I still have to decide what's the best way to
do that) to user-defined (in the configuration) "views": a mix of
database query + templates to create custom visualizations of content.
I'm going to release all the code as soon as I finish adding access
control, so that I can also install a demo site somewhere (shouldn't
take long, it should only be matter of adding a few decorators..).
I think we should also start organizing the development of the CMS
application:
- who's up for development?
- who's up for testing?
- who's up for documentation? (developers should! documentation is
awesome! I already wrote more documentation than code for this CMS!)
- should we setup a project page / wiki / bugtracker / ..? I think that
it would be a good idea to have at least a wiki, for the moment, on
which to write all the ideas / misc brainstorming, in order to discuss
about the important decisions that should be taken before starting the
actual development.
- should we create another mailing-list just for the cms thing, in order
to keep separate the discussions?
- Do you guys use IRC? I see a #web2py channel on freenode but, although
there is always some people in it, I never saw pretty much anybody
speaking in there..
--
Samuele ~redShadow~ Santi
----------------------------------------------------------------
redshadow[at]hackzine.org - redshadowhack[at]gmail.com
Blog: http://hackzine.org
GPG Key signature:
050D 3E9F 6E0B 44CE C008 D1FC 166C 3C7E EB26 4933
----------------------------------------------------------------
/me recommends:
Squadra Informatica - http://www.squadrainformatica.com
----------------------------------------------------------------
- Proud ThinkPad T-Series owner
- Registered Linux-User: #440008
* GENTOO User since 1199142000 (2008-01-01)
* former DEBIAN SID user
----------------------------------------------------------------
"Software is like sex: it's better when it's free!"
-- Linus Torvalds
I can help with:
- testing
- server resources if needed
- setting up bugtracker, wikipage
I think a own mailinglist and a wiki page first. Very soon a bugtracker.
Maybe a web2py based bugtracker.
Kenneth
> Since I would regularly use and CMS/Blog functionality, I would be
> happy to contribute code and test it, as I would probably be using it
> every day. I would also have regular users play with it and
> incorporate their feedback into it to make something that is better
> than WordPress and Drupal combined.
Same here...If we agree to work on such a thing, it means I'll fully focus on
using web2py solely for all my web needs (which I very much prefer over
fiddling with concrete5/wordpress), learn web2py, write add-ons, writing docs,
testing, translating...
Sincerely,
Gour
--
In the material world, one who is unaffected by whatever good
or evil he may obtain, neither praising it nor despising it,
is firmly fixed in perfect knowledge.
> Here is what you are looking for
>
> https://github.com/lucasdavila/web2py-cms
I'm not sure it's good or robust enough for the users needs expressed
here.
Otoh, we hope that Massimo will provide his $.02 when he finishes with
the current tasks...
Sincerely,
Gour
--
But a person free from all attachment and aversion and able
to control his senses through regulative principles of
freedom can obtain the complete mercy of the Lord.
> The CMS (bloog) from Lucas is nice, but it is incomplete, can be used
> as base for a new project.
Better than Instant Press?
If I'd have skills, I'd 'port' Concrete5 to web2ps making the match in
heaven from C5's front-end capabilities (easy theming, templating,
in-context editing, block-based layout) with web2py's 'back-end'
quality.
Sincerely,
Gour
--
A person who is not disturbed by the incessant flow of
desires — that enter like rivers into the ocean, which is
ever being filled but is always still — can alone achieve
peace, and not the man who strives to satisfy such desires.
> As far as a CMS vs a Blog goes, I have always viewed a Blog and
> viewing content in a particular manner. To me a Blog is a subset of a
> CMS. If we have a basic CMS, adding a Blog simply means organizing
> that particular set of data a certain way.
Yes...In Concrete5 which I use atm, blog/news are just add-ons for the
CMS-based frameworl.
> - content blocks? you have have multiple blocks in a view
> - easily reorganize block with drag and drop
Those are the great features in Concrete5. One C5 user nicely described
some of those features in comparison with WP:
"Which brings me to my point... to me the key insight to understanding
Concrete5 is that in addition to designing the front-end (with HTML and
CSS and themes and templates), you are *also* designing the editing
interface. Where Wordpress confines you to basically one huge content
block per page and some widgets on one sidebar, Concrete5 lets you the
designer choose what the confines for the user are as it best makes
sense for your design (one sidebar? two sidebars? no sidebars? 2 content
areas stacked on top of each other? whatever you want!).
There is a whole spectrum of choices you as the designer can make in
terms of setting up the editing interface as best suits your design --
things like how many different page types you set up and where you put
the editable areas into those page types (as Franz describes above),
using Page Defaults and global scrapbooks for content that changes less
frequently and is common across the entire site, hard-coding blocks into
templates where you need their functionality but don't want the user to
be able to change them ever (e.g. the main navigation menu), not to
mention using the sitemap itself as an organizing structure -- e.g.
setting up a "Recent News" section of your site, and every new page
added to that section gets a new excerpt automatically displayed at the
top of the "News Index" list via the "Page List" block. "
So, in short, I believe that Web2Py deserves better CMS than just clone
of WP. ;)
Sincerely,
Gour
--
A person who has given up all desires for sense gratification,
who lives free from desires, who has given up all sense of
proprietorship and is devoid of false ego — he alone can
attain real peace.
http://atmarama.net | Hlapicina (Croatia) | GPG: 52B5C810
I cannot help presenting my developing plugin, which has a concrete5-
like wysiwyg functionality:
http://dev.s-cubism.com/plugin_managed_html/page1/_managed_html_edit
(note: use chrome or FF)
In this page, you can click highlighed blocks and edit their texts,
images, and htmls, and move specified blocks, and also check
corresponding the preview and live page.
These editable blocks are defined in web2py views using functions and
decorators:
https://github.com/sqlabs/sqlabs/blob/master/views/plugin_managed_html/page1.html
Although it's very experimental and plenty remains to be done, the
core logic may be closely related to this discussions.
Give it a try and welcome any feedback.
I've heard that Bruno is rewriting the web2pyslices.com and plugins
will be able to be hosted. Should I host my plugins at the current
plugin site, or wait until the new site open?
> I cannot help presenting my developing plugin, which has a concrete5-
> like wysiwyg functionality:
Wow!
This looks very interesting.
> Although it's very experimental and plenty remains to be done, the
> core logic may be closely related to this discussions.
Now the question is we can come to some consensus about what kind of CMS
platform we want to build for Web2py, or as Massimo wrote: "list of
features".
I know that's it probably hard to make it "one size fits all", but I
still believe that ONE robust CMS which enables to easily convert
HTML/CSS/JS template into native one (theming/skinning), inline editing
using custom content blocks etc. would be much better than having dozen
of half-or-more-baked solutions.
However, for such a thing we need to hear the voice of web2py giants. ;)
Sincerely,
Gour
--
One who restrains his senses, keeping them under full control,
and fixes his consciousness upon Me, is known as a man of
steady intelligence.
> For a site like this, the CMS feature that's needed most is to make it
> dead simple for others to edit text and insert images for upcoming
> concerts and have it come out in fonts and colors that are consistent
> throughout the site and without messing up things that should be
> centralized in the db (e.g. concert dates, ticket prices, soloist
> bios, etc.)
Have you tried Concrete5 (http://www.concrete5.org/) until we make
web2py-based one...
Sincerely,
Gour
--
When your intelligence has passed out of the dense forest
of delusion, you shall become indifferent to all that has
been heard and all that is to be heard.
> Thanks, Gour. It's a nice looking framework and seems to be well-
> designed.
Yup, it's quite nice.
> I look forward to the web2py version!
Let's see if it will happen...otherwise (without decent CMS) we'd have
to tinker wiht PHP. :-/
Sincerely,
Gour
--
From anger, complete delusion arises, and from delusion
bewilderment of memory. When memory is bewildered,
intelligence is lost, and when intelligence is lost
one falls down again into the material pool.
> this will be the top priority after web2py 2.0 is released and the
> book 4th edition. By the end of November.
you've made my day, Massimo!!
That's great to hear.
I must confess that when I started to tinker with Django and heard that
answer to "Any CMS in Django" question is "Write one..." it wasn't so
exciting considering it's not that everyone has time/skills to do it.
Hearing that web2py is going to work on one, makes me really
enthusiastic to help in any way we can.
Sincerely,
Gour
--
As the embodied soul continuously passes, in this body,
from boyhood to youth to old age, the soul similarly passes
into another body at death. A sober person is not bewildered
by such a change.
I do not know how to reconcile wysiwyg inline editor+drag-drop with
custom layouts. I am leaning for a single html layout similar to the
new web2py welcome app (skeleton) and arbitrary customization using
css only. This opens lots of possibilities but the CMS could not use
existing themes. Converting concrete5 or wordpress themes would be a
pain anyway.
Any ideas? Suggestions?
Any ideas? Suggestions?
> This opens lots of possibilities but the CMS could not use existing
> themes. Converting concrete5 or wordpress themes would be a pain
> anyway.
That's not the problem. What I like in concrete5 is the *ease* of
converting HTML/CSS/JS into the Concrete5 one.
If something similar is available for web2py - then it would be great.
Sincerely,
Gour
--
Never was there a time when I did not exist,
nor you, nor all these kings; nor in the future
shall any of us cease to be.
Glad to know someone is using my plugin :)
On Dec 9, 3:15 pm, Bruno Rocha <rochacbr...@gmail.com> wrote:
What's the plugin? can you send me a link?
On Dec 9, 3:15 pm, Bruno Rocha <rocha...@gmail.com> wrote:
What's the plugin? can you send me a link?
Peter
On Dec 10, 4:55 am, Bruno Rocha <rochacbr...@gmail.com> wrote:
> On Sat, Dec 10, 2011 at 12:32 AM, Massimo Di Pierro <
>
> massimo.dipie...@gmail.com> wrote:
> > What's the plugin? can you send me a link?
>
> Yes, thats the link
>
> https://bitbucket.org/PhreeStyle/web2py_ckeditor/src
>
> I made some changes, my code is here:
>
> https://github.com/rochacbruno/Movuca/blob/master/modules/plugin_cked...