Robert Shiplett's Blog

8 Posts

Language popularity

Posted by Robert Shiplett Sep 1, 2010

Over at http://langpop.com/ you can see a web-sampling of the company we keep: Icon, Mercury, Oz, Prolog, Rebol, Self, Snobol and Strongtalk are among our invisible cohort ...

 

One language which is present in those serial graphs is Erlang - a language that almost disappeared due to a language fiat at Ericsson. Other new or incubating languages that are off the charts include Converge, Falcon and Io.

 

But Forth is there.

 

One missing chart is languages mapped to "suitability to task". That could be amusing.  Or languages mapped to "excessive number of lines of code". Or "maintenance nightmares".  It may be that such charts derived from "lessons-learned" posts can be created in Web 4.0

 

Smalltalk appears in the charts in a few disguises: as Objective-C and Ruby. Post-Smalltalk Self is there in disguise as JavaScript and ActionScript ( and word is that Google V8 may have benefited from revisiting the use of inlining in Self.)  And Smalltalk Traits are there in Scala.  But surely Algol tops the list of "shadow" languages.

 

Perhaps a chart for top-rated corporate app's in Japan and Korea would find Curl jousting in the lists.

 

Siemens had been an early user of Curl and they remain a user of legacy Pascal in some important and profitable applications.  So it is not surprising to see Pascal there (it may still be used for teaching purposes here and there.)

0 Comments Permalink Tags: web_metrics, programming_language

Over at http://aule-browser.com/multi-curl/index.htm I have placed a new Curl example. This one shows two Curl applets embedded within a single web page.

 

It might not be obvious why you would want to do this, but I can think of at least three examples involving compliance monitoring, audit and annotations.

 

I have another example of running more than one EmbeddedBrowserGraphic against books.google.com within the same Curl applet, but this is somewhat different.

 

Each applet is embedded in one of two div elements within a main div in the HTML page's body element.  The height of each div on the page is set by a style with a percent value.

 

Tested on webkit (Safari), Mozilla gecko, Opera 10.60 and IE8

1 Comments Permalink Tags: html, div, object, embed, multiple_applet

Enterprise development is very often for the company's approved browser only, but Curl pages on the internet have to address cross-browser issues.

 

For the past few days I have been trying to get all of my pages to resize and paginate correctly on a half-size netbook screen in an Ubuntu Web-Kit browser.

 

There is still a way to go: the worst problem is the MIME-type behavior.  I have finally stopped embedding .curl URL's in the href of any of my public Curl { link } expressions and retreated to always wrapping Curl in HTML.

 

This has had the positive result of getting me to update my HTML and XHTML.  In other blog posts here I have noted some of the changes that seem effective across all browsers: chief among them is setting a <div> inside the <body> and styling that div to have a height of 100%.  Also I am now careful to place a <div> inside the embedding <object> element so that my HTML pages which embed Curl now end as

       </div>

     </object>

    </div>

  </body>

</html>

which lets me see at a glance that probably the page presents OK and validates as well.

 

You can test my HTML efforts at logiquewerks.com/index.htm and my XHTML+RDFa efforts at logiquewerks.com/index.html

 

Of course this effort is moot if my sitemap.xml file is not picked up by search engines such as Google.

 

Curl Corp. might want to consider updating the default HTML boilerplate for embedding Curl and the docs on embedding Curl in XHTML pages as at least one of the CSS issues was not obvious.

 

Curl Corp's Chris Barber has some very useful JavaScript snippets over at his Zuzu pages at code.google.com and I'll post a note on using those next time.

0 Comments Permalink Tags: rdfa, zuzu, html, css, sitemap.xml, link, defaultdocument, plaindocument, document-style, height, cross-browser, dtd, validate, xhtml, div, embedding, embed

Curl MDI Framework

Posted by Robert Shiplett Jun 22, 2010

Over at www.logiquewerks.com there is now a Curl 7.0 version of Paul Sheehan's "Enterprise Curl" MDI framework as version 1.2.  You will find it under the "Curl Examples" link.

 

I will update the code repository at code.google.com over the next 24-hours.

 

The worst issue was restoring window drag behavior to the AppCanvas.  An MDI Window would only drag to a point where the cursor reached the bounds of its previous position!  You could move a window across the screen in steps, but not in one sweep of the mouse.  This was really odd and I could not find an error in the event handling.

 

Then in an odd moment of inspiration I went to flip the color of the background canvas to see if there was something obscure there - bingo!  No background was set in the constructor and as soon as a {Background } was provided the strange behavior vanished. To test this, I removed the "fix"and redeployed.  Fenced-in behavior returned.  Made the one change, deployed that PCurl only: odd behavior vanished. But is it a bug?

 

Another nuisance was to track down the places where bits of web server context information were hard-coded.  I forced the issue by moving all files, directories and even package names to lower-case ( I think of this as unix-friendly and a break with Java-file-mindset.)  It took a little patience, but now that hard-coding issue is looked after.

 

There is still lots of work to do on this little demo framework: visit the project at code.google.com

0 Comments Permalink Tags: curl, enterprise, background, drop, drag, canvas, framework, mdi

Over at astro.aule-browser.com there is now a page with one of the most beautiful images returned to us from the Hubble Space Telescope: M13*.

 

One of Galileo's achievements had been establishing that some "nebulae" were not "clouds" but clusters of stars.  One of the most beautiful of these can be seen even in a smal telescope by "looking off the fovea".  It is a remarkable experience once you have learned not to "look" at the fuzzy patch, but just allow it to be seen by the outer areas of your retina.

 

I have tried to find an optimal layout for this beautiful image: at the moment I am using a 600px X 600px JPG.  I will add more size options. The image is loaded without blocking, so you may see a reminder in white-on-black in the intended frame.

 

If you have a layout suggestion for this very fine image, please add a comment.  The image preserves its aspect-ratio on resizing the browser and the ImageGraphic instance is wrapped in a black frame using black {Fill } and sits in a "silver" background using silver {Fill }.  The title is centered in a { TextFlowBox }.

 

See the Curl documentation on ImageGraphic, ImageData and ImageLoader for more information.

 

The text-proc {image } is intended to be used in a simple document and an example can be found in the docs under Frame.

 

One issue about loading images async is that the target must be compatible with your server's Curl license.  What this means in my case is that I am at the moment unable to target astro.aule-browser.com but must instead use the full www.aule-browser.com/astro as the path to the image.  If a user enters from astro.aule-browser.com they get a warning when the applet tries to load from the available www path.  Each time a subdomain is added to aule-browser, I face these license issues ... but only if the applet tries to go back for a resource after startup.  I think this may also be an issue for the {image } text-proc.

 

*M13 or NGC  6205 is known as the Hercules Globular Cluster because it is in the "keystone" or "flower pot" of the constellation Hercules.  In the northern hemisphere near summer solstice (about now) it is overhead before midnight and very visible in even good binoculars.  Look in the "western" long-edge of the "keystone" asterism - the grey fuzzy area is not a star!  Although called Messier 13, it is credited to Halley.  M13 was recently shown to have captured a younger blue "field" star in the course of its movement in the Milky way.  A cluster within a galaxy such as M13 should not be confused with a distant elliptical galaxy (itself likely part of a galactic group.)

0 Comments Permalink Tags: jpg, messier, hubble, m13, imagedata, imageloader, fill, aspect_ratio, imagegraphic, image

There are a number of ways to ensure that a confidential document cannot be printed or screen-captured when presented in a Curl widget.

 

One essential thing to know about print suppression is that if you embed a Curl applet in HTML as an <object> then you can use the style for that page to control presentation on screen separately from presentation in print.

 

Here is a simple example of CSS that I use in a page presenting copyright material which is for eyes-only (no permission to reproduce)

<style type="text/css" media="print">
  html {overflow: auto; margin:0; height:5%;}
  body {overflow: hidden;
    margin:0;
    padding:0;
    height:3%;
  }
object{
   height:2%;
   width:3%;
}
</style>

The result for a page print is a minimal page with perhaps the title as header and the url as footer.

 

The key is in the media attribute of the style's type - in our case media="print".

 

The page has another style definition for media="screen".

 

For printing, the HTML has a minimal height, the body somewhat less, and the object element almost none.  I avoid zero values if I can because some browsers have a history of reacting poorly to some zero values.  And when I see SOMETHING print (a header and footer), I know what will NOT print.

 

And of course you will want to test your style against multiple browsers on the usual operating systems.

 

What is more: the Curl content itself should have a top-level graphic which is suppressing its context menu and the entire applet should suppress the inspection gesture.

1 Comments Permalink Tags: url, title, footer, header, width, height, embed, style_type, print_preview, element, object, body, screen, media, type, style, browser, applet, print, confidential_document, text, css, curl

One good reason to use CSS with the <object> tag when embedding Curl applets in HTML is that you can specify the media type in the style sheet.

 

When the media type is "screen" I set the view to 100% sizes for HTML, BODY nd OBJECT.

 

But when I have copyrighted text to present, I set the values of height and width to minimal pixel non-zero values for HTML, BODY and OBJECT in the separate style for "print" media.

 

In Curl we ususally suppress the developer menu popup with {disable-inspection-gesture}.

 

For the top-level graphic, we can suppress the context menu with

 

my-graphic.add-event-handler
    {on evt:AttachEvent do
       set evt.root-frame.context-menu-for-view = null
    }

 

You can even simply pass

    {on evt:AttachEvent do
       set evt.root-frame.context-menu-for-view = null
    }

to a {paragraph } that is an outer wrapper ( I do this in a custom {view-only} text procedure.)

 

Whether or not selection is left enabled, IE will still have Select-all enabled and then Copy will enable on the browser Edit menu - but nothing is captured.

 

If you have set a title for you page, the print view in the browser offers just about that much.

 

By monitoring mouse events and key events and/or using a splash screen you can also keep the clipboard clear and block Screen Print/capture activities when you want a document to be "for-your-eyes-only".

 

By using just the outer wrapper to suppress the context menu, you can encourage users to register, respect copyright or others restrict access to text resources such as restricted technical or policy papers or pre-prints of not-for-release materials.  For registered users, you point to a page with a stub for that wrapper - but the Curl markup of a text need not change.  It remains a simple, useful, readable and elegant as ever.

1 Comments Permalink Tags: context_menu_for_view, inspection_gesture, print, media, style, object, css, embed, curl, popup, suppress

I have a couple of new examples of using our Embedded Browser Graphic in my Curl pages at logiquewerks.com

 

There is now an internet search browser, an e-mail browser and an on-line movies browser.

 

Another is for an "eyes-only" browser for text on confidential web pages using Windows and Internet Explorer.

 

Use the Move Controller button first and drag the controller dialog to one side.

 

Then click Show Document.

 

Suggestions welcome.  One way of defeating the "controller" was overcome today.

 

And it keeps an eye on the Windows clipboard ;-)

 

 

Technorati Profile

7 Comments Permalink Tags: aule_browser, site-specific_browser, browser, embeddedbrowsergraphic, curl, ssb
Robert Shiplett

Robert Shiplett

 Member since: Oct 17, 2007

Curl RIA developer notes.

View Robert Shiplett's profile

Actions

Popular Blog Posts