You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@lenya.apache.org by "Scherler, Thorsten" <th...@apache.org> on 2004/07/23 18:33:43 UTC

External tools and roles

Hello devs,

 >>>>>...I may have some time in august where I learn python in a training.
 >>>>>I have an idea to programm a python gui for lenya administration, but
 >>>>>that is not more then an idea so far!
 >
 >
 >>>Cool! (that's what I meant with "external tools")
 >
 >
 > I sense some contradiction here! Lenya means Usecases, CMS screens 
and the
 > like to me. How might that be in line with having a lot of unrelated
 > external tools that will most likely for example make assumptions about
 > filenames and schema that Lenya uses?
 >
 > I am currently having a look at Haskell. (This is another programming
 > language.) Should I go ahead and implement some Lenya tools in Haskell?
 >
 > If external tools means that there will be a plug-in concept for CMS
 > screens, that would make sense not only to be but most likely also to the
 > *users* who want *one* somewhat *seamless* interface to get their work
 > done. Web designer type of people don't like unixy command line tools. We
 > might, they don't. But these plugins should still be written using the
 > same technology than the rest of Lenya.
 >

Whoops, I think you misunderstood me there. I just said I want to create 
an external tool for my *personal* pratice! I never stated that should 
be an example or anything similar.

To further clearify in what I am planing to do let me tell something 
about python. You can use it as command line like you stated but the 
most likely use case to make operating system independent GUIs. IMO GUIs 
are for webdesigner! I would pick up the filesystem (for now) of lenya 
and *not* assume it. I just said for now because with 1.4 that will 
change. Lenya support then abstract layer! On this layer (filesystem 
independent) you can build any tool for lenya! I saw python interfaces 
apear in some other apache projects that is the main reason why I was 
thinking about to create one *as personal practice*!

I disagree that interfaces for lenya have to be written in the same 
language then the rest for user reason! IMO the user of lenya should not 
be bothered in which language lenya and their components are written! 
They are worried about which button to press to archieve a certain 
action! I could write a flashy Java Swing GUI if I want to keep your 
demand to stay in the same technology like the rest but I do not 
understand why I should!

 > No problem with the fact that there is a roadmap and the developer
 > community should stick to it. And I agree that industrial strength is 
very
 > imporant and maybe even more important than a low entry barrier.
 >

Yes, but a low entry barrier for me is that I do not have to use a 
filesystem! I got use to have dbs. I would love to drop the filesystem 
by tomorrow but we will have to wait for 1.4.

 > But currently the entry barrier to Lenya is somewhat prohibitive in my
 > view which is why I guess a lot of people that might become fans of Lenya
 > rather go for Zope

Ok, I have to disagree if you want to get started with developing Zope 
then you have to learn even more concepts then in lenya and I am 
speaking from personal experience!

 > and the like or for PHP / MySQL based approaches

That you are right but I do not have seen *any* php based CMS that have 
the same focus like lenya! Again I analysed some of the most famous ones!

 > because it currently takes a Java / XML / Cocoon Guru to introduce Lenya
 > into a project.
 > And it takes a person with the same skillset to support
 > editors that use Lenya. (I speak from experience and I would like to try
 > to solve this; partly because I made a promise to my user community.)
 >

Yeah, I reckon to develope with lenya you have to know the technologies 
you mentioned. When I get started with Wyona CMS (the former CMS lenya 
is based on) I did not had a clue about any of the mentioned 
technologies. I started to learn cocoon (xml) and then Java!

...and saying this you have a perfect point. IMO you are committed to 
*your* community and I see that you have started to be as well for the 
*lenya* one :). Your work help to see what we have to change in the 
future but sometimes we can change it in a day! We need help! Keep it up 
and become a committer to lenya!

I as well feel strongly committed to make it for editors as easy as 
possible but speaking of editors leads me to the role concept of lenya. 
Trying to write a better documentation I see 5 roles in the use of 
lenya. The next statement is from Andrew (he sees 4 roles):
"I see that there is the IMPLEMENTOR (the person who will INSTALL 
Lenya), the ADMIN (who will RUN it), CONTRIBUTORS (who will submit 
items, maintain areas, etc), and USERS (site visitors)"

IMO we have two main groups devs and user.
devs:
- IMPLEMENTOR
- ADMIN
- webdesigner

user:
- CONTRIBUTORS (editors)
- USER

I see the designer in the dev class that may change when we can apply 
standard contracts for designers.

King regards
thorsten
-- 
<thorsten>
  <name>Thorsten Scherler</name>
  <country>Spain</country>
  <@m...@mail>
  <@cocoon-WIKI>
http://wiki.apache.org/cocoon/Scherler
</...@cocoon-WIKI>
  <acronymfinder>
http://www.acronymfinder.com/af-query.asp?String=exact&Find=Find&Acronym=
  </acronymfinder>
  <motto>
    "My task which I am trying to achieve is,
     by the power of the written word,
     [...] to make you see."
     *Joseph Conrad (1857-1924)*
  </motto>
</thorsten>



---------------------------------------------------------------------
To unsubscribe, e-mail: lenya-dev-unsubscribe@cocoon.apache.org
For additional commands, e-mail: lenya-dev-help@cocoon.apache.org