really weird conversation for me, too….
> On Apr 29, 2015, at 11:28 AM, Chuck Hill wrote:
>
> Thanks. Now I have to go wash my mind out.
>
> On 2015-04-29, 7:53 AM, "Tom Philip" wrote:
>
> Nothing of mine will be put into DaveLips.
>
> Ever.
>
> Tom
>
> On Apr 29, 2015, at 7:52 AM, Ken Ande
Thanks. Now I have to go wash my mind out.
On 2015-04-29, 7:53 AM, "Tom Philip" wrote:
Nothing of mine will be put into DaveLips.
Ever.
Tom
On Apr 29, 2015, at 7:52 AM, Ken Anderson
mailto:kenli...@anderhome.com>> wrote:
Is it checked in? I think the entire community needs to try out DaveLi
> On Apr 29, 2015, at 10:53 AM, Thomas Philip wrote:
>
> Nothing of mine will be put into DaveLips.
>
> Ever.
That’s probably just fine. All code going into DaveLips will need to be
extensively beer-reviewed, anyway.
I am planning on pulling *frequently* into DaveLips and, unfortunately, the
Nothing of mine will be put into DaveLips.
Ever.
Tom
> On Apr 29, 2015, at 7:52 AM, Ken Anderson wrote:
>
> Is it checked in? I think the entire community needs to try out DaveLips
> (YIKES)
>
>> On Apr 29, 2015, at 7:23 AM, David Avendasora
>> wrote:
>>
>> Pt. Eclipse is so yesterda
Aand there it is. The death of the usefulness of this thread (and the
highpoint of my day).
> On Apr 29, 2015, at 7:52 AM, Ken Anderson wrote:
>
> Is it checked in? I think the entire community needs to try out DaveLips
> (YIKES)
>
>> On Apr 29, 2015, at 7:23 AM, David Avendasora >
Is it checked in? I think the entire community needs to try out DaveLips
(YIKES)
> On Apr 29, 2015, at 7:23 AM, David Avendasora
> wrote:
>
> Pt. Eclipse is so yesterday. I created a D2JC-based Text Editor / IDE
> called DaveLips™ It exclusively uses Vertical Inheritance in it’s modeling
Pt. Eclipse is so yesterday. I created a D2JC-based Text Editor / IDE
called DaveLips™ It exclusively uses Vertical Inheritance in it’s modeling
component and it is deployed in a servlet container.
> On Apr 27, 2015, at 1:42 PM, Chuck Hill wrote:
>
> Dave, have you been typing in Eclipse
Dave, have you been typing in Eclipse again?
On 2015-04-26, 11:02 PM, "David Avendasora" wrote:
The standard WO exception page is starting to show its age and I think it's
high time we improve it.
Ehhx... Ehhhxsep... Exseeeption?
Are you referring to the page that WO always returns until
> On Apr 27, 2015, at 11:11 AM, Gavin Eadie wrote:
>
> A suggestion that might be over-kill: A button for “send error to developer”
> (maybe if, and only if, a Property with a target email exists).
.. as pointed out by others, probably not for production, but I could imagine a
production, app-
Very, very nice .. A suggestion that might be over-kill: A button for “send
error to developer” (maybe if, and only if, a Property with a target email
exists). I get screenshots from customers now, if they know how to make them;
or copy/paste emails if they know where to send them ..
> On Apr
> The standard WO exception page is starting to show its age and I think it’s
> high time we improve it.
Ehhx... Ehhhxsep... Exseeeption?
Are you referring to the page that WO always returns until my code has been
peer-reviewed?
If so, I do think your new one is pretty darn nice!
Dave
>> You'd never put that in a _production_ release though, would you?
>>
>> Looks perfect for development, but in production I'd prefer my exception
>> views to be pretty generic with a non-technical message, unless the app is
>> for internal staff. So, er, that's what we do.
>>
>> Yeah, I woul
On 2015-04-26, 8:43 PM, "Paul Hoadley" wrote:
Aside: am I mis-remembering, or did the Yellow Box exception view include a
link to the IDE code base class and line in development, you know, a zillion
years ago?
Now that you mention it, I recall this too.
Oh you old timers. I'll get off your law
On 27 Apr 2015, at 1:08 pm, Chuck Hill wrote:
> You'd never put that in a _production_ release though, would you?
>
> Looks perfect for development, but in production I'd prefer my exception
> views to be pretty generic with a non-technical message, unless the app is
> for internal staff. So,
On 2015-04-26, 8:34 PM, "Matthew Ness" wrote:
That looks really nice.
Yes, nice work!
You'd never put that in a _production_ release though, would you?
Looks perfect for development, but in production I'd prefer my exception views
to be pretty generic with a non-technical message, unless the
That looks really nice.
You'd never put that in a _production_ release though, would you?
Looks perfect for development, but in production I'd prefer my exception
views to be pretty generic with a non-technical message, unless the app
is for internal staff. So, er, that's what we do.
Aside: am I
I agree, looks great!
Sent from my iPad
> On Apr 26, 2015, at 7:34 PM, Paul Hoadley wrote:
>
>> On 27 Apr 2015, at 7:09 am, Hugi Thordarson wrote:
>>
>
>> The standard WO exception page is starting to show its age and I think it’s
>> high time we improve it. I started a new error page today
On 27 Apr 2015, at 7:09 am, Hugi Thordarson wrote:
> The standard WO exception page is starting to show its age and I think it’s
> high time we improve it. I started a new error page today and added the
> capability to show the code that’s throwing the error (a feature of some of
> the younger
Hi all.
The standard WO exception page is starting to show its age and I think it’s
high time we improve it. I started a new error page today and added the
capability to show the code that’s throwing the error (a feature of some of the
younger web frameworks that I like) but I’d love to hear id
19 matches
Mail list logo