Re: [FCKeditor-Developers] Distribution files "specialization"

[Frederico C. K. <fr...@fc...>]

> -----Original Message-----
> From: Alexander Kandzior
> Sent: 30 March 2007 11:31

> Server side technology is not not really a language based thing. Server
> side
> technology e.g. in Java can differ greatly, depending on which Framework
> you
> use. There are just too many possible server side systems to have a "drop
> in" solution that works for everyone. We could have 10 FCKeditor packages
> for Java based servers alone.

You are right... but, wouldn't it be good to have the current two separated
distribution files (for Java usage, I mean) merged in a single file for
distribution? A kind of generic Java distribution, to be then adapted to
each framework you will be installing it.


> A default server side integration should not be the goal in a language
> package. Instead the goal should be some well defined API that allows
> integrating the server side part of FCKeditor with whatever server side
> repository you use in your technology.

The default integration is certainly needed for the average user. The idea
of a standard integration API is wonderful too. Let's thought about it too.


FredCK 
 
 

> -----Original Message-----
> From: fck...@li...
> [mailto:fck...@li...] On Behalf Of
> Alexander Kandzior
> Sent: 30 March 2007 11:31
> To: 'FCKeditor Developer's List'
> Subject: Re: [FCKeditor-Developers] Distribution files "specialization"
> 
> > So, I think that we should have separate preconfigured
> > drop-in zip file.
> > But I think we should name them in a way that makes it clear
> > that they are
> > just preconfigured installation of FCKEditor for a specific server
> > technology, not a different product.
> >
> > And with different files we can start building some more
> > specific for the
> > application server we are targeting:
> > For example with ASP.NET we could make just one drop-in dll
> > that includes
> > all he files (html, js and images in a resource file) or
> > something similar
> > also for java.
> 
> Server side technology is not not really a language based thing. Server
> side
> technology e.g. in Java can differ greatly, depending on which Framework
> you
> use. There are just too many possible server side systems to have a "drop
> in" solution that works for everyone. We could have 10 FCKeditor packages
> for Java based servers alone.
> 
> If e.g. you are using some sort of a Database to store your files managed
> by
> FCKeditor (as probably most CMS systems do), then a default implementation
> that uses the file system is fee of value for you.
> 
> A default server side integration should not be the goal in a language
> package. Instead the goal should be some well defined API that allows
> integrating the server side part of FCKeditor with whatever server side
> repository you use in your technology.
> 
> Best,
> 
> Alexander Kandzior
> 
> -------------------
> 
> Alkacon Software GmbH - The OpenCms Experts
> Alexander Kandzior
> An der Wachsfabrik 13
> 50996 Koeln, DE
> 
> Tel: +49 (0)2236 3826-0
> Fax: +49 (0)2236 3826-20
> Email: a.k...@al...
> 
> http://www.alkacon.com
> http://www.opencms.org
> 
> 
> -------------------------------------------------------------------------
> Take Surveys. Earn Cash. Influence the Future of IT
> Join SourceForge.net's Techsay panel and you'll get the chance to share
> your
> opinions on IT & business topics through brief surveys-and earn cash
> http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
> _______________________________________________
> FCKeditor-Developers mailing list
> FCK...@li...
> https://lists.sourceforge.net/lists/listinfo/fckeditor-developers