RE: Announcing jj5-win

"Shawn Wildermuth" <[email protected]> Sun, 25 Mar 2012 13:47:33 -0400
Newsgroups gmane.comp.windows.off-topic
Message-ID <[email protected]>
I think that's always been a problem of yours.

 

- stw

 

Note: This was typed on a big ole laptop so any misspellings and
punctuations are completely my fault.not my phone's.

 

From: [email protected]
[mailto:[email protected]] On Behalf Of Shawn A. Van Ness
Sent: Sunday, March 25, 2012 1:23 AM
To: [email protected]
Subject: Re: [OT] Announcing jj5-win

 

  

Disregard my below rant about WPF and powershell.  Now that I take 10
seconds to look, it is *not* a WPF based UI...   not sure how I got it into
my head that it was.  

 

I think I was mis-remembering some inhouse prototype that I saw...  probably
a perf-test app to measure scrolling/clipping performance in WPF.

 

After a few years inside MS, it became very difficult for me to keep track
of what was real and what was imaginary... lol.

 

-S

 

On Sat, Mar 24, 2012 at 9:57 PM, Shawn A. Van Ness <[email protected]>
wrote:

    del /s *

?

 

Maybe that doesn't work on XP..?   Try this...

 

    for /f "usebackq delims=" %I in (`dir /s /b /a-d`) do @del "%I"

 

Or expand to something like this, if you need special handling for
readonly/hidden files, or symlinks.

 

    for /f "usebackq delims=" %I in (`dir /s /b /a-d`) do (

        @attrib -s -h -r "%I"

        @del "%I"

    )

 

Even I haven't yet found the patience to learn powershell.   It was a great
idea, but the fact that they built the console UI with WPF frightens me
greatly.  (And I say that as a huge WPF fan...  it's just the wrong tool for
the job.  And the wrong job for the tool, from a program mgmt perspective --
there are dozens maybe hundreds of OS features that could benefit from a WPF
rewrite.  But the cmd console?  wtf...  yeah I really wanted my cmd console
process to use 30x more memory, and scroll shit slow because my server box
can't do hw accel clipping, or rasterization of font glyphs, or what have
you)

 

Anyway, long ago, before the advent of powershell...  for anything that I
couldn't reasonably do via ordinary cmd script, I wrote a little 2-line
script to compile and execute a JScript.NET file.

 

I still have a collection of about a dozen of those little .js scriptlets,
which I use for things like beautifying xml files, converting a text file
to/from UTF8 or UTF16, converting tabs to spaces in source files, etc etc.

 

I should clean up those scripts and post them somewhere.   JScript.NET is
all but abandoned, as a language, I gather, but the jsc.exe compiler for CLR
v2 is preinstalled on Windows, so as long as that remains true, who cares.
:-)

 

-S

 

On Sat, Mar 24, 2012 at 5:46 PM, John Elliot <[email protected]> wrote:

On 2012-03-25 11:25, Adwait Ullal wrote:
> Powershell?

BASH? :)

I think I'm done learning about new Microsoft technology. :P

I'm still running Windows XP (in VMWare Fusion on my Mac) and can't see
myself upgrading any time soon.

I'll just kick along with my old tricks for now.

What did you think of my idea of finding distinct characters to use in
'IDs' and 'codes' provided by my software? I think this could be a huge
boost to productivity as misheard and misread characters waste the time
of a lot of people every day.







------------------------------------

Yahoo! Groups Links