On 6/1/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
>
> [EMAIL PROTECTED] wrote:
> > You can try this EnergyKey
> > http://www30.webSamba.com/SmartStudio
> > This may be help you.
> > Now I always use EnergyKey, it helps me so much in my work.
>
> very intresting tool!
There's an interesting ph
[EMAIL PROTECTED] wrote:
> You can try this EnergyKey
> http://www30.webSamba.com/SmartStudio
> This may be help you.
> Now I always use EnergyKey, it helps me so much in my work.
very intresting tool!
.
--
http://lazaridis.com
--~--~-~--~~~---~--~~
You receiv
You can try this EnergyKey
http://www30.webSamba.com/SmartStudio
This may be help you.
Now I always use EnergyKey, it helps me so much in my work.
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers"
Adrian Holovaty wrote:
> On 5/31/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
>> I think you've missinterpreted the writings in the frot-page.
>
> OK, everybody, let's settle down... This is slowly turning into a
> really lame argument that's not much fun to read.
>
> More smiles! More comrade
On 5/31/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
> I think you've missinterpreted the writings in the frot-page.
OK, everybody, let's settle down... This is slowly turning into a
really lame argument that's not much fun to read.
More smiles! More comradery! More friendliness!
Ilias, thank
Kenneth Gonsalves wrote:
>
> On 01-Jun-06, at 12:28 AM, [EMAIL PROTECTED] wrote:
>
This is actually one of the accepted Summer of Code projects for
Django, so the best answer is perhaps to way until the end of the
summer to see what happens with it.
>>> I cannot wait so long and a
John Melesky wrote:
> Ilias Lazaridis wrote:
>> Comparing with other systems, this admin interface is one of the
>> strongest points of Django.
>>
>> Remember that not every user is able to take all the setup barriers.
>
> If Django were an application intended to be used by end-users, then i
>
Jay Parlar wrote:
> On 5/31/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
>> And an efficient tool should assist a user to become productive immediately.
>>
>> http://case.lazaridis.com/multi/wiki/Product#Functionality
>>
>> There are webframeworks which provide this functionality.
>>
>
> What e
On 01-Jun-06, at 12:28 AM, [EMAIL PROTECTED] wrote:
>
>>> This is actually one of the accepted Summer of Code projects for
>>> Django, so the best answer is perhaps to way until the end of the
>>> summer to see what happens with it.
>>
>> I cannot wait so long and additionally I sense several pr
Ilias Lazaridis wrote:
> Comparing with other systems, this admin interface is one of the
> strongest points of Django.
>
> Remember that not every user is able to take all the setup barriers.
If Django were an application intended to be used by end-users, then i
might buy this argument. But it
On 5/31/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
>
> And an efficient tool should assist a user to become productive immediately.
>
> http://case.lazaridis.com/multi/wiki/Product#Functionality
>
> There are webframeworks which provide this functionality.
>
What exactly are you basing that c
James Bennett wrote:
> On 5/31/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
>> Please feel free to send me any concrete criticism about my website via
>> private email (your comments are very welcome).
>
> I seem to have screwed that up by forgetting that replies go to the
> list by default. My
James Bennett wrote:
> On 5/25/06, lazaridis_com <[EMAIL PROTECTED]> wrote:
>> * Replace command "django-admin.py" by "django-admin" or "django"
Thanks for your reply, but the discussion has evolved a little.
I had already replied to the reply of Mr. Joseph Kocherhans:
http://groups.google.com/
On 5/31/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
> Please feel free to send me any concrete criticism about my website via
> private email (your comments are very welcome).
I seem to have screwed that up by forgetting that replies go to the
list by default. My apologies for the mistake.
--
On 5/25/06, lazaridis_com <[EMAIL PROTECTED]> wrote:
> * Replace command "django-admin.py" by "django-admin" or "django"
Naming it 'django' would likely cause confusion, leading users to
believe that it runs an entire Django-powered site. There is a web
server built in to it, but this web server
Jay Parlar wrote:
> On 5/31/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
>> Additionally: The fact that I have _not_ the full domain knowledge (=
>> background information) enables me to make those "sweeping suggestions"
>> from a newcomers point of view (who cares not much about project details
On 5/31/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
> The term 'Audit' explained here:
>
> http://case.lazaridis.com/multi/wiki/ProjectOverview
That page is a lot of marketing speak along with a note that open
source projects can order your services at a "reduced rate". So now
you sound like y
On 5/31/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
> Additionally: The fact that I have _not_ the full domain knowledge (=
> background information) enables me to make those "sweeping suggestions"
> from a newcomers point of view (who cares not much about project details
> and internals, but j
Tom Tobin wrote:
> On 5/31/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
>> Jacob Kaplan-Moss wrote:
>>> On May 25, 2006, at 11:27 AM, lazaridis_com wrote:
>>>
At this point, Django's persistency layer seems intresting, but the
evaluation uncovered a few weaknesses, most importantly the
James Bennett wrote:
> On 5/31/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
>> Additionally: The fact that I have _not_ the full domain knowledge (=
>> background information) enables me to make those "sweeping suggestions"
>> from a newcomers point of view (who cares not much about project deta
[EMAIL PROTECTED] wrote:
>>> This is actually one of the accepted Summer of Code projects for
>>> Django, so the best answer is perhaps to way until the end of the
>>> summer to see what happens with it.
>> I cannot wait so long and additionally I sense several problems for the
>> SoC project:
>>
On 5/31/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
> Additionally: The fact that I have _not_ the full domain knowledge (=
> background information) enables me to make those "sweeping suggestions"
> from a newcomers point of view (who cares not much about project details
> and internals, but j
[EMAIL PROTECTED] wrote:
>> I assume "Adrian Holovaty" is the Django Project Lead?
>>
>> Is there a Team Overview available?
>
> Disclaimer: I don't intend this to be rude, so forgive me if it sounds
> that way...
>
> Is it possible, given you haven't read the very first link on the
> Django Sit
> I assume "Adrian Holovaty" is the Django Project Lead?
>
> Is there a Team Overview available?
Disclaimer: I don't intend this to be rude, so forgive me if it sounds
that way...
Is it possible, given you haven't read the very first link on the
Django Site
(http://www.djangoproject.com/document
>> This is actually one of the accepted Summer of Code projects for
>> Django, so the best answer is perhaps to way until the end of the
>> summer to see what happens with it.
>
> I cannot wait so long and additionally I sense several problems for the
> SoC project:
>
> http://case.lazaridis.com/m
On 5/31/06, Ilias Lazaridis <[EMAIL PROTECTED]> wrote:
>
> Jacob Kaplan-Moss wrote:
> > On May 25, 2006, at 11:27 AM, lazaridis_com wrote:
> >
> >> At this point, Django's persistency layer seems intresting, but the
> >> evaluation uncovered a few weaknesses, most importantly the lack of
> >> sche
Jacob Kaplan-Moss wrote:
> On May 25, 2006, at 11:27 AM, lazaridis_com wrote:
>
>> At this point, Django's persistency layer seems intresting, but the
>> evaluation uncovered a few weaknesses, most importantly the lack of
>> schema evolution support:
>
> This is actually one of the accepted Summ
Joseph Kocherhans wrote:
> On 5/25/06, lazaridis_com <[EMAIL PROTECTED]> wrote:
>> At this point, Django's persistency layer seems intresting, but the
>> evaluation uncovered a few weaknesses, most importantly the lack of
>> schema evolution support:
>>
>> http://case.lazaridis.com/multi/wiki/Djan
On Friday 26 May 2006 8:14 am, Eugene Lazutkin wrote:
> > This is actually one of the accepted Summer of Code projects
> > for Django, so the best answer is perhaps to way until the
> > end of the summer to see what happens with it.
>
> ...or he can discuss it with Derek Anderson (the student) a
Jacob Kaplan-Moss wrote:
>
>> schema evolution support:
>
> This is actually one of the accepted Summer of Code projects for
> Django, so the best answer is perhaps to way until the end of the
> summer to see what happens with it.
...or he can discuss it with Derek Anderson (the student) an
and i would be said SoC applicant. :)
Kenneth Gonsalves wrote:
> On Thursday 25 May 2006 10:43 pm, Joseph Kocherhans wrote:
>> Schema evolution support has already been discussed at length.
>> See: http://code.djangoproject.com/wiki/SchemaEvolution but it's
>> not implemented yet.
>
> there is
On Thursday 25 May 2006 10:43 pm, Joseph Kocherhans wrote:
> Schema evolution support has already been discussed at length.
> See: http://code.djangoproject.com/wiki/SchemaEvolution but it's
> not implemented yet.
there is a django soc project for this
--
regards
kg
http://www.livejournal.com/
On May 25, 2006, at 11:27 AM, lazaridis_com wrote:
> At this point, Django's persistency layer seems intresting, but the
> evaluation uncovered a few weaknesses, most importantly the lack of
> schema evolution support:
This is actually one of the accepted Summer of Code projects for
Django, so
On 5/25/06, lazaridis_com <[EMAIL PROTECTED]> wrote:
>
> At this point, Django's persistency layer seems intresting, but the
> evaluation uncovered a few weaknesses, most importantly the lack of
> schema evolution support:
>
> http://case.lazaridis.com/multi/wiki/DjangoProductEvaluation
Schema ev
For a long term project, I am selecting a python based persistency
system:
http://case.lazaridis.com/multi/wiki/Persist
At this point, Django's persistency layer seems intresting, but the
evaluation uncovered a few weaknesses, most importantly the lack of
schema evolution support:
http://case.l
35 matches
Mail list logo
