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
I've been pointed to this document here:
http://www.djangoproject.com/documentation/faq/#who-s-behind-this
but I'm missing information about the further team member and their roles.
Is such a document available, which lists e.g.
* committers
* subsystem leads (or component leads)
* code
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
On 31-May-06, at 7:07 PM, Michael Radziej wrote:
> It looks as if the current way to handle Django has overloaded the
> core
> developers :-( Simple tickets shouldn't take long. And it would also
> help to know that your ticket ain't gonna make it, but in close time,
> not months later.
look
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
That's right. I just put app_label as a Meta option.
and I hope one day we don't need to set this app_label manaully if
somebody refator the code in ModelBase.__new__ to let our models
app_label set automatically.
Thanks for all your help. :-)
--~--~-~--~~~---~--~---
+1 on 1) ;)
On 6/1/06, John Melesky <[EMAIL PROTECTED]> wrote:
>
> James Bennett wrote:
> > On 5/31/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> >> 1) a commandline util only (via manage.py)
>
> +1
>
> -johnn
>
> >
>
--
Honza Král
E-Mail: [EMAIL PROTECTED]
ICQ#: 107471613
Phone:
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
James Bennett wrote:
> On 5/31/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>> 1) a commandline util only (via manage.py)
+1
-johnn
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" gr
> 1) a commandline util only (via manage.py)
+1
James Bennett wrote:
> On 5/31/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > 1) a commandline util only (via manage.py)
>
> This would maintain consistency with the rest of Django's management
> options; I'd always figured that at lea
On 5/31/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> 1) a commandline util only (via manage.py)
This would maintain consistency with the rest of Django's management
options; I'd always figured that at least part of the schema evolution
interface would involve manage.py.
--
"May the fo
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
regarding how a developer would interact with any schema evolution
implementation...would you prefer / see as more natural:
1) a commandline util only (via manage.py)
2) a web-based UI only (via the admin screens)
3) both
(remember that we're likely talking about a multi-step upgrade
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
You got it. I could barely get any feedback on this project anyhow,
and I don't have much time right now to focus on it. So, no problem.
GL
On 5/29/06, Derek Anderson <[EMAIL PROTECTED]> wrote:
>
> jeroen, brant, ilias, etc:
>
> schema evolution was an idea suggested and specifically granted f
Yeah, I always do that. Sorry.
On 5/29/06, Jeroen Ruigrok van der Werven <[EMAIL PROTECTED]> wrote:
> Brant,
>
> On 4/24/06, Brant Harris <[EMAIL PROTECTED]> wrote:
> > I've created a proposal for working all of the Schema Evolution tidbits out:
> > http://code.djangoproject.com/wiki/SchemaEvolu
Adrian Holovaty wrote:
> On 5/31/06, Jay Parlar <[EMAIL PROTECTED]> wrote:
>> Just wondering what the procedure is for getting a patch accepted? I
>> submitted a patch (http://code.djangoproject.com/ticket/1994) a week
>> ago, and have had no feedback on it so far.
>>
>> Is there some kind of mont
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
On 5/31/06, Michael Radziej <[EMAIL PROTECTED]> wrote:
> Could you trust a patch when some other developers have positively
> reviewed it? This might take a time until your ideas of proper patches
> have been "revealed", but then we'd have a more or less peer review
> system. And it could get the
Adrian Holovaty wrote:
> Ideas for improving
> this system would be much appreciated!
How about spreading the routine work with tickets?
I think you have some people within the non-committers who have a
sufficient deep knowledge of django andf also sufficient trust to
pre-handle tickets. You cou
>> Works like a charm. (I'm hardly an svk expert, though, so there are
>> probably easier/less verbose recipes for doing the same thing.)
> If only Darcs were the norm...
As far as distributed VCSes go, I'd like to cast my vote for Mercurial.
It's a little Python jewel, as fast as Git, more con
On 5/31/06, Adrian Holovaty <[EMAIL PROTECTED]> wrote:
> It's the latter. Me, I generally have one afternoon a week in which I
> focus on clearing out patches and tickets, plus weeknights as my
> schedule allows. I'm pretty sure Jacob works the same way, although he
> has been *super* busy traveli
On 5/31/06, Jay Parlar <[EMAIL PROTECTED]> wrote:
> Just wondering what the procedure is for getting a patch accepted? I
> submitted a patch (http://code.djangoproject.com/ticket/1994) a week
> ago, and have had no feedback on it so far.
>
> Is there some kind of monthly IRC meetup where pending p
On 5/31/06, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
>
> Hi Jay,
>
> svk is your friend. It won't help with getting patches reviewed, but it
> does make keeping a tree of local patches almost painless. Here's my
> recipe:
>
> # set up mirrors of your repository and django trunk
> # and copy dj
Hi Jay,
svk is your friend. It won't help with getting patches reviewed, but it
does make keeping a tree of local patches almost painless. Here's my
recipe:
# set up mirrors of your repository and django trunk
# and copy django trunk under vendor/ in your repository
svk mirror http://code.django
On 5/31/06, Michael Radziej <[EMAIL PROTECTED]> wrote:
> I don't have any experience on how to cope with this efficiently, anyone
> else? Like, having a few experienced Django hackers who'd volunteer to
> review patches, triage old bugs, together with a set of criteria from
> Adrian what would mak
favo wrote:
> Thanks a lot ,I have follow the patch
> put my appsname int hte Meta. it works.
> Thanks. Michael!!
Just to note: you do not need the patch for this to work i.e. if you
can put app_label as a Meta option. The patch enables you to have a
single module level attribute to do the sam
Jay Parlar wrote:
> Just wondering what the procedure is for getting a patch accepted?
You hit it! It would be so nice to have some kind of process in place.
And not just random wait-and-see, as it is currently.
Currently, it's a lot easier for me to just patch django and not share
my patches.
"Ramiro Morales" <[EMAIL PROTECTED]> writes:
> On 5/30/06, Joseph Kocherhans <[EMAIL PROTECTED]> wrote:
>>
>> Has anyone tested out the multi-auth branch yet? I haven't heard
>> anything, so either people aren't using it, or it's working well and
>> the docs are good enough. Personally, I've been
Just wondering what the procedure is for getting a patch accepted? I
submitted a patch (http://code.djangoproject.com/ticket/1994) a week
ago, and have had no feedback on it so far.
Is there some kind of monthly IRC meetup where pending patches are
discussed? Or is it just when the core developer
Ivan Sagalaev wrote:
> gabor wrote:
>
>> for example, i was building a very simple web-file-manager. you can ask
>> python to get you the os.listdir, etc, data in unicode, which i think
>> the only sensible way, because otherwise you have to watch out for the
>> filesystem-encoding. but becaus
Thanks a lot ,I have follow the patch
put my appsname int hte Meta. it works.
Thanks. Michael!!
--~--~-~--~~~---~--~~
You received this message because you are subscribed to the Google Groups
"Django developers" group.
To post to this group, send email to django-
favo wrote:
> I hope someone can see the post because I don't want to repeat it.
> http://groups.google.com/group/django-users/browse_thread/thread/cb3d55413a92151a
>
> I think is easy to fix. anywhere we have the function in 0.91.
> Thanks.
I don't have a fix, but the patch in ticket 1821 might
I hope someone can see the post because I don't want to repeat it.
http://groups.google.com/group/django-users/browse_thread/thread/cb3d55413a92151a
I think is easy to fix. anywhere we have the function in 0.91.
Thanks.
--~--~-~--~~~---~--~~
You received this mes
Bryan wrote:
> My point is how do you lock the user out until he confirms his changed
> email address?
Ah, I had no idea you would want to do that, and can't see why you
would want to (the e-mail address that is stored is still correct), but
you know your requirements. But, you can always set i
Andy Shaw wrote:
> PS: would Luke's GenericForeignKey allow for inline editing, assuming it
> was to be adopted? Personally I'd much rather be able to alter a row's
> permissions on its own admin page than have to switch table.
There would have to be very specialised support for it. I haven't
Luke,
On 5/29/06, Luke Plant <[EMAIL PROTECTED]> wrote:
> In case you didn't notice, this is now done.
Verified to work in my case with the FileField(). Thanks again.
--
Jeroen Ruigrok van der Werven
--~--~-~--~~~---~--~~
You received this message because you a
55 matches
Mail list logo
