greywire
Posts: 37
|
| Posted: 04/10/2008, 11:03 AM |
|
I've been trying to use CCS4 with a new project but have a couple issues.
First of all, is CCS's requirement to put all its support files into the root of the website (common.php, mysql.php, etc). There is no way to, say, put them all into a folder ("ccslibraries" or something). Not to mention things like functions.js -- why is that not in the js folder? I suppose this isn't really a serious issue, but its really ugly.. Just adding a setting in Server/Script for "common files folder" would do it.
The other problem is that we want our application to have modules, where other people can easily add new modules and these modules can be packaged and installed separately. Codecharge makes it tricky to even put pages into folders, much less make modularity possible.
Unfortunately we will probably be switching to a completely open source framework that doesn't have an IDE but that does have no limiting factors..
_________________
--
Aric Caley
Fonality, inc |
 |
|
DonB
|
| Posted: 04/10/2008, 12:37 PM |
|
I've never seen any software of any kind that had no limiting factors.
--
DonB
"greywire" <greywire@forum.codecharge> wrote in message
news:547fe56853f0ad@news.codecharge.com...
> I've been trying to use CCS4 with a new project but have a couple issues.
>
> First of all, is CCS's requirement to put all its support files into the
> root
> of the website (common.php, mysql.php, etc). There is no way to, say, put
> them
> all into a folder ("ccslibraries" or something). Not to mention things
> like
> functions.js -- why is that not in the js folder? I suppose this isn't
> really a
> serious issue, but its really ugly.. Just adding a setting in
> Server/Script for
> "common files folder" would do it.
>
> The other problem is that we want our application to have modules, where
> other
> people can easily add new modules and these modules can be packaged and
> installed separately. Codecharge makes it tricky to even put pages into
> folders, much less make modularity possible.
>
> Unfortunately we will probably be switching to a completely open source
> framework that doesn't have an IDE but that does have no limiting
> factors..
> _________________
> --
> Aric Caley
> Fonality, inc
> ---------------------------------------
> Sent from YesSoftware forum
> http://forums.codecharge.com/
>
|
|
|
|
DonP
|
| Posted: 04/10/2008, 2:43 PM |
|
Having all the common files in the root has always been a big issue for
me too and has even cost me money when the client didn't like it and
canceled the contract. Short of manually editing all the code, CCS
simply does not make a way for it to be done. It's a shame too because,
for an otherwise good application, it is just poor housekeeping to have
all that "junk" in the root! A Workaround is to put the entire site into
a subfolder and have only a manually created index.html page at the root
that loads the site itself into a full-browser frame. This route should
not be necessary but it works.
I really wish that CCS would be fixed to not have this annoying problem,
which is nothing short of a bug! I was one of the beta testers for v1.0
and up with this pointed out each time.
Don (DonP)
greywire wrote:
> I've been trying to use CCS4 with a new project but have a couple issues.
>
> First of all, is CCS's requirement to put all its support files into the root
> of the website (common.php, mysql.php, etc). There is no way to, say, put them
> all into a folder ("ccslibraries" or something). Not to mention things like
> functions.js -- why is that not in the js folder? I suppose this isn't really a
> serious issue, but its really ugly.. Just adding a setting in Server/Script for
> "common files folder" would do it.
>
> The other problem is that we want our application to have modules, where other
> people can easily add new modules and these modules can be packaged and
> installed separately. Codecharge makes it tricky to even put pages into
> folders, much less make modularity possible.
>
> Unfortunately we will probably be switching to a completely open source
> framework that doesn't have an IDE but that does have no limiting factors..
> _________________
> --
> Aric Caley
> Fonality, inc
> ---------------------------------------
> Sent from YesSoftware forum
> http://forums.codecharge.com/
>
|
|
|
|
greywire
Posts: 37
|
| Posted: 04/11/2008, 7:38 AM |
|
Of course nothing is perfect...
but at least with an open source framework it can be changed to our needs..
I am really trying to keep CCS so we will see...
Quote DonB:
I've never seen any software of any kind that had no limiting factors.
--
DonB
"greywire" < greywire@forum.codecharge> wrote in message
news:547fe56853f0ad@news.codecharge.com...
> I've been trying to use CCS4 with a new project but have a couple issues.
>
> First of all, is CCS's requirement to put all its support files into the
> root
> of the website (common.php, mysql.php, etc). There is no way to, say, put
> them
> all into a folder ("ccslibraries" or something). Not to mention things
> like
> functions.js -- why is that not in the js folder? I suppose this isn't
> really a
> serious issue, but its really ugly.. Just adding a setting in
> Server/Script for
> "common files folder" would do it.
>
> The other problem is that we want our application to have modules, where
> other
> people can easily add new modules and these modules can be packaged and
> installed separately. Codecharge makes it tricky to even put pages into
> folders, much less make modularity possible.
>
> Unfortunately we will probably be switching to a completely open source
> framework that doesn't have an IDE but that does have no limiting
> factors..
> _________________
> --
> Aric Caley
> Fonality, inc
> ---------------------------------------
> Sent from YesSoftware forum
> http://forums.codecharge.com/
>
_________________
--
Aric Caley
Fonality, inc |
|
|
|
greywire
Posts: 37
|
| Posted: 04/28/2008, 10:36 AM |
|
well, I have managed to get around some of these issues by simply doing a post-processing on the code to change references to those included files so they can be put into a folder.
Annoying, but it works.
Then I came up against another problem: the translations file is just a simple text file, and there's only one of them.
The problem with this, is that we want to be able to package modules separately and have them intallable only if you want them (and let other developers create their own modules). So how to handle the translations? You can't overwrite that file because you might blow away some other module's additions.
_________________
--
Aric Caley
Fonality, inc |
|
|
|
|
 |
|
|
|
