headers
marc_clifton2000 | 10 Jul 16:20

Imperative vs. Declarative programming

Hi All,

I've posted a short blurb about the benefits of separating 
declarative code from imperative code:

http://www.myxaml.com/wiki/ow.asp?DeclarativeVsImperativeProgramming

Comments are welcome!

Marc

------------------------ Yahoo! Groups Sponsor --------------------~--> 
Yahoo! Domains - Claim yours for only $14.70
http://us.click.yahoo.com/Z1wmxD/DREIAA/yQLSAA/nhFolB/TM
--------------------------------------------------------------------~-> 

 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/xaml-talk/

<*> To unsubscribe from this group, send an email to:
    xaml-talk-unsubscribe <at> yahoogroups.com

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/
Permalink | Reply | 2 comments |
headers
Gerald Bauer | 10 Jul 16:57
Picon
Favicon

xaml-talk Archive and Newsgroup Service @ Gmane Now Live

Hello,

  Thanks to Gmane - http://gmane.org - the XAML Developers Mailinglist
(xaml-talk) is now also available as a newsgroup subscription service
@ news://news.gmane.org/gmane.comp.lang.xaml.general

  Gmane also keeps an online archive that you can use as an
alternative to the Yahoo! Group archive; you find it online @
http://news.gmane.org/gmane.comp.lang.xaml.general

- Gerald

-------------------
Gerald Bauer

XUL Alliance | http://xul.sourceforge.net  
United XAML  | http://xaml.sourceforge.net

Interested in hiring Gerald Bauer? Yes, I'm available. 
If you know of an opportunity, please contact me today.

------------------------ Yahoo! Groups Sponsor --------------------~--> 
Yahoo! Domains - Claim yours for only $14.70
http://us.click.yahoo.com/Z1wmxD/DREIAA/yQLSAA/nhFolB/TM
--------------------------------------------------------------------~-> 

 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Gerald Bauer | 11 Jul 00:42
Picon
Favicon

Re: Imperative vs. Declarative programming

Hello,

> I've posted a short blurb about the benefits of separating 
> declarative code from imperative code:

   I just stumbled over a comment by Manish Jethani that touches on
the same theme. Manish writes:

   The "in" thing now is to put the UI description, including the
association of event handlers with their controls, into an XML file.
XUL, XAML, SwixML, .... The UI is separate from the logic.

 Mozilla, in particular, actually does all of its UI work in the XUL
layer. The event handlers are actually just JavaScript functions! The
execution doesn't go into Mozilla "core" (I mean the C++ code, the
components that make up the real Mozilla) until there's some real work
to be done. It's really fantastic.

  Now, haven't we come full circle? The UI in VB was a FMB (binary)
file. In VC++ it was a RES (binary again) file. They've just become
XML files now. :) Writing programming language code manually to set up
the UI never appealed to me.

   - Gerald

-------------------
Gerald Bauer

XUL Alliance | http://xul.sourceforge.net  
United XAML  | http://xaml.sourceforge.net
(Continue reading)

Permalink | Reply | 1 comment |
headers
marc_clifton2000 | 11 Jul 01:46

Re: Imperative vs. Declarative programming

I think the key point is in this statement: "The execution doesn't 
go into Mozilla "core" (I mean the C++ code, the components that 
make up the real Mozilla) until there's some real work to be done. 
It's really fantastic."

in particular--"until there's some real work to be done".

So no, I don't think we've come full circle.  I like the idea of 
having workflows defined in a scripting language.  While I'm not 
using JavaScript with MyXaml (hmmm, maybe I really should take 
another look at this), I've put together a concept piece for 
managing workflows in XML.

See http://www.myxaml.com/wiki/ow.asp?Workflows

Marc

------------------------ Yahoo! Groups Sponsor --------------------~--> 
Make a clean sweep of pop-up ads. Yahoo! Companion Toolbar.
Now with Pop-Up Blocker. Get it for free!
http://us.click.yahoo.com/L5YrjA/eSIIAA/yQLSAA/nhFolB/TM
--------------------------------------------------------------------~-> 

 
Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/xaml-talk/

<*> To unsubscribe from this group, send an email to:
(Continue reading)

Permalink | Reply | 0 comments |
headers
Gerald Bauer | 19 Jul 22:59
Picon
Favicon

Miguel de Icaza (Mono Chief) and Brendan Eich (Mozilla Chief) On MS-XAML/Avalon

Hello,

   InfoWorld has published a short interview of Miguel de Icaza (Mono
Chief) and Brendan Eich (Mozilla Chief) about Avalon/MS-XAML.

   Miguel de Icaza: Avalon is a very extensive API, but while there is
a lot of abstraction, there is not enough encapsulation. It's a
high-level standard toolkit. The problem we have today with Unix
toolkits, Mac OS toolkits, and Windows toolkits is that we are still
using the same controls. Developers and designers are building
applications in terms of the following items: scroll bars, enter
lines, buttons, text entries, radio buttons, pop-up menus, combo
boxes. Avalon is not presenting us with new controls or innovative
ways of dealing with large volumes of data. And yet this massive API
says you have to be completely bound to a particular version of the
.Net Framework. This is not the approach the Web has taken, which is
that a table or button can be rendered in different ways appropriate
to the platform.

 Brendan Eich: That's right. If you look at XAML's style language,
they really muddle the presentation/structure separation. 

   ... 

  Q: It's been argued that because there are 15 ways people have
approached XUL [Extensible User Interface Language], Flex, XAML,
whatever -- and you can't reconcile them -- maybe it's time for a de
facto standard implementation.

 Brendan Eich: XAML is not that thing, though, because, as Miguel
(Continue reading)

Permalink | Reply | 2 comments |
headers
marc_clifton2000 | 20 Jul 03:52

Re: Miguel de Icaza (Mono Chief) and Brendan Eich (Mozilla Chief) On MS-XAML/Avalon

Yeah, I read that a few days ago, and the last line struck me as odd:

"XAML is not that thing, though, because, as Miguel says, they've 
bound it too tightly to their class structure."

There's something here that I'm confused about.  My understanding is 
that Microsoft implemented a general parser engine and then some 
custom stuff for visual trees, compound notation, etc.  I come to 
that conclusion because of my understanding of how the namespace 
mapping works, and that in theory you should be able to plug in any 
assembly and use it.

Now, given that assumption, the sentence about being too tightly 
bound to their class structure doesn't make any sense.  XAML can 
work with ANY class structure, supposedly, not just Avalon.  Now, of 
course, there ARE specific things about the parser, in my 
understanding, like how styles and visual trees work, but that's 
only a part of puzzle.  What the above quote implies is a coupling 
that would prevent XAML from working with anything other than 
Microsoft's Avalon class structure, which I don't think is the case.

Anyone care to enlighten me on this?  Or does Miguel and Brendan not 
know what they're talking about?

Marc

------------------------ Yahoo! Groups Sponsor --------------------~--> 
Yahoo! Domains - Claim yours for only $14.70
http://us.click.yahoo.com/Z1wmxD/DREIAA/yQLSAA/nhFolB/TM
--------------------------------------------------------------------~->
(Continue reading)

Permalink | Reply | 1 comment |
headers
Gerald Bauer | 20 Jul 05:12
Picon
Favicon

Re: Miguel de Icaza (Mono Chief) and Brendan Eich (Mozilla Chief) On MS-XAML/Ava

Hello,

> Anyone care to enlighten me on this?  Or does Miguel and Brendan not 
> know what they're talking about?

  Ok let me try how I understand Miguel's and Brendan's comments. I
think Brendan's point is that there is no such thing as a well-defined
XAML format (e.g. like HTML). When you use MS-XAML you are always
bound to the underlying API. Of course, that's excactly what Microsoft
wants to get you locked in. Also the Avalon API is a monster on
purpose so you can't clone it without spending a billion or two.  

  The web architecture in contrast is different. A REST-style stresses
document formats instead of APIs and also stress universal human
readable addresses (e.g. URL) and so on. 

  Also one strength of HTML is that it is fault tolerant and thus you
can add attributes or tags as you please and they just get ignored. In
contrast, as far as I understand MS-XAML, if you use tags or
attributes that don't match the Windows API or Windows class structure
you will get compile time errors and thus Microsoft can break
compatibility as they please and gently force you to upgrade as they
do know. 

   - Gerald 

-------------------
Gerald Bauer

XUL Alliance | http://xul.sourceforge.net
(Continue reading)

Permalink | Reply | 0 comments |
headers
Gerald Bauer | 20 Jul 16:11
Picon
Favicon

Poll Update: Python (52%), JavaScript (11%), Groovy (10%), Perl (7%)

Hello,

  Just to let you know that the Richmond Post poll asking "What is
Your Scripting Language of Choice for XML UIs? will run for another week.

  If you haven't yet cast your vote, I urge you to rush to the
pollstation now before it's too late. 

  Here's the standing as of July 20th:

  * Python       64 votes (52%)
  * JavaScript	 13 votes (11%)
  * Groovy       12 votes (10%)
  * Perl          8 votes ( 7%)
  and so on

  You can find the pollstation online @
http://xul.sourceforge.net/post/2004/06/poll_what_is_your_scripting_language_of_choice_for_xml_uisxul.html

   - Gerald

-------------------
Gerald Bauer

XUL Alliance | http://xul.sourceforge.net  
United XAML  | http://xaml.sourceforge.net

Interested in hiring Gerald Bauer? Yes, I'm available. 
If you know of an opportunity, please contact me today.
(Continue reading)

Permalink | Reply | 0 comments |

Gmane