Hi folks.
We were discussing about this in the Pharo mailing list but the idea is for
all Smalltalkers. I am not sure if this will work, but it is worth to try it
as I don't have anything to loose.
We were thinking to have a place, an environment and hopefully a community,
where we can freely discuss about Smalltalk papers or OO in general. All
smalltalkers of all flavors can join, discuss, tell their experiences and
thoughts, share and learn.
The main purpose about that list is:
- be able to FREELY discuss about papers about Smalltalk or OO in general. I
say freely because maybe someone gives an opinion of a paper that the person
who wrote it is also in this place. We are all professional and I think we
can discuss with respect.
- LEARN.
Other uses:
- Don't reinvent the wheel. Maybe I wanted to do something and I read that
XXX person did YYY. So, I can look at it.
- Be aware of what other people is doing, working, writing and learning.
- Have different opinions of a certain topic / paper.
- A little step to join all the Smalltalk community in one place. We can
meet people, join forces, etc.
- Help in the preparation, ANN, collaborate, etc in Workshops, conferences,
and so on.
- Ask for help on review. Several times someone has several papers to review
for a certain conference. This can be a place to ask for that help.
- Publish papers that were rejected from someone. How many times some papers
where rejected but do you still read it and find it useful ?
- Educate people and being educated.
- Share latex template, commands, or tricks related to smalltalk code for
example.
- Discuss about research in general.
- Ask for a certain topic. Suppose I want to start to work in XXX topic, I
can ask to see if someone knows related papers or work.
- others
In two words: DISCUSS AND LEARN.
FAQ:
1) Which is the address?
http://groups.google.com/group/smalltalk-research
2) Do I need to be "Researcher" to join ?
Not necessary. You may just be interested.
3) Is there a Nabble interface?
Yes: http://n4.nabble.com/Smalltalk-Research-f1473466.html
Now, please what I would appreciate is if you can help me to you distribute
(I am not in Gemstone, Cincom or GNU for example) this ANN. It would be cool
to create a community. I know there are a lot of Smalltalk researchers that
doesn't have time to follow the active smalltalks lists. If you can send
private mails to them would be fantastic!
Thank you very much.
Mariano
Hi,
I want to add some attributes to a generated embeded link (an image I'm
embedding)... for instance, I want to say something like this:
+style:'width: 500px' myImage+
is there a way to do something like this?
Cheers,
Esteban
Hi:
I installed (using the Metacello configuration) the Seaside 3.0 and
migrated one of my applications.
Now, playing with the new Pier 2:
1. Reading this list I managed how to configure and setup, but I can't
make it show the look of the
older version nor the possibility of change to the old Events look.
These features are not availables?
2. I want to add an own seaside component on a Pier page, but the
combo to select only show the
examples and so.....how I can add to this list my own seaside components?
Thanks.
--
=================================================
Germán S. Arduino <gsa @ arsol.net> Twitter: garduino
Arduino Software & Web Hosting http://www.arduinosoftware.com
PasswordsPro http://www.passwordspro.com
=================================================
First let me assume that WAKomEncoded is what I should be starting, versus WAKom ?
Us old Smalltalkers remember starting WAKom so in WikiServer startup that is what happens.
I *guess* it really should be WAKomEncoded?
So what's the fall out, I mean I can stuff UTF8 chars into PRPages... Happy Happy.
Well not quite, I got a support email out of South Korea that the UTF8 character that was entered for the
Page title was being mangled. In fact if they use the *wrong* character the app would hang as it's loading
from binary storage to instantiate the PRPage.
In looking at this it turns out that because WAKom is used, the UTF8 data from the request is being passed
as a String into PRStructure (instance var name). Later lazy initialization is used to populate title
title
"Answer the title of the receiver, essentially the name but starting uppercase."
^ title ifNil: [ title := self name capitalized]
Now here is the bad part, the capitalized runs Character>>asUppercase which actually is kinda unicode aware
so it's attempting only to deal with wide characters but since the UTF8 character is multiple bytes in a String then it mangles
the first byte to uppercase thus destroying the meaning of the UTF8 sequence.
However now if I restart with WAKomEncoded the squeak to utf8 process then messes the UTF8 data that was
stored in the binary data file.
So thoughts on how to fix things when I load the PRPages from storage, and what fields would need fixing are welcome
--
===========================================================================
John M. McIntosh <johnmci(a)smalltalkconsulting.com> Twitter: squeaker68882
Corporate Smalltalk Consulting Ltd. http://www.smalltalkconsulting.com
===========================================================================
I've been writing a couple of Pier components, let's call them
StructureA and StructureB (both subclassed from PRStructure), and each
has a corresponding view (answered by #viewComponentClass), ViewA and
ViewB (subclassed from PRDefaultView).
Now I find I want to embed a 'B' inside of an 'A', so that ViewB gets
rendered inside of ViewA.
I've added a StructureB instance as a child of the StructureA instance.
What I can't figure out is, from within ViewA>>renderContentOn:, how do
I go about getting hold of an instance of ViewB, so that I can pass it
as an arg to "html render: ... " ?
(I could instantiate ViewB myself, but presumably I would at a minimum
have to set the context ivar to something, but I know not what.)
Or am I going about this the wrong way?
Cheers,
Nick Brown
Hi,
I've created a PRJQuerySearchWidget as a plug in replacement for the
existing PRAjaxSearchWidget. It uses the new Seaside JQuery autocomplete
widget, which Lukas has recently added. I implemented it as I'm using other
JQuery widgets on my page and didn't want to be without autocomplete search
AND I haven't found a satisfactory way to mix scriptaculous and jquery
widgets on the same page.
I'll check it in as soon as a couple of fixes go into Seaside:
http://lists.squeakfoundation.org/pipermail/seaside/2010-January/022458.htmlhttp://lists.squeakfoundation.org/pipermail/seaside/2010-February/022485.ht…
Currently if you create an default pier instance with:
PRPierFrame registerAsApplication: 'pier' kernel: (PRKernel named:
'pier')
..Scriptaculous libraries (if present) are added in PRPierFrame
class>>configureApplication:
Perhaps we should allow either JQuery or Scripaculous to be specified for
this default implementation, or at least add the JQuery libraries (if
present), if the Scriptaculous libraries are absent.
Thoughts?
Nick
I am trying to figure out the relation between PRFile, MAFileModel,
MAFileDescription, and possibly others. They seem to duplicate a lot of
information, such as mimetype and filename.
I'm using the Pier-1.2 download.
PRFile says it references an instance of MAFileModel, but a lot of test
code for seems to get by without an MAFileModel.
I've looked for references to the classes, but have found either
extremely terse and trivial tests or the setupup for, e.g., defaultCSS.
I also don't know which of the classes is intended for display, or how
to display them.
Initially, I just want to use these to display links to files that are
on the disk. Presumably that will use MAExternalFileModel somehow.
Later on, I may want to have pseudo files that include the ability to
select a format in which to download the file or to display the file
inline on the web page.
Ross Boylan
