Seaside future on VW (Was vwnc] [Seaside] Seaside elements vs. HTML5 spec)

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Seaside future on VW (Was vwnc] [Seaside] Seaside elements vs. HTML5 spec)

Giorgio Ferraris
hi, 

this is just for putting the correct subject.. I hope someone on Cincom will reply. I suppose following Seaside release is not a lot of work, and should not slow down the work that is (eventually) done on the gui side...

bye

Giorgio

On Tue, Sep 27, 2011 at 1:34 PM, Boris Popov, DeepCove Labs <[hidden email]> wrote:

Yea, I get a sense of something similar, i.e. Seaside continues to be supported, but no longer the focus (last version published 152 days ago), which is typically driven either by product management or customer demand. I hesitate to ask whatever happened to Web Velocity and if lack of success on that front took some wind out of Cincom’s sails on the web front, where cool kids like Pharo and GemStone had gobbled up all of the attention recently.

 

-Boris

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of giorgio ferraris
Sent: Tuesday, September 27, 2011 7:28 AM
To: Boris Popov, DeepCove Labs
Cc: Visualworks Mailing List


Subject: Re: [vwnc] [Seaside] Seaside elements vs. HTML5 spec

 

Hi, Boris, 

 

yes, I supposed this, but this is a sad.

We (VW users) lost ground on the Gui side (see the amount of discussion about this ), and it was because of a strong move on the web (seaside) direction. And now Pharo is better for Seaside (To be fair, VW has much better infrastructure around and a  speediest  VM, at least  up to the time Eliot will close the gap) and Gui is enhancing very slowly. The grid control, for example  is still worst than the aragon one..

 

I supposed that Seaside was updated on a regular basis from the Cincom gui. Bani did a better job when he was doing the porting as a voluntary work...

 

ciao

 

Giorgio

On Tue, Sep 27, 2011 at 1:14 PM, Boris Popov, DeepCove Labs <[hidden email]> wrote:

One should be able to use Monticello tools in VisualWorks to get hold of most recent versions of Seaside, I’ve had some success in the past with that, although that was mostly by trial-and-error given how confusing the menu choices in the tool are/were.

 

-Boris

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of giorgio ferraris
Sent: Tuesday, September 27, 2011 7:08 AM
To: Visualworks Mailing List
Subject: Re: [vwnc] [Seaside] Seaside elements vs. HTML5 spec

 

Hi, 

 

it seems that Seaside was on top of priority for VW, and for this reason the work on the GUI side was delayed. And now we are late on the Gui work and late on the Seaside too!!

 

There are plans to officially follow the Seaside release on the VW side? (including the major add-on) (and without killing the Gui side, please...).

 

thanks

 

giorgio

On Mon, Sep 26, 2011 at 12:51 PM, David Buck <[hidden email]> wrote:

It seems that the version of Seaside I was basing this on was 3.0.3 which is the latest version ported to VisualWorks in the Cincom Public Store repository.  As you say, things have changed since and support for the HTML5 spec has improved.

Thanks,
David

Philippe Marschall wrote:

2011/9/25 David Buck [hidden email]:
  
The HTML5 spec is still changing and it's hard to keep up with the latest
changes.  Since I'm developing a Seaside course, I decided to go through the
current HTML5 spec (Editor's Draft 23 September 2011) and compare what
element tags are available in that spec versus the tags we support in
Seaside
    
Thanks for the effort and sharing.
 
  
(Seaside 3.0 - 8 released with VW7.8).
    
I don't know which Seaside version this is based on but the situation
in Seaside 3.0.6 is a bit different (see below). Most of the changes
probably come from Seaside 3.0.4.
 
  
In general, Seaside has
 
quite good support for HTML5.  Here are the differences I've found:
 
Note:  I'm simply offering this list as information for anyone interested.
 
 I needed to research this for the course and thought it would be good to
share the results.
 
The following tags are inconsistent between Seaside and the current version
of HTML5
  mark   (already reported)
 
Tags in HTML5 not supported by Seaside (some of these are poor style and
should use newer tags but are still supported in HTML):
  hgroup
    
#headingGroup there but missing tests
 
  
  figcaption
    
missing
 
  
  s
  i (should use emphasis)
  b (should use strong)
  u (shouldn't really use at all)
    
All of these are deprecated in HTML 4 in favor of CSS and intentionally missing.
 
  
  bdi
    
#bidirectional, there but missing tests, should probably be #biDirectional.
 
  
  bdo
    
missing indeed
 
  
  wbr
    
#lineBreakOpportunity, there but missing tests
 
  
  embed
    
#embed there but missing tests
 
  
  audio (interestingly, a WAAudioTag class exists with no call from the
canvas)
    
#audio, even has tests
 
 
  
  track
    
missing indeed
 
 
  
  map (WAImageMapTag class uses an anchor tag)
    
 
missing indeed
 
  
  area
    
 
missing indeed
 
  
  output
    
 
We have a WAOutputTag but it's never used :-(
 
  
  summary
    
missing indeed
 
  
The following tags are supported by Seaside but aren't in the current HTML5
spec (no problem keeping them for backward compatibility but perhaps they
should be marked as deprecated):
  rubyBase
  rubyBaseContainer
  rubyTextContainer
    
Indeed, they seem to be replaced by rt and rp
 
  
  datagrid
    
funny, yes missing
 
  
  acronym
    
"deprecated" but still in HTML 4, therefore likely to stay
 
  
  dialog
    
Indeed
 
  
  teletype
    
 
"deprecated" but still in HTML 4, therefore likely to stay
 
 
Cheers
Philippe
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
 
 
 
 
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1410 / Virus Database: 1520/3919 - Release Date: 09/25/11
 
 
  

 


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

 


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

 


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc



_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: Seaside future on VW (Was vwnc] [Seaside] Seaside elements vs. HTML5 spec)

Alan Knight-2
Well, our development cycles tend to be driven by our product release cycles. Seaside 3.0.3 is what was released when VisualWorks 7.8 went into code freeze. Having a current version of Seaside when we release is certainly on our agenda, keeping the public Store updated in between is less so.  It shouldn't be very much work at all to push an updated version into the public Store.

giorgio ferraris wrote:
hi, 

this is just for putting the correct subject.. I hope someone on Cincom will reply. I suppose following Seaside release is not a lot of work, and should not slow down the work that is (eventually) done on the gui side...

bye

Giorgio

On Tue, Sep 27, 2011 at 1:34 PM, Boris Popov, DeepCove Labs <[hidden email]> wrote:

Yea, I get a sense of something similar, i.e. Seaside continues to be supported, but no longer the focus (last version published 152 days ago), which is typically driven either by product management or customer demand. I hesitate to ask whatever happened to Web Velocity and if lack of success on that front took some wind out of Cincom’s sails on the web front, where cool kids like Pharo and GemStone had gobbled up all of the attention recently.

 

-Boris

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of giorgio ferraris
Sent: Tuesday, September 27, 2011 7:28 AM
To: Boris Popov, DeepCove Labs
Cc: Visualworks Mailing List


Subject: Re: [vwnc] [Seaside] Seaside elements vs. HTML5 spec

 

Hi, Boris, 

 

yes, I supposed this, but this is a sad.

We (VW users) lost ground on the Gui side (see the amount of discussion about this ), and it was because of a strong move on the web (seaside) direction. And now Pharo is better for Seaside (To be fair, VW has much better infrastructure around and a  speediest  VM, at least  up to the time Eliot will close the gap) and Gui is enhancing very slowly. The grid control, for example  is still worst than the aragon one..

 

I supposed that Seaside was updated on a regular basis from the Cincom gui. Bani did a better job when he was doing the porting as a voluntary work...

 

ciao

 

Giorgio

On Tue, Sep 27, 2011 at 1:14 PM, Boris Popov, DeepCove Labs <[hidden email]> wrote:

One should be able to use Monticello tools in VisualWorks to get hold of most recent versions of Seaside, I’ve had some success in the past with that, although that was mostly by trial-and-error given how confusing the menu choices in the tool are/were.

 

-Boris

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of giorgio ferraris
Sent: Tuesday, September 27, 2011 7:08 AM
To: Visualworks Mailing List
Subject: Re: [vwnc] [Seaside] Seaside elements vs. HTML5 spec

 

Hi, 

 

it seems that Seaside was on top of priority for VW, and for this reason the work on the GUI side was delayed. And now we are late on the Gui work and late on the Seaside too!!

 

There are plans to officially follow the Seaside release on the VW side? (including the major add-on) (and without killing the Gui side, please...).

 

thanks

 

giorgio

On Mon, Sep 26, 2011 at 12:51 PM, David Buck <[hidden email]> wrote:

It seems that the version of Seaside I was basing this on was 3.0.3 which is the latest version ported to VisualWorks in the Cincom Public Store repository.  As you say, things have changed since and support for the HTML5 spec has improved.

Thanks,
David

Philippe Marschall wrote:

2011/9/25 David Buck [hidden email]:
  
The HTML5 spec is still changing and it's hard to keep up with the latest
changes.  Since I'm developing a Seaside course, I decided to go through the
current HTML5 spec (Editor's Draft 23 September 2011) and compare what
element tags are available in that spec versus the tags we support in
Seaside
    
Thanks for the effort and sharing.
 
  
(Seaside 3.0 - 8 released with VW7.8).
    
I don't know which Seaside version this is based on but the situation
in Seaside 3.0.6 is a bit different (see below). Most of the changes
probably come from Seaside 3.0.4.
 
  
In general, Seaside has
 
quite good support for HTML5.  Here are the differences I've found:
 
Note:  I'm simply offering this list as information for anyone interested.
 
 I needed to research this for the course and thought it would be good to
share the results.
 
The following tags are inconsistent between Seaside and the current version
of HTML5
  mark   (already reported)
 
Tags in HTML5 not supported by Seaside (some of these are poor style and
should use newer tags but are still supported in HTML):
  hgroup
    
#headingGroup there but missing tests
 
  
  figcaption
    
missing
 
  
  s
  i (should use emphasis)
  b (should use strong)
  u (shouldn't really use at all)
    
All of these are deprecated in HTML 4 in favor of CSS and intentionally missing.
 
  
  bdi
    
#bidirectional, there but missing tests, should probably be #biDirectional.
 
  
  bdo
    
missing indeed
 
  
  wbr
    
#lineBreakOpportunity, there but missing tests
 
  
  embed
    
#embed there but missing tests
 
  
  audio (interestingly, a WAAudioTag class exists with no call from the
canvas)
    
#audio, even has tests
 
 
  
  track
    
missing indeed
 
 
  
  map (WAImageMapTag class uses an anchor tag)
    
 
missing indeed
 
  
  area
    
 
missing indeed
 
  
  output
    
 
We have a WAOutputTag but it's never used :-(
 
  
  summary
    
missing indeed
 
  
The following tags are supported by Seaside but aren't in the current HTML5
spec (no problem keeping them for backward compatibility but perhaps they
should be marked as deprecated):
  rubyBase
  rubyBaseContainer
  rubyTextContainer
    
Indeed, they seem to be replaced by rt and rp
 
  
  datagrid
    
funny, yes missing
 
  
  acronym
    
"deprecated" but still in HTML 4, therefore likely to stay
 
  
  dialog
    
Indeed
 
  
  teletype
    
 
"deprecated" but still in HTML 4, therefore likely to stay
 
 
Cheers
Philippe
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
 
 
 
 
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1410 / Virus Database: 1520/3919 - Release Date: 09/25/11
 
 
  

 


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

 


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

 


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Reply | Threaded
Open this post in threaded view
|

Re: Seaside future on VW (Was vwnc] [Seaside] Seaside elements vs. HTML5 spec)

Boris Popov, DeepCove Labs (SNN)

Alan,

 

I seem to recall asking about the proper process involving Monticello tools back at ESUG’10 - try as I may, I never quite figured out the difference between the various options. I’m sure if folks knew how to do it, you could get a fair bit more help from community when it comes to publishing current versions into PR between releases.

 

-Boris

 

From: Alan Knight [mailto:[hidden email]]
Sent: Tuesday, September 27, 2011 9:20 AM
To: giorgio ferraris
Cc: Boris Popov, DeepCove Labs; Visualworks Mailing List
Subject: Re: [vwnc] Seaside future on VW (Was vwnc] [Seaside] Seaside elements vs. HTML5 spec)

 

Well, our development cycles tend to be driven by our product release cycles. Seaside 3.0.3 is what was released when VisualWorks 7.8 went into code freeze. Having a current version of Seaside when we release is certainly on our agenda, keeping the public Store updated in between is less so.  It shouldn't be very much work at all to push an updated version into the public Store.

giorgio ferraris wrote:

hi, 

 

this is just for putting the correct subject.. I hope someone on Cincom will reply. I suppose following Seaside release is not a lot of work, and should not slow down the work that is (eventually) done on the gui side...

 

bye

 

Giorgio

On Tue, Sep 27, 2011 at 1:34 PM, Boris Popov, DeepCove Labs <[hidden email]> wrote:

Yea, I get a sense of something similar, i.e. Seaside continues to be supported, but no longer the focus (last version published 152 days ago), which is typically driven either by product management or customer demand. I hesitate to ask whatever happened to Web Velocity and if lack of success on that front took some wind out of Cincom’s sails on the web front, where cool kids like Pharo and GemStone had gobbled up all of the attention recently.

 

-Boris

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of giorgio ferraris
Sent: Tuesday, September 27, 2011 7:28 AM
To: Boris Popov, DeepCove Labs
Cc: Visualworks Mailing List


Subject: Re: [vwnc] [Seaside] Seaside elements vs. HTML5 spec

 

Hi, Boris, 

 

yes, I supposed this, but this is a sad.

We (VW users) lost ground on the Gui side (see the amount of discussion about this ), and it was because of a strong move on the web (seaside) direction. And now Pharo is better for Seaside (To be fair, VW has much better infrastructure around and a  speediest  VM, at least  up to the time Eliot will close the gap) and Gui is enhancing very slowly. The grid control, for example  is still worst than the aragon one..

 

I supposed that Seaside was updated on a regular basis from the Cincom gui. Bani did a better job when he was doing the porting as a voluntary work...

 

ciao

 

Giorgio

On Tue, Sep 27, 2011 at 1:14 PM, Boris Popov, DeepCove Labs <[hidden email]> wrote:

One should be able to use Monticello tools in VisualWorks to get hold of most recent versions of Seaside, I’ve had some success in the past with that, although that was mostly by trial-and-error given how confusing the menu choices in the tool are/were.

 

-Boris

 

From: [hidden email] [mailto:[hidden email]] On Behalf Of giorgio ferraris
Sent: Tuesday, September 27, 2011 7:08 AM
To: Visualworks Mailing List
Subject: Re: [vwnc] [Seaside] Seaside elements vs. HTML5 spec

 

Hi, 

 

it seems that Seaside was on top of priority for VW, and for this reason the work on the GUI side was delayed. And now we are late on the Gui work and late on the Seaside too!!

 

There are plans to officially follow the Seaside release on the VW side? (including the major add-on) (and without killing the Gui side, please...).

 

thanks

 

giorgio

On Mon, Sep 26, 2011 at 12:51 PM, David Buck <[hidden email]> wrote:

It seems that the version of Seaside I was basing this on was 3.0.3 which is the latest version ported to VisualWorks in the Cincom Public Store repository.  As you say, things have changed since and support for the HTML5 spec has improved.

Thanks,
David

Philippe Marschall wrote:

2011/9/25 David Buck [hidden email]:
  
The HTML5 spec is still changing and it's hard to keep up with the latest
changes.  Since I'm developing a Seaside course, I decided to go through the
current HTML5 spec (Editor's Draft 23 September 2011) and compare what
element tags are available in that spec versus the tags we support in
Seaside
    
Thanks for the effort and sharing.
 
  
(Seaside 3.0 - 8 released with VW7.8).
    
I don't know which Seaside version this is based on but the situation
in Seaside 3.0.6 is a bit different (see below). Most of the changes
probably come from Seaside 3.0.4.
 
  
In general, Seaside has
 
quite good support for HTML5.  Here are the differences I've found:
 
Note:  I'm simply offering this list as information for anyone interested.
 
 I needed to research this for the course and thought it would be good to
share the results.
 
The following tags are inconsistent between Seaside and the current version
of HTML5
  mark   (already reported)
 
Tags in HTML5 not supported by Seaside (some of these are poor style and
should use newer tags but are still supported in HTML):
  hgroup
    
#headingGroup there but missing tests
 
  
  figcaption
    
missing
 
  
  s
  i (should use emphasis)
  b (should use strong)
  u (shouldn't really use at all)
    
All of these are deprecated in HTML 4 in favor of CSS and intentionally missing.
 
  
  bdi
    
#bidirectional, there but missing tests, should probably be #biDirectional.
 
  
  bdo
    
missing indeed
 
  
  wbr
    
#lineBreakOpportunity, there but missing tests
 
  
  embed
    
#embed there but missing tests
 
  
  audio (interestingly, a WAAudioTag class exists with no call from the
canvas)
    
#audio, even has tests
 
 
  
  track
    
missing indeed
 
 
  
  map (WAImageMapTag class uses an anchor tag)
    
 
missing indeed
 
  
  area
    
 
missing indeed
 
  
  output
    
 
We have a WAOutputTag but it's never used :-(
 
  
  summary
    
missing indeed
 
  
The following tags are supported by Seaside but aren't in the current HTML5
spec (no problem keeping them for backward compatibility but perhaps they
should be marked as deprecated):
  rubyBase
  rubyBaseContainer
  rubyTextContainer
    
Indeed, they seem to be replaced by rt and rp
 
  
  datagrid
    
funny, yes missing
 
  
  acronym
    
"deprecated" but still in HTML 4, therefore likely to stay
 
  
  dialog
    
Indeed
 
  
  teletype
    
 
"deprecated" but still in HTML 4, therefore likely to stay
 
 
Cheers
Philippe
_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside
 
 
 
 
-----
No virus found in this message.
Checked by AVG - www.avg.com
Version: 10.0.1410 / Virus Database: 1520/3919 - Release Date: 09/25/11
 
 
  

 


_______________________________________________
seaside mailing list
[hidden email]
http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside

 


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

 


_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

 

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc

_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc