On Thu, 1 Dec 2005 09:10:08 +0200 Chady Kassouf <[EMAIL PROTECTED]>
babbled:
> On 12/1/05, The Rasterman Carsten Haitzler <[EMAIL PROTECTED]> wrote:
> >
> >
> > > Most modern CMS's store content in the DB, not the filesystem. At
> > > least the ones I've used. But we're quickly getting off-topic
On Wed, 30 Nov 2005 07:38:58 +0900 David Stevenson <[EMAIL PROTECTED]>
babbled:
> On that note, here is a resend for something I sent back at October (trivial
> and easily forgotten :-))
in cvs :)
--
- Codito, ergo sum - "I code, therefore I am" --
The Rasterman (Carste
On 12/1/05, The Rasterman Carsten Haitzler <[EMAIL PROTECTED]> wrote:
> Most modern CMS's store content in the DB, not the filesystem. At> least the ones I've used. But we're quickly getting off-topic here,> so I'll stop there. :)all the ones i looked at stored web pages text in the db, but image
On Wed, 30 Nov 2005 22:30:50 -0500 Michael Jennings <[EMAIL PROTECTED]> babbled:
> On Tuesday, 29 November 2005, at 23:11:41 (+),
> Andrew Williams wrote:
>
> > well, I sincerely apologise for not remembering this, but even after
> > the refresher I do not recall what the problem was - does s
Michael Jennings wrote:
Most modern CMS's store content in the DB, not the filesystem. At
least the ones I've used. But we're quickly getting off-topic here,
so I'll stop there. :)
the only thing a CMS should store to disk is images and large binary files..
if a CMS stores other stuff to dis
On Tuesday, 29 November 2005, at 23:11:41 (+),
Andrew Williams wrote:
> well, I sincerely apologise for not remembering this, but even after
> the refresher I do not recall what the problem was - does someone
> have a specific point, or is an "in general it leaks" issue?
I asked Tilman to pos
And follow the coding style of the project. It shouldn't be to difficult
for people, and it looks really messy if everyone just writes their own
style.
Sebastian
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
f
On Tue, 29 Nov 2005 23:09:02 +0100 Tilman Sauerbeck <[EMAIL PROTECTED]>
babbled:
> Vincent Torri <[EMAIL PROTECTED]> [2005-11-29 22:40]:
> > > [patch]
> > > Oooh slipped by us. :) (Really, I think we need something better than
> > > just the list for tracking patches, but, that's another story...)
On Tue, 29 Nov 2005 15:48:29 -0600 Brian Mattern <[EMAIL PROTECTED]>
babbled:
> On Tuesday 29 November 2005 15:05, Morten Nilsen wrote:
> > Brian Mattern wrote:
> > > Ok, it looks like we just need to lay out some simple guidelines to make
> > > everyone happy.
> > >
> > > Contributing code is ALW
On Tue, 29 Nov 2005 23:40:25 +0100 Morten Nilsen <[EMAIL PROTECTED]> babbled:
> Andrew Williams wrote:
> > is this the ecore_config lib patch for ARGB parsing?
>
> according to my archive, that patch came from Dylan Shell (and it got
> comments :)
> that patch also seems to be as simple as "s/st
as per bug #290 - do we want to link this bug tracker to the e website?
or is it just internal and belonging on edevelop?
/A
On Tue, Nov 29, 2005 at 06:15:39PM -0500, dan sinclair wrote:
> >
> > We already have Mantis set up that's not used :/
> > mantis.xcomputerman.com or something.
> >
>
>
>
> We already have Mantis set up that's not used :/
> mantis.xcomputerman.com or something.
>
xcomputerman.com/bugs
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? Stop! Download the new A
On Tue, Nov 29, 2005 at 11:40:25PM +0100, Morten Nilsen wrote:
> Andrew Williams wrote:
> >is this the ecore_config lib patch for ARGB parsing?
>
> according to my archive, that patch came from Dylan Shell (and it got
> comments :)
> that patch also seems to be as simple as "s/strtol/strtoul/" :)
On Tue, Nov 29, 2005 at 05:57:47PM -0500, Michael Jennings wrote:
> On Tuesday, 29 November 2005, at 21:49:24 (+),
> Andrew Williams wrote:
>
> > Many apologies, I do not remember which leak this is that you refer to.
>
> Allow me to refresh your memory...again:
>
> 1251 tilman: I'd lik
On Tuesday, 29 November 2005, at 21:49:24 (+),
Andrew Williams wrote:
> Many apologies, I do not remember which leak this is that you refer to.
Allow me to refresh your memory...again:
1251 tilman: I'd like to see it imported so that edb_gtk_ed
in libs/edb can die die die die die.
1251
Andrew Williams wrote:
is this the ecore_config lib patch for ARGB parsing?
according to my archive, that patch came from Dylan Shell (and it got
comments :)
that patch also seems to be as simple as "s/strtol/strtoul/" :)
or the ecore_config app patch for listing keys?
that one was by me,
On that note, here is a resend for something I sent back at October (trivial and easily forgotten :-))
This wee one liner just centers the optional digital text string for e's clock module (instead of left aligning it).
Index: apps/e/data/themes/default_clock.edc
===
>
> no.. I'm referring to my patch implementing ecore_config list :)
>
Can you just resend the patch and make this easier for everyone.
dan
---
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems? S
Many apologies, I do not remember which leak this is that you refer to.
I know ecore_config lacks features etc and I will attend to it as soon
as my TODO list reaches ecore_config. Engage also needs my love, and it
does in the background, simply nothing committed yet.
Not sure that "asleep at the
On Tue, Nov 29, 2005 at 10:05:42PM +0100, Morten Nilsen wrote:
> Brian Mattern wrote:
> >Ok, it looks like we just need to lay out some simple guidelines to make
> >everyone happy.
> >
> >Contributing code is ALWAYS welcome. Write your code, then use 'cvs diff
> >-u' to create a patch. Attach it
Nathan Ingersoll wrote:
On 11/29/05, Morten Nilsen <[EMAIL PROTECTED]> wrote:
In my opinion, however, I don't see why one wouldn't want dir sort..
Are you referring to ecore_file_ls?
no.. I'm referring to my patch implementing ecore_config list :)
Cheers,
--
Morten
--
On 11/29/05, Morten Nilsen <[EMAIL PROTECTED]> wrote:
In my opinion, however, I don't see why one wouldn't want dir sort..Cheers,--Morten
Are you referring to ecore_file_ls?
Vincent Torri <[EMAIL PROTECTED]> [2005-11-29 22:40]:
> > [patch]
> > Oooh slipped by us. :) (Really, I think we need something better than just
> > the
> > list for tracking patches, but, that's another story...)
>
> bugzilla ?
We already have Mantis set up that's not used :/
mantis.xcomputerma
Brian Mattern wrote:
On a quick glance, sorting directory first should probably be made an options.
I know I've seen contention on the list over which way is 'correct' before...
it's easy enough to select dir first or not at compile-time (change an
#if 1), but making it a run-time option shoul
On Tue, 29 Nov 2005 22:40:29 +0100 (CET) Vincent Torri
<[EMAIL PROTECTED]> wrote:
> On Tue, 29 Nov 2005, Brian Mattern wrote:
>
> > On Tuesday 29 November 2005 15:05, Morten Nilsen wrote:
> > > Brian Mattern wrote:
> > > > Ok, it looks like we just need to lay out some simple
> > > > guidelines t
On Tue, 29 Nov 2005, Brian Mattern wrote:
> On Tuesday 29 November 2005 15:05, Morten Nilsen wrote:
> > Brian Mattern wrote:
> > > Ok, it looks like we just need to lay out some simple guidelines to make
> > > everyone happy.
> > >
> > > Contributing code is ALWAYS welcome. Write your code, then
On Tuesday 29 November 2005 15:05, Morten Nilsen wrote:
> Brian Mattern wrote:
> > Ok, it looks like we just need to lay out some simple guidelines to make
> > everyone happy.
> >
> > Contributing code is ALWAYS welcome. Write your code, then use 'cvs diff
> > -u' to create a patch. Attach it to an
On Tuesday, 29 November 2005, at 22:05:42 (+0100),
Morten Nilsen wrote:
> I never heard anything about the ecore_config patch I sent in..
> noone even told me it sucked :)
Indeed! If you want to talk about showstoppers and maintainers who
are asleep at the wheel, let's talk about HandyAndE and t
Brian Mattern wrote:
Ok, it looks like we just need to lay out some simple guidelines to make
everyone happy.
Contributing code is ALWAYS welcome. Write your code, then use 'cvs diff -u'
to create a patch. Attach it to an email to this list. If you haven't heard
back after a few days, send an
Ok, it looks like we just need to lay out some simple guidelines to make
everyone happy.
Contributing code is ALWAYS welcome. Write your code, then use 'cvs diff -u'
to create a patch. Attach it to an email to this list. If you haven't heard
back after a few days, send another response. Or, sen
30 matches
Mail list logo
