<?xml version="1.0" encoding="UTF-8"?>
<rdf:RDF xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns="http://purl.org/rss/1.0/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:admin="http://webns.net/mvcb/">
  <channel rdf:about="http://blog.gmane.org/gmane.comp.ide.eclipse.orion.devel">
    <title>gmane.comp.ide.eclipse.orion.devel</title>
    <link>http://blog.gmane.org/gmane.comp.ide.eclipse.orion.devel</link>
    <description/>
    <syn:updatePeriod>hourly</syn:updatePeriod>
    <syn:updateFrequency>1</syn:updateFrequency>
    <syn:updateBase>1901-01-01T00:00+00:00</syn:updateBase>
    <items>
      <rdf:Seq>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1912"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1907"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1904"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1903"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1900"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1899"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1898"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1897"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1896"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1895"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1894"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1893"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1892"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1891"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1890"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1886"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1885"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1884"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1878"/>
        <rdf:li rdf:resource="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1877"/>
      </rdf:Seq>
    </items>
    <image rdf:resource="http://gmane.org/img/gmane-25t.png"/>
    <textinput rdf:resource=""/>
  </channel>
  <image rdf:about="http://gmane.org/img/gmane-25t.png">
    <title>Gmane</title>
    <url>http://gmane.org/img/gmane-25t.png</url>
    <link>http://gmane.org</link>
  </image>
  <item rdf:about="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1912">
    <title>[orion-dev] Web Accessibility Tip of the Day: Tip #5</title>
    <link>http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1912</link>
    <description>&lt;pre&gt;Tip #5: More on role="application", role="document" and 
role="presentation"

If you are creating a complex custom control and you have implemented and 
tested its keyboard interaction,
and then you try a screen reader and find that the screen reader consumes 
arrow keys or other keys that your control needs for interaction...
then you *may* need to set role="application" on the element containing 
your custom control.

Besides being a landmark role, "application" tells the screen reader to 
pass user keystrokes through,
so that your javascript has access to them.

Many screen readers have 2 modes of operation: "document/browse mode" and 
"forms/focus mode".
In browse mode, the screen reader consumes keystrokes like arrow keys and 
letter keys so that the user can use them to navigate through the 
document's content.
In forms mode, the screen reader passes many of these keys through to the 
browser and the javascript.
Forms mode is entered automatically when an interactive native HTML 
element or ARIA-enabled element gets focus.

CAVEAT EMPTOR: role="application" is a last resort. First, try to avoid it 
by considering the following:

- Make sure that your custom control is using the most semantically 
appropriate role.
  Is it very much like a tree? Then using role="tree" tells the screen 
reader which keys you (probably) need and it will pass those keys through.

- If your custom control contains non-focusable child elements that a 
screen reader user might typically use arrow keys to navigate to,
  for example table cells, then you may also need to turn off the 
semantics of these child elements by using role="presentation".
  (More on role="presentation" in another tip).

- Note that if you use role="application", then you will not get any free 
keyboard interaction behavior when a screen reader is running,
  so you need to handle all keystrokes yourself. You may be able to set 
role="document" on certain child elements of your custom control
  to regain the free navigation behavior for those child elements.
 
Also, before using role="application", read through these specs and 
relevant articles:
http://www.w3.org/WAI/PF/aria-practices/#kbd_layout_impact
http://rawgithub.com/w3c/aria-in-html/master/index.html#using-aria-role-application
http://www.marcozehe.de/2012/02/06/if-you-use-the-wai-aria-role-application-please-do-so-wisely/
http://www.netmagazine.com/features/aria-s-application-role

Car&lt;/pre&gt;</description>
    <dc:creator>Carolyn MacLeod</dc:creator>
    <dc:date>2013-05-23T15:00:39</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1907">
    <title>[orion-dev] Introduction and question getting the source bundles for orion server dependencies</title>
    <link>http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1907</link>
    <description>&lt;pre&gt;Hi Team,

I would like to introduce myself as a new participant on the Orion 
Project. I have joined the team of Orion developers here in Kanata, 
Ontario, Canada. Some of you may recognize me from my Eclipse background 
on various modeling projects like GMF and GEF, but most of my time the 
last few years have been spent on various products at IBM Rational 
Software.

I have a question about setting up a development environment for debugging 
the Orion server. I was able to follow 
http://wiki.eclipse.org/Orion/Getting_the_source#Local_computer_with_Eclipse_IDE 
and get a local self host with the client and server code running on my 
Linux machine, but I am having a problem getting the source bundles for 
the dependencies (the jetty source, javax.* source, org.apache.* source, 
etc, etc.). Is there an easy way to get the source bundles for all the 
dependencies?

Cheers...
Anthony
&lt;/pre&gt;</description>
    <dc:creator>Anthony Hunter</dc:creator>
    <dc:date>2013-05-22T19:05:17</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1904">
    <title>[orion-dev] Does Orion check for the protocol when cloning from agit repo</title>
    <link>http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1904</link>
    <description>&lt;pre&gt;Hi,

While playing with orions "clone from git repository" functionality I found out my local orion instance clones from URLs like 'file:/home/user/dondalfi'. With that I get access to all git repos hosted on the machine running the orion server. That's a security hole, or? Is it only that my local orion which can do that or  is it also true for orionhub.org? 

Ciao
  Chris

&lt;/pre&gt;</description>
    <dc:creator>Halstrick, Christian</dc:creator>
    <dc:date>2013-05-16T12:40:21</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1903">
    <title>[orion-dev] Web Accessibility Tip of the Day: Tip #4</title>
    <link>http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1903</link>
    <description>&lt;pre&gt;Tip #4: Use HTML5 section elements and ARIA landmark roles to semantically 
organize pages.

HTML5 introduced 8 semantic sectioning elements [1] to help define areas 
of a web page:
&amp;lt;header&amp;gt;, &amp;lt;nav&amp;gt;, &amp;lt;section&amp;gt;, &amp;lt;article&amp;gt;, &amp;lt;aside&amp;gt;, &amp;lt;figcaption&amp;gt;, &amp;lt;figure&amp;gt;, 
&amp;lt;footer&amp;gt;, (and new in 5.1 &amp;lt;main&amp;gt;)
Some of these are now supported by the major browsers and screen readers.

ARIA has 8 landmark roles [2] to help define semantic areas of a web page:
application, banner, complementary, contentinfo, form, main, navigation, 
search
These are all supported by the major browsers and screen readers.

Screen reader users can list - and navigate to - landmark regions; and the 
name and type of landmark is announced when the user enters and leaves it.
Some browsers support landmark navigation without a screen reader, either 
through a setting or a plugin.

Be sure to give your landmark regions a name, either with 
aria-label="Invisible name" or aria-labelledby="visible_name_element_id".
Usually the best visible_name_element for a landmark region is a &amp;lt;heading&amp;gt; 
or &amp;lt;h1&amp;gt;.

Some of the section elements and landmark roles overlap, and (as of this 
writing) doubling these up will give best results.

Here are some samples:
&amp;lt;main id="main"&amp;gt; for the main content of the page,
&amp;lt;header role="banner"&amp;gt; for the masthead of the site,
&amp;lt;nav role="navigation"&amp;gt; for each list of navigation links,
&amp;lt;form role="search"&amp;gt; for a search form,
&amp;lt;form role="form"&amp;gt; for a form,
&amp;lt;aside role="complementary"&amp;gt; for related information in a sidebar,
&amp;lt;footer role="contentinfo"&amp;gt; for copyright and contact info at the bottom,
&amp;lt;article role="article"&amp;gt; for an article,
&amp;lt;div role="application"&amp;gt; for a complex custom control (more on this in tip 
#5),
&amp;lt;section role="region"&amp;gt; for a region that doesn't have any of the above 
semantics.

Here are 7 steps to guide you through the thought process for breaking 
your page into semantic regions:
http://www.w3.org/WAI/PF/aria-practices/#kbd_layout_landmarks

Car

[1] http://www.w3schools.com/html/html5_semantic_elements.asp
[2] http://www.w3.org/WAI/PF/aria/roles#landmark_roles&lt;/pre&gt;</description>
    <dc:creator>Carolyn MacLeod</dc:creator>
    <dc:date>2013-05-16T06:07:55</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1900">
    <title>[orion-dev] Fw: [orion-releng] Orion Build : I20130514-2230</title>
    <link>http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1900</link>
    <description>&lt;pre&gt;

Deployed to orion.eclipse.org - A message about some changes from Libing:
                                                                                                    
 Please go to the settings-&amp;gt; git settings to reset the git user name and email. The previous        
 information stored in the user profile is no longer used                                           
                                                                                                    




Ken Walker
Co-Lead Eclipse Orion Project | Tools for the Web, On the Web
http://orionhub.org | http://wiki.eclipse.org/Orion
&amp;lt; at &amp;gt;kwalker | &amp;lt; at &amp;gt;orionhub



----- Forwarded by Ken Walker/Ottawa/IBM on 2013/05/15 10:00 AM -----
                                                                                                                                                      
  From:       e4Build-j9T/66MeVpFAfugRpC6u6w&amp;lt; at &amp;gt;public.gmane.org                                                                                                                     
                                                                                                                                                      
  To:         orion-releng-j9T/66MeVpFAfugRpC6u6w&amp;lt; at &amp;gt;public.gmane.org,                                                                                                               
                                                                                                                                                      
  Date:       2013/05/14 11:28 PM                                                                                                                     
                                                                                                                                                      
  Subject:    [orion-releng] Orion Build : I20130514-2230                                                                                             
                                                                                                                                                      
  Sent by:    orion-releng-bounces-j9T/66MeVpFAfugRpC6u6w&amp;lt; at &amp;gt;public.gmane.org                                                                                                        
                                                                                                                                                      





See here for the build results: I20130514-2230
The build contains the following changes:
+ Bug 399023 - CBI (Maven/Tycho) based build for Orion (NEW)
+ Bug 406810 - [sidebar] Renaming/deleting current file in sidebar
navigator causes trouble (FIXED)
+ Bug 407669 - Trying to save a deleted file pops up strange message.
(FIXED)
+ Bug 408053 - Project copy/move fails with server context path (FIXED)
+ Bug 408065 - Server: Cloning a git repository to use the user name and
email passed from the client side. (FIXED)

The following projects have changed:
org.eclipse.orion.client.core
org.eclipse.orion.client.editor
org.eclipse.orion.client.git
org.eclipse.orion.client.ui
org.eclipse.orion.client.users
org.eclipse.orion.server.core
org.eclipse.orion.server.git
org.eclipse.orion.server.servlets
org.eclipse.orion.server.tests
pom.xml

Test Results
                                                                         
 Test                       # Tests Failure Errors Success Rate   Time   
                                       s                                 
                                                                         
  JS Tests - Chrome 12       1478      0      0      100.00%     38.192  
                                                                         
  JS Tests - Firefox 17.0    1476      0      0      100.00%     29.007  
                                                                         
  JS Tests - Chrome Windows   DNF                                        
                                                                         
  JUnit Tests: Server Tests   313      0      3       99.04%    257.465  
                                                                         



_______________________________________________
orion-releng mailing list
orion-releng-j9T/66MeVpFAfugRpC6u6w&amp;lt; at &amp;gt;public.gmane.org
http://dev.eclipse.org/mailman/listinfo/orion-releng
&lt;/pre&gt;</description>
    <dc:creator>Ken Walker</dc:creator>
    <dc:date>2013-05-15T14:02:19</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1899">
    <title>[orion-dev] LotD: Polymer</title>
    <link>http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1899</link>
    <description>&lt;pre&gt;
"Polymer - A new web framework by Google designed to leverage the evolving
web platform."
.     http://polymer-project.appspot.com

McQ.
.&lt;/pre&gt;</description>
    <dc:creator>Mike Wilson</dc:creator>
    <dc:date>2013-05-15T14:00:44</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1898">
    <title>[orion-dev] Web Accessibility Tip of the Day: Tip #3</title>
    <link>http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1898</link>
    <description>&lt;pre&gt;Tip #3: Every focusable element needs a name.

When an element gets focus, screen readers ask the browser for the 
element's name (aka label) so that it can be spoken aloud or rendered on a 
Braille display.
You can specify an element's name in several ways:
1) If the element has innerHTML and if it's a type of element that can use 
content as its name, i.e. &amp;lt;button&amp;gt;Name&amp;lt;/button&amp;gt;, then give it a good name 
and you're done.
2) If there's a visible element that can be used as a label, then use the 
aria-labelledby attribute to use the text from the other element for the 
name (you can actually concatenate text from multiple elements).
3) If there's no visible element to use as a label, you can provide a name 
string with aria-label.
4) Provide &amp;lt;label&amp;gt; for &amp;lt;input&amp;gt; elements.
5) Provide alt text if the element is an &amp;lt;img&amp;gt; or other object that 
supports alt.
6) Optionally provide a title.

For grins, here is the somewhat complex algorithmic advice given to "User 
Agents" (aka browsers) for computing the name of an element:
http://www.w3.org/WAI/PF/aria-implementation/Overview.html#mapping_additional_nd_te

Car&lt;/pre&gt;</description>
    <dc:creator>Carolyn MacLeod</dc:creator>
    <dc:date>2013-05-15T07:02:31</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1897">
    <title>[orion-dev] Web Accessibility Tip of the Day: Tip #2</title>
    <link>http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1897</link>
    <description>&lt;pre&gt;Tip #2: Adding or augmenting the semantics of HTML elements with WAI-ARIA*

You can fine-tune the semantics of HTML elements by adding ARIA roles, 
states, and properties in order to make them more accessible.
The ARIA Authoring Practices "Design Patterns" table specifies the 
expected keyboard interaction and ARIA roles, states, and properties you 
should use to implement many common design patterns:
http://www.w3.org/WAI/PF/aria-practices/#aria_ex

Take a look at the list of design pattern names (37 as of this writing) 
and then look at a couple of them in detail, for example, menubutton and 
menu:
http://www.w3.org/WAI/PF/aria-practices/#menubutton
http://www.w3.org/WAI/PF/aria-practices/#menu

* WAI-ARIA: Web Accessibility Initiative - Accessible Rich Internet 
Applications
&lt;/pre&gt;</description>
    <dc:creator>Carolyn MacLeod</dc:creator>
    <dc:date>2013-05-14T03:59:58</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1896">
    <title>[orion-dev] Web Accessibility Tip of the Day: Tip #1</title>
    <link>http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1896</link>
    <description>&lt;pre&gt;Tip #1: Whenever possible, use semantically appropriate "native" HTML 
elements instead of &amp;lt;div&amp;gt; and &amp;lt;span&amp;gt;.
You can style them to get the look you want, and augment them to get the 
semantics and behavior you need.
As a bonus, this is usually a lot less work!

For example, use &amp;lt;button&amp;gt; instead of... &amp;lt;div role="button" tabindex="0"&amp;gt; 
and changing styles onmouseover/out/down/up and 
onfocus/blur/keydown/keyup.

Even if the native semantics are only "close", it is usually better to 
start native and augment (as long as you don't *change* any behavior).
For example, start with &amp;lt;ul&amp;gt; and &amp;lt;li&amp;gt; for a tree and its tree items, or a 
menu and its menu items.
This way, even if you do nothing else, a screen reader user will know that 
these items are grouped in a logical manner.
(Of course, you have to keep your DOM consistent too, i.e. use nested &amp;lt;ul&amp;gt; 
for new branches of the tree instead of using CSS to move them into 
place).

Take a minute to scroll through the Table of Contents for section 4 "The 
elements of HTML" in the draft HTML5.1 spec:
http://www.w3.org/html/wg/drafts/html/master/ and search (Ctrl+F) for "the 
elements".

For more on the semantics of HTML elements and how to augment them with 
ARIA, see the next Web Accessibility Tip of the Day.

Car&lt;/pre&gt;</description>
    <dc:creator>Carolyn MacLeod</dc:creator>
    <dc:date>2013-05-10T20:18:23</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1895">
    <title>[orion-dev] Git blame</title>
    <link>http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1895</link>
    <description>&lt;pre&gt;Hi my name is Chris Conley I'm a student at Brock University in Canada, 
and I know I'm kind of doing this backwards but I have applied for GSoC 
at the last minute for the Git Blame project and wanted to introduce 
myself. I guess this is geared towards Ken Walker since he would be the 
possible mentor. I was previously working on UCOSP with Andrew Ross on 
CBI, and I know Ken that you had 2 students working with you: Cameron 
and Sarah, so I have heard a lot about you. I was discussing doing a 
proposal earlier with Andrew in a different area of Eclipse(CBI) but it 
fell through at the last minute because of his crazy schedule, so I 
wrote a proposal for the Git Blame idea during the middle of the 
nightThursday, so I didn't have much time to introduce myself before the 
due date. I have been subscribed to the Orion mailing list for a few 
months just laying low since I thought I would apply through CBI and I 
saw that no one has mentioned this project, plus I think I could do some 
really cool and useful things with it. I know I've kind of done this 
backwards, proposal than introduction, so the slim chance of acceptance 
could be slimmer but I had to try! Thanks for your time.

Chris

&lt;/pre&gt;</description>
    <dc:creator>Chris Conley</dc:creator>
    <dc:date>2013-05-05T09:05:08</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1894">
    <title>[orion-dev] Fw: [orion-releng] Orion Build : I20130502-1622</title>
    <link>http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1894</link>
    <description>&lt;pre&gt;

Search is now available in the hamburger pane after you reload the plugins.

Ken Walker
Co-Lead Eclipse Orion Project | Tools for the Web, On the Web
http://orionhub.org | http://wiki.eclipse.org/Orion
&amp;lt; at &amp;gt;kwalker | &amp;lt; at &amp;gt;orionhub



----- Forwarded by Ken Walker/Ottawa/IBM on 2013/05/02 05:24 PM -----
|------------&amp;gt;
| From:      |
|------------&amp;gt;
  &amp;gt;--------------------------------------------------------------------------------------------------------------------------------------------------|
  |e4Build-j9T/66MeVpFAfugRpC6u6w&amp;lt; at &amp;gt;public.gmane.org                                                                                                                               |
  &amp;gt;--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------&amp;gt;
| To:        |
|------------&amp;gt;
  &amp;gt;--------------------------------------------------------------------------------------------------------------------------------------------------|
  |orion-releng-j9T/66MeVpFAfugRpC6u6w&amp;lt; at &amp;gt;public.gmane.org,                                                                                                                         |
  &amp;gt;--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------&amp;gt;
| Date:      |
|------------&amp;gt;
  &amp;gt;--------------------------------------------------------------------------------------------------------------------------------------------------|
  |2013/05/02 05:18 PM                                                                                                                               |
  &amp;gt;--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------&amp;gt;
| Subject:   |
|------------&amp;gt;
  &amp;gt;--------------------------------------------------------------------------------------------------------------------------------------------------|
  |[orion-releng] Orion Build : I20130502-1622                                                                                                       |
  &amp;gt;--------------------------------------------------------------------------------------------------------------------------------------------------|
|------------&amp;gt;
| Sent by:   |
|------------&amp;gt;
  &amp;gt;--------------------------------------------------------------------------------------------------------------------------------------------------|
  |orion-releng-bounces-j9T/66MeVpFAfugRpC6u6w&amp;lt; at &amp;gt;public.gmane.org                                                                                                                  |
  &amp;gt;--------------------------------------------------------------------------------------------------------------------------------------------------|





See here for the build results: I20130502-1622
The build contains the following changes:

The following projects have changed:
org.eclipse.orion.client.editor
org.eclipse.orion.client.ui

Test Results
                                                                         
 Test                       # Tests Failure Errors Success Rate   Time   
                                       s                                 
                                                                         
  JS Tests - Chrome 12       1478      0      0      100.00%     38.189  
                                                                         
  JS Tests - Firefox 17.0    1476      0      0      100.00%     29.175  
                                                                         
  JS Tests - Chrome Windows   DNF                                        
                                                                         
  JUnit Tests: Server Tests   308      0      1       99.68%    261.288  
                                                                         



_______________________________________________
orion-releng mailing list
orion-releng-j9T/66MeVpFAfugRpC6u6w&amp;lt; at &amp;gt;public.gmane.org
http://dev.eclipse.org/mailman/listinfo/orion-releng
&lt;/pre&gt;</description>
    <dc:creator>Ken Walker</dc:creator>
    <dc:date>2013-05-02T21:26:01</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1893">
    <title>[orion-dev] GSoC 2013 - Requesting few clarifications about the project - App Store for Orion Plugins</title>
    <link>http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1893</link>
    <description>&lt;pre&gt;Hello,
I am Alim, a master's student from Bangladesh. I have known about this
project from the Eclipse's Ideas page for Google Summer of Code (GSoC)
2013. I am interested in working on the project as a part of the GSoC
program. I have already read the Mailing list archives for gathering detail
information about the project and have almost prepared the project
proposal. However, I am stuck with a few points and thus can not complete
it.

In one of the replies, Ken has said - " Enhancements include allowing
multiple destination plugin sites". What I have came to understand by
reading this line is that plugin developers will expose their plugins via
web services. There will be an Enterprise Service Bus (ESB) which will keep
track of those services and the "getplugins()" extension will communicate
with the ESB. Am I thinking in a complicated way? Please do clarify.

In the same reply Ken has also mentioned - "allowing groups of plugins to
be installed together vs. individually". Does it mean that the plugins will
be associated with some metadata and based on that suggestions will be
provided to install the related plugins during the installation of a single
one? Or does it indicate that user can pick a set of plugins by putting
tick marks on them and then install all at once? Or both?

Moreover, I need clarifications on the following points-

   - Do the plugins are associated with metadata such as category, based on
   which filters can be applied?
   - Can the student get a chance to work with the server side technologies
   or s/he has to work only with HTML, CSS and JavaScript?
   - If the student can get a chance to work on the server side then what
   will be the technology (like J2EE) that s/he has to work with?

I am hoping for a reply soon. Thank you.


Alim Ul Gias

Master's Student

Institute of Information Technology, University of Dhaka
Dhaka, Bangladesh
&lt;/pre&gt;</description>
    <dc:creator>Alim Ul Gias</dc:creator>
    <dc:date>2013-05-01T11:51:11</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1892">
    <title>[orion-dev] GSoC 2013 - Requesting few clarifications about the project - App Store for Orion Plugins</title>
    <link>http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1892</link>
    <description>&lt;pre&gt;Dear Ken,
I am Alim, a master's student from Bangladesh. I have known about this
project from the Eclipse's Ideas page for Google Summer of Code (GSoC)
2013. I am interested in working on the project as a part of the GSoC
program. I have already read the Mailing list archives for gathering detail
information about the project and have almost prepared the project
proposal. However, I am stuck with a few points and thus can not complete
it.

In one of your replies, you have said - " Enhancements include allowing
multiple destination plugin sites". What I have came to understand by
reading this line is that plugin developers will expose their plugins via
web services. There will be an Enterprise Service Bus (ESB) which will keep
track of those services and the "getplugins()" extension will communicate
with the ESB. Am I thinking in a complicated way? Please do clarify.

In the same reply you have also mentioned - "allowing groups of plugins to
be installed together vs. individually". Does it mean that the plugins will
be associated with some metadata and based on that suggestions will be
provided to install the related plugins during the installation of a single
one? Or does it indicate that user can pick a set of plugins by putting
tick marks on them and then install all at once? Or both?

Moreover, I need clarifications on the following points-

   - Do the plugins are associated with metadata such as category, based on
   which filters can be applied?
   - Can the student get a chance to work with the server side technologies
   or s/he has to work only with HTML, CSS and JavaScript?
   - If the student can get a chance to work on the server side then what
   will be the technology (like J2EE) that s/he has to work with?

I have seen that you are replying all those emails related to Orion App
Store for GSoC and thus hoping that you will also reply in this case.


Best Regards,

Alim Ul Gias

Master's Student

Institute of Information Technology, University of Dhaka
Dhaka, Bangladesh
&lt;/pre&gt;</description>
    <dc:creator>Alim Ul Gias</dc:creator>
    <dc:date>2013-04-30T20:39:23</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1891">
    <title>[orion-dev] Welcome Bogdan Gheorghe as an Orion Committer!</title>
    <link>http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1891</link>
    <description>&lt;pre&gt;
Bogdan has been working on some great new editor features and is really
becoming proficient with the code there.  3.0 will have some great features
contributed by Bogdan and Silenio (Bogdenio).

Welcome!

Ken Walker
Co-Lead Eclipse Orion Project | Tools for the Web, On the Web
http://orionhub.org | http://wiki.eclipse.org/Orion
&amp;lt; at &amp;gt;kwalker | &amp;lt; at &amp;gt;orionhub

&lt;/pre&gt;</description>
    <dc:creator>Ken Walker</dc:creator>
    <dc:date>2013-04-29T14:03:05</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1890">
    <title>[orion-dev] Welcome Bogdan Gheorghe as a new eclipse.orion Committer</title>
    <link>http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1890</link>
    <description>&lt;pre&gt;eclipse.orion Committers,
This automatically generated message marks the completion of all the legal
paperwork and webmaster provisioning for Bogdan Gheorghe. Bogdan Gheorghe
is a new full Committer on the eclipse.orion project.

Welcome!
&lt;/pre&gt;</description>
    <dc:creator>portal on behalf of Simon Kaegi</dc:creator>
    <dc:date>2013-04-29T13:54:01</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1886">
    <title>[orion-dev] Committer vote for Bogdan Gheorghe has been approved bythe PMC</title>
    <link>http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1886</link>
    <description>&lt;pre&gt;eclipse.orion Committers,
This automatically generated message marks the PMC's approval of the vote
for Bogdan Gheorghe's full Committer status on the eclipse.orion project.
The next step is for the project lead to return to the portal and fill in
the VCS package and employer information for Bogdan Gheorghe.

The PMC's comments were: Welcome!

If you have any questions, please do not hesitate to contact your project
lead, PMC member, or the EMO &amp;lt;emo-j9T/66MeVpFAfugRpC6u6w&amp;lt; at &amp;gt;public.gmane.org&amp;gt;

&lt;/pre&gt;</description>
    <dc:creator>portal on behalf of portal-noreply</dc:creator>
    <dc:date>2013-04-26T06:52:01</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1885">
    <title>[orion-dev] Committer vote for Bogdan Gheorghe has concludedsuccessfully</title>
    <link>http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1885</link>
    <description>&lt;pre&gt;eclipse.orion Committers,
This automatically generated message marks the successful completion of
voting for Bogdan Gheorghe to receive full Committer status on the
eclipse.orion project. The next step is for the PMC to approve this vote,
followed by the EMO processing the paperwork and provisioning the account.

Vote summary: 11/0/0 with 11 not voting 
  +1  John Arthorne
   ?  Boris Bokowski
   ?  Szymon Brandys
  +1  Andrew Clement
   ?  Kris De Volder
   ?  Andrew Eisenberg
  +1  Grant Gayed
   ?  Felipe Heidrich
   ?  Nayna Jain
   ?  Malgorzata Janczarska
  +1  Simon Kaegi
   ?  Max Li
  +1  Mark Macdonald
  +1  Anton McConville
   ?  Susan McCourt
  +1  Andrew Niefer
  +1  Silenio Quarti
   ?  Mihai Sucan
  +1  Ken Walker
  +1  Libing Wang
  +1  Mike Wilson
   ?  Tomasz Zarna

If you have any questions, please do not hesitate to contact your project
lead, PMC member, or the EMO &amp;lt;emo-j9T/66MeVpFAfugRpC6u6w&amp;lt; at &amp;gt;public.gmane.org&amp;gt;

&lt;/pre&gt;</description>
    <dc:creator>portal on behalf of</dc:creator>
    <dc:date>2013-04-26T04:01:02</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1884">
    <title>[orion-dev] Meeting minutes April 25th,2013 - Sorry for lack of Eclipse Bridge</title>
    <link>http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1884</link>
    <description>&lt;pre&gt;
http://wiki.eclipse.org/Orion/Meeting_minutes/20130425

We have been having issues with the Eclipse VOIP Bridge on several calls.
Garbled voices, and today we could not call in at all.  Szymon could but we
just got a busy wait.

We might have to look into alternatives like a Google hangout but that will
involve us finding a good speaker/microphone setup for the Ottawa team.

Ken Walker
Co-Lead Eclipse Orion Project | Tools for the Web, On the Web
http://orionhub.org | http://wiki.eclipse.org/Orion
&amp;lt; at &amp;gt;kwalker | &amp;lt; at &amp;gt;orionhub

&lt;/pre&gt;</description>
    <dc:creator>Ken Walker</dc:creator>
    <dc:date>2013-04-25T20:28:36</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1878">
    <title>[orion-dev] Eclipse Bridge seems down for us</title>
    <link>http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1878</link>
    <description>&lt;pre&gt;
We'll keep re-dialing during the meeting to see if it comes back up

Ken Walker
Co-Lead Eclipse Orion Project | Tools for the Web, On the Web
http://orionhub.org | http://wiki.eclipse.org/Orion
&amp;lt; at &amp;gt;kwalker | &amp;lt; at &amp;gt;orionhub

&lt;/pre&gt;</description>
    <dc:creator>Ken Walker</dc:creator>
    <dc:date>2013-04-25T15:06:29</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1877">
    <title>[orion-dev] GSoC 2013 - Improve the Orion styling framework...</title>
    <link>http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1877</link>
    <description>&lt;pre&gt;Hello,

My name is Hiroyuki, I am an undergraduate student from University of
Aizu in Japan. It's nice to meet you.

Recently, I am interested in Web IDE such as Orion, Cloud9 and etc...,
because I have just been attempting to develop such application with my
friends. It is still in the planning stage, but we were discussing its
developing plan again and again, so I have thought over about Web IDE's
implementations.

However its project is under only student programmers, it has wishful
thinkings. Actually, when I looked over the Orion's source code on
GitHub, I realized that there are many things that I got lost on my project.


# Google Summer of Code 2013

In this summer, I would like to work for the Orion project as the GSoC
project. Through working, I want to cultivate a better understanding
about Web IDE.

From the ideas page, I found the idea ""Improve the Orion styling
framework and add additional languages"", and I am interested in it. Is
it OK to apply to GSoC 2013 for that?

I'm concerned that I might be late.


# Question

If it is OK, I have a question.

About the first part of the idea is said that "to add support to the
built in styler for HTML and mixed-mode". To confirm my recognition of
the task, I would like to ask you the following question:

For example,

```
&amp;lt;html&amp;gt;
    &amp;lt;head&amp;gt;
        ...
        &amp;lt;script&amp;gt;
           {A JavaScript code}
        &amp;lt;/script&amp;gt;
        ...
        &amp;lt;style&amp;gt;
           {A CSS code}
        &amp;lt;/style&amp;gt;
        ...
```

if there is the above, then Orion's Text Editor should style each part
of HTML, JS and CSS by appropriate styles(such as coloring, etc...)
respectively.

However, it hasn't yet been implemented the styling features that can do
that, so we need to implement it. It is the first task of that idea,
isn't it?


That is all. Thank you.
&lt;/pre&gt;</description>
    <dc:creator>Hiroyuki Sano</dc:creator>
    <dc:date>2013-04-25T12:13:13</dc:date>
  </item>
  <item rdf:about="http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1876">
    <title>[orion-dev] Default workspace layout</title>
    <link>http://comments.gmane.org/gmane.comp.ide.eclipse.orion.devel/1876</link>
    <description>&lt;pre&gt;Hi Orion Developers,

Is it possible to tweak the default mapping generation (Projects, Users, Workspaces) to follow the file structure like:

&amp;lt;root&amp;gt;/
/user1
/workspace1 (metadata)
/project1 (metadata)
/project2 (metadata)
/workspace2 (metadata)
/project1 (metadata)
/project2 (metadata)
/user2
/workspace1 (metadata)
/project1 (metadata)
/project2 (metadata)

The guid-like generation then will be as a feature, which can be switched on/off. This will give great flexibility for those who wants to integrate with Orion at lowest level (file system) reliably. Also the remapping at every request as well as the mapping management (bottleneck) itself can be disabled, if it is not needed.
What do you think?

Regards,
Nedelcho

&lt;/pre&gt;</description>
    <dc:creator>Delchev, Nedelcho</dc:creator>
    <dc:date>2013-04-25T09:32:43</dc:date>
  </item>
  <textinput rdf:about="http://search.gmane.org/?group=$group=gmane.comp.ide.eclipse.orion.devel">
    <title>Search Engine</title>
    <description>Search the mailing list at Gmane</description>
    <name>query</name>
    <link>http://search.gmane.org/?group=$group=gmane.comp.ide.eclipse.orion.devel</link>
  </textinput>
</rdf:RDF>
