[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [ide4edu-dev] Priorities
|
There are two parts to providing a build.
The first part is to create an automated script that can take the
existing code out of CVS, compile it, assemble it into bundles, and
create an update site that we can use to load our code into an existing
Eclipse installation. Much of this is already done. If I recall
correctly, the first part--based on the Athena Common Builder--is mostly
done (see the org.eclipse.ide4edu.releng project). The next step is to
get them running on the eclipse.org build server's Hudson instance. Bug
288663
The second step is to use the Eclipse Package Project (EPP) to create a
script that builds a fully-functional (all-in-one) single download of
"IDE4EDU" that students can grab and immediately use. I had this working
at one point, but never had it fully automated. Bug 242281.
Wayne
Miles Billsman wrote:
Hello!
I agree with Wayne about this list of priorities for the release:
1) Get a proper build working (Bug 288663)
2) Remove code that accesses non-API (Bugs 300275 and 300672)
3) Simplify the menu bar and toolbar. (Bug 299848)
Other things like better wizards, hiding packages would be nice as
well but are not essential to getting an initial, useful version of
IDE4EDU out there.
I don’t think Wayne wants us to completely decouple IDE4EDU from the
platform code. He just doesn’t want us to use any code that throws
“Discouraged access” warnings because that code is not guaranteed to
remain as is from version to version of Eclipse. This means all the
class, package and project wizards need to be reworked since they all
contain code that throws these warnings.
So Wayne, out of curiosity what is involved in getting a proper build
working? Does it mean build the RCP app that only loads the Java Lite
plugin and the JDT stuff as Cory is doing? Or does it mean something
different?
Cheers, Miles
*From:* ide4edu-dev-bounces@xxxxxxxxxxx
[mailto:ide4edu-dev-bounces@xxxxxxxxxxx] *On Behalf Of *Cory Matheson
*Sent:* Monday, January 25, 2010 9:21 PM
*To:* Eclipse IDE for Education
*Subject:* Re: [ide4edu-dev] Priorities
I have some doubts that we will be able to completely decouple IDE4EDU
from the platform code. From what I've gathered thus far, the project
is deeply intertwined to the platform - unless of course we re-write
essential underlying code....
However, wouldn't packaging as an RCP app sort of address this? At
least that way, we have control over the platform being used, so we
should only package the platform that we are compatible with?
Cory.
On Mon, Jan 25, 2010 at 6:20 PM, Wayne Beaton <wayne@xxxxxxxxxxx
<mailto:wayne@xxxxxxxxxxx>> wrote:
I agree that decluttering the UI is am important consideration. I'm
willing to make it number 3.
At this point, however, not having a proper build is a bit of an
exposure. It's hard to drive adoption if we don't have something that
we can distribute. Code that uses non-API is brittle and risks
breakage with each new release of the underlying software.
Wayne
Brenda Sadoway wrote:
I agree with Cory that concentrating on de-cluttering the UI would be
best because it gives that first impression to a brand new user that,
if they're also brand new to programming, can scare them off. It isn't
just toolbars and menus that need to be stripped down though; I think
simplifying common processes (wizards, debugging, renaming files
[simplistic refactoring?]) might also be looked into.
-Brenda
Quoting "Cory Matheson" <cmatheson.can@xxxxxxxxx
<mailto:cmatheson.can@xxxxxxxxx>>:
I'm not sure about other universities, but our last official day of
classes
seems to be April 12 this year. Of course, then we have exams and stuff
start shortly thereafter. I would set a final milestone around then.
(Keeping in mind, we have other courses, and they are probably going to do
the same).
I'd like to concentrate on UI de-cluttering and general usability.
(IMO, the
UI is everything for the 1st time user, and I think that is what turns
them
off the most when they see 3000 options and don't know what any of
them do).
Going to concentrate on the main (IDE4EDU) release for now - can
always port
the code later to the scheme plugin once we got it all worked out.
Also, UI de-cluttering should also indirectly help with your priority
#2, in
that we will also most likely need to create our own wizards, etc, and
then
we hopefully won't need to access as many non-APIs.
Thanks,
Cory.
On Mon, Jan 25, 2010 at 12:42 PM, Wayne Beaton <wayne@xxxxxxxxxxx
<mailto:wayne@xxxxxxxxxxx>> wrote:
FWIW, my two highest priorities wrt IDE4EDU are:
1) Get a proper build working (Bug 288663)
2) Remove code that accesses non-API (Bugs 300275 and 300672)
I will update the project plan accordingly. I will set a milestone date
that coincides with the end of the UCOSP term. Can somebody give me
the date
for that? I'll set the release date for sometime during the summer.
Does anybody else want to express their priorities for this release?
Wayne
--
Wayne Beaton, The Eclipse Foundation
http://www.eclipse.org
I'm going to EclipseCon!
http://www.eclipsecon.org
_______________________________________________
ide4edu-dev mailing list
ide4edu-dev@xxxxxxxxxxx <mailto:ide4edu-dev@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/ide4edu-dev
_______________________________________________
ide4edu-dev mailing list
ide4edu-dev@xxxxxxxxxxx <mailto:ide4edu-dev@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/ide4edu-dev
--
Wayne Beaton, The Eclipse Foundation
http://www.eclipse.org
I'm going to EclipseCon!
http://www.eclipsecon.org
_______________________________________________
ide4edu-dev mailing list
ide4edu-dev@xxxxxxxxxxx <mailto:ide4edu-dev@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/ide4edu-dev
------------------------------------------------------------------------
_______________________________________________
ide4edu-dev mailing list
ide4edu-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/ide4edu-dev
--
Wayne Beaton, The Eclipse Foundation
http://www.eclipse.org
I'm going to EclipseCon!
http://www.eclipsecon.org
