Hi, Tim, and all,
Attached is a fileout providing changes to the project-info dialog as
requested for the benefit of the "showcase" on Squeakland.org.
Basically, the "project info" dialog now contains three "enumerated"
items, "Subject", "Age", and "Region". These three are all governed
by pop-ups (in local language) rather than by type-ins. The results
are included in the project manifest.
Important notes:
(1) It is essential that this be filed in to an image updated at
least through update 2246PolygonFix-kfr. If filed in to an earlier
image, subsequently loading updates will clobber some of the changes
provided here.
(2) Yoshiki is also modifying code in the EToyProjectDetailsMorph
area in this same time-frame, so integration is likely to be necessary
before our two fileouts are published.
(3) There are a few obvious rough edges which someone may wish to
tweak, though I don't know of any show-stoppers. For example, this
has always been an English-only dialog, but now that the field names
are localized, there may be layout issues in some languages (once
translations are available.) Also, for the pop-up fields, if they've
never been set they show as blank, whereas once they've been set to
"(none)" (equivalent to blank) they show the text "(none)". Probably
we should always show "(none)" when values for these three popups have
not been supplied. Also, since some of the fields are now type-in and
some are pop-ups, perhaps some UI convention (slight color
difference?) should be used to hint at whether a field functions as a
type-in or a pop-up.
(4) This turned out to involve quite a bit of code, most of it
written with a fever and at very late hours. So there's the distinct
possibility of errors. I did test it briefly and it seemed to work as
I expected. HOWEVER: it really needs verification by someone else.
(5) The Preamble (please read if planning to test or use):
-=------
Change Set: projectInfoPopUps-sw
Date: 8 August 2009
Author: Scott Wallace
Changes to the project-info dialog, in support of new data desired for
the 'showcase' on squeakland.org:
- 'Sub-Category' removed.
- Subject, Age, and Region are added as pop-ups.
- Choices for Subject, Age, Region popups, and corresponding codes,
obtainable from web-site.
- Project manifest now includes Age, Subject (category,) and Region
info. The codes are strings of numbers, e.g. '554' as a Subject code
means 'Language Arts'
(look in #defaultAgeTriplets, #defaultSubjectTriplets,
#defaultRegionTriplets on class-side of EToyProjectDetailsMorph.)
- Names of fields are presented to the user in localized form.
- Choices for values of pop-up fields are presented to the user in
localized form.
Notes:
- There is support provided for obtaining up-to-date lists of the
subject, age, and region alternatives from the web site (see
EToyProjectDetailsMorph class updateTripletsFromWebSite) but it is not
actually called at this point, out of concern for potential for long
delay if connection to web site is slow.
- The *region* codes are at present *not* obtained from the web-site
(even when the user explicitly calls #updateTripletsFromWebSite,) but
rather a 'fake' set of regions, basically the continents, is
provided. This is probably temporary. We have no reasonable way to
confront the user with a pop-up showing 250 choices.
However, as per Tim's request, I have made it a point to include
Antarctica in the region list. (Tim: look at method
#defaultRegionTriplets for the current point of departure, if you want
to adopt that, temporarily at least, on the web site. And/or of
course change any defaults as needed.
-----------
Cheers,
-- Scott
On Jul 16, 2009, at 9:25 PM, jira(a)immuexa.com wrote:
> [ http://tracker.immuexa.com/browse/SQ-154?page=comments#action_35752
> ]
>
> Milan Zimmerman commented on SQ-154:
> ------------------------------------
>
> This makes sense. I am out of time now, but will test tomorrow or
> early weekend.
Thank you, Milan!
By mutual agreement among Bert, Yoshiki, and me, we decided to push
the latest fixes embodied in SQ-88, SQ-154, and SQ-257 to the etoys4.0
update stream today. This will make it easier for more people to
test, and we still have time before squeakfest/brasil to fix any
issues that may arise.
Cheers,
-- Scott
Hi,
I'm forwarding this to the Etoys developer list, someone will know the
answer :)
You may want to subscribe at
http://squeakland.org/discuss/etoys-dev/
- Bert -
On 24.08.2009, at 09:43, YunJae Jang wrote:
> Hi! I'm Korean Squeaker. (JangGoon)
>
> I have one question about Etoys translation.
>
> 1. I install Etoys 4.0 beta (http://svn.squeakland.org/installers/Etoys-To-Go-4.0.2253-beta.zip
> ), but I can't choose Korean in Language.
>
> 2. Then, I'm tring to find the ko folder but, ko folder have no
> existance in locale folder.
>
> 3. However, korean translation file(ko.po) exist in sugarlabs pootle
> server. (http://translate.sugarlabs.org/ko/etoys)
>
> 4. How can I use or add to korean Translation in Etoys 4.0 public
> release?
>
> Thanks!
>
> --
> =====================================
> 장윤재 Jang, Yun Jae
>
> Dept. Computer Science Education, Korea Univ.
> InC Lab : http://inc.korea.ac.kr
> InC Email : yunjae.jang(a)inc.korea.ac.kr
>
> Email : janggoons(a)gmail.com
> Blog : http://janggoons.kr
> twitter : http://twitter.com/janggoon
> C.P. : +82-10-2658-8712
> =====================================
As people are probably aware, a .png thumbnail of an etoys project is
now put inside the outer .pr file, but for the time being we haven't
removed the .gif thumbnail that historically has been put placed
*alongside* (rather than *within*) the outer .pr file. See: http://tracker.immuexa.com/browse/SQ-274
Several people have advocated removing the .gif file; it clutters up
the Squeaklets directory, for one thing, and it's now redundant, and
has only been retained for compatibility with Superswiki and possibly
Superswiki 2.
Now the question arises afresh: should we now stop producing the .gif
file -- thus requiring Superswiki and other clients who may be
interested in a thumbnail to use the embedded .png file?
On the JIRA ticket, in early August, Antonio reported 'That's Masashi
answer: "As I seen the code, I think the modification would be quite
trivial. I welcome the new, refactored project format."'.
So... do people think the time has now come (in advance of final
shipment of this summer's release) to remove the .gif?
-- Scott
I noticed yesterday that Yoshiki updated the FishAndPlankton example
project a year ago in the Sugar release, but that was still not in the
Squeakland repository. Same for the Guides and translations, which
were not updated for quite some time. Conversely, the launcher/
tutorials/demo projects were only updated in the Squeakland repository.
I (manually) synced the two repositories on Sunday but we need to find
a way to only have one repo, really.
I think the Sugar release and Squeakland release are virtually
indistinguishable now, right? Off the top of my head the only
difference is the swapControlAndAltKeys preference, which is enabled
for Sugar but not for Squeakland. But we really should set this to the
platform default anyway:
http://tracker.squeakland.org/browse/SQ-304
Other than for that, do we still need two different release images? Or
can we simply share the whole image folder now?
- Bert -
Hi all,
Made some changes to JIRA to help with release planning. Please
review this JIRA glossary first:
http://confluence.immuexa.com/display/sq/Process
If the terms don't seem to make sense, then return to the glossary and
read them again and again.
I've used JIRA with a wide variety of software teams over the last
five years, so please rely upon my experience until it becomes more
familiar.
JIRA is used by Apache and many other large open-source projects ...
there's truly a "there" there, but only if you relax and use it as it
was designed to be used.
The changes:
1. "must-have" = critical priority
2. "desirable" = normal priority
3. "possible" = eventual priority
4. "desirable but complex or risky" = optional priority
5. "published!" = closed
6. "ready for testing" = resolved
7. "internationalization" = moved in with the rest (in 4.1 release)
8. "pango" = moved in with the rest (in 4.1 release)
9. "dormant, residual, historical" = optional priority in someday
release
10. two big versions ... "etoys 4.0 - summer 2009" and "etoys 4.1 -
winter 2010" (summers will be even numbered, winters will be odd
numbered)
The reason for all of this is so that we can actually look at the
roadmap and see where we are. Things were too fragmented. They were
going against the way JIRA works.
So now, there's three release bins showing on the roadmap:
a. review ... all new stuff goes here and gets moved elsewhere after
discussion
b. etoys 4.0 ... current release
c. biz/ed ... these are the non-Etoys items that the business and
education teams must do
There will always be these three at the top of the release road
map ... click "all versions" to see etoys 4.1, etc.
Anyway, I hope this makes things clearer. As you continue to use
JIRA, you'll see that many tools exist that require this
functionality. (Try "Find Issues", for example, then click "New".)
So if you're wondering:
* what should I test? Click "Resolved" under Project Summary o see
a list of resolved issues. These need testing.
Add a comment saying, "works for me" and then put the change to the
update stream and click "Closed" (aka Published)
Would other words be more clear? Perhaps to some. In my opinion,
let's all try to learn these five states (scheduled, in progress,
resolved, closed) and five priorities (blocker, critical, normal,
eventual, optional). They work.
Also, remember ... the best view is "road map" ... it sorts by
priority into releases. It also has a nifty green & red progress bar
that motivates.
Now, I'm going back into my post-Squeakfest cave for a while ... in
the next week or so, please help move things in "review" or "etoys
4.0" that we can't do easily in the next few weeks to "etoys 4.1"
Our overall goal is to have Etoys 4.0 be all green in the roadmap.
Another goal is to have zero issues in "review".
Sorry for the draconian changes, but I couldn't get my finger on the
pulse of the release the way it was. This is a better way to work.
Tim
Hello,
The Public Education Departments are complaints from teachers about how
to find digital educational materials that may concern them, so they try
to unify criteria and establish standards for storage ...
As far as I know there are two widely used standards: SCORM, cataloging
more oriented to test-type material, yes/no exercises etc., and IMS
(http://www.imsglobal.org/), much less "behaviorist".
IMS Common Cartridge is basically a standard digital learning content
that defines a usage profile of four existing specifications:
1 .- IEEE LOM (metadata)
2 .- IMS Content Packaging v1.2
3 .- IMS Question & Test Interoperability
4 .- IMS Web Authorization Service v1.0
We're not talking about fun subjects at all, but in my opinion, to
facilitate the integration of projects done in Squeak in these public
servers is very important.
European Community is trying this:
http://ec.europa.eu/information_society/activities/econtentplus/index_en.htm
A little more:
http://www2.sims.berkeley.edu/research/projects/how-much-info-2003/execsum.…
Of course, nor teacher neither children can fill a big questionnaire
with dificult questions at save project moment, but this two materials
(metadata packaging by code at save moment and the information
introduced by the project's creator) could approach to IMS standard.
Regards and sorry for my english
Hi all,
I haven't spoken up here for a while. I halted my squeak work and thinking for a while and am just now finding reason to think about it again.
One of the outside things I have stumbled onto is inkscape. a svg drawing program. I did work a while back to fix curved polygons and remove some limitations from stars. During that work I got to wondering if I was doing something important or just reinventing the wheel in squeak. I had not looked for ideas or inspiration much outside of the squeak morphic environment. Turns out I seem to have done a little of both but maybe much more wheel reinventing.
Inkscape is a drawing program with some pretty powerful features. I doesn't do a lot of scripting though it allows enough extensions that I have seen produced from it animations of gears in a clock.
The thing people who play with morphic will find interesting are the basic objects that inkscape supports and the way they use handles to support the various features. Compare our rectangles, ellipses and stars to theirs. Notice that they also have ways to manipulate paths and add a special object for spirals.
All of these objects are directly manipulable in interesting ways. Even more control can be gotten from sets of buttons and parameters in button bars.
On the negative side, all this control makes for lots of clutter. There are also some annoying things that happen that squeak avoids. For example pulling prototype objects out of a parts bin when you want them beats having a modal cursor that generates a new one at each click.
Anyway, I highly recommend some play with inkscape's objects for inspirations as to what morphic could and should do in the future.
Inkscape is downloadable and works on all three platforms. (Mac, Windows, Linux). I have been playing with it on a ubuntu 8.04 system.
http://www.google.com/search?q=inkscape&ie=utf-8&oe=utf-8&aq=t&rls=com.ubun…
Yours in curiosity and service, --Jerome Peace
...nested projects can be really confusing...
of course, I'm agree, that 's an old question, but I see it as an extra
that provides an unnecessary hardship, as if it could be nested
documents within documents: it is never really necessary.
2cc