Dear Richard and Niphlod,

Thanks for your responses. Richard, your understanding is the indeed 
meaning of what i was trying to express.

Regarding my suggestions for improving web2py support for web-devs, i have 
2 suggestions i can think of right now:

   - When writing a Plugin or a Wizard or some add-on for web2py ask 
   yourself the question, "Is my intended user a Web Developer or Admin?".
   - Possibly set up a tag to categorize existing add-ons one way or the 
   other (or both?).   
   
I will try to think of more suggestions as they come to me.

Thanks again.

Love and peace,

Joe
On Thursday, January 29, 2015 at 1:07:30 PM UTC-8, Richard wrote:
>
> I am not sure where it is going... My understanding, is that Joe explain 
> what he means by admin and devs (that I did already understand in the first 
> place, but he make it clear)... And what I understand, is that he think 
> that web2py help more admins in their day to day work then developers...
>
> If my reading is rights, he wure has suggestion to improve web2py for 
> devs...
>
> Richard
>
> On Thu, Jan 29, 2015 at 3:54 PM, Niphlod <nip...@gmail.com <javascript:>> 
> wrote:
>
>> In that POV, you'll always identify an "administrator" as a person who 
>> "clicks" on existing apps he didn't code and a "developer" of apps someone 
>> that "clicks" on fruits of his mind. That's basically comparing oranges and 
>> bananas....wordpress is hardly a framework. It's an application that does 
>> one job well. 
>> The fact that php+mysql was the defacto standard for web hosters (and the 
>> relative lack of "easy blogging" environments) made the spread of wordpress 
>> "hacks" and ecosystem rather large, but making wordpress do "whatever" is 
>> pretty limited to installing something relatively uncoupled (except for 
>> authentication and the common "webpage style"). Moreover, if you don't know 
>> the first thing about php, any - little or big - customization you want 
>> means trusting someone else that did it. 
>>
>> web2py will hardly replace any known application that already does a job 
>> well. It's not a job for a framework but for an app. 
>> No company will adopt web2py as a file sharing platform if a sharepoint 
>> farm is already in place, and I won't ever recommend the builtin web2py 
>> wiki over mediawiki for a CMS with 10k pages.
>>
>> If you're fine with it, by all means, be an "administrator". But when 
>> you'll need something that no existing thing does (or you can't afford it), 
>> be a developer.
>>
>> -- 
>> Resources:
>> - http://web2py.com
>> - http://web2py.com/book (Documentation)
>> - http://github.com/web2py/web2py (Source code)
>> - https://code.google.com/p/web2py/issues/list (Report Issues)
>> --- 
>> You received this message because you are subscribed to the Google Groups 
>> "web2py-users" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to web2py+un...@googlegroups.com <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
>

-- 
Resources:
- http://web2py.com
- http://web2py.com/book (Documentation)
- http://github.com/web2py/web2py (Source code)
- https://code.google.com/p/web2py/issues/list (Report Issues)
--- 
You received this message because you are subscribed to the Google Groups 
"web2py-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to web2py+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to